cosmic-epoch icon indicating copy to clipboard operation
cosmic-epoch copied to clipboard

[BUG] Panel Disappears

Open nevdelap opened this issue 1 year ago • 7 comments

It started happening in recent days, and has happened maybe four or five times. I'm on Arch and I update regularly. I updated yesterday.

It has just been that I realise the panel has disappeared, usually because I go to look at the clock, not knowing how long it hasn't been there because all my attention is in VS Code or whatever. Because it isn't urgent enough that logging out and in and having to set up my applications and terminal windows across my workspaces I've been living without it until the end of the day.

Today I did notice that it disappeared from one screen (external monitor) but was still on the other screen (laptop) for some minutes, before it disappeared from that screen.

After it had disappeared cosmic-panel was still running, as per ps -ef | grep cosmic-panel. Since it is the weekend I decided I'd look for a workaround to try and get it back. I tried kill -HUP, but that froze everything, so I'd have had to log out and log in anyway. I tried a kill -HUP cosmic-comp which restarted it, amounting to the same thing.

So I don't have anything more useful at the moment other than to report that it is happening, and it had never happened between early August and a few days ago. (I've been using it at home since then, while still being on i3 at work, work 2.5 days at home, 2.5 days in the office.)

Also, this happens during use - not when unplugging screens, closing the laptop screen (it has never happened doing that), or sleeping/hibernating (my laptop stays on permanently).

nevdelap avatar Nov 02 '24 05:11 nevdelap

Two days later and the panel was still there. I used cosmic-settings to move it the left of the screen which worked, then back to the bottom, and now it has disappeared. (So that is different from it just disappearing, but I was testing if it was responding to changes in settings to do with another issue.)

nevdelap avatar Nov 03 '24 23:11 nevdelap

I've noticed that when the panel disappears from one screen but is still on the other screen, the remaining panel is frozen.

In this example it has disappeared from my external monitor, it is still on the laptop monitor, but is frozen at 3:01pm yesterday, it is now 7am. Switching workspaces on that screen works, but it is frozen on workspace 3.

image

Update: And actually, I was able to take that screenshot, but when I moved the mouse over the panel while not taking a screenshot, that is when the panel disappeared.

nevdelap avatar Nov 06 '24 21:11 nevdelap

So idk if it is related, but I got the following log line right around the time it dissapeared. I maybe tried dragging an applet while it happened.

Nov 07 09:15:47 MYDEVICE cosmic-panel[2784]: com.system76.CosmicAppList: Error getting config: com.system76.CosmicAppList [GetKey("enable_drag_source", Os { code: 2, kind: NotFound, message: "No such file or directory" })]

CrazyChaoz avatar Nov 07 '24 08:11 CrazyChaoz

I've just had it happen again, but it happened at about the same time as this, so the log might have both issues mixed in there.

Nov 08 09:21:24 zen google-chrome-stable[1188]: [1170:1170:1108/092124.586391:ERROR:interface_endpoint_client.cc(725)] Message 0 rejected by interface blink.mojom.WidgetHost
Nov 08 09:25:29 zen google-chrome-stable[1188]: [1170:1170:1108/092529.596819:ERROR:interface_endpoint_client.cc(725)] Message 0 rejected by interface blink.mojom.WidgetHost
Nov 08 09:25:41 zen slack[102370]: Opening in existing browser session.
Nov 08 09:31:45 zen systemd[1]: Starting Daily man-db regeneration...
Nov 08 09:31:56 zen systemd[1]: man-db.service: Deactivated successfully.
Nov 08 09:31:56 zen systemd[1]: Finished Daily man-db regeneration.
Nov 08 09:31:56 zen systemd[1]: man-db.service: Consumed 9.740s CPU time, 163.5M memory peak.
Nov 08 09:32:22 zen geoclue[1557]: Failed to query location: Query location SOUP error: Unknown Error
Nov 08 09:43:25 zen kernel: amdgpu 0000:03:00.0: [drm] Mode Validation Warning: Unknown Status failed validation.
Nov 08 09:43:35 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:77:crtc-1] flip_done timed out
Nov 08 09:44:59 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Nov 08 09:44:59 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:77:crtc-1] commit wait timed out
Nov 08 09:45:09 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Nov 08 09:45:09 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:52:plane-2] commit wait timed out
Nov 08 09:45:19 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Nov 08 09:45:19 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:64:plane-4] commit wait timed out
Nov 08 09:45:29 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Nov 08 09:45:29 zen kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:74:plane-6] commit wait timed out
Nov 08 09:45:29 zen cosmic-comp[1095]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:30 zen cosmic-comp[1095]: thread 'surface-HDMI-A-1' panicked at 'internal error: entered unreachable code': src/backend/kms/surface/mod.rs:780
                                          0: <unknown>
                                          1: <unknown>
                                          2: <unknown>
                                          3: <unknown>
                                          4: <unknown>
                                          5: <unknown>
                                          6: <unknown>
                                          7: <unknown>
                                          8: <unknown>
                                          9: <unknown>
                                         10: <unknown>
                                         11: <unknown>
                                         12: <unknown>
                                         13: <unknown>
                                         14: <unknown>
                                         15: <unknown>
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_files::tab] failed to read directory "/home/nevd/Desktop": No such file or directory (os error 2)
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_files::tab] failed to get item for "/home/nevd/Desktop": failed to read metadata for "/home/nevd/Desktop": No such file or directory (o>
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:30 zen cosmic-session[1034]: [2024-11-07T23:45:30Z WARN  cosmic_greeter::locker] output wl_output@56: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:35 zen cosmic-session[1034]: [2024-11-07T23:45:35Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:38 zen cosmic-comp[1095]: Failed to destroy old mode property blob: No such file or directory (os error 2)
Nov 08 09:45:38 zen cosmic-session[1034]: [2024-11-07T23:45:38Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:38 zen cosmic-session[1034]: [2024-11-07T23:45:38Z WARN  cosmic_files::tab] failed to read directory "/home/nevd/Desktop": No such file or directory (os error 2)
Nov 08 09:45:38 zen cosmic-session[1034]: [2024-11-07T23:45:38Z WARN  cosmic_files::tab] failed to get item for "/home/nevd/Desktop": failed to read metadata for "/home/nevd/Desktop": No such file or directory (o>
Nov 08 09:45:38 zen cosmic-session[1034]: [2024-11-07T23:45:38Z WARN  cosmic_greeter::locker] output wl_output@7: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:45:38 zen cosmic-session[1034]: [2024-11-07T23:45:38Z WARN  cosmic_greeter::locker] output wl_output@56: unsupported source Single([0.9411765, 0.9411765, 0.9411765])
Nov 08 09:47:55 zen systemd[1024]: Started Application launched by COSMIC.
Nov 08 09:47:57 zen cosmic-comp[1095]: Failed to handle X11 event
Nov 08 09:48:07 zen cosmic-comp[1095]: [GL] GL_INVALID_VALUE in glTexSubImage2D(xoffset 0 + width 36 > 24)
Nov 08 09:48:07 zen cosmic-comp[1095]: [GL] GL_INVALID_VALUE in glTexSubImage2D(xoffset 0 + width 36 > 24)
Nov 08 09:48:33 zen cosmic-notifications[1202]: Unknown hint: sender-pid
Nov 08 09:48:33 zen cosmic-session[1034]: 2024-11-07T23:48:33.282811Z  WARN cosmic_notifications_util: Unknown hint: sender-pid
Nov 08 09:48:33 zen cosmic-notifications[1202]: Failed to notify applet of notification I/O error: Broken pipe (os error 32)
Nov 08 09:48:33 zen cosmic-session[1034]: 2024-11-07T23:48:33.282977Z ERROR cosmic_notifications::subscriptions::notifications: Failed to notify applet of notification I/O error: Broken pipe (os error 32)
Nov 08 09:48:33 zen cosmic-notifications[1202]: Failed to notify applet of notification I/O error: Broken pipe (os error 32)
Nov 08 09:48:33 zen cosmic-session[1034]: 2024-11-07T23:48:33.283076Z ERROR cosmic_notifications::subscriptions::notifications: Failed to notify applet of notification I/O error: Broken pipe (os error 32)
Nov 08 09:49:57 zen sudo[105849]: pam_systemd_home(sudo:auth): New sd-bus connection (system-bus-pam-systemd-home-105849) opened.
Nov 08 09:49:58 zen sudo[105849]:     nevd : TTY=pts/8 ; PWD=/home/nevd ; USER=root ; COMMAND=/usr/bin/journalctl
Nov 08 09:49:58 zen sudo[105849]: pam_unix(sudo:session): session opened for user root(uid=0) by nevd(uid=1000)
Nov 08 09:50:01 zen sudo[105849]: pam_unix(sudo:session): session closed for user root
Nov 08 09:50:25 zen sudo[105985]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-105985) opened.
Nov 08 09:50:25 zen sudo[105985]:     nevd : TTY=pts/8 ; PWD=/home/nevd ; USER=root ; COMMAND=/usr/bin/journalctl -e
Nov 08 09:50:25 zen sudo[105985]: pam_unix(sudo:session): session opened for user root(uid=0) by nevd(uid=1000)

nevdelap avatar Nov 07 '24 22:11 nevdelap

@nevdelap What version of cosmic are you running, particularly cosmic-panel? I noticed the error message in your logs:

thread 'surface-HDMI-A-1' panicked at 'internal error: entered unreachable code':
  src/backend/kms/surface/mod.rs:780

But the last time src/backend/kms/mod.rs had a line 780 was quite some time ago (it was refactored and became a smaller file after this commit in May)

The only unreachable! code I see in that file is not on line 780 (it's on line 1377) and refers to mirroring two monitors. A call to unreachable! would result in the error message you noted above.

canadaduane avatar Nov 08 '24 03:11 canadaduane

cosmic-panel-git 1.0.0.alpha.3.r12.gd0d7972 I updated and rebooted yesterday. I see alpha3 was two weeks ago, and I update regularly.

And I see src/backend/kms/surface/mod.rs is actually in cosmic-comp and it is 1478 lines long. I'm on cosmic-comp-git 1.0.0.alpha.3.r1.g641bb75.

image

You must be looking at something else somewhere?

nevdelap avatar Nov 08 '24 04:11 nevdelap

I'm running the NixOS COSMIC flake with the following package versions and I'm also experiencing this issue. Usually when either connecting or disconnecting a display or suspending sometimes this happens. Though usually not just the panel disappears my entire screen goes black.

Packages
❯ nix-store -q --references /var/run/current-system/sw | cut -d'-' -f2- | grep -i cosmic
cosmic-icons-1.0.0-alpha.6-unstable-2025-02-25
cosmic-randr-1.0.0-alpha.6-unstable-2025-02-20
cosmic-settings-1.0.0-alpha.6-unstable-2025-03-17
cosmic-comp-1.0.0-alpha.6-unstable-2025-03-17
cosmic-applibrary-1.0.0-alpha.6-unstable-2025-03-18
xdg-desktop-portal-cosmic-1.0.0-alpha.6-unstable-2025-03-17
cosmic-settings-daemon-1.0.0-alpha.6-unstable-2025-02-28
cosmic-edit-1.0.0-alpha.6-unstable-2025-03-09
cosmic-bg-1.0.0-alpha.6-unstable-2025-02-05
cosmic-wallpapers-1.0.0-alpha.6-unstable-2024-10-31
cosmic-greeter-1.0.0-alpha.6-unstable-2025-03-15
cosmic-term-1.0.0-alpha.6-unstable-2025-03-13
cosmic-files-1.0.0-alpha.6-unstable-2025-03-13
cosmic-screenshot-1.0.0-alpha.6-unstable-2025-01-14
cosmic-player-1.0.0-alpha.6-unstable-2025-03-13
cosmic-notifications-1.0.0-alpha.6-unstable-2025-03-09
cosmic-session-1.0.0-alpha.6-unstable-2025-02-28
cosmic-applets-1.0.0-alpha.6-unstable-2025-03-18
cosmic-workspaces-epoch-1.0.0-alpha.6-unstable-2025-03-18
cosmic-panel-1.0.0-alpha.6-unstable-2025-03-18
cosmic-launcher-1.0.0-alpha.6-unstable-2025-03-18
cosmic-osd-1.0.0-alpha.6-unstable-2025-03-09
cosmic-idle-1.0.0-alpha.6-unstable-2025-02-25
Mar 25 17:33:13 nixlee .cosmic-panel-wrapped[4218]: [EGL] 0x300d (BAD_SURFACE) eglQuerySurface: EGL_BAD_SURFACE error: In eglQuerySurface: Surface (0xd10da565) must be bound as current
Mar 25 17:33:13 nixlee .cosmic-panel-wrapped[4218]: [EGL] 0x300d (BAD_SURFACE) eglQuerySurface: EGL_BAD_SURFACE error: In eglQuerySurface: Surface (0xd10da565) must be bound as current
Mar 25 17:33:14 nixlee .cosmic-panel-wrapped[4218]: [EGL] 0x300d (BAD_SURFACE) eglQuerySurface: EGL_BAD_SURFACE error: In eglQuerySurface: Surface (0xd10da565) must be bound as current
Mar 25 17:33:14 nixlee .cosmic-comp-wrapped[4160]: thread 'surface-DP-2' panicked at 'internal error: entered unreachable code': src/backend/kms/surface/mod.rs:814
                                                      0: <backtrace::capture::Backtrace as core::default::Default>::default
                                                      1: log_panics::Config::install_panic_hook::{{closure}}
                                                      2: std::panicking::rust_panic_with_hook
                                                      3: std::panicking::begin_panic_handler::{{closure}}
                                                      4: std::sys::backtrace::__rust_end_short_backtrace
                                                      5: rust_begin_unwind
                                                      6: core::panicking::panic_fmt
                                                      7: core::panicking::panic
                                                      8: <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::{{closure}}
                                                      9: <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events
                                                     10: cosmic_comp::backend::kms::surface::surface_thread
                                                     11: std::sys::backtrace::__rust_begin_short_backtrace
                                                     12: core::ops::function::FnOnce::call_once{{vtable.shim}}
                                                     13: std::sys::pal::unix::thread::Thread::new::thread_start
                                                     14: start_thread
                                                     15: __GI___clone3
Mar 25 17:33:14 nixlee .cosmic-comp-wrapped[4160]: thread 'surface-DP-1' panicked at 'internal error: entered unreachable code': src/backend/kms/surface/mod.rs:814
                                                      0: <backtrace::capture::Backtrace as core::default::Default>::default
                                                      1: log_panics::Config::install_panic_hook::{{closure}}
                                                      2: std::panicking::rust_panic_with_hook
                                                      3: std::panicking::begin_panic_handler::{{closure}}
                                                      4: std::sys::backtrace::__rust_end_short_backtrace
                                                      5: rust_begin_unwind
                                                      6: core::panicking::panic_fmt
                                                      7: core::panicking::panic
                                                      8: <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events::{{closure}}
                                                      9: <core::cell::RefCell<calloop::sources::DispatcherInner<S,F>> as calloop::sources::EventDispatcher<Data>>::process_events
                                                     10: cosmic_comp::backend::kms::surface::surface_thread
                                                     11: std::sys::backtrace::__rust_begin_short_backtrace
                                                     12: core::ops::function::FnOnce::call_once{{vtable.shim}}
                                                     13: std::sys::pal::unix::thread::Thread::new::thread_start
                                                     14: start_thread
                                                     15: __GI___clone3

Sirius902 avatar Mar 26 '25 00:03 Sirius902

For me both panel and dock disappears. But only when click on the panel after sometime of not interacting with it (while i'am working on something else and when click on power option on panel to see charge level suddenly both panel and dock disappears never to be seen again until i restart the system).

Should i post this as a separate issue?

nalladev avatar Nov 14 '25 10:11 nalladev