eject hotkey fails to eject cd

Bug #569994 reported by pauls on 2010-04-26
66
This bug affects 12 people
Affects Status Importance Assigned to Milestone
GNOME Settings Daemon
Expired
Medium
gvfs (Ubuntu)
Low
Unassigned

Bug Description

Dell E1505 inspiron laptop. Fn-F10 hotkey combo ejects cd/dvd tray on jaunty and earlier versions of gnome, but fails on lucid gnome.

When I hit Fn-F10, the eject on-screen-display icon appears, but the cd does not open. I've checked the tray on another OS and it works with that key combo, so it's not a hardware problem.

The output from xev when I press Fn-F10 is:

MappingNotify event, serial 36, synthetic NO, window 0x0,
    request MappingKeyboard, first_keycode 8, count 248

FocusOut event, serial 36, synthetic NO, window 0x5c00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 36, synthetic NO, window 0x5c00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 36, synthetic NO, window 0x0,
    keys: 4294967213 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
           0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

The fact that the eject on-screen-display icon pops up makes me think this has nothing to do with failure to recognize the key input, and more likely relates to how gnome processes the XF86Eject command.

For example, if I install xdotool and enter 'xdotool key XF86Eject' in a console, I see the same result. The o-s-d icon appears, but the cd/dvd fails to open.

Entering 'eject' in the console results in the cd/dvd opening.

Not sure what else you need, but let me know.

David Tombs (dgtombs) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage. I have classified this bug as a bug in gnome-settings-daemon.

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

affects: ubuntu → gnome-settings-daemon (Ubuntu)
Changed in gnome-settings-daemon (Ubuntu):
importance: Undecided → Low
Jan-Philipp Litza (jplitza) wrote :

Same here on Travelmate 8471 Timeline. Is there anything more I can do to fix this? Also, Brasero failed to eject the CD as well. I suppose that has the same reason...

Jan-Philipp Litza (jplitza) wrote :

A second after I posted that comment, I instinctively pressed my combo again and it worked. No idea why it didn't the first time. Does anyone else observe that behaviour?

cshong (cshong87) wrote :

This bug affect me. I am using Acer Aspire 4745G. If anyone need any information about my computer, please do not hestitate to give comments here.

Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Package: gnome-settings-daemon 2.30.0-0ubuntu6
PackageArchitecture: i386
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

tags: added: apport-collected

apport information

Still not working here. Now that I know it's gnome-settings-daemon, I did aptitude reinstall gnome-settings-daemon and still no success.

I opened the menu > system > preferences > keyboard shortcuts and can see the eject listed under the sound section. I tried disabling and re-enabling it, but stil only get the o-s-d eject icon and no tray opening. I tried adding a new shortcut with the command "eject" and assigned the fn-f10 (xf86eject) to it. The daemon worked and disabled the fn-f10 from the sound : eject section. With this, my tray opens, but the o-s-d icon is missing. So, I reassigned it back to the sound : eject section and now I get the icon but no tray operation.

I killed and restarted gnome-settings-daemon in a terminal. I notice the following relevant lines:

** (gnome-settings-daemon:8026): DEBUG: Starting keyboard manager
[1272886573,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
** Message: NumLock remembering disabled because hostname is set to "localhost"
** (gnome-settings-daemon:8026): DEBUG: Starting a11y_keyboard manager
** (gnome-settings-daemon:8026): DEBUG: Starting media_keys manager
** (gnome-settings-daemon:8026): DEBUG: Not a valid shortcut: ''
** (gnome-settings-daemon:8026): DEBUG: Not a valid shortcut: ''
** (gnome-settings-daemon:8026): DEBUG: Unable to parse: 'XF86AudioStop'

I'm not sure what the Not a valid shortcut:'' is referring to.

Any other ideas?

Attached is the entire terminal log of the daemon in debug mode (gsddebug.txt)

pauls (paulatgm) wrote :

I notice the changelog shows some upstream changes in how the eject action is executed. I suppose this is a regression due to that work.

Specifically, on 30 March 2010, this:
    - Replace "eject" spawn with GIO code (Bastien Nocera) (#580779)

and on 17 Jan 2010, this:
    - Make eject behave better on OpenBSD (Jasper Lievisse Adriaanse)
      (#598573)

Chris Coulson (chrisccoulson) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream. Thanks in advance!

pauls (paulatgm) wrote :

I'll give it a try.

pauls (paulatgm) wrote :
Sebastien Bacher (seb128) wrote :

thank you for sending the bug to GNOME

Changed in gnome-settings-daemon (Ubuntu):
status: New → Triaged
pauls (paulatgm) wrote :

The gnome developer has requested additional information from the affected systems:

 Bastien Nocera52 [gnome-settings-daemon developer] 2010-05-04 17:43:16 UTC

What's the output of "gvfs-mount -li" on those systems?

He is subscribed to this launchpad version, so please post it here.

pauls (paulatgm) wrote :

paul :~$ gvfs-mount -li
Drive(0): 100 GB Hard Disk
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sda'
  themed icons: [drive-harddisk-ata] [drive-harddisk] [drive]
  is_media_removable=0
  has_media=1
  is_media_check_automatic=0
  can_poll_for_media=0
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=unknown
  Volume(0): 45 GB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '9E64580A6457E395'
     unix-device: '/dev/sda2'
    themed icons: [drive-harddisk-ata] [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
  Volume(1): 107 MB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '1cf7a6e6-36a7-49eb-8892-238d9522701a'
     unix-device: '/dev/sda5'
    themed icons: [drive-harddisk-ata] [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
  Volume(2): 25 GB Encrypted
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '374ab152-07dc-4450-bfc4-aa9d173cf681'
     unix-device: '/dev/sda6'
    themed icons: [drive-harddisk-ata] [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
  Volume(3): 30 GB LVM2 Physical Volume
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '96e2838b-c02c-42f6-988b-5d58ce45dc19'
     unix-device: '/dev/mapper/sda8_crypt'
    themed icons: [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
Drive(1): CD/DVD Drive
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sr0'
  themed icons: [drive-optical] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=unknown

Changed in gnome-settings-daemon:
status: Unknown → New
cshong (cshong87) wrote :

Hello! Are you sure this bug related to gnome-settings-daeemon?

I found that this bug also affect Kubuntu 10.04.

affects: gnome-settings-daemon (Ubuntu) → gvfs (Ubuntu)
Matt Deaton (matt-d10online) wrote :

This also effect my Dell 1501 laptop and HP 3323 desktop. Both work fine with command line eject cdrom to open and eject -t cdrom to close.

Lucid 64-bit with Apple Aluminium keyboard.
it's not working for my keyboard, too.
i've tested with gnome-keybinding-properties to make a new combination.
i make a new keybinding for "eject -T" and map it to the eject key of my keyboard.
it works, but notify-osd doesn't show the notification.

ah, perhaps it is good to know that it works in 9.10 before i remove the extra audio-cable for the cd-drive.

manuarmata (manu-armata) wrote :

I have the same issue with my cherry cymotion linux keyboard witch also has an eject shortcut, since i'm using an old apple quicksilver case i need that button to eject my cd. i noticed it works fine when there is a CD in the drive and it doesn' work when the CD drive is empty. so maybe the drive needs to be mounted for the command to take effect. i also noticed a small, fast dissapearing dialog box when ejecting a CD witch says something like "it's safe to unmount this drive now. this wasn't the case in ubuntu 9.10.

David Tombs (dgtombs) wrote :

Hi all. This bug report is already "Triaged", meaning it has enough information already. Please do not provide any more "me too" comments. Thanks!

aprunai (aprunai) wrote :

Though the bug surely has been defined enough, I'd like to add a little piece of info.
System: Ubuntu Lucid (upgraded from Karmic)
Latest upgrades installed as of June 3rd
Keyboard: Apple, Inc. Hub in Pro Keyboard [Mitsumi, A1048]
Behaviour: whenever I press the eject key (which worked flawlessly in Karmic), my Sandisk card reader is ejected instead!!!!!
(I'm not kidding :) )
The 'eject' and 'eject -t' commands work correctly, my Pioneer 109 DVD recorder opens and closes its tray regularly.

Conscious User (conscioususer) wrote :

I have observed the same thing manuarmata did: the hotkey *always* works when a CD is already inserted. Is this true for everyone else here who is experiencing the bug? Sounds relevant.

Same here

On Sun, Jun 6, 2010 at 11:47 PM, Conscious User <email address hidden>wrote:

> I have observed the same thing manuarmata did: the hotkey *always* works
> when a CD is already inserted. Is this true for everyone else here who
> is experiencing the bug? Sounds relevant.
>
> --
> eject hotkey fails to eject cd on gnome lucid
> https://bugs.launchpad.net/bugs/569994
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gnome Settings Daemon: New
> Status in “gvfs” package in Ubuntu: Triaged
>
> Bug description:
> Dell E1505 inspiron laptop. Fn-F10 hotkey combo ejects cd/dvd tray on
> jaunty and earlier versions of gnome, but fails on lucid gnome.
>
> When I hit Fn-F10, the eject on-screen-display icon appears, but the cd
> does not open. I've checked the tray on another OS and it works with that
> key combo, so it's not a hardware problem.
>
> The output from xev when I press Fn-F10 is:
>
> MappingNotify event, serial 36, synthetic NO, window 0x0,
> request MappingKeyboard, first_keycode 8, count 248
>
> FocusOut event, serial 36, synthetic NO, window 0x5c00001,
> mode NotifyGrab, detail NotifyAncestor
>
> FocusIn event, serial 36, synthetic NO, window 0x5c00001,
> mode NotifyUngrab, detail NotifyAncestor
>
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
> keys: 4294967213 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> 0
> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>
> The fact that the eject on-screen-display icon pops up makes me think this
> has nothing to do with failure to recognize the key input, and more likely
> relates to how gnome processes the XF86Eject command.
>
> For example, if I install xdotool and enter 'xdotool key XF86Eject' in a
> console, I see the same result. The o-s-d icon appears, but the cd/dvd
> fails to open.
>
> Entering 'eject' in the console results in the cd/dvd opening.
>
> Not sure what else you need, but let me know.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-settings-daemon/+bug/569994/+subscribe
>

@hirumono: sounds like a different issue. This one says eject does /nothing/ while yours is that it does the /wrong thing/. Please report a new one with "ubuntu-bug gnome-settings-daemon". Thanks!

Marc Jauvin (marc-r4l) wrote :

I have the same broken behavior on my Thinkpad T61 in Lucid (worked on Karmic).

Sebastien Bacher (seb128) wrote :

could you get a gvfs-mount -li log?

Conscious User (conscioususer) wrote :
Conscious User (conscioususer) wrote :
aprunai (aprunai) wrote :

@David Tombs: I'll be happy to file a new bug, but before that I'd like to add the following to make sure this really IS a separate bug (and sorry for not replying before, but I have been away from my computer for a month):

- Sandisk card reader mounted, with memory card in: 'Eject' unmounts the card's volume;
- Sandisk card reader NOT mounted, CD/DVD in drive: 'Eject' correctly unmounts and expels disc (but doesn't close the tray on second press);
- Sandisk card reader NOT mounted, no CD/DVD in drive: 'Eject' does nothing;
-Sandisk card reader mounted, either before or after CD/DVD is inserted: 'Eject' always unmounts the card's volume;
- Sandisk card reader connected WITHOUT a memory card, CD/DVD in drive: 'Eject' correctly unmounts and expels disc (but doesn't close the tray on second press).

Sorry if this is a bit tedious. ;) My observation is that 'Eject' gives unmounting priority to USB volume, then CD/DVD, and if it doesn't find a mounted volume it does nothing (instead of opening the tray). Since pauls (the original reporter of this bug) just reported about not being able to open the CD tray, and manuarmata added that its Eject key works when a disk is inserted into the drive but fails otherwise, I'd like to ask them to try inserting an USB pen drive or hard disk and see what happens when the Eject key is pressed. This way we can determine if we have two bugs or just a single one.

Thanks!

David Tombs (dgtombs) wrote :

Hi hirumono,

Don't worry, your information may be "tedious" but that kind of detail is very helpful in differentiating bugs. :)

I still think you have a different issue: the upstream report shows that affected users' CD drives have an invalid value for the "can_eject" property, so gvfs will never unmount the drive. On the other hand, yours seems to work under certain circumstances. (manuarmata's also might be a different issue.) So, please do open a new report. Thanks for you help!

aprunai (aprunai) wrote :

Sorry for not checking the 'gvfs -li' output before (and for the late answer - I've just come back from an overseas trip). That's strange, because my 'gvfs -li' output shows the invalid value for "can_eject" property too - BTW, the same goes for the Sandisk card reader. So 'can_eject=0' is not apparently preventing gvfs from unmounting any volume:

Drive(1): Unità CD/DVD
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sr0'
  themed icons: [drive-optical] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=unknown

[stripped]

Drive(5): SanDisk SDDR-199
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sdd'
  themed icons: [drive-removable-media-usb] [drive-removable-media] [drive-removable] [drive]
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=0
  can_start=0
  can_stop=1
  start_stop_type=shutdown

aprunai (aprunai) wrote :

Just found out a very interesting bit of info. Look at my 'gfvs-mount -li' output AFTER I inserted a medium in my Pioneer:

Drive(5): Unità CD/DVD
  Type: GProxyDrive (GProxyVolumeMonitorGdu)
  ids:
   unix-device: '/dev/sr0'
  themed icons: [drive-optical] [drive]
  is_media_removable=1
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=1
  can_eject=1
  can_start=0
  can_stop=0
  start_stop_type=unknown
  Volume(0): Ubuntu 8.10 i386
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     unix-device: '/dev/sr0'
     label: 'Ubuntu 8.10 i386'
    themed icons: [media-optical-cd-rom] [media-optical-cd] [media-optical] [media]
    can_mount=1
    can_eject=1
    should_automount=1
    Mount(0): Ubuntu 8.10 i386 -> file:///media/Ubuntu%208.10%20i386
      Type: GProxyMount (GProxyVolumeMonitorGdu)
      default_location=file:///media/Ubuntu%208.10%20i386
      themed icons: [media-optical-cd-rom] [media-optical-cd] [media-optical] [media]
      x_content_types: x-content/win32-software
      can_unmount=1
      can_eject=1
      is_shadowed=0

It's as if gvfs decided that the device could be ejected because it did have a medium in it. :)
The same can be said about the Sandisk card reader: its state switched from 'can_eject=0' to 'can_eject=1' after a medium (8 GB SD card) was inserted. Looks like the 'eject' key is behaving as an 'unmount' key.

David Tombs (dgtombs) wrote :

@hirumono: I think that's expected behavior. Can you eject your card reader without a card in it? :) (Admittedly it would be nice to be able to eject an empty CD tray, but I don't think it's worth considering it a bug that you can't.) So, you have a different issue.

Conscious User (conscioususer) wrote :

@David, up until Karmic I was able to eject an empty CD tray with the hotkey. I don't think they disabled this behavior on Lucid on purpose.

Agreed i should be able to eject the tray to put media in.

On Sun, Aug 15, 2010 at 6:10 PM, Conscious User
<email address hidden> wrote:
> @David, up until Karmic I was able to eject an empty CD tray with the
> hotkey. I don't think they disabled this behavior on Lucid on purpose.
>
> --
> eject hotkey fails to eject cd on gnome lucid
> https://bugs.launchpad.net/bugs/569994
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gnome Settings Daemon: New
> Status in “gvfs” package in Ubuntu: Triaged
>
> Bug description:
> Dell E1505 inspiron laptop.  Fn-F10 hotkey combo ejects cd/dvd tray on jaunty and earlier versions of gnome, but fails on lucid gnome.
>
> When I hit Fn-F10, the eject on-screen-display icon appears, but the cd does not open.  I've checked the tray on another OS and it works with that key combo, so it's not a hardware problem.
>
> The output from xev when I press Fn-F10 is:
>
> MappingNotify event, serial 36, synthetic NO, window 0x0,
>    request MappingKeyboard, first_keycode 8, count 248
>
> FocusOut event, serial 36, synthetic NO, window 0x5c00001,
>    mode NotifyGrab, detail NotifyAncestor
>
> FocusIn event, serial 36, synthetic NO, window 0x5c00001,
>    mode NotifyUngrab, detail NotifyAncestor
>
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
>    keys:  4294967213 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>
> The fact that the eject on-screen-display icon pops up makes me think this has nothing to do with failure to recognize the key input, and more likely relates to how gnome processes the XF86Eject command.
>
> For example, if I install xdotool and enter 'xdotool key XF86Eject' in a console, I see the same result.  The o-s-d icon appears, but the cd/dvd fails to open.
>
> Entering 'eject' in the console results in the cd/dvd opening.
>
> Not sure what else you need, but let me know.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-settings-daemon/+bug/569994/+subscribe
>

Well, this bug regards ejecting the tray with a CD in, so you both are talking about a different issue. Please open a new bug with "ubuntu-bug gvfs". Thanks!

Conscious User (conscioususer) wrote :

@David, the description refers only to the tray. It does not specify that a CD should be in.

In fact, as you can see by the comments above, at least for me, manuarmata and KruyKaze, the hotkey *does work* when a CD is in.

David Tombs (dgtombs) wrote :

@Conscious: Well, the reporter never said anything about it working when there was a CD in the drive, so I just assumed that it never works for him. I might be wrong, though. In the meantime, could you please submit a different report and post the bug # in here? We'll make it a dupe if you're right.

Conscious User (conscioususer) wrote :

Wait, should I file a new one for when the CD is in or out? Because the comments so far were going in the direction of not having a CD. Maybe we should wait for a clarification from pauls.

pauls (paulatgm) wrote :

That's right, it makes no difference whether I have the drive loaded or not. Not that that matters. You want it to open regardless.

+1

On Mon, Aug 16, 2010 at 6:47 PM, pauls <email address hidden> wrote:
> That's right, it makes no difference whether I have the drive loaded or
> not.  Not that that matters.  You want it to open regardless.
>
> --
> eject hotkey fails to eject cd on gnome lucid
> https://bugs.launchpad.net/bugs/569994
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Gnome Settings Daemon: New
> Status in “gvfs” package in Ubuntu: Triaged
>
> Bug description:
> Dell E1505 inspiron laptop.  Fn-F10 hotkey combo ejects cd/dvd tray on jaunty and earlier versions of gnome, but fails on lucid gnome.
>
> When I hit Fn-F10, the eject on-screen-display icon appears, but the cd does not open.  I've checked the tray on another OS and it works with that key combo, so it's not a hardware problem.
>
> The output from xev when I press Fn-F10 is:
>
> MappingNotify event, serial 36, synthetic NO, window 0x0,
>    request MappingKeyboard, first_keycode 8, count 248
>
> FocusOut event, serial 36, synthetic NO, window 0x5c00001,
>    mode NotifyGrab, detail NotifyAncestor
>
> FocusIn event, serial 36, synthetic NO, window 0x5c00001,
>    mode NotifyUngrab, detail NotifyAncestor
>
> KeymapNotify event, serial 36, synthetic NO, window 0x0,
>    keys:  4294967213 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0
>
> The fact that the eject on-screen-display icon pops up makes me think this has nothing to do with failure to recognize the key input, and more likely relates to how gnome processes the XF86Eject command.
>
> For example, if I install xdotool and enter 'xdotool key XF86Eject' in a console, I see the same result.  The o-s-d icon appears, but the cd/dvd fails to open.
>
> Entering 'eject' in the console results in the cd/dvd opening.
>
> Not sure what else you need, but let me know.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/gnome-settings-daemon/+bug/569994/+subscribe
>

It matters from a bug fix point of view: one issue can be fixed without the other. Please report a new bug (using "ubuntu-bug gvfs") with a summary like "eject hotkey should eject an empty tray".

Conscious User (conscioususer) wrote :

Reported as Bug #619019.

Changed in gnome-settings-daemon:
importance: Unknown → Medium
summary: - eject hotkey fails to eject cd on gnome lucid
+ eject hotkey fails to eject cd

with Ubuntu 11.10 fresh install and my Apple Aluminium Keyboard the problem is still there.
notification is shown but nothing happens when pressing the eject key

My system is dell640m with lucid lynx (updated).
I've used the following workaround:
I've associated my eject key with a script that call eject (it works) and show the icon.
This is the script:
#!/bin/sh
notify-send "Icon" "Only" -i notification-device-eject -h string:x-canonical-private-icon-only:
eject

To have notify-send command in lucid you have to install the package libnotify-bin.

Let me know if it works also in 11.10.

Pascal

Changed in gnome-settings-daemon:
status: New → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.