Zim

[zim 0.28] Can't launch zim under jaunty 64-bit as a simple user

Bug #433704 reported by Νίκος Αλεξανδρής
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zim
Won't Fix
Low
Unassigned
Perl-zim
Won't Fix
Medium
Unassigned

Bug Description

I can't get zim (0.28) to work as a simple user under Ubuntu Jaunty 64-bit. I get the following message:
Can't call method "file" without a package or object reference at /usr/share/perl5/Zim/Store/Cached.pm line 47.

"zim -D" reports the following:
--%<--
## FS read: /home/nik/.config/zim/notebooks.list
## FS read: /home/nik/.config/zim/notebooks.list
## Got notebook: /home/nik/Notes/
# No daemon listening .. let's start one
# locale: en_US.UTF-8
# This is zim 0.28
# Gtk2 version is 1.190
# compiled against gtk+ 2.14.5
# linked against gtk+ 2.16.1
# Notebook path = /home/nik/Notes/
# page =
## Daemon: Forked client with PID 13080
## Daemon: Listening at PID 13078
Xlib: extension "RANDR" missing on display ":0.0".
## FS read: /home/nik/Notes/notebook.zim
# Store does not use version control
# Adding store of type 'Files' at ':'
## ':' using dir: /home/nik/Notes/
Can't call method "file" without a package or object reference at /usr/share/perl5/Zim/Store/Cached.pm line 47.
## Daemon: Client with PID 13080 exited
## Daemon: Last client exited
## Daemon: Exiting
--%<--

Launching zim as a superuser gives no problem/error message. Is this a bug?

Thanks, Nikos

Tags: 64-bit jaunty zim
summary: - Can't launch zim under jaunty 64-bit as a simple user
+ [zim 0.28] Can't launch zim under jaunty 64-bit as a simple user
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Reason for the difference when logged in as superuser is that this bug happens in the "cached" mode for the notebook. As superuser you have access to the notebook so this cached interface is not used.

Changed in zim:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Jaap Karssenberg (jaap.karssenberg) wrote :

Set this bug to "won't fix" since zim version 0.28 is outdated and no one is working on the perl version anymore. I believe this issue is not present in the current version of zim (0.4x) if it is please open a new report.

Changed in zim:
status: Confirmed → Won't Fix
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.