the error is the same as bug #1324 so marking as duplicate

*** This bug has been marked as a duplicate of bug 1324 ***

Status: NEW => RESOLVED
CC: (none) => balcaen.john
Resolution: (none) => DUPLICATE

Reopening since if the symptoms are similar, the cause is not the same as in bug #1324

Status: RESOLVED => REOPENED
Resolution: DUPLICATE => (none)

@ Jacques 

you filed this bug against cauldron, but in september there was no proper way to install cauldron directly, at that time you had to install mageia one and then update with the cauldron repositories to get a working cauldron install.

Is that what you did?

Did you get a chance to install Mageia 2 alpha (1,2,or 3)?
If so, did you have the same problem?

Keywords: (none) => NEEDINFO
CC: (none) => marja11, oliver.bgr

Usually, I install cauldron by ftp with a CD burned with boot.iso
Now it is not possible to have a clean LXDE because there is many needless
kde packages with it.
So I install a minimal cauldron + task-X + task-lxde + drakconf
In this case there is the same problem

Your suggestion to use mageia 1 and then update is not good to test cauldron
because the configuration has been made by mageia 1 not by cauldron.

We will see that problem when lxde will be install correctly.

Well, I don't see anything about LXDE installing incorrectly. Normaly packages don't do anything in the user's home directory on installation, and many people (including me) wouldn't be amused, if they did.
So it's xarchiver's problem, that it can't create the files/directories it needs.

@ Jacques
@ Oliver

Thx for your comments :)


cc'ing Jaromir, who committed xarchiver for cauldron yesterday

Keywords: NEEDINFO => (none)
CC: (none) => tavvva
Source RPM: (none) => xarchiver

Hello.

Yes, I also believe this should be fixed directly in the Xarchiver. I'll try to create a patch for that asap.

Regards,
Jaromir.

(In reply to comment #7)
> Hello.
> 
> Yes, I also believe this should be fixed directly in the Xarchiver. I'll try to
> create a patch for that asap.
> 
> Regards,
> Jaromir.

Thanks a lot :)

assigning to you

Please set status to ASSIGNED :)

Assignee: bugsquad => tavvva

Ok ...

Status: REOPENED => ASSIGNED

After some investigation here I started to believe it could be better to solve this directly in GTK. The same happens after opening files in Eye of Gnome, gaupol, gedit, ... and probably many others.
I'm gonna change the component to GTK and we'll see.

Assignee: tavvva => bugsquad
Source RPM: xarchiver => gtk+2.0-2.24.10-3.mga2.src.rpm

(In reply to comment #10)
> After some investigation here I started to believe it could be better to solve
> this directly in GTK. The same happens after opening files in Eye of Gnome,
> gaupol, gedit, ... and probably many others.
> I'm gonna change the component to GTK and we'll see.

assigning to Olav, then

Status: ASSIGNED => NEW
Assignee: bugsquad => olav

Please update the summary when assigning. I don't care about LXDE. I'm guessing this is about GTK+3.0.

Summary: Missing directories ~/.local/share for LXDE => GTK+ doesn't create ~/.local/share/recently-used.xbel
Source RPM: gtk+2.0-2.24.10-3.mga2.src.rpm => gtk+3.0-3.3.18-1.mga2

Not totally sure if GTK+ is responsible, filed https://bugzilla.gnome.org/show_bug.cgi?id=671817 upstream in GTK+. I'll follow whatever they say.

See Also: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=671817

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

This bug is still valid for Mageia 2.

Whiteboard: (none) => MGA2TOO

Not getting a response from upstream. Pinged them in upstream bug.

This is fixed in gtk+ 3.4.4. Going to push all of that in bug 7413.

Depends on: (none) => 7413

Is it still valid or fixed?

CC: (none) => tarakbumba

This bug is fixed, so I close it.

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