After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 579614 - fails to start if configured to appear on a non-existent monitor
fails to start if configured to appear on a non-existent monitor
Status: RESOLVED FIXED
Product: gnome-panel
Classification: Other
Component: panel
2.26.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-04-20 14:26 UTC by Chris Jones
Modified: 2009-10-03 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Chris Jones 2009-04-20 14:26:09 UTC 
Steps to reproduce:
1. Have one monitor
2. Set /apps/panel/toplevels/top_panel_screen0/monitor to 1
3. Restart gnome-panel


Stack trace:
** (gnome-panel:6288): CRITICAL **: panel_multiscreen_width: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:6288): CRITICAL **: panel_multiscreen_height: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:6288): CRITICAL **: panel_multiscreen_x: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:6288): CRITICAL **: panel_multiscreen_y: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed

No stack trace as such, but the above errors will spew into your terminal in what appears to be an endless loop.

Other information:
This is probably fallout from using a second monitor on the laptop in question at some point, but the panel should clearly degrade gracefully when this configuration is invalid with the current display setup.
Comment 1 Vincent Untz 2009-10-03 00:27:00 UTC 
I've fixed this in 2.28, it will go back to 0.