Closed maxmbed closed 6 years ago
damn - when budgie was uploaded nautilus had not been updated ...
mbed5 budgie-panel[26652]: Settings schema 'org.gnome.nautilus.desktop' is not installed
^^^
That error means that nautilus is now at 3.30. I'll post a new build tomorrow with desktop icon support switched off.
On Fri, 7 Sep 2018 at 23:31, Maxime notifications@github.com wrote:
Operating System Debian buster/sid (4.17.17-1)
Budgie version budgie-desktop 10.4
The issue encountered Budgie-destktop-settings is not able to start since the last update to 10.4 (+git20180830.01.f2dbc215fdb-2). The application exited straight after it launched.
Below, the syslog after launching budgie-desktop-settings
Sep 7 20:08:52 mbed5 kernel: [37853.501152] traps: budgie-panel[5850] trap int3 ip:7f9a28ee19f5 sp:7ffd3b99c810 error:0 in libglib-2.0.so.0.5800.0[7f9a28ea9000+7d000] Sep 7 20:08:52 mbed5 gnome-session[4908]: gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:08:52 mbed5 gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:08:53 mbed5 bluetoothd[535]: Failed to set mode: Blocked through rfkill (0x12) Sep 7 20:08:53 mbed5 budgie-panel[26623]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
And here, the returned message from the consol if run from terminal :
(process:31299): WARNING : 00:26:30.827: budgie-desktop-settings.vala:27: Failed to launch settings UI: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.budgie_desktop.Panel was not provided by any .service files
If I try it again, budgie seems to crash X server and bring back user to login menu :
Sep 7 20:10:10 mbed5 kernel: [37931.198505] traps: budgie-panel[26623] trap int3 ip:7f7612dd49f5 sp:7ffc0143f760 error:0 in libglib-2.0.so.0.5800.0[7f7612d9c000+7d000] Sep 7 20:10:10 mbed5 gnome-session[4908]: gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:10:10 mbed5 gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:10:10 mbed5 bluetoothd[535]: Failed to set mode: Blocked through rfkill (0x12) Sep 7 20:10:10 mbed5 budgie-panel[26652]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36) Sep 7 20:10:14 mbed5 budgie-panel[26652]: Settings schema 'org.gnome.nautilus.desktop' is not installed Sep 7 20:10:14 mbed5 kernel: [37935.335186] traps: budgie-panel[26652] trap int3 ip:7f0458dec9f5 sp:7ffc9a6fed90 error:0 in libglib-2.0.so.0.5800.0[7f0458db4000+7d000] Sep 7 20:10:14 mbed5 gnome-session[4908]: gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:10:14 mbed5 gnome-session[4908]: gnome-session-binary[4908]: WARNING: App 'budgie-panel.desktop' respawning too quickly Sep 7 20:10:14 mbed5 gnome-session-binary[4908]: Unrecoverable failure in required component budgie-panel.desktop Sep 7 20:10:14 mbed5 gnome-session-binary[4908]: WARNING: Application 'budgie-panel.desktop' killed by signal 5 Sep 7 20:10:14 mbed5 gnome-session-binary[4908]: WARNING: App 'budgie-panel.desktop' respawning too quickly Sep 7 20:10:14 mbed5 gnome-session[4908]: Unable to init server: Could not connect: Connection refused Sep 7 20:10:14 mbed5 gnome-session-f[26671]: Cannot open display: Sep 7 20:10:14 mbed5 gsd-print-notif[5105]: Source ID 2 was not found when attempting to remove it Sep 7 20:10:14 mbed5 kernel: [37935.409976] budgie-daemon[5289]: segfault at 0 ip 00007fc84e95716e sp 00007ffe09c6abf0 error 6 in libwnck-3.so.0.3.0[7fc84e941000+3e000] Sep 7 20:10:14 mbed5 budgie-daemon[5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 budgie-daemon[5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 kernel: [37935.412483] budgie-polkit-d[5290]: segfault at 560835652628 ip 00007f28b89fdcfe sp 00007ffead9a2e40 error 4 in libglib-2.0.so.0.5800.0[7f28b89e9000+7d000] Sep 7 20:10:14 mbed5 budgie-daemon[5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 budgie-daemon[5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 budgie-daemon[5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 [5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 [5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 [5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 [5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 [5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 [5289]: invalid unclassed pointer in cast to 'WnckWindow' Sep 7 20:10:14 mbed5 [5289]: _wnck_window_destroy: assertion 'WNCK_IS_WINDOW (window)' failed Sep 7 20:10:14 mbed5 kernel: [37935.430536] rfkill: input handler enabled Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/dbus.service, ignoring: Operation not permitted Sep 7 20:10:14 mbed5 gvfsd[4999]: A connection to the bus can't be made Sep 7 20:10:14 mbed5 systemd[4889]: Stopping D-Bus User Message Bus... Sep 7 20:10:14 mbed5 thunderbird[9298]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-extract[5300]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-extract[5300]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-extract[5300]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-extract[5300]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-extract[5300]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 Discord[5317]: Got Disconnected from DBus. Sep 7 20:10:14 mbed5 tracker-miner-f[5340]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-miner-f[5340]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-miner-f[5340]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-miner-f[5340]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-miner-f[5340]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 tracker-miner-apps.desktop[5310]: Received signal:15->'Terminated' Sep 7 20:10:14 mbed5 evolution-alarm[5302]: g_dbus_connection_call_internal: assertion 'object_path != NULL && g_variant_is_object_path (object_path)' failed Sep 7 20:10:14 mbed5 java[9576]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/dbus.service, ignoring: Operation not permitted Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Killing process 6334 (dbus-launch) with signal SIGKILL. Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Killing process 6335 (dbus-daemon) with signal SIGKILL. Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/dbus.service, ignoring: Operation not permitted Sep 7 20:10:14 mbed5 systemd[4889]: Stopped D-Bus User Message Bus. Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Found left-over process 6334 (dbus-launch) in control group while starting unit. Ignoring. Sep 7 20:10:14 mbed5 systemd[4889]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 7 20:10:14 mbed5 systemd[4889]: dbus.service: Found left-over process 6335 (dbus-daemon) in control group while starting unit. Ignoring. Sep 7 20:10:14 mbed5 systemd[4889]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 7 20:10:14 mbed5 systemd[4889]: Started D-Bus User Message Bus. Sep 7 20:10:14 mbed5 budgie-wm[5230]: budgie_shell_shim_on_disappeared: assertion 'conn != NULL' failed Sep 7 20:10:14 mbed5 gnome-software[5339]: lost session service Sep 7 20:10:14 mbed5 java[9576]: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 java[9576]: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 java[9576]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:14 mbed5 java[9576]: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts Sep 7 20:10:15 mbed5 NetworkManager[545]:
[1536343815.0134] device (wlp2s0): state change: activated -> deactivating (reason 'connection-removed', sys-iface-state: 'managed') Sep 7 20:10:15 mbed5 NetworkManager[545]: [1536343815.0138] manager: NetworkManager state is now DISCONNECTING Sep 7 20:10:15 mbed5 tracker-miner-apps.desktop[5310]: OK Sep 7 20:10:15 mbed5 NetworkManager[545]: [1536343815.0223] device (wlp2s0): state change: deactivating -> disconnected (reason 'connection-removed', sys-iface-state: 'managed') Sep 7 20:10:15 mbed5 avahi-daemon[534]: Withdrawing address record for fe80::e989:b5bd:e093:d216 on wlp2s0. Sep 7 20:10:15 mbed5 avahi-daemon[534]: Leaving mDNS multicast group on interface wlp2s0.IPv6 with address fe80::e989:b5bd:e093:d216. Sep 7 20:10:15 mbed5 budgie-wm[5230]: budgie-wm: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 7 20:10:15 mbed5 avahi-daemon[534]: Interface wlp2s0.IPv6 no longer relevant for mDNS. Sep 7 20:10:15 mbed5 dbus-daemon[540]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=545 comm="/usr/sbin/NetworkManager --no-daemon ") Steps to reproduce the issue Run budgie-destop-setting (nothing happen) Run it a second time (X server crashed)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/solus-project/budgie-desktop/issues/1561, or mute the thread https://github.com/notifications/unsubscribe-auth/AA8zkPnYgLjscC5AWwKpA10b7uqQs1ihks5uYvPbgaJpZM4WfkEQ .
Yep, Nautilus have been kept to 3.30 on my system.
New build should be available in unstable shortly.
Just update. I am able to open desktop-setting as expected. Thanks @fossfreedom
Operating System Debian buster/sid (4.17.17-1)
Budgie version budgie-desktop 10.4
The issue encountered Budgie-destktop-settings is not able to start since the last update to 10.4 (+git20180830.01.f2dbc215fdb-2). The application exited straight after it launched.
Below, the syslog after launching budgie-desktop-settings
And here, the returned message from the consol if run from terminal :
** (process:31299): WARNING **: 00:26:30.827: budgie-desktop-settings.vala:27: Failed to launch settings UI: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.budgie_desktop.Panel was not provided by any .service files
If I try it again, budgie seems to crash X server and bring back user to login menu :
Steps to reproduce the issue Run budgie-destop-setting (nothing happen) Run it a second time (X server crashed)