Bug 6982 - drakconf.real crashed (The URI 'applications://tools/' is not an absolute URI)
Summary: drakconf.real crashed (The URI 'applications://tools/' is not an absolute URI)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-08-08 03:59 CEST by Garth Hoyman
Modified: 2012-09-06 11:43 CEST (History)
1 user (show)

See Also:
Source RPM: drakconf-12.30-1.mga2
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Garth Hoyman 2012-08-08 03:59:09 CEST 
The "drakconf.real" program crashed. Drakbug-14.21 caught it.

opening kde system settings

The URI 'applications://tools/' is not an absolute URI using the "file" scheme at /usr/sbin/drakconf.real line 995.
Perl's trace:
standalone::bug_handler() called from /usr/sbin/drakconf.real:1106

Theme name: oxygen-gtk
Kernel version = 3.3.6-desktop586-2.mga2
Distribution=Mageia release 2 (Official) for i586
CPU=Intel(R) Celeron(R) CPU 2.60GHz
Comment 1 Manuel Hiebel 2012-08-08 15:44:55 CEST 
>opening kde system settings

how ? (I don't see the relation with drakconf)

Keywords: (none) => NEEDINFO

Comment 2 Garth Hoyman 2012-08-08 16:23:11 CEST 
I don't know that there is any connection
it's just what I was doing when the crash occured

I had done an upgrade to mageia2 
My lower panel kept disappearing & other odd things happening, causing me to have to restart
I disabled all desktop effects, which seemed to help

this bug can probably be closed, I was just following through the bug procedure
Thanks for your time & hard work
Thierry Vignaud 2012-09-06 11:34:22 CEST

CC: (none) => thierry.vignaud
Summary: drakconf.real crashed => drakconf.real crashed (The URI 'applications://tools/' is not an absolute URI)

Comment 3 Thierry Vignaud 2012-09-06 11:43:33 CEST 
Still a crash that can be fixed.
Fixed in git

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.