Bug 356055 - login error
Summary: login error
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-29 08:04 UTC by venember
Modified: 2018-02-23 20:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
developer bug tracking list (6.23 KB, text/plain)
2015-12-08 11:24 UTC, venember
Details

Note You need to log in before you can comment on or make changes to this bug.
Description venember 2015-11-29 08:04:51 UTC
- manage remote host
- Upgrade from 13.2 to Tumbleweed in opensuse
- polkit problems, uninstall polkit, the system wipes the kde also
- use icewm via vnc
 some other errors
- update Tumbleweed, reinstall kde
- login with vnc, login on simple screen cannot start kde plasma

Reproducible: Always

Steps to Reproduce:
1. login via passworded vnc
2. login into plasma
3. error


Expected Results:  
smooth login
use kde without polkit and other security suffs
Comment 1 Christoph Feck 2015-12-01 13:43:26 UTC
> uninstall polkit

I doubt that this is supported by your distribution. Please ask there.
Comment 2 venember 2015-12-02 08:28:27 UTC
It was about YOUR error ticketing system screen when I was trying to log in...
And it was not too easy to send the error.
Comment 3 venember 2015-12-08 11:24:02 UTC
Created attachment 95934 [details]
developer bug tracking list

Developer message:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9886e77900 (LWP 18691))]

Thread 7 (Thread 0x7f986e98f700 (LWP 18693)):
#0 0x00007f98803e920d in poll () at /lib64/libc.so.6
#1 0x00007f98852eb432 in () at /usr/lib64/libxcb.so.1
#2 0x00007f98852ed007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3 0x00007f987114ae29 in () at /usr/lib64/libQt5XcbQpa.so.5
#4 0x00007f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#5 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#6 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f98644df700 (LWP 18699)):
#0 0x00007f98803e920d in poll () at /lib64/libc.so.6
#1 0x00007f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007f987ca8c36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3 0x00007f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007f9880cb063a in QEventLoop::exec(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5 0x00007f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x00007f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f98587af700 (LWP 18710)):
#0 0x00007f98803e920d in poll () at /lib64/libc.so.6
#1 0x00007f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007f987ca8c36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3 0x00007f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007f9880cb063a in QEventLoop::exec(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5 0x00007f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x00007f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f9856dcf700 (LWP 18713)):
#0 0x00007f98803e920d in poll () at /lib64/libc.so.6
#1 0x00007f987ca8c264 in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007f987ca8c36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3 0x00007f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007f9880cb063a in QEventLoop::exec(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5 0x00007f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007f9883db59a5 in () at /usr/lib64/libQt5Qml.so.5
#7 0x00007f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f9855427700 (LWP 18726)):
#0 0x00007f987fbed07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1 0x00007f9886567a84 in () at /usr/lib64/libQt5Script.so.5
#2 0x00007f9886567ac9 in () at /usr/lib64/libQt5Script.so.5
#3 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#4 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f97c67cf700 (LWP 18727)):
#0 0x00007f987cacf4d4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1 0x00007f987ca8c21e in () at /usr/lib64/libglib-2.0.so.0
#2 0x00007f987ca8c36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3 0x00007f9880d0652b in QEventDispatcherGlib: rocessEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4 0x00007f9880cb063a in QEventLoop::exec(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5 0x00007f9880adcb1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6 0x00007f9884942e42 in () at /usr/lib64/libQt5Quick.so.5
#7 0x00007f9880ae194f in () at /usr/lib64/libQt5Core.so.5
#8 0x00007f987fbe74a4 in start_thread () at /lib64/libpthread.so.0
#9 0x00007f98803f1b9d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f9886e77900 (LWP 18691)):
[KCrash Handler]
#6 0x00007f988033cd38 in raise () at /lib64/libc.so.6
#7 0x00007f988033e18a in abort () at /lib64/libc.so.6
#8 0x00007f9880acf82e in () at /usr/lib64/libQt5Core.so.5
#9 0x00007f98849ac5c4 in () at /usr/lib64/libQt5Quick.so.5
#10 0x00007f98849ad545 in () at /usr/lib64/libQt5Quick.so.5
#11 0x00007f98849ae44e in () at /usr/lib64/libQt5Quick.so.5
#12 0x00007f9881201c3b in QWindow::event(QEvent*) () at /usr/lib64/libQt5Gui.so.5
#13 0x00007f98849e5621 in QQuickWindow::event(QEvent*) () at /usr/lib64/libQt5Quick.so.5
#14 0x000000000043ff66 in DesktopView::event(QEvent*) ()
#15 0x00007f98820398cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#16 0x00007f988203e9d6 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#17 0x00007f9880cb2cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#18 0x00007f98811fa6e4 in QGuiApplicationPrivate: rocessExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib64/libQt5Gui.so.5
#19 0x00007f98811fb37d in QGuiApplicationPrivate: rocessWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib64/libQt5Gui.so.5
#20 0x00007f98811e09f8 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Gui.so.5
#21 0x00007f987117aed0 in () at /usr/lib64/libQt5XcbQpa.so.5
#22 0x00007f987ca8c097 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#23 0x00007f987ca8c2c8 in () at /usr/lib64/libglib-2.0.so.0
#24 0x00007f987ca8c36c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#25 0x00007f9880d0650f in QEventDispatcherGlib: rocessEvents(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#26 0x00007f9880cb063a in QEventLoop::exec(QFlags<QEventLoop: rocessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#27 0x00007f9880cb82fd in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#28 0x0000000000434150 in main ()
Comment 4 venember 2015-12-08 20:52:26 UTC
kactivity segfault in libQt5Sql.so.5.5.1 ....
Comment 5 Christoph Feck 2015-12-08 20:57:10 UTC
Please report issues separately.

Comment #3 is bug 346519
Comment #4 is bug 356291 (which is probably already fixed, see bug 355478)
Comment 6 venember 2015-12-09 00:21:24 UTC
It is the same issue
After upgrading from opensuse 13.2 to Tumbleweed I can not login into KDE graphical environmet, I got the upper error.
I have an own compiled nvidia driver.
If I delete the polkit and connected software (cca 200 pieces), I can login into a graphical environment via simple splash screen.
The Xorg. log is error-free.
I got error message in log records mentioned above: kactivity segfault
The other log records next to
EXIT: vnc status 0
org.ally.atspi.Registry XIO fatal IO error (Resource temporarily unavailable) on X server
....
The X11 connection have broke (error 2). Did the X server die?
org.freedesktop.Tracker: --- 'Terminated'

I sent a forum message/thread into into opensuse forum, nothing happened.

It lasts over 10 days.
Comment 7 Christoph Feck 2015-12-09 02:15:31 UTC
> It is the same issue

Which issue? You are posting random unrelated comments and backtraces.

> I have an own compiled nvidia driver.

We cannot help you, sorry.
Comment 8 venember 2015-12-09 09:15:05 UTC
What do not you understand?
1. KDE is your desktop manager system.
2. It is a report about the remote crash (accross vnc) on YOUR crash report screen (i copied this onto my machine).
3. Plus I investigated the relevant records from the system logging: after crash  I logged in via ssh.
4. The error persists.
5. I have deleted the KDE because I need a working desktop.

The complete result: BEFORE opensuse 13.2 to Tumbleweed upgrade my KDE graphical environment worked. AFTER upgrade I can choose between a full upgrade WITHOUT  desktop (crash) OR a half-wiped system (polkit with other stuff, I do not know what causes the error) with IceWM desktop.

I sent the problem onto the opensuse TUMBLEWEED forum, there is no answer.
I can not decide that is is either your problem or the opensuse distribution. It seems to be none of you, only mine...
Comment 9 Ben Creasy 2018-02-23 20:42:41 UTC
This is downstream issue with openSUSE and polkit (https://serverfault.com/questions/195952/what-does-upstream-and-downstream-mean).

If you get the chance, a link to your open issue with Tumbleweed might be helpful in figuring out if KDE can integrate better there, but closing for now.