You are not logged in.

#51 2022-05-29 14:11:55

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Yes, unfortunately there's nothing odd about that either.
The files are world-readable, so there should™ be no problem to access them.

pacman -Qikk glibc

And while idk how it could cause an EACCES

localectl

The root FS is ext4?

lsblk -f

I'm not sure that a re-installation would help (given you repeat all the steps that lead to this)
In doubt make sure to "sudo pacman -Syu" to not face some partial update.

Online

#52 2022-05-29 14:32:32

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Yes, unfortunately there's nothing odd about that either.
The files are world-readable, so there should™ be no problem to access them.

pacman -Qikk glibc

And while idk how it could cause an EACCES

localectl

The root FS is ext4?

lsblk -f

I'm not sure that a re-installation would help (given you repeat all the steps that lead to this)
In doubt make sure to "sudo pacman -Syu" to not face some partial update.

'pacman -Qikk glibc': http://ix.io/3YT3
'localectl':

Could not get properties: Failed to activate service 'org.freedesktop.locale1': timed out (service_start_timeout=25000ms)

Offline

#53 2022-05-29 14:43:42

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Could not get properties: Failed to activate service 'org.freedesktop.locale1': timed out (service_start_timeout=25000ms)

Wellwelllwelll…

ps fax
sudo journalctl -b
loginctl session-status # will probably fail as well

Online

#54 2022-05-30 13:42:18

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Could not get properties: Failed to activate service 'org.freedesktop.locale1': timed out (service_start_timeout=25000ms)

Wellwelllwelll…

ps fax
sudo journalctl -b
loginctl session-status # will probably fail as well

me likey the sound of that...
here:
'ps fax':http://ix.io/3YWY
'sudo journalctl -b':

May 30 19:02:53 Joker kernel: Linux version 5.15.43-1-lts (linux-lts@archlinux) (gcc (GCC) 12.1.0, GNU ld (GNU Binut>
May 30 19:02:53 Joker kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-linux-lts root=UUID=3722fc90-12bb-471c-9239-4b8>
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
May 30 19:02:53 Joker kernel: x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
May 30 19:02:53 Joker kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
May 30 19:02:53 Joker kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
May 30 19:02:53 Joker kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
May 30 19:02:53 Joker kernel: x86/fpu: xstate_offset[9]:  960, xstate_sizes[9]:    8
May 30 19:02:53 Joker kernel: x86/fpu: Enabled xstate features 0x21f, context size is 968 bytes, using 'compacted' f>
May 30 19:02:53 Joker kernel: signal: max sigframe size: 3632
May 30 19:02:53 Joker kernel: BIOS-provided physical RAM map:
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000053053fff] usable
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000053054000-0x0000000053054fff] ACPI NVS
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000053055000-0x0000000053055fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000053056000-0x0000000064824fff] usable
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064825000-0x0000000064a14fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a15000-0x0000000064a16fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a17000-0x0000000064a1afff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a1b000-0x0000000064a1bfff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a1c000-0x0000000064a1ffff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a20000-0x0000000064a20fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a21000-0x0000000064a25fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a26000-0x0000000064a26fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a27000-0x0000000064a2bfff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a2c000-0x0000000064a2efff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a2f000-0x0000000064a32fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a33000-0x0000000064a34fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a35000-0x0000000064a38fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a39000-0x0000000064a39fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a3a000-0x0000000064a3dfff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a3e000-0x0000000064a3ffff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a40000-0x0000000064a44fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a45000-0x0000000064a46fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a47000-0x0000000064a4bfff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a4c000-0x0000000064a4efff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a4f000-0x0000000064a53fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a54000-0x0000000064a6afff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a6b000-0x0000000064a8dfff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a8e000-0x0000000064a8efff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a8f000-0x0000000064a92fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a93000-0x0000000064a93fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a94000-0x0000000064a98fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a99000-0x0000000064a99fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a9a000-0x0000000064a9efff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064a9f000-0x0000000064a9ffff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064aa0000-0x0000000064aa3fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064aa4000-0x0000000064aa5fff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064aa6000-0x0000000064aaafff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064aab000-0x0000000064aacfff] type 20
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000064aad000-0x00000000678b3fff] reserved
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x00000000678b4000-0x0000000067f23fff] ACPI NVS
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000067f24000-0x0000000067ffdfff] ACPI data
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000067ffe000-0x0000000067ffefff] usable
May 30 19:02:53 Joker kernel: BIOS-e820: [mem 0x0000000067fff000-0x000000006f7fffff] reserved

'loginctl session-status': http://ix.io/3YX2

Offline

#55 2022-05-30 14:01:05

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

That's only the head of the journal, try

sudo journalctl -b | curl -F 'file=@-' 0x0.st

logind responds, so it's only about the systemd-localed (activation)
Can you

sudo /usr/lib/systemd/systemd-localed

and then check "localectl" (from a different terminal, in the best of all cases the previous command will just keep running w/o any output)

Online

#56 2022-05-30 14:15:01

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

That's only the head of the journal, try

sudo journalctl -b | curl -F 'file=@-' 0x0.st

logind responds, so it's only about the systemd-localed (activation)
Can you

sudo /usr/lib/systemd/systemd-localed

and then check "localectl" (from a different terminal, in the best of all cases the previous command will just keep running w/o any output)

here:
'sudo journalctl -b | curl -F 'file=@-' 0x0.st': http://0x0.st/oBL5.txt

and yes 'sudo /usr/lib/systemd/systemd-localed' it just keeps running for sometime

Offline

#57 2022-05-31 14:20:15

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

So these two fail

May 30 19:03:20 Joker dbus-daemon[478]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms)
…
May 30 19:03:35 Joker dbus-daemon[478]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out (service_start_timeout=25000ms)

and we get

May 30 19:02:55 Joker systemd-hostnamed[516]: /usr/lib/systemd/systemd-hostnamed: error while loading shared libraries: libsystemd-shared-251.1-1.so: cannot open shared object file: Permission denied
ldd /usr/lib/systemd/systemd-hostnamed
stat /usr/lib/systemd/libsystemd-shared-251.1-1.so

Online

#58 2022-06-02 13:19:59

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

So these two fail

May 30 19:03:20 Joker dbus-daemon[478]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms)
…
May 30 19:03:35 Joker dbus-daemon[478]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out (service_start_timeout=25000ms)

and we get

May 30 19:02:55 Joker systemd-hostnamed[516]: /usr/lib/systemd/systemd-hostnamed: error while loading shared libraries: libsystemd-shared-251.1-1.so: cannot open shared object file: Permission denied
ldd /usr/lib/systemd/systemd-hostnamed
stat /usr/lib/systemd/libsystemd-shared-251.1-1.so

'ldd /usr/lib/systemd/systemd-hostnamed': http://ix.io/3Zbq
'stat /usr/lib/systemd/libsystemd-shared-251.1-1.so': http://ix.io/3Zbr

sorry for late reply, i was busy with college

Offline

#59 2022-06-02 14:21:27

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Same situation: the correct file gets resolved and is world-readable, yet you get access denied.
I assume you can't "hostnamectl" but have no issues to "sudo /usr/lib/systemd/systemd-hostnamed"?
Can you "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" ?

Something  is rotten in the state of … dbus

Online

#60 2022-06-03 03:45:07

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Same situation: the correct file gets resolved and is world-readable, yet you get access denied.
I assume you can't "hostnamectl" but have no issues to "sudo /usr/lib/systemd/systemd-hostnamed"?
Can you "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" ?

Something  is rotten in the state of … dbus

'sudo -u dbus /usr/lib/systemd/systemd-hostnamedl':

Failed to run event loop: Transport endpoint is not connected

'hostnamectl':

Failed to query system properties: Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms)

Offline

#61 2022-06-03 14:14:09

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Failed to run event loop: Transport endpoint is not connected

That only shows up after a looong while?
When  you run "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" and while it "hangs" call "hostnamectl", does it respond?

Online

#62 2022-06-04 08:25:39

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Failed to run event loop: Transport endpoint is not connected

That only shows up after a looong while?
When  you run "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" and while it "hangs" call "hostnamectl", does it respond?

yes it shows up after a while, and when i try to run one after the other like you said, it shows the same output/errors

Offline

#63 2022-06-04 14:48:37

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

???
The idea is to run "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" and while it's running (*before* it says "Failed to run event loop: Transport endpoint is not connected") to run "hostnamectl".
hostnamectl wants to talk to systemd-hostnamed and is supposed to and tries to start it (but that gets you a freakish "libsystemd-shared-251.1-1.so: cannot open shared object file: Permission denied")

If you can run "hostnamectl" against a running systemd-hostnamed but not having hostnamectl start systemd-hostnamed, there's something™ severely broken w/ the dbus activation process.

Online

#64 2022-06-05 07:53:56

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

???
The idea is to run "sudo -u dbus /usr/lib/systemd/systemd-hostnamed" and while it's running (*before* it says "Failed to run event loop: Transport endpoint is not connected") to run "hostnamectl".

that is exactly what i did but i think something is broken like you said in the last sentence

Offline

#65 2022-06-06 06:53:04

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

And what was the output of "hostnamectl" at this point?

Online

#66 2022-06-06 13:14:43

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

And what was the output of "hostnamectl" at this point?

its the same error as before

Offline

#67 2022-06-06 13:19:30

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Wich error? The timeout?
Please don't paraphrase - it makes things much harder when I have to guess all the time what you're seeing.

Online

#68 2022-06-06 13:48:33

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Wich error? The timeout?
Please don't paraphrase - it makes things much harder when I have to guess all the time what you're seeing.

this error:

Failed to query system properties: Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms)

Offline

#69 2022-06-06 14:14:02

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

Does "hostnameclt" work while "sudo /usr/lib/systemd/systemd-hostnamed" is waiting for a query?

Online

#70 2022-06-07 13:10:12

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

Does "hostnameclt" work while "sudo /usr/lib/systemd/systemd-hostnamed" is waiting for a query?

i gave you the same thing, while 'sudo -u dbus /usr/lib/systemd/systemd-hostnamed' is waiting for query, 'hostnamectl' gives the above error. btw what is a 'successful' output for both the commands?

Last edited by kashishme (2022-06-07 13:11:10)

Offline

#71 2022-06-07 13:25:24

seth
Member
Registered: 2012-09-03
Posts: 29,765

Re: Printer not getting connected due to some issue in avahi

I'm not sure what you're sayinghere, but nb. that there's a significant difference beween "sudo -u dbus …" and "sudo …" (the latter one is equivalent to "sudo -u root")
hostnamectl prints your hostname, some machine ID etc - the output iself is less important than the fact that it doesn't work.

Online

#72 2022-06-07 13:41:10

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

seth wrote:

I'm not sure what you're sayinghere, but nb. that there's a significant difference beween "sudo -u dbus …" and "sudo …" (the latter one is equivalent to "sudo -u root")
hostnamectl prints your hostname, some machine ID etc - the output iself is less important than the fact that it doesn't work.

oh sorry, i tried it without '-u dbus' and here is the output:

 Static hostname: Joker
       Icon name: computer
      Machine ID: a83851bcc36b450282a40a8421ceee
         Boot ID: 6d82bad2a90b456eb98e5e5bc84e78
Operating System: Arch Linux                      
          Kernel: Linux 5.15.44-1-lts
    Architecture: x86-64
 Hardware Vendor: Dell Inc.
  Hardware Model: G3 3500
Firmware Version: 1.9.0

Offline

#73 2022-06-07 14:17:53

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

so this hostnamectl works, what do we do now?

Offline

#74 2022-06-11 13:02:10

kashishme
Member
Registered: 2021-01-08
Posts: 155

Re: Printer not getting connected due to some issue in avahi

@seth ?

Last edited by kashishme (2022-06-11 13:02:25)

Offline

#75 2022-06-11 13:23:11

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 3,963

Re: Printer not getting connected due to some issue in avahi


How to post. A sincere effort to use modest and proper language and grammar is a sign of respect toward the community.

Offline

Board footer

Powered by FluxBB