-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wf-backgroud crashes after disconnecting external monitor. #219
Comments
Comiped it with buidtype=debug. In log - Fist time it loaded background when I re-start it in terminal after crash. Second time it reloaded it when I connected the monitor and system started negotiation for monitor mode. Third time - when monitor mode was selected and it started show the picture. So wf-background is receving signals for monitor change when monitor is connected. But when I disconnected monitor - it did not reload the wallpaper. Next time it reloaded next wallpaper on timeut Loaded /usr/share/backgrounds/dark/17.jpg (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_width: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_height: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): GdkPixbuf-CRITICAL **: 14:08:04.374: gdk_pixbuf_new_from_file_at_scale: assertion 'width > 0 || width == -1' failed (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_width: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_height: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): GdkPixbuf-CRITICAL **: 14:08:04.374: gdk_pixbuf_new_from_file_at_scale: assertion 'width > 0 || width == -1' failed (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_width: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): Gtk-CRITICAL **: 14:08:04.374: gtk_widget_get_allocated_height: assertion 'GTK_IS_WIDGET (widget)' failed (wf-background:46816): GdkPixbuf-CRITICAL **: 14:08:04.374: gdk_pixbuf_new_from_file_at_scale: assertion 'width > 0 || width == -1' failed |
(gdb) bt |
Can you try the PR #220, I think that should be enough to fix the crash. |
It does not crash anymore. But behaves differently than I expected - now the both monitors are not in sync with the wllpaper image, and each monitor has its own timer. For external monitor the timer runs only when it is connected, Anyway that's not a bug, that's a way it works. |
Yeah I can see that. I suppose we can fix them to be in sync - feel free to send a PR if you manage to patch it. |
Also thanks for testing :) |
@ammen99 , is there any way to get logs without building debug version from scratch? |
No, release builds explicitly remove most source code information and you cannot easily find how the crash occurs without this information. |
Connect external monitor to the latop.
Backgroud image is perfectly painted on it straigh away.
Disconnect external monitor.
Wait till the cycle timout event happens and wf-background will load the next wallpaper. It changes wallpaper on the main screen and crahes almost immediately - looks like it is attempting to paint new wallpaper on the disconnected output.
The text was updated successfully, but these errors were encountered: