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 2316 - knotify crash
Summary: knotify crash
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: other (any) (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-01-17 23:57 CST by Darrell
Modified: 2018-05-27 10:47 CDT (History)
2 users (show)

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

Attachments
knotify crash (32.73 KB, text/plain)
2015-01-17 23:57 CST, Darrell 		Details
knotify crash backtrace (32.60 KB, text/plain)
2015-05-31 21:07 CDT, 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-01-17 23:57:53 CST 
Created attachment 2423 [details]
knotify crash

Through the past few weeks I have seen knotify crashes more than once. I am _not_ certain, but I think the attached backtrace crash occurred when coming out of monitor DPMS sleep.
Comment 1 Darrell 2015-02-05 14:44:25 CST 
Please refer to bug 2345 and bug 2349. I believe the root cause is related.
Comment 2 Darrell 2015-02-17 17:49:12 CST 
When this crash occurs I no longer can access remote systems via VNC, even with non TDE apps. Worse, I have to exit TDE in the remote system, manually kill TDE processes and restart TDE.
Comment 3 Darrell 2015-05-31 13:01:28 CDT 
Please add this bug report and bug 2345 and bug 2349 to the next release priorities.

I use remote desktop a lot. When the remote system monitor has entered DPMS, I always have to ssh into the remote system to first run xset before attempting to use VNC. If I do not run xset then I am unable to use VNC. All I see is a black screen.

About half the time I see the knotify crash attached in this bug report. When that happens I have to restart the remote Trinity desktop.

About half the time the remote desktop krfb does not terminate when ending the VNC session. I have to ssh into the remote system to kill the existing krfb before I can again use VNC into the remote system.

I am sure all of these bug reports are related. While the xset requirement when the remote monitor is in DPMS is repeatable, I cannot fully repeat the knotify crash or krfb not terminating properly.

Not to forget the swapped mouse buttons I have to endure as reported in bug 1583.

Not to sound bitter or angry, but my VNC experience in TDE is having a classic "paper cut" affect on my enthusiasm for the project. :(
Comment 4 Darrell 2015-05-31 13:08:35 CDT 
Probably should add bug 2023 and bug 2336 to this list.
Comment 5 Darrell 2015-05-31 21:07:42 CDT 
Created attachment 2514 [details]
knotify crash backtrace

A kcrash backtrace is attached.

I have not tested for repeatability, but I get this knotify crash often on my home theater pc (HTPC). To trigger the crash and backtrace:

* I power on the HTPC or the HTPC is already on for a scheduled recording.

* At my laptop or office computer I su - to root.

* I ssh to my HTPC with keys.

* I su - htpc, which is my default HTPC user account.

* I perform maintenance or schedule TV recordings.

* I exit as user htpc.

* I exit the ssh session.

As I do this remotely, I do not have my TV on to monitor the HTPC desktop. Somewhere along the way the KCrash dialog appears. I will notice this only after powering on the TV to watch a recording or listen to music. Because of the crash, I exit the session, restart the X server, and manually login as htpc.

The HTPC is running Slackware 14.1 and Trinity GIT built on Feb 15.