Sebastien Bacher [2010-06-01 19:49 -]:
** Attachment added: strace log until getting the udisks log
http://launchpadlibrarian.net/49517978/debug
Ah, this indeed shows some open('/dev/fd0') in the main udisks process
(pid 4632), which cause some 2-second hang.
To confirm that it's really
strace log while it's hanging
[pid 4467] 21:38:59.773938 read(11, 1\n, 4096) = 2
[pid 4467] 21:38:59.773997 read(11, , 4094) = 0
[pid 4467] 21:38:59.774032 close(11) = 0
[pid 4467] 21:38:59.774064 open(/dev/fd0, O_RDONLY|O_LARGEFILE unfinished
...
[pid 4468] 21:39:01.594819 ... poll
** Attachment added: strace log until getting the udisks log
http://launchpadlibrarian.net/49517969/debug
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
** Attachment added: strace log until getting the udisks log
http://launchpadlibrarian.net/49517978/debug
** Attachment removed: strace log until getting the udisks log
http://launchpadlibrarian.net/49517969/debug
--
Attempts to mount floppy despite no media present - disable automount
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
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
Uwe Geuder [2010-05-31 12:33 -]:
After logging out and in again it works correctly:
There's a high chance that the difference is that on first login
nautilus/gvfs trigger udisks-daemon to start up, while it's already
running on the second login. You can do sudo killall udisks-daemon
and log
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 mere
stacktrace while nautilus is hanging after stopping the udisks-daemon
#0 0x0012d422 in __kernel_vsyscall ()
#1 0x00d8fb4b in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0x00f6c13b in _dbus_poll (fds=0xbfffeab4, n_fds=1,
timeout_milliseconds=25000) at dbus-sysdeps-unix.c:1970
#3
seems the session is starting but gvfs clients hang this way
those warnings are displayed while running udisks --dump after stopping
the udisks-daemon end_request: I/O error, dev fd0, sector 0
--
Attempts to mount floppy despite no media present - disable automount
11562 ?D 0:00 /usr/lib/udisks/udisks-daemon
11563 ?S 0:00 \_ udisks-daemon: polling /dev/sr0
while it's hanging
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because
Hey Seb,
Sebastien Bacher [2010-05-31 20:59 -]:
11562 ?D 0:00 /usr/lib/udisks/udisks-daemon
I suspect that this is the root of the problem. Can you please start
udisks-daemon under strace -vvftts1024 and then do udisks --dump? The
timestamps should then tell us what took it so
Uwe Geuder [2010-05-30 3:40 -]:
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.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received
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. You
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
Uwe Geuder [2010-05-30 23:43 -]:
1. nautilus tries to mount floppy drives at startup.
It doesn't, gvfs says (I believe) should_automount=0. The problem
seems to be that some lower-level process such as udisks probes the
floppy on startup, which makes gvfs/nautilus hang in a sync d-bus
call.
Sebastien Bacher, a colleague of mine, now has access to affected
hardware, so setting to triaged.
** Changed in: gvfs (Ubuntu)
Status: Incomplete = Triaged
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this
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 or
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
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
I don't have nautilus, just libnautilus-extension1 but I'm also affected
by this.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
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
I looks like that mount doesn't hung for me because it didn't appear when I ran
the pstree command right after log-in. I made a bootchart and mount runs in an
instant. I do observe though those long idle times at login.
Sorry for the confusion.
--
Attempts to mount floppy despite no media
I tried the suggestion in comment #74, to disable the floppy in bios -
rebooted, plugged in my flash drive and...nothing :(
But, I no longer see the floppy drive icon. So, that's an improvement AND I
shaved several seconds on my boot time too!
For the record, I do not have a floppy drive, never
If you do not have a BIOS option for this, you can try this:
echo blacklist floppy | sudo tee /etc/modprobe.d/blacklist-floppy.conf
sudo update-initramfs -u
does that help after a reboot?
It'd still help if someone who is affected could provide me access to
the box, via ssh or empathy
Is the blacklist module thing applicable only if you have floppy module
loaded (e.g. check via lsmod |grep floopy)?
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of
mehturt [2010-05-27 9:34 -]:
Is the blacklist module thing applicable only if you have floppy module
loaded (e.g. check via lsmod |grep floopy)?
Yes.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug
It works for me, thank you Martin.
On Thu, May 27, 2010 at 5:25 AM, Martin Pitt martin.p...@ubuntu.com
wrote:
If you do not have a BIOS option for this, you can try this:
echo blacklist floppy | sudo tee /etc/modprobe.d/blacklist-floppy.conf
sudo update-initramfs -u
does that help after
Martin, I would gladly help giving you access to my computer. I already
added you to my gmail contacts in pidgin, just tell me what to do when
we both are online.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug
I had the same problem on Compaq Evo Laptop (has no floppy and no option
to disable)
I've got it working now so if you have the floppy issue do the following:
- comment out (put # in front) the floppy line in /etc/fstab
- blacklist the floppy module add a line to /etc/modprobe.d/blacklist.conf:
Hi I have this problem too, but I don' t understand how to do all these
procedures...
can you explain me step by step, thanks.[?][?]
On Wed, May 26, 2010 at 2:47 AM, pallgone pallg...@gmail.com wrote:
I had the same problem on Compaq Evo Laptop (has no floppy and no option
to disable)
I've
nautilus or gvfs hanging should not block the session, could it be that
dbus is blocking?
** Also affects: gvfs (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: gvfs (Ubuntu Lucid)
Importance: Undecided = Medium
** Changed in: gvfs (Ubuntu Lucid)
Status: New =
Sebastien Bacher wrote:
nautilus or gvfs hanging should not block the session, could it be that dbus
is blocking?
Does this answer your question?
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/539515/comments/56
--
Attempts to mount floppy despite no media present - disable automount
What about if I don't have the option in the BIOS to disable the floppy?
How can this damn problem be solved???
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
How to remove that line? where?
2010/5/20 Herrero Grégory gregory.herr...@gmail.com
I had this problem too on my Lucid 10. and I confirm that you just need
to disable floppy in Bios and remove the line with /dev/fd0 in
/etc/fstab even if you have no floppy drive.
--
Attempts to mount
I also have this problem. As far as I can tell, I have disabled a non
existant floppy disk drive, I have unchecked everything in the start up
applications, after I login, it takes 13 seconds to display the desktop.
When will this bug be fixed?
Even the Mrs said, Why is the computer so slow, what
I had this problem too on my Lucid 10. and I confirm that you just need
to disable floppy in Bios and remove the line with /dev/fd0 in
/etc/fstab even if you have no floppy drive.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You
I am affected too by this bug and disabling the floppy in the bios
worked too..
But i don't agree with the medium importance assigned to this bug, it
definitely reduces the whole system performance, in particular every
time nautilus is accessed. It's not a very good visit card for users who
are
My notebook does not have a floppy drive, and the BIOS does not have an option
to disable it, and I am affected by this bug too (or at least my desktop takes
an eternity to load up). I didn't had problems before 10.04.
This is reaaly annoing. It takes 2 minutes to open Gnome.
--
I have Dell XPS M1530. I do have this problem, I do not have a floppy
and there's no floppy in BIOS.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop
I'm also bugged by this bug :-)
Disabling Floppy from within the BIOS makes the Desktop load much faster.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop
+1 this problem, workaround by disabling floppy drive in BIOS.
http://ubuntuforums.org/showthread.php?t=1468152
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Marcosroriz,
Can you please check in your bios and see if there is any mention of a floppy
drive. If you can disable the floppy controller, please do so and see if it
fixes the bug for you.
My issue is that I am one of the few people who may actually use a floppy. Most
of the time the drive
slayer [2010-04-30 11:54 -]:
But what if someone (still) uses floppies?
Then there shouldn't be problems. The long hang is due to the kernel
trying to speak to a nonexisting floppy (and not ever getting any
answer)
--
Attempts to mount floppy despite no media present - disable automount
Confirmed.
I installed Lucid RC1, and have updated my way to the final release
since then. Last update today. After installation I got an floppy icon,
but I have no floppy drive. I commented the floppy line in fstab and the
floppy icon disappeared. But also the icon for my ntfs partition (not
I'm witht his bug too.
And I don't have floppy or other device connected
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ditto for me on my machine, which does not have a floppy drive. I had
the 'unrecoverable error' during initial installation and the hang-up
from the login screen to when the GNOME panels loaded. Ubuntu
automatically inserted an entry in /etc/fstab for my floppy:
#/dev/fd0 /media/floppy0
I have this bug on a Sony laptop with a removable floppy drive that may
be used occasionally. I see repeated attempts in the logs to mount a
floppy when the drive is not attached. This also prevents USB drives
from auto-mounting and makes playing DVD movies impossible.
I didn't have the issue in
On Sat, May 1, 2010 at 1:50 PM, Bartek Bialasek da...@poczta.fm wrote:
Computer: Thinkpad T41 (old but favourite;)
I have this problem in the final release of Ubuntu 10.04.
I've removed fd0 from /etc/fstab and disabled in BIOS floppy drive.
And it works;) ubuntu is faster than ever, in the
Computer: Thinkpad T41 (old but favourite;)
I have this problem in the final release of Ubuntu 10.04.
I've removed fd0 from /etc/fstab and disabled in BIOS floppy drive.
And it works;) ubuntu is faster than ever, in the Computer Nautilus
places there is no longer floppy drive.
And what is most
I'm affected too, the workaround of disabling the flobby in the bios
works. But what if someone (still) uses floppies? A fix should be nice
:)
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification
Same issue on archlinux with udisks 1.0.1.
http://bbs.archlinux.org/viewtopic.php?pid=749653
Description and log files are in posts 1 and 3, solution (disabling
floppy in bios) in post 16.
Summary:
After every restart of dbus, 'udisks --dump' (and all GTK file dialogs) takes
~30 seconds.
I disabled the floppy from BIOS but desktop session startup is still
very long.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
It tooks more than 40 seconds in my system from gdm password entry to
full gnome-session
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Confirm this on my side too. I have the floppy ('cause I need it).
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
Did an fresh install from daily build (earlier upgraded from karmic),
now the delay after gdm is gone..
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop
Oh, another question: Can you please check if you have a line with
/dev/fd0 in /etc/fstab? Does commenting it out (put a # in front of
the line) help?
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug
Hm, reading the gvfs code it should already not mark floppies for auto-
mount. But let's check the gvfs-mount output once it arrives.
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are
gvfs-mount -li attached
no fd0/floppy references in fstab
** Attachment added: gvfs.txt
http://launchpadlibrarian.net/44242112/gvfs.txt
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because
I had the same problem with a long delay on my session start.
I then deactivated the floppy in my BIOS and this problem went away.
I now have the new problem that nautilus shows me a nonexistant floppy drive.
When I am at home again, i will check if there is an entry in my fstab,
--
Attempts to
Thanks SevenMachines; this confirms that floppies are indeed not
automounted. So it's probably some probing going on (which is async in
udev/udisks, so it shouldn't block nautilus). At this point I'm afraid I
need access to an affected machine.
--
Attempts to mount floppy despite no media
@ Martin Pitt remote desktop?
--
Attempts to mount floppy despite no media present - disable automount
https://bugs.launchpad.net/bugs/539515
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
desktop-bugs mailing list
linusr [2010-04-15 21:29 -]:
@ Martin Pitt remote desktop?
While this is pretty clumsy over long distances due to the high
latency, it would certainly be enough for me to set up an ssh
tunnel/connection so that I can ssh in afterwards.
I'm pi...@jabber.org, BTW.
--
Martin Pitt
63 matches
Mail list logo
