[Desktop-packages] [Bug 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
** Attachment added: "_usr_bin_media-hub-server.32011.crash" https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1544477/+attachment/4756983/+files/_usr_bin_media-hub-server.32011.crash -- 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
http://paste.ubuntu.com/23290548/ -- 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1631519] Re: No X on boot with external monitor connected
** Attachment added: "moving a window across the display" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+attachment/4757009/+files/ezgif.com-video-to-gif%20%282%29.gif -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631364] [NEW] gnome-screensaver crashes on remote login
Public bug reported: Simply log in remotely (ThinLinc, VNC, etc.) and you get a dialog stating that gnome-screensaver has crashed. One such report is available here: https://errors.ubuntu.com/user/4d1bab2c9cd5a9cb11c04501a4a6a28eb367d6dbe38fc21aa0baa5d470d950ff46f96949884a5795a806dd62ffabb4005d068082c4001c9296f95327d2621d0c Only seems to happen on the initial login for a user. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1631364 Title: gnome-screensaver crashes on remote login Status in gnome-screensaver package in Ubuntu: New Bug description: Simply log in remotely (ThinLinc, VNC, etc.) and you get a dialog stating that gnome-screensaver has crashed. One such report is available here: https://errors.ubuntu.com/user/4d1bab2c9cd5a9cb11c04501a4a6a28eb367d6dbe38fc21aa0baa5d470d950ff46f96949884a5795a806dd62ffabb4005d068082c4001c9296f95327d2621d0c Only seems to happen on the initial login for a user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1631364/+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 1631508] Re: Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot
** Description changed: Test Case here: - Seen on both 660m & 770m laptops, both with ssd's + Seen on both 660m & 775m laptops, both with ssd's Fresh install of 16.04.1 Fully updated Install the nvidia-361 package Reboot What happens: boots to Intel drivers Open nvidia settings > prime profiles > pick nvidia log out/in What happens: log in uses Nvidia drivers Reboot What happens: boots to Intel Attaching gpu-manager.log which reflects immediately above scenario ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:35:17 2016 InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1631508 Title: Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Test Case here: Seen on both 660m & 775m laptops, both with ssd's Fresh install of 16.04.1 Fully updated Install the nvidia-361 package Reboot What happens: boots to Intel drivers Open nvidia settings > prime profiles > pick nvidia log out/in What happens: log in uses Nvidia drivers Reboot What happens: boots to Intel Attaching gpu-manager.log which reflects immediately above scenario ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:35:17 2016 InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1631508/+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 1631519] Re: No X on boot with external monitor connected
** Summary changed: - xorg hall-of-mirrors on external display + No X on boot with external monitor connected ** Description changed: - Running from today's (201610907) daily yakkety livecd I can boot to the - desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). - Attaching a 1920x1080 LCD via miniDP extends the desktop but windows - moved around produce a trail of windows that persist even after the - window is closed. + When booting from today's (201610907) daily yakkety livecd with an + external display attached X does not start. - Also, when booting from the livecd with the external display attached X - does not start. + If the external monitor is attached after X has started I can boot to + the desktop using only using the laptop's LCD (ThinkPad x230, intel + graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop + but windows moved around produce a trail of windows that persist even + after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: - Installed: 1:7.7+13ubuntu4 - Candidate: 1:7.7+13ubuntu4 - Version table: - *** 1:7.7+13ubuntu4 500 - 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:7.7+13ubuntu4 + Candidate: 1:7.7+13ubuntu4 + Version table: + *** 1:7.7+13ubuntu4 500 + 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Changed in: xorg (Ubuntu) Importance: Undecided => Critical -- 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/1631519 Title: No X on boot
[Desktop-packages] [Bug 1631519] Re: No X on boot with external monitor connected
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1631519 ** Tags added: iso-testing -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631528] [NEW] Blank screen after grub menu
Public bug reported: After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some problems booting. After the grub menu the screen goes blank and nothing happens after that. I think the system is booting properly apart from the screen not showing anything, I can change the volume using the hardware keys and I can connect with SSH from another machine. I've found two workarounds for this problem. 1) Select recovery mode from the grub meny and then resume normal boot, however, the screen resolution is not set properly. 2) Change my grub config file to boot into text mode. I commented out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and changed GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX=”text" and uncommented the line #GRUB_TERMINAL=console After running sudo update-grub and rebooting the system boots into MATE and the correct screen resolution is set. I've collected dmesg after a "blank screen" boot, let me know if there is anything else I should provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Oct 7 22:41:04 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze xenial ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1631528/+attachment/4757005/+files/dmesg.txt -- 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/1631528 Title: Blank screen after grub menu Status in xorg package in Ubuntu: New Bug description: After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some problems booting. After the grub menu the screen goes blank and nothing happens after that. I think the system is booting properly apart from the screen not showing anything, I can change the volume using the hardware keys and I can connect with SSH from another machine. I've found two workarounds for this problem. 1) Select recovery mode from the grub meny and then resume normal boot, however, the screen resolution is not set properly. 2) Change my grub config file to boot into text mode. I commented out the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" and changed GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX=”text" and uncommented the line #GRUB_TERMINAL=console After running sudo update-grub and rebooting the system boots into MATE and the correct screen resolution is set. I've collected dmesg after a "blank screen" boot, let me know if there is anything else I should provide. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Oct 7 22:41:04 2016 InstallationDate: Installed on 2016-10-06 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631528/+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 1631519] Re: No X on boot with external monitor connected
The attached gif tries to show the effect of moving a window across the screen. Not captured in the low-framerate gif is that the trails of the window are flickering and moving (compiz cpu usage is high when this happens). Hitting WIN+w to display windows and then drop back to the desktop clears the current trail. But that is not a reasonable workaround and does not address the basic issue that the livecd (or a fully installed desktop) does not boot to X with an external monitor attached. -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631519] Re: No X on boot with external monitor connected
A monitor attached to the Thinkpad x230 via the docking station DVI port is fine (boots to X and no crazy window trails). This is seen when attaching a monitor via DP on the dock or mDP from the laptop. I was using an mDP to HDMI cable or a DP to DualLink-DVI adapter to connect monitors when I found this issue. Multiple monitors were tried and all experienced the issue when connect to the monitor's HDMI port from the laptop's mDP port. -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: When booting from today's (201610907) daily yakkety livecd with an external display attached X does not start. If the external monitor is attached after X has started I can boot to the desktop using only using the laptop's LCD (ThinkPad x230, intel graphics). The attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+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 1631429] [NEW] GNOME Wayland session does not start
Public bug reported: GNOME Wayland session no longer starts. I am not sure, but I believe this is a regression from when Unity 8 / Mir was pushed 2-3 days ago. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:15:46 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1631429 Title: GNOME Wayland session does not start Status in gnome-session package in Ubuntu: New Bug description: GNOME Wayland session no longer starts. I am not sure, but I believe this is a regression from when Unity 8 / Mir was pushed 2-3 days ago. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session-wayland 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:15:46 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1631429/+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 729831] Re: Output controls are not switched to headset
The same thing happens with USB headsets, so, it seems related to having multiple output devices dynamically connected. -- 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/729831 Title: Output controls are not switched to headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After my bluetooth headset is connected to the system, the sound output is switched from the speakers to the headset, but the volume control does not set the volume of the headset. I have to go to "Sound Preferences... -> Output", then choose my headset here. Then I can control the volume. Also, after selecting a new output device, the "Output volume" slider changes its position, but the volume remains the same. I have to either click on the slider or use the volume keys on the keyboard to actually set the volume. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xvro 2336 F pulseaudio /dev/snd/pcmC1D0c: xvro 2336 F...m pulseaudio /dev/snd/controlC0: xvro 2336 F pulseaudio /dev/snd/pcmC0D0p: xvro 2336 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 5 21:36:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 04/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4B dmi.board.name: EX38-DQ6 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX38-DQ6 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 1611955] Re: Install icon overlaps Examples icon in "Try Ubuntu" desktop
Phew, that was a hard one. I think I got it though, with thanks to csoriano @ upstream. Uploaded - this should be on the ISO imho, since it mostly affects the live session. ** Bug watch added: GNOME Bug Tracker #765601 https://bugzilla.gnome.org/show_bug.cgi?id=765601 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=765601 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Changed in: nautilus (Ubuntu Yakkety) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1611955 Title: Install icon overlaps Examples icon in "Try Ubuntu" desktop Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Yakkety: Fix Committed Bug description: This is perhaps a duplicate of the very old bug 838714. I tried out today's Ubuntu live yakkety image in VirtualBox on yakkety. The Install Ubuntu 16.10 icon overlaps the Examples icon on the desktop. I am attaching a screenshot. This was also duplicated today by another user as seen in his screenshot at https://github.com/shimmerproject/Greybird/issues/127#issuecomment-238980774 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 10 16:10:13 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-09 (122 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1611955/+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 1631424] [NEW] GTK theme is not applied in Classic session
Public bug reported: The Adwaita GTK theme is not applied to the Classic session. Instead it forces the Ubuntu Ambiance theme. I can chose to use Adwaita in GNOME Tweak Tool and it works in GNOME but not in GNOME Classic session. This is a regression, it worked fine 2-3 days ago. Then the Unity 8 / Mir thing was pushed out, and that's when it broke. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:10:06 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1631424 Title: GTK theme is not applied in Classic session Status in gnome-session package in Ubuntu: New Bug description: The Adwaita GTK theme is not applied to the Classic session. Instead it forces the Ubuntu Ambiance theme. I can chose to use Adwaita in GNOME Tweak Tool and it works in GNOME but not in GNOME Classic session. This is a regression, it worked fine 2-3 days ago. Then the Unity 8 / Mir thing was pushed out, and that's when it broke. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:10:06 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1631424/+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 1631398] [NEW] package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.co
Public bug reported: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631398 Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 729831] Re: Output controls are not switched to headset
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/729831 Title: Output controls are not switched to headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio After my bluetooth headset is connected to the system, the sound output is switched from the speakers to the headset, but the volume control does not set the volume of the headset. I have to go to "Sound Preferences... -> Output", then choose my headset here. Then I can control the volume. Also, after selecting a new output device, the "Output volume" slider changes its position, but the volume remains the same. I have to either click on the slider or use the volume keys on the keyboard to actually set the volume. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 ProcVersionSignature: Ubuntu 2.6.35-27.48-generic 2.6.35.11 Uname: Linux 2.6.35-27-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xvro 2336 F pulseaudio /dev/snd/pcmC1D0c: xvro 2336 F...m pulseaudio /dev/snd/controlC0: xvro 2336 F pulseaudio /dev/snd/pcmC0D0p: xvro 2336 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xea40 irq 49' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a002,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'SAA7134'/'saa7133[0] at 0xea315000 irq 19' Mixer name : 'SAA7134 Mixer' Components : '' Controls : 6 Simple ctrls : 3 Date: Sat Mar 5 21:36:59 2011 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: pulseaudio dmi.bios.date: 04/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4B dmi.board.name: EX38-DQ6 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4B:bd04/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEX38-DQ6:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX38-DQ6:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX38-DQ6 dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.pulse.default.pa: 2010-12-19T18:10:08.489783 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/729831/+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 423534] Re: Select sound output from gnome-volume-control-applet menu
This could help when using USB headsets. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/423534 Title: Select sound output from gnome-volume-control-applet menu Status in GNOME media utilities: New Status in gnome-media package in Ubuntu: Triaged Bug description: Binary package hint: gnome-media This is not a bug. Set it please to wishlist. I've made some changes in gnome-media package for ease of switching the sound output in cases where you have more than one sound output. Now there is sub-menu in the gnome-volume-control-applet menu where you can choose the current sound output. This is very useful if you have a bluetooth headset. Menu will show up only when there is more than one audio output devices. I've contacted gnome-media maintainer Marc-André Lureau. He recommended me to register it as a bug on bugzilla.gnome.org, which i did. Bug:#593752 http://bugzilla.gnome.org/show_bug.cgi?id=593752 Also he said that this will not be in the 2.28 because it is in UI/string freeze. Maybe it is possible to get it into Ubuntu karmic? Attached patch file with changes made. Just get gnome-media source package, drop patch into package's debian/pathces directory and build it. Here you can see how it looks in action: http://dl.getdropbox.com/u/225762/select-sink-submenu-screenshot.png Here you can take a ready-compiled packages for karmic: http://dl.getdropbox.com/u/225762/gnome-media/gnome-media_2.27.90-0ubuntu1%7Eviks1_i386.deb http://dl.getdropbox.com/u/225762/gnome-media/gnome-media-common_2.27.90-0ubuntu1%7Eviks1_all.deb http://dl.getdropbox.com/u/225762/gnome-media/libgnome-media0_2.27.90-0ubuntu1%7Eviks1_i386.deb To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-media/+bug/423534/+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 1583538] Re: [desktop] Error creating OpenGL context using Java
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags added: xmir -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1583538 Title: [desktop] Error creating OpenGL context using Java Status in Libertine: Triaged Status in xorg-server package in Ubuntu: New Bug description: User reports error when attempting to start applications that use OpenGL when using the desktop personality. See traceback below. Time: 2016-05-18 21:26 Description: Initializing game java.lang.ExceptionInInitializerError at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) Caused by: java.lang.NullPointerException at org.lwjgl.opengl.LinuxDisplay.getAvailableDisplayModes(LinuxDisplay.java:947) at org.lwjgl.opengl.LinuxDisplay.init(LinuxDisplay.java:738) at org.lwjgl.opengl.Display.(Display.java:138) ... 4 more A detailed walkthrough of the error, its code path and all known details is as follows: --- -- Head -- Stacktrace: at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) -- Initialization -- Details: Stacktrace: at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) -- System Details -- Details: Minecraft Version: 1.9.2 Operating System: Linux (amd64) version 4.4.0-22-generic Java Version: 1.8.0_91, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 144126120 bytes (137 MB) / 252248064 bytes (240 MB) up to 3194421248 bytes (3046 MB) JVM Flags: 5 total; -Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn256M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 1.9.2 LWJGL: 2.9.4 OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. GL Caps: Using VBOs: No Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1583538/+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 1583538] Re: [desktop] Error creating OpenGL context using Java
Looks to me like Java is querying display modes and doesn't receive anything back. Jave doesn't handle this gracefully and crashes. Xmir should probably at least return something meaningful back when being queried for display modes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1583538 Title: [desktop] Error creating OpenGL context using Java Status in Libertine: Triaged Status in xorg-server package in Ubuntu: New Bug description: User reports error when attempting to start applications that use OpenGL when using the desktop personality. See traceback below. Time: 2016-05-18 21:26 Description: Initializing game java.lang.ExceptionInInitializerError at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) Caused by: java.lang.NullPointerException at org.lwjgl.opengl.LinuxDisplay.getAvailableDisplayModes(LinuxDisplay.java:947) at org.lwjgl.opengl.LinuxDisplay.init(LinuxDisplay.java:738) at org.lwjgl.opengl.Display.(Display.java:138) ... 4 more A detailed walkthrough of the error, its code path and all known details is as follows: --- -- Head -- Stacktrace: at bcc.ar(SourceFile:620) at bcc.an(SourceFile:428) -- Initialization -- Details: Stacktrace: at bcc.a(SourceFile:377) at net.minecraft.client.main.Main.main(SourceFile:124) -- System Details -- Details: Minecraft Version: 1.9.2 Operating System: Linux (amd64) version 4.4.0-22-generic Java Version: 1.8.0_91, Oracle Corporation Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 144126120 bytes (137 MB) / 252248064 bytes (240 MB) up to 3194421248 bytes (3046 MB) JVM Flags: 5 total; -Xmx3G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn256M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 1.9.2 LWJGL: 2.9.4 OpenGL: ~~ERROR~~ RuntimeException: No OpenGL context found in the current thread. GL Caps: Using VBOs: No Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: Current Language: ~~ERROR~~ NullPointerException: null Profiler Position: N/A (disabled) CPU: To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1583538/+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 1620517] Re: toolbox.py crashed with TypeError in /usr/bin/hp-toolbox: 'NoneType' object is not iterable
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1620517 Title: toolbox.py crashed with TypeError in /usr/bin/hp-toolbox: 'NoneType' object is not iterable Status in hplip package in Ubuntu: Confirmed Bug description: hplip does not operate in my H/Y, i have recently upgraded to ubuntu 16.10, from 16.04 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: hplip-data 3.16.7+repack0-1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Tue Sep 6 12:05:35 2016 Dependencies: gcc-6-base 6.2.0-3ubuntu11 libc6 2.24-0ubuntu1 libgcc1 1:6.2.0-3ubuntu11 liblzma5 5.1.1alpha+20120614-2.1ubuntu1 xz-utils 5.1.1alpha+20120614-2.1ubuntu1 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2016-07-12 (55 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 Lpstat: device for HP-Deskjet-4610-series: usb://HP/Deskjet%204610%20series?serial=CN2AJ241ZN05TK=1 device for HP-Deskjet-4610-series-FAX: usb://HP/Deskjet%204610%20series%20FAX?serial=CN2AJ241ZN05TK=2 device for Samsung-ML-2165: smb://WORKGROUP/CHRISTINE/Samsung-ML-2160-Series MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Deskjet-4610-series.ppd', '/etc/cups/ppd/HP-Deskjet-4610-series-FAX.ppd', '/etc/cups/ppd/Samsung-ML-2165.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Deskjet-4610-series.ppd: Permission denied grep: /etc/cups/ppd/HP-Deskjet-4610-series-FAX.ppd: Permission denied grep: /etc/cups/ppd/Samsung-ML-2165.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic.efi.signed root=UUID=4582dd83-d575-420a-8455-f4ab15e11d56 ro quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/hp-toolbox'] SourcePackage: hplip Title: toolbox.py crashed with TypeError in /usr/bin/hp-toolbox: 'NoneType' object is not iterable Traceback: Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 269, in QApplication, ui_package = utils.import_dialog(ui_toolkit) TypeError: 'NoneType' object is not iterable UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A75M-D3H 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.:bvrF5:bd03/12/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1620517/+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 1612367] Re: [Touch] Incoming call gets silent randomly
@anupam thats an interesting theory, I got a log of when the power button is pressed and it goes from paused to stopped almost instantly, whereas your logs generally show a delay and stopped is only issued once the call is answered. @jim I still thinks its a thread issue in media hub, I can't get by the fact that its logging engine playing uri multiple times on each incoming call and logging paused multiple times. Perhaps thats benign but unclear to me why the same code is executed more than once "sometimes". -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 1631424] Re: GTK theme is not applied in Classic session
** Description changed: The Adwaita GTK theme is not applied to the Classic session. Instead it forces the Ubuntu Ambiance theme. I can chose to use Adwaita in GNOME Tweak Tool and it works in GNOME but not in GNOME Classic session. - This is a regression, it worked fine 2-3 days ago. + This is a regression, it worked fine 2-3 days ago. Then the Unity 8 / + Mir thing was pushed out, and that's when it broke. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:10:06 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1631424 Title: GTK theme is not applied in Classic session Status in gnome-session package in Ubuntu: New Bug description: The Adwaita GTK theme is not applied to the Classic session. Instead it forces the Ubuntu Ambiance theme. I can chose to use Adwaita in GNOME Tweak Tool and it works in GNOME but not in GNOME Classic session. This is a regression, it worked fine 2-3 days ago. Then the Unity 8 / Mir thing was pushed out, and that's when it broke. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-session 3.20.2-1ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Classic:GNOME Date: Fri Oct 7 18:10:06 2016 InstallationDate: Installed on 2013-12-26 (1015 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1631424/+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 1631431] Re: HPlib not working (from repo)- non hplib (3.16.7 and above) able to install
*** This bug is a duplicate of bug 1620517 *** https://bugs.launchpad.net/bugs/1620517 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1620517, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** Changed in: hplip (Ubuntu) Importance: Undecided => Medium ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1631431/+attachment/4756862/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1631431/+attachment/4756864/+files/ProcStatus.txt ** This bug has been marked a duplicate of bug 1620517 toolbox.py crashed with TypeError in /usr/bin/hp-toolbox: 'NoneType' object is not iterable ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1631431 Title: HPlib not working (from repo)- non hplib (3.16.7 and above) able to install Status in hplip package in Ubuntu: New Bug description: Since approx two weeks you are not able anymore to use HPlib from repo or from online installation (hplib 3.16.7 and above tried). During installation from hp the install rutine fails (qt gui). The repo version see this report. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: hplip-data 3.16.7+repack0-1ubuntu1 Uname: Linux 4.8.0-040800-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Fri Oct 7 18:19:15 2016 Dependencies: gcc-6-base 6.2.0-5ubuntu12 libc6 2.24-3ubuntu1 libgcc1 1:6.2.0-5ubuntu12 liblzma5 5.1.1alpha+20120614-2.1ubuntu1 xz-utils 5.1.1alpha+20120614-2.1ubuntu1 ExecutablePath: /usr/share/hplip/toolbox.py InstallationDate: Installed on 2016-10-04 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161004) InterpreterPath: /usr/bin/python3.5 Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: Gigabyte Technology Co., Ltd. Default string PackageArchitecture: all Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Officejet-Pro-8610.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Officejet-Pro-8610.ppd: Permission denied ProcCmdline: /usr/bin/python3 /usr/bin/hp-toolbox ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-040800-generic root=UUID=c1ba50e2-7666-4084-a69d-8a862d572883 ro rootflags=subvol=@ quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/hp-toolbox'] SourcePackage: hplip Title: toolbox.py crashed with TypeError in /usr/bin/hp-toolbox: 'NoneType' object is not iterable Traceback: Traceback (most recent call last): File "/usr/bin/hp-toolbox", line 269, in QApplication, ui_package = utils.import_dialog(ui_toolkit) TypeError: 'NoneType' object is not iterable UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6a dmi.board.asset.tag: Default string dmi.board.name: X99-Ultra Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6a:bd08/31/2016:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99-UltraGaming-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1631431/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
Also if I wait a bit (let's say 30 seconds), everything is fine. This 'workaround' is similar to #26 -- 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/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1506704/+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 1627964] Re: fwupd assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x000055f0c0f9f141 ***
** Changed in: fwupd (Ubuntu) Status: New => Incomplete ** Changed in: appstream-glib (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1627964 Title: fwupd assert failure: *** Error in `/usr/lib/x86_64-linux- gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 *** Status in appstream-glib package in Ubuntu: Incomplete Status in fwupd package in Ubuntu: Incomplete Bug description: When I booted it gave the error. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: fwupd 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AssertionMessage: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 *** Date: Sun Sep 25 20:26:14 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/fwupd/fwupd InstallationDate: Installed on 2016-08-24 (33 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/fwupd/fwupd ProcEnviron: Signal: 6 SourcePackage: fwupd StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f1bd7f01358 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ar_ptr=, ptr=, str=0x7f1bd7efdeef "free(): invalid pointer", action=3) at malloc.c:5046 _int_free (av=, p=, have_lock=) at malloc.c:3902 __GI___libc_free (mem=) at malloc.c:2982 ?? () from /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 Title: fwupd assert failure: *** Error in `/usr/lib/x86_64-linux-gnu/fwupd/fwupd': free(): invalid pointer: 0x55f0c0f9f141 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1627964/+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
Re: [Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
See attached. --Dick Miller, Partner, MMS> On 10/07/2016 04:02 AM, bagl0312 wrote: > I found a workaround to invert the two finger scrolling behavior. > It is enough to add a file .Xmodmap in the home dir with the following > content: > > $ cat .Xmodmap > pointer = 2 3 5 4 6 7 8 9 10 > > (note that the forth and fifth numbers are swapped) > > This invert the two finger scrolling direction, but unfortunately also > the direction of scrolling of the wheel of an external mouse, if used... > > Anyway, for those using only the touchpad I think it is a good, > temporary compromise :) > -- You received this bug notification because you are subscribed to > xserver-xorg-input-synaptics in Ubuntu. Matching subscriptions: A. > Richard Miller https://bugs.launchpad.net/bugs/1590590 Title: Touchpad > not recognized on Dell Latitude E7470 Ultrabook Status in linux > package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics > package in Ubuntu: Confirmed Bug description: Expected: Touchpad > settings available in Mouse & Touchpad Settings dialog Actual result: > Touchpad settings missing entirely Details: The touchpad on my Dell > Ultrabook (Latitude E7470) functions mostly. The settings for the > touchpad are not available at all in the Mouse and Touchpad settings > (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as > expected except it's using "Natural Scrolling" by default and there is > no way to change it. xinput list does not display a touchpad at all: ⎡ > Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST > pointer id=4 [slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11 [slave > pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core > XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave > keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button > id=8 [slave keyboard (3)] ↳ Sleep Button id=9 [slave keyboard (3)] ↳ > Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 > keyboard id=12 [slave keyboard (3)] ↳ Dell WMI hotkeys id=14 [slave > keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] > /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" > Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: > 16.04 xserver-xorg-input-synaptics version information: > xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: > 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 > http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 > /var/lib/dpkg/status To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists
[Desktop-packages] [Bug 1593586] Re: Issue with two external screens
This problem is solved for me after applying the latest updates. -- 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/1593586 Title: Issue with two external screens Status in xorg package in Ubuntu: New Bug description: When I boot my Laptop (Dell latitude 7470 + Dell E-Port Plus II docking station) with two external Dell screens attached (via Display port, each separate connected) at the beginning of my session everything works fine. The lid is closed while booting. After starting Firefox the focus of the mouse is some how lost. Then it is not possible to open the context menu of Firefox. Typed letters appear on the other screen. The focus is also lost when I remove the Laptop from the dockingstation and attach it back to the docking station. The focus works fine when only the built-in display is used. WORKAROUND: Boot the laptop at the beginning with only one attached screen (cable disconnected). After login attach the second screen, open the "Displays" configuration menu, and click on something without changing the configuration. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 17 08:16:07 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06dc] InstallationDate: Installed on 2016-06-10 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.3:bd04/18/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.2 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jun 17 08:04:44 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1168 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1593586/+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 1631398] Re: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1631398 Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 Status in account-plugins package in Ubuntu: New Bug description: hi my frends ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-google 0.13+16.10.20160831-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Fri Oct 7 07:55:35 2016 DuplicateSignature: package:account-plugin-google:0.13+16.10.20160831-0ubuntu1 Unpacking account-plugin-google (0.13+16.10.20160929.1-0ubuntu1) over (0.13+16.10.20160831-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-V6mfaf/03-account-plugin-google_0.13+16.10.20160929.1-0ubuntu1_all.deb (--unpack): trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 InstallationDate: Installed on 2016-02-11 (239 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-google 0.13+16.10.20160831-0ubuntu1 failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package kaccounts-providers 4:16.04.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.signon-ui.webkit-options.d.accounts.google.com.conf: 2016-07-02T19:13:58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1631398/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
I'm afraid this didn't work for me. I installed network-manager 1.2.2-0ubuntu0.16.04.3 from xenial-proposed, ran 'systemctl restart NetworkManager' as root and reconnected to the VPN and I see the same behaviour (i.e. I get DNS resolution failure for non-VPN domains). I am on wifi only and both v4 and v6 are set to route all outbound traffic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1612367] Re: [Touch] Incoming call gets silent randomly
Excuse this naive comment, but if I'm not mistaken, while the phone rings on an incoming call, pressing the power button pauses the ringtone. Is it possible that the same/similar action is simulated here even when the user is not pressing the power button? -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+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 814826] Re: bamfdaemon crashed with SIGSEGV in gdk_display_get_event()
By the way my ubuntu version is: Ubuntu 16.10 yakkety-yak -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/814826 Title: bamfdaemon crashed with SIGSEGV in gdk_display_get_event() Status in BAMF: Expired Status in Unity: Expired Status in unity-2d: Expired Status in bamf package in Ubuntu: Expired Bug description: Resuming from suspend (opening laptop lid), this happened. I did not get prompted to enter my password per usual. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: bamfdaemon 0.2.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-6.7-generic-pae 3.0.0-rc7 Uname: Linux 3.0.0-6-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jul 23 06:56:03 2011 ExecutablePath: /usr/lib/bamf/bamfdaemon InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: /usr/lib/bamf/bamfdaemon ProcEnviron: SHELL=/bin/bash LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0xb712cc71:mov0x8(%esi),%ebp PC (0xb712cc71) ok source "0x8(%esi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%ebp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bamf StacktraceTop: ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 gdk_display_get_event () from /usr/lib/libgdk-3.so.0 Title: bamfdaemon crashed with SIGSEGV in gdk_display_get_event() UpgradeStatus: Upgraded to oneiric on 2011-06-14 (37 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/814826/+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 814826] Re: bamfdaemon crashed with SIGSEGV in gdk_display_get_event()
and my processor is 64-bit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/814826 Title: bamfdaemon crashed with SIGSEGV in gdk_display_get_event() Status in BAMF: Expired Status in Unity: Expired Status in unity-2d: Expired Status in bamf package in Ubuntu: Expired Bug description: Resuming from suspend (opening laptop lid), this happened. I did not get prompted to enter my password per usual. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: bamfdaemon 0.2.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-6.7-generic-pae 3.0.0-rc7 Uname: Linux 3.0.0-6-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Jul 23 06:56:03 2011 ExecutablePath: /usr/lib/bamf/bamfdaemon InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: /usr/lib/bamf/bamfdaemon ProcEnviron: SHELL=/bin/bash LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0xb712cc71:mov0x8(%esi),%ebp PC (0xb712cc71) ok source "0x8(%esi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%ebp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bamf StacktraceTop: ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 ?? () from /usr/lib/libgdk-3.so.0 gdk_display_get_event () from /usr/lib/libgdk-3.so.0 Title: bamfdaemon crashed with SIGSEGV in gdk_display_get_event() UpgradeStatus: Upgraded to oneiric on 2011-06-14 (37 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/814826/+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 1615575] Re: Emoji support
In defense of Launchpad, haha: It may not be as pretty, but is tightly integrated with Ubuntu, open source, and run by Canonical. I've always expected support for CBLC/CBDT color format fonts in Linux before SVGinOT. It's quicker to implement since it just uses bitmaps, no SVG renderer needed. SVGinOT is the long term choice due to file size, for example a CBLC/CBDT of EmojiOne will be 20MB+. An option for now is to add emoji support using the existing font rendering system. Both of my fonts provide regular fallback non-color glyphs. They are machine generated, but acceptable IMO. Feature requests could to be filed for support of SVGinOT and CBLC/CBDT in the stack below Onboard. Greatly extends the timeline, but avoids a custom font render system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1615575 Title: Emoji support Status in Onboard: Confirmed Status in onboard package in Ubuntu: Confirmed Bug description: Any plans for emoji support? These days it's commonly used in communication. If onboard had emoji support it would be a very useful tool. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1615575/+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 1631475] [NEW] Google Chrome crashed, nouveau 0000:01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201
Public bug reported: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1239182 ? versions: Ubuntu 16.01.01 Kernel 4.4.0-38-generic xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Description changed: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1239182 ? + + versions: + Ubuntu 16.01.01 + Kernel 4.4.0-38-generic + xserver-xorg-video-nouveau 1:1.0.12-1build2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1631475 Title: Google Chrome crashed, nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: My Chrome just crashed, and I found this line in dmesg: nouveau :01:00.0: fifo: CACHE_ERROR - ch 5 [chrome[3710]] subc 0 mthd 0060 data beef0201 Related to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg- video-nouveau/+bug/1239182 ? versions: Ubuntu 16.01.01 Kernel 4.4.0-38-generic xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1631475/+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 1631479] Re: Thunderbird 45.3 failed to be built for Yakkety
** Information type changed from Private Security to Public Security ** Changed in: thunderbird (Ubuntu) Status: New => Triaged ** Changed in: thunderbird (Ubuntu) Importance: Undecided => Critical ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Chris Coulson (chrisccoulson) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1631479 Title: Thunderbird 45.3 failed to be built for Yakkety Status in thunderbird package in Ubuntu: Triaged Bug description: Thunderbird is stuck at version 45.2 on Yakkety's proposed repository. Packages for all archs failed to build. It should be v. 45.3 as Xenial's packages. Additionally, there is a security notice : https://www.mozilla.org/en-US/security/advisories/mfsa2016-62/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1631479/+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 1629132] Re: Please merge network-manager-openvpn 1.2.6-2 from Debian (unstable) to Ubuntu (yakkety)
We are in final freeze, so unless this fixes a specific critical bug in yakkety we should punt this to SRU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1629132 Title: Please merge network-manager-openvpn 1.2.6-2 from Debian (unstable) to Ubuntu (yakkety) Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety), to match with the version of main network-manager package (1.2.4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1629132/+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 1631499] [NEW] package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1631499 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1631499] Re: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1631499 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: Installing new version of config file /etc/X11/Xsession.d/75dbus_dbus-launch ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libffi6 (>= 3.0.4); however: Package libffi6:i386 is not configured yet. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Fri Oct 7 15:22:06 2016 DuplicateSignature: package:libglib2.0-0:i386:2.48.1-1~ubuntu16.04.1:dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2014-09-03 (765 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.48.1-1~ubuntu16.04.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1631499/+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 1611955] Re: Install icon overlaps Examples icon in "Try Ubuntu" desktop
** Changed in: nautilus Status: Unknown => Fix Released ** Changed in: nautilus Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1611955 Title: Install icon overlaps Examples icon in "Try Ubuntu" desktop Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Committed Status in nautilus source package in Yakkety: Fix Committed Bug description: This is perhaps a duplicate of the very old bug 838714. I tried out today's Ubuntu live yakkety image in VirtualBox on yakkety. The Install Ubuntu 16.10 icon overlaps the Examples icon on the desktop. I am attaching a screenshot. This was also duplicated today by another user as seen in his screenshot at https://github.com/shimmerproject/Greybird/issues/127#issuecomment-238980774 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Aug 10 16:10:13 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-09 (122 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1611955/+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 1544477] Re: No sound notification for new SMS (Ubuntu Touch)
Sorry to say that guys, but... my phone (E4.5 under OTA13) doesn't give a sound any more. Do You want to see any logs before I reboot it? -- 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/1544477 Title: No sound notification for new SMS (Ubuntu Touch) Status in Canonical System Image: Fix Released Status in indicator-sound package in Ubuntu: Invalid Status in media-hub package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Status in qtmultimedia-opensource-src package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: I noticed for last 2-3 days there is no sound notification for a new SMS, but there's a blinking green LED notification. Also in the indicator menu the envelope icon turns green and the new SMS is listed as usual. Things are working alright for Telegram, Gmail etc. (sound+LED+indicator menu). Device: bq Aquaris E5 HD, Ubuntu 15.04 (OTA-9) UPDATE: Screenshots get silent too. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1544477/+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 1631508] [NEW] Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot
Public bug reported: Test Case here: Seen on both 660m & 770m laptops, both with ssd's Fresh install of 16.04.1 Fully updated Install the nvidia-361 package Reboot What happens: boots to Intel drivers Open nvidia settings > prime profiles > pick nvidia log out/in What happens: log in uses Nvidia drivers Reboot What happens: boots to Intel Attaching gpu-manager.log which reflects immediately above scenario ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:35:17 2016 InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/bugs/1631508/+attachment/4756977/+files/gpu-manager.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1631508 Title: Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Test Case here: Seen on both 660m & 770m laptops, both with ssd's Fresh install of 16.04.1 Fully updated Install the nvidia-361 package Reboot What happens: boots to Intel drivers Open nvidia settings > prime profiles > pick nvidia log out/in What happens: log in uses Nvidia drivers Reboot What happens: boots to Intel Attaching gpu-manager.log which reflects immediately above scenario ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:35:17 2016 InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1631508/+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 1631508] Re: Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot
This behavior does not occur if I downgrade to _0.4.17 i.e. downgrade, restart, switch to nvidia, log out/in, restart ** Tags added: regression -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1631508 Title: Enabiling nvidia drivers thru nvidia-prime doesn't survive a reboot Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Test Case here: Seen on both 660m & 770m laptops, both with ssd's Fresh install of 16.04.1 Fully updated Install the nvidia-361 package Reboot What happens: boots to Intel drivers Open nvidia settings > prime profiles > pick nvidia log out/in What happens: log in uses Nvidia drivers Reboot What happens: boots to Intel Attaching gpu-manager.log which reflects immediately above scenario ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 7 15:35:17 2016 InstallationDate: Installed on 2016-10-07 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1631508/+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 1364642] Re: package ubuntu-docs 12.04.6 failed to install/upgrade: symbolic link '/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has changed from 69 to 4
I will use as is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1364642 Title: package ubuntu-docs 12.04.6 failed to install/upgrade: symbolic link '/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has changed from 69 to 4 Status in dpkg package in Ubuntu: Confirmed Status in gnome-user-docs package in Ubuntu: Confirmed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: I cannot install all updates. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-docs 12.04.6 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 Date: Tue Sep 2 23:39:46 2014 DuplicateSignature: package:ubuntu-docs:12.04.6:symbolic link '/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has changed from 69 to 4 ErrorMessage: symbolic link '/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has changed from 69 to 4 InstallationDate: Installed on 2013-12-27 (248 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) PackageArchitecture: all SourcePackage: ubuntu-docs Title: package ubuntu-docs 12.04.6 failed to install/upgrade: symbolic link '/usr/share/help/ja/ubuntu-help/music-player-notrecognized.page' size has changed from 69 to 4 UpgradeStatus: Upgraded to trusty on 2014-08-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1364642/+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 1631549] Re: nautilus crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1628350 *** https://bugs.launchpad.net/bugs/1628350 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1628350, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1631549/+attachment/4757068/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757070/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757074/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757075/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757076/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757077/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1631549/+attachment/4757078/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1628350 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1631549 Title: nautilus crashed with SIGABRT in g_assertion_message() Status in nautilus package in Ubuntu: New Bug description: I can't open Nautilus..! ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Fri Oct 7 15:53:42 2016 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2016-10-05 (2 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161004) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1631549/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3
This bug was fixed in the package ubuntu-themes - 16.10+16.10.20161007-0ubuntu1 --- ubuntu-themes (16.10+16.10.20161007-0ubuntu1) yakkety; urgency=medium [ Martin Wimpress ] * Fix borders of Libreoffice toolbars, so that they don't overlap the window decorations (LP: #1624571) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Fri, 07 Oct 2016 16:30:52 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around LibreOffice toolbars in when using GTK3 Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen
Confirm! -- 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: New 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/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 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group
** Package changed: alsa-driver (Ubuntu) => procps (Ubuntu) -- 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/1610499 Title: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group Status in procps package in Ubuntu: Confirmed Bug description: when i run hadoop in ubuntu 16.04, ssh will exit, all process which belong to hadoop user will be killed ,through debug ,i found the /bin/kill in ubuntu16.04 has a bug , it has bug in killing process group . Ubuntu version is: Description:Ubuntu 16.04.1 LTS Release:16.04 (1)The way to repeat this bug It is easy to repeat this bug , run “/bin/kill -15 -12345” or any like “/bin/kill -15 -1” in ubuntu16.04 , it will kill all the process . (2)Cause analysis The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 , when I run “/bin/kill -15 -1” , it actually send signal 15 to -1 , -1 mean it will kill all the process . (3)The bug in procps-3.3.10/skill.c ,I think the code "pid = (long)('0' - optopt) " is not right . static void __attribute__ ((__noreturn__)) kill_main(int argc, char **argv) { case '?': if (!isdigit(optopt)) { xwarnx(_("invalid argument %c"), optopt); kill_usage(stderr); } else { /* Special case for signal digit negative * PIDs */ pid = (long)('0' - optopt); if (kill((pid_t)pid, signo) != 0) exitvalue = EXIT_FAILURE; exit(exitvalue); } loop=0; } (4) the cause sometimes when the resource is tight or a hadoop container lost connection in sometime, the nodemanager will kill this container , it send a signal to kill this jvm process ,it is a normal behavior for hadoop to kill a task and then reexecute this task. but with this kill bug ,it kill all the process belong to a hadoop user . (5) The way to workaround I copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is ok in this way . I also think it is better to ask procps-3.3.10 maintainer to solve their bug,but i don't know how to contact them . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1610499/+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 1631335] Re: sharing : gnome-settings-daemon crashed with SIGSEGV in g_hash_table_unref
*** This bug is a duplicate of bug 1630853 *** https://bugs.launchpad.net/bugs/1630853 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1630853, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1631335/+attachment/4756639/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756641/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756644/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756645/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756646/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756647/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1631335/+attachment/4756648/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1630853 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1631335 Title: sharing : gnome-settings-daemon crashed with SIGSEGV in g_hash_table_unref Status in gnome-settings-daemon package in Ubuntu: New Bug description: GSD crashes after login (Unity). No further information. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-settings-daemon 3.22.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Fri Oct 7 13:26:31 2016 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2016-04-12 (177 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon SegvAnalysis: Segfault happened at: 0x7fe9f85c7a84:mov0x18(%r12),%rax PC (0x7fe9f85c7a84) ok source "0x18(%r12)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libsharing.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libsharing.so ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/gnome-settings-daemon-3.0/libsharing.so Title: [sharing]: gnome-settings-daemon crashed with SIGSEGV in g_hash_table_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1631335/+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 1623666] Re: iOS10 will not connect to Ubuntu
** Changed in: libimobiledevice (Ubuntu) Assignee: (unassigned) => per (eura) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS10 will not connect to Ubuntu
@Per when you fix this will it be backported to Ubuntu 16.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1615575] Re: Emoji support
Because most open source projects these days use GitHub. A lot of users have a GitHub account, so it's easy for them to report issues on a GitHub issue tracker for various projects with a single account. GitHub also is better designed and more familiar than Launchpad IMHO. What's also nice is the mentioning feature ( https://github.com/blog/821 -mention-somebody-they-re-notified ). And pull requests also seem to be easier on GitHub? Oh and..., for the killer feature: GitHub supports Emojis: https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and- comments ;D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1615575 Title: Emoji support Status in Onboard: Confirmed Status in onboard package in Ubuntu: Confirmed Bug description: Any plans for emoji support? These days it's commonly used in communication. If onboard had emoji support it would be a very useful tool. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1615575/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Indeed, if a workaround to invert the "natural scrolling" behavior will be found we could survive until a real support is enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1631288] [NEW] XV video screen always on top
Public bug reported: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Skylake Integrated Graphics [1179:001d] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d] InstallationDate: Installed on 2016-10-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: TOSHIBA TECRA Z50-C PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.70 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z50-C dmi.product.version: PT577E-01100GCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 17:44:07 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1237 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- 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/1631288 Title: XV video screen always on top Status in xorg package in Ubuntu: New Bug description: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics
[Desktop-packages] [Bug 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop
Lubuntu version is 16.04.1 (with latest stable updates) LightDM version 1.18.20ubuntu2. lightdm-gtk-greeter is 2.0.1-2ubuntu4. I'll check out the permissions later and get back to you. -- 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/1628790 Title: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop Status in lightdm package in Ubuntu: Incomplete Bug description: After setting my account to login automatically through the user and groups setting in Lubuntu. After the computer reboots it gets stuck in a loop on the login screen. Logging in will just send you back to the same screen. The only way I could fix the issue was to press CRTL + ALT + F1, logging in through the CLI and typing: "sudo mv .Xauthority .Xauthority.bak" and then once I was back to the login screen I was able to login and turn the setting off. I did check to see weather that was what caused it, by restarting the computer without turning off the auto-login. However the same issue happened and only turning off auto-login would stop the login loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1628790/+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 1506166] Re: Bracketed paste should be per-terminal [PATCH]
(subscribed sponsors to take care of #14 and #15 - thanks, Alexander) Egmont, if you're still reading this, I'm happy to help with uploading backports of fixes to vte in older releases if you're willing to help identify the commits. I get a lot of bug mail and there's a good chance I'd miss it if you post it here or on another bug - so if you do take this up then please either subscribe me to the bug or email me (address in LP profile). Cheers. ** Also affects: vte (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: vte3 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: vte3 (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1506166 Title: Bracketed paste should be per-terminal [PATCH] Status in Gnome Virtual Terminal Emulator: Fix Released Status in vte package in Ubuntu: New Status in vte3 package in Ubuntu: Fix Released Status in vte source package in Trusty: New Status in vte3 source package in Trusty: Fix Released Status in vte source package in Xenial: New Status in vte3 source package in Xenial: Fix Released Bug description: [Impact] Bracketed paste mode (\e[?2004h) should be per-terminal (as it is for xterm), not per-screen. This was fixed upstream for vte3 0.36.2, however Trusty ships vte3 0.34.2 and it didn't make it: https://bugzilla.gnome.org/show_bug.cgi?id=729533 This bug is causing annoying garbage appended to every paste in mc: https://www.midnight-commander.org/ticket/3207 I have backported the fix to Trusty, tested it in my PPA and would appreciate if someone could sponsor an upload in updates, since Trusty is LTS after all. [Test Case] Select some text ("test") and copy it into the clipboard buffer. After that, install mc if you don't have it already and start it: sudo apt-get install mc mc Press CTRL+O to swap the panels, right click with the mouse button and pick "Paste" from the context menu. You will see that "~0test~1" is pasted into the console instead of "test" as it should be. For more details, see the bug report on mc bug tracker referenced above. [Regression Potential] The patch is taken from the vte3 bug tracker; it has been in trunk for more than a year and is contained in vte3 0.36.2+ releases. Nobody has reported any problems caused by this change so far... To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1506166/+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 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622005/comments/9 -- 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/1623173 Title: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work Status in xorg package in Ubuntu: New Bug description: On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7, 4.7.3 nor 4.8-rc6. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.8.0-040800rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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 Sep 13 21:49:46 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2016-06-01 (104 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW 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.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 13 21:14:29 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623173/+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 1631288] Re: XV video screen always on top
** Tags added: bios-outdated-7.40 -- 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/1631288 Title: XV video screen always on top Status in xorg package in Ubuntu: New Bug description: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Skylake Integrated Graphics [1179:001d] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d] InstallationDate: Installed on 2016-10-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: TOSHIBA TECRA Z50-C PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.70 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z50-C dmi.product.version: PT577E-01100GCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 17:44:07 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1237 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1623666] Re: iOS10 will not connect to Ubuntu
Sorry for the miss-understanding I slip on the keyboard last night it was dark when I change the status Changed in libimobiledevice (Ubuntu): status: Confirmed → Fix Committed status: Fix Committed → Confirmed Ignore this Sorry / Per -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3
** Summary changed: - White lines visible around toolbars in LibreOffice when using GTK3 and a dark theme + White lines visible around LibreOffice toolbars in when using GTK3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around LibreOffice toolbars in when using GTK3 Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: In Progress Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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 1625877] Re: VLC screen always on top
Here is the new bug created with ubuntu-bug xorg Hope it will help. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288 -- 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/1625877 Title: VLC screen always on top Status in xorg package in Ubuntu: Invalid Bug description: After new installed VLC on 16.04 The video screen always on top only while playing with VLC the interface disappeared while minimum VLC (video playing) video screen remains only but the situation is fixed after canceled the option "Accelerated video output(Overlay)" in Preference > Video > Display Reference: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1537053 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 21 09:23:57 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6588] InstallationDate: Installed on 2016-09-01 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5b0 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: COPELION INTERNATIONAL CO., LTD. SY Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5e244808-04fe-428e-993a-b6260daede38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: SY Series dmi.board.vendor: COPELION INTERNATIONAL CO., LTD. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd07/09/2016:svnCOPELIONINTERNATIONALCO.,LTD.:pnSYSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALCO.,LTD.:rnSYSeries:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: SY Series dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 20 22:21:24 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625877/+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 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
I found a workaround to invert the two finger scrolling behavior. It is enough to add a file .Xmodmap in the home dir with the following content: $ cat .Xmodmap pointer = 1 2 3 5 4 6 7 8 9 10 (note that the forth and fifth numbers are swapped) This invert the two finger scrolling direction, but unfortunately also the direction of scrolling of the wheel of an external mouse, if used... Anyway, for those using only the touchpad I think it is a good, temporary compromise :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1631346] [NEW] spurious colord authentication request for remote session
Public bug reported: Remote sessions get nagged with polkit authentication requests, despite no action from the user. This has already been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=751775 https://github.com/hughsie/colord/issues/16 https://bugs.kde.org/show_bug.cgi?id=357247 However it still needs to be fixed in current versions in Ubuntu, especially the latest LTS release. ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1631346 Title: spurious colord authentication request for remote session Status in colord package in Ubuntu: New Bug description: Remote sessions get nagged with polkit authentication requests, despite no action from the user. This has already been reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=751775 https://github.com/hughsie/colord/issues/16 https://bugs.kde.org/show_bug.cgi?id=357247 However it still needs to be fixed in current versions in Ubuntu, especially the latest LTS release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1631346/+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 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
SOLVE THIS PLEASE ! It really sucks. Makes inkscape USELESS for me ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Confirmed Status in inkscape package in Ubuntu: Confirmed Status in inkscape package in Debian: Confirmed Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+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 1631241] Re: Name resolution stops working after resume from suspend
OK. This could be because NM does not feed it with correct DNS data, or dnsmasq itself gets confused after resuming. Assigning to NetworkManager for now. ** Package changed: systemd (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend Status in network-manager package in Ubuntu: New Bug description: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
im-config 0.29-1ubuntu12.2 is uploaded to xenial-proposed and ensures the newer apparmor is installed. Please see the updated description for im-config in Test Case and Regression Potential for details. ** Description changed: IMPORTANT: SRU Team, see comment #25 for why this bug is temporarily marked verification-failed = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. + + Extended test case to verify input support still works in unconfined and confined applications: + + 1. Systems Settings Language Support, if prompted install the complete language support + 2. Install Chinese (simple and traditional) + 3. sudo apt-get install ibus-pinyin ibus-sunpinyin + 4. logout / login + 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) + 6. select pinyin from the indicator + 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... + 8. open gnome-calculator and try to type something in (should get a pop-up) + 9. open evince and try to search a pdf (should get a pop up) + 10. upgrade apparmor and im-config from xenial-proposed + 11. logout and back in + 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... + 13. open gnome-calculator and try to type something in (should get a pop-up) + 14. open evince and try to search a pdf (should get a pop up) + 15. verify no new apparmor denials + + [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus-daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd - interface, which is in progress. Currently the change should not regress - snapdsbehavior due to other issues surrounding using ibus unrelated to - security policy. + interface, which is in already done. + + This change intentionally requires a change to apparmor to add a unix + rule for communicating with the new ibus address. This is in xenial- + proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages + changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to + ensure that the apparmor abstraction is updated and policy recompiled + before ibus is restarted. This was omitted from the initial im-config + upload which resulted in bug #1588197. Test cases ensuring this is + working properly is included above under 'Extended test case'. + = SRU apparmor = [Impact] The upload that adjusts ibus-daemon to start with "--address 'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be sufficient due to the lack of a rule for the new socket path. This upload adds such a rule. [Test Case] 1. Start a unity session after updating to the im-config package in -proposed but before the
[Desktop-packages] [Bug 1631241] [NEW] Name resolution stops working after resume from suspend
You have been subscribed to a public bug: After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from suspend DNS resolution stops working. After resuming, systemd-resolved is running and libnss-resolve is installed, but /etc/resolv.conf contains 127.0.1.1 as the the only name server. The dnsmasq-base package is installed since it is pulled in by both network-manager and lxc1, and both NM and libvirt have spawned instances of dnsmasq: > 1155 pts/2S+ 0:00 grep dnsmasq > 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order > --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 > --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override > --except-interface=lo --interface=lxcbr0 > --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative > 2992 ?S 0:00 /usr/sbin/dnsmasq > --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro > --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 2993 ?S 0:00 /usr/sbin/dnsmasq > --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro > --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper > 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground > --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid > --listen-address=127.0.1.1 --cache-size=0 --conf-file=/dev/null > --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq > --conf-dir=/etc/NetworkManager/dnsmasq.d Let me know if you need any extra info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libnss-resolve 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 7 13:52:40 2016 InstallationDate: Installed on 2015-07-22 (443 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- Name resolution stops working after resume from suspend https://bugs.launchpad.net/bugs/1631241 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. -- 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 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)
** Description changed: = SRU im-config = [Impact] ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has AppArmor mediation, ibus-daemon does not so it is important that its abstract socket not be confused with dbus-daemon's. By modifying ibus-daemon's start arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue mediating DBus abstract sockets like normal and also mediate access to the ibus-daemon-specific abstract socket via unix rules. This also tidies up the abstract socket paths so that it is clear which are for ibus-daemon, which for dbus-daemon, etc. The upload simply adjusts 21_ibus.rc to start ibus-daemon with "-- address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code changes are required. [Test Case] 1. start a unity session before updating to the package in -proposed 2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76 3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 2973 jamie8u unix 0x 0t0 29606 @/tmp/dbus-oxKYpN30 type=STREAM 4. update the package in -proposed and perform '2' and '3'. The IBUS_ADDRESSES should be the same as before 5. logout of unity, then log back in 6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0 IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e (notice '/tmp/ibus/' in the path) 7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus' ibus-daem 3471 jamie8u unix 0x 0t0 26107 @/tmp/ibus/dbus-SpxOl8Fc type=STREAM ... (notice '@/tmp/ibus/' in the path) In addition to the above, you can test for regressions by opening 'System Settings' under the 'gear' icon in the panel and selecting 'Text Entry'. From there, add an input source on the right, make sure 'Show current input source in the menu bar' is checked, then use the input source panel indicator to change input sources. Extended test case to verify input support still works in unconfined and confined applications: 1. Systems Settings Language Support, if prompted install the complete language support 2. Install Chinese (simple and traditional) 3. sudo apt-get install ibus-pinyin ibus-sunpinyin 4. logout / login 5. System Settings / Text Entry - add Chinese (Pinyin) (IBus) 6. select pinyin from the indicator 7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-... 8. open gnome-calculator and try to type something in (should get a pop-up) 9. open evince and try to search a pdf (should get a pop up) 10. upgrade apparmor and im-config from xenial-proposed 11. logout and back in 12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/... 13. open gnome-calculator and try to type something in (should get a pop-up) 14. open evince and try to search a pdf (should get a pop up) 15. verify no new apparmor denials [Regression Potential] The regression potential is considered low because there are no compiled code changes and because the changes only occur after ibus-daemon is restarted, which is upon session start, not package upgrade. When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are updated accordingly for other applications to pick up. This change intentionally requires a change to the unity7 snapd interface, which is in already done. This change intentionally requires a change to apparmor to add a unix rule for communicating with the new ibus address. This is in xenial- proposed 2.10.95-0ubuntu2.3 (and 2.10.95-0ubuntu2.4). The packages changes to im-config use 'Breaks: apparmor (<< 2.10.95-0ubuntu2.3) to ensure that the apparmor abstraction is updated and policy recompiled before ibus is restarted. This was omitted from the initial im-config upload which resulted in bug #1588197. Test cases ensuring this is - working properly is included above under 'Extended test case'. + working properly are included above under 'Extended test case'. = SRU apparmor = [Impact] The upload that adjusts ibus-daemon to start with "--address 'unix:tmpdir=/tmp/ibus'" causes the ibus AppArmor abstraction to no longer be sufficient due to the lack of a rule for the new socket path. This upload adds such a rule. [Test Case] 1. Start a unity session after updating to the im-config package in -proposed but before the apparmor package in -proposed 2. Use the ibus client program to list the available engines $ ibus list-engine language: Spanish; Castilian xkb:latam::spa - Spanish (Latin American) xkb:es::spa - Spanish language: Slovak xkb:sk:qwerty:slo - Slovak (qwerty) xkb:sk::slo - Slovak ... 3. Create an AppArmor profile file, called ibus, with the following contents: #include
[Desktop-packages] [Bug 1631547] [NEW] /usr/bin/rhythmbox:11:rb_track_transfer_queue_cancel_batch:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit:gtk_button_do_release
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding rhythmbox. This problem was most recently seen with version 3.3-1ubuntu7, the problem page at https://errors.ubuntu.com/problem/788272b85360f97cc3f267c8937779dd259903c6 contains more details. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: kylin-15.04 utopic vivid wily xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1631547 Title: /usr/bin/rhythmbox:11:rb_track_transfer_queue_cancel_batch:_g_closure_invoke_va:g_signal_emit_valist:g_signal_emit:gtk_button_do_release Status in rhythmbox package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding rhythmbox. This problem was most recently seen with version 3.3-1ubuntu7, the problem page at https://errors.ubuntu.com/problem/788272b85360f97cc3f267c8937779dd259903c6 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1631547/+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 1447860] Re: Ibus m17n does not use system keybaord layout
The bug still persists in 16.04. It seems to affect other m17n input methods as well, such as the Sanskrit IAST transliteration IME. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1447860 Title: Ibus m17n does not use system keybaord layout Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Since 14.04 I can not not use Ibus Other-latin-post(m17n) input method because it uses English keyboard layout. I have a Japanese keyboard, ibus-setup Advanced->Use system keyboard layout is ignored. There is no option to choose keyboard in ibus-setup Input Method ->Other-latn-post (m17n) either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1447860/+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 1631519] [NEW] No X on boot with external monitor connected
Public bug reported: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 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: Fri Oct 7 20:23:46 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161007) MachineType: LENOVO 2306CTO ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/username.seed boot=casper quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Oct 7 20:18:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- 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/1631519 Title: No X on boot with external monitor connected Status in xorg package in Ubuntu: New Bug description: Running from today's (201610907) daily yakkety livecd I can boot to the desktop if only using the laptop's LCD (ThinkPad x230, intel graphics). Attaching a 1920x1080 LCD via miniDP extends the desktop but windows moved around produce a trail of windows that persist even after the window is closed. Also, when booting from the livecd with the external display attached X does not start. This is a regression from Xenial. $ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 $ apt-cache policy xorg xorg: Installed: 1:7.7+13ubuntu4 Candidate: 1:7.7+13ubuntu4 Version table: *** 1:7.7+13ubuntu4 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CompizPlugins: No
[Desktop-packages] [Bug 1447860] Re: Ibus m17n does not use system keybaord layout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1447860 Title: Ibus m17n does not use system keybaord layout Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Since 14.04 I can not not use Ibus Other-latin-post(m17n) input method because it uses English keyboard layout. I have a Japanese keyboard, ibus-setup Advanced->Use system keyboard layout is ignored. There is no option to choose keyboard in ibus-setup Input Method ->Other-latn-post (m17n) either. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1447860/+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 1610733] Re: ubuntu software empty
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1610733 Title: ubuntu software empty Status in gnome-software package in Ubuntu: Expired Bug description: I read what was on the forum and mine also didnt work after trying the fixes thet didnt work. I looked in the application manager and found that it had 2 versions ubuntu software and ubuntu software manager I deleted the ubuntu software manager and the problem was solved. ubuntu software manager from the old version 15.10 was interfering with ubuntu software . Thanks Randy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1610733/+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 1506166] Re: Bracketed paste should be per-terminal [PATCH]
** No longer affects: vte3 (Ubuntu Xenial) ** Changed in: vte (Ubuntu) Importance: Undecided => Medium ** Changed in: vte (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: vte (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1506166 Title: Bracketed paste should be per-terminal [PATCH] Status in Gnome Virtual Terminal Emulator: Fix Released Status in vte package in Ubuntu: New Status in vte3 package in Ubuntu: Fix Released Status in vte source package in Trusty: New Status in vte3 source package in Trusty: Fix Released Status in vte source package in Xenial: New Bug description: [Impact] Bracketed paste mode (\e[?2004h) should be per-terminal (as it is for xterm), not per-screen. This was fixed upstream for vte3 0.36.2, however Trusty ships vte3 0.34.2 and it didn't make it: https://bugzilla.gnome.org/show_bug.cgi?id=729533 This bug is causing annoying garbage appended to every paste in mc: https://www.midnight-commander.org/ticket/3207 I have backported the fix to Trusty, tested it in my PPA and would appreciate if someone could sponsor an upload in updates, since Trusty is LTS after all. [Test Case] Select some text ("test") and copy it into the clipboard buffer. After that, install mc if you don't have it already and start it: sudo apt-get install mc mc Press CTRL+O to swap the panels, right click with the mouse button and pick "Paste" from the context menu. You will see that "~0test~1" is pasted into the console instead of "test" as it should be. For more details, see the bug report on mc bug tracker referenced above. [Regression Potential] The patch is taken from the vte3 bug tracker; it has been in trunk for more than a year and is contained in vte3 0.36.2+ releases. Nobody has reported any problems caused by this change so far... To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1506166/+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 1631560] [NEW] Narrow spacing of icons in Files affects file names
Public bug reported: When I upgraded to Ubuntu 16.10 beta a few days ago, horizontal distance between icons in Files and on the desktop got much smaller. Because of this there's less room horizontally for the file names, and many words got their last letters cut off to the next row. In many file names full rows now alternate with rows of only a couple of cut off letters. Name fields with longer file names also look disproportionately narrow and tall now. I think the spacing should be changed back to what it was, or at least it should be user selectable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-20.22-generic 4.8.0 Uname: Linux 4.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 04:04:55 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time']" InstallationDate: Installed on 2016-03-27 (194 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fi PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1631560 Title: Narrow spacing of icons in Files affects file names Status in nautilus package in Ubuntu: New Bug description: When I upgraded to Ubuntu 16.10 beta a few days ago, horizontal distance between icons in Files and on the desktop got much smaller. Because of this there's less room horizontally for the file names, and many words got their last letters cut off to the next row. In many file names full rows now alternate with rows of only a couple of cut off letters. Name fields with longer file names also look disproportionately narrow and tall now. I think the spacing should be changed back to what it was, or at least it should be user selectable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-20.22-generic 4.8.0 Uname: Linux 4.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 04:04:55 2016 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'thumbnail-limit' b'uint64 4294967295' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time']" InstallationDate: Installed on 2016-03-27 (194 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=fi PATH=(custom, no user) LANG=fi_FI.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1631560/+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 1628790] Re: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop
OK I changed my account to an admin in hopes it would stop. But it still gets stuck in the loop as soon as the Auto-Login feature is turned on in Lubuntu. Anyway, "ls .Xauthority -l" returns with: -rw--- 1 joel joel 55 Oct 8 12:35 .Xauthority. -- 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/1628790 Title: Changing the user settings to autologin on Lubuntu 16.04 causes LightDM to get stuck in a login loop Status in lightdm package in Ubuntu: Incomplete Bug description: After setting my account to login automatically through the user and groups setting in Lubuntu. After the computer reboots it gets stuck in a loop on the login screen. Logging in will just send you back to the same screen. The only way I could fix the issue was to press CRTL + ALT + F1, logging in through the CLI and typing: "sudo mv .Xauthority .Xauthority.bak" and then once I was back to the login screen I was able to login and turn the setting off. I did check to see weather that was what caused it, by restarting the computer without turning off the auto-login. However the same issue happened and only turning off auto-login would stop the login loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1628790/+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 1631288] Re: XV video screen always on top
Christorpher, first thank you for your concern. 1) I just buy this computer and the previous releases were not correctly working whith the hardware that's why i chose this release and test it only. 2) I did not have time to test this issue seen that i was facing other HW issue such as network. 3) I will perform a test ASAP. Steph -- 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/1631288 Title: XV video screen always on top Status in xorg package in Ubuntu: Incomplete Bug description: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Skylake Integrated Graphics [1179:001d] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d] InstallationDate: Installed on 2016-10-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: TOSHIBA TECRA Z50-C PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.70 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z50-C dmi.product.version: PT577E-01100GCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 17:44:07 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1237 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1629132] Re: Please merge network-manager-openvpn 1.2.6-2 from Debian (unstable) to Ubuntu (yakkety)
I uploaded this to the queue now, thanks. I think it would be reasonable to have this be an SRU instead, depending on what the reviewer thinks. The changes aren't super small and while as far as I can tell they are all fine, there's a chance there is a problem. Either would be okay with me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1629132 Title: Please merge network-manager-openvpn 1.2.6-2 from Debian (unstable) to Ubuntu (yakkety) Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Please merge network-manager-openvpn 1.2.4-1 from Debian (unstable) to Ubuntu (yakkety), to match with the version of main network-manager package (1.2.4). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1629132/+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 1623835] Re: Updated gtk element means you need to specify a size on the details drop down or it is only 1 line high
** Changed in: deja-dup (Ubuntu) Status: New => Triaged ** Changed in: deja-dup (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Low -- 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/1623835 Title: Updated gtk element means you need to specify a size on the details drop down or it is only 1 line high Status in deja-dup package in Ubuntu: Triaged Bug description: STEPS: 1. install 16.10 2. Run deja-dup 3. Click on the details drop down EXPECTED: I expect to see 4-5 lines in height and it be scrollable ACTUAL: The drop down appears to be 1 line and not scroll ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: deja-dup 34.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 15 09:21:28 2016 InstallationDate: Installed on 2016-07-25 (51 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: deja-dup UpgradeStatus: Upgraded to yakkety on 2016-09-06 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1623835/+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 551982] Re: Feature request: Add Amazon S3 support to gvfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- 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/551982 Title: Feature request: Add Amazon S3 support to gvfs Status in gvfs package in Ubuntu: Confirmed Bug description: Binary package hint: gvfs Amazon S3 (Simple Storage Service) is an online storage web service offered by Amazon Web Services. Amazon S3 provides unlimited storage through a simple web services interface. This report was created to track the request to add Amazon S3 support to gvfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/551982/+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 1631288] Re: XV video screen always on top
dabrain, thank you for reporting this and helping make Ubuntu better. To clarify: 1) Did this issue start after an update? 2) Did this issue occur in a Ubuntu release prior to 16.04? 3) To see if this is resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1631288 Title: XV video screen always on top Status in xorg package in Ubuntu: Incomplete Bug description: When playing a video with vlc, gstreamer(xvimagesink), the video stays on top of every X window. In VLC this bug can be bypassed disabling overlay video. In Gstreamer using ximagsink is ok too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: 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: Fri Oct 7 09:45:31 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Skylake Integrated Graphics [1179:001d] Subsystem: Toshiba America Info Systems GM108M [GeForce 930M] [1179:001d] InstallationDate: Installed on 2016-10-03 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: TOSHIBA TECRA Z50-C PlymouthDebug: Error: [Errno 13] Permission denied: '/var/log/plymouth-debug.log' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=f4f5014d-ef0f-49c7-9842-c164aa8b4bbc ro plymouth:debug splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2016 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 5.70 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-C dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion5.70:bd04/15/2016:svnTOSHIBA:pnTECRAZ50-C:pvrPT577E-01100GCE:rvnTOSHIBA:rnTECRAZ50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: TECRA Z50-C dmi.product.version: PT577E-01100GCE dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.68-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 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-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Oct 6 17:44:07 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1237 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631288/+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 1624571] Re: White lines visible around LibreOffice toolbars in when using GTK3
** Branch linked: lp:~flexiondotorg/ubuntu-themes/lp1624571 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1624571 Title: White lines visible around LibreOffice toolbars in when using GTK3 Status in ubuntu-mate: Triaged Status in libreoffice package in Ubuntu: Triaged Status in ubuntu-mate-artwork package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: In Progress Bug description: There are some portions where the theme is not consistent like on the right side "x" and so on. In the pictures you will see a comparation side by side with UBUNTU Mate 16.04 with Mate 1.14 gtk2 ppa The top bar from the picture it's from 16.10 and the next bar it's from 16.04 OS: Ubuntu 16.10 daily Interface : Mate 1.15.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1624571/+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