Bug#520965: fails to start with Segmentation fault
On Thu, 26 Mar 2009 18:50:40 +1100 Ben Finney wrote: > package deluge > severity 520965 important > retitle 520965 deluge: segfault if locale is not using UTF-8 encoding > tags 520965 moreinfo > thanks > > On 25-Mar-2009, Konstantin Kostadinov wrote: > > You are right, that solves the problem with faulty start. > > It is work now with en_US.UTF-8 > > Can you report (here in this bug report) what the locale was that led > to the segfault? > > Though there is now a workaround, the program should never crash > regardless of the locale. I'm changing the severity to ‘important’ > because of this. > I'v tried with some other locales, and the result is : bg_BG - segfault bg_BG.UTF-8 - starting fine ru_RU.CP1251 - segfault ru_RU.KOI8-R - segfault ru_RU.UTF-8 - starting fine en_US - starting fine en_US.UTF-8 - starting fine So the final conclusion is that the Cyrillic alphabet characters locales without UTF support in it, makes deluge to segfault. The workaround for this, is to use locale with UTF support, like some_area.UTF-8 ( bg_BG.UTF-8, ru_RU.UTF-8 ) It is possible the affected locales (without .UTF-8 part) to be all locales that do not use latin alphabet. The program should work stable if you use Latin based locale, or non Latin one with .UTF-8 part of the locale set. Thanks again for the help ! ;-) -- Konstantin Kostadinov pgp key : F2C41D57 : at : subkeys.pgp.net BOFH excuse #261: The Usenet news is out of date signature.asc Description: PGP signature
Bug#520965: fails to start with Segmentation fault
package deluge severity 520965 important retitle 520965 deluge: segfault if locale is not using UTF-8 encoding tags 520965 moreinfo thanks On 25-Mar-2009, Konstantin Kostadinov wrote: > You are right, that solves the problem with faulty start. > It is work now with en_US.UTF-8 Can you report (here in this bug report) what the locale was that led to the segfault? Though there is now a workaround, the program should never crash regardless of the locale. I'm changing the severity to ‘important’ because of this. -- \ “Man cannot be uplifted; he must be seduced into virtue.” | `\ —Donald Robert Perry Marquis | _o__) | Ben Finney signature.asc Description: Digital signature
Bug#520965: fails to start with Segmentation fault
You are right, that solves the problem with faulty start. It is work now with en_US.UTF-8 Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#520965: fails to start with Segmentation fault
On Tue, Mar 24, 2009 at 01:22:39AM +0200, Konstantin wrote: > Package: deluge > Version: 1.1.5+dfsg-1 > Severity: grave > Justification: renders package unusable > > > After dist-upgrade on home and office machine, deluge fails to start with > Segmentation fault. > > Copy paste: > -cut- > :~$ deluge > 1.1.5 > /var/lib/python-support/python2.5/deluge/ui/gtkui/mainwindow.py:51: > GtkWarning: Invalid input string > "glade/main_window.glade")) > Segmentation fault > -cut- Hi, this seems to be a problem with your locale, please try using one with UTF8 support. Thanks, -- Cristian Greco GPG key ID: 0x0C095825 signature.asc Description: Digital signature
Bug#520965: fails to start with Segmentation fault
Package: deluge Version: 1.1.5+dfsg-1 Severity: grave Justification: renders package unusable After dist-upgrade on home and office machine, deluge fails to start with Segmentation fault. Copy paste: -cut- :~$ deluge 1.1.5 /var/lib/python-support/python2.5/deluge/ui/gtkui/mainwindow.py:51: GtkWarning: Invalid input string "glade/main_window.glade")) Segmentation fault -cut- On the office machine, the arch is amd64, with sid again, and the situation is the same. I'v tried to deinstall with --purge all deluge packages, and install it again with no success. Removing the ~/.config/deluge dir is done, withoud succsess again. After download the development version from deluge site subversion repository, and compile it, the error was the same. ( new development version was installed, after purging debian packages with dpkg ). Downgrading deluge packages to 0.5.9.3 was with success, and deluge starts without problems. There is no more ideas from me, if you get some, i'll try it. Thanks -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.27.8 (SMP w/2 CPU cores) Locale: LANG=bg_BG, LC_CTYPE=bg_BG (charmap=CP1251) Shell: /bin/sh linked to /bin/bash Versions of packages deluge depends on: ii dbus-x111.2.12-1 simple interprocess messaging syst ii deluge-common 1.1.5+dfsg-1 bittorrent client written in Pytho ii librsvg2-common 2.22.3-2 SAX-based renderer library for SVG ii notification-daemon 0.4.0-1 a daemon that displays passive pop ii python 2.5.4-2 An interactive high-level object-o ii python-dbus 0.83.0-1 simple interprocess messaging syst ii python-glade2 2.14.1-1 GTK+ bindings: Glade support ii python-notify 0.1.1-2+b1 Python bindings for libnotify ii python-support 0.8.7automated rebuilding support for P deluge recommends no packages. deluge suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
