September 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 995930] GPG clients (GPA, Kleopatra, Kgpg, etc.) cannot sign, change ownertrust
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=995930 http://bugzilla.suse.com/show_bug.cgi?id=995930#c1 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com Assignee|security-team(a)suse.de |premysl.janouch(a)suse.com --- Comment #1 from Marcus Meissner <meissner(a)suse.com> --- assign to gpg maitnainer ... not sure whose fault this is -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 995782] Editing "proposal settings" doesn't recalculate size of / partition
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=995782 http://bugzilla.suse.com/show_bug.cgi?id=995782#c4 --- Comment #4 from Aleksa Sarai <asarai(a)suse.com> --- > This is intentional. There is a maximum size for the root partition that can > be set in a product's control.xml file. For example, this is the relevant > section of that file for SLES-12 SP2 (Leap 42.1 might be somewhat different, > but certainly similar): Okay, so what would be the process for proposing that openSUSE Tumbleweed / Leap have a different control.xml file? Open a FATE request (is there a FATE link for the original change that made this behaviour intentional)? And if we were to remove the <root_max_size> line (or set it to be unlimited), would YaST then correctly resize the root parition so that it takes up the entire disk? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 996985] New: 42.2b1, after installation and boot nothing visible except background
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.opensuse.org/show_bug.cgi?id=996985 Bug ID: 996985 Summary: 42.2b1, after installation and boot nothing visible except background Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: hohenecken(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 690591 --> http://bugzilla.opensuse.org/attachment.cgi?id=690591&action=edit This screenshot shows how it ends up finally, get stuck here, this is it. Did a clean install of 42.2b1, with KDE. The PC is of 2007, with some Nvidia Quadro graphics card of that time. The installation seemed to work finally, but on first boot, what happens is: The first coloured pictures of Grub and of the animated background work. But when it is then fully up, the task bar is visible for less than a fraction of a second, it immediately vanishes, no more windows are visible, just the background remains visible and the mouse arrow. Please see the screenshot, to get an idea. I can do nothing from there, except moving the mouse. But whereever I would try to click on, e.g. the corner, nothing happens anymore. So when I reach that state "fully booted up", this KDE system is unusable to me. Not sure which component to open this ticket against, and sorry I might be wrong here: - it might be a KDE issue - it might be a graphics card issue (but in this case, why do I still see the background screen, and the coloured screens before) - or it might be an installation issue in the sense that I should have chosen to go with non-default screen resolutions or drivers, but wouldn't know which to select in that case. As I couldn't open any window after this boot, also not sure how to debug this further. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 944659] After installing Leap M2, 9 out of 10 times, the system hangs with black screen, just after the bootloader hands over
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=944659 http://bugzilla.suse.com/show_bug.cgi?id=944659#c47 --- Comment #47 from milan zimmermann <milan.zimmermann(a)gmail.com> --- Fixed in 42.2 Alpha 3 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 944659] After installing Leap M2, 9 out of 10 times, the system hangs with black screen, just after the bootloader hands over
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=944659 milan zimmermann <milan.zimmermann(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NORESPONSE |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 995707] New: suspend terminates kde session
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.opensuse.org/show_bug.cgi?id=995707 Bug ID: 995707 Summary: suspend terminates kde session Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: m.waack(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suspend to RAM terminates the running kde session: suspend itself works, but if a user suspends the current kde session, after the resume he finds itself in front of the login screen and its session was closed. This issue is reproducable in several ways: 1. Klicking on K->Power/Session->Suspend 2. systemctl suspend 3. qdbus org.kde.Solid.PowerManagement /org/kde/Solid/PowerManagement/Actions/SuspendSession suspendToRam 4. qdbus org.kde.Solid.PowerManagement /org/freedesktop/PowerManagement Suspend All 4 actions terminate the current session. Leap was installed as an inline update from 13.2 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 996551] Make libldap library to be a symlink to libldap_r library
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=996551 http://bugzilla.suse.com/show_bug.cgi?id=996551#c1 Howard Guo <hguo(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Severity|Normal |Major --- Comment #1 from Howard Guo <hguo(a)suse.com> --- good idea! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 996916] lvm volume does not activate on boot
by bugzilla_noreply＠novell.com 02 Sep '16

02 Sep '16

http://bugzilla.opensuse.org/show_bug.cgi?id=996916 http://bugzilla.opensuse.org/show_bug.cgi?id=996916#c1 Neil Rickert <nwr10cst-oslnx(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nwr10cst-oslnx(a)yahoo.com --- Comment #1 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- This is probably the same issue as in bug 989871 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 995921] 32-bit Install image contains 64-bit programs "openSUSE42_2_xxx.exe"
by bugzilla_noreply＠novell.com 01 Sep '16

01 Sep '16

http://bugzilla.suse.com/show_bug.cgi?id=995921 http://bugzilla.suse.com/show_bug.cgi?id=995921#c4 Yasuhiko Kamata <belphegor(a)belbel.or.jp> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Yasuhiko Kamata <belphegor(a)belbel.or.jp> --- Just submitted to Tumbleweed as OBS submit request #424344: https://build.opensuse.org/request/show/424344. Tumbleweed repository (http://download.opensuse.org/tumbleweed/repo/oss/) will be updated after acceptance of this request. BTW, URL which mentioned comment#3 was changed due to update, check instlux-Tumbleweed_SVN62-*.i586.rpm in the following URL in future: http://download.opensuse.org/repositories/home:/belphegor_belbel:/instlux/o… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 996995] New: snapper diff should not request file list from snapperd if file is specified
by bugzilla_noreply＠novell.com 01 Sep '16

01 Sep '16

http://bugzilla.opensuse.org/show_bug.cgi?id=996995 Bug ID: 996995 Summary: snapper diff should not request file list from snapperd if file is specified Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stefan.bruens(a)rwth-aachen.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- snapper requests the list of changed files from snapperd, even if a list of files has been specified (either as last parameter or read from file via "-i"). snapper should either supply the filelist to snapperd for pre-filtering, or avoid the interaction with snapperd completely. -- You are receiving this mail because: You are on the CC list for the bug.

1 0