Bug 4265 - Messsage that conquerorrc is not writable after clicking on link in Drakx
Summary: Messsage that conquerorrc is not writable after clicking on link in Drakx
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 19:22 CET by Michiel Keuterman
Modified: 2012-12-02 14:31 CET (History)
1 user (show)

See Also:
Source RPM: rpmdrake-5.26.10-1.mga1
CVE:
Status comment:


Attachments

Description Michiel Keuterman 2012-01-24 19:22:06 CET
Description of problem: After I clicked on a link to the Nvidia website in drakx, i first got a message 'your Firefox profile cannot be loaded. It may be misssssing or inaccesible.' Then I clicked OK an then i got the message that /root/kde4/config/conquerorrc is 'niet schrijfbaar'(this was in Dutch it means 'not writable', but i wasn't sure about the transslation). 


Version-Release number of selected component (if applicable):


How reproducible:it happened each time i tried it. That was 3 times with the Nvidia website and one time with the Firefox website


Steps to Reproduce:
1.Open drakx
2.select a pakage
3.click on 'details'
4.click on the link to the official website
5.click OK
6.read the messsage
Comment 1 Marja Van Waes 2012-02-14 06:18:12 CET
Thanks for your bug report

I suppose you mean /root/.kde4/share/config/konquerorrc

That file is only writeable by root, and it is good FF doesn't start as root :)

When I try to reproduce, I get your first message, too, but only if FF wasn't already started. When FF is already running, the page I click on opens fine in FF. Instead of the second message, the page is opened with epiphany.

assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => thierry.vignaud
Source RPM: /root/kde4/share/config/conquerorrc => rpmdrake-5.26.10-1.mga1

Comment 2 Manuel Hiebel 2012-02-14 13:12:47 CET
duplicate of https://bugs.mageia.org/show_bug.cgi?id=287 ?
Comment 3 Marja Van Waes 2012-02-15 15:28:40 CET
(In reply to comment #2)
> duplicate of https://bugs.mageia.org/show_bug.cgi?id=287 ?

No, if FF would start as root, /root/.kde4/share/config/konquerorrc wouldn't be a problem because it is owned by root and thus root writeable. 

And Epiphany, when available, doesn't start as root, either, but as normal user.

So bug 287 was and remains solved :)
Comment 4 Marja Van Waes 2012-07-06 15:03:32 CEST
Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D
Comment 5 Manuel Hiebel 2012-11-05 16:51:10 CET
This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

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 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 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 Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

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 Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad
Comment 6 Manuel Hiebel 2012-12-02 14:31:16 CET
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.