Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 140977
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 135818
Assigned To: Gentoo KDE team <kde@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Martin von Gagern <Martin.vGagern@gmx.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 140977 depends on: Show dependency tree
Bug 140977 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-07-18 15:28 0000
I'd like to write or wall messages to a user that has started KDE using startx
from a terminal login. Unfortunately, the messages don't get displayed on my
screen out of the box. They arrive at the terminal where I started the X
server, but as I prefer to do "startx & logout", this is not a good enough
solution.

kwrited aka. "KDE Write Daemon" is selected and running in the KDE Service
Manager part of the KDE Control Center.

The probably related KDE issue is stated in the URL. It states some KDE log
file, but I can't find any such on my system. Where do KDE log messages go on a
Gentoo ~x86 system?

The issue seems to be related to bug 18252, and probably to the transition from
utempter to libutempter.

"utmpdump < /var/run/utmp" only states the terminal where I started my X
session, nothing that seems related to kwrited.

Currently I have these versions installed:
kde-base/kde-meta-3.5.3  USE="-accessibility"
kde-base/konsole-3.5.3-r1  USE="arts -debug -kdeenablefinal
-kdehiddenvisibility -xinerama"
sys-libs/libutempter-1.1.4.1

------- Comment #1 From Martin von Gagern 2006-07-18 16:48:09 0000 -------
I think bug 135818 might be related as well.
And that made me look at my kdelibs version as well:
kde-base/kdelibs-3.5.3-r3
That is configured --without-utempter, so maybe I should not be surprised.

------- Comment #2 From Martin von Gagern 2006-07-19 01:14:06 0000 -------
OK, it really was an utempter issue. I just wrote a patch I submitted as
bug 135818 comment 4 and with that it works, even if I "startx & logout".

I also found the messages of where KWrited was listening on one of the output
streams from startx, i.e. directly on the console. Strange thing is, before I
applied my patch, the KWrited lines appered in the shutdown portion, not during
startup.

Anyway, finding those I found that KDE allocates a new pty for kded, which is
the reason why closing the one where I started X is al right.

Should this bug here now be resolved DUPLICATE of 135818 or rather depend on
it?

------- Comment #3 From Carsten Lohrke 2006-08-24 08:55:43 0000 -------
Dupe is fine. ;)

*** This bug has been marked as a duplicate of 135818 ***

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug