Gnome-display-properties crashes if you try to mirror with a smaller screen

Bug #414914 reported by Lionel Dricot
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

1) Attach to your computer a screen with a maximal resolution smaller than you current one.

2) Open gnome-display-properties and clic "mirror"

3) it crashes with the error :
 display-properties:ERROR:xrandr-capplet.c:684:rebuild_resolution_combo: code should not be reached

The reason is obvious : the attached screen cannot clone the current one as it doesn't have the physical resolution to do it.

Exepected 3) Current resolution is lowered as needed (because it's what the user wants if he clicked on "mirror")

summary: - Gnome-display-properties crashes if you try to mirror with a smaller
- screen
+ [Karmic alpha 4] Gnome-display-properties crashes if you try to mirror
+ with a smaller screen
Revision history for this message
Chris Coulson (chrisccoulson) wrote : Re: [Karmic alpha 4] Gnome-display-properties crashes if you try to mirror with a smaller screen

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
summary: - [Karmic alpha 4] Gnome-display-properties crashes if you try to mirror
- with a smaller screen
+ Gnome-display-properties crashes if you try to mirror with a smaller
+ screen
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Also, please don't put the release name (ie, "karmic alpha 4") in the bug title. It implies that it only happens in that release, which would not be true if it is not fixed by the next alpha.

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Hello Chris,

I will do that but I didn't find the dbg package, I was unaware of the ddeb repository.

On a side note, I think I disagree with your use of "incomplete" in Launchpad. For me, it means that it's a bug that cannot even be verified without the requested information.

In this case, anybody with two screens should be able to reproduce this bug, I think I provided enough information to reproduce the bug. Marking it as incomplete is dangerous because if I don't reply, the bug will disapear from LP but not magically from Ubuntu.

Of course, if you tested it yourself with 2 screens and nobody else was able to reproduce that bug, then it makes sense. ;-)

PS : I will do the debugging stuff ASAP, don't worry

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

No, incomplete means it is still waiting on information to be useful - ie, a backtrace. I don't have 2 screens, and lots of other developers don't either. Without a backtrace, there's not enough information here to do anything.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

And also, you assume that everyone else can reproduce the bug - that's not always the case with some crashers. It could just be something unique to your setup (and lots of users have 2 screens and never hace this problem).

I don't know why you think Incomplete is dangerous. It just means that the bug report doesn't have enough information. Bug reports set to Incomplete don't just magically disappear from Launchpad.

Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

Chris > Never mind, it's just that I don't use "incomplete" that way for my projects. Not a big deal, I was just noting it.

In order to be forgiven, I offer you a nice traceback ;-)

Changed in gnome-control-center (Ubuntu):
status: Incomplete → New
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks, but there are some debug symbols missing from your trace. Could you please try again with the following extra packages installed:

libgtk2.0-dbg, libglib2.0-dbg, libc6-dbg

Thanks

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
Lionel Dricot (ploum-deactivatedaccount) wrote :

hope it's complete

Changed in gnome-control-center (Ubuntu):
status: Incomplete → New
Revision history for this message
Facundo Batista (facundo) wrote :

Here you have an strace of this problem...

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thanks, I will build a version of gnome-control-center in my PPA later which will print out some debug statements to provide some more information, before I send this upstream.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

We have a distro-patch which touches some of this code, so this crash could be caused by that. I will investigate this some more before deciding if it should go upstream.

Changed in gnome-control-center (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Confirmed
tags: added: regression-potential
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Ok, this is actually an upstream issue, reported here: http://bugzilla.gnome.org/show_bug.cgi?id=593866

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.