Your message dated Thu, 21 Jun 2012 17:41:02 +0200
with message-id <[email protected]>
and subject line
has caused the Debian Bug report #641461,
regarding geany: Crashes when opening a second file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
641461: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641461
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: geany
Version: 0.20-1.1
Severity: important
Hi!
Geany crashes when opening a second file. To reproduce:
Open any file. While it is open, select "Open" from the "File" menu.
Geany crashes!
Running it from the terminal gives the following error message:
tmac@asus:~$ geany
**
Gtk:ERROR:/scratch/build-area/gtk+2.0-2.24.6/gtk/gtkfilechooserdefault.c:8764:gtk_file_chooser_default_initial_focus:
assertion failed: (widget != NULL)
Aborted
Best regards
Torquil Sørensen
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (700, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.4 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages geany depends on:
ii libatk1.0-0 2.0.1-2
ii libc6 2.13-20
ii libcairo2 1.10.2-6.1
ii libfontconfig1 2.8.0-3
ii libfreetype6 2.4.6-2
ii libgcc1 1:4.6.1-10
ii libgdk-pixbuf2.0-0 2.24.0-1
ii libglib2.0-0 2.28.6-1
ii libgtk2.0-0 2.24.6-1
ii libpango1.0-0 1.28.4-3
ii libstdc++6 4.6.1-10
geany recommends no packages.
Versions of packages geany suggests:
ii doc-base <none>
ii libvte9 1:0.28.1-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.21.dfsg-1
Was probably a GTK+ bug and a workaround should have been released (was in SVN
afer 0.20). If the bug persists, feel free to reopen it.
--
Jonathan Michalon
IT student in Strasbourg
--- End Message ---