Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 2024-03-25 11:52:13 - [swaybg-1.2.0/main.c:293] Found config * for output DP-1 (Dell Inc. DELL U2312HM 59DJP26KA9QL)
- 2024-03-25 11:52:13 - [swaybg-1.2.0/main.c:293] Found config * for output DP-2 (Dell Inc. DELL U2212HM Y9KCH2AF0LLL)
- [2024-03-25 11:52:14.698] [info] Using configuration file /home/vrein/.config/waybar/config
- [2024-03-25 11:52:14.846] [info] Using CSS file /home/vrein/.config/waybar/style.css
- [2024-03-25 11:52:14.852] [warning] Mapping is not an object
- [2024-03-25 11:52:14.890] [warning] module temperature: Disabling module "temperature", Can't open /sys/class/hwmon/hwmon3/temp1_input
- [2024-03-25 11:52:14.935] [warning] Mapping is not an object
- [2024-03-25 11:52:14.942] [warning] module temperature: Disabling module "temperature", Can't open /sys/class/hwmon/hwmon3/temp1_input
- blueman-applet 11.52.15 WARNING PluginManager:94 load_plugin: Failed to start plugin GameControllerWakelock: Only X11 platform is supported
- [2024-03-25 11:52:15.200] [info] Bar configured (width: 1920, height: 26) for output: DP-1
- [2024-03-25 11:52:15.200] [error] Item '': No icon name or pixmap given.
- [2024-03-25 11:52:15.232] [info] Bar configured (width: 1920, height: 26) for output: DP-2
- [2024-03-25 11:52:15.232] [error] Item '': No icon name or pixmap given.
- (waybar:694): Gtk-CRITICAL **: 11:52:15.694: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.694: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.695: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.695: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.696: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.696: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.697: gtk_widget_set_accel_path: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- (waybar:694): Gtk-CRITICAL **: 11:52:15.697: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
- [
- {
- "success": true
- }
- ]
- [
- {
- "success": true
- }
- ]
- 00:00:13.697 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- [
- {
- "success": true
- }
- ]
- [
- {
- "success": true
- }
- ]
- 00:00:23.666 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:23.749 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:23.999 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- The XKEYBOARD keymap compiler (xkbcomp) reports:
- > Warning: Could not resolve keysym XF86CameraAccessEnable
- > Warning: Could not resolve keysym XF86CameraAccessDisable
- > Warning: Could not resolve keysym XF86CameraAccessToggle
- > Warning: Could not resolve keysym XF86NextElement
- > Warning: Could not resolve keysym XF86PreviousElement
- > Warning: Could not resolve keysym XF86AutopilotEngageToggle
- > Warning: Could not resolve keysym XF86MarkWaypoint
- > Warning: Could not resolve keysym XF86Sos
- > Warning: Could not resolve keysym XF86NavChart
- > Warning: Could not resolve keysym XF86FishingChart
- > Warning: Could not resolve keysym XF86SingleRangeRadar
- > Warning: Could not resolve keysym XF86DualRangeRadar
- > Warning: Could not resolve keysym XF86RadarOverlay
- > Warning: Could not resolve keysym XF86TraditionalSonar
- > Warning: Could not resolve keysym XF86ClearvuSonar
- > Warning: Could not resolve keysym XF86SidevuSonar
- > Warning: Could not resolve keysym XF86NavInfo
- Errors from xkbcomp are not fatal to the X server
- The XKEYBOARD keymap compiler (xkbcomp) reports:
- > Warning: Unsupported maximum keycode 708, clipping.
- > X11 cannot support keycodes above 255.
- > Warning: Could not resolve keysym XF86CameraAccessEnable
- > Warning: Could not resolve keysym XF86CameraAccessDisable
- > Warning: Could not resolve keysym XF86CameraAccessToggle
- > Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou
- > Warning: Could not resolve keysym XF86KbdInputAssistNextgrou
- > Warning: Could not resolve keysym XF86NextElement
- > Warning: Could not resolve keysym XF86PreviousElement
- > Warning: Could not resolve keysym XF86AutopilotEngageToggle
- > Warning: Could not resolve keysym XF86MarkWaypoint
- > Warning: Could not resolve keysym XF86Sos
- > Warning: Could not resolve keysym XF86NavChart
- > Warning: Could not resolve keysym XF86FishingChart
- > Warning: Could not resolve keysym XF86SingleRangeRadar
- > Warning: Could not resolve keysym XF86DualRangeRadar
- > Warning: Could not resolve keysym XF86RadarOverlay
- > Warning: Could not resolve keysym XF86TraditionalSonar
- > Warning: Could not resolve keysym XF86ClearvuSonar
- > Warning: Could not resolve keysym XF86SidevuSonar
- > Warning: Could not resolve keysym XF86NavInfo
- Errors from xkbcomp are not fatal to the X server
- 00:00:24.867 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:24.869 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:25.301 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:25.417 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:25.418 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:26.952 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:26.985 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:28.586 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:28.669 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:29.153 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:29.170 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:30.170 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:40.040 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- 00:00:44.725 [ERROR] [wlr] [backend/drm/atomic.c:73] connector DP-2: Atomic commit failed: Device or resource busy
- Io error: Broken pipe (os error 32)
- [2024-03-25 11:53:06.113] [error] Workspaces: Unable to receive IPC header
- Io error: Broken pipeGdk-Message: 11:53:06.113: Error reading events from display: Broken pipe
- (os error [2024-03-25 11:53:06.113] [error] Workspaces: Unable to receive IPC header
- 32)
- [2024-03-25 11:53:06.113] [error] Workspaces: Unable to receive IPC header
- Gdk-Message: 11:53:06.113: Error reading events from display: Broken pipe
- Gdk-Message: 11:53:06.113: Error reading events from display: Connection reset by peer
- Gdk-Message: 11:53:06.113: Error reading events from display: Broken pipe
- Io error: Broken pipe (os error 32)
- Error: ExitFailure(1)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement