December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 955092] New: Some applications use bold font type
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=955092 Bug ID: 955092 Summary: Some applications use bold font type Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: 64bit OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: kde-maintainers(a)suse.de Reporter: artkoz78(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: In some applications used fonts are bold e.g. LibreOffice, VirtualBox, Qt4. Qt4 settings shows fonts Oxygen-Sans, Style Sans-Bold, changing to Sans-Book do not change anything. GTK font is set to Oxygen-Sans, Sans-Book. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 957015] New: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=957015 Bug ID: 957015 Summary: Software Update Error "License Agreement Failed" But A License Agreement Is Never Presented Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bill_wayson(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 657585 --> http://bugzilla.opensuse.org/attachment.cgi?id=657585&action=edit Zip file with error message screenshot, zypper.log, and pk_backend_zypp files. On Thursday (11/26/2015 PST) I was presented with several updates by the KDE software updater widget. I pressed the "Install Updates" button, and the update began. But it quickly stopped with a message dialog "Update Error The license agreement failed. The license agreement was not agreed to. To use this software you have to accept the license." The problem is that a license agreement dialog was never presented, and there was no indication of which of the updates required the license agreement (so that I could, say, deselect it). I did figure out that the license message seems to be part of the "openSUSE-2015-799 (1) - Optional update for desktop-fonts" update. The updater proceeds as expected when that package is deselected. I have left that patch uninstalled in case anyone wants to use it in troubleshooting this. I have attached a zip file that contains screenshots of the error message and of the Yast2 Systemd journal reader (because it appears to include related messages, the 6th and 5th messages from the bottom), and the zypper.log and pk_backend_zypp files. The latter file appears to be the log updated by the software updater and appears to include a pertinent message. This error is exactly the same as the error I have already reported on Tumbleweed as bug 956153. I hope I chose the correct component. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 953666] New: Steam will not run under XFCE
by bugzilla_noreply＠novell.com 20 Feb '18

20 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=953666 Bug ID: 953666 Summary: Steam will not run under XFCE Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: kmgramm(a)code3pse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 654668 --> http://bugzilla.opensuse.org/attachment.cgi?id=654668&action=edit this is the crash file steam created On a default install of Leap 42.1, using the XFCE desktop, steam crash out with the error: ken@linux-c9me:~> steam Setting up Steam content in /home/ken/.local/share/Steam /home/ken/.local/share/Steam/steam.sh: line 102: no match: **: Running Steam on opensuse 42.1 64-bit STEAM_RUNTIME is enabled automatically Installing breakpad exception handler for appid(steam)/version(0) No protocol specified No protocol specified Assert( Assertion Failed: Could not open connection to X ):/home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamexe/./updateui_xwin.cpp:337 Installing breakpad exception handler for appid(steam)/version(1.0) sh: /home/ken/.local/share/Steam/steam_msg.sh: No such file or directory crash_20151104165347_3.dmp[3866]: Uploading dump (out-of-process) /tmp/dumps/crash_20151104165347_3.dmp ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt". [2015-11-04 16:53:47] Startup - updater built May 5 2015 12:15:27 /home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamexe/./updateui_xwin.cpp (337) : Assertion Failed: Could not open connection to X /home/buildbot/buildslave_steam/steam_rel_client_ubuntu12_linux/build/src/steamexe/./main.cpp (513) : Assertion Failed: failed to initialize update status ui, or create initial window crash_20151104165347_3.dmp[3866]: Finished uploading minidump (out-of-process): success = yes crash_20151104165347_3.dmp[3866]: response: CrashID=bp-690e6f25-80e1-44c2-af11-efe312151104 crash_20151104165347_3.dmp[3866]: file ''/tmp/dumps/crash_20151104165347_3.dmp'', upload yes: ''CrashID=bp-690e6f25-80e1-44c2-af11-efe312151104'' On all three other native desktops (ie. KDE, GNOME, LXDE) have not issues. In all four cases, my steps were: 1) Boot from CD 2) Reformat HD 3) Pick default settings during install 4) After install finishes, run zypper update to patch 5) Activate NON-OSS Repo 6) Install steam 7) run steam as regular user On XFCE, steam starts, puts an icon on the desktop and displays the terms and conditions. That's it. All three other desktops download the steam client and proceed to the login / create account screen. For the record, this machine is an older i7, with 8GB RAM, and a NVIDIA Quadro FX 880M. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 819514] New: After update pushed 5/10/2013, network unavailable after resuming from sleep
by bugzilla_noreply＠novell.com 20 Feb '18

20 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c0 Summary: After update pushed 5/10/2013, network unavailable after resuming from sleep Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 First reported in this Forum thread http://forums.opensuse.org/english/get-technical-help-here/network-internet… For others in the thread, unknown whether recommendations were helpful. Note that others in the thread were not using Network Manager, whereas I am. For myself, my wireless networking was not functional (for that matter any networking) was functional resuming from sleep. Attempted to systemctl stop|start|restart network.service systemctl status network service returned Active with no errors after each above attempt. Service was verified stopped and restarted without errors. After rebooting, my network was still unavailable. Attampted again to stop|start|restart services. Then, I did a hardware NIC disable/re-enable which resulted in NM reporting networking enabled, but wireless "undetermined" (no check or unchecked box, a weird white box). Using NM, unchecked, re-checked "networking" and the wireless box was "normal, unchecked" Checked the box an wireless is working. After the wireless working was working again, I re-ran "systemctl status network.service" with the following results NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2013-05-11 14:35:15 PDT; 56s ago Main PID: 26829 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └─26829 /usr/sbin/NetworkManager --no-daemon May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr0): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> ModemManager available in the bus The above may not be helpful, I suspect that the errors only refer to a number of virtual device bridges I have configured on this machine, but of course NM does not support managing those. Reproducible: Always Steps to Reproduce: 1. zypper up 5/10/2013 2. Put machine to sleep 3. resume machine Actual Results: Networking unavailable. Expected Results: Network should re-connect to available networks automatically Assigning Major, but impact likely depends on whether the User is able to regain networking either by restarting the network service or re-booting. If there are critical programs which would be adversely affected by a re-boot, then the problem is very serious, maybe even critical. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 929856] New: Shell crashes on /bin/login
by bugzilla_noreply＠novell.com 19 Feb '18

19 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=929856 Bug ID: 929856 Summary: Shell crashes on /bin/login Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner-meier(a)gmx.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 633405 --> http://bugzilla.opensuse.org/attachment.cgi?id=633405&action=edit strace log of /bin/login as root Environment: I'm using OpenSUSE Tumbleweed 20150503. (I'm sorry if this is the wrong association, I couldn’t select that exact version.) Description: The command "/bin/login" issued as root causes the shell to crash. As far as I could determine it doesn't matter which shell. I use bash. I know it would be pointless to issue /bin/login as a already logged in user. But I found this bug as I want to test an old serial terminal with agetty. I can see the login prompt on the terminal and I can enter my name. But after that, the shell crashes on the host system. Reproducible: always - open a shell and log in as root - call the command "login". - see the shell crashing - (My locale settings are de_DE.UTF-8 if that matters) Expected Result: - something better than a crashing shell :-) I've attached a strace log. I hope this helps to find the bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 955652] New: Leap 42.1 hibernation problem - display stays dark/black (Acer Aspire 5253)
by bugzilla_noreply＠novell.com 19 Feb '18

19 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=955652 Bug ID: 955652 Summary: Leap 42.1 hibernation problem - display stays dark/black (Acer Aspire 5253) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi just came around a problem with hibernation on an Acer Aspire 5253. After resume the display stays dark, but the system is reachable via ssh. To bring the screen up again, the following simple command can be used. #> xrandr -d :0 --auto The next problem that occurred was that the mouse cursor vanished after resume. This sounded similar to the following Ubuntu bug. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/492… And the following comment was a valid workaround. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/55224… At the end I've created the following systemd-sleep script to have it working at the moment. #> cat /usr/lib/systemd/system-sleep/display.sh #!/bin/sh case $1/$2 in post/*) xrandr -d :0 --auto chvt 1 chvt 7 ;; esac -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 959849] New: multiple instances of Dolphin opening on boot
by bugzilla_noreply＠novell.com 18 Feb '18

18 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=959849 Bug ID: 959849 Summary: multiple instances of Dolphin opening on boot 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: farcusnz(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/47.0.2526.80 Safari/537.36 Build Identifier: Leap 42.1 with plasma 5.5.1 When booting, plasma randomly loads instances of dolphin. Session is set to restore on boot but Dolphin in prev sessions have always been closed (so this indicates that the process wasn't really terminated on close) Setting to start with a new session stops the problem. Today on boot - plasma kindly started six instances of dolphin for me. Reproducible: Sometimes -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 934751] New: Bad checksum on repository
by bugzilla_noreply＠novell.com 17 Feb '18

17 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=934751 Bug ID: 934751 Summary: Bad checksum on repository Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jamesrome(a)alum.mit.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Retrieving repository 'openSUSE:13.2:Update' metadata -----------------------------------------------------------------------------------------------------[|] Warning: Digest verification failed for file '03f8cec0b5ba52d39c90891a512c6d2ca7d7b125aa1bed572372463bcbe37c5f-appdata.xml.gz' [/var/cache/zypp/raw/openSUSE:13.2:UpdateqhyOCY/repodata/03f8cec0b5ba52d39c90891a512c6d2ca7d7b125aa1bed572372463bcbe37c5f-appdata.xml.gz] expected 4b7b13246a375b856bfaff1f019ca731f289408604329e47135520637217e549 but got e6c5988694e984d4674f01930765d016f384d5c5d33b2655ec3f397e23e47ab0 Accepting packages with wrong checksums can lead to a corrupted system and in extreme cases even to a system compromise. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 915677] New: locking the screen does not always work in lxde
by bugzilla_noreply＠novell.com 17 Feb '18

17 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=915677 Bug ID: 915677 Summary: locking the screen does not always work in lxde Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If lightdm is installed and in lxde I select Lock Screen in the logout window nothing happens. This is because the program lxsession-logout calls lxlock and lxlock contains: if test x"`which dm-tool 2>/dev/null`" != x""; then dm-tool switch-to-greeter So, if lightdm is installed, lxlock will execute "dm-tool switch-to-greeter" to lock the screen. Such command will fail with the error message: Not running inside a display manager, XDG_SEAT_PATH not defined But if I set lightdm as display manager then XDG_SEAT_PATH is defined and "dm-tool switch-to-greeter" will lock the screen. The fix is to change the if statement in lxlock like this: if test x"$XDG_SEAT_PATH" != x"" -a x"`which dm-tool 2>/dev/null`" != x""; then dm-tool will be executed only if lightdm is installed AND it is used as display manager. This fix is only for 13.2 and 13.1 (lxsession 0.4.9.3) newer version do not have this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 958888] New: missing manpages during installation - packaging fault?
by bugzilla_noreply＠novell.com 16 Feb '18

16 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=958888 Bug ID: 958888 Summary: missing manpages during installation - packaging fault? Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dieter.jurzitza(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I wanted to install both python-Cheetah and python-Spinx in order to build krb5. During zypper process, the following warnings were spit out. Please check what is going on here - IMHO man - page files are missing / corrupt. Thank you for looking into this, take care Dieter Jurzitza Test auf Dateikonflikte: ...............................................[fertig] (1/7) Installation von: python-docutils-0.11-3.2 .......................[fertig] Zusätzliche RPM-Ausgabe: update-alternatives: using /usr/bin/rst2html-2.7 to provide /usr/bin/rst2html (rst2html) in auto mode (2/7) Installation von: python-setuptools-18.0.1-2.2 ...................[fertig] (3/7) Installation von: python-Cheetah-2.4.4-10.1 ......................[fertig] (4/7) Installation von: python-MarkupSafe-0.23-7.2 .....................[fertig] (5/7) Installation von: python-Pygments-1.6-8.1 ........................[fertig] (6/7) Installation von: python-Jinja2-2.7.3-4.2 ........................[fertig] (7/7) Installation von: python-Sphinx-1.2b3-3.2 ........................[fertig] Zusätzliche RPM-Ausgabe: update-alternatives: using /usr/bin/sphinx-apidoc-2.7 to provide /usr/bin/sphinx-apidoc (sphinx-apidoc) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/sphinx-all.1.gz because associated file /usr/share/man/sphinx-all-2.7.1.gz (of link group sphinx-apidoc) doesn't exist update-alternatives: warning: skip creation of /usr/share/man/man1/sphinx-apidoc.1.gz because associated file /usr/share/man/sphinx-apidoc-2.7.1.gz (of link group sphinx-apidoc) doesn't exist update-alternatives: warning: skip creation of /usr/share/man/man1/sphinx-build.1.gz because associated file /usr/share/man/sphinx-build-2.7.1.gz (of link group sphinx-apidoc) doesn't exist update-alternatives: warning: skip creation of /usr/share/man/man1/sphinx-quickstart.1.gz because associated file /usr/share/man/sphinx-quickstart-2.7.1.gz (of link group sphinx-apidoc) doesn't exist -- You are receiving this mail because: You are on the CC list for the bug.

1 3