Bug 428926 - kde crashed on kali nethunter through tightvnc
Summary: kde crashed on kali nethunter through tightvnc
Status: RESOLVED NOT A BUG
Alias: None
Product: frameworks-kidletime
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-10 11:07 UTC by roger.qea
Modified: 2021-04-06 01:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screen shot of vncviewer, the kde start but not working correctly (310.49 KB, image/jpeg)
2020-11-10 11:07 UTC, roger.qea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description roger.qea 2020-11-10 11:07:33 UTC
Created attachment 133200 [details]
screen shot of vncviewer, the kde start but not working correctly

SUMMARY

I am using nethunter from kali on Xiaomi 8. xfce4 can work smoothly with tightvnc and x11 server, but kde with sddm crashes.

STEPS TO REPRODUCE
1. on nethunter arm64, apt install kde-plasma-desktop, select sddm during installaion
2. edit .vnc/xstartup and add startplasma-x11
3. start vncserver and connect the server with vncviewer on android

OBSERVED RESULT

kde is partly started as I can use the browser to report this issue, but it is not working correctly as no widget or windows appesr.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: kali nethunter arm64 latest version
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION




Application: The KDE Crash Handler (drkonqi), signal: Segmentation fault
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x760966d010 (LWP 5257))]

Thread 2 (Thread 0x76033a40e0 (LWP 5264)):
#0  __GI___libc_read (nbytes=16, buf=0x76033a3598, fd=<optimized out>) at ../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=<optimized out>, buf=0x76033a3598, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24
#2  0x000000760bdb79d0 in ?? () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#3  0x000000760bd69750 in g_main_context_check () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#4  0x000000760bd69bc0 in ?? () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#5  0x000000760bd69d44 in g_main_context_iteration () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
#6  0x000000760d4b5ba4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#7  0x000000760d45719c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#8  0x000000760d278620 in QThread::exec() () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#9  0x000000760dd7f204 in ?? () from /lib/aarch64-linux-gnu/libQt5DBus.so.5
#10 0x000000760d279a64 in ?? () from /lib/aarch64-linux-gnu/libQt5Core.so.5
#11 0x000000760c7c9628 in start_thread (arg=0x76033a39e0) at pthread_create.c:477
#12 0x000000760cf151dc in thread_start () at ../sysdeps/unix/sysv/linux/aarch64/clone.S:78

Thread 1 (Thread 0x760966d010 (LWP 5257)):
[KCrash Handler]
#4  0x0000007601bcbb90 in ?? () from /usr/lib/aarch64-linux-gnu/qt5/plugins/kf5/org.kde.kidletime.platforms/KF5IdleTimeXcbPlugin0.so
#5  0x000000760ce799ec in __run_exit_handlers (status=0, listp=0x760cfae688 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108
#6  0x000000760ce79b7c in __GI_exit (status=<optimized out>) at exit.c:139
#7  0x000000760ce6419c in __libc_start_main (main=0x5b42f99970, argc=22, argv=0x7fc2ebad78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=<optimized out>) at ../csu/libc-start.c:342
#8  0x0000005b42f9b730 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
[Inferior 1 (process 5257) detached]
Comment 1 Harald Sitter 2020-11-10 11:30:57 UTC
Alas, that backtrace is of insufficient quality.
https://community.kde.org/Get_Involved/Issue_Reporting#Crash_reports_must_include_backtraces
Comment 2 Nate Graham 2021-04-06 01:00:55 UTC
It appears that you are using Kali Linux, which is not appropriate for general use, and you will find a million and a half other little weirdnesses like this, because running everything as root is explicitly unsupported and never recommended. I would encourage you to re-install your system with a more appropriate general purpose Linux distro, such as one of the ones you can se at https://kde.org/distributions.