Gdbus error org freedesktop policykit1 error failed user of caller and user of subject differs - Исправление ошибок и поиск оптимальных решений проблем

November 19, 2013
How to, Kali Linux, Linux

This is a small guide on How to fix GDBus Error org freedesktop PolicyKit1 Error Failed : An authentication agent already exists for the given subject error in Kali, LMDE or Debian Linux.

How to fix GDBus Error org freedesktop PolicyKit1 Error Failed

Background:

I use gdm3+XFCE on my box (amd64, Kali Linux). When I start my XFCE session, I have been getting this error message

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subject

Even starting a new XFCE session will not help. So far, it looks that this error message has no consequences, but it is annoying. I found a way to fix this, sharing for interested readers.

Screenshots were taken from Kali Linux

root@kali:~# lsb_release -a
No LSB modules are available.
Distributor ID:    Debian
Description:    Debian GNU/Linux Kali Linux 1.0
Release:    Kali Linux 1.0
Codename:    n/a
root@kali:~#

I am using XFCE desktop/window manager.

To fix this go to Application Menu > Settings > Session and Startup >

Now un-check LXPolkit from Application Autostart tab. Click on Close.

That’s it, you won’t see that error message again.

Conclusion

GDBus Error org freedesktop PolicyKit1 Error Failed is a common issue in many Linux Operating systems which is not just limited to Kali Linux or Debian Linux.

GDbus Error org openobex Error Failed: Unable to request session problem
Problem installing .deb files on Wheezy
gnome-shell:oh no something has gone wrong error
Bug 657006 – GDBus Error org freedesktop PolicyKit1 Error Failed: An authentication agent already exists for the given subject
Raspberry Pi error
GDBus Error org freedesktop PolicyKit1 Error Failed An authentication agent already exists for the given subject
GDBus Error org openobex Error Failed Unable to request session
Error GDBus Error org freedesktop DBus Error Spawn ExecFailed: Failed to execute program /usr/lib/dbus-1.0/dbus-daemon-launch-helper: Success
MATE-Desktop for fedora
Bug#687844: debian-policy: GDBus Error org freedesktop PolicyKit1 Error Failed:
Installing Nessus in Kali Linux
I am kali linx user i hv some problm when i install any type of software app in my kali linux this error show GDBus Error org gtk GDBus Un?
GDBus Error org gtk GDBus UnmappedGError Quark._pk_5ftransaction_5ferror.Code4: SimulateInstallFiles not supported by backend
Debian Bug report logs – #703016 policykit-1-gnome: polkit-gnome-authentication-agent-1 fails to start
Small problem with the version of Mate ..

I cannot say if my fix will apply to every situation, but it seems to work for me and my friends.

Thanks for reading. Please share.

Check Also

Cracking password in Kali Linux using John the Ripper

John the Ripper is a free password cracking software tool. Initially developed for the Unix …

Источник

Hi!

Just installed a fresh copy of Archlinux. Xorg has been configured with the nouveau driver and is running fine with openbox and i3.

I installed gnome including every package from the gnome and gnome-extra groups.

I’m starting gnome using the following in my .xinitc (copied from skeleton)

Upon startup, I am immediately greeted by a Oh no! Something has gone wrong. message.

Here’s the full stdout/stderr output from gnome-session:

libGL error: failed to load driver: nouveau
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
GNOME_KEYRING_CONTROL=/home/MYUSER/.cache/keyring-Pzuvga
GNOME_KEYRING_PID=6917
GNOME_KEYRING_CONTROL=/home/MYUSER/.cache/keyring-Pzuvga
GNOME_KEYRING_CONTROL=/home/MYUSER/.cache/keyring-Pzuvga
GPG_AGENT_INFO=/home/MYUSER/.cache/keyring-Pzuvga/gpg:0:1
GNOME_KEYRING_CONTROL=/home/MYUSER/.cache/keyring-Pzuvga
GPG_AGENT_INFO=/home/MYUSER/.cache/keyring-Pzuvga/gpg:0:1
SSH_AUTH_SOCK=/home/MYUSER/.cache/keyring-Pzuvga/ssh
Connection failure: Connection refused
pa_context_connect() failed: Connection refused

(gnome-settings-daemon:6908): power-plugin-WARNING **: Unable to inhibit suspend: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.0" (uid=0 pid=327 comm="/usr/lib/systemd/systemd-logind ") interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" error name="(unset)" requested_reply="0" destination="org.freedesktop.PolicyKit1" (uid=102 pid=6154 comm="/usr/lib/polkit-1/polkitd --no-debug ")

(gnome-settings-daemon:6908): power-plugin-WARNING **: Unable to inhibit lid switch: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.0" (uid=0 pid=327 comm="/usr/lib/systemd/systemd-logind ") interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" error name="(unset)" requested_reply="0" destination="org.freedesktop.PolicyKit1" (uid=102 pid=6154 comm="/usr/lib/polkit-1/polkitd --no-debug ")

(gnome-settings-daemon:6908): media-keys-plugin-WARNING **: Unable to inhibit keypresses: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 1 matched rules; type="method_call", sender=":1.0" (uid=0 pid=327 comm="/usr/lib/systemd/systemd-logind ") interface="org.freedesktop.PolicyKit1.Authority" member="CheckAuthorization" error name="(unset)" requested_reply="0" destination="org.freedesktop.PolicyKit1" (uid=102 pid=6154 comm="/usr/lib/polkit-1/polkitd --no-debug ")

(gnome-settings-daemon:6908): color-plugin-WARNING **: failed to create device: GDBus.Error:org.freedesktop.ColorManager.Failed: failed to obtain org.freedesktop.color-manager.create-device auth
libGL error: failed to load driver: nouveau
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
Initializing tracker-store...
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/home/MYUSER/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/MYUSER/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/MYUSER/.local/share/tracker/tracker-store.log'
Tracker-Message: Setting up monitor for changes to config file:'/home/MYUSER/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/MYUSER/.local/share/tracker/tracker-miner-fs.log'
Failed to play sound: File or data not found

** (nm-applet:6963): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
** Message: applet now removed from the notification area

** (nm-applet:6963): WARNING **: fetch_connections_done: error fetching connections: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details..

** (nm-applet:6963): WARNING **: Failed to register as an agent: (32) Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
      JS LOG: Error: Requiring IBus, version none: Typelib file for namespace 'IBus' (any version) not found
Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
    JS ERROR: !!!   Exception was: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
    JS ERROR: !!!     message = '"GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs."'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/components/polkitAgent.js"'
    JS ERROR: !!!     lineNumber = '329'
    JS ERROR: !!!     stack = '"0 anonymous()@/usr/share/gnome-shell/js/ui/components/polkitAgent.js:329
1 wrapper()@/usr/share/gjs-1.0/lang.js:204
2 anonymous("name" = ""polkitAgent"")@/usr/share/gnome-shell/js/ui/components/__init__.js:56
3 wrapper(""polkitAgent"")@/usr/share/gjs-1.0/lang.js:204
4 anonymous("name" = ""polkitAgent"", 1, [object Array])@/usr/share/gnome-shell/js/ui/components/__init__.js:22
5 anonymous()@/usr/share/gnome-shell/js/ui/components/__init__.js:21
6 wrapper()@/usr/share/gjs-1.0/lang.js:204
7 anonymous()@/usr/share/gnome-shell/js/ui/components/__init__.js:13
8 wrapper()@/usr/share/gjs-1.0/lang.js:204
9 anonymous()@/usr/share/gjs-1.0/lang.js:145
10 anonymous()@/usr/share/gjs-1.0/lang.js:239
11 start()@/usr/share/gnome-shell/js/ui/main.js:150
12 <TOP LEVEL>@<main>:1
"'
Window manager warning: Log level 32: Execution of main.js threw exception: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
libGL error: failed to load driver: nouveau
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
      JS LOG: Error: Requiring IBus, version none: Typelib file for namespace 'IBus' (any version) not found

** (gnome-screensaver:7041): WARNING **: screensaver already running in this session
Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Unit dbus-org.freedesktop.NetworkManager.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.NetworkManager.service' for details.
Window manager warning: Log level 16: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
    JS ERROR: !!!   Exception was: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
    JS ERROR: !!!     message = '"GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs."'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/components/polkitAgent.js"'
    JS ERROR: !!!     lineNumber = '329'
    JS ERROR: !!!     stack = '"0 anonymous()@/usr/share/gnome-shell/js/ui/components/polkitAgent.js:329
1 wrapper()@/usr/share/gjs-1.0/lang.js:204
2 anonymous("name" = ""polkitAgent"")@/usr/share/gnome-shell/js/ui/components/__init__.js:56
3 wrapper(""polkitAgent"")@/usr/share/gjs-1.0/lang.js:204
4 anonymous("name" = ""polkitAgent"", 1, [object Array])@/usr/share/gnome-shell/js/ui/components/__init__.js:22
5 anonymous()@/usr/share/gnome-shell/js/ui/components/__init__.js:21
6 wrapper()@/usr/share/gjs-1.0/lang.js:204
7 anonymous()@/usr/share/gnome-shell/js/ui/components/__init__.js:13
8 wrapper()@/usr/share/gjs-1.0/lang.js:204
9 anonymous()@/usr/share/gjs-1.0/lang.js:145
10 anonymous()@/usr/share/gjs-1.0/lang.js:239
11 start()@/usr/share/gnome-shell/js/ui/main.js:150
12 <TOP LEVEL>@<main>:1
"'
Window manager warning: Log level 32: Execution of main.js threw exception: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
gnome-session[6852]: WARNING: App 'gnome-shell.desktop' respawning too quickly

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed

(gnome-settings-daemon:6908): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
gnome-session[6852]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed
gnome-session[6852]: Gtk-CRITICAL: gtk_main_quit: assertion `main_loops != NULL' failed

Received signal:1->'Hangup'
Received signal:1->'Hangup'
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Terminated'

(tracker-miner-fs:6959): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed

(tracker-miner-fs:6959): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.

Received signal:15->'Terminated'
(tracker-miner-fs:6959): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed

OK


OK

I googled some of the warnings and errors from that log and couldn’t find anything relevant. Some post led me to check my dbus service and here’s what systemctl has to say:

]$ systemctl status dbus-org
dbus-org.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)

Not sure where to go from there. This is a very fresh Arch install.

Any ideas?

Thanks!

Last edited by Cron0 (2013-01-18 03:53:01)

Источник

# 9 лет, 1 месяц назад
Темы: 292 Сообщения: 1960 Участник с: 20 ноября 2013	Вот полный текст сообщения GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subjec Когда закрываю вроде всё работает нормально.После перезагрузки опять появляется.Никаких программ не устанавливал и не удалял.Никаких флешек или чего другого не подключал. Как эту заразу убрать,никто не знает? Система Openbox Linux Forever!

#
9 лет, 1 месяц назад

Темы:

292

Сообщения:

1960

Участник с: 20 ноября 2013

Вот полный текст сообщения

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exists for the given subjec

Когда закрываю вроде всё работает нормально.После перезагрузки опять появляется.Никаких программ не устанавливал и не удалял.Никаких флешек или чего другого не подключал.
Как эту заразу убрать,никто не знает?
Система Openbox

Linux Forever!

vasek	# 9 лет, 1 месяц назад
Темы: 47 Сообщения: 11417 Участник с: 17 февраля 2013	Легко гуглится, например это, где приведена также ссылка на багтрекер редхата. Если не поможет, погугли еще — имеются и другие решения. Ошибки не исчезают с опытом — они просто умнеют

vasek

#
9 лет, 1 месяц назад

Темы:

Сообщения:

11417

Участник с: 17 февраля 2013

Легко гуглится, например это, где приведена также ссылка на багтрекер редхата.
Если не поможет, погугли еще — имеются и другие решения.

Ошибки не исчезают с опытом — они просто умнеют

Vadim	# 9 лет, 1 месяц назад
Темы: 292 Сообщения: 1960 Участник с: 20 ноября 2013	Разобрался,получился с двух мест пытался запустится lxpolkit ,из /etc/xdg/autostart и из ~/.config/openbox/autostart ,сюда я сам написал автостарт lxpolkit и забыл,и получался конфликт. Из ~/.config/openbox/autostart убрал строчку lxpolkit и весь вопрос исчерпан, Почему до последнего обновления не было конфликта не знаю. Linux Forever!

Vadim

#
9 лет, 1 месяц назад

Темы:

292

Сообщения:

1960

Участник с: 20 ноября 2013

Разобрался,получился с двух мест пытался запустится lxpolkit ,из
/etc/xdg/autostart
и из ~/.config/openbox/autostart ,сюда я сам написал автостарт lxpolkit и забыл,и получался конфликт.
Из ~/.config/openbox/autostart убрал строчку lxpolkit и весь вопрос исчерпан,
Почему до последнего обновления не было конфликта не знаю.

Linux Forever!

Zzz	# 12 месяцев назад
Темы: 0 Сообщения: 16 Участник с: 08 декабря 2021	вапчхе беда GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exist for the given subject ## polkit agent if [[ ! `pidof xfce-polkit` ]]; then /usr/lib/xfce-polkit/xfce-polkit & fi

Zzz

#
12 месяцев назад

Темы:

Сообщения:

Участник с: 08 декабря 2021

вапчхе беда
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: An authentication agent already exist for the given subject

## polkit agent
if [[ ! `pidof xfce-polkit` ]]; then
    /usr/lib/xfce-polkit/xfce-polkit &
fi

vs220	# 12 месяцев назад
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	Zzz некропостинг не очень приветствуется. И уточните где именно прописан запуск полкит агента и собственно зачем?

Zzz	# 12 месяцев назад (отредактировано 12 месяцев назад)
Темы: 0 Сообщения: 16 Участник с: 08 декабря 2021	vs220 Zzz некропостинг не очень приветствуется. И уточните где именно прописан запуск полкит агента и собственно зачем? аа, я чёт… собстно говоря, стала появляться ошибка при запуске agent XFCE PolicyKit img /home/admin/.config/openbox/autostart не могу ладу дать, что бы её убрать

Zzz

#
12 месяцев назад

(отредактировано

12 месяцев назад)

Темы:

Сообщения:

Участник с: 08 декабря 2021

vs220
Zzz некропостинг не очень приветствуется.
И уточните где именно прописан запуск полкит агента и собственно зачем?

аа, я чёт…
собстно говоря, стала появляться ошибка при запуске agent XFCE PolicyKit
img
/home/admin/.config/openbox/autostart
не могу ладу дать, что бы её убрать

vs220	# 12 месяцев назад
Темы: 22 Сообщения: 8090 Участник с: 16 августа 2009	Zzz home/admin/.config/openbox/autostart Уберите его от туда, он из /etc/xdg/autostart/xfce-polkit.desktop и так запускается

vs220

#
12 месяцев назад

Темы:

Сообщения:

8090

Участник с: 16 августа 2009

Zzz
home/admin/.config/openbox/autostart

Уберите его от туда, он из /etc/xdg/autostart/xfce-polkit.desktop и так запускается

Zzz	# 12 месяцев назад (отредактировано 12 месяцев назад)
Темы: 0 Сообщения: 16 Участник с: 08 декабря 2021	vs220 Zzz home/admin/.config/openbox/autostart Уберите его от туда, он из /etc/xdg/autostart/xfce-polkit.desktop и так запускается ## polkit agent ##if [[ ! `pidof xfce-polkit` ]]; then /usr/lib/xfce-polkit/xfce-polkit & fi тогда неичего на рабочем столе не отображается вернее всё так же и остаётся.. опа… Благодарю!!! всю строку удалил и пропала ошибка. А до этого производил эти все манипуляции и ничего не помогало….

Zzz

#
12 месяцев назад

(отредактировано

12 месяцев назад)

Темы:

Сообщения:

Участник с: 08 декабря 2021

vs220

Zzz
home/admin/.config/openbox/autostart

Уберите его от туда, он из /etc/xdg/autostart/xfce-polkit.desktop и так запускается

## polkit agent
##if [[ ! `pidof xfce-polkit` ]]; then
/usr/lib/xfce-polkit/xfce-polkit &
fi

тогда неичего на рабочем столе не отображается
вернее всё так же и остаётся..
опа…
Благодарю!!!
всю строку удалил и пропала ошибка.
А до этого производил эти все манипуляции и ничего не помогало….

vadik	# 11 месяцев, 4 недели назад
Темы: 55 Сообщения: 5410 Участник с: 17 августа 2009	Вопросы решены. Тему закрываю и напоминаю, некропостинг — зло!

Источник

View previous topic :: View next topic

Author

Message

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Mon Aug 10, 2020 1:10 pm Post subject: cannot start desktop with sddm (solved)

I have installed Xorg-server, sddm, plasma-desktop, twm and xterm. But I cannot get any of those running someting usable.

1: I log in as my regular user.

— if I want to start sddm I get

Code:

user@desktop ~$ sddm

[14:42:04.819] (II) DEAMON: Initializing…

[14:42:04.824] (II) DEAMON: Starting…

[14:42:04.824] (II) DEAMON: Logind interface found…

[14:42:04.825] (II) DEAMON: Adding new display on vt7 …

[14:42:04.826] (II) DEAMON: Loading theme configuration from «»

[14:42:04.826] (II) DEAMON: Display server starting…

[14:42:04.826] (II) DEAMON: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{d4583f19-3cd6-4df9-8f9b31ed4a54} -background none -noreset -displayfd 16 -seat seat0 vt7

[14:42:04.861] (II) DEAMON: Failed to read display number from pipe

[14:42:04.861] (II) DEAMON: Display server failed to start. Exiting

Aborted

user@desktop ~$

2: if I log in as my regular user and run

Code:

user@desktop ~$startx /usr/bin.twm

I get a black screen. But if I click on the left mouse button I get a drop down menu, I can choose Xterm and it opens and runs. So I take it that X can run and do something useful. Only after I close Xterm do I get a mouse cursor.

3: if I login as root and then

Code:

desktop ~ # sddm

Then SDDM starts and displays the graphical login for my user. If I next give the user password I briefly see the plasma logo and then I get dropped into the terminal with a blinking _. But I cannot type anything, alt-ctrl-backspace does not work. Only way to get out of it is a second terminal and reboot.

If I go into the /home/user/.local/share/sddm/xorg-session.log I see:

Code:

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

cannot convert KDE_FULL_SESSION argument to STRING or COMPOUND_TEXT.

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

kdeinit5: preparing to launch ‘/usr/lib64/libexec/kf5/klauncher’

kdeinit5: Launched KLauncher, pid = 2813, result = 0

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

kdeinit5: opened connection to :0

kdeinit5: preparing to launch ‘libkdeinit5_kded5’

Could not open kded5 using a library: Cannot load library libkdeinit5_kded5: (libkdeinit5_kded5: cannot open shared object file: No such file or directory)

kdeinit5: Launched KDED, pid = 2816 result = 0

kdeinit5: preparing to launch ‘libkdeinit5_kcminit_startup’

kdeinit5: Launched ‘kcminit_startup’, pid = 2817 result = 0

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

Initializing «kcm_style» : «kcminit_style»

kdeinit5: Got SETENV ‘GTK_RC_FILES=/etc/gtk/gtkrc:/home/ikke/.gtkrc:/home/ikke/.config/gtkrc’ from launcher.

kdeinit5: Got SETENV ‘GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/ikke/.gtkrc-2.0:/home/ikke/.config/gtkrc-2.0’ from launcher.

Initializing «kcm_mouse» : «kcminit_mouse»

Initializing «kcm_access» : «kcminit_access»

kdeinit5: Got EXEC_NEW ‘/usr/bin/kaccess’ from launcher.

kdeinit5: preparing to launch ‘/usr/bin/kaccess’

kdeinit5: PID 2817 terminated.

Xlib XKB extension major= 1 minor= 0

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

X server XKB extension major= 1 minor= 0

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

Qt: Session management error: networkIdsList argument is NULL

Configuring Lock Action

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

kdeinit5: Got SETENV ‘SESSION_MANAGER=local/desktop:@/tmp/.ICE-unix/2887,unix/desktop:/tmp/.ICE-unix/2887’ from launcher.

kcm_touchpad: Using X11 backend

Initializing «kded_touchpad» : «kcminit_touchpad»

kcm_touchpad: Using X11 backend

org.kde.plasma.session: Starting autostart service «/etc/xdg/autostart/org.kde.plasmashell.desktop» («/usr/bin/plasmashell»)

org.kde.plasma.session: Starting autostart service «/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop» («/usr/lib64/libexec/polkit-kde-authentication-agent-1»)

QDBusConnection: name ‘org.kde.kglobalaccel’ had owner » but we thought it was ‘:1.11’

Session path: «/org/freedesktop/login1/session/_32»

QDBusConnection: name ‘org.kde.kglobalaccel’ had owner » but we thought it was ‘:1.11’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

New PolkitAgentListener 0x560038705ca0

Adding new listener PolkitQt1::Agent::Listener(0x560038722740) for 0x560038705ca0

Listener online

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

kwin_xkbcommon: XKB: couldn’t find a Compose file for locale «C.utf8»

«Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.»

Authentication agent result: false

Couldn’t register listener!

org.kde.plasma.session: Starting autostart service «/etc/xdg/autostart/gmenudbusmenuproxy.desktop» («/usr/bin/gmenudbusmenuproxy»)

org.kde.plasmaquick: Applet preload policy set to 1

kf5.kpackage: No metadata file in the package, expected it at: «/usr/share/wallpapers/Next/contents/images/»

kf5.kpackage: No metadata file in the package, expected it at: «/usr/share/wallpapers/Next/contents/images/»

kf5.kpackage: No metadata file in the package, expected it at: «/usr/share/wallpapers/Next/contents/images/»

file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList

file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int

file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:75:9: Unable to assign [undefined] to int

file:///usr/share/plasma/wallpapers/org.kde.image/contents/ui/main.qml:76:9: Unable to assign [undefined] to QStringList

qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 896, resource id: 41943053, major code: 3 (GetWindowAttributes), minor code: 0

qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 897, resource id: 41943053, major code: 14 (GetGeometry), minor code: 0

trying to show an empty dialog

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

kdeinit5: Got EXEC_NEW ‘/usr/lib64/qt5/plugins/kf5/kio/file.so’ from launcher.

kdeinit5: preparing to launch ‘/usr/lib64/qt5/plugins/kf5/kio/file.so’

lock called

Lock window Id: 27262983

CreateNotify: 27262983

CreateNotify: 27262985

CreateNotify: 35651588

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-ikke’

Qt: Session management error: networkIdsList argument is NULL

So a regular user cannot start sddm and sddm cannot launch a desktop if the one that starts sddm (root) is not the one the user the desktop is started for. And you cannot start a desktop for root. A bit of a catch-22 I think.
_________________
Expert in non-working solutions

Last edited by Spanik on Wed Aug 12, 2020 8:06 am; edited 1 time in total

account
n00b
n00b

Joined: 02 Sep 2009
Posts: 10

Posted: Mon Aug 10, 2020 6:06 pm Post subject:

That’s not how you should start your DE. See instructions here: https://wiki.gentoo.org/wiki/SDDM#Service

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Mon Aug 10, 2020 6:55 pm Post subject:

But that way it starts automatically at boot! Now as I run into trouble after each emerge —update @world because something changed with plasma/python/perl/poppler or some other small thing, this means that each time after an update I need to boot back into a CD, change it back to boot in runlevel 3 , get it back working and then change it back to auto? There must be a way to start sddm after boot and them log in as a normal user? _________________ Expert in non-working solutions

asturm
Developer

Joined: 05 Apr 2007
Posts: 8767
Location: Austria

Posted: Mon Aug 10, 2020 6:58 pm Post subject:

Why would you want to log into your user only to start sddm and… log into your user again? _________________ backend.cpp:92:2: warning: #warning TODO — this error message is about as useful as a cooling unit in the arctic

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Tue Aug 11, 2020 8:11 am Post subject:

Because whenever I do an update @world it completely breaks. And then you cannot log in because no way to get into a terminal unless you boot the live cd, change it so sddm doesn’t start automatically, get it working again, change it back to automatically, boot again only to find it still doesn’t work and so on. Whenever a single component of plasma changes the updates mess everything up. I have had days of troubles after a poppler update, complete reintalls after something of python or perl changes. I don’t use systemd but after every tiny change of it the updates break the system. With Plasma circular dependencies where one component depends on version X but it doesn’t emerge the dependency because component Y needs another incompatible version of it are the norm after updates. And certainly with a new install. I just log into a root terminal and emerge all the applications I need/want. What is the use of logging into your user if whatever you need to do, you need sudo or su root when emerging? So I prefer by far to boot into a root terminal (maybe do some needed maintenance stuff) and then start my user. OK, this might be against some rules, but this is a personal desktop, not a production server. I know, then why use Plasma? Can’t help it, but other desktops just don’t allow the configuration to get them working how I prefer. _________________ Expert in non-working solutions

account
n00b
n00b

Joined: 02 Sep 2009
Posts: 10

Posted: Tue Aug 11, 2020 9:39 am Post subject:

You can remove sddm from default runlevel before doing @world update. On reboot you will get your text console login, you can fix stuff and do whatever you want, and once everything works you can add sddm back to default runlevel.

As mentioned on the wiki page it is very easy to start sddm manually

Code:

rc-service sddm start

However, from the way you describe how everything breaks when you do an update is suspect there might be some misconfiguration with your system. Normally it does not happen that a @world update breaks stuff to the degree that you don’t get a working DE and you are forced to fix things in text console.

asturm
Developer

Joined: 05 Apr 2007
Posts: 8767
Location: Austria

Posted: Tue Aug 11, 2020 9:51 am Post subject:

Spanik wrote:

With Plasma circular dependencies where one component depends on version X but it doesn’t emerge the dependency because component Y needs another incompatible version of it are the norm after updates.

Sounds like you have a mess with package.accept_keywords.
_________________
backend.cpp:92:2: warning: #warning TODO — this error message is about as useful as a cooling unit in the arctic

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Tue Aug 11, 2020 10:24 am Post subject:

Could be, but that doesn’t help me now does it? So, how can I log into a root terminal and then start the desktop as my regular user? _________________ Expert in non-working solutions

pietinger
Moderator

Joined: 17 Oct 2006
Posts: 2401
Location: Bavaria

Posted: Tue Aug 11, 2020 10:36 am Post subject:

If you think about the future, what would be better: Making your system clean and having no problems with any world-updates, or finding a specific solution now which will break after your next emerge world ?

If you want help for the first solution post these infos:

Code:

more /etc/portage/make.conf

emerge —info

eselect profile show

asturm
Developer

Joined: 05 Apr 2007
Posts: 8767
Location: Austria

Posted: Tue Aug 11, 2020 10:40 am Post subject:

Spanik wrote:

So, how can I log into a root terminal and then start the desktop as my regular user?

No, you log into your regular user and start your desktop directly.

Gentoo KDE Wiki to the rescue: https://wiki.gentoo.org/wiki/KDE/de#No_display_manager
_________________
backend.cpp:92:2: warning: #warning TODO — this error message is about as useful as a cooling unit in the arctic

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Tue Aug 11, 2020 11:12 am Post subject:

asturm wrote:

Spanik wrote:

So, how can I log into a root terminal and then start the desktop as my regular user?

No, you log into your regular user and start your desktop directly.

Gentoo KDE Wiki to the rescue: https://wiki.gentoo.org/wiki/KDE/de#No_display_manager

Thanks, this seems to work. I can log in as a regular user and start Plasma. But after looking around I don’t know if I’m going to keep that sluggish thing. Goodness me is that like wading in treacle.
_________________
Expert in non-working solutions

asturm
Developer

Joined: 05 Apr 2007
Posts: 8767
Location: Austria

Posted: Tue Aug 11, 2020 11:30 am Post subject:

If it is sluggish, then you have a problem. It is obviously not normal. But that’s not very specific. _________________ backend.cpp:92:2: warning: #warning TODO — this error message is about as useful as a cooling unit in the arctic

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Tue Aug 11, 2020 1:21 pm Post subject:

asturm wrote:

If it is sluggish, then you have a problem. It is obviously not normal. But that’s not very specific.

It is hard to compare and I do not have it yet configured as I like. So a lof off things like animations, tooltips, previews etc are still on. Also not yet configured the mouse and keyboard.

This latest is something very annoying in Linux: no system wide setting for keyboard layout, num lock, mouse (left-right swap, focus, acceleration…). So I have it now that in the terminals I do have the correct keyboard layout but start X and it is all gone.

I’ll plod on. But for now I can continue. Thanks!
_________________
Expert in non-working solutions

Spanik
l33t
l33t

Joined: 12 Dec 2003
Posts: 813
Location: Belgium

Posted: Wed Aug 12, 2020 8:05 am Post subject:

Ok, more or less solved. A bit inconvenient at times but good enough. Thanks for the help. _________________ Expert in non-working solutions

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

I’ve had this problem for some weeks and I’m unable to fix it. I would be grateful if someone can come up with a solution. Running XFCE on Debian testing/sid; I’m unable to run any task that requires policykit (eg. mounting disks from the file manager, creating partitions from gnome-disks, running programs with pkexec, etc).

I can see from the process list that /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 is not running (which it should, since it is marked for autostart in /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop, I can verify in my desktop autostart settings and in the .desktop itself that it is supposed to be running.)

Running /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 manually during my desktop session also fails with the following error.

$ /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1

** (polkit-gnome-authentication-agent-1:28852): WARNING **: Unable to register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.
Cannot register authentication agent: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: User of caller and user of subject differs.

The error I get when using pkexec:

$ pkexec gnome-disks
==== AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/gnome-disks' as the super user
Authenticating as: ,,, (user)
Password: 
polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
==== AUTHENTICATION FAILED ===
Error executing command as another user: Not authorized

This incident has been reported.

Error I get when trying to mount drives in Thunar

Not authorized to perform operation.

Error I get when trying to perform operations on partitions in my disk utility:

Not authorized to perform operation (udisks-error-quark, 4)

So… what is the next step? What should I look into? I’d report a bug but have no idea if 1. it’s actually a software bug and not a configuration error (my config is mostly vanilla debian, pretty sure I didn’t touch policykit) 2. against what package to report it.

The desktop session is started through lightdm and xfce4-session.

Источник

Bug 994961
— User of caller and user of subject differs

Summary:

User of caller and user of subject differs

Keywords:
Status:	CLOSED EOL
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	lxpanel
Sub Component:
Version:	19
Hardware:	x86_64
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	—
Assignee:	Christoph Wickert
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2013-08-08 10:00 UTC by Giacomo Mattiuzzi
Modified:	2015-02-17 16:38 UTC (History)
CC List:	6 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-02-17 16:38:54 UTC
Type:	Bug
Dependent Products:

Attachments

(Terms of Use)

The Error Message

(68.93 KB,
image/jpeg)

2013-08-08 10:00 UTC,

Giacomo Mattiuzzi

no flags

Details

.xsession-errors of the second user to log in

(145.33 KB,
text/plain)

2013-08-20 05:57 UTC,

Pavel Roskin

no flags

Details

View All

Add an attachment
(proposed patch, testcase, etc.)

Источник

How to fix GDBus Error org freedesktop PolicyKit1 Error Failed

Background:

Conclusion

Check Also

Cracking password in Kali Linux using John the Ripper

Читайте также: