Bug 282553 - kpackage crashed and wont allow report; says "/Unknown error./"
Summary: kpackage crashed and wont allow report; says "/Unknown error./"
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-22 13:09 UTC by papillion
Modified: 2011-09-22 13:38 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: lucid


Attachments
kpackage crashed and wont allow bug report (5.54 KB, application/octet-stream)
2011-09-22 13:09 UTC, papillion
Details

Note You need to log in before you can comment on or make changes to this bug.
Description papillion 2011-09-22 13:09:08 UTC
Created attachment 63855 [details]
kpackage crashed and wont allow bug report

Version:           unspecified
OS:                Linux


kpackage is set to allow me to review packages before install yet seems to have a mind of its own and tries to install updates at times autonomously. Also when trying to access bugs.kde.org a window popped up saying the security certificate was invalid so I had to press "continue" to the untrusted site or it would have terminated the dialogue. I wonder if this pc is hacked sometimes because of its strange behavior... especially with regards to security update details information and also a wierd splash screen that pops up when booting which appears to have programming lines flash on screen very quickly in a large font but too fast to see what it reads and is unlike the normal small font which appears just after that time and is readable.

Reproducible: Didn't try

Steps to Reproduce:
explained in details

Actual Results:  
explained in details

Expected Results:  
expected to be able to review package details before install

explained in details
Comment 1 papillion 2011-09-22 13:14:37 UTC
This pc has lucid installed. Is there a way to have a "scan" done remotely to identify problems with installation?
Comment 2 Christoph Feck 2011-09-22 13:38:49 UTC
The bug has been fixed in KPackageKit 0.6.3.