Re: [arch-general] Can not run kdesu kate

[Ralf Mardorf]

On Sun, 16 Jul 2017 01:54:51 +0200, sL1pKn07 SpinFlo via arch-general
wrote:
>the "problem" is kate, not kdesudo or kdesu
>
>https://cgit.kde.org/kate.git/commit/?id=9adcebd3c2e476c8a32e9b455cc99f46b0e12a7e

Good catch! So the OP should ignore my reply :).

Re: [arch-general] Can not run kdesu kate

[sL1pKn07 SpinFlo via arch-general]

2017-07-16 1:57 GMT+02:00 Ralf Mardorf :
> On Sat, 15 Jul 2017 23:37:54 +, Junayeed Ahnaf wrote:
>>Freshly installed arch with KDE and I can not run kdesu kate
>>filename . When I enter this command it asks for a password and after
>>that it does absolutely nothing. What can I do ?
>
> Hi,
>
> did you expect "sudo" or "su"? IOW did you type the correct password
> "user" or "root" password? Did you run it from command line to get
> detailed information?
>
> On my system I've got "kdesu4" installed, but there is no "kdesu"
> available.
>
> [rocketmouse@archlinux ~]$ ls -hAl /usr/bin/kdesu
> ls: cannot access '/usr/bin/kdesu': No such file or directory
> [rocketmouse@archlinux ~]$ ls -hAl /usr/bin/kdesu*
> lrwxrwxrwx 1 root root 27 Jul 12 09:41 /usr/bin/kdesu4 -> 
> /usr/lib/kde4/libexec/kdesu
> [rocketmouse@archlinux ~]$ pacman -Qo /usr/bin/kdesu4
> /usr/bin/kdesu4 is owned by kdebase-runtime 17.04.3-1
>
> So if I e.g. type
>
> [rocketmouse@archlinux ~]$ kdesu xed
> bash: kdesu: command not found
>
> I get "command not found".
>
> Btw. I don't use it ;).
>
> Seemingly the command "kdesu" does exist on your machine, but it seems
> to be configured incorrectly.
>
> Did you take care of
>
> https://wiki.archlinux.org/index.php/sudo#kdesu
>
> ?
>
> Regards,
> Ralf

kdesu is part of kde-cli-tools from [extra]

Re: [arch-general] Can not run kdesu kate

[Ralf Mardorf]

On Sat, 15 Jul 2017 23:37:54 +, Junayeed Ahnaf wrote:
>Freshly installed arch with KDE and I can not run kdesu kate
>filename . When I enter this command it asks for a password and after
>that it does absolutely nothing. What can I do ?

Hi,

did you expect "sudo" or "su"? IOW did you type the correct password
"user" or "root" password? Did you run it from command line to get
detailed information?

On my system I've got "kdesu4" installed, but there is no "kdesu"
available.

[rocketmouse@archlinux ~]$ ls -hAl /usr/bin/kdesu
ls: cannot access '/usr/bin/kdesu': No such file or directory
[rocketmouse@archlinux ~]$ ls -hAl /usr/bin/kdesu*
lrwxrwxrwx 1 root root 27 Jul 12 09:41 /usr/bin/kdesu4 -> 
/usr/lib/kde4/libexec/kdesu
[rocketmouse@archlinux ~]$ pacman -Qo /usr/bin/kdesu4
/usr/bin/kdesu4 is owned by kdebase-runtime 17.04.3-1

So if I e.g. type

[rocketmouse@archlinux ~]$ kdesu xed
bash: kdesu: command not found

I get "command not found".

Btw. I don't use it ;).

Seemingly the command "kdesu" does exist on your machine, but it seems
to be configured incorrectly.

Did you take care of

https://wiki.archlinux.org/index.php/sudo#kdesu

?

Regards,
Ralf

Re: [arch-general] Can not run kdesu kate

[sL1pKn07 SpinFlo via arch-general]

2017-07-16 1:51 GMT+02:00 Junayeed Ahnaf :
> Any idea why kdesu isn't working?
>
> Sent from BlueMail
> On Jul 16, 2017, at 5:50 AM, sL1pKn07 SpinFlo via arch-general
>  wrote:
>>
>> 2017-07-16 1:37 GMT+02:00 Junayeed Ahnaf via arch-general
>> :
>>>
>>>  Hello,
>>>
>>>
>>>  Freshly installed arch with KDE and I can not run kdesu kate filename .
>>> When I enter this command it asks for a password and after that it does
>>> absolutely nothing. What can I do ?
>>>
>>>
>>>  Thanks
>>>
>>>
>>>
>>>  Junayeed Ahnaf Nirjhor
>>>  Twitter @ Nirjhor
>>
>>
>> SUDO_EDITOR=kate sudoedit 
>>
>> i'm not like, but works

the "problem" is kate, not kdesudo or kdesu

https://cgit.kde.org/kate.git/commit/?id=9adcebd3c2e476c8a32e9b455cc99f46b0e12a7e

Re: [arch-general] Can not run kdesu kate

[Junayeed Ahnaf via arch-general]

Any idea why kdesu isn't working?

Sent from BlueMail
On Jul 16, 2017, at 5:50 AM, sL1pKn07 SpinFlo via arch-general 
> wrote:

2017-07-16 1:37 GMT+02:00 Junayeed Ahnaf via arch-general
:
 Hello,


 Freshly installed arch with KDE and I can not run kdesu kate filename . When I 
enter this command it asks for a password and after that it does absolutely 
nothing. What can I do ?


 Thanks



 Junayeed Ahnaf Nirjhor
 Twitter @ Nirjhor

SUDO_EDITOR=kate sudoedit 

i'm not like, but works

Re: [arch-general] Can not run kdesu kate

[sL1pKn07 SpinFlo via arch-general]

2017-07-16 1:37 GMT+02:00 Junayeed Ahnaf via arch-general
:
> Hello,
>
>
> Freshly installed arch with KDE and I can not run kdesu kate filename . When 
> I enter this command it asks for a password and after that it does absolutely 
> nothing. What can I do ?
>
>
> Thanks
>
>
>
> Junayeed Ahnaf Nirjhor
> Twitter @ Nirjhor

SUDO_EDITOR=kate sudoedit 

i'm not like, but works

[arch-general] Can not run kdesu kate

[Junayeed Ahnaf via arch-general]

Hello,


Freshly installed arch with KDE and I can not run kdesu kate filename . When I 
enter this command it asks for a password and after that it does absolutely 
nothing. What can I do ?


Thanks



Junayeed Ahnaf Nirjhor
Twitter @ Nirjhor

Re: [arch-general] New - systemd 234 - luks partition fails to ask for password

[Noah Schoem via arch-general]

I'm also running cryptsetup 1.7.5-1, but with an out-of-date linux kernel
and systemd (4.11.9-1 and 233.75-3, respectively) and it's working fine;
it's plausibly a regression with one of those two.

Is this bug also present on the linux-lts kernel? I've found some issues
I've had go away with a different kernel.

On Jul 15, 2017 16:07, "Genes Lists via arch-general" <
arch-general@archlinux.org> wrote:


This has been working for years - starting on recent reboots systemd is
failing to ask for password for luks encrypted /home partition and boot
halts.

Fully updated from testing repos - when I reboot now, systemd no longer
asks for password to unlock luks partition. There is no hesitation at all
and no password prompt at all. The boot runs through and gives an error
that crypt set up failed.

Root is not encrypted just /home. I'm then prompted to press Ctl D or
give root password and drop to single user mode - doing that then I can
manually do:

   cryptsetup open /dev/sdxx home

which prompts for password and succeeds

After I do above, then the error goes away evidenced by:
   systemctl status systemd-cryptsetup@home.service

shows all is normal - exiting from single user 'repair' mode - then
boot continues and completes normally. And /home gets mounted via
/dev/mapper as normal

The issue is with latest systemd that I no longer get prompted for a
password for the luks encrypted partition.

Thoughts:
systemd password agents:
running systemd-ask-password by hand does indeed ask for password
in the console.

/run/systemd/ask-password is empty directory.

the journal contains this:

systemd-cryptsetup[316]: Failed to query password: Timer expired
systemd[1]: Failed to start Cryptography Setup for home.
(Its possible that the bug is in systemd-cryptsetup in latest release?)

Versions:
# pacman -Q linux systemd

linux 4.12.1-2
systemd 234.0-2
cryptsetup 1.7.5-1

I googled but was no able to find any relevant bugs - checked systemd
github issues but found nothing similar.

thanks.





--
Gene
li...@sapience.com

Re: [arch-general] New - systemd 234 - luks partition fails to ask for password - workaround

[Genes Lists via arch-general]

Could wel be related: 
https://github.com/systemd/systemd/pull/6264




-- 
Gene
li...@sapience.com

Re: [arch-general] New - systemd 234 - luks partition fails to ask for password - workaround

[Genes Lists via arch-general]

I have a work around which is to add timeout=90

It seems the  timeout=0, which is the default) and is supposed to mean
wait indefinitely) is now treated as dont prompt or wait at all.

I cannot say if this is a change in behavior which is intentional and
the man pages need to be updated (man crypttab) or a bug causing the
change - but changing to use a non-zero timeout does now prompt for
password.


-- 
Gene
li...@sapience.com

[arch-general] New - systemd 234 - luks partition fails to ask for password

[Genes Lists via arch-general]

This has been working for years - starting on recent reboots systemd is
failing to ask for password for luks encrypted /home partition and boot
halts.

Fully updated from testing repos - when I reboot now, systemd no longer
asks for password to unlock luks partition. There is no hesitation at all and 
no password prompt at all. The boot runs through and gives an error that crypt 
set up failed. 

Root is not encrypted just /home. I'm then prompted to press Ctl D or
give root password and drop to single user mode - doing that then I can
manually do:

   cryptsetup open /dev/sdxx home

which prompts for password and succeeds

After I do above, then the error goes away evidenced by: 
   systemctl status systemd-cryptsetup@home.service

shows all is normal - exiting from single user 'repair' mode - then
boot continues and completes normally. And /home gets mounted via
/dev/mapper as normal

The issue is with latest systemd that I no longer get prompted for a
password for the luks encrypted partition.

Thoughts:
systemd password agents:
running systemd-ask-password by hand does indeed ask for password
in the console. 

/run/systemd/ask-password is empty directory.

the journal contains this:

systemd-cryptsetup[316]: Failed to query password: Timer expired
systemd[1]: Failed to start Cryptography Setup for home.
(Its possible that the bug is in systemd-cryptsetup in latest release?)

Versions:
# pacman -Q linux systemd

linux 4.12.1-2
systemd 234.0-2
cryptsetup 1.7.5-1

I googled but was no able to find any relevant bugs - checked systemd
github issues but found nothing similar.

thanks.





-- 
Gene
li...@sapience.com