[Desktop-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases
@Magezi: Please note that this is a bug report, not a support forum. This Ask Ubuntu question may help: https://askubuntu.com/q/915415 -- 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/1663157 Title: Guest session processes are not confined in 16.10 and newer releases Status in Light Display Manager: New Status in lightdm package in Ubuntu: Fix Released Status in lightdm source package in Yakkety: Fix Released Status in lightdm source package in Zesty: Fix Released Status in lightdm source package in Artful: Fix Released Bug description: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1663157/+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 1731929] Re: cairomm drops v5, whilst debian didn't
** Changed in: cairomm (Ubuntu) Assignee: Ubuntu Desktop (ubuntu-desktop) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairomm in Ubuntu. https://bugs.launchpad.net/bugs/1731929 Title: cairomm drops v5, whilst debian didn't Status in cairomm package in Ubuntu: Fix Released Bug description: cairomm drops v5, whilst debian didn't cairomm (1.12.2-1ubuntu1) bionic; urgency=medium * Revert package rename for g++5 ABI transition, since the affected symbols were not part of the ABI; Provide: the renamed package for compatibility, and Conflicts/Replaces the old package. These changes can be dropped after the 18.04 release. -- Simon Quigley Thu, 09 Nov 2017 20:51:35 -0600 clarification is needed, if we want to do this or not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairomm/+bug/1731929/+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 1582986] Re: NetworkManager service does not start during bootup
*** This bug is a duplicate of bug 1487679 *** https://bugs.launchpad.net/bugs/1487679 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nfs-utils (Ubuntu) Status: New => Confirmed -- 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/1582986 Title: NetworkManager service does not start during bootup Status in network-manager package in Ubuntu: Confirmed Status in nfs-utils package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 4.4.0-22 systemd 229-4 network-manager 1.1.93 network-manager-gnome 1.2.0 Multiple services and targets are deleted by systemd to "break ordering cycle" (cf. boot.log), but NetworkManager is the only one of them (network.target,rpcbind,sysinit.target,open-iscsi.service,remote- fs-pre.target,iscsid.service,zfs-fuse.service - cf. their respective logs) which is not started after bootup: sudo systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) May 18 05:00:10 samsung-ubuntu systemd[1]: NetworkManager.service: Job NetworkManager.service/verify-active deleted to break ordering cycle starting with network.target/start Attachments: --- - journalctl -l -b0 --system _COMM=systemd > boot.log - systemctl -l status rpcbind > rpcbind.log - systemctl -l status network.target > network.target.txt - systemctl -l status remote-fs-pre.target > remote-fs-pre.target.log - systemctl -l status sysinit.target > sysinit.target.log - systemctl -l status zfs-fuse.service > zfs-fuse.service.log - systemctl -l status open-iscsi.service > open-iscsi.service.log - systemctl -l status iscsid.service > iscsid.service.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1582986/+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 388553] Re: Wi-Fi Protected Setup (WPS) not supported
This was fixed upstream with Network Manager 1.10: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-10 Now we need a good GUI to configure all the WPS stuff (gnome-control-center). -- 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/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: In Progress Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1732113] [NEW] [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No sound at all
Public bug reported: no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1p: l 1719 F...m pulseaudio /dev/snd/pcmC0D0c: l 1719 F...m pulseaudio /dev/snd/controlC0: l 1719 F pulseaudio l 2727 F alsamixer CurrentDesktop: Unity Date: Tue Nov 14 10:17:50 2017 InstallationDate: Installed on 2017-09-10 (64 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Internes Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1p: l 1719 F...m pulseaudio /dev/snd/pcmC0D0c: l 1719 F...m pulseaudio /dev/snd/controlC0: l 1719 F pulseaudio l 2727 F alsamixer Symptom_Jack: Green Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU911000L dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1732113 Title: [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: no sound at all ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1p: l 1719 F...m pulseaudio /dev/snd/pcmC0D0c: l 1719 F...m pulseaudio /dev/snd/controlC0: l 1719 F pulseaudio l 2727 F alsamixer CurrentDesktop: Unity Date: Tue Nov 14 10:17:50 2017 InstallationDate: Installed on 2017-09-10 (64 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Internes Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D1p: l 1719 F...m pulseaudio /dev/snd/pcmC0D0c: l 1719 F...m pulseaudio /dev/snd/controlC0: l 1719 F pulseaudio l 2727 F alsamixer Symptom_Jack: Green Speaker, Internal Symptom_Type: No sound at all Title: [HP EliteBook 8730w, Analog Devices AD1984A, Green Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU911000L dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1732113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1732117] [NEW] PPA for stable ("still") versions
Public bug reported:
I would like to have a PPA that follows the stable ("still") LibreOffice
version.
The "still" LibreOffice version is encouraged for users that want
stability. According to LibreOffice.org :
"If you deploy LibreOffice in an enterprise or corporate environment or
are a conservative user, please choose this version."
I am not a corporate user, but I prefer stable packages, as I have hit
the occasional bug in the "fresh" version.
Therefore, I am using LibreOffice 5.3 at the moment. I was shocked to
find out that the last maintenance update has been released around Oct
29, 2017, and the "End of Life" is coming as quickly as November 26,
2017. That's less than a month to manually upgrade all my PCs to the 5.4
version. A "still" PPA is something I can install and forget.
Actually, using PPAs for fixed versions, like 5.2, should be discouraged
on this website, as they are no longer receiving security updates.
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
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/1732117
Title:
PPA for stable ("still") versions
Status in libreoffice package in Ubuntu:
New
Bug description:
I would like to have a PPA that follows the stable ("still")
LibreOffice version.
The "still" LibreOffice version is encouraged for users that want
stability. According to LibreOffice.org :
"If you deploy LibreOffice in an enterprise or corporate environment
or are a conservative user, please choose this version."
I am not a corporate user, but I prefer stable packages, as I have hit
the occasional bug in the "fresh" version.
Therefore, I am using LibreOffice 5.3 at the moment. I was shocked to
find out that the last maintenance update has been released around Oct
29, 2017, and the "End of Life" is coming as quickly as November 26,
2017. That's less than a month to manually upgrade all my PCs to the
5.4 version. A "still" PPA is something I can install and forget.
Actually, using PPAs for fixed versions, like 5.2, should be
discouraged on this website, as they are no longer receiving security
updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1732117/+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 1732116] [NEW] HDMI device is not working / not found
Public bug reported: after conecting TV over HDMI, Ubuntu doenst find the external display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Tue Nov 14 10:29:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-09-10 (64 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU911000L dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.13 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 14 09:58:47 2017 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) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1732116 Title: HDMI device is not working / not found Status in xorg package in Ubuntu: New Bug description: after conecting TV over HDMI, Ubuntu doenst find the external display ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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: Tue Nov 14 10:29:17 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-09-10 (64 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 8730w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.13 dmi.board.name: 30EC dmi.board.vendor: Hewlett
[Desktop-packages] [Bug 1731873] Re: Backport amdgpu-pro support
@Alberto what exactly version of the one proposed ? I can not find related change log on current proposed : http://paste.ubuntu.com/25959552/ ** Tags added: from-1728547 -- 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/1731873 Title: Backport amdgpu-pro support Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: In Progress Status in ubuntu-drivers-common source package in Zesty: In Progress Bug description: SRU Request: [Impact] Support for the amdgpu-pro driver has been available in Artful since May 2017. We need to backport the code to the other stable releases. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the amdgpu-pro packages are installed (if not, install them, and restart your system). 3) Check that power saving mode is supported: amdgpu-pro-px --ispx If it returns true, then it is supported by the hardware. 4) Set power saving mode: sudo amdgpu-pro-px --mode powersaving 5) Restart your computer and check that the "Enabling power saving mode for amdgpu-pro" line is in your /var/log/gpu-manager.log. 6) Install the mesa-utils package: sudo apt install mesa-utils 7) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default, unless users set power saving manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1731873/+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 1731873] Re: Backport amdgpu-pro support
@Alex they haven't approved my upload yet. It's still in the queue: https://launchpad.net/ubuntu/xenial/+queue?queue_state=1&queue_text= https://launchpadlibrarian.net/345595463/ubuntu-drivers- common_0.4.17.4_source.changes http://launchpadlibrarian.net/345596100/ubuntu-drivers- common_1%3A0.4.17.3_1%3A0.4.17.4.diff.gz The only change is in the changelog. -- 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/1731873 Title: Backport amdgpu-pro support Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Xenial: In Progress Status in ubuntu-drivers-common source package in Zesty: In Progress Bug description: SRU Request: [Impact] Support for the amdgpu-pro driver has been available in Artful since May 2017. We need to backport the code to the other stable releases. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common" 2) Make sure the amdgpu-pro packages are installed (if not, install them, and restart your system). 3) Check that power saving mode is supported: amdgpu-pro-px --ispx If it returns true, then it is supported by the hardware. 4) Set power saving mode: sudo amdgpu-pro-px --mode powersaving 5) Restart your computer and check that the "Enabling power saving mode for amdgpu-pro" line is in your /var/log/gpu-manager.log. 6) Install the mesa-utils package: sudo apt install mesa-utils 7) Check the output of the following command (which should mention Intel): glxinfo | grep OpenGL [Regression Potential] Low, as the feature is disabled by default, unless users set power saving manually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1731873/+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 1726616] Re: Firefox crashes repeatedly after system update
Hello, I see that the status of this ticket has been changed from "New" to "Invalid" without any explanation. Is there something I did wrong (or that I could have done better) when I submitted the bug ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1726616 Title: Firefox crashes repeatedly after system update Status in ubuntu-mate: Invalid Status in firefox package in Ubuntu: New Bug description: How to reproduce: - Download and install Ubuntu Mate 16.04.2 LTS, Raspberry Edition, on a micro SD card. - Boot the Pi with that card, and launch Firefox. Everything's OK so far. By the way, it's FF 54.0. - Update everything either with Software Updater or with apt-get update + apt-get upgrade. - (Attempt to) launch Firefox again. It won't start at all, and all you'll get will be a window repeatedly saying that Firefox has crashed, and proposing to send a bug report. I've initially noticed this issue on the latest (LTS) version of the Raspberry Edition of Ubuntu Mate (16.04.2), and afterwards reproduced it on the 32-bit version of the Desktop Edition (16.04.3), so it's not a Raspberry-specific issue. But, oddly enough, not on the 64-bit version, where Firefox was updated from 54.0 to 56.0 and kept running fine. I did not try more recent versions of the Desktop Edition (17.04 or 17.10) because the latest available for the Pi is the 16.04.2. I wish I could help more, by pinpointing precisely what has gone wrong, but this is the first time I report a bug in Ubuntu, and I don't know where to start the debugging. Thanks for reading, Marc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1726616/+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 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Any progress in seeing this fixed in Xenial? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1732151] [NEW] [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: That's the second time i wanted to use Ubuntu and had the same issue. This is a fresh installation and I didn't install nothing related to sound. ProblemType: Bug DistroRelease: elementary 0.4.1 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rchgonzaga 1613 F pulseaudio CurrentDesktop: Pantheon Date: Tue Nov 14 08:36:00 2017 InstallationDate: Installed on 2017-11-12 (1 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rchgonzaga 1613 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 7460 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug loki third-party-packages -- 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/1732151 Title: [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: That's the second time i wanted to use Ubuntu and had the same issue. This is a fresh installation and I didn't install nothing related to sound. ProblemType: Bug DistroRelease: elementary 0.4.1 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rchgonzaga 1613 F pulseaudio CurrentDesktop: Pantheon Date: Tue Nov 14 08:36:00 2017 InstallationDate: Installed on 2017-11-12 (1 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rchgonzaga 1613 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [Inspiron 7460, Intel Kabylake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.1 dmi.board.name: 09WC1G dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.1:bd02/14/2017:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn09WC1G:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 7460 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1732151/+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 1727057] Re: Drag and Drop Malfunction
*** This bug is a duplicate of bug 1704765 *** https://bugs.launchpad.net/bugs/1704765 Yup - I have the same problem. Be nice is Ubuntu would recognize and issue a patch -- 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/1727057 Title: Drag and Drop Malfunction Status in nautilus package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 17.04 64bit to 17.10 transferring a file from one folder to another fails with drag and drop. The grab will move the file but not drop it. It is as if the mouse-up does not register. The grab remains but mouse will not release until I log out of my account and log in again. The right click "move to" will work to move files. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe 10841 F pulseaudio /dev/snd/controlC1: joe 10841 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:31:02 2017 HibernationDevice: RESUME=UUID=8aeb251b-127a-4963-905c-dda8e223e0ba InstallationDate: Installed on 2015-11-20 (703 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=159fdd5e-4a8b-4a5b-850f-5dabb27d2be3 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (4 days ago) dmi.bios.date: 03/26/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/26/2012:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1727057/+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 388553] Re: Wi-Fi Protected Setup (WPS) not supported
Grazie mille! Sadly, I'm a very long way from being able to handle the creation of the GUI side... it's too many decades since I used to programme. Respect to the coders! On 14 November 2017 at 09:08, Daniele Napolitano wrote: > This was fixed upstream with Network Manager 1.10: > https://cgit.freedesktop.org/NetworkManager/NetworkManager/ > tree/NEWS?h=nm-1-10 > > > Now we need a good GUI to configure all the WPS stuff > (gnome-control-center). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/388553 > > Title: > Wi-Fi Protected Setup (WPS) not supported > > Status in Ayatana Design: > New > Status in NetworkManager: > In Progress > Status in network-manager package in Ubuntu: > Triaged > > Bug description: > As the title the Wi-Fi Protected Setup (WPS) is not supported by > NetworkManager (but is supported by wpa_supplicant). > > The WPS WI-Fi standard is implementated in various newer access points > and allow user to configure the access point in just a few of steps > and do all configuring process very simple. > > Specifications: http://www.wi-fi.org/wifi-protected-setup/ > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ayatana-design/+bug/388553/+subscriptions > -- 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/388553 Title: Wi-Fi Protected Setup (WPS) not supported Status in Ayatana Design: New Status in NetworkManager: In Progress Status in network-manager package in Ubuntu: Triaged Bug description: As the title the Wi-Fi Protected Setup (WPS) is not supported by NetworkManager (but is supported by wpa_supplicant). The WPS WI-Fi standard is implementated in various newer access points and allow user to configure the access point in just a few of steps and do all configuring process very simple. Specifications: http://www.wi-fi.org/wifi-protected-setup/ To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/388553/+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 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
libsane1 is marked as "Multi-Arch: same", but the contents of /lib/udev/hwdb.d/20-sane.hwdb are different among architectures: $ dpkg-deb --control /var/cache/apt/archives/libsane1_1.0.27-1~experimental2ubuntu1_amd64.deb amd64/ $ dpkg-deb --control /var/cache/apt/archives/libsane1_1.0.27-1~experimental2ubuntu1_i386.deb i386/ $ grep 20-sane.hwdb amd64/md5sums 822a0103c173599c49c01c41e7431450 lib/udev/hwdb.d/20-sane.hwdb $ grep 20-sane.hwdb i386/md5sums ed74da55eee3cbfee774e04f55669d28 lib/udev/hwdb.d/20-sane.hwdb So, this is a bug in this package's packaging. I'll change the header to reflect this. ** Summary changed: - package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 + package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1725928 Title: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files Status in sane-backends package in Ubuntu: Confirmed Bug description: apport error this morning. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 09:37:46 2017 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2016-10-08 (378 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1725928/+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 1725238] Re: Clicking snap:// urls doesn't work
** Branch linked: lp:~mozillateam/firefox/firefox.trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1725238 Title: Clicking snap:// urls doesn't work Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Confirmed Bug description: I am unable to trigger GNOME Software to install snaps. Steps to reproduce: 1. Visit http://snapcraft.io/zzt 2. Click green Install button 3. Browser is taken to snap://zzt Outcome:- "The address wasn't understood" error page in Firefox Expected outcome:- GNOME Software launches directly on the ZZT snap app page. Here's a video showing it:- https://www.youtube.com/watch?v=rOaGt8W2zrY ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 2350 F pulseaudio /dev/snd/controlC1: alan 2350 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 12:06:27 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-02 (78 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1725238/+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 1732173] [NEW] Java GUI apps do not work properly under Wayland
Public bug reported: I'm running Ubuntu 17.10 with Wayland enabled. I noticed Java GUI apps running with native look and feel (i.e. Swing based apps with GTK look and feel) do not properly work, i.e. fonts are not displayed properly, windows sometimes do not draw correctly and other problems. If I switch to X11 all works fine instead. The Java version is: java version "1.8.0_152" Java(TM) SE Runtime Environment (build 1.8.0_152-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 12:20:33 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2017-10-24 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=4f5a6ba3-2eb6-42d3-aa57-c85c628e312d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1732173 Title: Java GUI apps do not work properly under Wayland Status in xorg package in Ubuntu: New Bug description: I'm running Ubuntu 17.10 with Wayland enabled. I noticed Java GUI apps running with native look and feel (i.e. Swing based apps with GTK look and feel) do not properly work, i.e. fonts are not displayed properly, windows sometimes do not draw correctly and other problems. If I switch to X11 all works fine instead. The Java version is: java version "1.8.0_152" Java(TM) SE Runtime Environment (build 1.8.0_152-b16) Java HotSpot(TM) 64-Bit Server VM (build 25.152-b16, mixed mode) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 12:20:33 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2017-10-24 (20 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UU
[Desktop-packages] [Bug 1708874] Re: Touchpad stops working after a few seconds
I have similar issue on Ubuntu 17.10(Ubuntu on Xorg), 4.10.0-37-generic running on: Manufacturer: Acer Product Name: Spin SP513-51 The touch-pad freezes, though not immediately after reboot, but every 2-3 hours or so. There are no records in dmesg at the time of freeze. Logging out and back does not help, only rebooting works. The issue persists in Ubuntu(Wayland) as well. Changing kernel did not help. Please let me know if you need any logs. -- 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/1708874 Title: Touchpad stops working after a few seconds Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ideapad 320, AMD A12 processor AMD A12-9720P RADEON R7, 12 COMPUTE CORES 4C+8G × 4 Software: Ubuntu Mate 17.10 Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Expected Behavior: Touchpad working. Actual Behavior: Touchpad works for about 30 or fewer seconds on boot, then doesn't work again until reboot. Dmesg shows nothing happening when it stops working. Let me know if I need to do anything. Thanks! ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: MATE Date: Sat Aug 5 14:52:39 2017 InstallationDate: Installed on 2017-08-05 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1708874/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I have the same issue. especially when VLC is hung. I think it happens when a not-responding dialog is showing on some window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I have the same issue in Ubuntu 17.10 (Wayland). I was using Netbeans, Chrome and a VirtualBox VM running Windows 10. It seemed that the VirtualBox grabbed the mouse, but it has mouse integration, and the actions bar and activities were clickable. I couldn't resolve it by switching to another virtual terminal, neither by running "gnome-shell -r" on a gnome-terminal (it said: (gnome- shell:5963): mutter-WARNING **: Can't initialize KMS backend: Could not get session ID: No such file or directory). So, I had to close everything and logout and login again. It worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1732054] Re: Different monitors with different DPIs aren't properly scaled
** Changed in: gnome-shell Status: Unknown => In Progress ** Changed in: gnome-shell Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1732054 Title: Different monitors with different DPIs aren't properly scaled Status in GNOME Shell: In Progress Status in gnome-shell package in Ubuntu: In Progress Bug description: In a multi-monitor setup with monitors with different pixel density, it's not possible to have them scaled differently. Currently this can be enabled with the command: gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']" But not enabled by default. Also, in this case the resources aren't properly scaled and look blurry. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1732054/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock
** Changed in: pulseaudio (Ubuntu) Status: Triaged => In Progress ** Changed in: hwe-next Status: Triaged => In Progress -- 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/1718824 Title: The analogue audio does not work on the Dell USB Dock Status in HWE Next: In Progress Status in pulseaudio package in Ubuntu: In Progress Bug description: SRU Document: [Impact] If users use the latest Dell USB Dock, e.g. TB16, they will found the analog audio (lineout jack) can't work under ubuntu linux [Test Case] After applying the fix, users can play sound via analog speaker or lineout freely. Without the fix, users can't play sound from lineout jack. [Regression Potential] No any possibility to introduce regression since this fix just adding a new dock's support, it does not change any existing code. [Other Info] No more info here Steps: 1. Cold boot system with BME/IE connected 2. Plug in a speaker to Line-out jack 3. Set Analog Stereo Output from Sound settings Expected results: Line-out port can work Actual results: Line-out port not work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1479710] Re: /usr/bin/gnome-disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now
** Changed in: gnome-disk-utility Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1479710 Title: /usr/bin/gnome- disks:11:g_dbus_object_get_interface:udisks_object_peek_drive:gdu_window_select_object:create_partition_cb:g_task_return_now Status in GNOME Disks: Expired Status in udisks: Confirmed Status in gnome-disk-utility package in Ubuntu: Triaged Status in udisks2 package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-disk-utility. This problem was most recently seen with version 3.16.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/9ec0e4eaf2490589696da7e6514c5fc0507946b0 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-disk-utility/+bug/1479710/+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 1731941] Re: duplicity should be installed by default as a dependency of deja-dup
Thank you, Michael! I put this up for discussion [1]. [1] https://bugs.launchpad.net/duplicity/+bug/1732183 -- 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/1731941 Title: duplicity should be installed by default as a dependency of deja-dup Status in deja-dup package in Ubuntu: Won't Fix Bug description: Just tested my Deja-dup backup configuration on a fresh install of 18.04. I was prompted to install duplicity. I am wondering whether duplicity should not better be installed as a dependency of deja-dup which is the default backup tool. What do you think? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1731941/+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 1732195] [NEW] Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter
Public bug reported: Alienware Alpha R2 Ubuntu 16.04.3 LTS Primary monitor is connected to Nvidia GTX 960 Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu) If only one monitor is connected via Nvidia GTX 960, it is totally normal. If the second monitor is also connected via Startech USB32HD4K, mouse cursor flickers frequently and can even disappear on the PRIMARY monitor (the one that is connected to Nvidia GTX 960). On the second monitor, everything is fine. One interesting thing I noticed is that if I set rotation in "All Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180 degrees" (just not "Normal") on the PRIMARY monitor, this issue is mitigated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Nov 14 23:59:01 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:072b] InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 002: ID 17e9:4301 DisplayLink Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware ASM201 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.8 dmi.board.name: 0GWM1Y dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00: dmi.product.name: ASM201 dmi.product.version: 1.0.8 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 14 23:55:35 2017 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) modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 displaylink 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/1732195 Title: Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter Status in xorg package in Ubuntu: New Bug description: Alienware Alpha R2 Ubuntu 16.04.3 LTS Primary monitor is connected to Nvidia GTX 960 Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu) If only one monitor is connected via Nvidia GTX 960, it is totally normal. If the second monitor is also connected via Startech USB32HD4K, mouse cursor flickers frequently and can even disappear on the PRIMARY monitor (the one that is connected to Nvidia GTX 960). On the second monitor, everything is fine. One interesting thing I noticed is that if I set rotation in "All Settings"->"Screen Display" to "Clockwise", "Anti
[Desktop-packages] [Bug 1732204] [NEW] Totem could not get a screenshot of the video
Public bug reported: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video Status in totem package in Ubuntu: New Bug description: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+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 1732204] Re: Totem could not get a screenshot of the video
I have fully upgraded the system and the problem persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video Status in totem package in Ubuntu: New Bug description: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+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 263369] Re: Save file reverts to last location used. If not available, error is displayed.
** Changed in: gimp Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/263369 Title: Save file reverts to last location used. If not available, error is displayed. Status in The Gimp: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: New Bug description: Binary package hint: gimp If saving a file, some programs (such as GIMP and Thunderbird) will try to revert to the last location used when saving. If that location no longer exists (disk off line, path name changed, etc.), it warns you that it could not be found. Steps to reproduce: 1) Insert USB key 2) Create file, then save file 3) Unmount USB key 4) Create a new file then save file -ERROR- (Screenshot attached) "Error stating file: No such file or directory" What is expected: Ignore the error, do not display error to user as it is not productive, instead show the user's home directory as the default path to save if the last path used is not available. I will report if this happens under any other applications as well. If anyone has experienced this using another application please report it below. Version Information: Ubuntu Hardy (2.6.24-19-generic) gimp 2.4.5-1ubuntu2 thunderbird 2.0.0.16+nobinonly-0ubuntu0.8.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/263369/+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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
I notice that the amd64-microcode package never gets updated in a stable Ubuntu release. amd microcode is part of upstream linux-firmware. Is it also shipped inside the ubuntu linux-firmware package? For example, this is the latest amd microcode commit upstream: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=5f8ca0c1db6106a2d6d7e85eee778917ff03c3de So my point is, is there a local policy to organize where the amd microcode is going to be shipped in Ubuntu? amd64-microcode or linux- firmware? -- 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/1386257 Title: intel-microcode should be installed by default, when the CPU is GenuineIntel Status in intel: Fix Released Status in Ubuntu Kylin: Fix Released Status in amd64-microcode package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntukylin-meta package in Ubuntu: Fix Released Bug description: intel-microcode should be installed by default on the bare-metal systems which are running on GenuineIntel CPUs, by the installers. Similarly other microcode packages for other CPUs brands should be considered for inclusion (e.g. amd64-microcode). I hope that ubuntu-drivers-common can gain ability to detect cpu series and/or vendors, packages that provide microcodes similarly declare support for cpu series and/or vendors, the microcode packages are shipped on the CDs in the pool directory, and installed on to the target machines as part of the installation. This should help with rapid correction of bugs and behaviour of the CPUs in the field. 2017 update, amd64-microcode should also be seeded, as it is useful to have it autoinstallable. In the recent years there have been critical CPU security vulnerabilities which got fixed with microcode updates. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1386257/+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 1732195] Re: Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter
Wei Cai, thank you for reporting this and helping make Ubuntu better. In order for DisplayLink to review this issue, could you please cross post this to them following their instructions from: http://support.displaylink.com/knowledgebase/articles/757047-how-can-i-report-ubuntu-issues-to-displaylink Please provide the URL of the post to them once submitted for tracking. ** Description changed: Alienware Alpha R2 - Ubuntu 16.04.3 LTS Primary monitor is connected to Nvidia GTX 960 Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu) If only one monitor is connected via Nvidia GTX 960, it is totally normal. If the second monitor is also connected via Startech USB32HD4K, mouse cursor flickers frequently and can even disappear on the PRIMARY monitor (the one that is connected to Nvidia GTX 960). On the second monitor, everything is fine. - One interesting thing I noticed is that if I set rotation in "All - Settings"->"Screen Display" to "Clockwise", "Anti-clockwise" or "180 - degrees" (just not "Normal") on the PRIMARY monitor, this issue is - mitigated. + WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following: + Clockwise + Anti-clockwise + 180 degrees ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Nov 14 23:59:01 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: - NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:072b] + NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:072b] InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: - Bus 002 Device 002: ID 17e9:4301 DisplayLink - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2b Intel Corp. - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 17e9:4301 DisplayLink + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware ASM201 ProcEnviron: - LANGUAGE=en_AU:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.8 dmi.board.name: 0GWM1Y dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00: dmi.product.name: ASM201 dmi.product.version: 1.0.8 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 14 23:55:35 2017 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) - modeset(G0): glamor initialization failed + Failed to loa
[Desktop-packages] [Bug 1731910] Re: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***
** Package changed: gnome-shell (Ubuntu) => evolution-data-server (Ubuntu) ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Fix Committed ** Bug watch added: GNOME Bug Tracker #789677 https://bugzilla.gnome.org/show_bug.cgi?id=789677 ** Also affects: evolution-data-server via https://bugzilla.gnome.org/show_bug.cgi?id=789677 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1731910 Title: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** Status in evolution-data-server: Unknown Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: no idea how to reproduce. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.1-0ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 AssertionMessage: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 10:13:10 2017 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid pointer", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 e_cal_component_free_datetime () at /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19 Title: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1731910/+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 1732195] Re: [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K
** Summary changed: - Mouse cursor keep flickering on primary monitor after a second monitor is connected via Displaylink USB3-TO-HDMI adapter + [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K -- 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/1732195 Title: [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K Status in xorg package in Ubuntu: Incomplete Bug description: Alienware Alpha R2 Primary monitor is connected to Nvidia GTX 960 Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu) If only one monitor is connected via Nvidia GTX 960, it is totally normal. If the second monitor is also connected via Startech USB32HD4K, mouse cursor flickers frequently and can even disappear on the PRIMARY monitor (the one that is connected to Nvidia GTX 960). On the second monitor, everything is fine. WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary monitor change Rotation from Normal to any of the following: Clockwise Anti-clockwise 180 degrees ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Nov 14 23:59:01 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:072b] InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 002: ID 17e9:4301 DisplayLink Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Alienware ASM201 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.8 dmi.board.name: 0GWM1Y dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00: dmi.product.name: ASM201 dmi.product.version: 1.0.8 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 14 23:55:35 2017 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) modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732195/+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 1725416] Re: Elantech touch pad device not detected/working properly
I recently installed Debian 9 with GNOME, it worked perfectly there. Upgraded to testing, keeped working. I don't know why Ubuntu is broken here, maybe just check the patch diff to debian. Must be there somewhere? Again - how can I help here further? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1725416 Title: Elantech touch pad device not detected/working properly Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I just upgraded to Ubuntu 17.10 (hooray, GNOME!). But there are some quirks. Under Unity/Ubuntu 17.04 my built-in Touchpad worked flawlessly - especially the "natural scrolling" mode was working well. As I saw under Ubuntu Gnome 17.04, the corresponding setting in gnome- control-center "Natural scrolling" just targets the mouse and has no effect on the touchpad. I can see the touchpad using "xinput list": ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=14 [slave pointer (2)] ⎜ ↳ Logitech Performance MX id=12 [slave pointer (2)] alongside my Logitech mouse on a Unifying receiver. Is there any chance that this touchpad is detected? Or should I forget about that (WONTFIX) as Xorg is already unsupported? ATM I am using the prop. nvidia drivers. Currently uninstalling them to see if Wayland is starting using nouveau... Thanks. What else do you need from me? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 20:20:04 2017 InstallationDate: Installed on 2016-11-27 (327 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1725416/+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 1731053] Re: Update gnome-shell to 3.26.2
This bug was fixed in the package gnome-shell - 3.26.2-0ubuntu1 --- gnome-shell (3.26.2-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release (LP: #1731053) * debian/control.in: - Drop redundant Suggests on gir1.2-gdm-1.0 * Drop patches applied in new release: - fix_reset_initial_focus.patch - git_layout-unset-when-headless.patch [ Didier Roche ] * Modify debian/patches/70_allow_sound_above_100.patch: - Fix a crasher when people log into the ubuntu session without installing gsettings-ubuntu-schemas (LP: #1712798) -- Jeremy Bicha Wed, 08 Nov 2017 16:19:02 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1731053 Title: Update gnome-shell to 3.26.2 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: In Progress Bug description: Impact == gnome-shell has released a new stable bugfix release. https://git.gnome.org/browse/gnome-shell/tree/NEWS/?h=gnome-3-26 https://git.gnome.org/browse/gnome-shell/log/?h=gnome-3-26 We had already cherry-picked two fixes: - fix_reset_initial_focus.patch - git_layout-unset-when-headless.patch We are also adding a fix for LP: #1712798 Test Case = After installing this update, please restart your computer. Verify that the default Ubuntu 17.10 desktop still works as well as it did before. Also log in to the "vanilla" GNOME session to verify that it works (you may need to install gnome-session and restart first). Optionally, you can go through some of the fixed bugs to verify the bug and the fix. Regression Potential GNOME Shell is also used for the login screen so it is really important that updates don't break it. This is a much smaller update than 3.26.1 (in terms of commits and lines of code changed) so it seems pretty unlikely to cause that kind of breakage. GNOME 3.26 distros will be shipping this update. There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731053/+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 1712798] Re: gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled
This bug was fixed in the package gnome-shell - 3.26.2-0ubuntu1 --- gnome-shell (3.26.2-0ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * New upstream release (LP: #1731053) * debian/control.in: - Drop redundant Suggests on gir1.2-gdm-1.0 * Drop patches applied in new release: - fix_reset_initial_focus.patch - git_layout-unset-when-headless.patch [ Didier Roche ] * Modify debian/patches/70_allow_sound_above_100.patch: - Fix a crasher when people log into the ubuntu session without installing gsettings-ubuntu-schemas (LP: #1712798) -- Jeremy Bicha Wed, 08 Nov 2017 16:19:02 -0500 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1712798 Title: gnome-shell errors out when gsettings-ubuntu-schemas is uninstalled Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: In Progress Bug description: [Impact] People installing ubuntu-desktop without recommends have a segfault when selecting the ubuntu session (not the GNOME vanilla one) on start [Test Case] * update from the version in proposed * ensure you don't have gsettings-ubuntu-schemas installed * boot into the ubuntu session -> you should have the Shell drawn, you won't have the option to set the sound above 100% though. [Regression Potential] The new code (listener callback) is now all protected by the same schema installed condition as when we first listened to it. Step to reproduce : - Install from http://archive.ubuntu.com/ubuntu/dists/artful/main/installer-amd64/current/images/netboot/mini.iso 2017-08-16 07:48 - Select Command-line install - Choose default option (wipe disk) - sudo apt update - sudo apt install ubuntu-desktop --no-install-recommends - reboot - upon login, the screen return immediately to the login screen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 Date: Thu Aug 24 13:08:38 2017 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1712798/+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 1580605] Re: gnome-shell crashes often
I do not know why this was changed to invalid. This is a critical issue
that has clearly introduced a regression set of crashes.
(there MAY be confusing reports from other users for other issues, but I
can confirm the originally submitted report)
This isn't fun, several times per day a crash:
{{{
$ dmesg -T | grep seg
[Thu Nov 9 09:58:27 2017] gnome-shell[17846]: segfault at e8 ip
7fd954f6d6a2 sp 7ffe04425eb8 error 4 in
libgdk-3.so.0.1800.9[7fd954f3+d4000]
[Thu Nov 9 10:11:16 2017] dota2[22006]: segfault at 0 ip 7fef2866683a sp
7fff560539a0 error 6 in libtier0.so[7fef2863+8]
[Thu Nov 9 13:04:18 2017] gnome-shell[1356]: segfault at e8 ip
7f15ccddd6a2 sp 7fff9ecf47f8 error 4 in
libgdk-3.so.0.1800.9[7f15ccda+d4000]
[Thu Nov 9 17:16:45 2017] gnome-shell[14440]: segfault at e8 ip
7f196afdd6a2 sp 7ffea13b5948 error 4 in
libgdk-3.so.0.1800.9[7f196afa+d4000]
[Thu Nov 9 17:16:52 2017] dconf worker[18015]: segfault at 52c ip
004a133c sp 7f351f7e6170 error 4 in perl[40+1cf000]
[Thu Nov 9 20:35:24 2017] gnome-shell[32271]: segfault at e8 ip
7fd6ef0256a2 sp 7ffebb0d3608 error 4 in
libgdk-3.so.0.1800.9[7fd6eefe8000+d4000]
[Thu Nov 9 20:42:09 2017] gnome-shell[11070]: segfault at 23 ip
7fc2bd8687bf sp 7fffcc3bc680 error 4 in
libgnome-desktop-3.so.12.0.0[7fc2bd848000+39000]
[Thu Nov 9 23:13:09 2017] gnome-shell[24832]: segfault at 6 ip
7fb95e624818 sp 7ffc656ced30 error 4 in
libgio-2.0.so.0.4800.2[7fb95e56+18]
[Thu Nov 9 23:51:17 2017] gnome-shell[3253]: segfault at e8 ip
7f2d1f4756a2 sp 7fff455b3128 error 4 in
libgdk-3.so.0.1800.9[7f2d1f438000+d4000]
[Fri Nov 10 01:09:27 2017] gnome-shell[31134]: segfault at e8 ip
7f3b923756a2 sp 7fff91dea558 error 4 in
libgdk-3.so.0.1800.9[7f3b92338000+d4000]
[Fri Nov 10 01:12:43 2017] gnome-shell[9188]: segfault at e8 ip
7f683370d6a2 sp 7ca20198 error 4 in
libgdk-3.so.0.1800.9[7f68336d+d4000]
[Fri Nov 10 03:40:54 2017] gnome-shell[25978]: segfault at e8 ip
7f8af06ed6a2 sp 7ffdf3c5cfc8 error 4 in
libgdk-3.so.0.1800.9[7f8af06b+d4000]
[Sat Nov 11 00:49:59 2017] gnome-shell[31566]: segfault at e8 ip
7ffab7ae56a2 sp 7fff76561338 error 4 in
libgdk-3.so.0.1800.9[7ffab7aa8000+d4000]
[Sat Nov 11 20:01:10 2017] gnome-shell[23459]: segfault at e8 ip
7f6a4c1dd6a2 sp 7ffdfcd62008 error 4 in
libgdk-3.so.0.1800.9[7f6a4c1a+d4000]
[Sat Nov 11 21:05:36 2017] gnome-shell[28874]: segfault at e8 ip
7f48523d56a2 sp 7ffd15fbc738 error 4 in
libgdk-3.so.0.1800.9[7f4852398000+d4000]
}}}
My setup:
* Dual monitors
* OFTEN switch between users
a) using the GDM3 "switch user" GUI
b) using CTRL+ALT+FXX quick flips
* Daily I suspend the system and resume (Power Management)
Versions
{{{
$ cat /etc/issue
Ubuntu 16.04.3 LTS \n \l
$ uname -a
Linux 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ dpkg --list | grep gnome-shell
ii chrome-gnome-shell
9-0ubuntu1~ubuntu16.04.3 all GNOME Shell
extensions integration for web browsers
ii gnome-shell
3.18.5-0ubuntu0.3amd64graphical shell for
the GNOME desktop
ii gnome-shell-common
3.18.5-0ubuntu0.3all common files for the
GNOME graphical shell
ii gnome-shell-timer
0.3.12+20140924-3all GNOME Shell extension
providing a countdown timer in the top panel
$ dpkg --list | grep libgdk
ii libgdk-pixbuf2.0-0:amd64
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
ii libgdk-pixbuf2.0-0:i386
2.32.2-1ubuntu1.3i386 GDK Pixbuf library
ii libgdk-pixbuf2.0-common
2.32.2-1ubuntu1.3all GDK Pixbuf library -
data files
ii libgdk-pixbuf2.0-dev
2.32.2-1ubuntu1.3amd64GDK Pixbuf library
(development files)
}}}
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1580605
Title:
gnome-shell crashes often
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
I don't have full stacktrace right now unfortunately but gnome-shell
appears to be crashing a lot for me.
I am running it with multiple monitors and it crashes with following
errors:
[58566.199387] gnome-shell[11622]: segfault at e8 ip 7f577582c582
sp 7ffc
[Desktop-packages] [Bug 1637235] Re: xorg crashes on lock screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1637235 Title: xorg crashes on lock screen Status in lightdm package in Ubuntu: Confirmed Bug description: When I return from a locked screen, I get a the crash dialog "System program problem detected". The related file in /var/log crash shows this in the header lines: ProblemType: Crash Architecture: amd64 Date: Thu Oct 27 10:33:08 2016 DistroRelease: Ubuntu 16.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1473867446 ProcCmdline: /usr/lib/xorg/Xorg -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcCwd: / ProcEnviron: It appears that the xorg instance on vt8 is crashing while starting the lock process; the crash file in /var/crash appears just after locking the screen. I have attached the xorg log from the display that is crashing (Xorg.1.log). There is a related output in the main display log (Xorg.0.log): [ 10248.316] (II) AIGLX: Suspending AIGLX clients for VT switch [ 10248.350] (II) NOUVEAU(G0): NVLeaveVT is called. [ 10254.968] (II) AIGLX: Resuming AIGLX clients after VT switch [ 10254.968] (II) intel(0): switch to mode 1920x1080@60.0 on LVDS2 using pipe 0, position (0, 0), rotation normal, reflection none [ 10255.002] (II) NOUVEAU(G0): NVEnterVT is called. [ 10255.340] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found The screen locking appears to be working. VT7 is locked with a re- direct to VT8. I can log back in through VT8 and everything is normal, with the exception of the initial crash and subsequent crash dialog pop-up. Here is some relevant system information: Lenovo ThinkPad W520 Description:Ubuntu 16.04.1 LTS Release:16.04 lightdm: Installed: 1.18.3-0ubuntu1 xorg: Installed: 1:7.7+13ubuntu3 xserver-xorg-video-intel: Installed: 2:2.99.917+git20160325-1ubuntu1.1 xserver-xorg-video-nouveau: Installed: 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637235/+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 1725081] Re: Clipboard support broken in Ubuntu 17.10
Not sure whether this is the same issue. Since I moved to Ubuntu 17.10 I cannot copy and paste from gedit anymore. If I open gedit, write something, and then try to paste it in Firefox it does not work. When I try to paste, I get the following line in the stderr of gedit: (gedit:#): Gdk-WARNING **: Error writing selection data: Error writing to file descriptor: Broken pipe Copying and paste from and among other applications works just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1725081 Title: Clipboard support broken in Ubuntu 17.10 Status in mono package in Ubuntu: Confirmed Bug description: Mono apps can no longer modify system clipboard. For example, KeePass 2.x (https://keepass.info/). It was working perfect in Ubuntu 17.04. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mono-complete 4.6.2.7+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 04:13:09 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: mono UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1725081/+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 1731910] Re: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x0000559ef762f960 ***
** Changed in: evolution-data-server Status: Unknown => Fix Released ** Changed in: evolution-data-server Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1731910 Title: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib /gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** Status in evolution-data-server: Fix Released Status in evolution-data-server package in Ubuntu: Fix Committed Bug description: no idea how to reproduce. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.1-0ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 AssertionMessage: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 10:13:10 2017 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-calendar-server InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-calendar-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f6c814714e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7f6c8146de6e "free(): invalid pointer", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7f6c816a3c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 e_cal_component_free_datetime () at /usr/lib/x86_64-linux-gnu/libecal-1.2.so.19 Title: gnome-shell-calendar-server assert failure: *** Error in `/usr/lib/gnome-shell/gnome-shell-calendar-server': free(): invalid pointer: 0x559ef762f960 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1731910/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
I'm on kubuntu 17.04 with pulseaudio 10.0, I'm still having this issue. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1732241] [NEW] graphic card driver
Public bug reported: issue in starting lubuntu 17.10 it seems like a screen problem but i think its a driver issue since itried aditional driver tool but its not aorking and thanks. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 14 17:44:48 2017 InstallationDate: Installed on 2017-11-13 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 -- 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/1732241 Title: graphic card driver Status in xorg package in Ubuntu: New Bug description: issue in starting lubuntu 17.10 it seems like a screen problem but i think its a driver issue since itried aditional driver tool but its not aorking and thanks. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: i386 CurrentDesktop: LXDE Date: Tue Nov 14 17:44:48 2017 InstallationDate: Installed on 2017-11-13 (0 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732241/+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 1732253] [NEW] Firefox 58 doesn't start the second time: entity is not defined
Public bug reported: This is a transfer of https://bugzilla.mozilla.org/show_bug.cgi?id=1416851, reported on the wrong platform. I'm on linux mint, so ubuntu-bug didn't work, and I didn't find how to use apport correctly. Since yesterday, I updated my firefox package but without luck. Steps to reproduce: OS: Linux mint 18.1 cinnamon 64 bits Installed firefox from PPA: (from my apt sources lists:) deb http://ppa.launchpad.net/ubuntu-mozilla-daily/firefox-aurora/ubuntu xenial main deb-src http://ppa.launchpad.net/ubuntu-mozilla-daily/firefox-aurora/ubuntu xenial main Firefox version 58.0~b3+build2-0ubuntu0.16.04.1 Steps I've done: -Launched firefox -Enjoyed it -Close it -Launch firefox again later, (after a reboot for example) -See the awful message -Tried -safe-mode without luck -Downgrade to 56 -Firefox is starting again -Upgrade again -First run is ok, second is broken. Actual results: See the attached screenshot. For non-french speakers, here is my translation: XML analysis error : Entity is not defined Location : chrome://browser/content/browser.xul Line 381, Column 7 https://bugs.launchpad.net/bugs/1732253/+attachment/5009035/+files/startup_screenshot.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1732253 Title: Firefox 58 doesn't start the second time: entity is not defined Status in firefox package in Ubuntu: New Bug description: This is a transfer of https://bugzilla.mozilla.org/show_bug.cgi?id=1416851, reported on the wrong platform. I'm on linux mint, so ubuntu-bug didn't work, and I didn't find how to use apport correctly. Since yesterday, I updated my firefox package but without luck. Steps to reproduce: OS: Linux mint 18.1 cinnamon 64 bits Installed firefox from PPA: (from my apt sources lists:) deb http://ppa.launchpad.net/ubuntu-mozilla-daily/firefox-aurora/ubuntu xenial main deb-src http://ppa.launchpad.net/ubuntu-mozilla-daily/firefox-aurora/ubuntu xenial main Firefox version 58.0~b3+build2-0ubuntu0.16.04.1 Steps I've done: -Launched firefox -Enjoyed it -Close it -Launch firefox again later, (after a reboot for example) -See the awful message -Tried -safe-mode without luck -Downgrade to 56 -Firefox is starting again -Upgrade again -First run is ok, second is broken. Actual results: See the attached screenshot. For non-french speakers, here is my translation: XML analysis error : Entity is not defined Location : chrome://browser/content/browser.xul Line 381, Column 7 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1732253/+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 1648183] Re: Crackling and popping sound when using headphones
Same problem with HP Pavilion Power 15-cb. Kernel 4.10.0-38-generic. Although @robertjjoynt workaround WORKED for me also, I think this issue should be fixed from it's root... -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
Suggest increasing the importance of this bug, considering it has a CVE assignment? I realize that it's a DoS, which is low on the "vulnerability" totem pole; but especially with buffer overruns I tend to suspect that "DoS" is code for "might allow code execution but no one's bothered to prove it". Anyway, the fix is trivial, and provided in the attached debdiff. Cheers! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Confirmed Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Confirmed Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 40872] Re: Desktop icons are allowed to overlap
** Changed in: desktop Status: New => Confirmed -- 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/40872 Title: Desktop icons are allowed to overlap Status in Desktop: Confirmed Status in One Hundred Papercuts: Invalid Status in Nautilus: Confirmed Status in nautilus-elementary: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: I have some icons with long file names. Sometimes I unintentionally end up with completely illegible icon labels and overlapping icons. I have created a snapshot of my intentionally horrific example. This problem is easy to reproduce when working with file previews (irregularly shaped images) and icons with long file names. Just create some and drag them close together, paying attention to not trigger the a file move event. I have noticed what I consider to be a related problem. When I remove a file from my desktop or a new icon is added as a result of some program adding an entry, the desktop isn't refreshed with autoarranged icons. I have looked and looked and can find no way to make this my desktop's behavior. I think this is terrible UI from a usability standpoint. I will attach the image showing the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/desktop/+bug/40872/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
I've supplied a debdiff to address the fix for this CVE, based on upstream Debian's fix. ** Patch added: "Debdiff, adapted from Debian 1:1.3.1-11" https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+attachment/5009069/+files/libjpeg-turbo.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Confirmed Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Confirmed Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
The attachment "Debdiff, adapted from Debian 1:1.3.1-11" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Confirmed Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Confirmed Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu
I see this from time to time, according to no apparent pattern. I will just suddenly hear my laptop fan come on, and from running `top` will see `gnome-keyring-daemon` consuming 60–80% CPU, along with some CPU from `chromium-browser`. The problem seems to go away on its own after a while. Disabling keyring integration in Chromium is not a viable workaround for me; this feature was in fact a “key” reason I switched from Firefox. Currently running Xubuntu 17.10 with all updates. I have 800+ passwords in the store acc. to `secret-tool search --all scheme 0 2>&1 | fgrep label | wc -l`, not synched with a Google account. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1174162 Title: chrome-browser makes gnome-keyring-daemon use 100% cpu Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Bug description: After upgrading to 13.04, when starting the chromium browser, the gnome-keyring-daemon runs at full CPU load and the chromium-browser has no access to the stored passwords. The issue seems to be known (https://code.google.com/p/chromium/issues/detail?id=98601). I'm personally a bit surprised that Ubuntu 13.04 was released with such a serious problem. The frequently proposed workaround (e.g. https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4) doesn't work because (a) there is no .gnome2/keyrings any more and (b) it's rather inresponsible to store your passwords unencryted. I found that killing gnome-keyring-server several times eventually gives you a working system. --- ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mnl 18759 F pulseaudio CRDA: country DE: (2400 - 2483 @ 40), (N/A, 20) (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), DFS DistroRelease: Ubuntu 13.04 HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140 InstallationDate: Installed on 2010-11-10 (900 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD) MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-19-generic N/A linux-backports-modules-3.8.0-19-generic N/A linux-firmware1.106 Tags: raring Uname: Linux 3.8.0-19-generic i686 UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice wireshark WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP] dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PDD Ver. F.20 dmi.board.name: 30DD dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.23 dmi.chassis.asset.tag: CNU9326SJY dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6730b (GB990EA#ABD) dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1732270] [NEW] this computer is very unresponsive
Public bug reported: Takes a long time to load on various sites. Sometimes the commands do not work ! Navigation response is very spotty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 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 Nov 14 15:17:11 2017 DistUpgraded: 2017-01-26 19:38:06,653 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01f2] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01f2] InstallationDate: Installed on 2013-10-06 (1499 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MachineType: Dell Inc. Inspiron 1720 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=380418a6-87fb-4c43-b576-c68c8e1df6bb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-01-27 (291 days ago) dmi.bios.date: 07/11/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0UK439 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn0UK439:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1720 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 14 10:04:19 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor LPL xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 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/1732270 Title: this computer is very unresponsive Status in xorg package in Ubuntu: New Bug description: Takes a long time to load on various sites. Sometimes the commands do not work ! Navigation response is very spotty. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 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 Nov 14 15:17:11 2017 DistUpgraded: 2017-01-26 19:38:06,653 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01f2] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01f2] InstallationDate: Installed on 2013-10-06 (1499 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MachineType: Dell Inc. Inspiron 1720 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=380418a6-87fb-4c43-b576-c68c8e1df6bb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded
[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()
Thank you for this, José. My machines that were crashing had the evolution-indicator package installed, and the one that never crashed did not. Hopefully, removing that package solves the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1725315 Title: evolution crashed with SIGSEGV in g_hash_table_lookup_node() Status in evolution package in Ubuntu: Confirmed Bug description: Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release. Apport crashdump analysis attached. Looking at /var/log/syslog after one of these crashes, I see the following entries: Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 7ffee4f96718 error 14 in evolution[557e54c52000+7000] It is not clear that the first few syslog entries are related. Running evolution with debugging enabled: CAMEL_DEBUG=all evolution I see the following output when the crash occurs: ### message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk" (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important" (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo" (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))--- message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1 Segmentation fault (core dumped) Not sure if I can provide further information. This crash is highly- repeatable, happening hundreds of times/day. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 09:50:57 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2017-05-31 (142 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: evolution -c current ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so org_gnome_mail_new_notify () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so Title: evolution crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: Upgraded to artful on 2017-10
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released ** Also affects: network-manager (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Xenial) Status: New => Triaged ** Changed in: network-manager (Ubuntu Xenial) Importance: Undecided => Low -- 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/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Triaged Bug description: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.5 dev eth0 proto static metric 100 192.168.0.0/24 dev eth0 proto kernel scope link s
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Description changed: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). - - The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: - default via 192.168.0.5 dev eth0 proto static metric 100 - 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 - 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 + default via 192.168.0.5 dev eth0 proto static metric 100 + 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 + 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 IwConfig: - lono wireless extensions. - - eth1 no wireless extensions. - - eth0 no wireless extensions. + lono wireless extensions. + + eth1 no wireless extensions. + + eth0 no wireless extensions. NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEn
[Desktop-packages] [Bug 41301] ❣Re: omg some new stuff
Hey friend, Don't miss up this new stuff, you are going to be delighted, learning much more here http://www.x-met.ch/curious.php?UE80MTMwMUBidWdzLmxhdW5jaHBhZC5uZXQ- Yours faithfully, Nina Wesley -- 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/41301 Title: PS/2 Logitech MX310 clicks stop working sporadically Status in X.Org X server: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in Debian: Invalid Bug description: This bug is a long standing one for me in Dapper but it becomes more and more frequent in recent Dapper beta. Unfortunatly, there's no way I can reproduce it. Symptoms : the mouse buttons (all of them) stop working without any reason. Seems to happen mainly when surfing with Epiphany but not only. In fact, it's just like my mouse was in another dimension. I use "focus follow pointer" and it doesn't work anymore. I can see my cursor and moving it : the system just ignore it. No more click, no more focus following pointer. Also, the keyboard keeps working perfectly. By using shortcut keys, I can continue working normally. The workaround to have the mouse again is hopefully very simple : use the change desktop shortcut. The alt-tab shortcut is also working. Yes, it's strange, but they are the only two shortcuts I've found that bypass this bug ! Strange isn't it ? My mouse is a PS/2 Logitech MX310. The workaround seems to be the proof that it's not an hardware failure. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/41301/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
Precise EOL as per: https://wiki.ubuntu.com/Releases ** Changed in: libjpeg-turbo (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Won't Fix Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Won't Fix Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
Vivid EOL as per: https://wiki.ubuntu.com/Releases ** Changed in: libjpeg-turbo (Ubuntu Vivid) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Won't Fix Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Won't Fix Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1720820] Re: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics
I just got hit by this bug completely randomly. I did not wanted hardware acceleration, I just wanted to play some video and got black screen. It just happened that previously I had installed ubuntu- restricted-extras which automatically installs this vaapi thing. After I uninstalled ubuntu-restricted-extras i got my picture back. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1720820 Title: Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: WORKAROUNDS Just for totem: sudo apt remove gstreamer1.0-vaapi Or to workaround in all players: sudo apt remove mesa-va-drivers ORIGINAL DESCRIPTION Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Fix uploaded. ** Changed in: network-manager (Ubuntu Xenial) Status: Triaged => In Progress ** Description changed: I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 03:13:19 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 03:13:19 pampus dhclient[1532]: bound to 192.168.0.166 -- renewal in 2708 seconds. However, at 03:21:07 (exactly 2 hours and 1 second after the last lease reported by NetworkManager) Avahi and NTP report that the IP address is gone: jun 07 03:21:07 pampus avahi-daemon[1167]: Withdrawing address record for 192.168.0.166 on eth0. jun 07 03:21:07 pampus avahi-daemon[1167]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.166. jun 07 03:21:07 pampus avahi-daemon[1167]: Interface eth0.IPv4 no longer relevant for mDNS. jun 07 03:21:08 pampus ntpd[18832]: Deleting interface #3 eth0, 192.168.0.166#123, interface stats: received=2512, sent=2549, dropped=0, active_time=111819 secs So I suspect NetworkManager dropped the IP address from the interface, because it wasn't informed by dhclient that the lease was renewed. The logs don't explicitly say this, so I may have to turn on more verbose debugging logs in NetworkManager or dhclient to verify this. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 7 14:48:59 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-04 (214 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) IpRoute: default via 192.168.0.5 dev eth0 proto static metric 100 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.166 metric 100 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH
[Desktop-packages] [Bug 1707352] Update Released
The verification of the Stable Release Update for sane-backends has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Released Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1567250] Re: ssh signin problem since OTA-10
** Changed in: gnome-keyring (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) ** Changed in: indicator-network (Ubuntu) Assignee: Pete Woods (pete-woods) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1567250 Title: ssh signin problem since OTA-10 Status in Canonical System Image: Confirmed Status in Ubuntu Terminal App: Incomplete Status in gnome-keyring package in Ubuntu: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in openssh package in Ubuntu: Invalid Bug description: Not sure if this is a terminal or image issue, but here goes. Since the update last night to OTA-10 I cannot ssh to a server anymore. Error message: "Agent Admitted Failure To Sign Using The Key" On server side and client side nothing changed to the user settings or keys. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
This bug was fixed in the package sane-backends - 1.0.27-1~experimental2ubuntu2.1 --- sane-backends (1.0.27-1~experimental2ubuntu2.1) artful; urgency=medium * Add version to Provides. Use Conflicts instead of Breaks (LP: #1707352) sane-backends (1.0.27-1~experimental2ubuntu2) artful; urgency=medium * Add "Provides: libsane" to libsane1 (LP: #1707352) -- Jeremy Bicha Tue, 24 Oct 2017 21:43:06 -0400 ** Changed in: sane-backends (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Artful: Fix Released Status in sane-backends package in Debian: New Bug description: Note to SRU Team The first proposed fix (1.0.27-1~experimental2ubuntu2) failed because it needed to be a versioned Provides, not just a Provides. Impact == 1) The Debian maintainer renamed libsane to libsane1-experimental "to match with the soname". This apparently fixes a Lintian warning, but makes installing 3rd-party plug-ins hard, as they typically depend on "libsane", not on "libsane1". The first try to add a "Provides: libsane" to libsane1 (which created a virtual package) didn't make drivers installable that claim to depend on a minimum version of libsane as virtual packages are ignored in this case. 2) The soname change might be justified by the new version breaking (several? most?) 3rd party plug-ins even if the library version number doesn't indicate any bigger change than any ordinary new version of the library - which might indicate that this phenomenon might be an upstream bug. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 It is to note that depending on the manufacturer for many old scanners there won't be new versions of the plug-ins that are recompiled like this. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. Impossibility of workarounds Just installing an old version of libsane is impossible as it uninstalls libgtk (which depends on libsane1 which conflicts with libsane) making the system basically useless. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: indicator-network (Ubuntu) Status: Incomplete => Invalid -- 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/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in Canonical System Image: Fix Released Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Fix Released Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+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 1722151] Re: Incorrect syntax when writing to ~/.pam_environment
This bug was fixed in the package language-selector - 0.180.1 --- language-selector (0.180.1) artful-proposed; urgency=medium * LanguageSelector/LocaleInfo.py: Adapt to changed syntax in ~/.pam_environment (LP: #1722151). -- Gunnar Hjalmarsson Fri, 27 Oct 2017 19:43:00 +0200 ** Changed in: language-selector (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1722151 Title: Incorrect syntax when writing to ~/.pam_environment Status in accountsservice package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in accountsservice source package in Artful: Fix Committed Status in language-selector source package in Artful: Fix Released Bug description: [Impact] When the syntax for the entries in ~/.pam_environment was changed, the GUI in language-selector-gnome for maintaining the language priority list was broken since language-selector-gnome reads from ~/.pam_environment. The language-selector upload to artful makes language-selector-gnome handle both the old and the new syntax correctly. An additional similar change to accountsservice (the update-langlist script) is needed; hence also an accountsservice upload to artful. [Test Case] * Log in to an "Ubuntu on Xorg" session. * Open Language Support and find that it appears as if you can only set one item before the "English" item in the language list. With the new version, it works as expected again. [Regression Potential] Low. This is necessary to fix the regression caused by the change in accountsservice. [Original description] While investigating bug #1662031, I found out that /usr/share /language-tools/save-to-pam-env writes to ~/.pam_environment using an incorrect syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: accountsservice 0.6.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 06:57:17 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (463 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: accountsservice UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1722151] Update Released
The verification of the Stable Release Update for language-selector has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1722151 Title: Incorrect syntax when writing to ~/.pam_environment Status in accountsservice package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in accountsservice source package in Artful: Fix Committed Status in language-selector source package in Artful: Fix Released Bug description: [Impact] When the syntax for the entries in ~/.pam_environment was changed, the GUI in language-selector-gnome for maintaining the language priority list was broken since language-selector-gnome reads from ~/.pam_environment. The language-selector upload to artful makes language-selector-gnome handle both the old and the new syntax correctly. An additional similar change to accountsservice (the update-langlist script) is needed; hence also an accountsservice upload to artful. [Test Case] * Log in to an "Ubuntu on Xorg" session. * Open Language Support and find that it appears as if you can only set one item before the "English" item in the language list. With the new version, it works as expected again. [Regression Potential] Low. This is necessary to fix the regression caused by the change in accountsservice. [Original description] While investigating bug #1662031, I found out that /usr/share /language-tools/save-to-pam-env writes to ~/.pam_environment using an incorrect syntax: "VARIABLE=value" on each line. The expected syntax is "VARIABLE [DEFAULT=[value]] [OVERRIDE=[value]]" (man pam_env.conf). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: accountsservice 0.6.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 9 06:57:17 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (463 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: accountsservice UpgradeStatus: Upgraded to artful on 2017-06-04 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1722151/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
** Description changed: - I've found an issue on some of our Xenial office machines, causing - NetworkManager to drop its IP address lease in some cases when it - shouldn't. I'm not sure if the actual bug is in NetworkManager or - perhaps dbus or dhclient, but I'll do my best to help to figure out - where it is. + SRU REQUEST: + + Debdiff (nm-dhcp-helper.debdiff) attached. + + Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug + was fixed upstream in 1.4. + + [Impact] + + * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP + lease renewal due to a DBus race condition. + + * Upstream NetworkManager 1.4 fixes the race condition by changing + nm-dhcp-helper's DBus notification from signal "Event" to method + "Notify". + + * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's + NM 1.2.x. + + [Test Case] + + * Not reliably reproducible. Out of hundreds of machines, only a + dozen or so fail to notify NetworkManager of a DHCP lease + renewal about 30-50% of the time. (i.e. It's always the same + handful of machines that fail.) + + * All such machines with the patched packages have been fine for weeks, + over many dozens of lease renewals. + + [Regression Potential] + + * The patch changes both nm-dhcp-helper and NetworkManager itself. As + soon as the new packages are unpacked, the new nm-dhcp-helper will be + used on DHCP lease renewals, with the new Notify mechanism. Since the + running, old NetworkManager is still expecting Event notifications, the + patched nm-dhcp-helper has fallback capability to Event. + + * Once NetworkManager is restarted and is running the patched version, + it will have the new Notify support. + + [Other Info] + + * Upstream bug w/ patch: + https://bugzilla.gnome.org/show_bug.cgi?id=784636 + + * RHEL bug with links to the 1.4 commits from which the patch was + derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 + + * NOTE: The final comment on the upstream GNOME bug claims that the + fix is incomplete. However, it is possible that the running + NetworkManager was not restarted (see Regression Potential notes above), + which is why nm-dhcp-helper is falling back to Event. The remainder of + the log messages in that final comment are from a custom wrapper the + submitter was running around nm-dhcp-helper. I have deployed the exact + same patch (without said wrapper) to real-world systems and tested + extensively, and see nothing but successful DHCP lease renewal + notifications using D-Bus Notify, not D-Bus Event. + + + + I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.4' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] domain name 'office.screenpointmed.com' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9531] dhcp4 (eth0): state changed bound -> bound After this, dhclient is supposed to keep the lease fresh, which it does. E.g. at 03:13:19 you can see a DHCPREQUEST and DHCPACK; I've seen this DHCPACK in a tcpdump and it contains a new lease time of 7200 seconds. jun 07 03:13:19 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Hi Ray/Julian, > * NOTE: The final comment on the upstream GNOME bug claims that the fix > is incomplete. However, it is possible that the running NetworkManager was > not restarted (see Regression Potential notes above), which is why > nm-dhcp-helper is falling back to Event. This is not the case. Even today, one of the machines is showing the message from the wrapper that indicates the DHCP lease was not correctly applied according to the journal: ➜ sjors@cuba ~ cat /tmp/nm-helper-retries.log Tue Nov 14 07:23:07 CET 2017: needed 5 attempts to update NetworkManager (RENEW). Tue Nov 14 09:17:45 CET 2017: needed 5 attempts to update NetworkManager (RENEW). Tue Nov 14 10:06:58 CET 2017: needed 4 attempts to update NetworkManager (RENEW). This is even though the machine was rebooted yesterday, so the daemon was restarted: ➜ sjors@cuba ~ uptime 23:12:16 up 1 day, 14:04, 3 users, load average: 0,59, 0,49, 0,47 And the machine is using the patched version of the network-manager: ➜ sjors@cuba ~ apt-cache policy network-manager network-manager: Installed: 1.2.6-0ubuntu0.16.04.1screenpoint1 Candidate: 1.2.6-0ubuntu0.16.04.1screenpoint1 Version table: *** 1.2.6-0ubuntu0.16.04.1screenpoint1 100 100 /var/lib/dpkg/status 1.2.6-0ubuntu0.16.04.1 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages However, I have not investigated why this happens, as the wrapper script is an acceptable work-around. I'll report back, however, whether we still have this problem with the updated Xenial packages -- there is always a chance I made an error somewhere. -- 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/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: In Progress Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interfac
[Desktop-packages] [Bug 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed
Sjors: I'm interested to know how it goes for you with this update (either from the included debdiff, or from the packages when they hit -proposed.) We were seeing the exact same symptoms you were, and deep-dove into your backported fix from the GNOME bug and it all seems like it should fix the issue. We've tested extensively with your fix and the symptoms completely disappeared, even from the machines most frequently affected. -- 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/1696415 Title: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: In Progress Bug description: SRU REQUEST: Debdiff (nm-dhcp-helper.debdiff) attached. Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This bug was fixed upstream in 1.4. [Impact] * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP lease renewal due to a DBus race condition. * Upstream NetworkManager 1.4 fixes the race condition by changing nm-dhcp-helper's DBus notification from signal "Event" to method "Notify". * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix to NM 1.2. This SRU request applies that backported patch to Xenial's NM 1.2.x. [Test Case] * Not reliably reproducible. Out of hundreds of machines, only a dozen or so fail to notify NetworkManager of a DHCP lease renewal about 30-50% of the time. (i.e. It's always the same handful of machines that fail.) * All such machines with the patched packages have been fine for weeks, over many dozens of lease renewals. [Regression Potential] * The patch changes both nm-dhcp-helper and NetworkManager itself. As soon as the new packages are unpacked, the new nm-dhcp-helper will be used on DHCP lease renewals, with the new Notify mechanism. Since the running, old NetworkManager is still expecting Event notifications, the patched nm-dhcp-helper has fallback capability to Event. * Once NetworkManager is restarted and is running the patched version, it will have the new Notify support. [Other Info] * Upstream bug w/ patch: https://bugzilla.gnome.org/show_bug.cgi?id=784636 * RHEL bug with links to the 1.4 commits from which the patch was derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276 * NOTE: The final comment on the upstream GNOME bug claims that the fix is incomplete. However, it is possible that the running NetworkManager was not restarted (see Regression Potential notes above), which is why nm-dhcp-helper is falling back to Event. The remainder of the log messages in that final comment are from a custom wrapper the submitter was running around nm-dhcp-helper. I have deployed the exact same patch (without said wrapper) to real-world systems and tested extensively, and see nothing but successful DHCP lease renewal notifications using D-Bus Notify, not D-Bus Event. I've found an issue on some of our Xenial office machines, causing NetworkManager to drop its IP address lease in some cases when it shouldn't. I'm not sure if the actual bug is in NetworkManager or perhaps dbus or dhclient, but I'll do my best to help to figure out where it is. What appears to happen: * NetworkManager is informed of a new IPv4 lease. * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs regularly. * In spite of this, NetworkManager drops the IP address from the interface when the last reported lease time expires. This happens on various machines, once every few days. We are using a failover DHCP configuration using two machines (192.168.0.3 'bonaire' and 192.168.0.4 'curacao'). The machine where I've done the debugging is called 'pampus' (192.168.0.166). As you can see in the logs, at 01:21:06 NetworkManager reports a new lease with lease time 7200. jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 to 192.168.0.4 port 67 (xid=0x3295b440) jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] address 192.168.0.166 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] plen 24 (255.255.255.0) jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] gateway 192.168.0.5 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] server identifier 192.168.0.4 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] lease time 7200 jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.9530] nameserver '192.168.0.3' jun 07 01:21:06 pampus NetworkManager[1161]: [1496791266.
[Desktop-packages] [Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
I tried the SRU candidate and it worked for me. Thanks! -- 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/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in GNOME Software: Confirmed Status in gnome-software package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: New Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+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 1732300] [NEW] i don't know what this is
Public bug reported: This started whn i trid to in stall th application Discord ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Nov 14 15:38:00 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fc30] InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA Satellite P755 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=45d2d6e6-c951-4ca8-9bdd-4d8fbeb9f1c8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.80 dmi.board.asset.tag: NULL dmi.board.name: PEQAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.80:bd10/30/2012:svnTOSHIBA:pnSatelliteP755:pvrPSAY1U-02C027:rvnTOSHIBA:rnPEQAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite P755 dmi.product.version: PSAY1U-02C027 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.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Nov 14 15:05:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1732300 Title: i don't know what this is Status in xorg package in Ubuntu: New Bug description: This started whn i trid to in stall th application Discord ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Nov 14 15:38:00 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fc30] InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA Satellite P755 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=45d2d6e6-c951-4ca8-9bdd-4d8fbeb9f1c8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 2.80 dmi.board.asset.tag: NULL dmi.board.name: PEQAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr2.80:bd10/30/2012:svnTOSHIBA:pnSatelliteP755:pvrPSAY1U-02C0
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Maybe there are separate issues. Booting to a black screen after update happened on three of my machines (2 nvidia, 1 AMD). On all of them it was enough to remove the binary drivers, reboot and reinstall them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage
** Changed in: gnome-software Status: Confirmed => Unknown -- 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/1723362 Title: gnome-software spams error messages to journald and causes 100% CPU usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Triaged Status in snapd-glib package in Ubuntu: New Bug description: gnome-software spams this message to journald: Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-software 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 10:58:38 2017 InstallationDate: Installed on 2016-10-25 (352 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.1-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to artful on 2017-10-04 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1723362/+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 1732309] Re: the calendar crashed after i think i tried to open it
*** This bug is a duplicate of bug 1719273 *** https://bugs.launchpad.net/bugs/1719273 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 #1719273, 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/1732309/+attachment/5009118/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009120/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009123/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009124/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009125/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009126/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1732309/+attachment/5009127/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1719273 ** 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-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1732309 Title: the calendar crashed after i think i tried to open it Status in gnome-calendar package in Ubuntu: New Bug description: it crashed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-calendar 3.26.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: Budgie:GNOME Date: Tue Nov 14 20:25:16 2017 ExecutablePath: /usr/bin/gnome-calendar LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=C.UTF-8 SegvAnalysis: Segfault happened at: 0x5612f1d81f31 : mov0x18(%rdi),%rdi PC (0x5612f1d81f31) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gcal_manager_is_client_writable () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-calendar crashed with SIGSEGV in gcal_manager_is_client_writable() 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-calendar/+bug/1732309/+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 1726352] Re: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1726352 Title: gnome-shell crashed with SIGSEGV in meta_window_move_resize_request() Status in gnome-shell package in Ubuntu: Confirmed Bug description: Ordinary bug report in 17.10 ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 13:08:15 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['hidetop...@mathieu.bidon.ca', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']" b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Terminal.desktop', 'org.gnome.Nautilus.desktop', 'google-chrome.desktop', 'jetbrains-rubymine.desktop', 'jetbrains-webstorm.desktop', 'jetbrains-studio.desktop', 'keepass2.desktop', 'spotify.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7f8d82fc8c5c:mov0x18(%rax),%esi PC (0x7f8d82fc8c5c) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 meta_window_x11_configure_request () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726352/+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 1732322] [NEW] package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before
Public bug reported: I tried to update the environment by running the apt-get update command, it keeps giving me some error such as /var/lib/dpkg ... message. I've researched online as to resolving this issue, its all to no avail. I restarted the server and I saw so many crash messages and it suggested that I report the message. Please I need your help on this matter. Thanks Best regards, Kay Ade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-libc-dev: Install linux-libc-dev: Configure python3-jwt: Configure shotwell: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 14 01:30:15 2017 DuplicateSignature: package:shotwell:0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 Setting up linux-libc-dev:amd64 (4.4.0-98.121) ... dpkg: error processing package python3-jwt (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: shotwell Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1732322 Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in shotwell package in Ubuntu: New Bug description: I tried to update the environment by running the apt-get update command, it keeps giving me some error such as /var/lib/dpkg ... message. I've researched online as to resolving this issue, its all to no avail. I restarted the server and I saw so many crash messages and it suggested that I report the message. Please I need your help on this matter. Thanks Best regards, Kay Ade. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: linux-libc-dev: Install linux-libc-dev: Configure python3-jwt: Configure shotwell: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue Nov 14 01:30:15 2017 DuplicateSignature: package:shotwell:0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 Setting up linux-libc-dev:amd64 (4.4.0-98.121) ... dpkg: error processing package python3-jwt (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-11-14 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: shotwell Title: package shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1732322/+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 1705951] Re: Ubuntu 17.10 freezes soon after login.
Old NVIDIA G73 (GeForce 7600 GS) here. Fresh install. Freezes with Wayland and xorg using the nouveau driver, also seeing various flashing and other issues when using the recommended nvidia driver (+ freezes). Did not see any of these issues on 17.04 or earlier versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1705951 Title: Ubuntu 17.10 freezes soon after login. Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Edited 1: After some updates received, it freezes just after login, making any action impossible. I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 17.10 and have had many problems with crashes and freezes. After login, the normal screen appears, the screen flashes and the top bar disappears, flashes again and appears normal, but frozen. Clicking again blinks back to the login screen. In order to access the system I was forced to install GNOME Classic. I noticed that in ubuntu 17.04 and ubuntu GNOME 16.04 it works normal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.agp.gpu: Fast Writes: Supported SBA: Supported AGP Rates:8x 4x Registers:0xff000e1b:0x1f000302 .proc.driver.nvidia.agp.host-bridge: Host Bridge: PCI device 1106:0308 Fast Writes: Supported SBA: Supported AGP Rates:8x 4x Registers:0x1f000a1b:0x0b02 .proc.driver.nvidia.agp.status: Status: Enabled Driver: AGPGART AGP Rate: 8x Fast Writes: Disabled SBA: Enabled .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 18:13:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-17 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=7a3a72ab-cccf-4c14-97c3-1dcd85b1aca8 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/08/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5VDC-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 23 18:12:42 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputMicrosoft Basic Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBO
[Desktop-packages] [Bug 1717240] Re: libreoffice base not working properly, crashing.
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- 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/1717240 Title: libreoffice base not working properly, crashing. Status in libreoffice package in Ubuntu: Expired Bug description: 1. lsb_release -rd : Description: Zorin OS 12.2 Release: 12 1a. lsb_release -a : No LSB modules are available. Distributor ID: Zorin Description: Zorin OS 12.2 Release: 12 Codename: xenial 1b. uname -a : 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 i686 i686 i686 GNU/Linux 1c. cat /proc/version : Linux version 4.10.0-33-generic (buildd@lcy01-22) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 2. apt-cache policy libreoffice-base libreoffice-base: Instalat: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Candidează: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Tabela de versiuni: *** 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 500 500 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1:5.1.2-0ubuntu1 500 500 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 Packages apt-show-versions -r libreoffice-base : libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate apt-show-versions -r libreoffice* : libreoffice:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-avmedia-backend-gstreamer:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-calc:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-dmaths:all/xenial 3.5.4+dfsg1-1 uptodate libreoffice-draw:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gnome:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:i386 not installed libreoffice-gtk2:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk3:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-us:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-impress:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-java-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-za:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-ro:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-librelogo:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-math:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-mysql-connector:i386/xenial 1.0.2+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-nlpsolver:all/xenial 0.9+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-ogltrans:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:i386 not installed libreoffice-report-builder:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-report-builder-bin:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-bsh:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-js:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-python:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-hsqldb:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-postgresql:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-breeze:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-elementary:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-galaxy:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-hicontr
[Desktop-packages] [Bug 1717240] Re: libreoffice base not working properly, crashing.
Sorry for the lack of feedback. Are you still experiencing that crash? Is there a corresponding crash file under /var/crash ? If so, can you please attach it to this bug, and run: apport-collect 1717240 Thanks! ** Changed in: libreoffice (Ubuntu) Status: Expired => Incomplete -- 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/1717240 Title: libreoffice base not working properly, crashing. Status in libreoffice package in Ubuntu: Incomplete Bug description: 1. lsb_release -rd : Description: Zorin OS 12.2 Release: 12 1a. lsb_release -a : No LSB modules are available. Distributor ID: Zorin Description: Zorin OS 12.2 Release: 12 Codename: xenial 1b. uname -a : 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 i686 i686 i686 GNU/Linux 1c. cat /proc/version : Linux version 4.10.0-33-generic (buildd@lcy01-22) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #37~16.04.1-Ubuntu SMP Fri Aug 11 14:03:33 UTC 2017 2. apt-cache policy libreoffice-base libreoffice-base: Instalat: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Candidează: 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 Tabela de versiuni: *** 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 500 500 http://ppa.launchpad.net/libreoffice/libreoffice-5-4/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 1:5.1.6~rc2-0ubuntu1~xenial2 500 500 http://ro.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages 1:5.1.2-0ubuntu1 500 500 http://ro.archive.ubuntu.com/ubuntu xenial/main i386 Packages apt-show-versions -r libreoffice-base : libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate apt-show-versions -r libreoffice* : libreoffice:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-avmedia-backend-gstreamer:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-base-drivers:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-calc:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-core:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-dmaths:all/xenial 3.5.4+dfsg1-1 uptodate libreoffice-draw:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gnome:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk:i386 not installed libreoffice-gtk2:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-gtk3:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-help-en-us:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-impress:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-java-common:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-gb:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-en-za:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-l10n-ro:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-librelogo:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-math:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-mysql-connector:i386/xenial 1.0.2+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-nlpsolver:all/xenial 0.9+LibO5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-ogltrans:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-pdfimport:i386 not installed libreoffice-report-builder:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-report-builder-bin:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-bsh:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-js:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-script-provider-python:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-hsqldb:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-sdbc-postgresql:i386/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-breeze:all/xenial 1:5.4.1~rc2-0ubuntu0.16.04.1~lo0 uptodate libreoffice-style-elementary:all/xenial 1:5.4.1~rc2-
[Desktop-packages] [Bug 1732358] [NEW] failed to rescan
Public bug reported: On every boot of 17.10: Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-background-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-bluetooth-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-color-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-control-center.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-datetime-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-default-apps-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-display-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-info-overview-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-info-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-keyboard-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-mouse-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-network-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-notifications-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-online-accounts-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-power-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-printers-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-privacy-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-region-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-removable-media-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-search-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-sharing-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-sound-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-ubuntu-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-universal-access-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-user-accounts-panel.desktop file: cannot process file of type application/x-desktop Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse /usr/share/applications/gnome-wacom-panel.desktop file: cannot process file of type application/x-deskt
[Desktop-packages] [Bug 1732357] [NEW] g_strsplit: assertion 'string != NULL' failed
Public bug reported: Tons of the following in the log on 17.10: Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1732357 Title: g_strsplit: assertion 'string != NULL' failed Status in gnome-software package in Ubuntu: New Bug description: Tons of the following in the log on 17.10: Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 'str_array != NULL' failed Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 'member_name != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1732357/+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
