[Desktop-packages] [Bug 2062387] Re: cheese stops working when video record button is pressed
Hi, Pls remove this, It is not important anymore, I will wait for the new LTS to see if the problem exists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/2062387 Title: cheese stops working when video record button is pressed Status in cheese package in Ubuntu: New Bug description: Ubuntu 22.4.4 , Webcam Logitech C279 HD, cheese 44 installed by snap The camera works and pictures can be taken but as soon as Video button is pressed Cheese crashes, probably due to Audio? cheese Gtk-Message: 17:12:58.813: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. (cheese:31586): Gtk-WARNING **: 17:12:58.880: GTK+ module /snap/cheese/40/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 17:12:58.880: Failed to load module "canberra-gtk-module" (cheese:31586): Gtk-WARNING **: 17:12:58.882: GTK+ module /snap/cheese/40/gnome-platform/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded. GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported. Gtk-Message: 17:12:58.882: Failed to load module "canberra-gtk-module" (cheese:31586): cheese-WARNING **: 17:12:59.963: Can't find vp8enc preset: "Profile Realtime", using alternate preset: "Cheese Realtime". If you see this, make a bug report! (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.963: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): GStreamer-WARNING **: 17:12:59.986: gst_value_deserialize_g_value_array: unimplemented (cheese:31586): cheese-WARNING **: 17:13:03.425: Failed to connect stream: Access denied: ../ext/pulse/pulsesrc.c(1622): gst_pulsesrc_prepare (): /GstCameraBin:camerabin/GstAutoAudioSrc:audiosrc/GstPulseSrc:audiosrc- actual-src-puls (cheese:31586): cheese-WARNING **: 17:13:03.426: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstAutoAudioSrc:audiosrc/GstPulseSrc:audiosrc-actual-src-puls: streaming stopped, reason not-negotiated (-4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/2062387/+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 611265] Re: canberra-gtk-play gobbles ram when no sound device is available
It seems like your system is experiencing a memory allocation failure while trying to play sound using the canberra-gtk-play library. This can be caused by a variety of issues, but one possible reason could be that your sound card is not being detected properly by your system. You may want to check if your sound card is properly installed and recognized by your operating system. You can do this by running the "lspci" command in a terminal and looking for your sound card in the output. If your sound card is not listed, you may need to install the proper drivers or firmware for it. Another possible reason for the memory allocation failure is that your system may be low on memory. You can check this by running the "free -m" command in a terminal and looking at the output. If your system is low on memory, you may need to close some applications like https://usernamesideas.com/ or upgrade your system's RAM. If neither of these solutions work, you may want to try reinstalling the canberra-gtk-play library or seeking further assistance from the Ubuntu community or support team. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/611265 Title: canberra-gtk-play gobbles ram when no sound device is available Status in libcanberra package in Ubuntu: New Bug description: my sound card doesn't come up automatically, and canberra-gtk-play seems to not like that one little bit: Jul 29 07:54:52 hulla kernel: [ 140.491494] Out of memory: kill process 1516 (gnome-session) score 85435 or a child Jul 29 07:54:52 hulla kernel: [ 140.492817] Killed process 1572 (canberra-gtk-pl) vsz:235188kB, anon-rss:1308kB, file-rss:0kB [...] Jul 29 07:56:47 hulla kernel: [ 256.040878] Out of memory: kill process 1806 (gnome-session) score 75932 or a child Jul 29 07:56:47 hulla kernel: [ 256.040881] Killed process 1818 (canberra-gtk-pl) vsz:154476kB, anon-rss:1200kB, file-rss:20kB Jul 29 07:56:47 hulla kernel: [ 256.040892] canberra-gtk-pl: page allocation failure. order:0, mode:0x201da Jul 29 07:56:47 hulla kernel: [ 256.040894] Pid: 1818, comm: canberra-gtk-pl Not tainted 2.6.35-11-generic #16-Ubuntu etc ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libcanberra-gtk0 0.25-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-11.16-generic 2.6.35-rc5 Uname: Linux 2.6.35-11-generic x86_64 Architecture: amd64 Date: Thu Jul 29 08:36:54 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) ProcEnviron: LANGUAGE=en_GB:en_US:en PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libcanberra To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/611265/+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 1967935] [NEW] there is no bluetooth in 22.04
Public bug reported: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1967935 Title: there is no bluetooth in 22.04 Status in bluez package in Ubuntu: New Bug description: 21.10 there was bluetooth no problem 22.04 bluetooth is off and stays off ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 20:07:02 2022 InstallationDate: Installed on 2022-01-30 (65 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: bnep btusb bluetooth MachineType: GOOGLE Panther ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-31 (5 days ago) dmi.bios.date: 01/04/2019 dmi.bios.release: 4.0 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.9 dmi.board.name: Panther dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.9:bd01/04/2019:br4.0:efr0.0:svnGOOGLE:pnPanther:pvr1.0:rvnGOOGLE:rnPanther:rvr1.0:cvnGOOGLE:ct3:cvr:sku: dmi.product.family: Google_Beltino dmi.product.name: Panther dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1967935/+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 1886653] Re: cups-pki-expired
The same problem with HP DeskJet 3830 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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 1886869] Re: Double dock after screen lock.
Thank you for your reply, apparently i have 2 docks, disabling extensions solves this problem, but after disabling all extensions and locking the screen now i see the dock on the blocked screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886869 Title: Double dock after screen lock. Status in gnome-shell package in Ubuntu: Incomplete Bug description: After locking my screen and unlocking, i see a double dock. The first one have the trash can icon and the main one doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 15:27:41 2020 DistUpgraded: 2020-04-24 12:10:19,615 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon R7 Graphics [1458:d000] NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:375a] InstallationDate: Installed on 2020-04-04 (94 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=acb80b2e-decc-41c3-b1b0-daa06a3b7465 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (75 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A68HM-H 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.:bvrFD:bd10/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A68HM-H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: 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 N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886869/+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 1886869] [NEW] Double dock after screen lock.
Public bug reported: After locking my screen and unlocking, i see a double dock. The first one have the trash can icon and the main one doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 8 15:27:41 2020 DistUpgraded: 2020-04-24 12:10:19,615 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e6) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon R7 Graphics [1458:d000] NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:375a] InstallationDate: Installed on 2020-04-04 (94 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=acb80b2e-decc-41c3-b1b0-daa06a3b7465 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (75 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FD dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A68HM-H 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.:bvrFD:bd10/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A68HM-H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: 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 N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- 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/1886869 Title: Double dock after screen lock. Status in xorg package in Ubuntu: New Bug description: After locking my screen and unlocking, i see a double dock. The first one have the trash can icon and the main one doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
The proposed fix worked for me in Ubuntu Budgie 20.04. Now, the super key shows the menu with any keyboard layout. -- 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/1871913 Title: super key does not work with secondary keyboard layout Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] When keyboard layout is set in a secondary layout (i.e. Persian) pressing Super does not open Activities overview. It just works when the input is set on English. [ Test case ] - Enable a secondary keyboard layout - Switch to this layout - Hit super - Overview should open [ Regression potential ] Modifiers may no work well in shell context ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1871913/+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 1871913] Re: super key does not work with secondary keyboard layout
xev for primary layout: KeymapNotify event, serial 38, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FocusOut event, serial 38, synthetic NO, window 0x4e1, mode NotifyGrab, detail NotifyNonlinear FocusIn event, serial 38, synthetic NO, window 0x4e1, mode NotifyUngrab, detail NotifyNonlinear --- xev for secondary layout: KeymapNotify event, serial 38, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FocusOut event, serial 38, synthetic NO, window 0x4e1, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 38, synthetic NO, window 0x4e1, mode NotifyUngrab, detail NotifyAncestor what is the difference between NotifyNonlinear and NotifyAncestor? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1871913] Re: super key does not work with secondary keyboard layout
Obviously this is an upstream bug reported to gnome / mutter developers a while ago. As usual, they responded by being arrogant and refusing to acknowledge the problem. We will have to wait for them to open their eyes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1871913] Re: super key does not work with secondary keyboard layout
** Also affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 exactly same problem ubuntu 18.04.03 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+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 1573959] Re: On-screen text disappears after suspend
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend Status in linux-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: After resuming from a suspend, almost all text on screen is not visible. This includes menu items, text in all three boxes (list of folders, list of e-mails, e-mail body) in Thunderbird (with the curious exception of "ffl" in the File menu), top menu in Chromium (but not the menu obtained by pressing the hamburger button), and the menus produced by clicking items in the system tray. Also, the apport dialog had no text except for a few capital letters. WORKAROUND / 'FIX' (added on March 9, 2017) Several people have mentioned upgrading to kernel 4.8 or higher solves the issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 16.04, that is) by running sudo apt install linux-generic-hwe-16.04 If you are still experiencing this issue after upgrading to kernel 4.8, please share your system details in the comments. ADDITIONAL INFORMATION: * initctl restart unity-panel-service restarts the panel, but the text is still missing * suspend and resume does not fix the issue * Logging out fixes the issue * Other affected applications: ** Chromium file select dialog ** Terminal (entire window) ** ttys 1-6 (Ctrl+Alt+F1, etc.) ** Document viewer (menus) ** Software Updater ** Rhythmbox ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc ** ubuntu-bug ** Nautilus ** LibreOffice Calc (spreadsheet text contents) ** Firefox * Unity dash is not affected. * Skype is not affected. * Mousing over a button in a dialog correctly shows the text. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Apr 23 12:04:57 2016 DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics Controller [14c0:0075] InstallationDate: Installed on 2015-01-21 (457 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Compal VAW70 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) dmi.bios.date: 07/31/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01T01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Compal dmi.board.version: V1.01T01 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: VAW70 dmi.product.version: V1.01T01 dmi.sys.vendor: Compal upstart.unity-panel-service-lockscreen.log: (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not found when attempting to remove it version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-
[Desktop-packages] [Bug 1853790] [NEW] Can't connect external monitor to laptop
Public bug reported: When i plug in the hdmi cable to the laptop, the monitor does not turn on. However when i am in windows, the monitor works just fine. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 09:22:11 2019 InstallationDate: Installed on 2019-11-09 (15 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- 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/1853790 Title: Can't connect external monitor to laptop Status in mutter package in Ubuntu: New Bug description: When i plug in the hdmi cable to the laptop, the monitor does not turn on. However when i am in windows, the monitor works just fine. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: mutter 3.32.2+git20190711-2ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 09:22:11 2019 InstallationDate: Installed on 2019-11-09 (15 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853790/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Experiencing this: Device 9C:64:8B:7D:C7:3D (public) Name: Amir’s AirPods Alias: Amir’s AirPods Class: 0x00240418 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (74ec2172-0bad-4d01-8f77-997b2be0722a) UUID: Vendor specific (9bd708d7-64c7-4e9f-9ded-f6b6c4551967) Modalias: bluetooth:v004Cp200Fd0A00 RSSI: -54 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576559/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Experiencing this Device 9C:64:8B:7D:C7:3D (public) Name: Amir’s AirPods Alias: Amir’s AirPods Class: 0x00240418 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Vendor specific (74ec2172-0bad-4d01-8f77-997b2be0722a) UUID: Vendor specific (9bd708d7-64c7-4e9f-9ded-f6b6c4551967) Modalias: bluetooth:v004Cp200Fd0A00 RSSI: -54 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1767454] Re: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04
I have to say that this bug is a dissapointment. The whole samba support in Ubuntu since 18.04 is abysmal. Prior to this, I was able to access shares with no problems, now there is a problem. The bug has been posted one year ago. After changing the protoocol, I discovered I needed to change the interface too, because samba somehow insists on using virtbr0. Why? These things are a dealbreaker. My wife uses a NAS drive on our network. Each time I tried to show her the advantages of linux, some _basic_ function like using a NAS without configuring a f.. FTP client for her, just coming to the box and finding that it works, prevented her from switching. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 Status in dolphin: Unknown Status in gvfs: Fix Released Status in OEM Priority Project: New Status in samba: Unknown Status in gvfs package in Ubuntu: Fix Released Status in samba package in Ubuntu: Invalid Bug description: Ubuntu: 18.04 clean install Nautilus: 1:3.26.3-0ubuntu4 The actions taken to produce the problem: Click on “Other Locations” in Nautilus. The expected result of these actions: Samba servers to automatically show up under “Networks”. This is the behavior in Ubuntu 17.10 using Nautilus 1:3.26.0-0ub. Also, clicking on “”Windows Network” immediately shows "Folder is Empty". The actual result of these actions: The Samba servers never show up under “Networks” and clicking on "Windows Network" always immediately comes up with "Folder is Empty". Further information: This happens on both machines with a clean Ubuntu 18.04 install. My Ubuntu 17.10 machines still work like expected. I can still manually type in the Samba information in "Connect to Server" and the 18.04 machines connect just fine. From syslog: Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Activating service name='org.gnome.Nautilus' requested by ':1.13' (uid=1000 pid=1468 comm="/usr/bin/gnome-shell " label="unconfined") Apr 27 13:49:34 david-HP-ProBook-440-G2 dbus-daemon[1333]: [session uid=1000 pid=1333] Successfully activated service 'org.gnome.Nautilus' Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.131' (uid=1000 pid=4857 comm="/usr/bin/nautilus --gapplication-service " label="unconfined") Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Starting Hostname Service... Apr 27 13:49:35 david-HP-ProBook-440-G2 nautilus[4857]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Apr 27 13:49:35 david-HP-ProBook-440-G2 dbus-daemon[754]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 27 13:49:35 david-HP-ProBook-440-G2 systemd[1]: Started Hostname Service. Apr 27 13:49:40 david-HP-ProBook-440-G2 gvfsd[1432]: mkdir failed on directory /var/cache/samba: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+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 1803078] Re: Screensaver unlock screen shown twice after playing video
It may be considered a bug in Totem, actually. Is it OK for it to ask D-Bus to launch the Gnome screensaver in the first place, while not running in a Gnome session? +Bastien Nocera, what do you think[1]? [1] https://gitlab.gnome.org/GNOME/totem/commit/336154c47dc415299e54b260c5438def6afd6f8b -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1803078 Title: Screensaver unlock screen shown twice after playing video Status in cinnamon-session package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Observed behaviour: resuming from screensaver, after unlocking the screen with a password, the desktop is shown briefly and is immediately locked again, but with a different look-and-feel lock screen. Entering the password once more will finally show the desktop. This started happening seemingly sporadically, and would continue to happen consistently until end of session (logout or shutdown). Digging further, it was found that a `gnome-screensaver` process was running in addition to the normal `cinnamon-screensaver`. It was a child process of `systemd --user`, so a `ps -o pid,comm,cgroup` found that it was running as part of `dbus.service`. Finally, the culprit was found in the journal for that unit (`dbus.service`): Nov 12 15:03:40 laptop dbus-daemon[1696]: [session uid=1000 pid=1696] Activating service name='org.gnome.ScreenSaver' requested by ':1.206' (uid=1000 pid=3445 comm="/usr/bin/totem --gapplication-service " label="unconfined") So, the workaround (which I am quite happy with, frankly) is to use VLC instead of Totem. ☺ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cinnamon-session 3.6.1-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Nov 13 08:56:37 2018 InstallationDate: Installed on 2018-10-31 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: cinnamon-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1803078/+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 1803078] Re: Screensaver unlock screen shown twice after playing video
** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1803078 Title: Screensaver unlock screen shown twice after playing video Status in cinnamon-session package in Ubuntu: New Status in totem package in Ubuntu: New Bug description: Observed behaviour: resuming from screensaver, after unlocking the screen with a password, the desktop is shown briefly and is immediately locked again, but with a different look-and-feel lock screen. Entering the password once more will finally show the desktop. This started happening seemingly sporadically, and would continue to happen consistently until end of session (logout or shutdown). Digging further, it was found that a `gnome-screensaver` process was running in addition to the normal `cinnamon-screensaver`. It was a child process of `systemd --user`, so a `ps -o pid,comm,cgroup` found that it was running as part of `dbus.service`. Finally, the culprit was found in the journal for that unit (`dbus.service`): Nov 12 15:03:40 laptop dbus-daemon[1696]: [session uid=1000 pid=1696] Activating service name='org.gnome.ScreenSaver' requested by ':1.206' (uid=1000 pid=3445 comm="/usr/bin/totem --gapplication-service " label="unconfined") So, the workaround (which I am quite happy with, frankly) is to use VLC instead of Totem. ☺ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cinnamon-session 3.6.1-1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Tue Nov 13 08:56:37 2018 InstallationDate: Installed on 2018-10-31 (12 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: cinnamon-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1803078/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
Correction - after two restarts switching back and forth, the output is as follows: sudo cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr::00:02.0 1:DIS: :Off::01:00.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1757180] Re: nvidia-prime can't switch off the discrete GPU
This bug was not fixed. It still affects me. The GPU doesn't go off, so the power consumption remains pretty high (and the fan keeps on going). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+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 1689110] Re: There are two keyboards for the Hausa language with the same name
Awesome! When is this supposed to be distributed to Ubuntu users? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1689110 Title: There are two keyboards for the Hausa language with the same name Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Triaged Bug description: The keyboard selection window has two entries for the Hausa language. To reproduce: * Click "Text Entry Settings". * Click the + * Scroll down to H There are two entries with the identical name "Hausa". They should have different names so that it would be clear what is the difference between them. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun May 7 20:01:29 2017 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-02-26 (801 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2017-04-19 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1689110/+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 1689110] [NEW] There are two keyboards for the Hausa language with the same name
Public bug reported: The keyboard selection window has two entries for the Hausa language. To reproduce: * Click "Text Entry Settings". * Click the + * Scroll down to H There are two entries with the identical name "Hausa". They should have different names so that it would be clear what is the difference between them. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun May 7 20:01:29 2017 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-02-26 (801 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2017-04-19 (18 days ago) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1689110 Title: There are two keyboards for the Hausa language with the same name Status in unity-control-center package in Ubuntu: New Bug description: The keyboard selection window has two entries for the Hausa language. To reproduce: * Click "Text Entry Settings". * Click the + * Scroll down to H There are two entries with the identical name "Hausa". They should have different names so that it would be clear what is the difference between them. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun May 7 20:01:29 2017 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-02-26 (801 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity-control-center UpgradeStatus: Upgraded to zesty on 2017-04-19 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1689110/+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 1505216] [NEW] Bug 1277245
Public bug reported: Using the nvidia card with prime-select nvidia, display freezes randomly. Recovery possible by ctrlaltF1 altF7. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.93 Wed Aug 19 16:49:15 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 12 14:17:07 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3901] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3901] InstallationDate: Installed on 2014-12-11 (304 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO Lenovo G580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=d7e6e24a-be6e-41ac-a885-7ae1d3fc2319 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN33WW(V2.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Product Name dmi.board.vendor: LENOVO dmi.board.version: Mainboard version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G580 dmi.modalias: dmi:bvnLENOVO:bvr5ECN33WW(V2.03):bd06/06/2012:svnLENOVO:pnLenovoG580:pvrLenovoG580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoG580: dmi.product.name: Lenovo G580 dmi.product.version: Lenovo G580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Oct 12 14:16:14 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install trusty ubuntu -- 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/1505216 Title: Bug 1277245 Status in xorg package in Ubuntu: New Bug description: Using the nvidia card with prime-select nvidia, display freezes randomly. Recovery possible by ctrlaltF1 altF7. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.93 Wed Aug 19 16:49:15 PDT 2015 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 12 14:17:07 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3901] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3901] InstallationDate: Installed on 2014-12-11 (304 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO Lenovo G580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=d7e6e24a-be6e-41ac-a885-7ae1d3fc2319 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/06/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5ECN33WW
Re: [Desktop-packages] [Bug 1277245] Re: nvidia prime causing mouse and screen to freeze
Should this be done after the freeze occurs? For instance, from the terminal? Or at anytime? Amir 2015-10-11 15:11 GMT+02:00 Christopher M. Penalver < christopher.m.penal...@gmail.com>: > Amir, it will help immensely if you filed a new report via a terminal: > ubuntu-bug xorg > > Please ensure you have the package xdiagnose installed, and that you > click the Yes button for attaching additional debugging information. > > Also, please feel free to subscribe me to it. > > ** Changed in: xorg (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1277245 > > Title: > nvidia prime causing mouse and screen to freeze > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of > 6th Feb. 64bit. > After installing nvidia-prime and nvidia-331, i can see frequent mouse > freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. > Only way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back > by unloading and loading the psmouse module > > modprobe -r psmouse. > > lspci | grep VGA > 00:02.0 VGA compatible controller: Intel Corporation Core Processor > Integrated Graphics Controller (rev 18) > 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce > 310M] (rev a2) > > > uname -a > Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 > UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/lsb-release > DISTRIB_ID=Ubuntu > DISTRIB_RELEASE=14.04 > DISTRIB_CODENAME=trusty > DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" > > This issue does not occur while running the opensource driver. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+subscriptions > -- 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/1277245 Title: nvidia prime causing mouse and screen to freeze Status in xorg package in Ubuntu: Incomplete Bug description: I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th Feb. 64bit. After installing nvidia-prime and nvidia-331, i can see frequent mouse freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by unloading and loading the psmouse module modprobe -r psmouse. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) uname -a Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" This issue does not occur while running the opensource driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+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 1277245] Re: nvidia prime causing mouse and screen to freeze
This shouldn't be marked as expired. The bug still affects me, the display freezes periodically when using the nvidia card and can only be recovered by switching in an out of the dm. However, this makes normal work impossible. So I think everybody just uses their intel card instead. This doesn't mean that the bug doesnt exist. -- 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/1277245 Title: nvidia prime causing mouse and screen to freeze Status in xorg package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th Feb. 64bit. After installing nvidia-prime and nvidia-331, i can see frequent mouse freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by unloading and loading the psmouse module modprobe -r psmouse. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) uname -a Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" This issue does not occur while running the opensource driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+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 1277245] Re: nvidia prime causing mouse and screen to freeze
** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- 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/1277245 Title: nvidia prime causing mouse and screen to freeze Status in xorg package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th Feb. 64bit. After installing nvidia-prime and nvidia-331, i can see frequent mouse freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by unloading and loading the psmouse module modprobe -r psmouse. lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) uname -a Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" This issue does not occur while running the opensource driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+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 1452373] [NEW] Keyboard language switching shortcut doesn't work
Public bug reported: In lightdm's login page the shortcut keys for switching the keyboard language don't work. As a result, every time you resume from suspend or want to unlock the computer you have to use your mouse to switch the language back to English in order to enter your password. Having to do this every time is slow and frustrating. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Description changed: In lightdm's login page the shortcut keys for switching the keyboard language don't work. - As a result, every time you suspend from resume or want to unlock the computer you have to use your mouse to switch the language back to English in order to enter your password. Having to do this every time is slow and frustrating. + As a result, every time you resume from suspend or want to unlock the computer you have to use your mouse to switch the language back to English in order to enter your password. Having to do this every time is slow and frustrating. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1452373 Title: Keyboard language switching shortcut doesn't work Status in lightdm package in Ubuntu: New Bug description: In lightdm's login page the shortcut keys for switching the keyboard language don't work. As a result, every time you resume from suspend or want to unlock the computer you have to use your mouse to switch the language back to English in order to enter your password. Having to do this every time is slow and frustrating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1452373/+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 1302416] Re: deja-dup monitor was taking 6GB of memory
Same problem after installing xrdp on trusty. Simply purged deja-dup and problem was fixed :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1302416 Title: deja-dup monitor was taking 6GB of memory Status in deja-dup package in Ubuntu: Confirmed Status in deja-dup package in Debian: Unknown Bug description: Booted fresh, computer started to be slow and after a while i realized deja-dup monitor was taking 6GB of memory. Haven't tried rebooted again. Will do so in a moment. Sorry can't provide more info :/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:40:07 2014 InstallationDate: Installed on 2011-11-21 (864 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=ca_ES TERM=xterm PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416/+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 1425003] [NEW] compiz uses high cpu usage when seconday monitor is plugged in during logging in
Public bug reported: This is ongoing issue that I've been having since 12.04. Now I'm on 14.04 the issue still persist. On my netbook which runs on Intel GMA 3150 graphic video, if I log into my account while secondary monitor plugged in, it's almost guaranteed that compiz process will go wild and take unusually high cpu usage than normal, rendering desktop to crawl even when doing simple thing like hovering mouse pointer over launcher icon. However I'm not seeing this problem if I plug the secondary monitor only after Ive already logged into my user account. I've been doing that as workaround to this problem though it's not very convenience having to unplug and replug the monitor at every boot up/reboot. Can someone please look into this? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 24 17:48:46 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.22, 3.13.0-45-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (328 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 24 16:00:04 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17 vendor INL xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1425003 Title: compiz uses high cpu usage when seconday monitor is plugged in during logging in Status in compiz package in Ubuntu: New Bug description: This is ongoing issue that I've been having since 12.04. Now I'm on 14.04 the issue still persist. On my netbook which runs on Intel GMA 3150 graphic video, if I log into my account while secondary monitor plugged in, it's almost guaranteed that compiz process will go wild and take unusually high cpu usage than normal, rendering desktop to crawl even when doing simple thing like hovering mouse pointer over launcher icon. However I'm not seeing this problem if I plug the secondary monitor only after Ive already logged into my user account. I've been doing that as workaround to this problem though it's not very convenience having to unplug and replug the monitor at every boot up/reboot. Can someone please look into this? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11.3+14.04.2
[Desktop-packages] [Bug 1413808] [NEW] texlive polyglossia bidi package missing in some configurations
Public bug reported: It is possible for users to have a configuration where Hebrew doesn't work in XeLaTeX without a reasonable cause. The package texlive-lang-hebrew is a dummy package, that depends on texlive-lang-other. The package texlive-lang-other includes the "polyglossia" tex package, a modern replacement for the "babel" package, and also includes Hebrew fonts. When polyglossia is used in a tex document with RTL languages, such as Hebrew, it automatically loads the "bidi" package. However, the "bidi" tex package is not included in texlive-lang-other, only in texlive-lang-arabic (the package for Arabic and Farsi). Therefore, if a user only installs the Hebrew language pack, and uses Hebrew in a tex document with polyglossia, she gets an error "File `bidi.sty' not found". My proposed solution: either a) include bidi.sty and its dependencies in texlive-lang-other, or b) make texlive-lang-hebrew a real package: split the hebrew fonts from texlive-lang-other, and polyglossia, and maybe some other stuff, and also copy the "bidi" package from texlive-lang-arabic. ** Affects: texlive-lang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-lang in Ubuntu. https://bugs.launchpad.net/bugs/1413808 Title: texlive polyglossia bidi package missing in some configurations Status in texlive-lang package in Ubuntu: New Bug description: It is possible for users to have a configuration where Hebrew doesn't work in XeLaTeX without a reasonable cause. The package texlive-lang-hebrew is a dummy package, that depends on texlive-lang-other. The package texlive-lang-other includes the "polyglossia" tex package, a modern replacement for the "babel" package, and also includes Hebrew fonts. When polyglossia is used in a tex document with RTL languages, such as Hebrew, it automatically loads the "bidi" package. However, the "bidi" tex package is not included in texlive-lang-other, only in texlive-lang-arabic (the package for Arabic and Farsi). Therefore, if a user only installs the Hebrew language pack, and uses Hebrew in a tex document with polyglossia, she gets an error "File `bidi.sty' not found". My proposed solution: either a) include bidi.sty and its dependencies in texlive-lang-other, or b) make texlive-lang-hebrew a real package: split the hebrew fonts from texlive-lang-other, and polyglossia, and maybe some other stuff, and also copy the "bidi" package from texlive-lang-arabic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-lang/+bug/1413808/+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 1333935] [NEW] Unity now prompts 2 unlock screen upon resuming from suspend
Public bug reported: For some unknown reasons, when I resume my Ubuntu from suspend, I am prompted with the old unlock screen (one that we had before Trusty) and subsequently the new Unity built-in unlock screen after I unlocked the old lock screen http://i.imgur.com/CBah4Hk.jpg http://i.imgur.com/ANCLKdk.jpg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jun 24 20:06:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-27-generic, i686: installed vboxhost, 4.3.12, 3.13.0-29-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (84 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 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-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 23 11:26:59 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17 vendor INL xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1333935 Title: Unity now prompts 2 unlock screen upon resuming from suspend Status in “unity” package in Ubuntu: New Bug description: For some unknown reasons, when I resume my Ubuntu from suspend, I am prompted with the old unlock screen (one that we had before Trusty) and subsequently the new Unity built-in unlock screen after I unlocked the old lock screen http://i.imgur.com/CBah4Hk.jpg http://i.imgur.com/ANCLKdk.jpg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jun 24 20:06:04 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.12, 3.13.0-27-generic, i686: installed vboxhost, 4.3.12, 3.13.0-29-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Devi
[Desktop-packages] [Bug 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen
Using CapsLock as the shortcut on 14.04, pressing in while in the lock screen behaves as if it is not defined (classic behaviour). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1244548 Title: Keyboard shortcut for changing keyboard layout does not work on lock and login screen Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Shortcut for changing keyboard layout does not work on lock screen (to change keyboard layout for entering password). - Switch to some non-english layout (otherwise lock screen will not have layout indicator at all) - Lock the screen - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it will not change layout - Clicking layout indicator near password entry box works -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 11:01:10 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-10-23 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548/+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 1182007] Re: Failed to SUID root
Same problem here May 19 09:19:10 amir-laptop signond[2306]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available. running 14.04 TLS (64-bit) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1182007 Title: Failed to SUID root Status in “signon” package in Ubuntu: Confirmed Bug description: signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init Failed to SUID root. Secure storage will not be available. This report appears in syslog each time Empathy tries and fails to connect to Google Talk using the google-talkplugin interface. It is not clear whether this SUID report is related to the Empathy failure. See bug #1168582 "Google talk "Requires Authorization" after suspend/resume" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+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 1314939] [NEW] Some elements in UI don't honor UI scale settings anymore
Public bug reported: My laptop is connected to an external monitor which I use as primary display. After few normal routines of suspend and wakeup everyday, I notice some UI elements in Unity don't respect UI scale settings anymore when my laptop wakes up and resume my login session and Unity even ignore the settings completely when I adjust around the UI scale in Display applet. Please see screenshot links below http://i.imgur.com/y1ZXmCL.png http://i.imgur.com/wCmtNZ2.png http://i.imgur.com/XVbshir.png http://i.imgur.com/7va9taj.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 1 15:51:33 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.10, 3.13.0-24-generic, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 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-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 20:07:51 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 268 vendor ACR xserver.version: 2:1.15.1-0ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1314939 Title: Some elements in UI don't honor UI scale settings anymore Status in “unity” package in Ubuntu: New Bug description: My laptop is connected to an external monitor which I use as primary display. After few normal routines of suspend and wakeup everyday, I notice some UI elements in Unity don't respect UI scale settings anymore when my laptop wakes up and resume my login session and Unity even ignore the settings completely when I adjust around the UI scale in Display applet. Please see screenshot links below http://i.imgur.com/y1ZXmCL.png http://i.imgur.com/wCmtNZ2.png http://i.imgur.com/XVbshir.png http://i.imgur.com/7va9taj.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 1 15:51:33 2014 DistUpgrad
[Desktop-packages] [Bug 1301918] Re: High CPU usage with Compiz upon logging into account while external monitor is plugged in
*** This bug is a duplicate of bug 1300393 *** https://bugs.launchpad.net/bugs/1300393 ** This bug has been marked a duplicate of bug 1300393 Connected external monitor causes very high cpu usage by compiz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1301918 Title: High CPU usage with Compiz upon logging into account while external monitor is plugged in Status in “compiz” package in Ubuntu: New Bug description: I've been having this issue on my laptop since some earlier versions of Ubuntu Steps to reproduce: 1. Plug in external monitor to laptop 2. Log out or restart 3. Log into user account 4. Watch compiz process consume high cpu usage causing the entire desktop become so sluggish ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 3 19:56:30 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 2 20:50:56 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17 vendor INL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+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 1301918] [NEW] High CPU usage with Compiz upon logging into account while external monitor is plugged in
Public bug reported: I've been having this issue on my laptop since some earlier versions of Ubuntu Steps to reproduce: 1. Plug in external monitor to laptop 2. Log out or restart 3. Log into user account 4. Watch compiz process consume high cpu usage causing the entire desktop become so sluggish ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz 1:0.9.11+14.04.20140328-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 3 19:56:30 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:a001] Subsystem: Intel Corporation Device [8086:a001] InstallationDate: Installed on 2014-04-01 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily i386 (20140331) MachineType: Intel Corporation Pine Trail - M CRB PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=cb7acec2-e0c5-4138-beb9-da46e06eaa8e ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.asset.tag: PTL Nanjing dmi.board.name: Pine Trail - M CRB dmi.board.vendor: Intel Corporation dmi.board.version: Revision A dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2010:svnIntelCorporation:pnPineTrail-MCRB:pvrRevisionA:rvnIntelCorporation:rnPineTrail-MCRB:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: Pine Trail - M CRB dmi.product.version: Revision A dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 2 20:50:56 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17 vendor INL xserver.version: 2:1.15.0-1ubuntu7 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063051/+files/DpkgLog.txt ** Attachment removed: "BootDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063047/+files/BootDmesg.txt ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063048/+files/BootLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063060/+files/UdevDb.txt ** Attachment removed: "UdevLog.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063061/+files/UdevLog.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063054/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063053/+files/Lspci.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063057/+files/ProcEnviron.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063049/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1301918/+attachment/4063050/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1301918 Title: High CPU usage with Compiz upon logging into account while external monitor is plugged in
[Desktop-packages] [Bug 1296093] [NEW] Allow ungrouping window or application switchers
Public bug reported: Dear Unity developers, please make it possible to ungroup same windows or applications on unity launcher. Rapid switching between same applications would be much less painful if there was such option. That’s far more important than asking if users want a “Show workspace” icon among the switcher options. Even Windows offers an option to disable application grouping in the Taskbar ** Affects: ayatana-design Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: ayatana-design Importance: Undecided Status: New -- 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/1296093 Title: Allow ungrouping window or application switchers Status in Ayatana Design: New Status in “unity” package in Ubuntu: New Bug description: Dear Unity developers, please make it possible to ungroup same windows or applications on unity launcher. Rapid switching between same applications would be much less painful if there was such option. That’s far more important than asking if users want a “Show workspace” icon among the switcher options. Even Windows offers an option to disable application grouping in the Taskbar To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1296093/+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 871808] Re: Asus N55SF/N75SF - External subwoofer not working
(in reponse t o#76) Raymond, the subwoofer signal is not a different output-bus on this laptop, it's something built into the sound card. There's no need to 'jack detect'. I have this laptop and applied the fix mentioned above. Still, my mixer only shows a stereo output (and the subwoofer works). The hardware is connected via a proietary jack, not a 1/8" or RCA jack. What I believe the problem is, is that ALSA does not assign the right "model" according to the firmware ID on this laptop, or some other mumbo-jumbo that I am not familiar with. -- 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/871808 Title: Asus N55SF/N75SF - External subwoofer not working Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Asus N55SF laptop with external subwoofer wich connects to dedicated 2.5mm plug. http://www.asus.com/Notebooks/Multimedia_Entertainment/N55SF/ In Windows it works fine but in Ubuntu it not works at all (see Ubuntu Question and Answers #173797 - https://answers.launchpad.net/ubuntu/+question/173797 ) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: pulseaudio 1:1.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denis 1957 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xdf00 irq 51' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431b73,0011' Controls : 23 Simple ctrls : 13 Date: Mon Oct 10 19:11:30 2011 ExecutablePath: /usr/bin/pulseaudio InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111005) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N55SF.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N55SF dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N55SF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2011-10-07T16:17:51.250612 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808/+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 1263078] Re: Truncate long device description in applet menu
Mathieu, I'm well are of the gtk_label_set_ellipsize() function but the reason why I didn't use in the first place is because it only cut off long string after x number of characters then append '...' to it. I didn't like the idea because you'd lose the meaningful portion of info near the end of the long string so imo it's a bad way to truncate long string in user interface In comparison, here's how a long device desc will look like under two different method of truncation gtk_label_set_ellipsize() -> Qualcomm Atheros AW-NE785 / AW-NE7... what my patch suggests -> Qualcomm Atheros AW-NE785.. PCIe Card -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1263078 Title: Truncate long device description in applet menu Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: With some network interface devices, nma_utils_get_device_description could return a very long description string so you'll end up with awkwardly wide nm applet menu that spans almost more than half of horizontal area on your screen. On small screen device like laptop and netbook where screen estate is limited , you don't really want this. So it'd be a good idea to truncate the desc string if it's too long. I'm proposing the maximum length for the desc string to be 35 characters before it gets truncated. Also truncation is done in the middle so we don't lose the info bit near the end of the desc string. I've prepared a patch for that. Please check the patch file that I attached. Screenshots Before: http://i.imgur.com/5KC84X8.png After: http://i.imgur.com/FQmGJ20.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1263078/+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 1263078] [NEW] Truncate long device description in applet menu
Public bug reported: With some network interface devices, nma_utils_get_device_description could return a very long description string so you'll end up with awkwardly wide nm applet menu that spans almost more than half of horizontal area on your screen. On small screen device like laptop and netbook where screen estate is limited , you don't really want this. So it'd be a good idea to truncate the desc string if it's too long. I'm proposing the maximum length for the desc string to be 35 characters before it gets truncated. Also truncation is done in the middle so we don't lose the info bit near the end of the desc string. I've prepared a patch for that. Please check the patch file that I attached. Screenshots Before: http://i.imgur.com/5KC84X8.png After: http://i.imgur.com/FQmGJ20.png ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: long-device-desc too-wide-menu ** Attachment added: "Truncate long device desc if it exceeds 35 characters" https://bugs.launchpad.net/bugs/1263078/+attachment/3933207/+files/truncate_long_device_desc_in_applet_menu.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1263078 Title: Truncate long device description in applet menu Status in “network-manager-applet” package in Ubuntu: New Bug description: With some network interface devices, nma_utils_get_device_description could return a very long description string so you'll end up with awkwardly wide nm applet menu that spans almost more than half of horizontal area on your screen. On small screen device like laptop and netbook where screen estate is limited , you don't really want this. So it'd be a good idea to truncate the desc string if it's too long. I'm proposing the maximum length for the desc string to be 35 characters before it gets truncated. Also truncation is done in the middle so we don't lose the info bit near the end of the desc string. I've prepared a patch for that. Please check the patch file that I attached. Screenshots Before: http://i.imgur.com/5KC84X8.png After: http://i.imgur.com/FQmGJ20.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1263078/+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 1262014] Re: Switch button to toggle automatic inclusion of online search results
** Package changed: ubuntu => unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1262014 Title: Switch button to toggle automatic inclusion of online search results Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: The idea is so that users can turn off *automatic* inclusion of online results when remote search is enabled but still allow online search to performed manully with keyword search (eg info:weather in some place). As of now, the big switch button in Privacy lets you to enable remote search and pull online results automatically as you search or disable remote search completely when it's turned off so you dont get online results at all. I think it would be desireable if there is another switch to toggle the automatic inclusion of online search results in dash. I believe some of users such as myself love the idea of being able to do online search in dash but not when results from local search are mixed together with online results as the current behaviour of dash home. TL;DR - Add switch button to disable automatic inclusion of online search in dash home but still allow remote search with keyword To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1262014/+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 1101816] Re: #define MIN_ICONSIZE 32.0 should be changed to 8.0
You mean the centered tick mark under the scale? I did it was shifted a little to the right after I changed the MIN_ICONSIZE. I thought it was intended to indicate the medium value on the scale so I include the changes in line "iconsize_adj" and "gtk_scale_add_mark" in the patch to move it back to the center, otherwise just ignore these 2 changes in the patch file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-unity in Ubuntu. https://bugs.launchpad.net/bugs/1101816 Title: #define MIN_ICONSIZE 32.0 should be changed to 8.0 Status in “gnome-control-center-unity” package in Ubuntu: In Progress Bug description: It's been approved, enabled & available in ccsm, no reason not to have in Appearances panel ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center-unity 1.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Sat Jan 19 10:50:49 2013 InstallationDate: Installed on 2012-12-28 (21 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121228) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center-unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-unity/+bug/1101816/+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 1101816] Re: #define MIN_ICONSIZE 32.0 should be changed to 8.0
This patch seems to be working fine for me..I also fixed the position of the center scale mark after changing the ICON_MINSIZE http://i.imgur.com/2wJO07i.png https://dl.dropboxusercontent.com/u/2371091/gnome-control-center- unity_1.3daily13.06.19%7E13.04-0ubuntu1_i386.deb ** Patch added: "gcc-unity min icon size 8px" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-unity/+bug/1101816/+attachment/3814379/+files/cc-appearance-panel.c.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center-unity in Ubuntu. https://bugs.launchpad.net/bugs/1101816 Title: #define MIN_ICONSIZE 32.0 should be changed to 8.0 Status in “gnome-control-center-unity” package in Ubuntu: Confirmed Bug description: It's been approved, enabled & available in ccsm, no reason not to have in Appearances panel ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center-unity 1.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Sat Jan 19 10:50:49 2013 InstallationDate: Installed on 2012-12-28 (21 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121228) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center-unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-unity/+bug/1101816/+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 1217704] [NEW] Unable to log in when default DE that was already removed still being set as default DE for a user
Public bug reported: If users install additional Desktop Environments then uninstall all the additional DE's, all user accounts that used any of the removed DEs during their last login session will be then unable to log into despite being recreated because there's no way to select alternative DE at login screen when you have a single DE installed so those accounts will be stuck with the DE that was already removed Steps to reproduce: 1. Install any additional Desktop Environment eg lxde 2. Create a new user 3. Log into lxde using that user account 4. Log out and go back to your main account 5. Remove the new user account 6. Remove all additional DE completely and now you're left with your one primary DE 7. Recreate the new user that you just removed 8. Try log into it and watch lightDM kicks you back to login screen Solutions: 1. Make lightdm fallback to primary DE when user's default DE no longer exist on system 2. Automatically remove config that stores user's default DE in /var/lib/AccountsService/users/ when removing user account ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Wed Aug 28 12:28:31 2013 InstallationDate: Installed on 2013-05-06 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1217704 Title: Unable to log in when default DE that was already removed still being set as default DE for a user Status in “lightdm” package in Ubuntu: New Bug description: If users install additional Desktop Environments then uninstall all the additional DE's, all user accounts that used any of the removed DEs during their last login session will be then unable to log into despite being recreated because there's no way to select alternative DE at login screen when you have a single DE installed so those accounts will be stuck with the DE that was already removed Steps to reproduce: 1. Install any additional Desktop Environment eg lxde 2. Create a new user 3. Log into lxde using that user account 4. Log out and go back to your main account 5. Remove the new user account 6. Remove all additional DE completely and now you're left with your one primary DE 7. Recreate the new user that you just removed 8. Try log into it and watch lightDM kicks you back to login screen Solutions: 1. Make lightdm fallback to primary DE when user's default DE no longer exist on system 2. Automatically remove config that stores user's default DE in /var/lib/AccountsService/users/ when removing user account ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Wed Aug 28 12:28:31 2013 InstallationDate: Installed on 2013-05-06 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1217704/+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 1184439] [NEW] [MacBook5, 2, Realtek ID 885, Green Headphone Out, Rear] No sound at all
Public bug reported: No sound through my headphones but my speakers work ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bahmann1950 F pulseaudio /dev/snd/pcmC0D0c: bahmann1950 F...m pulseaudio /dev/snd/timer: bahmann1950 f pulseaudio CurrentDmesg: [ 28.450149] snd_hda_intel :00:08.0: setting latency timer to 64 [ 30.321912] init: plymouth-stop pre-start process (1411) terminated with status 1 [ 373.514482] systemd-hostnamed[2722]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Mon May 27 00:18:33 2013 InstallationDate: Installed on 2013-05-23 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bahmann1950 F pulseaudio Symptom_Jack: Green Headphone Out, Rear Symptom_Type: No sound at all Title: [MacBook5,2, Realtek ID 885, Green Headphone Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB52.88Z.0088.B05.090416 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22788AA dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788AA dmi.modalias: dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA: dmi.product.name: MacBook5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1184439 Title: [MacBook5,2, Realtek ID 885, Green Headphone Out, Rear] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: No sound through my headphones but my speakers work ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bahmann1950 F pulseaudio /dev/snd/pcmC0D0c: bahmann1950 F...m pulseaudio /dev/snd/timer: bahmann1950 f pulseaudio CurrentDmesg: [ 28.450149] snd_hda_intel :00:08.0: setting latency timer to 64 [ 30.321912] init: plymouth-stop pre-start process (1411) terminated with status 1 [ 373.514482] systemd-hostnamed[2722]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Mon May 27 00:18:33 2013 InstallationDate: Installed on 2013-05-23 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: Built-in Audio - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bahmann1950 F pulseaudio Symptom_Jack: Green Headphone Out, Rear Symptom_Type: No sound at all Title: [MacBook5,2, Realtek ID 885, Green Headphone Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB52.88Z.0088.B05.090416 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22788AA dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788AA dmi.modalias: dmi:bvnAppleInc.:bvrMB52.88Z.0088.B05.090416:bd04/16/09:svnAppleInc.:pnMacBook5,2:pvr1.0:rvnAppleInc.:rnMac-F22788AA:rvr:cvnAppleInc.:ct10:cvrMac-F22788AA: dmi.product.name: MacBook5,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1184439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launc
[Desktop-packages] [Bug 871808] Re: Asus N55SF/N75SF - External subwoofer not working
I have an ASUS N55SF and I've just tried comment #34 and the subwoofer works! This is under Ubuntu 12.04 LTS. My Alsa Info: http://www.alsa-project.org/db/?f=d35ace5c8d037aa32728324df8c896de542faef2 It's worth mentioning I have JACK installed as I played around with my E-MU 0404 USB and it also works (but this is off-topic). -- 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/871808 Title: Asus N55SF/N75SF - External subwoofer not working Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Asus N55SF laptop with external subwoofer wich connects to dedicated 2.5mm plug. http://www.asus.com/Notebooks/Multimedia_Entertainment/N55SF/ In Windows it works fine but in Ubuntu it not works at all (see Ubuntu Question and Answers #173797 - https://answers.launchpad.net/ubuntu/+question/173797 ) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: pulseaudio 1:1.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denis 1957 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xdf00 irq 51' Mixer name : 'Realtek ALC663' Components : 'HDA:10ec0663,10431b73,0011' Controls : 23 Simple ctrls : 13 Date: Mon Oct 10 19:11:30 2011 ExecutablePath: /usr/bin/pulseaudio InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111005) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N55SF.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N55SF dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN55SF.207:bd08/29/2011:svnASUSTeKComputerInc.:pnN55SF:pvr1.0:rvnASUSTeKComputerInc.:rnN55SF:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N55SF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2011-10-07T16:17:51.250612 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808/+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 1175638] Re: extremely low volume macpro
The sound is normal through the internal speaker and the back speaker jack. -- 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/1175638 Title: extremely low volume macpro Status in “alsa-driver” package in Ubuntu: New Bug description: The volume is extremely low, at first I thought it wasn't working. If I turn it up to 150% I can hear it but its grainy/crackly. When I dual boot into OSX it's fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2378 F pulseaudio /dev/snd/pcmC0D0p: amir 2378 F...m pulseaudio /dev/snd/pcmC0D1c: amir 2378 F...m pulseaudio Date: Thu May 2 10:56:33 2013 InstallationDate: Installed on 2013-04-29 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: Volume slider, or mixer problems Title: [MacPro1,1, Realtek ALC889A, Green Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP11.88Z.005C.B08.0707021221 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP11.88Z.005C.B08.0707021221:bd07/02/07:svnAppleComputer,Inc.:pnMacPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.name: MacPro1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1175638/+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 1175638] [NEW] extremely low volume macpro
Public bug reported: The volume is extremely low, at first I thought it wasn't working. If I turn it up to 150% I can hear it but its grainy/crackly. When I dual boot into OSX it's fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2378 F pulseaudio /dev/snd/pcmC0D0p: amir 2378 F...m pulseaudio /dev/snd/pcmC0D1c: amir 2378 F...m pulseaudio Date: Thu May 2 10:56:33 2013 InstallationDate: Installed on 2013-04-29 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: Volume slider, or mixer problems Title: [MacPro1,1, Realtek ALC889A, Green Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP11.88Z.005C.B08.0707021221 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP11.88Z.005C.B08.0707021221:bd07/02/07:svnAppleComputer,Inc.:pnMacPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.name: MacPro1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1175638 Title: extremely low volume macpro Status in “alsa-driver” package in Ubuntu: New Bug description: The volume is extremely low, at first I thought it wasn't working. If I turn it up to 150% I can hear it but its grainy/crackly. When I dual boot into OSX it's fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amir 2378 F pulseaudio /dev/snd/pcmC0D0p: amir 2378 F...m pulseaudio /dev/snd/pcmC0D1c: amir 2378 F...m pulseaudio Date: Thu May 2 10:56:33 2013 InstallationDate: Installed on 2013-04-29 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_Type: Volume slider, or mixer problems Title: [MacPro1,1, Realtek ALC889A, Green Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/07 dmi.bios.vendor: Apple Computer, Inc. dmi.bios.version: MP11.88Z.005C.B08.0707021221 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F4208DC8 dmi.board.vendor: Apple Computer, Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Computer, Inc. dmi.chassis.version: Mac-F4208DC8 dmi.modalias: dmi:bvnAppleComputer,Inc.:bvrMP11.88Z.005C.B08.0707021221:bd07/02/07:svnAppleComputer,Inc.:pnMacPro1,1:pvr1.0:rvnAppleComputer,Inc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8: dmi.product.name: MacPro1,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Computer, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1175638/+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 1075367] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1071001 *** https://bugs.launchpad.net/bugs/1071001 ** This bug has been marked a duplicate of bug 1071001 Sound Card not detected NM10/ICH7 Intel HDA Internal -- 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/1075367 Title: PCI/internal sound card not detected Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Sound was disabled after upgrading from 12.04. Today I did a clean 12.10 install, to no avail. The only device listed is "Dummy Output". Added here some outputs that seem to be relevant: For "aplay -l": aplay: device_list:252: no soundcards found... For "cat /proc/asound/cards": --- no soundcards --- For "lspci -v | grep -A 6 Audio": 00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01) Subsystem: Dell Device 01de Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at febfc000 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel modules: snd-hda-intel For "lsb_release -rd": Description: Ubuntu 12.10 Release: 12.10 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Mon Nov 5 22:27:10 2012 InstallationDate: Installed on 2012-11-05 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0DN075 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/28/2007:svnDellInc.:pnPrecisionWorkStation390:pvr:rvnDellInc.:rn0DN075:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation 390 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1075367/+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 1022322] Re: GNOME keyring often fails to unlock in XFCE
I believe it's not only in XFCE. I'm using Mint 13 with MATE and it started showing this error when I try to push on git. SSH is working just fine though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1022322 Title: GNOME keyring often fails to unlock in XFCE Status in “gnome-keyring” package in Ubuntu: Confirmed Bug description: GNOME Keyring often fails to unlock at login in XFCE, other users in the xubuntu-users mailing list have also reported this. It affects applications using the gnome-keyring framework, including chromium / google chrome. The file causing the problem is /etc/xdg/autostart/gnome-keyring-pkcs11.desktop . The line OnlyShowIn=GNOME;Unity should be changed to OnlyShowIn=GNOME;Unity;XFCE to enable gnome-based applications using the keyring to run properly under XFCE. dpkg -S gnome-keyring-pkcs11.desktop gives gnome-keyring: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop so the package that needs to be fixed is definitely gnome-keyring. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Sun Jul 8 17:29:21 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome.keyring.pkcs11.desktop: 2012-07-08T17:29:16.745464 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1022322/+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 774417] Re: gapless playback does not work in any gstreamer application
The PPA did not fix my problem :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/774417 Title: gapless playback does not work in any gstreamer application Status in “gstreamer0.10” package in Ubuntu: Confirmed Bug description: After installing ubuntu 11.04 I installed rhythmbox (configuration files from version 10.10) and found a nasty flaw - to play without pauses between tracks no longer works. It's not very nice drawback, especially for live performances. I use the files in Flac. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libgstreamer0.10-0 0.10.32-3ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxSubmission: 75f98d6195798b80b1da540d612db817 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Sun May 1 00:30:33 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=ru_RU:en LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/774417/+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 914313] Re: Pictures in tags of audio files, which act as thumbnails, are NOT shown for ALL files in same directory
I had a similar problem, and found a workaround. All I did was completely remove the three folders in ~/.thumbnails: fail, large and normal. Nautilus then re-reads the metadata and assigns new icons to all the files on the computer. I hope this helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/914313 Title: Pictures in tags of audio files, which act as thumbnails, are NOT shown for ALL files in same directory Status in “totem” package in Ubuntu: Confirmed Bug description: Pictures embeded in tags of audio files (e.g. ID3v2 for MP3), which act as thumbnails, are NOT shown for ALL audio files in the same directory. Although all audio files have the same picture in their tags, only some random files show their thumbnails (See attached screenshots). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Jan 10 16:34:08 2012 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Package: libgstreamer0.10-0 0.10.36-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Tags: precise running-unity Uname: Linux 3.2.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/914313/+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 625793] Re: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated]
That's weird, it did not happen to me when I installed 12.04. Did happen on 11.10 but it was fixed after an upgrade (when the fix was released). -- 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/625793 Title: Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] Status in Gnome Settings Daemon: Invalid Status in Application Indicators: Fix Released Status in Release Notes for Ubuntu: Won't Fix Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Maverick: Fix Released Status in Baltix GNU/Linux: Fix Released Bug description: == General description == On some Ubuntu installs with two or more keyboard layouts (e.g. Russian and US English), after some time the keyboard layouts start switching in an endless loop and gnome-settings-daemon starts using more and more CPU until it reaches 100%. == Known information == 1) Some people here confirm that this happens with non-GTK (Java or Qt) windows more often then with native GTK. (probably, might be a coincidence) 2) Possible fixes are killing and restarting gnome-settings-daemon or disabling the "Separate layout for each window" option in keyboard preferences window. 3) The second fix, however didn't work for most people, though it might really reduce the probability of the bug appearing. 4) The bug happens both on upgrade installs and clean installs of Ubuntu, confirmed with RC and Alpha 3. 5) The bug is specific to Ubuntu, not existing in Arch Linux and AgiliaLinux. 6) There are users who experience this problem with Russian, Slovakian, Macedonian, Hebrew, Georgian layots. Having such a problem in final release will make keyboard use very problematic for users from these countries, so Ubuntu can lose many users. 7) The bug is still not fixed in GNOME 2.32, which again proves that it's an Ubuntu-specific issue. 8) For some users, the bug disappears after 2 to 15 minutes of use. 9) Confirmed for almost any key set for switching layouts (Shift+Alt, Shift+Ctrl, CapsLock, Alt, Ctrl) 10) Confirmed for both Latin and non-Latin layouts. 11) Permanent fix is to disable g-s-d keyboard plugin in gconf, not fully confirmed though. 12) Confirmed as a g-s-d issue, both with and without indicators. == Debug == APPORT DATA here: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/633167 and here: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/633346 MORE LOGS: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/636619 GDB DATA: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/629444 XSESSIONERRORS: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/630712 RANDOM LOGS: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/64082 XEV OUTPUT: infinite loop of PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174 (XKLAVIER_STATE), time 11886812, state PropertyNewValue [NEW] GSD output: (gnome-settings-daemon:2057): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed P.S. Do. Not. Touch. This. Please. There's more info here, which can make the devs remove the Incomplete status. Не трогайте это, пожалуйста. Здесь намного больше информации, чем во всех предыдущих описаниях, может снимут Incomplete. TO DEVELOPERS: Please, comment on what logs and other info you need to get this problem solved. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/625793/+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 885042] [NEW] edit filesystem label appends characters "nA" when underscores are used
Public bug reported: I edit a filesystem label for a USB disk with the following values: entered: TEST_TEST actual: TEST_TESTnA expected: TEST_TEST or an error saying why it's adding extra characters or what the rules or recommendations are for filesystem labels. It seems when an underscore is used with more than three characters it starts to pad it out with some string. entered, actual and expected: TEST entered, actual and expected: TEST_1 entered, actual and expected: TEST_A entered, actual and expected: TEST_AB entered: TEST_ABC actual: TEST_ABC nA entered: TEST_ABCDE actual: TEST_ABCDEA This was a W95 FAT32 (LBA) (0x0c) partition type, bootable flags ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-disk-utility 3.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 22:31:49 2011 ExecutablePath: /usr/bin/palimpsest ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/885042 Title: edit filesystem label appends characters "nA" when underscores are used Status in “gnome-disk-utility” package in Ubuntu: New Bug description: I edit a filesystem label for a USB disk with the following values: entered: TEST_TEST actual: TEST_TESTnA expected: TEST_TEST or an error saying why it's adding extra characters or what the rules or recommendations are for filesystem labels. It seems when an underscore is used with more than three characters it starts to pad it out with some string. entered, actual and expected: TEST entered, actual and expected: TEST_1 entered, actual and expected: TEST_A entered, actual and expected: TEST_AB entered: TEST_ABC actual: TEST_ABC nA entered: TEST_ABCDE actual: TEST_ABCDEA This was a W95 FAT32 (LBA) (0x0c) partition type, bootable flags ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-disk-utility 3.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 22:31:49 2011 ExecutablePath: /usr/bin/palimpsest ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/885042/+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 885042] Re: edit filesystem label appends characters "nA" when underscores are used
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/885042 Title: edit filesystem label appends characters "nA" when underscores are used Status in “gnome-disk-utility” package in Ubuntu: New Bug description: I edit a filesystem label for a USB disk with the following values: entered: TEST_TEST actual: TEST_TESTnA expected: TEST_TEST or an error saying why it's adding extra characters or what the rules or recommendations are for filesystem labels. It seems when an underscore is used with more than three characters it starts to pad it out with some string. entered, actual and expected: TEST entered, actual and expected: TEST_1 entered, actual and expected: TEST_A entered, actual and expected: TEST_AB entered: TEST_ABC actual: TEST_ABC nA entered: TEST_ABCDE actual: TEST_ABCDEA This was a W95 FAT32 (LBA) (0x0c) partition type, bootable flags ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-disk-utility 3.0.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Tue Nov 1 22:31:49 2011 ExecutablePath: /usr/bin/palimpsest ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/885042/+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
