[Desktop-packages] [Bug 1512886] [NEW] No sound in headphone at boot until they're unplugged and replugged in
Public bug reported: Realtek ALC889. It also works to go to sound settings and manually select headphones as output. I didn't used to have to unplug and replug the headphones to get the sound working but I can't remember which version. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gnarlin2148 F pulseaudio /dev/snd/controlC0: gnarlin2148 F pulseaudio /dev/snd/controlC1: gnarlin2148 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 3 22:01:08 2015 InstallationDate: Installed on 2014-10-25 (374 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To be filled by O.E.M., Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to vivid on 2015-05-05 (182 days ago) dmi.bios.date: 05/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FCb dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrFCb:bd05/31/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1512886 Title: No sound in headphone at boot until they're unplugged and replugged in Status in alsa-driver package in Ubuntu: New Bug description: Realtek ALC889. It also works to go to sound settings and manually select headphones as output. I didn't used to have to unplug and replug the headphones to get the sound working but I can't remember which version. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gnarlin2148 F pulseaudio /dev/snd/controlC0: gnarlin2148 F pulseaudio /dev/snd/controlC1: gnarlin2148 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 3 22:01:08 2015 InstallationDate: Installed on 2014-10-25 (374 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [To be filled by O.E.M., Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to vivid on 2015-05-05 (182 days ago) dmi.bios.date: 05/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FCb dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrFCb:bd05/31/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1512886/+su
[Desktop-packages] [Bug 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
It's been weeks. Is there anything happening to getting this fixed in the packages? I can't upgrade because of this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Is this bug getting fixed any time soon? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in boinc package in Ubuntu: Fix Released Status in fglrx-installer package in Ubuntu: In Progress Status in fglrx-installer-updates package in Ubuntu: In Progress Status in nvidia-cuda-toolkit package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-310-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-313-updates package in Ubuntu: Invalid Status in nvidia-graphics-drivers-319 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-319-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in pycuda package in Ubuntu: Fix Released Status in pyopencl package in Ubuntu: Fix Released Status in starpu-contrib package in Ubuntu: Fix Released Status in viennacl package in Ubuntu: Invalid Status in nvidia-cuda-toolkit package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1129409] Re: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.
Because of this critical bug I am downgrading to 14.04. This is the sort of problem that should be fixed in the beta. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1129409 Title: Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc. Status in “boinc” package in Ubuntu: Fix Released Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “nvidia-cuda-toolkit” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-310-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-313-updates” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-340” package in Ubuntu: Confirmed Status in “pycuda” package in Ubuntu: Fix Released Status in “pyopencl” package in Ubuntu: Fix Released Status in “starpu-contrib” package in Ubuntu: Fix Released Status in “viennacl” package in Ubuntu: Invalid Status in “nvidia-cuda-toolkit” package in Debian: Fix Released Bug description: The nvidia-cuda-toolkit package needs to depend on a minimum version of the CUDA library included in nvidia-graphics-drivers. The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on Debian systems by checking the version of libcuda1 and on Ubuntu systems by checking the version of nvidia-current, nvidia-curent-updates, nvidia-experimental-304 or nvidia-experimental-310. It would greatly simplify maintenance of packages building against libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could provide virtual packages that reflect the API level, for example, libcuda-5.0-1 and libopencl-1.2-1. It was decided that the nvidia drivers packages will provide libcuda-5.0-1, libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, nvidia-*.shlibs would contain: libOpenCL 1 libopencl1 libcuda1 libcuda-5.0-1 libGL 1 libgl1 Similarly, the amd drivers package will provide libopencl1 and opencl-icd virtual packages, as well as an .shlibs containing: libOpenCL 1 libopencl1 libGL 1 libgl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1129409/+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 1384965] [NEW] fglrx 2:14.200-0ubuntu1: fglrx kernel module failed to build
Public bug reported: After upgrading from 14.04 to 14.10 X fails to boot. After re-building fglrx modle, installing and rebooting X still won't start. Purged fglrx and fglrx-dev. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 DKMSKernelVersion: 3.16.0-23-generic Date: Thu Oct 23 21:49:25 2014 DistUpgraded: 2014-10-23 21:53:48,727 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.13.0-37-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-23-generic, x86_64: installed DuplicateSignature: dkms:fglrx:2:14.200-0ubuntu1:/var/lib/dkms/fglrx/14.200/build/2.6.x/firegl_public.c:1787:5: error: incompatible types when returning type ‘kuid_t’ but ‘KCL_TYPE_Uid’ was expected GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XT [Radeon HD 7790/8770 / R9 260 OEM] [1002:665c] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:226a] InstallationDate: Installed on 2014-01-10 (286 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageVersion: 2:14.200-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=72f3dfbb-51d8-48bd-bdd9-47d66bd1227b ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: fglrx 2:14.200-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (0 days ago) dmi.bios.date: 05/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FCb dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrFCb:bd05/31/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 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.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Oct 23 22:26:01 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1384965 Title: fglrx 2:14.200-0ubuntu1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: After upgrading from 14.04 to 14.10 X fails to boot. After re-building fglrx modle, installing and rebooting X still won't start. Purged fglrx and fglrx-dev. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 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 DKMSKernelVersion: 3.16.0-23-generic Date: Thu Oct 23 21:49:25 2014 DistUpgraded: 2014-10-23 21:53:48,727 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.13.0-37-generic, x86_64: installed virtualbox, 4.3.18, 3.16.0-23-generic, x86
[Desktop-packages] [Bug 1326994] [NEW] After settings the input method to chinese pinyin many letters don't offer suggestions for chinese characters
Public bug reported: After going to text entry settings, adding chinese (pingyin), choosing pinyin from the drop-down menu I try to type a word starting with a or o but no suggestions are shown. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 23:03:26 2014 SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus-pinyin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-pinyin in Ubuntu. https://bugs.launchpad.net/bugs/1326994 Title: After settings the input method to chinese pinyin many letters don't offer suggestions for chinese characters Status in “ibus-pinyin” package in Ubuntu: New Bug description: After going to text entry settings, adding chinese (pingyin), choosing pinyin from the drop-down menu I try to type a word starting with a or o but no suggestions are shown. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ibus-pinyin 1.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 5 23:03:26 2014 SourcePackage: ibus-pinyin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-pinyin/+bug/1326994/+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 1241656] [NEW] can't get chinese pinyin input method to work on 13.10
Public bug reported: No matter what I try I can't write using chinese charactes anymore. It worked perfectly in 13.04. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: chinese ibus input method ** Description changed: - No matter what I try I can't get write using chinese charactes. It + No matter what I try I can't write using chinese charactes anymore. It worked perfectly in 13.04. -- 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/1241656 Title: can't get chinese pinyin input method to work on 13.10 Status in “ibus” package in Ubuntu: New Bug description: No matter what I try I can't write using chinese charactes anymore. It worked perfectly in 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1241656/+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
