Debian Bug report logs -
#396653
listen: Fails to start with home over NFS
Toggle useless messages
Report forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>:
New Bug report received and forwarded. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, reply):
Package: listen
Version: 0.4.3-1
Severity: grave
Justification: renders package unusable
When home is mounted over NFS, listen fails to start with the following
backtrace:
Traceback (most recent call last):
File "/usr/bin/listen", line 409, in ?
Listen()
File "/usr/bin/listen", line 136, in __init__
self.run()
File "/usr/bin/listen", line 255, in run
from player import Player
File "/usr/lib/listen/player.py", line 35, in ?
from misc_widget import VolumeSlider
File "/usr/lib/listen/misc_widget.py", line 319, in ?
from podcast_manager import PodcastManager
File "/usr/lib/listen/podcast_manager.py", line 31, in ?
from db_manager import DBManager
File "/usr/lib/listen/db_manager.py", line 681, in ?
DBManager = ListenDBManager(True)
File "/usr/lib/listen/db_manager.py", line 39, in __init__
self.db = ListenDB(check_exist)
File "/usr/lib/listen/db_manager.py", line 519, in __init__
self.cur.execute( requete_songs_view )
pysqlite2.dbapi2.OperationalError: no such table: main.Media
When setting HOME to a directory located on a local filesystem, listen
starts normally.
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-vserver-amd64-k8
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages listen depends on:
ii gstreamer0.10-alsa 0.10.10-1 GStreamer plugin for ALSA
ii gstreamer0.10-plugins-base 0.10.10-1 GStreamer plugins from the "base"
ii gstreamer0.10-plugins-good 0.10.4-3 GStreamer plugins from the "good"
ii libatk1.0-0 1.12.3-1 The ATK accessibility toolkit
ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries
ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra
ii libfontconfig1 2.4.1-2 generic font configuration library
ii libglib2.0-0 2.12.4-1 The GLib library of C routines
ii libgtk2.0-0 2.8.20-3 The GTK+ graphical user interface
ii libpango1.0-0 1.14.7-1 Layout and rendering of internatio
ii libx11-6 2:1.0.3-2 X11 client-side library
ii libxcursor1 1.1.7-4 X cursor management library
ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.1-4 X11 miscellaneous 'fixes' extensio
ii libxi6 1:1.0.1-3 X11 Input extension library
ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library
ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library
ii libxrender1 1:0.9.1-3 X Rendering Extension client libra
ii python 2.4.4-1 An interactive high-level object-o
ii python-central 0.5.9 register and build utility for Pyt
ii python-dbus [python2.4-dbus] 0.71-3 simple interprocess messaging syst
ii python-gnome2 2.12.4-5 Python bindings for the GNOME desk
ii python-gnome2-extras 2.14.2-1+b1 Python bindings for the GNOME desk
ii python-gst0.10 0.10.5-5 generic media-playing framework (P
ii python-gtk2 2.8.6-6 Python bindings for the GTK+ widge
ii python-pymad 0.5.4-3.2 Python wrapper to the MPEG Audio D
ii python-pyogg 1.3-1.1 A Python interface to the Ogg libr
ii python-pysqlite2 2.3.2-1 python interface to SQLite 3
ii python-pyvorbis 1.3-1.2 A Python interface to the Ogg Vorb
ii python2.4 2.4.4-1 An interactive high-level object-o
Versions of packages listen recommends:
ii gstreamer0.10-esd 0.10.4-3 GStreamer plugin for ESD
ii gstreamer0.10-x 0.10.10-1 GStreamer plugins for X11 and Pang
ii serpentine 0.7-4 An application for creating audio
-- no debconf information
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to <julien@hathor.kirya.net>:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #10 received at 396653@bugs.debian.org (full text, mbox, reply):
package listen
forwarded 396653 http://sourceforge.net/tracker/?group_id=161415&atid=819743
thanks
Hi,
Thank you for your report. I have forwarded this upstream as it is a bug in the core engine of listen.
As I have not the possibility to test home over NFS, I will surely ask you kindly to test workarounds proposed by upstream.
Cheers,
Julien
Tags added: upstream
Request was from <julien@hathor.kirya.net>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to "Steinar H. Gunderson" <sgunderson@bigfoot.com>:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #21 received at 396653@bugs.debian.org (full text, mbox, reply):
On Wed, Nov 01, 2006 at 08:46:53PM -0300, Thadeu Lima de Souza Cascardo wrote:
> When home is mounted over NFS, listen fails to start with the following
> backtrace:
I've got home over NFS (actually, _everything_ over NFS) and listen starts
perfectly for me (both first and subsequent times). I've tested on two
different machines against two different servers, and no go... Are you sure
this is really the problem in question?
/* Steinar */
--
Homepage: http://www.sesse.net/
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to cascardo@minaslivre.org:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #26 received at 396653@bugs.debian.org (full text, mbox, reply):
On Tue, Nov 14, 2006 at 12:24:01AM +0100, Steinar H. Gunderson wrote:
> On Wed, Nov 01, 2006 at 08:46:53PM -0300, Thadeu Lima de Souza Cascardo wrote:
> > When home is mounted over NFS, listen fails to start with the following
> > backtrace:
>
> I've got home over NFS (actually, _everything_ over NFS) and listen starts
> perfectly for me (both first and subsequent times). I've tested on two
> different machines against two different servers, and no go... Are you sure
> this is really the problem in question?
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
What I am sure about is that setting HOME environment variable to a
directory not located over NFS and then executing listen does not get me
that error. And I have setups where my home is not over NFS and listen
works OK.
Two different setups (one, in fact, was Ubuntu, the other, Debian
unstable) where home was over NFS gave me errors related to pysqlite.
Perhaps, we could try a simple pysqlite code that can give this same
error.
Or perhaps there is something about our NFS server setup. Mine was using
the kernel server, because it has lock support (and its lack would be the
first thing I would point as the reason for the errors).
Any tests I can try? The setup is on a lab which I may have some remote
access (I will not be there until next week).
Regards,
Thadeu Cascardo.
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to "Steinar H. Gunderson" <sgunderson@bigfoot.com>:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #31 received at 396653@bugs.debian.org (full text, mbox, reply):
On Mon, Nov 13, 2006 at 10:22:21PM -0200, cascardo@minaslivre.org wrote:
> What I am sure about is that setting HOME environment variable to a
> directory not located over NFS and then executing listen does not get me
> that error. And I have setups where my home is not over NFS and listen
> works OK.
What happens if you first move away your .listen directory? It's entirely
possible that yours became corrupt for some reason and mine didn't.
> Or perhaps there is something about our NFS server setup. Mine was using
> the kernel server, because it has lock support (and its lack would be the
> first thing I would point as the reason for the errors).
I'm using the NFS kernel server, too. I don't think anybody uses the NFS user
server anymore; it hasn't been developed for years either.
> Any tests I can try? The setup is on a lab which I may have some remote
> access (I will not be there until next week).
In general, I'd try to isolate if this is a feature of your NFS setup in
general, or your specific .listen directory (probably media.db). What happens
if you copy the .listen directory to somewhere on non-NFS, set $HOME to that
place and the run listen? Also, does this happen _every_ time or can you run
listen a few times before the database goes bonkers? You don't access the
database from multiple hosts at the same time, do you?
/* Steinar */
--
Homepage: http://www.sesse.net/
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to cascardo@minaslivre.org:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #36 received at 396653@bugs.debian.org (full text, mbox, reply):
On Tue, Nov 14, 2006 at 01:46:10AM +0100, Steinar H. Gunderson wrote:
>
> What happens if you first move away your .listen directory? It's entirely
> possible that yours became corrupt for some reason and mine didn't.
>
> I'm using the NFS kernel server, too. I don't think anybody uses the NFS user
> server anymore; it hasn't been developed for years either.
>
> In general, I'd try to isolate if this is a feature of your NFS setup in
> general, or your specific .listen directory (probably media.db). What happens
> if you copy the .listen directory to somewhere on non-NFS, set $HOME to that
> place and the run listen? Also, does this happen _every_ time or can you run
> listen a few times before the database goes bonkers? You don't access the
> database from multiple hosts at the same time, do you?
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
I could not run listen one single time while HOME was over NFS. I may
try these (removing .listen and trying it again over NFS and moving
.listen to a non-NFS filesystem and running listen over ther), but I
don't think there would be any results. As soon as I do these, I'll post
again with the results. Since I have a second machine now, I may even
try this at home (no pun intended) and see if I get the same results.
Regards,
Thadeu Cascardo.
Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to Julien Valroff <julien@kirya.net>:
Extra info received and forwarded to list.
(full text, mbox, link).
Message #41 received at 396653@bugs.debian.org (full text, mbox, reply):
package: listen
tags 396653 + moreinfo unreproducible
thanks
Le lundi 13 novembre 2006 à 23:34 -0200, cascardo@minaslivre.org a
écrit :
[...]
> I could not run listen one single time while HOME was over NFS. I may
> try these (removing .listen and trying it again over NFS and moving
> listen to a non-NFS filesystem and running listen over ther), but I
> don't think there would be any results. As soon as I do these, I'll post
> again with the results. Since I have a second machine now, I may even
> try this at home (no pun intended) and see if I get the same results.
Hi,
I have been able to launch listen with home over NFS (tested with NFS
server in both Sarge and Unstable, with both clients in Etch and
Unstable).
Please try the proposed tests to check if your .listen is corrupted or
not.
Thanks for your help
Cheers,
Julien
Tags added: moreinfo, unreproducible
Request was from Julien Valroff <julien@kirya.net>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to "Steinar H. Gunderson" <sgunderson@bigfoot.com>:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #48 received at 396653@bugs.debian.org (full text, mbox, reply):
severity 396653 important
thanks
On Tue, Nov 14, 2006 at 07:13:43PM +0100, Julien Valroff wrote:
> I have been able to launch listen with home over NFS (tested with NFS
> server in both Sarge and Unstable, with both clients in Etch and
> Unstable).
>
> Please try the proposed tests to check if your .listen is corrupted or
> not.
Since nobody else can reproduce this, I've been given permission from the RMs
to downgrade the bug.
/* Steinar */
--
Homepage: http://www.sesse.net/
Severity set to `important' from `grave'
Request was from "Steinar H. Gunderson" <sgunderson@bigfoot.com>
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to Julien Valroff <julien@kirya.net>:
Extra info received and forwarded to list.
(full text, mbox, link).
Message #55 received at 396653@bugs.debian.org (full text, mbox, reply):
Le mardi 14 novembre 2006 à 00:24 +0100, Steinar H. Gunderson a écrit :
> On Wed, Nov 01, 2006 at 08:46:53PM -0300, Thadeu Lima de Souza Cascardo wrote:
> > When home is mounted over NFS, listen fails to start with the following
> > backtrace:
>
> I've got home over NFS (actually, _everything_ over NFS) and listen starts
> perfectly for me (both first and subsequent times). I've tested on two
> different machines against two different servers, and no go... Are you sure
> this is really the problem in question?
Hi,
WRT this bug, do you have any news?
Can you please detail your NFS setup so that we can try reproducing the
bug?
With no answer from you, I will close the bug.
Cheers,
Julien
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to cascardo@minaslivre.org:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #60 received at 396653@bugs.debian.org (full text, mbox, reply):
On Sat, Jan 27, 2007 at 11:13:14AM +0100, Julien Valroff wrote:
> Le mardi 14 novembre 2006 ?? 00:24 +0100, Steinar H. Gunderson a ??crit :
> > On Wed, Nov 01, 2006 at 08:46:53PM -0300, Thadeu Lima de Souza Cascardo wrote:
> > > When home is mounted over NFS, listen fails to start with the following
> > > backtrace:
> >
> > I've got home over NFS (actually, _everything_ over NFS) and listen starts
> > perfectly for me (both first and subsequent times). I've tested on two
> > different machines against two different servers, and no go... Are you sure
> > this is really the problem in question?
>
> Hi,
>
> WRT this bug, do you have any news?
>
> Can you please detail your NFS setup so that we can try reproducing the
> bug?
>
> With no answer from you, I will close the bug.
>
> Cheers,
> Julien
>
Hello,
I've just tested it on a different setup. Instead of getting the same
error as I've got before, listen simply takes forever to start.
This time I've tried harder to fix it. Installing nfs-common in the
client solved the problem. I was able to start listen with home over
NFS.
Would this be worth a note in README.Debian?
Thanks,
Thadeu Cascardo.
Severity set to `wishlist' from `important'
Request was from cascardo@holoscopio.com (Thadeu Lima de Souza Cascardo)
to control@bugs.debian.org.
(full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Julien Valroff <julien@kirya.net>:
Bug#396653; Package listen.
(full text, mbox, link).
Acknowledgement sent to "Steinar H. Gunderson" <sgunderson@bigfoot.com>:
Extra info received and forwarded to list. Copy sent to Julien Valroff <julien@kirya.net>.
(full text, mbox, link).
Message #67 received at 396653@bugs.debian.org (full text, mbox, reply):
On Sun, Jan 28, 2007 at 11:35:58AM -0200, cascardo@minaslivre.org wrote:
> I've just tested it on a different setup. Instead of getting the same
> error as I've got before, listen simply takes forever to start.
>
> This time I've tried harder to fix it. Installing nfs-common in the
> client solved the problem. I was able to start listen with home over
> NFS.
Urm, if you don't have nfs-common installed, I'm surprised you can mount NFS
shares at all. I'd simply close this with "user error"; it's a basic
misconfiguration which has nothing to do with listen.
/* Steinar */
--
Homepage: http://www.sesse.net/
Reply sent to <julien@hathor.kirya.net>:
You have taken responsibility.
(full text, mbox, link).
Notification sent to Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>:
Bug acknowledged by developer.
(full text, mbox, link).
Message #72 received at 396653-done@bugs.debian.org (full text, mbox, reply):
Hi,
Given the new elements, it seems the issue has nothing to do with listen, and
I am thus closing the bug.
Feel free to re-open it if you are absolutely sure it is a problem in listen.
Cheers,
Julien
Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Mon, 18 Jun 2007 08:30:15 GMT) (full text, mbox, link).
Send a report that this bug log contains spam.
Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Sat Apr 15 20:27:59 2023;
Machine Name:
buxtehude
Debian Bug tracking system
Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.