Just to clarify after such a lengthy discussion:
> The problem still exists on my T40.
The problem means: No notification when changing the volume or
muting/unmuting using hardware keys. But the volume changes like
expected.
This has worked in Ubuntu Intrepid at least.
--
No notification when
I have Kubuntu Lucid with all updates. The problem still exists on my
T40.
The status of this bug is fix-released in the kernel. So either the
kernel fix does not work or there is another Kubuntu-specific component
involved, which is not yet listed under affected compontents.
--
No notification
Hi Felicia!
In response to your questions in https://bugs.launchpad.net/584052 :
I have really no clue whether your problem here is a duplicate of any of
the existing reports or something different.
I would recommend to update udisks before any further investigations. If you
don't want to wait
> You can do "sudo killall udisks-daemon"
> and log out, and check if the next login then behaves like the initial
> one.
Yes, your assumption is correct. At the next login nautilus runs the the
mount command, which takes 18 minutes to complete.
> Likewise, it's interesting to check whether a mer
> After logging out and in again it works correctly:
1.) function automount_all_volumes is called (of course) but it doesn't
call g_volume_mount for the fd
2.) function volume_added_callback is called for the floppy and it calls
nautilus_file_operations_mount_volume
But no mount process is start
>> 1. nautilus tries to mount floppy drives at startup.
>
>It doesn't,
Yes it does. The be exact it does it in the first session after booting.
If you log out and in again, nautilus is being restarted but it doesn't
try to mount the floppy anymore. (as already mentioned in
https://bugs.launchpad.n
To summarize:
I believe we have 2 problems now:
1. nautilus tries to mount floppy drives at startup. Maybe it has always
done this, but I think in year 2010 it could also be removed. I guess
many of the floppy controllers existing today don't have a floppy drive
attached. At least not in laptops.
>> But what does the detects change mean? It has no way to detect whether
>> it has media or not???
>
>Right, that's why the value is 0.
Yes, now I remember that's the way floppy drives work. Once a program
wants to read, the drive just tries to access the floppy, whether one is
inserted or not. Y
My "udisk --dump" reports
device-file: /dev/fd0
has media: 1
detects change:0
The "has media" is obviously incorrect, because I don't even have a fd drive.
But what does the detects change mean? It has no way to detect whether
it has media
eev2 wrote:
> I don't have nautilus, just libnautilus-extension1 but I'm also
affected by this.
interesting. So either not all duplicates of this bug are the same issue
or there are different ways to get the same problem.
eev2, could you please run the command "pstree -p -l" during the mount com
Hmm, this bug is assigned to gvfs. I must admit that I understand gvfs
less then well. But according to my analysis
https://bugs.launchpad.net/bugs/586873 gvfs was not involved in this
issue.
nautilus just calls /bin/mount (see
http://launchpadlibrarian.net/49269052/pstree2.txt ) with a single
par
Response to some people are wondering how this can be possible, if
there is no floppy drive in the machine. Obviously the presence of the
floppy controller is enough. There is no recognition whether a drive is
connected to the controller. (Or maybe that recognition is broken, but I
don't believe t
Correction: Starting a new GNOME session will not trigger the problem.
It happens only once until the machine is rebooted.
Further info:
The mount program running is really /bin/mount, checked from
/proc/nnn/maps (So source package would be util-linux)
The command line is
mount /media/floppy0
Or should mount actually fail more quickly?
Hmm, which mount program is running actually? Now it has just finished
(about 30 minutes) after boot, need to restart my session to find out.
--
GNOME tries to mount non-existing floppy in Lucid
https://bugs.launchpad.net/bugs/586873
You received this
Here is how I decided to blame nautilus:
$ sudo lsof /dev/fd0
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
mount 1472 root3u BLK2,0 0t0 2108 /dev/fd0
pstree output is attached. It shows that nautilus has started mount
(1472).
** Attachment added: "pstree output"
h
apport has not added the syslog, so I do it manually.
These are the error messages:
May 28 18:47:36 geuder-t40-u kernel: [ 1177.350646] end_request: I/O error, dev
fd0, sector 0
May 28 18:47:36 geuder-t40-u kernel: [ 1177.350661] Buffer I/O error on device
fd0, logical block 0
** Attachment ad
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49268305/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/49268306/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/49268307/ProcStatus.txt
** Attachm
Public bug reported:
Binary package hint: nautilus
Each time when starting a GNOME session, the system tries to mount
/dev/fd0. This machine has no floppy disk drive (but obviously an FD
controller)
Symptoms:
- "disk light" is permanently on for at least 20 minutes
- mount process is hanging th
The question is of course whether the bug is in gdmgreeter code proper
or in some library it uses.
If anybody has some hints how to debug this? (maybe something easier
than building gdmgreeter myself with debug indo and single-stepping
through it)
--
gdmgreeter exits if remote Xserver supports
Alternative work-around: Disable RandR altogether on your remote Xserver
supporting only v1.1. gdmgreeter works fine now.
--
gdmgreeter exits if remote Xserver supports only RandR v1.1
https://bugs.launchpad.net/bugs/296127
You received this bug notification because you are a member of Ubuntu
Des
** Description changed:
Binary package hint: gnome-control-center
1) $ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
2) $ apt-cache policy gnome-control-center
gnome-control-center:
Installed: 1:2.24.0.1-0ubuntu7.1
Candidate: 1:2.24.0.1-0ubuntu7.1
Vers
** Description changed:
Binary package hint: gnome-control-center
1) $ lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
2) $ apt-cache policy gnome-control-center
gnome-control-center:
Installed: 1:2.24.0.1-0ubuntu7.1
Candidate: 1:2.24.0.1-0ubuntu7.1
Vers
Public bug reported:
Binary package hint: gnome-control-center
1) $ lsb_release -rd
Description:Ubuntu 8.10
Release:8.10
2) $ apt-cache policy gnome-control-center
gnome-control-center:
Installed: 1:2.24.0.1-0ubuntu7.1
Candidate: 1:2.24.0.1-0ubuntu7.1
Version table:
*** 1:2.2
** Summary changed:
- gdmgreeter exits on RandR v1.1
+ gdmgreeter exits if Xserver supports only RandR v1.1
** Description changed:
Binary package hint: gdm
1) $ lsb_release -rd
Description: Ubuntu 8.04.1
Release: 8.04
2) $ apt-cache policy gdm
gdm:
Installed: 2.20.7-
Public bug reported:
Binary package hint: gdm
1) $ lsb_release -rd
Description:Ubuntu 8.04.1
Release:8.04
2) $ apt-cache policy gdm
gdm:
Installed: 2.20.7-0ubuntu1.1
Candidate: 2.20.7-0ubuntu1.1
Version table:
*** 2.20.7-0ubuntu1.1 0
500 http://fi.archive.ubuntu.com ha
25 matches
Mail list logo
