By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2345 - [stdout/stderr] TQObject::activate_signal
Summary: [stdout/stderr] TQObject::activate_signal
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: qt3 (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 major
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-02-05 00:25 CST by Darrell
Modified: 2018-05-27 10:48 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
knotify crash that might be related (32.72 KB, text/plain)
2015-02-05 11:46 CST, Darrell 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2015-02-05 00:25:07 CST 
I see the following in xsession-errors:

TQObject::activate_signal: Invoking cross-thread method from object 0x9847740 (member 2 receiver 0x97d9e8

TQObject::activate_signal: Emitting cross-thread signal from object 0x978e258 (member 15 receiver 0x978e2

TQObject::moveToThread: Cannot move objects with a parent
X Error: BadAccess (attempt to access private resource denied) 10
  Major opcode:  2
  Minor opcode:  0
  Resource id:  0x3000029

The messages can be triggered by starting the screen saver:

dcop kdesktop KScreensaverIface save

When stopping the screen saver I see the following:

[kdesktop_lock] Warning: unable to create control socket '/tmp/tdesocket-global/kdesktoplockcontrol-0'.  Interactive logon modules may not function properly.
[tdecore] Deleting stale lockfile /dev/shm/tde-htpc/kdesktop_lock_lockfile

Refer to bug 2123 about the hard-coded location for the socket file.
Comment 1 Darrell 2015-02-05 11:46:12 CST 
Created attachment 2447 [details]
knotify crash that might be related

I cannot trigger this crash repeatedly, but I have triggered the crash often with the following approximate steps.

For testing, change the user's screen saver timeout to something short, like 30 seconds (edit kdesktoprc or use kwriteconfig to obtain a timeout less than 1 minute).

At another console or through ssh, log in as root.

Wait for the screen saver to activate (ps aux | grep kss).

'su -' to the user's account

Stop the screen saver (DISPLAY=:0; dcop kdesktop KScreensaverIface quit).

Exit from the 'su -' session.

There might now be two dcopserver processes running and the knotify crash might occur.

Trinity gets confused once there are two dcopserver processes running. For example, as root attempting to force the user to logout often fails (dcop --user ${LOGGED_IN_USER} ksmserver default logout 0 0 -1).

I have not been able to determine the exact sequence to trigger the crash but the crash always occurs related to both the screen saver and when I use 'su -'.

The crash occurs frequently on my htpc. Frequently I log in remotely with ssh and use 'su -' during such a session to schedule recordings as normal user.

This bug report probably is related to bug 2316 or the same.
Comment 2 Darrell 2015-02-05 11:52:48 CST 
Bumping to Major beccause after the kcrash occurs the system becomes challenging to use.
Comment 3 Darrell 2015-02-05 14:35:06 CST 
Please refer to bug 2349. I believe the root cause is related.