first login on ltsp client fails due to missing gstreamer database

Bug #66808 reported by Oliver Grawert
2
Affects Status Importance Assigned to Milestone
ltsp (Ubuntu)
Fix Released
High
Oliver Grawert

Bug Description

the 80_ltsp-sound runs:
rm $HOME/.gstreamer-0.10/registry.*.xml
to flush the gstreamer audiosink database and force a regeneration to make the ltspsudiosink take effect.
if the file doesnt exist this makes the login fail. a user needs to log in on the server directly to have an initial file that can be deleted.
the rm command needs to be changed to rm -f to not fail if the file is nonexistent.

Revision history for this message
Oliver Grawert (ogra) wrote :

hmm, the first sentence above should have been:
"the /etc/X11/Xsession.d/80_ltsp-sound script runs:"

Changed in ltsp:
assignee: nobody → ogra
importance: Undecided → High
status: Unconfirmed → Confirmed
Revision history for this message
Oliver Grawert (ogra) wrote :

ltsp (0.124) edgy; urgency=low
 .
   * add the -f option to the rm command in the 80_ltsp-sound Xsession
     script to avoid crashers on login, closes malone #66808

Changed in ltsp:
status: Confirmed → 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.