3:34 p.m.
I keep getting this notification after a kernel crash (yeah, f18 has been
crashy. Maybe vbox issue).
No clues are given what this internal error is about. But every few minutes I
get another notification.
3:38 p.m.
Am 02.03.2013 22:34, schrieb Neal Becker:
I keep getting this notification after a kernel crash (yeah, f18 has
been
crashy. Maybe vbox issue).
No clues are given what this internal error is about. But every few minutes I
get another notification.
and what should anybody say to it with zero information
except "shit happens"?
dmesg or /var/logM7essages is your friend
at least anybody needs infos what KDE version and
what hardware you are using
3:41 p.m.
Reindl Harald wrote:
Am 02.03.2013 22:34, schrieb Neal Becker:
> I keep getting this notification after a kernel crash (yeah, f18 has been
> crashy. Maybe vbox issue).
>
> No clues are given what this internal error is about. But every few minutes
> I get another notification.
and what should anybody say to it with zero information
except "shit happens"?
dmesg or /var/logM7essages is your friend
at least anybody needs infos what KDE version and
what hardware you are using
I don't see anything useful in /var/log/messages or .xsession-errors
The notification plasma says
An internal system error has occurred
The backend exited unexpectedly. This is a serious error as the spawned backend
did not complete the pending transaction.
Hmm, smells like yum issue.
4:04 p.m.
On 03/02/2013 03:38 PM, Reindl Harald wrote:
Am 02.03.2013 22:34, schrieb Neal Becker:
> I keep getting this notification after a kernel crash (yeah, f18 has been
> crashy. Maybe vbox issue).
>
> No clues are given what this internal error is about. But every few minutes I
> get another notification.
and what should anybody say to it with zero information
except "shit happens"?
My educated guess would be this is coming from apper and PackageKit-yum
backend.
-- rex
4:23 p.m.
Rex Dieter wrote:
On 03/02/2013 03:38 PM, Reindl Harald wrote:
>
>
> Am 02.03.2013 22:34, schrieb Neal Becker:
>> I keep getting this notification after a kernel crash (yeah, f18 has been
>> crashy. Maybe vbox issue).
>>
>> No clues are given what this internal error is about. But every few minutes
>> I get another notification.
>
> and what should anybody say to it with zero information
> except "shit happens"?
My educated guess would be this is coming from apper and PackageKit-yum
backend.
-- rex
Yeah. Strangely, it seems to be fixed now, after running yum install digikam.
yum reported no errors, did the install. But now I'm not seeing messages from
apper. Strangely also, running apper manually (before fixing the problem)
reported no errors, and seemed to operate normally.
4:25 p.m.
Am 02.03.2013 23:23, schrieb Neal Becker:
Rex Dieter wrote:
> On 03/02/2013 03:38 PM, Reindl Harald wrote:
>>
>>
>> Am 02.03.2013 22:34, schrieb Neal Becker:
>>> I keep getting this notification after a kernel crash (yeah, f18 has been
>>> crashy. Maybe vbox issue).
>>>
>>> No clues are given what this internal error is about. But every few minutes
>>> I get another notification.
>>
>> and what should anybody say to it with zero information
>> except "shit happens"?
>
> My educated guess would be this is coming from apper and PackageKit-yum
> backend.
>
> -- rex
>
Yeah. Strangely, it seems to be fixed now, after running yum install digikam.
yum reported no errors, did the install. But now I'm not seeing messages from
apper. Strangely also, running apper manually (before fixing the problem)
reported no errors, and seemed to operate normally
package-cleanup --problems
yum clean metadata && yum upgrade
are always the best you can do as first step
throw away all this graphical update-crap
4072
days inactive
4072
days old
5 comments
3 participants
participants (3)
-
Neal Becker -
Reindl Harald -
Rex Dieter