[solved] gparted doesn't start because of missing 90-mandatory.d/

[musca]

Hello,

when you try to start gparted and nothing happens, this might help.

Running from terminal i saw this message:

Code: [Select]

$ gparted-pkexec
/var/lib/polkit-1/localauthority/90-mandatory.d does not exist. Please install policykit-1But policykit-1 is installed, of course.

The solution is another nice finding of our user terroreek. Please execute as root:

Code: [Select]

# mkdir -p /var/lib/polkit-1/localauthority/90-mandatory.d/
This will enable gparted to create the file /var/lib/polkit-1/localauthority/90-mandatory.d/udisks2-inhibit.pkla while it is running.

greetings
musca

[gabrielb]

Thanks a lot!

[dibl]

I hit this issue yesterday and had no idea what was wrong, so I had to boot a USB stick to deal with a drive. Yes, thanks very much.

[musca]

hello,

thanks for the feedback.

For KDE users there is the kvpm volume and partition manager which can deal with lvm2 volumes.

greetings
musca

[bullgard4]

This helped with me, too.
Thank you very much.

[gnasch]

dpkg-reconfigure gparted helped here and created the necessary directory.

best,
gnasch

[michaa7]

Thanks. just saw this. Stumbled into this yesterday, solved now.

[seasons]

Link to bug report is always helpful: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790333
So it's closed, but where is the bug report for policykit-1?

[melmarker]

it wasn't really a debian bug - i was my fault to upload the new version of policykit-1, which don't play nice with the other components - so before filing a bug against debian a look into apt-cache could be useful. in case the package in charge is from the siduction repos it would be wise to ask here first

[michaa7]

it wasn't really a debian bug ...

Hm, I had this bug, but the siduction version of policykit-1 was not installed.

# apt-cache policy policykit-1
policykit-1:
  Installiert:           0.112-5.2
  Installationskandidat: 0.112-5.3.1~really-0.105-8
  Versionstabelle:
     0.112-5.3.1~really-0.105-8 0
        500 ftp://ftp.uni-stuttgart.de/siduction/extra/ unstable/main amd64 Packages
 *** 0.112-5.2 0
        100 /var/lib/dpkg/status
     0.112-5 0
          1 http://http.debian.net/debian/ experimental/main amd64 Packages
     0.105-8 0
        500 http://http.debian.net/debian/ unstable/main amd64 Packages
        500 http://http.debian.net/debian/ testing/main amd64 Packages
     0.105-3 0
        500 http://http.debian.net/debian/ wheezy/main amd64 Packages

[seasons]

it wasn't really a debian bug - i was my fault to upload the new version of policykit-1, which don't play nice with the other components - so before filing a bug against debian a look into apt-cache could be useful. in case the package in charge is from the siduction repos it would be wise to ask here first

Ah, thank you. I'm sorry if I caused any confusion. :/

[musca]

hello seasons,

no worries your questions are welcome.

hello michaa7,

your installed version has a higher versionnumber than the debian package.
In fact you are still using the faulty package.

greetings
musca

[michaa7]

You are right. I was confused, because you can't see where the installed package came from.