transmission crashed with SIGSEGV in g_type_check_instance_is_a()

Bug #192515 reported by Krzemo
10
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: transmission

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION="Ubuntu hardy (development branch)"

ii transmission-common 1.05-0ubuntu1 free, lightweight BitTorrent client
ii transmission-gtk 1.05-0ubuntu1 free, lightweight BitTorrent client (graphic

When i want to change my download directory and save the settings.

ProblemType: Crash
Architecture: i386
Date: Sun Feb 17 00:23:02 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/transmission
NonfreeKernelModules: cdrom
Package: transmission-gtk 1.05-0ubuntu1
PackageArchitecture: i386
ProcCmdline: transmission
ProcCwd: /home/krzemo
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: transmission
StacktraceTop:
 g_type_check_instance_is_a ()
 g_file_get_path () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/gtk-2.0/2.10.0/filesystems/libgio.so
 ?? ()
 ?? ()
Title: transmission crashed with SIGSEGV in g_type_check_instance_is_a()
Uname: Linux krzemo 2.6.24-8-generic #1 SMP Thu Feb 14 20:40:45 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev video

Revision history for this message
Krzemo (krzemoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in transmission:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in transmission:
status: Incomplete → 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.