[Desktop-packages] [Bug 1730612] Re: Enable Remote desktop feature during build
Pipewire is packaged now, can we get it enabled? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730612] Re: Enable Remote desktop feature during build
With that being true, we just need mutter built with the correct flag Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730612] Re: Enable Remote desktop feature during build
Link in comment #3 also shows an upstream pipewire master https://launchpad.net/~jan-koester/+archive/ubuntu/pipewiremaster Maybe we could get that linked as the upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"
Came here to say that either there is another bug than the "MetaSyncRing" bug or that is not a clear indicator of this bug. Like others I had upgraded a couple of days ago and had horrible stutter in vte based terminals, other apps were fine. Wayland resolved the issue, but there are huge problems with Wayland in other ways so back to x11 I had to go. Installed the ppa from Daniel (vanvugt) with the versions of mutter there and all problems have ceased. But to re-itterate, I never had MetaSyncRing issues in any logs. Just wanted to say thanks though, a very speedy fix from Daniel on something which was impacting daily usability. Top work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: In Progress Status in mutter source package in Mantic: In Progress Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] Input or the entire screen may freeze at times on systems using the Nvidia Xorg driver with GNOME. [ Test Plan ] 0. Set up a desktop with Nvidia driver 545 or 550. 1. Log into Ubuntu, ensuring it's a Xorg session. 2. Open a Terminal, resize it vigorously, and type several lines of text. 3. Run: journalctl -b0 | grep MetaSyncRing 4. Verify the above command does NOT show "MetaSyncRing" messages such as: Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Sync object is not ready -- were events handled properly? Window manager warning: MetaSyncRing: Too many reboots -- disabling [ Where problems could occur ] Anywhere in Nvidia (proprietary driver) Xorg sessions since the code being modified is only used with that driver. [ Original Description ] There is a noticeable delay in input while using the native terminal. I belive it was caused by a recent software update, as this issue is relatively new. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 30 19:57:13 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-30 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
Same issue, GJS already installed. 22.04 LTS X11 Nvidia 515 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
I am finding that display does turn off (following the fade to black) but within 20 to 30s the monitors turn back on and either remain on fully or just blank after a period of time but still powered. Not convinced this is gnome-settings related and maybe this bug is in the wrong place? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971434] Re: Display powersave only blanks, but does not turn off
More appropriate project ** Package changed: gnome-settings-daemon (Ubuntu) => gnome-screensaver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in GNOME Screensaver: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1971434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726116] Re: Thunderbird "unread email" counter doesn't always update when unread emails are opened
Still happening Thunderbird 60.7.0(64-bit) Ubuntu-GNOME 18.04.2 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1726116 Title: Thunderbird "unread email" counter doesn't always update when unread emails are opened Status in thunderbird package in Ubuntu: Confirmed Bug description: BEHAVIOR With Thunderbird in the Ubuntu Dock favorites, a counter will appear in the top-right showing the number of (I believe) a combination of unread emails and/or new email notifications. After opening some of those emails, the counter in the top-right doesn't always change. It looks like any unread emails that were present upon opening Thunderbird don't alter the counter when they're opened, but new emails received after Thunderbird is opened will alter the counter number when opened. EXPECTED BEHAVIOR For the counter number to be affected when emails are opened, regardless whether they were received after Thunderbird opened or not. (Could just be my ignorance as to whether the counter is alerting me of new email notifications or total unread emails.) BUG DISCOVERED USING Ubuntu 17.10 Thunderbird 52.4.0 GNOME 3.26.1 Nvidia 384.90 proprietary driver X.org 1.19.5 Linux kernel 4.13.0-16-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1726116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085320] Re: White borders around *.desktop files on the desktop
I have this bug and am running the version 1:3.6.3-0ubuntu5~ubuntu12.10.1 is this a regression or because I am using the gnome3-ppa and the patch hasn't gone upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1085320 Title: White borders around *.desktop files on the desktop Status in Nautilus: Fix Released Status in “nautilus” package in Ubuntu: Fix Released Bug description: Ubuntu 13.04, Nautilus 1:3.6.3-0ubuntu2 Desktop launcher files are drawn on the desktop with a heavy white border and very thin border in Home Folder. This only happens with *.desktop files. Links, folders, and files display normally. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1085320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1135402] Re: gsettings requires 'kick' to update
Anybody able to reproduce or is it just me? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1135402 Title: gsettings requires 'kick' to update Status in “glib2.0” package in Ubuntu: New Bug description: issuing the commands gsettings set org.gnome.desktop.background picture-uri 'file://fileuri.jpg' gsettings set org.gnome.desktop.background picture-options 'zoom' as an example, under 12.04, changed the backround picture instantly. now in 12.10, the picture remains until you open the appearence settings app, then the changes are suddenly displayed. this could be an intended modification, but it certainly is a bug and not a feature for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1135402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I switched to xim and rebooted. Media keys, brightness keys and one custom shortcut worked. Others did not. A reboot later and back to nothing working. What is the handler for keyboard shortcuts? where does ubuntu store the shortcuts? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I can confirm this bug. Didn't notice at first as my custom shortcuts were for things like screen brightness. Went to add a new one today and nothing, not even the workarounds mentioned work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
This is deffo an ubuntu issue. Logging into a gnome session, all my media keys and shortcuts work, log back into ubuntu, none of them work. This must be fairly new as I was using media keys a few days ago. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
For 14.04 i get standard keybindings back, but custom ones fail to work. E.g. i can remap screenshot keys, but custom ones for brightness fail. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
Still no joy with ccsm, although I may have identified more of the issue. If I setup a commandline and try to invoke with some of the more "special' keys, e.g. "Brightness Up" that I have on my daskeyboard, it "grabs" the key combination as "XF86Launch6", or "XF86Launch5" for brightness down, or "XF86Eject", for eject (as I have no optical media drive I reassign this for other things) If I pick a standard key like "F12", the command line executes. I'm not knowledgeable enough about the input system to know what the differences are between a "standard" key and an "emulated XF86" one and the ways they are interpreted by the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I have just returned to ccsm to edit the keybindings and try to diagnose this futher. All the commandlines are empty, and the keybindings tab has blank buttons for any commands I had previously enabled. Where does ccsm read this from as this may be one of the causes of this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1333073] Re: PPA Fatal error when opening…loading libexpwraplo.so failed
Workaround in #9 doesn't work for me - cannot open LibreOffice -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1333073 Title: PPA Fatal error when opening…loading libexpwraplo.so failed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: When I install the libreoffice package (1:4.3.0~rc1-0ubuntu1~trusty0) on Ubuntu 14.04 from ppa:libreoffice/libreoffice-prereleases, both 32-bit and 64-bit, the splash screen appears, soon followed by a Fatal Error dialog: The application cannot be started. service not supplied: loading component library failed I have not tested if any upstream packaging produces the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1333073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1021581] Re: When printing large PDF documents evince sends incomplete output
I encountered this error with single page (a3 size) very large documents. They wouldn't print, spent 2 hours debugging CUPS, only to then try ocular, which printed fine first time. Then I noticed the document sizes being sent to CUPS were vastly (magnitude of 10 times) smaller than the document to be printed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1021581 Title: When printing large PDF documents evince sends incomplete output Status in Evince document viewer: New Status in “evince” package in Ubuntu: Confirmed Bug description: When trying to print a PDF document containing many pages (e.g. 15) printing is impossible using either Adobe Reader or Evince. When trying to print the whole document with Evince, the printer only feeds a single paper but doesn't print anything onto it. When trying to print the whole document with AR, the printer symbol appears for a second and then disappears. Printing queue shows no jobs. Printing only one page from the same document works! Not sure if I chose the right package to report this bug. My printer is Brother DCP-395CN. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups-filters 1.0.18-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19 Uname: Linux 3.2.0-26-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Fri Jul 6 06:40:59 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lpstat: device for DCP-7010: usb://Brother/DCP-7010?serial=000L7J203843 device for DCP395CN: socket://speedport.ip:9100 device for Stylus-D68: usb://EPSON/Stylus%20D68?serial=ABC010511292005000 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 003: ID 064e:c21c Suyin Corp. MachineType: Acer Aspire 5750G Papersize: a4 PpdFiles: Stylus-D68: Epson Stylus D68 - CUPS+Gutenprint v5.2.8-pre1 DCP-7010: Brother DCP-7010 Foomatic/hl1250 (recommended) DCP395CN: Brother DCP-395CN CUPS ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic-pae root=UUID=57c016a5-8773-4a08-9276-48aa6e1bdf73 ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE50_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire5750G:pvrV1.11:rvnAcer:rnJE50_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire 5750G dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1021581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I agree, I had got Audio keys working again by luck, and decided to try custom shortcuts for something else again via the control panel. Now lost all shortcuts again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/libxfce4ui/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
As an update, I found this post :- http://ubuntuforums.org/showthread.php?t=2217890 and bug report https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1302885 Stating " The problem is that an incorrect string is set in dconf key: (Example) Original (working) value: ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up 'XF86AudioRaiseVolume' After running "unity-control-center keyboard", and setting the shortcut for volume-up key: ~$ gsettings get org.gnome.settings-daemon.plugins.media-keys volume-up 'AudioRaiseVolume' When I checked with dconf, my media keys were indeed screwed up as in this post. I added the XF86 prefix and they now work. However, this is only one small part of the bug. (in fact a different bug) If I try to capture keyboard events with xev, I am not getting any keypresses for keys I have assigned in the control centre gui. For example, Brightness Up and Down keys - instead of triggering "keypress" and "keyrelease" events, instead trigger "Mapping notify", "focusout", "focusout", "focusin" and "keymapnotify" events. I have also found that I can get the unresponsive keys to trigger the correct events in xev by pressing them with another key, e.g. press eject and F12, and I will get keypress events for both (and the shortcut assigned to a key sometimes will execute too) In desperation I have even installed xbindkeys and configured it, but it seems to be too far up the keyboard handling chain to receive the keys before something else has stolen them and done nothing with them. ** Also affects: gnome-control-center Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I have had a bit of success. Everything is working again. I did 3 things: 1. Removed all custom keybindings in dconf editor 2. Installed and the uninstalled xbindkeys 3. Made the system create an .Xmodmap in my user directory Now all shortcuts are working, including a terminal script being run from my eject key. Can't say for certain what fixed the issue, but for now working (and i'll be avoiding the gnome control centre for adjusting shortcuts until that is patched) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
I ran xmodmap -pke > ~/. Xmodmap In a terminal. My keys are still working after several reboots. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
No space before Xmodmap xmodmap -pke > ~/. Xmodmap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “libxkbcommon” package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1241752] Re: Crash when opening image files larger than 5M (>5M)
There is no kernel.shmmax line in my /etc/sysctl.conf file, is it safe to add one? under 14.10 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1241752 Title: Crash when opening image files larger than 5M (>5M) Status in “cairo” package in Ubuntu: Confirmed Bug description: This is similar to the bug reported here: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=710701 However, the crash that is now getting generated is from an entirely different call and file. Specifically, the error is: eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. Aborted (core dumped) In the message above, I was using eog, but this affects other apps, like gThumb as well. In terms of the environment, I'm using Ubuntu 13.10 on an 64-bit machine, and am using libcairo2-1.12.16. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libcairo2 1.12.16-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 18 11:08:27 2013 InstallationDate: Installed on 2013-04-25 (176 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cairo UpgradeStatus: Upgraded to saucy on 2013-10-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1241752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
Upgraded to 14.10 and lost all but volume keys again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in gnome-control-center package in Ubuntu: Confirmed Status in libxkbcommon package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224732] Re: Custom keyboard shortcuts don't work
Ran through my actions in post #52 and now have all shortcuts working again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1224732 Title: Custom keyboard shortcuts don't work Status in GNOME Control Center: New Status in libxfce4ui: New Status in gnome-control-center package in Ubuntu: Confirmed Status in libxkbcommon package in Ubuntu: Confirmed Bug description: Just noticed that adding custom keyboard shortcuts does not have any effect. If, for example, I add a custom keyboard shortcut for Evince and set it to Ctrl+Alt+E, pressing this key combination won't launch Evince. * What happens * When I add a custom keyboard shortcut (and bind it to some key combination), the shortcut does not run the associated command. * What I expect * After adding the custom shortcut, I expect that the shortcut launches the associated command. Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 gnome-control-center: Installed: 1:3.6.3-0ubuntu36 Candidate: 1:3.6.3-0ubuntu36 Version table: *** 1:3.6.3-0ubuntu36 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu36 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic i686 ApportVersion: 2.12.1-0ubuntu4 Architecture: i386 Date: Thu Sep 12 19:21:56 2013 InstallationDate: Installed on 2013-08-31 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130830) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20130903-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3daily13.06.14.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1224732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1135402] Re: gsettings requires 'kick' to update
This problem has re-occurred in 14.10. This time I am able to change settings via gsettings or dconf, only for them to be ignored. In the screenshot here http://imgur.com/7Tkwv0N I have just set the parameters by dconf in the cli, opened dconf gui editor and the settings displayed are different. I then read the parameters with the dconf cli, and they were correct. The same happens if I use gsettings on the cli. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1135402 Title: gsettings requires 'kick' to update Status in glib2.0 package in Ubuntu: New Bug description: issuing the commands gsettings set org.gnome.desktop.background picture-uri 'file://fileuri.jpg' gsettings set org.gnome.desktop.background picture-options 'zoom' as an example, under 12.04, changed the backround picture instantly. now in 12.10, the picture remains until you open the appearence settings app, then the changes are suddenly displayed. this could be an intended modification, but it certainly is a bug and not a feature for this use case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1135402/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314780] Re: Full screen between xorg and VMWare-Workstation
Still a bug on 15.04 vmware workstation 11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314780 Title: Full screen between xorg and VMWare-Workstation Status in xorg package in Ubuntu: Confirmed Bug description: This is a minor bug that seems to be a conflict between xorg and VMWare Workstation 9 in Ubuntu 14.04. It seems most noticeable and prevalent with dual monitors. This issue was not present in 12.04. The taskbar at the top of the screen that is always present seems to give issues with full screen VMWare. In 12.04, it would stay at the top for a bit and then go away if you clicked anywhere in the full screen window. With 14.04, it doesn't show up at all anymore but it is still "there". It is a ghost of it and then will be a selectable option. If you click in the full screen window anywhere, the taskbar does not show at the top, but it is still selectable as an option. The "focus" does not go to the full screen. You can do things in there as long as the thing you are trying to do doesn't reside at the top of the screen where it would be the taskbar. Once you select the "top of the screen where the taskbar should be, this makes the VMWare window the active window in xorg, it then goes on top of the taskbar again. This is a major inconvenience bug because when you try to select anything in the top right while the taskbar is still "on top" of the full screen without appearing to be on top, it will select either the calendar or power settings or anything up in the top right. Attached are screenshots as the process happens. Step 1. Click on the screen which ISN'T FULL SCREEN VMWARE. Step 2. Click anywhere in full screen VMWare window except top where taskbar resides. Taskbar is hidden but still "on top". Step 3. Click where taskbar is in right corner and it will overtake the full screen window. You can select date, power, english, etc.. Step 4. Click anywhere else at very top of screen, taskbar will then go away and VMWare fullscreen will work properly. EDIT: Apparently I have been calling the bar at the top the wrong name. It's MenuBar. The Ubuntu MenuBar is not playing well with fullscreen VMWare Workstation. It also doesn't show up for using File, Edit, etc... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,resize,mousepoll,regex,gnomecompat,imgpng,place,wall,snap,animation,grid,unitymtgrabhandles,move,fade,vpswitch,expo,session,workarounds,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 30 10:47:50 2014 DistUpgraded: 2014-04-28 18:43:58,883 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f6] InstallationDate: Installed on 2013-06-07 (327 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MachineType: LENOVO 2392ARU ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=2abc73fb-99e8-4973-8796-c8fb273307bb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-28 (1 days ago) dmi.bios.date: 02/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET93WW (2.53 ) dmi.board.asset.tag: Not Available dmi.board.name: 2392ARU dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET93WW(2.53):bd02/22/2013:svnLENOVO:pn2392ARU:pvrThinkPadT530:rvnLENOVO:rn2392ARU:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2392ARU dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2
[Desktop-packages] [Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
Any fix for vivid? Tried the sane backend dev ppa, but was getting crash notifications on boot. Have a lide 210. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends package in Fedora: New Status in sane-backends package in Gentoo Linux: Unknown Bug description: I have a HP Scanject 2100c and a Canoscan LIDE-25 both of which use the Sane plustek backend for comms. My PC only has a USB 3 root hub, when either of these devices are connected, either directly or via an external USB 2 hub, they do not work. In general (although not always), 'scanimage -L' will detect the scanner ok: device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c flatbed scanner however there is always about a 30s delay before the shell prompt is returned. Scanning always fails however, using the suggested method on the sane HOW-TO page: scanimage -vvv -format pnm >outfile.pnm Calling sane_exit is the usual response. By enabling debug on the plustek backend, the response I normally get results in the following: [plustek] Vendor ID=0x03F0, Product ID=0x0505 [plustek] usbio_DetectLM983x [plustek] * could not read version register! [plustek] open failed: -1 [plustek] sane_get_devices (0x7fff0686dbc8, 0) In an effort to try and diagnose this, I've build the latest SANE backends from scratch and tried out the latest libusb none of which has resolved the issue. My original kernel was a 3.5.x, I pushed it up to 3.8.0-30 this also made no difference. My guess based on what I've seen is that this is related to the USB 3 hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel with USB 2 hub) and I've had the Canon one working (albeit not that reliably) on a Raspberry Pi with a 3.6.11 kernel. The key difference (aside from this being a 64 bit flavour of Linux) is the USB. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libsane 1.0.22-7ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.5 Architecture: amd64 Date: Mon Nov 11 19:41:08 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1475174] [NEW] Unity launcher badges too small for smaller icons
Public bug reported: If, using unity-tweak, you drop the size of launcher icons down to a smaller size - say 32px - the badges that count things like unread messages are too small. This has been a bug since 14.04 and persists through 15.04. There should be a minimum size for badges so that they are always readable. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-services 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,imgpng,vpswitch,unitymtgrabhandles,move,compiztoolbox,mousepoll,resize,regex,gnomecompat,place,session,wall,animation,expo,workarounds,fade,ezoom,scale,unityshell] CurrentDesktop: Unity Date: Thu Jul 16 08:12:57 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-22-generic, x86_64: installed nvidia-346-updates, 346.59, 3.19.0-15-generic, x86_64: installed nvidia-346-updates, 346.59, 3.19.0-22-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3683] InstallationDate: Installed on 2015-07-11 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=33ba1dec-b49f-45c6-bd17-aa4011f8abfb ro priority=low acpi=off nomodeset quiet splash nomodeset video=uvesafb:mode_option=1680x1050-32,mtrr=3,scroll=ywrap SourcePackage: unity UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Wed Jul 15 20:01:29 2015 xserver.configfile: default xserver.devices: inputDasKeyboard KEYBOARD, id 6 inputDasKeyboard KEYBOARD, id 7 inputLogitech M570MOUSE, id 8 inputUVC Camera (046d:0990) KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1475174 Title: Unity launcher badges too small for smaller icons Status in unity package in Ubuntu: New Bug description: If, using unity-tweak, you drop the size of launcher icons down to a smaller size - say 32px - the badges that count things like unread messages are too small. This has been a bug since 14.04 and persists through 15.04. There should be a minimum size for badges so that they are always readable. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity-services 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generi