new sidiction-settings-xfce package seems to be broken

Started by m-puzirew, 2013/07/01, 02:16:10

Previous topic - Next topic

m-puzirew

Ouch. It's interesting - I don't see any /home/max/.gvfs folder in
Double Commander as root but I can see it in Thunar (both as root and as user). Really weird... :shock:

michaa7

In Thunar "show hidden files" is activated, in Double Commander not.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

m-puzirew

:lol: You took me for someone else. I know what hidden files are and how to set Double Commander to show them. Anyway, thank you for helping healthy laughter!
But seriously, this might be a new Double commander beta bug. If so, It is strange that the bug proved itself with that "enigmatic" folder, as if on cue.
P.S. Most likely, it's because of the fact that .gvfs is not a common folder, but represents a virtual filesystem. Now I can't remember the reason why I had installed it, maybe to handle with a cloud storage or something. Hmm, I need to deal with this...

m-puzirew

As an experiment, after deleting gvfs-fuse and gvfs-bin the siduction-settings-xfce package installation showed no error, but user settings was lost on reboot again all the same. This perhaps proves that siduction-settings-xfce package is indeed broken and have to be changed.

convbsd

Thank you.
I have taked a look at it and it will be ok.

musca

Hello m-puzirew,

you don't need to translate messages manually. To produce english output you can prepend any command with an assignment ,e.g.
# LC_ALL=C apt-mark hold  siduction-settings-kde
siduction-settings-kde set on hold.

I hope this saves you some time.

musca
,,Es irrt der Mensch, solang er strebt."  (Goethe, Faust)

LeYaude

Hi,

I may be late to the party, but I ran into the same problem with .gvfs lately, with the update to lxde-settings.
From what I gathered on the Internet, it's because .gvfs is a fuse mount mounted by the user, and fuse mounts cannot be touched by other users, be it root. I could work around it by first unmounting .gvfs (with no bad effect at least until now) running

sudo umount ~/.gvfs

and then proceeded successfully to the update.

Hope this helps.
Yoann.

m-puzirew

Thanks, musca, this may be helpful when in terminal!
LeYanude, thank you too, I'll take your advice into consideration.