reassign 613765 python-gtk2 thanks Hi Drew, first of all let me thank your for the detailed report and the time you spend debugging reportbug issue! How I hope all the reports are like yours :)
On Thu, Feb 17, 2011 at 02:47, Bennett, Drew <drew.benn...@itron.com> wrote: > > Package: reportbug > Severity: normal > > - Background > > I tried to use 'reportbug' for the first time today. I eventually gave > up on it and manually e-mailed my bug report because the GTK2 client > repeatedly crashed and froze (it *crashed* each time I viewed a screen > for the first time, then *froze* many other times) and because after I can see the unpleasant situation. > filling out my bug report 'reportbug' failed to send the report > (probably because I don't have 'sendmail' configured, nor do I care to). yep, reportbug needs a working mta or some way to send an email to the outside world (that's because the debian bug tracking system works only via email) > - Replication > > I re-configured reportbug to comment out the 'gtk2' line, so I could > write my bug report without constant crashing. Then I came back and > tried to repeat the freezes, by running "reportbug --ui=gtk2". I am > able to repeat the freezes easily, by following these steps: > > - reportbug --ui=gtk2 > - the 'reportbug' window opens > - I move my mouse into the 'reportbug' window > - I move my mouse out of the 'reportbug' window > - I move my mouse back into the 'reportbug' window > > At this point, 'reportbug' is frozen: I can't click on any buttons. The > only thing I can do is click the 'X' button to close the window, at > which point nothing happens for about 5 seconds until I get the Force > Close dialog. > > - Supporting Information > > Nothing gets written to whatever logs 'dmesg' draws from, nor to > ~/.xsession-errors. > > 'dmesg | tail' includes the following 2 lines, which are from earlier > crashes, not my more recent attempts to repeat the mouse-away-then-back > freezes: > > [621019.952644] reportbug[7701] trap divide error ip:7fa34e8d9cf0 > sp:7fa3429a0f60 error:0 in libgtk-x11-2.0.so.0.2000.1[7fa34e7ad000+415000] > [621095.381655] reportbug[7790] trap divide error ip:7fdb6c551cf0 > sp:7fdb60618f60 error:0 in libgtk-x11-2.0.so.0.2000.1[7fdb6c425000+415000] > > > I have a somewhat non-standard focus-follows-mouse setup: > > $ gconftool-2 -a /apps/metacity/general > visual_bell_type = fullscreen > auto_raise_delay = 500 > titlebar_font = Sans Bold 10 > reduced_resources = false > application_based = false > theme = Clearlooks > mouse_button_modifier = <Alt> > focus_new_windows = smart > action_double_click_titlebar = none > audible_bell = true > resize_with_right_button = false > titlebar_uses_system_font = false > compositing_manager = false > num_workspaces = 4 > button_layout = menu:minimize,maximize,close > action_middle_click_titlebar = lower > disable_workarounds = false > focus_mode = mouse > raise_on_click = false > action_right_click_titlebar = lower > auto_raise = false > visual_bell = false > > > > Here is the log of my first attempts to run 'reportbug'. I *believe* > that all the instances where it says "Killed" are from the > mouse-away-then-back freeze, while the Python tracebacks are from the > crashes I saw the first time each screen was displayed: > > $ reportbug > Welcome to reportbug! Since it looks like this is the first time you > have used > reportbug, we are configuring its behavior. These settings will be saved > to the > file "/home/dbennett/.reportbugrc", which you will be free to edit further. > Please choose the default operating mode for reportbug. > > 1 novice Offer simple prompts, bypassing technical questions. > > 2 standard Offer more extensive prompts, including asking about things > that a > moderately sophisticated user would be expected to know about > Debian. > > 3 advanced Like standard, but assumes you know a bit more about Debian, > including "incoming". > > 4 expert Bypass most handholding measures and preliminary triage > routines. > This mode should not be used by people unfamiliar with Debian's > policies and operating procedures. > > Select mode: [novice] 2 > Please choose the default interface for reportbug. > > 1 text A text-oriented console user interface > > 2 gtk2 A graphical (GTK+) user interface. > > Select interface: 2 > Will reportbug often have direct Internet access? (You should answer yes to > this question unless you know what you are doing and plan to check whether > duplicate reports have been filed via some other channel.) [Y|n|q|?]? y > What real name should be used for sending bug reports? > [Drew Bennett]> > Which of your email addresses should be used when sending bug reports? (Note > that this address will be visible in the bug tracking system, so you may > want > to use a webmail address or another address with good spam filtering > capabilities.) > [drew.benn...@itron.com]> drew.benn...@itron.com > Do you have a "mail transport agent" (MTA) like Exim, Postfix or SSMTP > configured on this computer to send mail to the Internet? [Y|n|q|?]? n > Please enter the name of your SMTP host. Usually it's called something like > "mail.example.org" or "smtp.example.org". If you need to use a different > port > than default, use the <host>:<port> alternative format. Just press ENTER > if you > don't have one or don't know, and so a Debian SMTP host will be used. > > > Please enter the name of your proxy server. It should only use this > parameter > if you are behind a firewall. The PROXY argument should be formatted as > a valid > HTTP URL, including (if necessary) a port number; for example, > http://192.168.1.1:3128/. Just press ENTER if you don't have one or > don't know. > > > Default preferences file written. To reconfigure, re-run reportbug with > the "-- > configure" option. > > > Killed > $ > $ > $ reportbug > /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: > shaping failure, expect ugly output. shape-engine='BasicEngineFc', > font='DejaVu Sans 9.9990234375', text='' > gtk.main () > /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: > pango_layout_get_line_count: assertion `layout != NULL' failed > gtk.main () > Floating point exception > $ reportbug > Killed > $ reportbug > Killed > $ reportbug > /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: > pango_layout_set_width: assertion `layout != NULL' failed > gtk.main () > /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: > pango_layout_get_extents: assertion `layout != NULL' failed > gtk.main () > /usr/lib/pymodules/python2.6/reportbug/ui/gtk2_ui.py:476: PangoWarning: > pango_layout_get_line_count: assertion `layout != NULL' failed > gtk.main () > Floating point exception sadly it's a known situation - I'm reassigning this bug to the relevant package. Thanks for your time and patience, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
