June 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1041966] A new Build cycle involving java-1_7_0-openjdk-bootstrap has appeard
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

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

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt(a)suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c35 --- Comment #35 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to Josef Reidinger from comment #31) > OK, now I do some debugging here is result: > > 1. in gnome it looks ok for me. I see icon, but it is not properly grouped. > > 2. passing name was more tricky then I though, as there is no simple way to > modify it in y2start. But I can pass it to y2start from other script we have > there, but at least in gnome it does not help with grouping. Still I see two > different windows there. > > I do not have at hand KDE, so if you can test how it will look like if you > call > > /usr/lib/YaST2/bin/y2start <module e.g. bootloader> qt -name YaST2 > > and test it if it helps at least in KDE. I see that change is > > WM_CLASS from "ruby", "YaST2 bootloader @ dhcp77" to "YaST2", "YaST2 > bootloader @ dhcp77" Grouping works fine, but the icon is still missing. Appending "-icon yast" to y2start as well fixes that. Note that for wayland support qApp->setDesktopFileName("YaST") needs to get called on startup as native. I had a talk with a KDE Plasma developer, he told me that the *second* field of the WM_CLASS is important for connecting windows to applications. Qt gets that from QCoreApplication::applicationName(), so need to call setApplicationName with "YaST2" and not the window title. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c34 --- Comment #34 from Josef Reidinger <jreidinger(a)suse.com> --- (In reply to Oliver Kurz from comment #32) > Created attachment 728399 [details] > screenshot conducted during normal non-remote installation with label in > dialog hidden behind border > > > if you check https://openqa.suse.de/tests/925004#step/welcome/1 you see that > > even in past was there that YaST2 @ something > > For installations using ssh+X-forwarding I consider the display of the title > helpful because it allows identification of the installer window on the > users desktop where there could be multiple unrelated windows. Also how it > looks would very much depend on what the customer is using, e.g. macOS, > ubuntu gnome, etc. We should not care much about how it looks there but > still show any string, at least "YaST2". > > For the physical, non-remote installation we should care about a proper UX > because the local installer system is fully in the hand of SUSE/openSUSE and > therefore a visual regression reflects badly on the project. These are the > screens early testers and also reporters will see. And a screenshot like the > attached looks not nice. > > > so maybe skip installation part, to not mention it is installation client? > > I am sorry but I don't understand what you mean by this sentence. I mean if it helps to show in installation "YaST2 @ dhcp77" instead of "YaST2 installation @ dhcp77" ? In general problem is that such title have to be set very early, so I would like to have it simple, as even error handlers are not set yet. I can change title to whatever, but I am favor of having too much logic in it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043218] YaST crashes on installation of banshee
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043218 http://bugzilla.suse.com/show_bug.cgi?id=1043218#c4 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |YaST2 Assignee|zypp-maintainers(a)forge.prov |yast2-maintainers(a)suse.de |o.novell.com | QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com --- Comment #4 from Michael Andres <ma(a)suse.com> --- Fixed potential crashes in libzypp: TRUNK libzypp 16.12.1 SLE-12-SP3 libzypp 16.12.1 SLE-12-SP2 libzypp 16.12.1 SLE-12-SP1 libzypp 15.25.1 SLE-12 libzypp 14.45.5 ->yast2-maintainers to fix pkg-bindings -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c33 --- Comment #33 from Lukas Ocilka <locilka(a)suse.com> --- Hint: we need manual testing of real /official/ ISO. Then we can compare "what is in the ISO" vs "how it behaves" vs "the latest package(s)". -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043534] New: GDB package is part of "Plasma 5 Desktop" pattern
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1043534 Bug ID: 1043534 Summary: GDB package is part of "Plasma 5 Desktop" pattern Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: anton.smorodskyi(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GDB package is part of "Plasma 5 Desktop" pattern Expected : GNU source level debugger has no relation to Plasma 5 Desktop so it should be removed from pattern -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c32 --- Comment #32 from Oliver Kurz <okurz(a)suse.com> --- Created attachment 728399 --> http://bugzilla.suse.com/attachment.cgi?id=728399&action=edit screenshot conducted during normal non-remote installation with label in dialog hidden behind border > if you check https://openqa.suse.de/tests/925004#step/welcome/1 you see that > even in past was there that YaST2 @ something For installations using ssh+X-forwarding I consider the display of the title helpful because it allows identification of the installer window on the users desktop where there could be multiple unrelated windows. Also how it looks would very much depend on what the customer is using, e.g. macOS, ubuntu gnome, etc. We should not care much about how it looks there but still show any string, at least "YaST2". For the physical, non-remote installation we should care about a proper UX because the local installer system is fully in the hand of SUSE/openSUSE and therefore a visual regression reflects badly on the project. These are the screens early testers and also reporters will see. And a screenshot like the attached looks not nice. > so maybe skip installation part, to not mention it is installation client? I am sorry but I don't understand what you mean by this sentence. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1037891] All YaST module window names show "ruby" instead of a more specifc name (was: Yast module windows in Plasma: generic x window icon and grouped as "ruby" in task manager)
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.suse.com/show_bug.cgi?id=1037891 http://bugzilla.suse.com/show_bug.cgi?id=1037891#c31 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(fvogt(a)suse.com) --- Comment #31 from Josef Reidinger <jreidinger(a)suse.com> --- OK, now I do some debugging here is result: 1. in gnome it looks ok for me. I see icon, but it is not properly grouped. 2. passing name was more tricky then I though, as there is no simple way to modify it in y2start. But I can pass it to y2start from other script we have there, but at least in gnome it does not help with grouping. Still I see two different windows there. I do not have at hand KDE, so if you can test how it will look like if you call /usr/lib/YaST2/bin/y2start <module e.g. bootloader> qt -name YaST2 and test it if it helps at least in KDE. I see that change is WM_CLASS from "ruby", "YaST2 bootloader @ dhcp77" to "YaST2", "YaST2 bootloader @ dhcp77" -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1043536] New: Kwallet (with gpg key encrytion) does accept the password input to open the wallet only after about 8 repetitions
by bugzilla_noreply＠novell.com 09 Jun '17

09 Jun '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1043536 Bug ID: 1043536 Summary: Kwallet (with gpg key encrytion) does accept the password input to open the wallet only after about 8 repetitions Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is reproducible stable to a 100% I open my session. I open Kontact. As the kmail account passwords are stored in wallet with kgpg, I was usually asked the password one time. Then it opens, fine. Now, observed behavior: you input the password, the password is not accepted (I did proof this by watching every stroke, it is(!) the right one). So I do a repetition of 8 time of the password input, trying again and again. At a point then suddenly the password is accepted. You can now work with problems as the wallet opened with the very password it claimed was wrong before. Desired behavior: kwallet should open with the password after one input. The only particularity is to be seen when you use an external screen and keyboard. This should however be unrelated but is mentioned for completeness: If your password input of kde is on the external screen it will jump at the refusal to the laptop screen. However, the input from the external desktop is correctly taken (at least the "dots" appear in the window). Kwallet settings: - only one wallet for local and internet. - kgpg signature with 4096 RSA (no email address as this signature is used for wallet only). -- You are receiving this mail because: You are on the CC list for the bug.

1 5