Public bug reported:
I noticed this after installing Lightscribe on Ubuntu 11.10.
Synaptic displays The list of installed files is only available for installed
packages instead of the file list.
The package is indeed installed and I have used it.
To reproduce do the following:
cd /tmp
wget
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904853
Title:
Does not display the file list for packages installed with --force-
acrchitecture
To manage notifications about this bug go to:
I have a canoscan LIDE 30 with the same problem. I connect it into a
USB 3.0 port no go in a USB 2.0 port on the same machine it works. I
can give you all the pertinent information if you need. This is also a
problem in Oneiric with the default kernel.
** Changed in: linux (Ubuntu)
Its back...
Setting up tzdata (2008a-0ubuntu0.7.10) ...
dpkg: error processing tzdata (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
tzdata
E: Sub-process /usr/bin/dpkg returned an error code (1)
Is there a quick work
I didn't figure out exactly what was causing it but its definitely
because some one is using dash to do something dash doesn't do. I
changed the interpreter from /bin/sh a link to dash to /bin/bash and now
the world is happy again.
So I answer my own question here the quick fix:
Edit the first
Chris: The message Cannot eject volume. is a separate issue and will
not effect usage in any way. I take it you are using Nautilus to
eject the volume. Nautilus eject does other things besides running
umount on the device. Nautilus is using gvm and hence hal for various
reasons. The problem
Júlio: Thats true you may not want your mom to do that. In that case
the simple way is since you have sudo just make a fstab entry for the
drive using uuid and do not put in the user, users or group options.
Then you can mount it using sudo and it can not be mounted by a standard
user. The
It may also be noted that the options I gave above are only for
preventing getting root access. If you want to protect data that diff.
It also may not be desirable to let users mount the drive.
Anyway enough said. You can go around in circles about this stuff.
--
mounting via UUID behaves
