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 1386

Summary:	KDED Write Daemon not working
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdebase	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	normal	CC:	bugwatch, darrella
Priority:	P5
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:

Description Darrell 2013-01-08 14:30:29 CST

Using GIT R14, the KDED Write Daemon is not working for me in Slackware 14.0 64-bit. The daemon is working correctly in Slackware 13.1 32-bit.

The rwall daemon is working correctly in Slackware 14.0. I can pipe a text message to rwalld and the message appears in a console but no TDE popup window appears. With the same test the popup window appears in 13.1.

The 14.0 64-bit system has KDE4 installed so I can test and watch for conflicts with TDE. The 13.1 does not have KDE4 installed. One possible cause then is a conflict with KDE4.

Another possible cause is the 64-bit environment.

kded_kwrited.la and kded_kwrited.so exists on the 14.0 system. Therefore a compilation problem is unlikely.

I use the same user Trinity profile between the 13.1 and 14.0 system.

There are no xsession-error log entries for the daemon and nothing obvious in ps ax. kddebug 7020 (kded) is enabled. ps ax shows kded [tdeinit] --new-startup. Other than the popup window there does not seem to be any way to test or debug.

I don't know where or how to debug. I don't know whether problem is distro-only or even PEBKAC.

This is a personal blocker because I rely on the popup windows for certain messages in my network.

Comment 1 Darrell 2013-01-15 21:33:12 CST

In tdebase/konsole/konsole/kwrite.cpp:

  TQString txt = i18n("KWrited - Listening on Device %1").arg(pty->ttyName());
  setCaption(txt);

  kdDebug() << txt << endl;

When should this text string appear in the xsession error log or stdout/stderr? kddebug 7020 (kded) is enabled on my system yet I don't see this message anywhere.

The TDE kwrite daemon is working on a Slackware 14.0 32-bit virtual machine. At this point I suspect something is not building correctly on the 64-bit machine.

Comment 2 Darrell 2013-11-25 17:46:14 CST

Somewhere along the way this problem got resolved.