[Desktop-packages] [Bug 1243642] Re: .Xmodmap not automatically loaded on start
Suggest changing the title to “Need a per-user method of remapping keys (.Xmodmap, .Xkbmap don't work)” -- 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/1243642 Title: .Xmodmap not automatically loaded on start Status in xorg package in Ubuntu: Confirmed Bug description: I'm using a ~/.Xmodmap file to define two keycode mappings. 13.10 doesn't seem to automatically load this file any more. 13.04 did. (same file, same laptop) manual execution of "xmodmap ~/.Xmodmap" works on 13.10! That means I'm e.g. able to use this key in a terminal or in geany. I discovered, that by switching the keyboard layouts using "gnome- control-center region layouts" the mappings of the "xmodmap ~/.Xmodmap" will be lost again. Then another manual execution of "xmodmap ~/.Xmodmap" has to be executed and it works again. Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control- center () later. Sorry, I can't figure out which packet this bug has to be asigned to. By using apport-bug "xorg" was choosen, but it could be "xorg-server" or "gnome-control-center", also. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 12:05:11 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:013c] Subsystem: Acer Incorporated [ALI] Device [1025:013c] InstallationDate: Installed on 2013-10-18 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Acer Extensa 5630 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 23 11:15:16 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5459 vendor CMO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+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 1243642] Re: .Xmodmap not automatically loaded on start
One thing to add (I'm shocked nobody mentioned yet): edits in anything in /usr/... will be lost next time the respective package is updated. So, even on single-user machines, a per-user (or at least /etc) option is *needed*. -- 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/1243642 Title: .Xmodmap not automatically loaded on start Status in xorg package in Ubuntu: Confirmed Bug description: I'm using a ~/.Xmodmap file to define two keycode mappings. 13.10 doesn't seem to automatically load this file any more. 13.04 did. (same file, same laptop) manual execution of "xmodmap ~/.Xmodmap" works on 13.10! That means I'm e.g. able to use this key in a terminal or in geany. I discovered, that by switching the keyboard layouts using "gnome- control-center region layouts" the mappings of the "xmodmap ~/.Xmodmap" will be lost again. Then another manual execution of "xmodmap ~/.Xmodmap" has to be executed and it works again. Perhaps the ~/.Xmodmap is loaded and lost by the the gnome-control- center () later. Sorry, I can't figure out which packet this bug has to be asigned to. By using apport-bug "xorg" was choosen, but it could be "xorg-server" or "gnome-control-center", also. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Oct 23 12:05:11 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:013c] Subsystem: Acer Incorporated [ALI] Device [1025:013c] InstallationDate: Installed on 2013-10-18 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Acer Extensa 5630 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/vg01-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Homa dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd08/11/2009:svnAcer:pnExtensa5630:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5630 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 23 11:15:16 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5459 vendor CMO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+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 499416] Re: Scanner not detected when connected after program start
How did this expire? IMO it's the most important bug of “simple scan”; it's the only one I ever noticed, and it kind of defeats the “simple” description. Most of the time I open the program first and *then* turn the scanner on… there's no reason why that shouldn't be supported. Note, the original description no longer applies 100% — there's no “list of scanners” anymore, anywhere in the UI. It simply says there are no scanners, and if you turn it on or connect after the app is running, there's no way to detect it. ** Changed in: simple-scan (Ubuntu) Status: Expired => Confirmed ** Also affects: simple-scan Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/499416 Title: Scanner not detected when connected after program start Status in Simple Scan: New Status in simple-scan package in Ubuntu: Confirmed Bug description: Turning on my scanner when simple scan is already running does not make it show up in the list of scanners. Perhaps a "rescan devices" button can be added to the preferences if automatically detecting them isn't possible? To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/499416/+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 1397142] Re: Bluetooth play/pause key not fully effective in various media players
** Summary changed: - Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee + Bluetooth play/pause key not fully effective in various media players ** Summary changed: - Bluetooth play/pause key not fully effective in various media players + Bluetooth headset play/pause key not fully effective in various media players -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Bluetooth headset play/pause key not fully effective in various media players Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings- daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run "evtest /dev/input/event9", then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run "xev" and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+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 1397142] Re: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee
+1 here, mine is a Philips SHB7150, and the problem was already present at least in 14.10, maybe earlier. Reason I'm commenting though: playing around with xev, it seems to take some black magic to predict whether I'll get XF86AudioPlay or XF86AudioPause. - If no app is playing, it's always XF86AudioPlay, regardless what combination of apps is running. - If rhythmbox is playing, it's XF86AudioPause. - If gmusicbrowser, mpv, or vlc is playing, it alternates between the two (but neither app responds to it regardless of state and event). - And mplayer probably doesn't register itself with whatever it is, since it always gets XF86AudioPlay. I also found that if vlc or mpv is focused, it does play when it's paused and I press the button; when it's playing, it will only pause every other press (thinking of the xev experiment above, I guess when the generated keysym is XF86AudioPause). The same is not true of gmusicbrowser. As for mplayer, if it's focused it responds exactly right. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1397142 Title: Sony SRS-BTM8 play/pause key not fully effective in Rhythmbox or Banshee Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: I have a Sony SRS-BTM8 Bluetooth speaker, and its audio side works fairly well with Ubuntu. It also has a play/pause button and that doesn't work so well. I think the problem lies in unity-settings- daemon. To demonstrate that the Bluetooth side is working, if I switch to a text console and run "evtest /dev/input/event9", then when pressing the button I get events for KEY_PLAYCD if the speaker is not playing anything, and alternating KEY_PAUSECD and KEY_PLAYCD if it is playing something. However, within the Unity desktop I find that if I'm running Banshee or Rhythmbox then pressing the button successfully pauses the music, but doesn't start it playing again. If I run "xev" and give it the keyboard focus while testing this (so xev sees all ungrabbed keystrokes) then it sees only a KeyRelease event for XF86AudioPause, but both KeyPress and KeyRelease events for XF86AudioPlay. I've attached the full output from xev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140606-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33~14.04.2-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Thu Nov 27 23:43:01 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (1632 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-08-15 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1397142/+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 1235991] Re: Can't “use system keyboard layout” in Saucy
Still happening on 14.04… unfortunately the upgrade killed the work- around. Any chance this could be fixed already? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy Status in “ibus” package in Ubuntu: Confirmed Bug description: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+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 1179180] Re: Impossible to open Empathy contact list window if already started with '-h' option
And if you don't want to kill you because you're in the middle of a chat… dconf write /org/gnome/empathy/ui/main-window-hidden true dconf write /org/gnome/empathy/ui/main-window-hidden false -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1179180 Title: Impossible to open Empathy contact list window if already started with '-h' option Status in “empathy” package in Ubuntu: Confirmed Bug description: If I add Empathy to 'Startup Applications' to start it with '-h' option, I'll never be able to open the contact list window. Tried: - If query with 'ps -ef | grep emapthy', I can see empathy is running. - If run 'empathy' from command line, the command exits without any output, but nothing happens after that. - If choose 'Empathy Internet Messaging' from Unity Dashboard, nothing happens. - If choose from the locked lens, I can see the icon "blinks slowly" (if you know what I mean, I'm not native speaker of English), and then it stops blinking, nothing happens after that. However, if I didn't start Empathy with '-h' option, everything seems normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 12 18:27:52 2013 InstallationDate: Installed on 2012-08-12 (273 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to raring on 2013-04-26 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1179180/+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 1235991] Re: Can't “use system keyboard layout” in Saucy
Hi ibus-ers, After the last updates, this is working correctly for me. (For “correctly” defined as, it always uses my keymap; there's still no option to turn that off that I can find, but I don't think many people would want that anyway.) I'm not 100% sure the bug is fixed, it could just be a combination between something updated in the package and something I fiddled with trying to make it work… so it would be nice if other people with a fresh system could confirm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy Status in “ibus” package in Ubuntu: Confirmed Bug description: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+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 1246624] [NEW] Reminders from Google are displayed as “This is an event reminder”
Public bug reported: When Evolution syncs from Google Calendar, event reminders are displayed at the right time, but the title of the popup is “This is an event reminder” instead of the correct text. Discussion here: http://ubuntuforums.org/showthread.php?t=2182365&p=12822808#post12822808 Release: 13.10 evolution: Installed: 3.8.4-0ubuntu1 ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” Status in “evolution” package in Ubuntu: New Bug description: When Evolution syncs from Google Calendar, event reminders are displayed at the right time, but the title of the popup is “This is an event reminder” instead of the correct text. Discussion here: http://ubuntuforums.org/showthread.php?t=2182365&p=12822808#post12822808 Release: 13.10 evolution: Installed: 3.8.4-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+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 1235991] [NEW] Can't “use system keyboard layout” in Saucy
Public bug reported: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy Status in “ibus” package in Ubuntu: New Bug description: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+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 407585] Re: use system keyboard layout setting by default
I don't know if it's the same bug or a new one, but since in Saucy ibus is more tightly integrated, this becomes more important; but beyond that, it's actually not possible (as far as I can see) to change that setting manually! So my input methods are rendered essentially useless… -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/407585 Title: use system keyboard layout setting by default Status in “ibus” package in Ubuntu: Confirmed Bug description: Binary package hint: ibus the current default for "ibus preferences - advanced - keyboard layout - use system keyboard layout" is off. I think the sane default in this case is on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/407585/+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 1168441] Re: rhyhtmbox: high cpu-usage when playing music from second hard drive
Similar, 13.04. None of rhythmbox, gnome, pulse, gstreamer, python, or gtk are affected by any PPAs, in fact as far as I can see none of the dependencies. In my case the music is in a multi-volume BTRFS mount which is auto-mounted. I don't see rhythmbox-metadata in my process list at all, instead it's the rhythmbox process itself that takes 100% of one CPU. The UI is often grey. Oddly, audio reproduction itself almost never glitches, but responding to multimedia keys or the buttons in the indicator widget sometimes takes up to a minute. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1168441 Title: rhyhtmbox: high cpu-usage when playing music from second hard drive Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: As described above. When I'm playing music from my second hard drive, which isn't auto-mounted, rhyhtmbox produces a high cpu-usage. In fact one of my four cpus is used completely by the process rhythmbox- metadata. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Fri Apr 12 16:56:54 2013 InstallationDate: Installed on 2012-11-03 (159 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to raring on 2013-04-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1168441/+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 976076] Re: Can't switch between speakers and headphones
You should say “strange” rather than “unlikely”, since I just posted that it does, indeed, work for me. I don't have the required ALSA/kernel/sound knowledge to figure out why, but it does. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/976076 Title: Can't switch between speakers and headphones Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: This is a freshly-installed Precise (from beta2 iso) on an AMD64 custom built computer; the motherboard is an ASRock N68-GE3 UCC, as you can see from the files the chipsets are all NVIDIA. The audio codec is VIA. Main problem: alsa and pulse's idea of switching between the speakers and headset is wrong. If I open alsamixer and toggle the (problematic, I heard) “Independent HP” switch, that works like a charm; turn it on and I get sound only on the speakers, turn it off and I get sound only on the headset. But nothing else (jack sense, clicking an output on Sound Settings, even muting “Front” by hand) works. Secondary problem: once that's working, it would be nice if jack sensing would do it automatically. I tried playing with the “model” flag and even “sense_mask”, but nothing works. I currently reset my alsa-base.conf to factory. I read many reports telling me to install the latest from ubuntu- audio-dev, but of course there aren't any for precise yet. Also installed some hda stuff from diwic; hda-jack-retask reports my front pin is a green headphones front pin as it's supposed to be, so I didn't override anything. And hda-jack-sense-test calls it “Green HP Out”; but only lists it with -a. lalo:~> sudo hda-jack-sense-test -a Pin 0x24 (Green Line Out): present = Yes Pin 0x25 (Black Line Out): present = No Pin 0x26 (Orange Line Out): present = No Pin 0x27 (Grey Line Out): present = No Pin 0x28 (Green HP Out): present = Yes Pin 0x29 (Pink Mic): present = No Pin 0x2a (Blue Line In): present = No Pin 0x2b (Pink Mic): present = No Pin 0x2c (Internal CD): present = No Pin 0x2d (Not connected): present = No Pin 0x2e (Not connected): present = No Pin 0x2f (Not connected): present = No ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 18:58:24 2012 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-GE3 UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/07/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GE3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-07T17:16:20.066290 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/976076/+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 976076] Re: Can't switch between speakers and headphones
Raymond, there's no such setting in my BIOS, I can turn the front panel on or off. % sudo hda-jack-sense-test -a Pin 0x24 (Green Line Out): present = Yes Pin 0x25 (Black Line Out): present = Yes Pin 0x26 (Orange Line Out): present = Yes Pin 0x27 (Grey Line Out): present = Yes Pin 0x28 (Green HP Out): present = Yes Pin 0x29 (Pink Mic): present = No Pin 0x2a (Blue Line In): present = No Pin 0x2b (Pink Mic): present = No Pin 0x2c (Internal CD): present = No Pin 0x2d (Not connected): present = No Pin 0x2e (Not connected): present = No Pin 0x2f (Not connected): present = No (That would be pin 28, as you can see it's already seen as HP Out.) However, on quantal hda-jack-retask does work, even though it's retasking the pin to the same thing it reports it already was without retasking. Go figure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/976076 Title: Can't switch between speakers and headphones Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: This is a freshly-installed Precise (from beta2 iso) on an AMD64 custom built computer; the motherboard is an ASRock N68-GE3 UCC, as you can see from the files the chipsets are all NVIDIA. The audio codec is VIA. Main problem: alsa and pulse's idea of switching between the speakers and headset is wrong. If I open alsamixer and toggle the (problematic, I heard) “Independent HP” switch, that works like a charm; turn it on and I get sound only on the speakers, turn it off and I get sound only on the headset. But nothing else (jack sense, clicking an output on Sound Settings, even muting “Front” by hand) works. Secondary problem: once that's working, it would be nice if jack sensing would do it automatically. I tried playing with the “model” flag and even “sense_mask”, but nothing works. I currently reset my alsa-base.conf to factory. I read many reports telling me to install the latest from ubuntu- audio-dev, but of course there aren't any for precise yet. Also installed some hda stuff from diwic; hda-jack-retask reports my front pin is a green headphones front pin as it's supposed to be, so I didn't override anything. And hda-jack-sense-test calls it “Green HP Out”; but only lists it with -a. lalo:~> sudo hda-jack-sense-test -a Pin 0x24 (Green Line Out): present = Yes Pin 0x25 (Black Line Out): present = No Pin 0x26 (Orange Line Out): present = No Pin 0x27 (Grey Line Out): present = No Pin 0x28 (Green HP Out): present = Yes Pin 0x29 (Pink Mic): present = No Pin 0x2a (Blue Line In): present = No Pin 0x2b (Pink Mic): present = No Pin 0x2c (Internal CD): present = No Pin 0x2d (Not connected): present = No Pin 0x2e (Not connected): present = No Pin 0x2f (Not connected): present = No ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 18:58:24 2012 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-GE3 UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/07/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GE3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-07T17:16:20.066290 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/976076/+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 976076] Re: Can't switch between speakers and headphones
Raymond, thanks, that's all very interesting technically, and to my amazement I actually understand everything you said. The average user, however, cares for none of that; they expect (in fact, even I expect, although I'm probably much techier than the “average user”) that when the headset is plugged in, sound to the speakers stops. The “independent hp” thing was ever only a workaround; the fact that it doesn't work around the issue anymore only makes the bug more urgent. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/976076 Title: Can't switch between speakers and headphones Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: This is a freshly-installed Precise (from beta2 iso) on an AMD64 custom built computer; the motherboard is an ASRock N68-GE3 UCC, as you can see from the files the chipsets are all NVIDIA. The audio codec is VIA. Main problem: alsa and pulse's idea of switching between the speakers and headset is wrong. If I open alsamixer and toggle the (problematic, I heard) “Independent HP” switch, that works like a charm; turn it on and I get sound only on the speakers, turn it off and I get sound only on the headset. But nothing else (jack sense, clicking an output on Sound Settings, even muting “Front” by hand) works. Secondary problem: once that's working, it would be nice if jack sensing would do it automatically. I tried playing with the “model” flag and even “sense_mask”, but nothing works. I currently reset my alsa-base.conf to factory. I read many reports telling me to install the latest from ubuntu- audio-dev, but of course there aren't any for precise yet. Also installed some hda stuff from diwic; hda-jack-retask reports my front pin is a green headphones front pin as it's supposed to be, so I didn't override anything. And hda-jack-sense-test calls it “Green HP Out”; but only lists it with -a. lalo:~> sudo hda-jack-sense-test -a Pin 0x24 (Green Line Out): present = Yes Pin 0x25 (Black Line Out): present = No Pin 0x26 (Orange Line Out): present = No Pin 0x27 (Grey Line Out): present = No Pin 0x28 (Green HP Out): present = Yes Pin 0x29 (Pink Mic): present = No Pin 0x2a (Blue Line In): present = No Pin 0x2b (Pink Mic): present = No Pin 0x2c (Internal CD): present = No Pin 0x2d (Not connected): present = No Pin 0x2e (Not connected): present = No Pin 0x2f (Not connected): present = No ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 18:58:24 2012 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-GE3 UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/07/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GE3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-07T17:16:20.066290 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/976076/+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 976076] Re: Can't switch between speakers and headphones
Upgraded to 12.10. Problem still exists, and “Independent HP” workaround (and therefore my script) won't work anymore :-( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/976076 Title: Can't switch between speakers and headphones Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: This is a freshly-installed Precise (from beta2 iso) on an AMD64 custom built computer; the motherboard is an ASRock N68-GE3 UCC, as you can see from the files the chipsets are all NVIDIA. The audio codec is VIA. Main problem: alsa and pulse's idea of switching between the speakers and headset is wrong. If I open alsamixer and toggle the (problematic, I heard) “Independent HP” switch, that works like a charm; turn it on and I get sound only on the speakers, turn it off and I get sound only on the headset. But nothing else (jack sense, clicking an output on Sound Settings, even muting “Front” by hand) works. Secondary problem: once that's working, it would be nice if jack sensing would do it automatically. I tried playing with the “model” flag and even “sense_mask”, but nothing works. I currently reset my alsa-base.conf to factory. I read many reports telling me to install the latest from ubuntu- audio-dev, but of course there aren't any for precise yet. Also installed some hda stuff from diwic; hda-jack-retask reports my front pin is a green headphones front pin as it's supposed to be, so I didn't override anything. And hda-jack-sense-test calls it “Green HP Out”; but only lists it with -a. lalo:~> sudo hda-jack-sense-test -a Pin 0x24 (Green Line Out): present = Yes Pin 0x25 (Black Line Out): present = No Pin 0x26 (Orange Line Out): present = No Pin 0x27 (Grey Line Out): present = No Pin 0x28 (Green HP Out): present = Yes Pin 0x29 (Pink Mic): present = No Pin 0x2a (Blue Line In): present = No Pin 0x2b (Pink Mic): present = No Pin 0x2c (Internal CD): present = No Pin 0x2d (Not connected): present = No Pin 0x2e (Not connected): present = No Pin 0x2f (Not connected): present = No ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 18:58:24 2012 PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-GE3 UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd03/07/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GE3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-07T17:16:20.066290 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/976076/+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
