June 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 982708] New: home:Ledest:misc/apt: Bug
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982708 Bug ID: 982708 Summary: home:Ledest:misc/apt: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ledest(a)gmail.com Reporter: ms(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Installing apt and running apt-get causes an immediate segmentation fault Tested on openSUSE 13.2 and Leap42.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982129] New: [TW] mutt-1.6.1 unusable built with --enable-sidebar
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982129 Bug ID: 982129 Summary: [TW] mutt-1.6.1 unusable built with --enable-sidebar Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- New messages detection does not work in the current version of mutt on openSUSE Tumbleweed. As a long time mutt user I'm used to shuffle through the list of folders containing new/unread messages using the 'c' followed by 'space' key sequence. I narrowed it down to the configure option "--enable-sidebar", which enables some pseudo graphical functionality for - I guess - mutt newbies. Rebuilding the otherwise unchanged package with "--disable-sidebar" produces a normally working mutt again. I strongly recommend to disable this code until it gets fixed. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 982136] Installation is very slow on aarch64, openQA times out
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982136 http://bugzilla.suse.com/show_bug.cgi?id=982136#c5 Martin Vidner <mvidner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Severity|Normal |Major --- Comment #5 from Martin Vidner <mvidner(a)suse.com> --- Setting the same severity+priority as for the SLE variant, https://bugzilla.suse.com/show_bug.cgi?id=982137 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957226] NTP does not start after upgrade to Leap 42.1
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.novell.com/show_bug.cgi?id=957226 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:running:62772:low |maint:running:62772:low |maint:released:oes11-sp2:62 |maint:released:oes2015:6277 |773 |4 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 957226] NTP does not start after upgrade to Leap 42.1
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.novell.com/show_bug.cgi?id=957226 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|maint:running:62772:low |maint:running:62772:low | |maint:released:oes11-sp2:62 | |773 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 918396] New: sddm: segfault when starting
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=918396 Bug ID: 918396 Summary: sddm: segfault when starting Classification: openSUSE Product: openSUSE Factory Version: 201502* Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: X11 Applications Assignee: hrvoje.senjan(a)gmail.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 623693 --> http://bugzilla.opensuse.org/attachment.cgi?id=623693&action=edit backtrace It seems that sddm segfault when starting (on first attempt to start after boot): # systemctl status display-manager.service display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; disabled) Active: failed (Result: timeout) since Wed 2015-02-18 14:07:57 CET; 40min ago Process: 1857 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS) Feb 18 14:06:56 daredevil sddm-helper[2207]: [PAM] Preparing to converse... Feb 18 14:06:56 daredevil sddm-helper[2207]: [PAM] Conversation with 1 messages Feb 18 14:06:57 daredevil sddm-helper[2207]: [PAM] returning. Feb 18 14:06:57 daredevil sddm[2114]: Authenticated successfully Feb 18 14:06:57 daredevil sddm-helper[2207]: pam_unix(sddm:session): session opened for user plusky by (uid=0) Feb 18 14:06:57 daredevil pam_ssh[2207]: /tmp/ssh-ECt5WlA8kPKm/agent.5470: No such file or directory Feb 18 14:06:57 daredevil sddm[2114]: Auth: sddm-helper exited successfully Feb 18 14:06:57 daredevil sddm[2114]: Session started Feb 18 14:07:57 daredevil systemd[1]: display-manager.service start operation timed out. Terminating. Feb 18 14:07:57 daredevil systemd[1]: Failed to start X Display Manager. # zypper info sddm|grep Version Version: 0.11.0-1.2 bt (for full output see attached log): #0 QHashData::nextNode (node=node@entry=0xa64220) at tools/qhash.cpp:512 #1 0x00007f23fdbc8ed8 in operator++ (this=<synthetic pointer>) at ../../src/corelib/tools/qhash.h:439 #2 QDBusConnectionPrivate::socketRead (this=0xa60fd0, fd=7) at qdbusintegrator.cpp:1188 #3 0x00007f23fdc0f373 in QDBusConnectionPrivate::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at .moc/moc_qdbusconnection_p.cpp:130 #4 0x00007f23fce2f641 in QMetaObject::activate (sender=sender@entry=0xa62fd0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9a822750) at kernel/qobject.cpp:3716 #5 0x00007f23fce2fc67 in QMetaObject::activate (sender=sender@entry=0xa62fd0, m=m@entry=0x7f23fd23b7a0 <QSocketNotifier::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff9a822750) at kernel/qobject.cpp:3582 #6 0x00007f23fceac7ee in QSocketNotifier::activated (this=this@entry=0xa62fd0, _t1=7) at .moc/moc_qsocketnotifier.cpp:133 #7 0x00007f23fce3c4d9 in QSocketNotifier::event (this=0xa62fd0, e=0x7fff9a8228c0) at kernel/qsocketnotifier.cpp:296 #8 0x00007f23fce000bd in QCoreApplication::notify (this=<optimized out>, receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:994 #9 0x00007f23fcdffdc5 in QCoreApplication::notifyInternal (this=0x7fff9a822b60, receiver=0xa62fd0, event=event@entry=0x7fff9a8228c0) at kernel/qcoreapplication.cpp:932 #10 0x00007f23fce58035 in sendEvent (event=0x7fff9a8228c0, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:228 #11 socketNotifierSourceDispatch (source=0xa5f050) at kernel/qeventdispatcher_glib.cpp:101 #12 0x00007f23f9868a04 in g_main_dispatch (context=0xa5ec20) at gmain.c:3111 #13 g_main_context_dispatch (context=context@entry=0xa5ec20) at gmain.c:3710 #14 0x00007f23f9868c48 in g_main_context_iterate (context=context@entry=0xa5ec20, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3781 #15 0x00007f23f9868cec in g_main_context_iteration (context=0xa5ec20, may_block=1) at gmain.c:3842 #16 0x00007f23fce5711b in QEventDispatcherGlib::processEvents (this=0xa5dad0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #17 0x00007f23fcdfdd1b in QEventLoop::exec (this=this@entry=0x7fff9a822ad0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #18 0x00007f23fce053a6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1185 #19 0x000000000041958b in main (argc=1, argv=0x7fff9a822cb8) at /usr/src/debug/sddm-0.11.0/src/daemon/DaemonApp.cpp:138 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 982516] New: openssh complains about an unset $DISPLAY
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982516 Bug ID: 982516 Summary: openssh complains about an unset $DISPLAY Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pvh(a)oma.be QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build Identifier: After upgrading to the latest OpenSSH, if you have a configuration that enables X forwarding in general but your current session does not have $DISPLAY set, ssh prints an error message about it on every connection. Specifically, it reports: DISPLAY "(null)" invalid; disabling X11 forwarding This behavior did not exist before the upgrade. This is a divergence from historical behavior and screws up any number of things. Reproducible: Always Steps to Reproduce: 1.Have a host, call it THEHOST, and a key that will work for the host, call it $HOME/.ssh/id_rsa. 2.Run: env - ssh -F /dev/null -o "ForwardX11 yes" -i $HOME/.ssh/id_rsa THEHOST /bin/true Actual Results: ssh complains: DISPLAY "(null)" invalid; disabling X11 forwarding Expected Results: No complaint. Silence about $DISPLAY being unset, because this is routine. OpenSSH version: openssh-6.6p1-11.1.x86_64 This report is a carbon copy of https://bugzilla.redhat.com/show_bug.cgi?id=1303260 -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 982129] [TW] mutt-1.6.1 unusable when built with --enable-sidebar
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982129 http://bugzilla.suse.com/show_bug.cgi?id=982129#c13 Dr. Werner Fink <werner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(manfred.h(a)gmx.net | |) --- Comment #13 from Dr. Werner Fink <werner(a)suse.com> --- (In reply to Manfred Hollstein from comment #12) Thanks for debugging. The main problem seems that with the keywords.patch there are two new functions mutt_label_ref_dec() and mutt_label_ref_inc() in which there is not checked if the used hash pointer `Labels' is initialized. https://github.com/neomutt/neomutt/issues/40 Just submitted a fixed version to server:mail/mutt and build has finished with mutt-1.6.1-138.1.x86_64.rpm mutt-debuginfo-1.6.1-138.1.x86_64.rpm mutt-debugsource-1.6.1-138.1.x86_64.rpm Please test out, thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982661] YaST2 shows duplicated packages
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982661 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|YaST2 shows duplicated |YaST2 shows duplicated |packets |packages -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982329] New: lvmetad doesn't activate volumes
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982329 Bug ID: 982329 Summary: lvmetad doesn't activate volumes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This has some history. For some time, "use_lvmetad = 1" in /etc/lvm/lvm.conf used to work. With some update this got reset to "0" by default. While the system used to work, it became apparent that running "dracut" (former "mkinitrd") now takes appr. 1 minute per installed kernel. Also, running "lvs" almost takes forever... When I compared my Tumbleweed installation with my other Leap installations, I found out that on Leap "lvmetad" is running, resulting in snappy responses after "lvs" commands, and also pretty fast "dracut" runs. OK, let's activate "lvmetad" in Tumbleweed. First I activated/enabled and started "lvm2-lvmetad.socket", followed by stopping a potentially running (but there was't any) "lvm2-lvmetad.service". I then set "use_lvmetad = 1" in /etc/lvm/lvm.conf, started and enabled "lvm2-lvmetad.service" and rebuilt the initrd. The following reboot then got hung at "Waiting for /dev/mapper/rdisk00-swapdev1 to appear" and a similar message for the corresponding LV for /var. My setup is using /dev/md0 (MD-raid10) as a physical volume, providing space for such volumes as /var, /swapdev1 and /home. It is my understanding that at some point "/usr/lib/udev/rules.d/69-dm-lvm-metad.rules" should run "pvscan --cache" to provide the necessary udev events feeding into dm/udev to actually activate volumes, but, apparently this doesn't happen. Whe I got stuck in the single-boot/rescue phase after the boot, running "pvscan --cache" manually, followed by a "udevadm trigger" made the missing VG and LVs available; but, since /var is on an LV, the system is not actually usable at that point in time. I then downgraded the "lvm2" package (from "2.02.141-64.2" in current TW) to "2.02.120-67.1" to Leap's most current version, repeated all the lvmetad related configs from above, rebuilt the initrd, rebooted and - voila - my system boots again - and running "dracut" is not at all that boring again (appr. 10 secs. per kernel now). It looks to me that the current LVM2 package is not lvmetad capable. -- You are receiving this mail because: You are on the CC list for the bug.

1 12