January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 991878] New: there are no .pc files for libibverbs-devel
by bugzilla_noreply＠novell.com 20 Jul '18

20 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=991878 Bug ID: 991878 Summary: there are no .pc files for libibverbs-devel Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bliu(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I cpmpile corosync with dependency on libibverbs-devel, and confirm that I 've installed the this package, but configure said there was no such lib. I checked the configure file which used pkg-config to check whether a devel package installed or not. Then I checked the pkgconfig directory, no pc files for the package above. And I used 'rpm -ql' to double confirm there is no pc file in the devel package. you can refer to 991846 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 936320] New: update to tumbleweed snapshot 12.06.2015 from a freshly installed 13.2 fails reliably.
by bugzilla_noreply＠novell.com 20 Jul '18

20 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=936320 Bug ID: 936320 Summary: update to tumbleweed snapshot 12.06.2015 from a freshly installed 13.2 fails reliably. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 639432 --> http://bugzilla.opensuse.org/attachment.cgi?id=639432&action=edit last yast2log Trying to update a 13.2 fresh install to tumbleweed. The first error I was able to capture was: undefined method split for it_IT:Array caller /usr/lib64/addr ruby/2.20/yast/builtimg.rb:455:in "splitsting" Then there comes a second error and it all aborts anyway. The installer calls for bugreport and requests yast2logs. Well, I attach you all I have. Interrupting the installation gives a normal 13.2 system. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 939506] New: iBus tray icon cannot display in Plasma 5
by bugzilla_noreply＠novell.com 20 Jul '18

20 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=939506 Bug ID: 939506 Summary: iBus tray icon cannot display in Plasma 5 Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cycharlie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- iBus functions under 42.1, but the tray icon does not show on the toolbar in Plasma 5. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 963321] New: Black screen after update of sddm
by bugzilla_noreply＠novell.com 18 Jul '18

18 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=963321 Bug ID: 963321 Summary: Black screen after update of sddm Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Subject says it all. Btw: xdm works flawlwss. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 956357] New: Inconsistent fonts between Qt4 and GTK/Qt5 apps when using Roboto
by bugzilla_noreply＠novell.com 13 Jul '18

13 Jul '18

http://bugzilla.suse.com/show_bug.cgi?id=956357 Bug ID: 956357 Summary: Inconsistent fonts between Qt4 and GTK/Qt5 apps when using Roboto Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 657030 --> http://bugzilla.suse.com/attachment.cgi?id=657030&action=edit qtconfig showing that Roboto Black is selected. Hi! I'm using openSUSE Tumbleweed with MATE 1.12 desktop and Qt theme is set to GTK+. After last snapshot, I switched the default font to Google's Roboto using `mate-appearance-properties`. I also changed it in KDE `systemsettings5`. However, I noticed that all Qt4 apps was showing a darker font. Then, when I tried to configure using `qtconfig`, it shows that the selected font was Roboto Black instead of Roboto Regular. I tried many things, but as far as GTK+ theme is selected, I could not change the font in `qtconfig` to Roboto Regular, which seems to be causing the problem. I'm uploading three figures: 1) The qtconfig showing that Roboto Black font is selected; 2) A screenshot of kwrite, showing the correct font (Roboto Regular); 3) A screenshot of digikam, showing the wrong font (Roboto Black). Here is additional information about my system: $cat /etc/os-release NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20151118" PRETTY_NAME="openSUSE Tumbleweed (20151118) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20151118" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 980389] New: Excessive dependencies on systemd
by bugzilla_noreply＠novell.com 10 Jul '18

10 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=980389 Bug ID: 980389 Summary: Excessive dependencies on systemd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem Assignee: jengelh(a)inai.de Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: dimstar(a)opensuse.org Found By: --- Blocker: --- Not all programs require systemd to run, in particular, within containers. One of them for example is boinc-client. Consider: mkdir /c/etc cp /etc/{passwd,group,shadow} /c/etc/ zypper -R /c in boinc-client systemd-nspawn -D /c -u jengelh /bin/sh -c 'cd ~; exec /usr/bin/boinc-client' This pulled in systemd not too long ago, but boinc does not actually use systemd itself in any way. Therefore, boinc-client.rpm is not to have requirements on systemd in its specfile, and in fact already had this removed earlier in 2015 already. A number of packages remain in openSUSE which still have these requirements on systemd though they should not. These need to be audited and, as time and joy permits, be edited to live without systemd where possible. Points to note: 1. 17:48 < DimStar> I think the main issue of dropping the systemd_requires all over the place is the fact that on a fresh system install, an rpm that might be triggered for install CAN be installed before systemd - then having some fun bugs to fix 17:51 < va> somehow we also manage to install aaa_base first, so if systemd really had this "needs to be there" thing, it should not be a big deal. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 979775] New: KDE session duplication
by bugzilla_noreply＠novell.com 09 Jul '18

09 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=979775 Bug ID: 979775 Summary: KDE session duplication Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: floux.dp(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I lock my session, I am able to create a new one with the already logged user. It seems weird. After that, I can still unlock the first session but cannot lock it anymore. At this moment, my screen becomes black with a message saying something like "It is impossible to lock your session, press CTRL+ALT+F2 then execute this command 'loginctl unlick-sessions' and then press CTRL+ALT+F7". -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1017175] New: With Kernel 4.4: crash of sddm and it seems of the X server (repeatable)
by bugzilla_noreply＠novell.com 06 Jul '18

06 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1017175 Bug ID: 1017175 Summary: With Kernel 4.4: crash of sddm and it seems of the X server (repeatable) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Laptop X201 Lenovo (not brandnew hardware). After update to 42.2 - when starting the system sddm shows user selection. 1st selection problem free. When selecting change user: a) if I click explicitly on the "Plus" symbol of sddm then a new sddm window opens and I can select that user. The users starts and I can from there select a third etc. b) if I just click on "change user" without selecting the "plus" explicitly, sddm crashes immediately. And the current user crashes too. It seems the the session is still running but that the desktop is reduced to a 1 mm wide stripe on the left side of the screen, no interaction is possible. A hard reset is necessary as all tty are now black and unresponsive. This is repeatable to 100%. c) if you do as in a) and you have several users open, then following applies: The use of ctrl+alt+F7,8,9 (etc) to select another user will result in immediate crash of sddm and all other open sessions. The rest is like in b). Repeatable to 100% - always. This is clearly kernel dependent: if you use instead the kernel from kernel stable (currently kernel 4.9) then all this does not happen any more. So the kernel 4.4 from the standard 42.2 breaks something on this system. If you are interested to find the reasons and guide me: I have both kernel versions installed and can switch easily. Starting the machine with the 4.4 is giving the results as of above. Repeatable. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 953012] New: Unable (or at least wasn't shown) to do "just" remove a package with zypper
by bugzilla_noreply＠novell.com 05 Jul '18

05 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=953012 Bug ID: 953012 Summary: Unable (or at least wasn't shown) to do "just" remove a package with zypper Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: trifanstanislav(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 Build Identifier: I try to remove firefox package. But zypper try to install another one, but I don't want it, and there is no option for skipping new install. Reproducible: Always Steps to Reproduce: $> sudo zypper remove firefox Actual Results: root's password: Loading repository data... Reading installed packages... 'firefox' not found in package names. Trying capabilities. Resolving package dependencies... The following NEW package is going to be installed: MozillaThunderbird The following application is going to be REMOVED: Firefox The following package is going to be REMOVED: MozillaFirefox 1 new package to install, 1 to remove. Overall download size: 33.1 MiB. Already cached: 0 B After the operation, 5.9 MiB will be freed. Continue? [y/n/p/? shows all options] (y): Expected Results: Add in the line: `Continue? [y/n/p/? shows all options] (y):` an option for remove only. It may be used `ro` option for remove only, and there should be information what it means. This actually is an usability bug. You may found tricks over the web that people do for that. That's totally not good and makes SUSE to loose points in usability versus other OSes. BTW: is not meaningful to use `p` for restart whatever it is. It make sense to put option with 2 or 3 chars that will make action intuitive to remember and use. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1017232] New: Polkit issue with networkmanager applet and multi-user environment
by bugzilla_noreply＠novell.com 04 Jul '18

04 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1017232 Bug ID: 1017232 Summary: Polkit issue with networkmanager applet and multi-user environment Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This issue appeared after updating to 42.2 from 42.1 (where 42.1 was a fresh install at the time). Take a system, create three users (can also be with less or more, not proven however). User A is creating a wlan connection that does not belong to all user but only to A. Other user shall not have the right to manipulate this connection. Start User B once A is active and the wireless connect is active. When user B starts up, it will ask for the root password in order to take control of the network. But it shouldn't ask! The Wlan connection is there, it works, network is up. There has been no request for additional services by this user (like VPN) ergo it should not see any necessity to ask for the root password. Still one time at the beginning of the session it pops up. When you start up user C, this sometimes happens. But not always. I have yet not seen any reasonable pattern to distinguish when it decides to do it and when not. Polkit should make sure that you have a sensible and working authorization network within ever user and should not ask for root Password when a network connection is already on and usable to that user. In this specific case the request comes from networkmanager applet in the system tray (which shows wrongly buy the way that I am connected to all users in the list of available networks. If I am connected or not (maybe this is an unrelated regression). -- You are receiving this mail because: You are on the CC list for the bug.

1 1