I've seen it twice too since the latest batch of PackageKit related updates came in,
https://admin.fedoraproject.org/updates/FEDORA-2015-0921
-- rex
________________________________________ From: kde-bounces@lists.fedoraproject.org kde-bounces@lists.fedoraproject.org on behalf of Peter G. pgueckel@gmail.com Sent: Thursday, January 22, 2015 11:35 AM To: kde@lists.fedoraproject.org Subject: Plasma Desktop - An internal system error has occurred.
My system is up-to-date every day. Yesterday, right after logging in and again today, right after logging in, the following pop-up appeared on the screen, before I did anything:
A problem that we were not expecting has occurred. Please report this bug with the error description.
Details:
Did not receive a reply. Possible causes include: The remote application did not send reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
When this occurs, I am unable to do anything: no right click on the desktop, the task bar is inactive and unresponsive, but I can still use the active screen edges to change virtual desktops. I click around, repeatedly clicking on the application tabs on the task bar, click the fedora 'f' a number of times, and presto! Suddenly it all works again. I don't notice any problems with the session until, presumably, the same error upon the subsequent login.
Wha?
_______________________________________________ kde mailing list kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
Rex Dieter wrote:
I've seen it twice too since the latest batch of
PackageKit related
updates came in,
https://admin.fedoraproject.org/updates/FEDORA-2015-0921
-- rex
They gave it 5 Karma! Shouldn't it have -5?
Do you think I should vote? Would that get their heads working? :D
On Thu, Jan 22, 2015 at 10:57:59AM -0700, Peter G. wrote:
https://admin.fedoraproject.org/updates/FEDORA-2015-0921 They gave it 5 Karma! Shouldn't it have -5?
Do you think I should vote? Would that get their heads working? :D
I'm not sure where that tone is coming from. It worked for the people who tested it. It would certainly be helpful to have more testers, especially for critical updates like this one.
Working on a test plan for PackageKit (see http://fedoraproject.org/wiki/QA:SOP_package_test_plan_creation) which also includes KDE cases would certainly help.
Matthew Miller wrote:
Do you think I should vote? Would that get their
heads
working? :D
I'm not sure where that tone is coming from. It
worked for the people
who tested it. It would certainly be helpful to have
more testers,
especially for critical updates like this one.
Sorry. No intention to offend :( I didn't even know that this was a PackageKit problem until Rex told me. Is this one in testing? I didn't know. Again, sorry. I don't actually run testing repo, but I have it enabled in F21 for some reason. There has been so little new stuff lately, I guess I wanted some excitement ;-) Usually, we get a new kde every few weeks LOL
Peter G. wrote:
They gave it 5 Karma! Shouldn't it have -5?
It got +5 karma so quickly because it fixed a critical regression in GNOME PackageKit caused by the previous update. And of course, as always, nobody bothers testing KDE, grrr…
Do you think I should vote? Would that get their heads working? :D
Unfortunately, -1 votes on updates that were already pushed to stable basically get ignored. Bodhi doesn't do anything with them (stable updates are never unpushed), and the maintainer usually won't care either. Filing bugs in Bugzilla is more effective.
Kevin Kofler
Hi,
On Thu 22 January 2015 17:38:05 Rex Dieter wrote:
I've seen it twice too since the latest batch of PackageKit related updates came in,
I have also seen this and think it could be Apper as the PackageKit updates did cause it some problems. Due to lack of time I had not looked into that further just yet, so for the time being I had to remove Apper :-(
Reading this thread as a quick test to confirm I re-installed Apper and checked updates with it and the error was back. So I can trigger it by checking for updates with Apper
PackageKit-1.0.4-1 apper-0.9.1-6 F21/4.14.4
Colin
Rex Dieter wrote:
I've seen it twice too since the latest batch of PackageKit related updates came in,
Based on a recent bug report, https://bugzilla.redhat.com/show_bug.cgi?id=1185180
It would appear the problem is a recent librepo update, https://admin.fedoraproject.org/updates/FEDORA-2015-0896/librepo-1.7.12-1.fc...
In short, for me, apper/PackageKit is happy with librepo-1.7.11, but problems start with librepo-1.7.12 is installed.
-- rex
Rex Dieter wrote:
Rex Dieter wrote:
I've seen it twice too since the latest batch of PackageKit related updates came in,
Based on a recent bug report, https://bugzilla.redhat.com/show_bug.cgi?id=1185180
It would appear the problem is a recent librepo update,
https://admin.fedoraproject.org/updates/FEDORA-2015-0896/librepo-1.7.12-1.fc...
In short, for me, apper/PackageKit is happy with librepo-1.7.11, but problems start with librepo-1.7.12 is installed.
And with some quick irc pinging, between hughsie and tmlcoch (librepo maintainer), the problem was quickly identified, the problematic librepo update will be revoked and a fixed librepo on the way asap.
-- Rex
On 01/23/2015 07:12 AM, Rex Dieter wrote:
Rex Dieter wrote:
Rex Dieter wrote:
I've seen it twice too since the latest batch of PackageKit related updates came in,
Based on a recent bug report, https://bugzilla.redhat.com/show_bug.cgi?id=1185180
It would appear the problem is a recent librepo update,
https://admin.fedoraproject.org/updates/FEDORA-2015-0896/librepo-1.7.12-1.fc...
In short, for me, apper/PackageKit is happy with librepo-1.7.11, but problems start with librepo-1.7.12 is installed.
And with some quick irc pinging, between hughsie and tmlcoch (librepo maintainer), the problem was quickly identified, the problematic librepo update will be revoked and a fixed librepo on the way asap.
-- Rex
Great work, Rex!
Rex Dieter wrote:
And with some quick irc pinging, between hughsie and
tmlcoch (librepo
maintainer), the problem was quickly identified, the
problematic librepo
update will be revoked and a fixed librepo on the way
asap.
Quick thinking :) Thanks!
-
Colin J Thomson -
Dan Mossor -
Kevin Kofler -
Matthew Miller -
Peter G. -
Rex Dieter -
Rex Dieter