After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348533 - Mounted devices pluged when Commander is running are not noticed.
Mounted devices pluged when Commander is running are not noticed.
Status: RESOLVED OBSOLETE
Product: gnome-commander
Classification: Other
Component: application
1.2.x
Other All
: Normal minor
: 2.0
Assigned To: GNOME Commander maintainer(s)
GNOME Commander maintainer(s)
: 757741 (view as bug list)
Depends on: 589069
Blocks:
 
 
Reported: 2006-07-24 15:06 UTC by Tomáš Hnyk
Modified: 2018-08-03 17:50 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tomáš Hnyk 2006-07-24 15:06:34 UTC 
Please describe the problem:
When I insert a CD or I plug in an external USB harddrive, Gnome Commander does not notice it and those devices do not appear up on the panel. When I restart Gnome Commander they, however, are noticed.

Steps to reproduce:
Insert a CD or a USB stick and see what happens.

Actual results:
Well, nothing.

Expected results:
Mounted devices to appear on the panel.

Does this happen every time?
Yes

Other information:
Comment 1 Tomáš Hnyk 2006-11-05 17:53:41 UTC 
I observed it a little further (usin version 1.2.1) and actually sometimes it works. When a device (external mass storage usb harddrive) is pluggen, indeed, nothing happens. However, when I use disk mounter (GNOME panel applet) to eject a and mount the device, it apperas. However, there are to partitions on the device, and only one is displayed, after the second is mounted, nothing happens.¨

With CDROM, it never works (obviously, it is impossible to mount CDROM via disk mounter).

When restarted, it reads all the external devices - boht partitions and cdrom correctly.
Comment 2 Bill Wood 2015-10-01 15:06:48 UTC 
Despite this being opened for a long time, the problem is STILL present in gnome-commander v1.4.3.  In addition, I tried the latest Ubuntu 15.10 beta 2, which uses Gnome-commander v1.4.7, and the problem is STILL present!  When is someone actually going to work on this and fix it?
Comment 3 Uwe Scholz 2015-10-02 15:08:44 UTC 
As you can see, this bug is blocked by bug #589069. I can not tell when both bugs will be fixed, but as gcmd is an open source project, any help would be very appreciated.
Comment 4 Uwe Scholz 2015-11-07 17:04:00 UTC 
*** Bug 757741 has been marked as a duplicate of this bug. ***
Comment 5 Uwe Scholz 2016-05-24 09:51:50 UTC 
*** Bug 766831 has been marked as a duplicate of this bug. ***
Comment 6 GNOME Infrastructure Team 2018-08-03 17:50:22 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-commander/issues/3.