grandr crashed with SIGSEGV in gtk_tree_model_get_valist()

Bug #127829 reported by Alex Willmer
64
Affects Status Importance Assigned to Milestone
grandr (Debian)
Fix Released
Unknown
grandr (Ubuntu)
Fix Released
Medium
Daniel Hahler
Nominated for Gutsy by Rolf Leggewie
Hardy
Fix Released
Medium
Daniel Hahler

Bug Description

Binary package hint: grandr

Chipset: G965
Motherboard: P5B VM
Monitor: LG Flatron 795FT Plus
Acitivty:: Click on monitor icon
Reproducable: Yes

alex@bertha:~$ grandr

(grandr:11348): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed

(grandr:11348): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.13.7/gobject/gtype.c:3339: type id `0' is invalid

(grandr:11348): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault (core dumped)

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Jul 23 22:45:23 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/grandr
NonfreeKernelModules: cdrom
Package: grandr 0.1-2
PackageArchitecture: amd64
ProcCmdline: grandr
ProcCwd: /home/alex
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
Signal: 11
SourcePackage: grandr
StacktraceTop:
 gtk_tree_model_get_valist ()
 gtk_tree_model_get ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: grandr crashed with SIGSEGV in gtk_tree_model_get_valist()
Uname: Linux bertha 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Related branches

Revision history for this message
Alex Willmer (alex-moreati) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? () from /usr/lib/libgtk-x11-2.0.so.0
?? ()
?? ()
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
tryp (cdouglass) wrote :

I get the same segfault as soon as I click on the TV icon

(grandr:13023): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed

(grandr:13023): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.13.7/gobject/gtype.c:3339: type id `0' is invalid

(grandr:13023): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault (core dumped)

the following is the output of xrandr -q

Screen 0: minimum 320 x 200, current 1440 x 900, maximum 1440 x 1440
VGA disconnected (normal left inverted right)
LVDS connected 1440x900+0+0 (normal left inverted right) 303mm x 190mm
   1440x900 60.0*+ 50.0
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 60.0 59.9
TMDS-1 disconnected (normal left inverted right)
TV connected 1024x768+0+0 (normal left inverted right) 0mm x 0mm
   1024x768 30.0*
   800x600 30.0
   848x480 30.0
   640x480 30.0

Changed in grandr:
status: New → Confirmed
Revision history for this message
SeG (razahel) wrote :

I have the same problem, when I try to use grandr it crashes instantly.
Here is my output of xrandr -q
Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 2560 x 1024
VGA-0 connected 1280x1024+0+0 (normal left inverted right) 338mm x 270mm
   1280x1024 60.0*+ 75.0 59.9
   1152x864 75.0
   1024x768 74.9 75.1 60.0
   832x624 74.6
   800x600 75.0 74.9 60.3
   640x480 75.0 74.8 60.0
   720x400 70.1
LVDS connected 1280x800+1280+0 (normal left inverted right) 0mm x 0mm
   1280x800 60.0*+ 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right)

Revision history for this message
FlagMan (flagman) wrote :

FYI:
grandr was written by <email address hidden>
It is under git version control here:
http://gitweb.freedesktop.org/?p=xorg/app/grandr.git

debian has this same bug here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445310

The original poster over there claims to fix this bug by a dirty hack.
I did not try it out, because I found that the xrandr cli does everything I need.

Changed in grandr:
status: Unknown → New
Revision history for this message
Brian Pitts (bpitts) wrote :

Same bug; Inspiron 1420N.

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

This fixes the crash as reported. I am not sure if the functionality is not affected, though.

There are still crashes if I click on rotation of external monitor. And, above all, it doesn't do anything really...

Revision history for this message
Michael R. Head (burner) wrote :

Got this crash with the latest hardy on a Thinkpad T30 with Radeon Mobility 7500 chip.

$ xrandr -q
Screen 0: minimum 320 x 200, current 1400 x 1050, maximum 1400 x 1200
VGA-0 disconnected (normal left inverted right x axis y axis)
DVI-0 disconnected (normal left inverted right x axis y axis)
LVDS connected 1400x1050+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1400x1050 50.0*+
   1280x800 60.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9
S-video disconnected (normal left inverted right x axis y axis)

Revision history for this message
sibidiba (sibidiba) wrote :

Can confirm this bug. grandr is currently unusable, selecting a display device results in a segfault:

(grandr:21760): Gtk-CRITICAL **: gtk_list_store_get_value: assertion `VALID_ITER (iter, list_store)' failed

(grandr:21760): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.15.6/gobject/gtype.c:3368: type id `0' is invalid

(grandr:21760): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced
Segmentation fault (core dumped)

$ xrandr -q
Screen 0: minimum 320 x 200, current 1680 x 1850, maximum 2048 x 2048
VGA connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
   1680x1050 60.0*+
   1280x1024 75.0 59.9
   1280x960 59.9
   1152x864 75.0 74.8
   1024x768 75.1 70.1 60.0
   832x624 74.6
   800x600 72.2 75.0 60.3 56.2
   640x480 75.0 72.8 66.7 60.0
   720x400 70.1
LVDS connected 1280x800+0+1050 (normal left inverted right x axis y axis) 331mm x 207mm
   1280x800 60.0*+ 60.0 50.0
   1280x768 60.0
   1024x768 60.0
   800x600 60.3
   640x480 59.9

Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

does anyonelse think that grandr development is dead?

Daniel Hahler (blueyed)
Changed in grandr:
assignee: nobody → blueyed
importance: Undecided → Medium
status: Confirmed → In Progress
Revision history for this message
Daniel Hahler (blueyed) wrote :

Thank you for the bug report(s) and especially the patch, which I've just applied and uploaded for Hardy.

Changed in grandr:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package grandr - 0.1-2ubuntu1

---------------
grandr (0.1-2ubuntu1) hardy; urgency=low

  * Fix crash in gtk_tree_mode_get_valist() (LP: #127829)
    - Inline patch for src/callbacks.c has been provided by Václav Šmilauer
  * Modify Maintainer value to match the DebianMaintainerField
    specification.

 -- Daniel Hahler <email address hidden> Mon, 17 Mar 2008 01:22:40 +0100

Changed in grandr:
status: Fix Committed → Fix Released
Revision history for this message
Fernando Miguel (fernandomiguel) wrote :

Thank you so much for finally fix that click crash bug.
I finally have a working multimonitor app for Hardy.

Now, if only Brice would get dcGTK ready....

--
BUGabundo :o)
(``-_-´´) http://Ubuntu.BUGabundo.net
Linux user #443786 GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net

Changed in grandr:
status: New → Fix Released
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I backported the hardy package to gutsy and verify that this fixed the bug -> https://launchpad.net/~r0lf/+archive

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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