[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #24 from Samuel Bernardo  ---
(In reply to Samuel Bernardo from comment #23)
> I'm detecting another problem with x2go session with kde5. GPU memory
> associated with X is always growing where x2go client is running...
> I can't reproduce the problem when using other applications.
> Can anyone reproduce the same memory leak on GPU?
> 
> I'm using x2goclient 4.0.3.2 and x2goserver 4.0.1.19.
> 
> I mentioned this because I don't know if it's related with KCMInit crash.

I tested x2go with mate and the gpu memory problem persists with X. Maybe this
is another problem related to the kde or the nvidia driver in my local PC. I
don't know how to analyse the problem, since I haven't a gpu from another
manufacturer and can't get the context of X process inside GPU memory...

I'm using kde 5.7.3 and nvidia driver 367.35.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #23 from Samuel Bernardo  ---
I'm detecting another problem with x2go session with kde5. GPU memory
associated with X is always growing where x2go client is running...
I can't reproduce the problem when using other applications.
Can anyone reproduce the same memory leak on GPU?

I'm using x2goclient 4.0.3.2 and x2goserver 4.0.1.19.

I mentioned this because I don't know if it's related with KCMInit crash.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #22 from Samuel Bernardo  ---
(In reply to Fabian Köster from comment #21)
> In fact Plasma 5 is working quite well using x2go, so I am wondering if this
> limitation is really true.

I have a segfault with KCMInit at login and plasmashell at logout.
I'm using KDE 5.7.3.

> This bug is about KCMInit crashing, which does not necessarily have to to
> with x2go lacking support for GLX 1.3. Maybe someone with deeper knowledge
> of the Plasma X11 stack can tell from which component this bug really comes
> from and whether it should be fixed or if we should wait for proper Wayland
> Remote Desktop support in Plasma.

I confirm that I can use remote x2go session besides the mentioned bugs of
login and logout. All applications I use seems to work without any problem, but
maybe that happens because they don't use GLX 1.3.
I'll be waiting for an answer of someone expert in KDE and x2go. I already sent
an email to x2go-users mailing list.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 353825] Login by x2go in Plasma 5 crashes KCMInit

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=353825

--- Comment #20 from Samuel Bernardo  ---
Reading the x2go desktop compatibility page, they don't support GLX 1.3 used in
KDE5. So plasmashell can't work as expected, as mentioned in the following
page:
http://wiki.x2go.org/doku.php/doc:de-compat

So in plasma 5 this is not a bug, but a limitation from x2go.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 366687] Bug 353825 - Login by x2go in Plasma 5 crashes KCMInit (duplicate)

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366687

Samuel Bernardo  changed:

   What|Removed |Added

 CC||samuelbernardo.mail@gmail.c
   ||om

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 366687] New: Bug 353825 - Login by x2go in Plasma 5 crashes KCMInit (duplicate)

[Samuel Bernardo via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366687

Bug ID: 366687
   Summary: Bug 353825 - Login by x2go in Plasma 5 crashes KCMInit
(duplicate)
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: samuelbernardo.m...@gmail.com

Application: kdeinit5 ()
 (Compiled from sources)
Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.4.16-gentoo-zerg x86_64
Distribution: "NAME=Gentoo"

-- Information about the crash:
- What I was doing when the application crashed:
Starting remote session of x2go client and x2goserver at remote machine running
plasma 5.7 crashed as shown in backtrace.
I already installed latest version of x2go and problem persists.
I'm using gentoo and I confirm that using MATE it works ok.

- Crash Reporting Assistant not working as expected
When I select a manual bug report and confirm that it was related, it didn't
add to the list de entry.
So since this seems to me a duplicate, I appointed in title the related bug
report.

The crash can be reproduced every time.

-- Backtrace:
Application: KCMInit (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa5cedd3800 (LWP 16156))]

Thread 3 (Thread 0x7fa5ba7c2700 (LWP 16158)):
#0  0x7fa5cd44cd4d in poll () from /lib64/libc.so.6
#1  0x7fa5ce2eeac2 in _xcb_conn_wait () from /usr/lib64/libxcb.so.1
#2  0x7fa5ce2f072f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7fa5bbecff69 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7fa5cd7b6e8c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fa5cb07a444 in start_thread () from /lib64/libpthread.so.0
#6  0x7fa5cd455dad in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7fa5b8a06700 (LWP 16160)):
#0  0x7fa5ca341ad4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7fa5ca2fd450 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7fa5ca2fde48 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fa5ca2fe02c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7fa5cd9a7cac in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7fa5cd959a1a in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7fa5cd7b26d4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7fa5ced29235 in QDBusConnectionManager::run() () from
/usr/lib64/libQt5DBus.so.5
#8  0x7fa5cd7b6e8c in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#9  0x7fa5cb07a444 in start_thread () from /lib64/libpthread.so.0
#10 0x7fa5cd455dad in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fa5cedd3800 (LWP 16156)):
[KCrash Handler]
#6  0x7fa5bbc8a73c in XIFreeDeviceInfo () from /usr/lib64/libXi.so.6
#7  0x7fa5b30d6cef in MouseSettings::apply(bool) [clone .part.12] () from
/usr/lib64/qt5/plugins/kcm_input.so
#8  0x7fa5b30dcde4 in kcminit_mouse () from
/usr/lib64/qt5/plugins/kcm_input.so
#9  0x7fa5bbf87a08 in KCMInit::runModule(QString const&,
QExplicitlySharedDataPointer) () from
/usr/lib64/libkdeinit5_kcminit_startup.so
#10 0x7fa5bbf881ef in KCMInit::runModules(int) () from
/usr/lib64/libkdeinit5_kcminit_startup.so
#11 0x7fa5bbf88998 in KCMInit::KCMInit(QCommandLineParser const&) () from
/usr/lib64/libkdeinit5_kcminit_startup.so
#12 0x7fa5bbf89931 in kdemain () from
/usr/lib64/libkdeinit5_kcminit_startup.so
#13 0x0040828f in launch(int, char const*, char const*, char const*,
int, char const*, bool, char const*, bool, char const*) ()
#14 0x00404d20 in main ()

Possible duplicates by query: bug 366015, bug 358873, bug 356701.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.