October 2016 - openSUSE Bugs - openSUSE Mailing Lists

[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 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 899627] New: p7zip package is missing 7zr executable
by bugzilla_noreply＠novell.com 03 Jul '18

03 Jul '18

http://bugzilla.opensuse.org/show_bug.cgi?id=899627 Bug ID: 899627 Summary: p7zip package is missing 7zr executable Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: me(a)shadsterling.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- /usr/bin/7zr, the "stand-alone" program that only handles the 7-zip format is missing from the p7zip package. /usr/bin/7z and /usr/bin/7za are included, as are man pages are for 7z, 7za, and 7zr. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1004657] New: wrong udev-id displayed
by bugzilla_noreply＠novell.com 27 Jun '18

27 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=1004657 Bug ID: 1004657 Summary: wrong udev-id displayed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- YaST displays a wrong udev-id if a disk contains a lvm pv and then the lvm pv is deleted and a partition on the disk is created. I my case there is initially the udev id link: lvm-pv-uuid-iVJRSF-4fdA-hGcS-KTj9-JCh2-H2IO-J7O1Oq -> sdb That link vanishes in the system when the lvm pv is deleted. But YaST does not know that and shows a wrong link for the new partition sdb1: lvm-pv-uuid-iVJRSF-4fdA-hGcS-KTj9-JCh2-H2IO-J7O1Oq-part1 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 978593] New: EFI fails to load up the grub2 image erroring out on snapshot path
by bugzilla_noreply＠novell.com 26 Jun '18

26 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=978593 Bug ID: 978593 Summary: EFI fails to load up the grub2 image erroring out on snapshot path Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After current clean Tumbleweed install efi fails to load up the grub2 menu. It tries to load it somewhere from snapshot and such file is not present. This computer has direct access to efi files and if I by hand select grub.efi file on the drive it loads up properly. (screenshot of the error will be attached). Fstab of the system: UUID=42ef9dda-9378-4c69-bbb9-540d8b8128db swap swap defaults 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 / btrfs defaults 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /opt btrfs subvol=@/opt 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /srv btrfs subvol=@/srv 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /tmp btrfs subvol=@/tmp 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /usr/local btrfs subvol=@/usr/local 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/crash btrfs subvol=@/var/crash 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/libvirt/images btrfs subvol=@/var/lib/libvirt/images 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mailman btrfs subvol=@/var/lib/mailman 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mariadb btrfs subvol=@/var/lib/mariadb 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/mysql btrfs subvol=@/var/lib/mysql 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/named btrfs subvol=@/var/lib/named 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/lib/pgsql btrfs subvol=@/var/lib/pgsql 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/log btrfs subvol=@/var/log 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/opt btrfs subvol=@/var/opt 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/spool btrfs subvol=@/var/spool 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /var/tmp btrfs subvol=@/var/tmp 0 0 UUID=5a0b5b07-f0da-40f4-9993-1cf094d5c7b7 /.snapshots btrfs subvol=(a)/.snapshots 0 0 UUID=5312-C90E /boot/efi vfat umask=0002,utf8=true 0 0 UUID=005d3151-b79e-435c-bcad-9d0304f53a9a /home xfs defaults 1 2 elitebook:~ # efibootmgr BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0000,0001 Boot0000* Notebook Upgrade Bay Boot0001* Notebook Hard Drive Boot0002* Notebook Hard Drive Boot0003* USB Hard Drive 1 - Alcor Micro Mass Storage Device Boot0004* SD Card Boot0005* opensuse -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 999100] New: grub2 menu
by bugzilla_noreply＠novell.com 26 Jun '18

26 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=999100 Bug ID: 999100 Summary: grub2 menu Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: me(a)xto.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi all, i just installed the 42.2-beta on my new Acer Travelmate B116. The grub-bootmenu is painted painfully slow (and really ugly (graphical). In first installation with original HDD i needed nomodeset to install 42.2-beta correctly (it broke with unreadable letters iprn text mode) so i tried with nomodeset which worked. Today i installed it again on a new and sealed ssd and I didnt need nomodeset-swith in installation-boot-menu (from USB-stick). I can provide more information as long as you tell me what to do :-) Greetings, Christian -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 964353] New: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down
by bugzilla_noreply＠novell.com 22 Jun '18

22 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=964353 Bug ID: 964353 Summary: QT 5.5.based plasmashell and sddm-greeter can't cope with no monitor or monitor powered down Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: lorenzodes(a)fastwebnet.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Plasmashell crashes or displays malfunctions if a monitor is unplugged or powered off. The problem is reported here: https://forums.opensuse.org/showthread.php/512997-Plasma-5-KDE-Switching-mo… To reproduce: xrandr --output DP3 --off ; xrandr --output DP3 --auto (change DP3 to the pertinent display name) This is the crash report: (gdb) bt #0 0x00007f7d08147ded in nanosleep () at /lib64/libc.so.6 #1 0x00007f7d08147c84 in sleep () at /lib64/libc.so.6 #2 0x00007f7d0e89bbac in startProcessInternal(int, char const**, bool, bool) (argc=<optimized out>, argv=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true, directly=directly@entry=false) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:650 #3 0x00007f7d0e89c22a in KCrash::startProcess(int, char const**, bool) (argc=argc@entry=21, argv=argv@entry=0x7ffe4b4744b0, waitAndExit=waitAndExit@entry=true) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:616 #4 0x00007f7d0e89c675 in KCrash::defaultCrashHandler(int) (sig=<optimized out>) at /usr/src/debug/kcrash-5.18.0/src/kcrash.cpp:527 #5 0x00007f7d080c6200 in <signal handler called> () at /lib64/libc.so.6 #6 0x00007f7d08fb8290 in QScreen::handle() const (this=0x0) at kernel/qscreen.cpp:112 #7 0x00007f7cfa7f4be9 in QXcbIntegration::createPlatformWindow(QWindow*) const (this=<optimized out>, window=0x2ae79d0) at qxcbintegration.cpp:196 #8 0x00007f7d08f98e25 in QWindowPrivate::create(bool) (this=0x1175d80, recursive=recursive@entry=false) at kernel/qwindow.cpp:392 #9 0x00007f7d08f9901b in QWindow::create() (this=this@entry=0x2ae79d0) at kernel/qwindow.cpp:548 #10 0x00007f7d08f990a8 in QWindow::winId() const (this=0x2ae79d0) at kernel/qwindow.cpp:567 #11 0x00007f7d0e667175 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #12 0x00007f7d0e6699f9 in () at /usr/lib64/libKF5PlasmaQuick.so.5 #13 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x297d830, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3713 #14 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffe4b474f90, r=0x297d830, this=0x29a86f0) at ../../src/corelib/kernel/qobject_impl.h:124 #15 0x00007f7d08a7073f in QMetaObject::activate(QObject*, int, int, void**) (sender=0xdf8370, signalOffset=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3698 #16 0x00007f7d08a70cc6 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0xdf41e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3713 #17 0x00007f7d08a712e7 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0xdf41e0, m=m@entry=0x7f7d08e8f860 <QTimer::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3578 #18 0x00007f7d08af2a90 in QTimer::timeout(QTimer::QPrivateSignal) (this=this@entry=0xdf41e0) at .moc/moc_qtimer.cpp:197 #19 0x00007f7d08a7df22 in QTimer::timerEvent(QTimerEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qtimer.cpp:247 #20 0x00007f7d08a718bc in QObject::event(QEvent*) (this=0xdf41e0, e=<optimized out>) at kernel/qobject.cpp:1220 #21 0x00007f7d09db9e7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xc666a0, receiver=receiver@entry=0xdf41e0, e=e@entry= 0x7ffe4b4754f0) at kernel/qapplication.cpp:3716 #22 0x00007f7d09dbecc8 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, e=0x7ffe4b4754f0) at kernel/qapplication.cpp:3499 #23 0x00007f7d08a40e95 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe4b4758a0, receiver=0xdf41e0, event=event@entry=0x7ffe4b4754f0) at kernel/qcoreapplication.cpp:965 #24 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (event=0x7ffe4b4754f0, receiver=<optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:224 #25 0x00007f7d08a9777d in QTimerInfoList::activateTimers() (this=0xcadc50) at kernel/qtimerinfo_unix.cpp:637 #26 0x00007f7d08a97aa1 in timerSourceDispatch(GSource*, GSourceFunc, gpointer) (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:177 #27 0x00007f7d0484ec84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #28 0x00007f7d0484eed8 in () at /usr/lib64/libglib-2.0.so.0 #29 0x00007f7d0484ef7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #30 0x00007f7d08a97d8b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0xca3db0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #31 0x00007f7d08a3ed53 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffe4b475730, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #32 0x00007f7d08a468f6 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229 #33 0x00007f7d08f8a79c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527 #34 0x00007f7d09db6605 in QApplication::exec() () at kernel/qapplication.cpp:2976 #35 0x0000000000436ab6 in main(int, char**) (argc=2, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.4/shell/main.cpp:181 sddm-greeter exits if the monitor is not switched on when the gretter is shown. The problem is reported here: https://forums.opensuse.org/showthread.php/513153-ssdm-greeter-exits-or-han… System logs: 2016-01-28T23:11:19.980147+01:00 kenshiro sddm[1091]: Running display setup script "/etc/X11/xdm/Xsetup" 2016-01-28T23:11:19.993288+01:00 kenshiro sddm[1091]: Display server started. 2016-01-28T23:11:19.993497+01:00 kenshiro sddm[1091]: Socket server starting... 2016-01-28T23:11:19.993639+01:00 kenshiro sddm[1091]: Socket server started. 2016-01-28T23:11:19.993885+01:00 kenshiro sddm[1091]: Greeter starting... 2016-01-28T23:11:19.994039+01:00 kenshiro sddm[1091]: Adding cookie to "/run/sddm/{5ab51fe3-b0e9-41b7-b2ed-294821cc0322}" 2016-01-28T23:11:19.998523+01:00 kenshiro sddm-helper[1653]: [PAM] Starting... 2016-01-28T23:11:19.998753+01:00 kenshiro sddm-helper[1653]: [PAM] Authenticating... 2016-01-28T23:11:19.998916+01:00 kenshiro sddm-helper[1653]: [PAM] returning. 2016-01-28T23:11:19.999052+01:00 kenshiro sddm-helper: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0) 2016-01-28T23:11:20.014407+01:00 kenshiro sddm[1091]: Greeter session started successfully 2016-01-28T23:11:20.027505+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/enlightenment.desktop" 2016-01-28T23:11:20.027786+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/gnome.desktop" 2016-01-28T23:11:20.027936+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/icewm.desktop" 2016-01-28T23:11:20.028071+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/kde-plasma.desktop" 2016-01-28T23:11:20.028204+01:00 kenshiro sddm-greeter[1655]: Reading from "/usr/share/xsessions/plasma5.desktop" 2016-01-28T23:11:20.028340+01:00 kenshiro sddm-greeter[1655]: Connected to the daemon. 2016-01-28T23:11:20.028474+01:00 kenshiro sddm[1091]: Message received from greeter: Connect 2016-01-28T23:11:20.062294+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.250847+01:00 kenshiro sddm-greeter[1655]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. 2016-01-28T23:11:20.404977+01:00 kenshiro sddm-greeter[1655]: file:///usr/share/sddm/themes/breeze/components/InfoPane.qml:52:22: Unable to assign [undefined] to int 2016-01-28T23:11:20.405245+01:00 kenshiro sddm-greeter[1655]: Adding view for "HDMI2" QRect(0,0 1920x1080) 2016-01-28T23:11:20.408967+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: Capabilities 2016-01-28T23:11:20.409139+01:00 kenshiro sddm-greeter[1655]: Message received from daemon: HostName 2016-01-28T23:15:03.058840+01:00 kenshiro sddm-helper[1653]: [PAM] Ended. 2016-01-28T23:15:03.059337+01:00 kenshiro sddm[1091]: Auth: sddm-helper exited successfully 2016-01-28T23:15:03.059517+01:00 kenshiro sddm[1091]: Greeter stopped. Apparently both are related to this upstream bug: https://bugreports.qt.io/browse/QTBUG-42985 Leap 42.1 KDE is basically unusable in this state and, as far as I can tell, upstream provided a bugfix but decided not to implement it in QT 5.5. Would it be possible to upgrade QT in Leap to 5.6? -- You are receiving this mail because: You are on the CC list for the bug.

1 3