August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 918051] New: After latest Glib update, KDE applications crash often
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918051 Bug ID: 918051 Summary: After latest Glib update, KDE applications crash often Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: ivan.topolsky(a)isb-sib.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build Identifier: Recently, lots of KDE applications have started to crash randomly. (Most often hadden with Plasma Workspace, and a few daemons like Bluetooth, etc.) After reading the dumps in KDE's crash reporter, it seems to me that most of the time, the crashed thread is either running in GLib, or some other function in the call stack further down called from within GLib. It seems to happens most often: - after resume from "Suspend-to-RAM" - after closing a KDE application (it crashes instead of closing) - after logging out (nearly always a KDE application or a few will crash. Workspace and daemon are the most popular, but other KDE apps might crash too). I've already filled one crash report with KDE's reporter. see KDE bug 344024 : https://bugs.kde.org/show_bug.cgi?id=344024 I can keep filing such crash dumps if it helps. Reproducible: Sometimes Steps to Reproduce: 1. Just wait. (very rare) Or: resume from "suspend-to-ram" (sometimes) Or: close an application (rarer, that only crashes the application itself) Or: log out (very oftern) Actual Results: One or several applications will crash, KDE crash handler appears, showing a dump, and offering to upload a crash report at bugs.kde.org When looking at the dump, the offending thread is a few calls down from glib. Expected Results: (system should be working crash free) Running KDE & co from stock openSUSE repository. (The 3rd party repo I use is Packman, but that's mostly used for media and should not crash basic KDE application). Everything started following latest glib update from "opensuse 13.2 updates" repo. Luckily I haven't lost any data to it. As mentionned, I can keep filing the crash dumps at bugs.kde.org if it helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 905844] New: lxde control center: no text visible under the program icons
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=905844 Bug ID: 905844 Summary: lxde control center: no text visible under the program icons 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: --- On a fresh 13.2 installation, usign LXDE, the window of LXDE control center only shows the program icons but there is no text under the icons. The only icon with text is the Install Software icon but the text under it is not "Install Software" but "Installed Size:". Clicking on the different icons starts the corresponding programs except for Install Software: the program that is supposed to run (package-manager) included in 13.1 in the package libzypp, does not exist in 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 927219] New: seccheck does not work without /var/log/messages (default Systemd Journal configuration)
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=927219 Bug ID: 927219 Summary: seccheck does not work without /var/log/messages (default Systemd Journal configuration) Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: bjoernv(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If openSUSE 13.2 is installed with default packages (logging with Systemd Journal, but without Syslog), the "seccheck" package does not work, because /var/log/messages is missing. cat /etc/cron.d/seccheck RUN_FROM_CRON=yes # # SuSE Security Checks # 0 0 * * * root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh daily & 0 1 * * 1 root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh weekly & 0 4 1 * * root test -x /usr/lib/secchk/security-control.sh && /usr/lib/secchk/security-control.sh monthly & # LANG=C /usr/lib/secchk/security-control.sh daily grep: /var/log/messages: No such file or directory grep: /var/log/messages: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 927637] New: VUL-0: CVE-2015-3138: tcpdump: denial of service in print-wb.c
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=927637 Bug ID: 927637 Summary: VUL-0: CVE-2015-3138: tcpdump: denial of service in print-wb.c Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other URL: https://smash.suse.de/issue/115973/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: vcizek(a)suse.com Reporter: astieger(a)suse.com QA Contact: qa-bugs(a)suse.de CC: puzel(a)suse.com, smash_bz(a)suse.de Found By: Security Response Team Blocker: --- Via RH: Recently an independent researcher had discovered a vulnerability in tcpdump, which would be a segmentation fault triggered through feeding into tcpdump a crafted packet, either from a live network interface or from a .pcap file. It has been assigned CVE-2015-3138 and you can find the steps to reproduce it here: https://github.com/the-tcpdump-group/tcpdump/issues/446 Subsequent analysis made it clear that the vulnerability was introduced into one of tcpdump functions by an accident not long before the 4.7.0 release. It remained in tcpdump releases 4.7.2 and 4.7.3 (4.7.1 was never released). The next release, 4.7.4, will have it fixed, but it is likely to be delayed. Since the vulnerability has been public for a few weeks, meanwhile you might want to fix it in an update to the tcpdump package. The fix is in the following commit: https://github.com/the-tcpdump-group/tcpdump/commit/3ed82f4ed0095768529afc2… openSUSE 13.1: 4.4.0 not affected openSUSE 13.2: 4.6.2 not affected network:utilities: 4.7.3 affected openSUSE:Factory: 4.7.3 affected References: https://bugzilla.redhat.com/show_bug.cgi?id=1212342 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-3138 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3138 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[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 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 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