Version 0.0.3.3-1ubuntu1 fails to start

Bug #869315 reported by Alin Andrei
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
CryptFolder-Indicator
Fix Released
High
Lorenzo Carbonell

Bug Description

The latest CryptFolder-Indicator 0.0.3.3-1ubuntu1 fails to start for me (Ubuntu 11.04 32bit):

andrei@andrei-desktop:~/Desktop$ cryptfolder-indicator
Traceback (most recent call last):
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 41, in <module>
    import crypto
  File "/usr/share/cryptfolder-indicator/crypto.py", line 33, in <module>
    from createenfs import CreateEncfs
  File "/usr/share/cryptfolder-indicator/createenfs.py", line 41, in <module>
    log = open('/home/atareao/log1.log','w')
IOError: [Errno 2] No such file or directory: '/home/atareao/log1.log'

Revision history for this message
luis longueira (luis.longueira) wrote :

Same problem.

~$ cryptfolder-indicator
Gtk-Message: Failed to load module "canberra-gtk-module"
Traceback (most recent call last):
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 41, in <module>
    import crypto
  File "/usr/share/cryptfolder-indicator/crypto.py", line 33, in <module>
    from createenfs import CreateEncfs
  File "/usr/share/cryptfolder-indicator/createenfs.py", line 41, in <module>
    log = open('/home/atareao/log1.log','w')
IOError: [Errno 2] No existe el fichero o el directorio: '/home/atareao/log1.log'

Ubuntu 11.04 32 bit

Revision history for this message
sokai (sokai) wrote :

This bug affects me, too. And I use Ubuntu 11.04 32 bit, too.

I've seen that you fixed it: http://bazaar.launchpad.net/~atareao/cryptfolder-indicator/0.1/revision/23 . - When there will be a package update?

Best regards!

Revision history for this message
Lorenzo Carbonell (lorenzo-carbonell) wrote :

Please, try it again. Thanks!!!

Revision history for this message
Alin Andrei (nilarimogard) wrote :

It still doesn't work:

cryptfolder-indicator
No LSB modules are available.
#####################################################
Distributor ID: Ubuntu
Description: Ubuntu 11.04
Release: 11.04
Codename: natty
Version: i686
#####################################################

CryptFolder-Indicator version: 0.0.3.4
#####################################################
0
`menu_proxy_module_load': /usr/bin/python: undefined symbol: menu_proxy_module_load

(cryptfolder-indicator.py:28650): Gtk-WARNING **: Failed to load type module: (null)

Traceback (most recent call last):
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 250, in <module>
    cfi=CryptFolderIndicator()
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 87, in __init__
    self.set_menu()
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 149, in set_menu
    add2menu(self.menu, text = folder['path'], icon = image, conector_event = 'activate', conector_action = self.on_path_clicked)
  File "/usr/share/cryptfolder-indicator/cryptfolder-indicator.py", line 61, in add2menu
    menu_item = Gtk.ImageMenuItem(text)
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

Revision history for this message
luis longueira (luis.longueira) wrote :

With version 0.0.3.4 I get the same error in the terminal that happens to andrei

Revision history for this message
sokai (sokai) wrote :

Hi!

I have filed a new bug for the new behavior in 0.0.3.4 here: https://bugs.launchpad.net/cryptfolder-indicator/+bug/870513
It has nothing to do with the original bug and has a new version number. Please add your comments there!

This bug (0.0.3.3) is fixed for me an can be closed! :)

Thanks!

Revision history for this message
luis longueira (luis.longueira) wrote :

Version 0.0.3.6 fixed this bug thanks :)

Changed in cryptfolder-indicator:
status: New → Fix Released
status: Fix Released → Fix Committed
importance: Undecided → High
assignee: nobody → Lorenzo Carbonell (lorenzo-carbonell)
sokai (sokai)
Changed in cryptfolder-indicator:
status: Fix Committed → Fix Released
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.