Pybliographer doesn't start

Bug #29484 reported by Erich Pawlik
14
Affects Status Importance Assigned to Milestone
pybliographer (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Pybliographer doesn't start after installation. When called from the menu, after a "please wait" cursor, nothing happens. When called from a command window, the output is:

Traceback (most recent call last):
  File "/usr/bin/pybliographer", line 35, in ?
    locale.setlocale (locale.LC_ALL, '')
  File "/usr/lib/python2.4/locale.py", line 381, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting

Possibly useful environment variables:

LANG=POSIX.UTF-8
LANGUAGE=POSIX

LC_ALL has not been set.

Regards

Erich

Revision history for this message
Erich Pawlik (erichpawlik) wrote :

With

export LC_:ALL=C
pybliographer

it is possible to start pybliographer from the command line.

description: updated
description: updated
Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

Thanks for the bug report. Could you tell which version of Ubuntu and pybliographer you are running?

I can't reproduce this bug with pybliographer 1.2.6.2-1ubuntu1 on dapper.

Changed in pybliographer:
assignee: nobody → motu
Revision history for this message
Erich Pawlik (erichpawlik) wrote :

I am using pybliographer 1.2.6.2-1ubuntu1, I don't know whether I found the bug on this version or an earlier one (I am always applying the most recent updates).

The problem has gone away on my machines. A guess (however I don't know how to set up a test to check whether the guess is Ok) is that the problem disappeared after I manually set the default language in System -> Language Selector to English (UK). The environment variables now are:

LANG=en_GB.UTF-8
LANGUAGE=en_GB:en

I can reproduce the error by entering

export LANG=POSIX.UTF-8
export LANGUAGE=POSIX
pybliographer

in a terminal window. Those were the settings after the Dapper installation (language=English (US), keyboard=German, location/time zone=Berlin).

Regards

Erich

Revision history for this message
Gauvain Pocentek (gpocentek) wrote :

This bug looks fixed, but feel free to reopen if it's still present.

Changed in pybliographer:
status: Unconfirmed → Fix Released
Revision history for this message
Erich Pawlik (erichpawlik) wrote :

reopened as bug #38706

Revision history for this message
William Grant (wgrant) wrote :

This bug is still present in the latest Feisty version.

Changed in pybliographer:
assignee: motu → nobody
status: Fix Released → Confirmed
Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote :

Erich, is this still a problem in Ubuntu 7.10 (gutsy) or the current development release hardy?

Changed in pybliographer:
assignee: nobody → pascal-devuyst
status: Confirmed → Incomplete
Revision history for this message
Matt Neilson (ichthyoboy) wrote :

I can confirm that this bug is still present in Gutsy.

Changed in pybliographer:
status: Incomplete → Confirmed
Changed in pybliographer:
assignee: pascal-devuyst → nobody
Revision history for this message
Aanjhan Ranganathan (aanjhan) wrote :

Still present in Hardy.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Lowering importance due to known workaround.

Changed in pybliographer:
importance: Medium → Low
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.