Bug 892758
| Summary: | knotify4: After upgrade to F18: "An internal system error has occurred" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Alan Schmidt <bucky> | ||||
| Component: | kde-runtime | Assignee: | Than Ngo <than> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | jreznik, kevin, ltinkl, rdieter, rnovacek, than | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-02-05 14:32:11 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
I *think* that's coming from akonadi, but hard to say indeed. Any clues in ~/.xsession-errors? The date on .xsession-errors is from last Friday, BEFORE I upgraded: $ ls -l .xsession-errors -rw-------. 1 aschmidt aschmidt 188950 Jan 4 15:57 .xsession-errors The last few lines go: $ tail .xsession-errors Application '/usr/bin/nepomukservicestub nepomukfileindexer' crashed! 0 restarts left. [/usr/bin/nepomukservicestub] Invalid MIT-MAGIC-COOKIE-1 keynepomukservicestub: cannot connect to X server :0 Application '/usr/bin/nepomukservicestub nepomukbackupsync' crashed! 0 restarts left. [/usr/bin/nepomukservicestub] Invalid MIT-MAGIC-COOKIE-1 key [/usr/bin/nepomukservicestub] nepomukservicestub: cannot connect to X server :0 [/usr/bin/nepomukservicestub] Invalid MIT-MAGIC-COOKIE-1 key [/usr/bin/nepomukservicestub] nepomukservicestub: cannot connect to X server :0 Application '/usr/bin/nepomukservicestub nepomukfileindexer' crashed to often. Giving up! Application '/usr/bin/nepomukservicestub nepomukbackupsync' crashed to often. Giving up! Application 'akonadiserver' exited normally... that's a bad sign, X isn't starting enough to even start logging errors. :( Recommendations: if you can, login as root, try some basic stuff : yum distro-sync try another user I'm logged in to KDE on the console as me.
$ ls -l /var/log/Xorg.0.log
-rw-r--r--. 1 root root 82006 Jan 7 09:56 /var/log/Xorg.0.log
# fgrep '(EE)' /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 32.043] (EE) Failed to load module "nv" (module does not exist, 0)
[ 32.043] (EE) Failed to load module "modesetting" (module does not exist, 0)
# yum distro-sync
Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
No Packages marked for Distribution Synchronization
I thought ~/.xsession-errors being unupdated for a few days was a good thing. :-(
The frequent error messages seem to have stopped as mysteriously as they began.
The last few things I did before they shut up were re-allowing some things that selinux forgot about in the upgrade (I'm in permissive mode):
# yum install policycoreutils-devel
# grep httpd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
Do you think "The backend" could have been the selinux notifier? I can honestly say I don't know the correct name of the selinux notifier backend. "ps ax | fgrep selinux" gives me a whole lot of nothing.
But bringing this back around to knotify4: Can knotify identify the process that sent it a message, or is it pretty much limited to displaying what it's been told? If it doesn't now, could it do it without breaking anything (even if it were just some kind of verbose logging thing)? This notification comes from Apper, it produces that warning when packagekitd gets killed while a transaction is in progress. This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 674262 [details] Snapshot of the popup notification message Need to be able to make knotify tell me what application is reporting a message to it. Description of problem: Every 10 minutes or so, the knotify tray application pops up a message: Icon: Big gray X Title: An internal system error has occurred Content: The backend exited unexpectedly. This is a serious error as the spawned backend did not complete the pending transaction. I have every expectation that this is NOT knotify itself (Maybe it IS! The message isn't clear, though), but I can't make knotify tell me what application is logging this error. SO: THIS report is all about getting knotify to tell me WHAT'S reporting to it, so I can properly file a report about the application that's having the error.