tinyerp-client doesn't start

Bug #179087 reported by booyo
60
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tinyerp-client (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by ClonedAgain

Bug Description

Binary package hint: tinyerp-client

bash$ tinyerp-client
Traceback (most recent call last):
  File "./tinyerp-client.py", line 93, in ?
    import modules
  File "/usr/lib/tinyerp-client/modules/__init__.py", line 30, in ?
    import gui
  File "/usr/lib/tinyerp-client/modules/gui/__init__.py", line 29, in ?
    import main
  File "/usr/lib/tinyerp-client/modules/gui/main.py", line 40, in ?
    import rpc
  File "/usr/lib/tinyerp-client/rpc.py", line 37, in ?
    import common
  File "/usr/lib/tinyerp-client/common/__init__.py", line 29, in ?
    from common import *
  File "/usr/lib/tinyerp-client/common/common.py", line 67, in ?
    TINYERP_ICON = gtk.gdk.pixbuf_new_from_file(terp_path_pixmaps('tinyerp-icon-32x32.png'))
TypeError: pixbuf_new_from_file() argument 1 must be string, not bool

installed from package

Revision history for this message
dukaa (duka-arpad) wrote :

Same problem in Hardy Heron i386.

Revision history for this message
tschentz (j-haeuser) wrote :

same error here, Hardy i386

Revision history for this message
vanhammersly (michnaugh1) wrote :

Same. Hardy, i386.

Revision history for this message
didi (db-urorg) wrote :

hi haf fix it:
you must install a older version like 4.0* and copy the /usr/share/pixmaps/tinyerp-client to (example) home directory.
remove your version 4.0*
after install the 4.2 version, you copy the tinyerp-client directory to the /usr/share/pixmaps/ !
thats it
sorry for my bad english ;)

i give the copy from the direktory to the attacment, so you dont need to install a older version, just copy to /usr/share/pixmaps/!

Revision history for this message
didi (db-urorg) wrote :

please unpack!! is importent!

lg
didi

Changed in tinyerp-client:
status: New → Confirmed
Revision history for this message
Schmirrwurst (schmirrwurst) wrote :

This fix worked for me

Revision history for this message
www.mgazelle.com (mgazelle) wrote :

This worked for me as well.
Thank you

Revision history for this message
fuzzyBSc (benjamincarlyle-soundadvice) wrote :

Confirmed: Hardy amd64. Fix seems to work.

Revision history for this message
Eric Morey (eric-glodime) wrote :

I have the same problem with package version tinyerp-client 4.2.0-1 in gNewSense 2.1 (Hardy i386). The current stable versions of tinyerp-client and tinyerp-server are 4.2.3.3. Can the package maintainer provide the current versions in the repository? I don't know if this problem persists in the current stable version.

Bug #273275 filed with OpenERP at https://bugs.launchpad.net/openerp/+bug/273275

Revision history for this message
KarlGoetz (kgoetz) wrote :

Eric,
The package wont be updated to the latest version, but the fix (which i suspect is some missing artwork or similar) can be.

My suspicion is that the pixmaps are getting installed somewhere that the tool isn't looking for them.

Could someone run `locate tinyerp-icon-32x32.png` and paste the output in this bug?

Thanks

Revision history for this message
KarlGoetz (kgoetz) wrote :

Think i spotted the problem - doing a test build now.

Revision history for this message
Gil/Ulises (iulisesq) wrote :

muito obrigado/Gracias/Thanks didi.
It worked perfect in my Hardy Heron 8.04 (on a Thinkpad T30)
Now I don't even need to run the server from Terminal...
Great Job!!!...

Revision history for this message
cuc (cuc+) wrote :

problem seems to be missing *.png files and falsly generated path in config file..
here is quick & dirty fix for hardy package tinyerp-client 4.2.0-1

~$ vi .terprc

[path]
pixmaps = /usr/share/pixmaps/tinyerp-client/

change to

[path]
pixmaps = /usr/share/tinyerp-client/

~$ cd /usr/share/tinyerp-client/
. $ sudo cp tinyerp_icon.png tinyerp-icon-32x32.png
. $ sudo mkdir icons
. $ sudo touch noimage.png

hope that helps

Revision history for this message
rohit (thakralrohit) wrote : Re: [Bug 179087] Re: tinyerp-client doesn't start

thanks cuc.

regards
rohit

On Fri, Oct 3, 2008 at 4:51 PM, cuc <email address hidden> wrote:

> problem seems to be missing *.png files and falsly generated path in config
> file..
> here is quick & dirty fix for hardy package tinyerp-client 4.2.0-1
>
> ~$ vi .terprc
>
> [path]
> pixmaps = /usr/share/pixmaps/tinyerp-client/
>
> change to
>
> [path]
> pixmaps = /usr/share/tinyerp-client/
>
>
> ~$ cd /usr/share/tinyerp-client/
> . $ sudo cp tinyerp_icon.png tinyerp-icon-32x32.png
> . $ sudo mkdir icons
> . $ sudo touch noimage.png
>
> hope that helps
>
> --
> tinyerp-client doesn't start
> https://bugs.launchpad.net/bugs/179087
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "tinyerp-client" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: tinyerp-client
>
> bash$ tinyerp-client
> Traceback (most recent call last):
> File "./tinyerp-client.py", line 93, in ?
> import modules
> File "/usr/lib/tinyerp-client/modules/__init__.py", line 30, in ?
> import gui
> File "/usr/lib/tinyerp-client/modules/gui/__init__.py", line 29, in ?
> import main
> File "/usr/lib/tinyerp-client/modules/gui/main.py", line 40, in ?
> import rpc
> File "/usr/lib/tinyerp-client/rpc.py", line 37, in ?
> import common
> File "/usr/lib/tinyerp-client/common/__init__.py", line 29, in ?
> from common import *
> File "/usr/lib/tinyerp-client/common/common.py", line 67, in ?
> TINYERP_ICON =
> gtk.gdk.pixbuf_new_from_file(terp_path_pixmaps('tinyerp-icon-32x32.png'))
> TypeError: pixbuf_new_from_file() argument 1 must be string, not bool
>
>
> installed from package
>

Revision history for this message
james begg (jbegg) wrote :

cuc's solution worked for me too... thanx

Revision history for this message
Bruno Lambert (bruno.lambert) wrote :

It now works on Intrepid. I've only installed the package on a Intrepid install, which never has tinyerp on it, and it work.

Revision history for this message
Eric Morey (eric-glodime) wrote :

On Fri, 2008-10-03 at 15:51 +0000, cuc wrote:
> problem seems to be missing *.png files and falsly generated path in config file..
> here is quick & dirty fix for hardy package tinyerp-client 4.2.0-1
>

I don't know what all of that code means. Is there a way to get a nice clean implementation of a fix in the repository?

Revision history for this message
KarlGoetz (kgoetz) wrote :

On Thu, October 9, 2008 09:15, Bruno Lambert wrote:
> It now works on Intrepid. I've only installed the package on a Intrepid
> install, which never has tinyerp on it, and it work.
>
> --
> tinyerp-client doesn't start
> https://bugs.launchpad.net/bugs/179087
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The bug doesnt affect 8.10.
kk

Revision history for this message
Crumplerdude (martin-crumpler) wrote :

cuc's workaround worked for us too.
We are running kubuntu 8.04, and the TinyERP client now starts within KDE - which is great!

Revision history for this message
Christophe Simonis (OpenERP) (kangol) wrote :

need new deb package with the last stable version.

The original maintainer is Daniel Baumann <email address hidden>

Revision history for this message
Stéphane Graber (stgraber) wrote :

This bug has been fixed in Intrepid and hasn't reappeared since then.
Please file a SRU request or backport request for fixing in previous releases adding a task for $release-updates so it can go through the SRU process.

Closing the bug as fix relesaed (as fixed in the current development version and previous stable)

Changed in tinyerp-client:
status: Confirmed → Fix Released
Revision history for this message
Eric Morey (eric-glodime) wrote :

On Sun, 2009-03-15 at 00:51 +0000, Stéphane Graber wrote:
> This bug has been fixed in Intrepid and hasn't reappeared since then.
> Please file a SRU request or backport request for fixing in previous releases adding a task for $release-updates so it can go through the SRU process.
>
> Closing the bug as fix relesaed (as fixed in the current development
> version and previous stable)
>
> ** Changed in: tinyerp-client (Ubuntu)
> Status: Confirmed => Fix Released
>

I'm a bit confused. Is a stable release update or backport the best or
easiest way to deal with a package that does not install properly, but
otherwise works with a workaround? Having the new features I'm sure
would be nice, but that is not a primary concern of a LTS release like
8.04 (Hardy).

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.