June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1041124] plasmashell exit with exit code 13
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1041124 Frank Schütte <F.Schuette(a)t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(F.Schuette@t-onli | |ne.de) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1041124] plasmashell exit with exit code 13
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1041124 http://bugzilla.suse.com/show_bug.cgi?id=1041124#c4 --- Comment #4 from Frank Schütte <F.Schuette(a)t-online.de> --- No, I can't. In a black screen I can press Alt-F2 and start plasmashell from there without problems. Is there a way to do the first(the start on login) start of plasmashell inside gdb? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042726] virtualbox is missing support for building kernel modules
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1042726 Andreas Stieger <astieger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger(a)suse.com, | |Larry.Finger(a)lwfinger.net, | |virt-bugs(a)suse.de Assignee|virt-bugs(a)suse.de |Larry.Finger(a)lwfinger.net -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1040197] Impossible to log into new user account which was created with “set password on first login”
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1040197 http://bugzilla.suse.com/show_bug.cgi?id=1040197#c4 --- Comment #4 from Yifan Jiang <yfjiang(a)suse.com> --- The specific g-c-c option seems simply doing the following password expiry change via accountsservice: $ /usr/bin/chage -d 0 -- $username See the example snippet at: > https://github.com/GNOME/gnome-control-center/blob/4cad3ca408125c15a0ddd952… > https://cgit.freedesktop.org/accountsservice/tree/src/user.c#n1797 While it might be on purpose we did not pass "nullok_secure" to the pam_unix module: > $ grep pam_unix /etc/pam.d/common-auth > $ auth required pam_unix.so try_first_pass Thus changing this line in common-auth should make the g-c-c option work, otherwise pam fails to authorize the no password login: auth required pam_unix.so try_first_pass nullok_secure -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042558] [Build 20170601] installer reports incorrect free space prediction in installation summary and then fails with "out of space"
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1042558 http://bugzilla.suse.com/show_bug.cgi?id=1042558#c2 Oliver Kurz <okurz(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(okurz(a)suse.com) | --- Comment #2 from Oliver Kurz <okurz(a)suse.com> --- (In reply to Lukas Ocilka from comment #1) > ## Observation > > There are two sets of tests in this bugreport > > ## Expectations > > One set per bugreport Sounds like you want to mock me. I wanted to give a reference to multiple test cases to clarify the differing situation for "clearly not enough space" and "probably not enough space" > ## More details > > ### Test Run 6558 > > There is an error reported to the user: Not enough disk space > http://lord.arch/tests/6558#step/installation_overview/3 > > No, you can't continue before fixing the problem > http://lord.arch/tests/6558#step/start_install/3 > > --> IMO behaves correctly, error does not let you continue yes, everything as expected here > ### Test Run 6559 > > There is a warning that it might not fit, but openQA test continues > http://lord.arch/tests/6559#step/installation_overview/3 > > RPM starts reporting errors, but that a common stderr, so it might be > warning, it might be anything, it's reported to the user, but RPM does not > report a failure (exit code) > http://lord.arch/tests/6559#step/install_and_reboot/17 > Or is this from libzypp running scripts directly? > > Then it fails hard, when RPMDB2SOLV finally reports an error with a > different exit code http://lord.arch/tests/6559#step/install_and_reboot/21 > > --> IMO Yast behaves correctly, you have been warned, you decided to > continue, but then it failed Maybe I am misreading the warning in http://lord.arch/tests/6559#step/installation_overview/3 but to me it reads like "If you continue the installation it will succeed but you will only have about 200MB in the installed system" which is hardly a usable setup. But the problem is that the installation can not continue successfully. This is why I argue that the calculation is wrong and the warning should be an error instead. > --> Yes, we could change Yast to start screaming when there is only, let's > say 10% left, or 15% left, or 20% or 55% ... the fact is, there is > nothing like a good number, and even btrfs experts don't know I know it's not easy, especially not with btrfs, but I would like to find a more conservative estimate, show an error and prevent installation. In the end when we can't find a better way, let an installation run empirically like I did but more fine grained HDD sizes. > --> The only thing that should be fixed is IMO RPM (scripts) to throw > a real error when "no space left on device" appears somehow, but that > might be also just the "xterm" post-script issue (ignoring errors) see > http://lord.arch/tests/6559#step/install_and_reboot/17 > > So, what do you feel needs to be fixed? 1. "no space left on device" should be a hard error while the installation is running 2. Show an error preventing installation when it can't succeed (like in http://lord.arch/tests/6558) but also for bigger HDD sizes where it *still* fails Maybe it's better to understand my reasoning when I explain that I came across bug 1039504 first. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1011147] Live Installer internal error "No base product found" in guided selection of disk/partition:
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1011147 Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sb56637(a)gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1011147] Live Installer internal error "No base product found" in guided selection of disk/partition:
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1011147 http://bugzilla.suse.com/show_bug.cgi?id=1011147#c10 --- Comment #10 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- Created attachment 727706 --> http://bugzilla.suse.com/attachment.cgi?id=727706&action=edit /etc/YaST2/control.xml from GeckoLinux ROLLING appliance I did not see this bug in GeckoLinux ROLLING appliances. They provide /etc/YaST2/control.xml that probably allows to avoid this problem. Needs to test. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 952876] Kontact fatal error at first start: Invalid parent
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=952876 http://bugzilla.suse.com/show_bug.cgi?id=952876#c2 Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- openSUSE 42.1 no longer maintained. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1042370] New: odp uses gcc6 to compile
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1042370 Bug ID: 1042370 Summary: odp uses gcc6 to compile Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Tumbleweed has been moving to GCC7 as the default compiler The package 'odp' though explicitly requires gcc6 in the spec file: BuildRequires: gcc6 [...] make V=1 CC=gcc-6 DESTDIR=%{buildroot} %{?_smp_mflags} install GCC6 is scheduled to be removed - so this will need to move up as well -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1040540] `qr` from package python-qrcode fails with "ImportError: No module named pkg_resources"
by bugzilla_noreply＠novell.com 05 Jun '17

05 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1040540 http://bugzilla.suse.com/show_bug.cgi?id=1040540#c2 --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1040540) was mentioned in https://build.opensuse.org/request/show/501164 Factory / python-qrcode -- You are receiving this mail because: You are on the CC list for the bug.

1 0