November 2015 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 956068] New: Gnome does not start
by bugzilla_noreply＠novell.com 16 Feb '18

16 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=956068 Bug ID: 956068 Summary: Gnome does not start Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: wodenhof(a)daad-alumni.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed primarily the KDE version. When it was up and running, I installed Gnome via YAST2 / software install or delete / patterns / gnome basic system and gnome desktop environment. No errors. When I (the user created during install) chose Gnome at the login screen entering user and password the screen turns black and I get an "x" as mouse pointer. <alt><F2> and login as root then "init 3" and "init 5" brings me back to the login screen. If a different user tries to login with gnome, same happens as described above, but some 10 or 15 seconds later one will be back to the login screen automatically. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 921875] New: .la files in lib64
by bugzilla_noreply＠novell.com 16 Feb '18

16 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=921875 Bug ID: 921875 Summary: .la files in lib64 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: edera(a)gmx.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Although the recommandation https://en.opensuse.org/Shared_Library_Packaging_Policy is clearly """ Avoid packaging libtool config files (.la files). If you do not package a static library, and if you are also placing the shared library in a standard search directory (i.e. %_lib, /usr/%_lib), they will not be needed. """ There are .la files in /usr/lib64 This triggered a long to find bug, when trying to build octave from source: https://savannah.gnu.org/bugs/?44467 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 913042] New:=?UTF-8?Q?=20Archiv=20unoil=2Ejar=20enth=C3=A4lt=20nur=20MANIFEST=2EMF?=
by bugzilla_noreply＠novell.com 13 Feb '18

13 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=913042 Bug ID: 913042 Summary: Archiv unoil.jar enthält nur MANIFEST.MF Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LibreOffice Assignee: bnc-team-ooo(a)forge.provo.novell.com Reporter: k.merkel(a)dzbw.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Das Javaarchiv program/classes/unoil.jar enthält nur den Ordner META-INF mit der Datei MANIFEST.MF. Die Datei müsste mehrere Packages mit Javaklassen enthalten, die für den Aufruf von Libreoffice aus Java nötig sind (z. B. XWindow.class). Aktuell installiert: libreoffice 4.3.5.2-81-x86_64 von openSUSE-13.2-Update -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 640407] New: SDL: erroneously uses xrandr-style mode switching
by bugzilla_noreply＠novell.com 09 Feb '18

09 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=640407 https://bugzilla.novell.com/show_bug.cgi?id=640407#c0 Summary: SDL: erroneously uses xrandr-style mode switching Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Beta-Customer Blocker: --- Starting with 11.3, I am seeing a new issue with my "oversize" desktop (2944x2208 VirtualSize on a 1280x1024 resolution). Problem: SDL-1.2.14. When SDL switches to fullscreen 640x480 - for example, because the game is configured to run in such resolution - or back, it changes the desktop size too by means of xrandr or something along the lines of that. Actual results: Windows on my desktop are reordered, which is usually a result of the WM being forced to do so because the desktop size (virtualsize) changed. Resolution switching also takes significantly longer than it did before — this is another sign that it switches desktop size (too), not just resolution. First the screen goes black-with-backlight and after roughly 500ms, the TFT screen finally gets the new 640x480 mode signal (I use VGA), which is evidenced by the backlight going briefly off. Expected results: Previous behavior. In other worsd, leave desktop size as-is (and subsequently keep my windows where they are) and _only_ change the resolution. The old switching style is also way faster in that there is no black-with-backlight delay. Additional information: Not all programs are affected. The entire group of Doom engines exhibits the behavior for example, though I found that UnrealTournament99 does not. Both Doom and UT use libSDL-1.2.so.0 (no static SDL as far as I can see). Overriding the system SDL 1.2.14 libraries and using LD_LIBRARY_PATH to point to SDL-1.2.13 libraries brings back the desired behavior. -- 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 917403] New: zypper lr sort by field != 'alias' is non-functional
by bugzilla_noreply＠novell.com 08 Feb '18

08 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=917403 Bug ID: 917403 Summary: zypper lr sort by field != 'alias' is non-functional Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: grantksupport(a)operamail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- zypper's "lr" provides sorting by field rpm -qa | grep -i zypp | sort libzypp-14.32.0-9.1.x86_64 libzypp-devel-14.32.0-9.1.x86_64 perl-zypp-0.6.4-12.1.x86_64 python-zypp-0.6.4-12.1.x86_64 zypper-1.11.17-9.1.x86_64 zypper-log-1.11.17-9.1.noarch zypp-plugin-python-0.4-2.1.3.x86_64 zypper lr --help repos (lr) [options] [repo] ... List all defined repositories. Command options: -e, --export <FILE.repo> Export all defined repositories as a single local .repo file. -a, --alias Show also repository alias. -n, --name Show also repository name. -u, --uri Show also base URI of repositories. -p, --priority Show also repository priority. -r, --refresh Show also the autorefresh flag. -d, --details Show more information like URI, priority, type. -s, --service Show also alias of parent service. -E, --show-enabled-only Show enabled repos only. -U, --sort-by-uri Sort the list by URI. -P, --sort-by-priority Sort the list by repository priority. -A, --sort-by-alias Sort the list by alias. -N, --sort-by-name Sort the list by name. sort by 'alias' appears to work zypper lr -A # | Alias | Name | Enabled | Refresh ----+--------------+----------------+---------+-------- 1 | Apache | Apache | Yes | Yes 2 | ApacheMod | ApacheMod | Yes | Yes 3 | Archiving | Archiving | Yes | Yes 4 | Backup | Backup | Yes | Yes 5 | BaseSystem | BaseSystem | No | Yes 6 | C_C++ | C_C++ | No | Yes 7 | Chromium | Chromium | Yes | Yes ... but sort by other field, e.g. 'priority', doesn't zypper lr -P # | Alias | Name | Enabled | Refresh | Priority ----+--------------+----------------+---------+---------+--------- 1 | Apache | Apache | Yes | Yes | 60 2 | ApacheMod | ApacheMod | Yes | Yes | 60 3 | Archiving | Archiving | Yes | Yes | 99 4 | Backup | Backup | Yes | Yes | 69 5 | BaseSystem | BaseSystem | No | Yes | 35 6 | C_C++ | C_C++ | No | Yes | 40 7 | Chromium | Chromium | Yes | Yes | 45 ... -- You are receiving this mail because: You are on the CC list for the bug.

1 1