[Desktop-packages] [Bug 2038748] Re: Xorg freeze amdgpu mst powersaving
** Package changed: xorg (Ubuntu) => linux-signed-hwe-6.2 (Ubuntu) ** Summary changed: - Xorg freeze amdgpu mst powersaving + amdgpu mst power saving null ptr deref -- 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/2038748 Title: amdgpu mst power saving null ptr deref Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2038748/+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 2038748] [NEW] Xorg freeze amdgpu mst powersaving
Public bug reported: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy 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/2038748 Title: Xorg freeze amdgpu mst powersaving Status in xorg package in Ubuntu: New Bug description: Reoccurrence of amdgpu MST power saving related null pointer deref. Likely should be against kernel instead, but let's see whether ubuntu- bug attached sensible part of logs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Sun Oct 8 10:23:57 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (528 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC.
[Desktop-packages] [Bug 2036998] [NEW] Xorg freeze
Public bug reported: Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in random order. May have reported this earlier myself. Details to be filled later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Sep 21 20:20:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (512 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze jammy 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/2036998 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Amdgpu tends to freeze on resume with DP1.2 chained monitors waking up in random order. May have reported this earlier myself. Details to be filled later. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-31.31~22.04.1-generic 6.2.15 Uname: Linux 6.2.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Thu Sep 21 20:20:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (512 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag:
[Desktop-packages] [Bug 1870597] Re: libinput says "your system is too slow"
I have two laptops with Ubuntu 22.04 and only one laptop has random freezes with this syslog: Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (II) event6 - Logitech M705: SYN_DROPPED event - some input events have been lost. Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (EE) client bug: timer event6 debounce: scheduled expiry is in the past (-1246ms), your system is too slow Aug 29 15:20:23 pulse /usr/libexec/gdm-x-session[1287]: (EE) client bug: timer event6 debounce short: scheduled expiry is in the past (-1259ms), your system is too slow $ uname -a Linux pulse 6.2.0-31-generic #31~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Once X got frozen permanently and I had to login via SSH to restart the X system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Fix Released Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1870597/+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 1969999] [NEW] Looping music without no gui
Public bug reported: rhythmbox 3.4.2 loop music without no gui. OS Ubuntu 18.04 LTS. 5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux rhytmbox version is 3.4.4 When you click playlist. Play song. Close the program in window x button. (From the x button right at the top. It's kill ui, but not stop music. Now is is looping your playlist. There is no icon for unhide the program. When you open program again and press play. You have seconds song playing. But you cannot stop first one. You can only kill app for find top command rhythmbox id, but i cannot find task manager any rhythmbox apps. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Looping music without no gui Status in rhythmbox package in Ubuntu: New Bug description: rhythmbox 3.4.2 loop music without no gui. OS Ubuntu 18.04 LTS. 5.4.0-109-generic #123~18.04.1-Ubuntu SMP Fri Apr 8 09:48:52 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux rhytmbox version is 3.4.4 When you click playlist. Play song. Close the program in window x button. (From the x button right at the top. It's kill ui, but not stop music. Now is is looping your playlist. There is no icon for unhide the program. When you open program again and press play. You have seconds song playing. But you cannot stop first one. You can only kill app for find top command rhythmbox id, but i cannot find task manager any rhythmbox apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/196/+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 1767542] Re: Turning off WiFi enables Airplane mode
Same issue in home desktop computer. Wifi not turn on. I have to restart wifi-dongle and computer. Ubuntu 18.04 LTS. I dont find any options in turned to off. Settings are same. -- 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/1767542 Title: Turning off WiFi enables Airplane mode Status in gnome-control-center: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Bug description: Turning off the WiFi from the top right control enables Airplane mode (see screenshots). Also after turning off airplane mode, the Wi-Fi is not turned back on, rather the Bluetooth is. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 17:46:34 2018 InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1767542/+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 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Exact reproduction conditions of bug #1891636 and bug #1891745 unknown. At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to errors.ubuntu.com now, marking these two as duplicates for now. ** This bug has been marked a duplicate of bug 1861609 [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper ** Information type changed from Public to Private -- 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/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings Status in xorg-server package in Ubuntu: New Bug description: AssertionMessage Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+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 1891745] Re: Xorg crashed with SIGSEGV in dixSaveScreens()
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Exact reproduction conditions of bug #1891636 and bug #1891745 unknown. At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to errors.ubuntu.com now, marking these two as duplicates for now. ** This bug has been marked a duplicate of bug 1891636 After recent updates Xorg crashes whenever entering Display Settings ** Information type changed from Public to Private ** This bug is no longer a duplicate of bug 1891636 After recent updates Xorg crashes whenever entering Display Settings ** This bug has been marked a duplicate of bug 1861609 [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- 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/1891745 Title: Xorg crashed with SIGSEGV in dixSaveScreens() Status in xorg package in Ubuntu: New Bug description: This instance happened after lockscreen, as such may be suspend-resume related. On the other hand at least 0 and 10 parts on backtrace appear similar to bug #1891636 While this appears to be a recent regression, DpkgLog.txt doesn't contain xorg references. Could it be related to kernel upgrades then, or just happened to slip by undetected after earlier upgrades? [ 81555.574] (EE) Backtrace: [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x560d53a2ee0c] [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fb62037b41f] [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb524a0] [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb52750] [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb4bb00] [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb4bba0] [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) [0x560d538fceb6] [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) [0x560d53a0e779] [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) [0x560d5390b65d] [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) [0x560d538cdeb9] [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4] [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fb6201990b3] [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e] [ 81555.581] (EE) [ 81555.581] (EE) Segmentation fault at address 0x0 [ 81555.581] (EE) Fatal server error: [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 81555.581] (EE) [ 81555.581] (EE) P.S. Don't currently have a remote debugging setup since all the other hosts nearby are headless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 13:17:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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:
[Desktop-packages] [Bug 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
** Tags added: regression-update -- 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/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings Status in xorg-server package in Ubuntu: New Bug description: AssertionMessage Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1891636/+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 1891636] Re: After recent updates Xorg crashes whenever entering Display Settings
No longer reproducible by visiting display settings after bug #1891745 crash. Possibly a duplicate of bug #1861609. ** Description changed: - AssertionMessage Xort: ../../../../../../include/privates.h:121: + AssertionMessage Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) -Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] + Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) + Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings Status in xorg-server package in Ubuntu: New Bug description: AssertionMessage Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet
[Desktop-packages] [Bug 1891745] [NEW] Xorg crashed with SIGSEGV in dixSaveScreens()
Public bug reported: This instance happened after lockscreen, as such may be suspend-resume related. On the other hand at least 0 and 10 parts on backtrace appear similar to bug #1891636 While this appears to be a recent regression, DpkgLog.txt doesn't contain xorg references. Could it be related to kernel upgrades then, or just happened to slip by undetected after earlier upgrades? [ 81555.574] (EE) Backtrace: [ 81555.577] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x560d53a2ee0c] [ 81555.578] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fb62037b41f] [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.578] (EE) 2: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb524a0] [ 81555.578] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 3: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb52750] [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 4: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb4bb00] [ 81555.579] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 81555.579] (EE) 5: /usr/lib/xorg/modules/drivers/amdgpu_drv.so (?+0x0) [0x7fb61fb4bba0] [ 81555.579] (EE) 6: /usr/lib/xorg/Xorg (dixSaveScreens+0x1e6) [0x560d538fceb6] [ 81555.580] (EE) 7: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x149) [0x560d53a0e779] [ 81555.580] (EE) 8: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) [0x560d5390b65d] [ 81555.580] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x2c9) [0x560d538cdeb9] [ 81555.580] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x560d538d1fd4] [ 81555.580] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fb6201990b3] [ 81555.581] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x560d538bba3e] [ 81555.581] (EE) [ 81555.581] (EE) Segmentation fault at address 0x0 [ 81555.581] (EE) Fatal server error: [ 81555.581] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 81555.581] (EE) [ 81555.581] (EE) P.S. Don't currently have a remote debugging setup since all the other hosts nearby are headless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 15 13:17:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (126 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1891745 Title: Xorg crashed with SIGSEGV in dixSaveScreens() Status in
[Desktop-packages] [Bug 1891636] [NEW] After recent updates Xorg crashes whenever entering Display Settings
Public bug reported: AssertionMessage Xort: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1891636 Title: After recent updates Xorg crashes whenever entering Display Settings Status in xorg-server package in Ubuntu: New Bug description: AssertionMessage Xort: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key-initialized' failed. Also affected by apport bug #1891634 making filling more information here somewhat tedious. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 14 13:08:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2020-04-10 (125 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=2b9e2f7d-99b7-45f9-aabc-5ca23e66a7a2 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3
[Desktop-packages] [Bug 1871916] Re: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
Not reproducible on fresh install on same hardware. -- 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/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu Status in xorg package in Ubuntu: New Bug description: Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect x.org drivers for RX 5500 XT. Those drivers appear to be missing features like multi-monitor support. On the other hand live- usb of 20.04 beta did manage to utilize all 3 connected monitors (before crashing), so the issue may also be related to upgrading process (used do-release-upgrade since update-managed does not scale down to 800x600 fallback which 18.04 used with unsupported hardware). Yes, this report is in need of some triaging, unless it happens to be a clear duplicate of another bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 22:01:36 2020 DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-46-generic, x86_64: installed nvidia, 390.132, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2016-09-25 (1292 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) XorgConf: Section "Device" Identifier "AMD" Driver "amdgpu" EndSection dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Apr 9 04:46:16 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.7-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871916/+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 1871916] [NEW] Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
Public bug reported: Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect x.org drivers for RX 5500 XT. Those drivers appear to be missing features like multi-monitor support. On the other hand live-usb of 20.04 beta did manage to utilize all 3 connected monitors (before crashing), so the issue may also be related to upgrading process (used do-release- upgrade since update-managed does not scale down to 800x600 fallback which 18.04 used with unsupported hardware). Yes, this report is in need of some triaging, unless it happens to be a clear duplicate of another bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 22:01:36 2020 DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 390.132, 5.3.0-46-generic, x86_64: installed nvidia, 390.132, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2016-09-25 (1292 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=4ae0053b-f333-4800-b242-42a9efca3dde ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago) XorgConf: Section "Device" Identifier "AMD" Driver "amdgpu" EndSection dmi.bios.date: 07/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS 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.:bvr2106:bd07/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Thu Apr 9 04:46:16 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.7-2ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance 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/1871916 Title: Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu Status in xorg package in Ubuntu: New Bug description: Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect x.org drivers for RX 5500 XT. Those drivers appear to be missing features like multi-monitor support. On the other hand live- usb of 20.04 beta did manage to utilize all 3 connected monitors (before crashing), so the issue may also be related to upgrading process (used do-release-upgrade since update-managed does not scale down to 800x600 fallback which 18.04 used with unsupported hardware). Yes, this report is in need of some triaging, unless it happens to be a clear duplicate of another bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 22:01:36 2020 DistUpgraded: 2020-04-09 04:40:21,578 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename:
[Desktop-packages] [Bug 1798941] [NEW] back button does nothing
Public bug reported: Steps: 1. Open Ubuntu Software 2. Search for "Dropbox" 3. Install it 4. Launch it 5. Click back button < in the top left corner. Expecting it navigates back to search or main view, but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 11:00:16 2018 InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1798941 Title: back button does nothing Status in gnome-software package in Ubuntu: New Bug description: Steps: 1. Open Ubuntu Software 2. Search for "Dropbox" 3. Install it 4. Launch it 5. Click back button < in the top left corner. Expecting it navigates back to search or main view, but nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 11:00:16 2018 InstallationDate: Installed on 2018-10-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1798941/+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
Same happened also me. Updating system and intel-microcode is installed in AMD machine. Updating intel laptop and also AMD-microcode is installed in intel-laptop. Is there no amendment here? What processor is used. -- 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 1386257] Re: intel-microcode should be installed by default, when the CPU is GenuineIntel
im updating latest intel-microcode (sudo apt-get update && sudo apt-get upgrade -y) and it is also automatically install also amd-microcode in my laptop. Why? my laptop not use amd-microcode. it is use only intel. Why it install it when updating my laptop. Is this a bug or what? -- 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 1759542] [NEW] package libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/
Public bug reported: apt dist-upgrade failed ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libgtk2.0-0:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 28 13:47:06 2018 DpkgTerminalLog: Preparing to unpack .../libgtk2.0-0_2.24.31-2ubuntu1_i386.deb ... Unpacking libgtk2.0-0:i386 (2.24.31-2ubuntu1) over (2.24.31-1ubuntu1.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libgtk2.0-0_2.24.31-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 InstallationDate: Installed on 2017-10-19 (159 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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.1 SourcePackage: gtk+2.0 Title: package libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- 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/1759542 Title: package libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 Status in gtk+2.0 package in Ubuntu: New Bug description: apt dist-upgrade failed ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 AptOrdering: libgtk2.0-0:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Mar 28 13:47:06 2018 DpkgTerminalLog: Preparing to unpack .../libgtk2.0-0_2.24.31-2ubuntu1_i386.deb ... Unpacking libgtk2.0-0:i386 (2.24.31-2ubuntu1) over (2.24.31-1ubuntu1.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libgtk2.0-0_2.24.31-2ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 InstallationDate: Installed on 2017-10-19 (159 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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.1 SourcePackage: gtk+2.0 Title: package libgtk2.0-0 2.24.31-2ubuntu1 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1759542/+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 1676423] Re: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1
upgrading packages and get this error. sudo apt upgrade -f I did it and the upgrade seemed to go ok. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1676423 Title: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1 Status in cups package in Ubuntu: Confirmed Bug description: I had reinstalled ubuntu 16.04 and everything seemed to go ok but after installing I updated and upgraded via terminal, and there it gave this cups-daemon*-error and suggested to use sudo apt upgrade -f I did it and the upgrade seemed to go ok, sorry I dont know if this is a real bug.. Also out of the current question I want to tell that ubuntu software-center(this orange icon with letter A on the left panel) did not open, I removed the gnome-software via synaptic and reinstalled it and now when you click this button search from computer, you can find this white looking like shopping bag with text "ohjelmistot" I think it is softwares in english (I have finnish ubuntu version),anyway that was the software-center and it works ok but it did not go to the left panel like it used to. Description: Ubuntu 16.04.2 LTS Release: 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Mon Mar 27 13:54:41 2017 ErrorMessage: aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1 InstallationDate: Installed on 2017-03-27 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS (Finnish Remix) "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: FUJITSU PRIMERGY TX100 S1 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=c8011005-3f48-4f37-bf7a-4fbbdd73b8cc ro quiet splash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=c8011005-3f48-4f37-bf7a-4fbbdd73b8cc ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.2 failed to install/upgrade: aliprosessi uusi pre-removal-komentosarja palautti virhetilakoodin 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2009 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.04.2679.B1 dmi.board.name: D2679-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D2679-Bxx WGSxx GSxx dmi.chassis.type: 6 dmi.chassis.vendor: FUJITSU dmi.chassis.version: TX100S1F dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.04.2679.B1:bd08/24/2009:svnFUJITSU:pnPRIMERGYTX100S1:pvr:rvnFUJITSU:rnD2679-B1:rvrS26361-D2679-BxxWGSxxGSxx:cvnFUJITSU:ct6:cvrTX100S1F: dmi.product.name: PRIMERGY TX100 S1 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676423/+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 738063] Re: gnome-keyring-daemon assertion failures when changing password remotely
Reproduced on trusty (using just the test124 part of reproduction instructions above): Aug 22 13:08:23 gx1 sshd[11844]: pam_unix(sshd:session): session opened for user test124 by (uid=0) Aug 22 13:08:23 gx1 systemd-logind[1275]: New session 4 of user test124. Aug 22 13:09:22 gx1 passwd[11988]: pam_unix(passwd:chauthtok): password changed for test124 Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: Gck: gck_module_new: assertion 'funcs != NULL' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: module_instances: assertion 'module' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 'error' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't find secret store module: (unknown) Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: create_credential: assertion 'GCK_IS_SESSION (session)' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: egg_error_message: assertion 'error' failed Aug 22 13:09:22 gx1 gnome-keyring-daemon[11994]: couldn't create new login credential: (unknown) Aug 22 13:09:22 gx1 passwd[11988]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. Aug 22 13:09:22 gx1 passwd[11988]: pam_ecryptfs: Passphrase file wrapped Aug 22 13:09:23 gx1 passwd[11997]: Error attempting to open [/home/test124/.ecryptfs/wrapped-passphrase] for reading Aug 22 13:09:23 gx1 passwd[11997]: pam_ecryptfs: Error attempting to unwrap passphrase; rc = [-5] Version: 3.10.1-1ubuntu4.2 ** Tags added: trusty ** Changed in: gnome-keyring (Ubuntu) Status: Invalid = New -- 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/738063 Title: gnome-keyring-daemon assertion failures when changing password remotely Status in gnome-keyring package in Ubuntu: New Bug description: Binary package hint: gnome-keyring Changing password remotely results in the following assertion failures in auth.log: Mar 19 09:49:18 gx1 passwd[17883]: pam_unix(passwd:chauthtok): password changed for test123 Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: gp11_module_get_slots: assertion `data-funcs' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_session: assertion `slot' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: create_credential: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: egg_error_message: assertion `error' failed Mar 19 09:49:18 gx1 gnome-keyring-daemon[17886]: couldn't create new login credential: (unknown) Mar 19 09:49:18 gx1 passwd[17883]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. Mar 19 09:49:18 gx1 passwd[17883]: Passphrase file wrapped Mar 19 09:55:57 gx1 passwd[18305]: pam_unix(passwd:chauthtok): password changed for test124 Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: gp11_module_get_slots: assertion `data-funcs' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_session: assertion `slot' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: lookup_login_keyring: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: create_credential: assertion `GP11_IS_SESSION (session)' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: egg_error_message: assertion `error' failed Mar 19 09:55:57 gx1 gnome-keyring-daemon[18309]: couldn't create new login credential: (unknown) Mar 19 09:55:57 gx1 passwd[18305]: gkr-pam: couldn't change password for the login keyring: the passwords didn't match. Mar 19 09:55:57 gx1 passwd[18305]: Passphrase file wrapped To reproduce: sudo adduser --encrypt-home test123 sudo adduser test124 ssh in as both users created above, run passwd and change the password. Have not tested behaviour without ecryptfs-utils installed, but it should be unrelated since both encrypted and unencrypted homedirs behaved the same. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-generic i686 Architecture: i386 CheckboxSubmission: bc3a49cd6e76f0d54c8965120b490eef CheckboxSystem: abf102d6ef41328208f5c1554651535a Date: Sat Mar 19 09:51:57 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/738063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
all x86 dev packages are broken. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Invalid Status in mesa source package in Trusty: Fix Released Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (= 0.91.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (= 1.15.8) but it is not going to be installed Depends: libcogl15 (= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+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 1458184] Re: 9.10~dfsg-0ubuntu10.2 gs removes special chars when converting from pdf to jpeg
Sadly seems that I need to find another media to push this forward and to find out how to debug this more. Any hints from anyone? Who to talk, how to start myself to look for the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1458184 Title: 9.10~dfsg-0ubuntu10.2 gs removes special chars when converting from pdf to jpeg Status in ghostscript package in Ubuntu: New Bug description: (Creating a bug report as suggested here: https://answers.launchpad.net/ubuntu/+question/267233) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy ghostscript ghostscript: Installed: 9.10~dfsg-0ubuntu10.2 Candidate: 9.10~dfsg-0ubuntu10.2 Version table: *** 9.10~dfsg-0ubuntu10.2 0 500 http://fi.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 9.10~dfsg-0ubuntu10 0 500 http://fi.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages What you expected to happen: When I ran: gs -o output.jpg -dBATCH -dNOPAUSE -sDEVICE=jpeg input.pdf I expect to have output.jpg, which look like this: http://62.210.181.5/has_all_chars.jpg What happened instead: Instead I get output.jpg which looks like this: http://62.210.181.5/missing_special_chars.jpg (notice the missing special chars, forexample ä letters). So far this seems to happen only for Arial chars. Test input.pdf file can be found here: http://62.210.181.5/input.pdf If I download http://downloads.ghostscript.com/public/ghostscript-9.10.tar.gz, and do: tar xvf ghostscript-9.10.tar.gz cd ghostscript-9.10 ./configure make bin/gs -o output.jpg -dBATCH -dNOPAUSE -sDEVICE=jpeg input.pdf The output is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1458184/+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 1458184] Re: 9.10~dfsg-0ubuntu10.2 gs removes special chars when converting from pdf to jpeg
Adding package. ** Package changed: ubuntu = ghostscript (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1458184 Title: 9.10~dfsg-0ubuntu10.2 gs removes special chars when converting from pdf to jpeg Status in ghostscript package in Ubuntu: New Bug description: (Creating a bug report as suggested here: https://answers.launchpad.net/ubuntu/+question/267233) lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 apt-cache policy ghostscript ghostscript: Installed: 9.10~dfsg-0ubuntu10.2 Candidate: 9.10~dfsg-0ubuntu10.2 Version table: *** 9.10~dfsg-0ubuntu10.2 0 500 http://fi.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 9.10~dfsg-0ubuntu10 0 500 http://fi.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages What you expected to happen: When I ran: gs -o output.jpg -dBATCH -dNOPAUSE -sDEVICE=jpeg input.pdf I expect to have output.jpg, which look like this: http://62.210.181.5/has_all_chars.jpg What happened instead: Instead I get output.jpg which looks like this: http://62.210.181.5/missing_special_chars.jpg (notice the missing special chars, forexample ä letters). So far this seems to happen only for Arial chars. Test input.pdf file can be found here: http://62.210.181.5/input.pdf If I download http://downloads.ghostscript.com/public/ghostscript-9.10.tar.gz, and do: tar xvf ghostscript-9.10.tar.gz cd ghostscript-9.10 ./configure make bin/gs -o output.jpg -dBATCH -dNOPAUSE -sDEVICE=jpeg input.pdf The output is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1458184/+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 1360756] Re: The URI ‘help:ubuntu-help/index’ does not point to a valid page.
i have a same problem, and im filled also bug report. This is not yelp bug. This is quickly, pgtk bug. Maybe helpers.py file working wrong. I have same problems other programs when go to programs. Menu, contents F1, opening help file. English help working correctly but others language help not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1360756 Title: The URI ‘help:ubuntu-help/index’ does not point to a valid page. Status in yelp package in Ubuntu: Incomplete Bug description: after upgrading to 14.10 alpha 2 when i try to launch yelp from command or from menu it shows The URI ‘help:ubuntu-help/index’ does not point to a valid page. even when i try to search it shows the same ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.6-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Aug 24 11:53:45 2014 InstallationDate: Installed on 2012-03-24 (882 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) SourcePackage: yelp SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to utopic on 2014-08-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1360756/+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 1443978] Re: The document does not exist Location help: my-program does not control the right side.
** Tags added: pygtk ** Description changed: I made a litte program in Ubuntu quickly. And im find a bug in pygtk help system. The program does not find the correct language settings. my language is Finnish. (default) - 1. open program + 1. open program 2. press F1 to open Contens 3. Help is opening and say in Finnish. Asiakirjaa ei löydy Sijainti ”ghelp:my-program” ei ohjaa oikealle sivulle. - and same in english + and same in english The document does not exist Location help: my-program does not control the right side. i made help files in path myprogram/help/fi/ * index.page * preferences.page * topic.page if im choosing english language pack (this maybe is default path) myprogram/help/c/ Are there any instructions. I could not find anything. I assume that the path is as myprogram/help/fi/ + + Help show correct it when go to the menu and press F1 and click the + program menu show all help documents. + + But not working in program when im pressing F1 Contents. Gtk program not + find or select correct language. ** Package changed: pygtk (Ubuntu) = yelp ** Description changed: I made a litte program in Ubuntu quickly. And im find a bug in pygtk - help system. The program does not find the correct language settings. + yelp help system. The program does not find the correct language + settings. my language is Finnish. (default) 1. open program 2. press F1 to open Contens 3. Help is opening and say in Finnish. Asiakirjaa ei löydy Sijainti ”ghelp:my-program” ei ohjaa oikealle sivulle. and same in english The document does not exist Location help: my-program does not control the right side. i made help files in path myprogram/help/fi/ * index.page * preferences.page * topic.page if im choosing english language pack (this maybe is default path) myprogram/help/c/ Are there any instructions. I could not find anything. I assume that the path is as myprogram/help/fi/ Help show correct it when go to the menu and press F1 and click the program menu show all help documents. But not working in program when im pressing F1 Contents. Gtk program not find or select correct language. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1443978 Title: The document does not exist Location help: my-program does not control the right side. Status in The Yelp Help Browser for Gnome: New Bug description: I made a litte program in Ubuntu quickly. And im find a bug in pygtk yelp help system. The program does not find the correct language settings. my language is Finnish. (default) 1. open program 2. press F1 to open Contens 3. Help is opening and say in Finnish. Asiakirjaa ei löydy Sijainti ”ghelp:my-program” ei ohjaa oikealle sivulle. and same in english The document does not exist Location help: my-program does not control the right side. i made help files in path myprogram/help/fi/ * index.page * preferences.page * topic.page if im choosing english language pack (this maybe is default path) myprogram/help/c/ Are there any instructions. I could not find anything. I assume that the path is as myprogram/help/fi/ Help show correct it when go to the menu and press F1 and click the program menu show all help documents. But not working in program when im pressing F1 Contents. Gtk program not find or select correct language. To manage notifications about this bug go to: https://bugs.launchpad.net/yelp/+bug/1443978/+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 1443978] [NEW] The document does not exist Location help: my-program does not control the right side.
Public bug reported: I made a litte program in Ubuntu quickly. And im find a bug in pygtk help system. The program does not find the correct language settings. my language is Finnish. (default) 1. open program 2. press F1 to open Contens 3. Help is opening and say in Finnish. Asiakirjaa ei löydy Sijainti ”ghelp:my-program” ei ohjaa oikealle sivulle. and same in english The document does not exist Location help: my-program does not control the right side. i made help files in path myprogram/help/fi/ * index.page * preferences.page * topic.page if im choosing english language pack (this maybe is default path) myprogram/help/c/ Are there any instructions. I could not find anything. I assume that the path is as myprogram/help/fi/ ** Affects: pygtk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1443978 Title: The document does not exist Location help: my-program does not control the right side. Status in pygtk package in Ubuntu: New Bug description: I made a litte program in Ubuntu quickly. And im find a bug in pygtk help system. The program does not find the correct language settings. my language is Finnish. (default) 1. open program 2. press F1 to open Contens 3. Help is opening and say in Finnish. Asiakirjaa ei löydy Sijainti ”ghelp:my-program” ei ohjaa oikealle sivulle. and same in english The document does not exist Location help: my-program does not control the right side. i made help files in path myprogram/help/fi/ * index.page * preferences.page * topic.page if im choosing english language pack (this maybe is default path) myprogram/help/c/ Are there any instructions. I could not find anything. I assume that the path is as myprogram/help/fi/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1443978/+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 1295247] Re: Cheese says There was an error playing video from webcam
Same behaior in 64bit trusty. uname -a Linux GameComputer 3.13.0-46-generic #79-Ubuntu SMP Tue Mar 10 20:06:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: gdb with cheese https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1295247/+attachment/4351049/+files/gdb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1295247 Title: Cheese says There was an error playing video from webcam Status in cheese package in Ubuntu: Confirmed Bug description: Whenever I open Cheese in Ubuntu 14.04 beta 1 (Unity), my webcam's light once turns on, then it turns off and Cheese turns black, written There was an error playing video from webcam. This never happened in any previous versions of Ubuntu. The problem is reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cheese 3.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 20 22:29:57 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140225) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1295247/+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 1341708] Re: wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33
*** This bug is a duplicate of bug 1323089 *** https://bugs.launchpad.net/bugs/1323089 ** This bug has been marked a duplicate of bug 1323089 wpa_supplicant writes to syslog every 2 minutes -- 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/1341708 Title: wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33 Status in “wpa” package in Ubuntu: New Bug description: Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: CTRL-EVENT-SCAN-STARTED Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: send_and_recv-nl_recvmsgs failed: -33 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 14 15:00:14 2014 InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+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 1224764] Re: scanimage crashed with SIGSEGV in memchr()
Same here. Kubuntu 13.10 Here's a backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to LWP 22748] memchr () at ../sysdeps/x86_64/memchr.S:39 39 ../sysdeps/x86_64/memchr.S: No such file or directory. (gdb) bt #0 memchr () at ../sysdeps/x86_64/memchr.S:39 #1 0x7787a267 in __GI__IO_getline_info (fp=fp@entry=0x7fffe4001370, buf=buf@entry=0x7fffeb3898f0 kazaa, n=n@entry=2047, delim=delim@entry=10, extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94 #2 0x7787a398 in __GI__IO_getline (fp=fp@entry=0x7fffe4001370, buf=buf@entry=0x7fffeb3898f0 kazaa, n=n@entry=2047, delim=delim@entry=10, extract_delim=extract_delim@entry=1) at iogetline.c:38 #3 0x7787ecbc in __GI_fgets_unlocked (buf=buf@entry=0x7fffeb3898f0 kazaa, n=n@entry=2048, fp=0x7fffe4001370) at iofgets_u.c:55 #4 0x7fffea98265d in internal_getent (result=result@entry=0x7fffeb38a530, buffer=buffer@entry=0x7fffeb3898f0 kazaa, buflen=buflen@entry=2048, errnop=errnop@entry=0x7fffeb38b680) at nss_files/files-XXX.c:207 #5 0x7fffea982a44 in _nss_files_getservbyname_r (name=0x7fffeb9f8812 sane-port, proto=0x7798a03e gaih_inet_typeproto+30 tcp, result=0x7fffeb38a530, buffer=0x7fffeb3898f0 kazaa, buflen=2048, errnop=0x7fffeb38b680) at nss_files/files-service.c:41 #6 0x77920bc2 in __getservbyname_r (name=name@entry=0x7fffeb9f8812 sane-port, proto=proto@entry=0x7798a03e gaih_inet_typeproto+30 tcp, resbuf=resbuf@entry=0x7fffeb38a530, buffer=buffer@entry=0x7fffeb3898f0 kazaa, buflen=buflen@entry=2048, result=result@entry=0x7fffeb38a520) at ../nss/getXXbyYY_r.c:266 #7 0x778d62cb in gaih_inet_serv (servicename=0x7fffeb9f8812 sane-port, tp=tp@entry=0x7798a034 gaih_inet_typeproto+20, st=st@entry=0x7fffeb38a5b0, req=optimised out) at ../sysdeps/posix/getaddrinfo.c:164 #8 0x778d6633 in gaih_inet (name=name@entry=0x7fffe4001138 kuutio.local, service=0x7fffeb38a7f0, req=req@entry=0x7fffeb38a950, pai=pai@entry=0x7fffeb38a7b0, naddrs=naddrs@entry=0x7fffeb38a790) at ../sysdeps/posix/getaddrinfo.c:341 #9 0x778da914 in __GI_getaddrinfo (name=0x7fffe4001138 kuutio.local, service=optimised out, hints=0x7fffeb38a950, pai=0x7fffeb38a948) at ../sysdeps/posix/getaddrinfo.c:2473 #10 0x7fffeb9f4c3c in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1 #11 0x7fffeb9f4f48 in ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1 #12 0x7fffeb5da5db in avahi_service_resolver_event () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 #13 0x7fffeb5d5ecc in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 #14 0x7fffeb39a9e6 in dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #15 0x7fffeb5dc606 in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 #16 0x7fffeb7e9668 in avahi_simple_poll_dispatch () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 #17 0x7fffeb7e994d in avahi_simple_poll_loop () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 #18 0x7fffeb7e9a14 in ?? () from /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 #19 0x76ab1f6e in start_thread (arg=0x7fffeb38b700) at pthread_create.c:311 #20 0x779049cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Sane versions at the client: tuomas@epsilon:~ $ dpkg -l | grep sane ii libksane-data 4:4.11.2-0ubuntu1 all scanner library (data files) ii libksane0 4:4.11.2-0ubuntu1 amd64scanner library (runtime) ii libsane:amd64 1.0.23-0ubuntu3 amd64API library for scanners ii libsane-common1.0.23-0ubuntu3 amd64API library for scanners -- documentation and support files ii libsane-dev 1.0.23-0ubuntu3 amd64API development library for scanners [development files] ii libsane-hpaio 3.13.9-1ubuntu0.1 amd64HP SANE backend for multi-function peripherals ii sane-utils1.0.23-0ubuntu3 amd64API library for scanners -- utilities ii xsane 0.998-5ubuntu1 amd64featureful graphical frontend for SANE (Scanner Access Now Easy) ii xsane-common 0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy) The Sane server is Debian Wheeze 7.5 with sane 1.0.22-7.4 and libsane- hpaio 3.12.6-3.1+deb7u1. -- 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/1224764
[Desktop-packages] [Bug 1224764] Re: scanimage crashed with SIGSEGV in memchr()
If I stop avahi daemon at the Sane server, the segfault goes away.
--
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/1224764
Title:
scanimage crashed with SIGSEGV in memchr()
Status in “sane-backends” package in Ubuntu:
Confirmed
Bug description:
clearly still unstable
chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5'
is a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -L
device `net:10.0.0.50:plustek:libusb:004:002' is a UMAX 3400 flatbed scanner
device `net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5'
is a Hewlett-Packard Deskjet_F4400_series all-in-one
chad@chad-VirtualBox:~$ scanimage -f
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$ scanimage -f
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
{ID:0,INUSE:0,DEVICE:net:10.0.0.50:plustek:libusb:004:002,NAME:UMAX
3400 flatbed
scanner},{ID:1,INUSE:0,DEVICE:net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5,NAME:Hewlett-Packard
Deskjet_F4400_series all-in-one},chad@chad-VirtualBox:~$ ^C
chad@chad-VirtualBox:~$ scanimage -f
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
Segmentation fault (core dumped)
chad@chad-VirtualBox:~$
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: sane-utils 1.0.23-0ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Thu Sep 12 22:56:32 2013
ExecutablePath: /usr/bin/scanimage
InstallationDate: Installed on 2013-07-27 (47 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130727)
MarkForUpload: True
ProcCmdline: scanimage -f {ID:%i,INUSE:0,DEVICE:%d,NAME:%v\ %m\
%t},
SegvAnalysis:
Segfault happened at: 0x7f462dca8e20 memchr+192: movdqa (%rdi),%xmm0
PC (0x7f462dca8e20) ok
source (%rdi) (0x7f462e40a000) not located in a known VMA region (needed
readable region)!
destination %xmm0 ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: sane-backends
StacktraceTop:
memchr () at ../sysdeps/x86_64/memchr.S:88
__GI__IO_getline_info (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100
z3950, n=n@entry=1023, delim=delim@entry=10,
extract_delim=extract_delim@entry=1, eof=eof@entry=0x0) at iogetline.c:94
__GI__IO_getline (fp=fp@entry=0x688950, buf=buf@entry=0x7f462179d100
z3950, n=n@entry=1023, delim=delim@entry=10,
extract_delim=extract_delim@entry=1) at iogetline.c:38
__GI_fgets_unlocked (buf=buf@entry=0x7f462179d100 z3950, n=n@entry=1024,
fp=0x688950) at iofgets_u.c:55
internal_getent (result=result@entry=0x7f462179d530,
buffer=buffer@entry=0x7f462179d100 z3950, buflen=buflen@entry=1024,
errnop=errnop@entry=0x7f462179e680) at nss_files/files-XXX.c:207
Title: scanimage crashed with SIGSEGV in memchr()
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/sane-backends/+bug/1224764/+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 1208091] Re: scanimage assert failure: *** Error in `scanimage': double free or corruption (top): 0x0000000002598130 ***
Is this possibly a duplicate of #1224764 ?
--
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/1208091
Title:
scanimage assert failure: *** Error in `scanimage': double free or
corruption (top): 0x02598130 ***
Status in “sane-backends” package in Ubuntu:
Confirmed
Status in “sane-backends” package in Debian:
Incomplete
Bug description:
Similar errors occur when the normal user runs this command
Accessing sacnner using network, setup notes are here
http://ubuntuforums.org/showthread.php?t=1519201
My other virtualbox client has no issue here
the server is running xubuntu 13.04
This output is from the saucy client
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage -f
{\ID\:%i,\INUSE\:0,\DEVICE\:\%d\,\NAME\:\%v %m %t\},
{ID:0,INUSE:0,DEVICE:net:10.0.0.50:plustek:libusb:003:002,NAME:UMAX
3400 flatbed
scanner},{ID:1,INUSE:0,DEVICE:net:10.0.0.50:hpaio:/usb/Deskjet_F4400_series?serial=CN05DC61TP05C5,NAME:Hewlett-Packard
Deskjet_F4400_series all-in-one},
www-data@127.0.0.1:/home/www-data/PHP-Scanner-Server$ scanimage --help -d
'net:10.0.0.50:plustek:libusb:003:002'
*** Error in `scanimage': double free or corruption (top): 0x02598130
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x80996)[0x7f4379829996]
/lib/x86_64-linux-gnu/libc.so.6(fclose+0x14d)[0x7f43798179bd]
/lib/x86_64-linux-gnu/libnss_files.so.2(_nss_files_getservbyname_r+0x11b)[0x7f4373df7adb]
/lib/x86_64-linux-gnu/libc.so.6(getservbyname_r+0xd2)[0x7f43798bf022]
/lib/x86_64-linux-gnu/libc.so.6(+0xcb72b)[0x7f437987472b]
/lib/x86_64-linux-gnu/libc.so.6(+0xcba93)[0x7f4379874a93]
/lib/x86_64-linux-gnu/libc.so.6(getaddrinfo+0xf4)[0x7f4379878d74]
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(+0x6c3c)[0x7f437939cc3c]
/usr/lib/x86_64-linux-gnu/sane/libsane-net.so.1(sane_net_init+0x428)[0x7f437939d438]
/usr/lib/x86_64-linux-gnu/libsane.so.1(+0x3b00)[0x7f4379b73b00]
/usr/lib/x86_64-linux-gnu/libsane.so.1(sane_dll_open+0xe2)[0x7f4379b74842]
scanimage[0x401fa8]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f43797cade5]
scanimage[0x403924]
=== Memory map:
0040-0040a000 r-xp 08:01 1355
/usr/bin/scanimage
0060a000-0060b000 r--p a000 08:01 1355
/usr/bin/scanimage
0060b000-0060c000 rw-p b000 08:01 1355
/usr/bin/scanimage
0258d000-025ae000 rw-p 00:00 0
[heap]
7f4373bdd000-7f4373bf2000 r-xp 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373bf2000-7f4373df1000 ---p 00015000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df1000-7f4373df2000 r--p 00014000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df2000-7f4373df3000 rw-p 00015000 08:01 1604
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4373df3000-7f4373dff000 r-xp 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373dff000-7f4373ffe000 ---p c000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373ffe000-7f4373fff000 r--p b000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f4373fff000-7f437400 rw-p c000 08:01 1621
/lib/x86_64-linux-gnu/libnss_files-2.17.so
7f437400-7f4374021000 rw-p 00:00 0
7f4374021000-7f437800 ---p 00:00 0
7f437810e000-7f437810f000 ---p 00:00 0
7f437810f000-7f437890f000 rw-p 00:00 0
[stack:17829]
7f437890f000-7f4378916000 r-xp 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378916000-7f4378b15000 ---p 7000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b15000-7f4378b16000 r--p 6000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b16000-7f4378b17000 rw-p 7000 08:01 1615
/lib/x86_64-linux-gnu/librt-2.17.so
7f4378b17000-7f4378b5b000 r-xp 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378b5b000-7f4378d5a000 ---p 00044000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5a000-7f4378d5b000 r--p 00043000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5b000-7f4378d5c000 rw-p 00044000 08:01 5920
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.4
7f4378d5c000-7f4378d73000 r-xp 08:01 1617
/lib/x86_64-linux-gnu/libpthread-2.17.so
7f4378d73000-7f4378f73000 ---p 00017000 08:01 1617
/lib/x86_64-linux-gnu/libpthread-2.17.so
[Desktop-packages] [Bug 1225622] Re: [FUJITSU AMILO La1703, VT1708, playback] No sound at all
This obviously does not help to resolve the bug, but I wonder if there is a way to make the above mentioned changes permanent or via command line without having to use the hda-analyzer GUI after every boot? -- 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/1225622 Title: [FUJITSU AMILO La1703, VT1708, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 13.04 Release: 13.04 The on-board soundcard appears on sound configuration page and on alsa-mixer, all the channels have the volume at maximum but it doesn't play any sound. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emil 2203 F pulseaudio Date: Sun Sep 15 11:45:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-15 (183 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Alpha amd64 (20130311.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:VT82xx failed Symptom_Card: VT8237A/VT8251 HDA Controller - HDA VIA VT82xx Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emil 2203 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA VIA VT82xx, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2007 dmi.bios.vendor: Phoenix dmi.bios.version: 8.2-0023-M007 dmi.board.name: E25 dmi.board.vendor: Inventec dmi.board.version: Rev 01 dmi.chassis.asset.tag: User Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E25_ dmi.modalias: dmi:bvnPhoenix:bvr8.2-0023-M007:bd08/02/2007:svnFUJITSUSIEMENS:pnAMILOLa1703:pvr1.0:rvnInventec:rnE25:rvrRev01:cvnFUJITSUSIEMENS:ct10:cvrE25_: dmi.product.name: AMILO La1703 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225622/+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 1225622] Re: [FUJITSU AMILO La1703, VT1708, playback] No sound at all
I just realized that the Exp-button in hda-analyzer does just what I was asking for. -- 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/1225622 Title: [FUJITSU AMILO La1703, VT1708, playback] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 13.04 Release: 13.04 The on-board soundcard appears on sound configuration page and on alsa-mixer, all the channels have the volume at maximum but it doesn't play any sound. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emil 2203 F pulseaudio Date: Sun Sep 15 11:45:59 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-15 (183 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Alpha amd64 (20130311.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:VT82xx failed Symptom_Card: VT8237A/VT8251 HDA Controller - HDA VIA VT82xx Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emil 2203 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA VIA VT82xx, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2007 dmi.bios.vendor: Phoenix dmi.bios.version: 8.2-0023-M007 dmi.board.name: E25 dmi.board.vendor: Inventec dmi.board.version: Rev 01 dmi.chassis.asset.tag: User Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: E25_ dmi.modalias: dmi:bvnPhoenix:bvr8.2-0023-M007:bd08/02/2007:svnFUJITSUSIEMENS:pnAMILOLa1703:pvr1.0:rvnInventec:rnE25:rvrRev01:cvnFUJITSUSIEMENS:ct10:cvrE25_: dmi.product.name: AMILO La1703 dmi.product.version: 1.0 dmi.sys.vendor: FUJITSU SIEMENS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1225622/+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 822275] Re: Bluetooth Browse files on functionality broken
i have same errors in 12.10 Ubuntu 64bit.
but this also working.
Mount to phones to linux use:
obexfs -b A8:7E:33:B2:D5:EA /home/tuomas/Nokia2720a
unmount to phones
fusermount -u /home/tuomas/Nokia2720a
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to obex-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/822275
Title:
Bluetooth Browse files on functionality broken
Status in “gnome-bluetooth” package in Ubuntu:
Confirmed
Status in “obex-data-server” package in Ubuntu:
Confirmed
Bug description:
It is not possible to browse files on bluetooth devides using the
`gnome-bluetooth` Browse files on
This is a regression from Karmic where the Browse file on
functionality was flawlessly working.
Steps to reproduce, TEST CASE:
1) enable bluetooth on mobile device;
2) select Browse files on from `gnome-bluetooth` applet;
3) select one mobile device;
4) wait for the nautilus window to appear (it will not).
Tested on a brand new Lucid LTS 10.04.3.
As suggested in bug #542805 (closed as fix released but only partially
really fixed), I tried running `/usr/share/doc/obexd-client/examples
/list-folders`. This little application crashes with
Traceback (most recent call last):
File /usr/share/doc/obexd-client/examples/list-folders, line 38, in
module
list_folder(folder)
File /usr/share/doc/obexd-client/examples/list-folders, line 12, in
list_folder
session_path = client.CreateSession({ Destination: sys.argv[1],
Target: ftp})
File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 68, in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 140, in __call__
**keywords)
File /usr/lib/pymodules/python2.6/dbus/connection.py, line 620, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.openobex.Error.Failed:
Bug #283064, comment 22 (bug closed as invalid) suggests that this
problem is caused by a mismatching version of `obex-data-server` and
offers a PPA (currently outdated) to solve this problem.
Bug #161 on obex-data-server's mantis
(http://bugs.muiline.com/view.php?id=161) from 2009 says that changing
the obex-data-server DBus config fixes this problems. They also
applied a patch to their SVN version.
Could you please fix this bug by backporting to Lucid versions of
gnome-bluetooth and obex-data-server that are compatible with each
other? Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-bluetooth 2.30.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic x86_64
Architecture: amd64
Date: Sun Aug 7 14:48:48 2011
InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release amd64
(20110720.1)
SourcePackage: gnome-bluetooth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/822275/+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 822275] Re: Bluetooth Browse files on functionality broken
Please also note that the Ubuntu 10.04 live-cd version software,
however, will work correct. But when you installed and updated software.
Software not working. What has be changed?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to obex-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/822275
Title:
Bluetooth Browse files on functionality broken
Status in “gnome-bluetooth” package in Ubuntu:
Confirmed
Status in “obex-data-server” package in Ubuntu:
Confirmed
Bug description:
It is not possible to browse files on bluetooth devides using the
`gnome-bluetooth` Browse files on
This is a regression from Karmic where the Browse file on
functionality was flawlessly working.
Steps to reproduce, TEST CASE:
1) enable bluetooth on mobile device;
2) select Browse files on from `gnome-bluetooth` applet;
3) select one mobile device;
4) wait for the nautilus window to appear (it will not).
Tested on a brand new Lucid LTS 10.04.3.
As suggested in bug #542805 (closed as fix released but only partially
really fixed), I tried running `/usr/share/doc/obexd-client/examples
/list-folders`. This little application crashes with
Traceback (most recent call last):
File /usr/share/doc/obexd-client/examples/list-folders, line 38, in
module
list_folder(folder)
File /usr/share/doc/obexd-client/examples/list-folders, line 12, in
list_folder
session_path = client.CreateSession({ Destination: sys.argv[1],
Target: ftp})
File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 68, in __call__
return self._proxy_method(*args, **keywords)
File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 140, in __call__
**keywords)
File /usr/lib/pymodules/python2.6/dbus/connection.py, line 620, in
call_blocking
message, timeout)
dbus.exceptions.DBusException: org.openobex.Error.Failed:
Bug #283064, comment 22 (bug closed as invalid) suggests that this
problem is caused by a mismatching version of `obex-data-server` and
offers a PPA (currently outdated) to solve this problem.
Bug #161 on obex-data-server's mantis
(http://bugs.muiline.com/view.php?id=161) from 2009 says that changing
the obex-data-server DBus config fixes this problems. They also
applied a patch to their SVN version.
Could you please fix this bug by backporting to Lucid versions of
gnome-bluetooth and obex-data-server that are compatible with each
other? Thank you.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gnome-bluetooth 2.30.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic x86_64
Architecture: amd64
Date: Sun Aug 7 14:48:48 2011
InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release amd64
(20110720.1)
SourcePackage: gnome-bluetooth
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/822275/+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 927515] Re: Thunderbird stuck at 100% CPU
Per Baekgaard, I tested your workaround suggestion, but it does not seem to help in my case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/927515 Title: Thunderbird stuck at 100% CPU Status in Mozilla Thunderbird Mail and News: New Status in The Ubuntu Power Consumption Project: Confirmed Status in “thunderbird” package in Ubuntu: Triaged Bug description: Just received the automatic update last night. Ever since, thunderbird is using 20-50% CPU constantly, according to top. Turned off global search and indexing to no avail. This is really bad for me as it's driving up the temperature of my laptop, runs up the fan noise and reduces battery time. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 10.0+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 BuildID: 20120129183038 Date: Mon Feb 6 10:44:55 2012 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=nl_NL:nl:en PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0Locales: extensions.sqlite corrupt or missing Profile0Plugins: pluginreg.dat isn't available Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=3.0.6/20100713193322 (Out of date) Profile1 (Default) - LastVersion=10.0/20120129183038 (Running) SourcePackage: thunderbird UpgradeStatus: Upgraded to oneiric on 2012-02-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/927515/+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 1171853] Re: Cannot log in to Google apps domain + Ubuntu SSO
Same errors with facebook account. 5 minute intervals combination browser request. using ubuntu 12.10 version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1171853 Title: Cannot log in to Google apps domain + Ubuntu SSO Status in Online Accounts: Sign-on UI: Fix Committed Status in “signon-ui” package in Ubuntu: Fix Released Status in “signon-ui” source package in Raring: Confirmed Bug description: I'm trying to log in to my Google apps account through the Online Accounts dialog and so far I've been unsuccessful. From the online accounts dialog, after the Google login page, I'm then taken to the Ubuntu SSO page, but when I enter my SSO user name and password, I get a blank screen with an error message that doesn't give me any pointers as to what's happened (see attached screenshot). I'm also attaching the output generated by invoking signon-ui from the command line with SSOUI_LOGGING_LEVEL=2 Additional information for the SRU request: [Impact] Makes it impossible to create Google apps accounts linked to Ubuntu SSO (and possibly others). [Test Case] Open Online Accounts, click on Add account, choose Google, then enter your e-mail address (leave the password field empty), and press Sign in. Follow the instructions, but if the bug is not fixed you'll soon be presented with the error message from comment #2. If the bug is fixed, the account creation should complete successfully. [Regression Potential] The code paths touched by this patch are only hit when a web page fails to load; we simply delay reporting the error by 3 seconds, and cancel the error condition if in the meantime the WebView has shown some signs of activity. So, this patch should not affect the successful creation of other accounts, but just add a small delay to the ones failing because of network errors. To manage notifications about this bug go to: https://bugs.launchpad.net/signon-ui/+bug/1171853/+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 1175603] Re: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build
*** This bug is a duplicate of bug 859101 *** https://bugs.launchpad.net/bugs/859101 I think this bug should not be marked as duplicate #859101 of due to completely different versions of both fglrx and kernel. It just the nature of these dkmsable modules which keeps them breaking over and over again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1175603 Title: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build OS: xubuntu 13.10 Kernel: Linux 3.9.0-0-generic #3-Ubuntu SMP Mon Apr 29 23:13:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Package DistroRelease: Ubuntu 13.10 Package: fglrx 2:9.010-0ubuntu3 ProcVersionSignature: Ubuntu 3.9.0-0.3-generic 3.9.0 Uname: Linux 3.9.0-0-generic x86_64 ApportVersion: 2.10-0ubuntu1 Architecture: amd64 DKMSBuildLog: DKMS make.log for fglrx-9.010 for kernel 3.9.0-0-generic (x86_64) 2013年 05月 02日 星期四 21:18:06 CST AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.9.0-0-generic/build/include not found or incomplete file: /lib/modules/3.9.0-0-generic/build/include/linux/version.h DKMSKernelVersion: 3.9.0-0-generic Date: Thu May 2 21:18:10 2013 DuplicateSignature: DKMS make.log for fglrx-9.010 for kernel 3.9.0-0-generic (x86_64) 2013年 05月 02日 星期四 21:18:06 CST AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.9.0-0-generic/build/include not found or incomplete file: /lib/modules/3.9.0-0-generic/build/include/linux/version.h InstallationDate: Installed on 2013-04-23 (8 days ago) InstallationMedia: Xubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True PackageVersion: 2:9.010-0ubuntu3 SourcePackage: fglrx-installer Title: fglrx 2:9.010-0ubuntu3: fglrx kernel module failed to build UpgradeStatus: Upgraded to saucy on 2013-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1175603/+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 927515] Re: Thunderbird stuck at 100% CPU
I do have this issue even if message pane is closed with F8 and also no other message windows or tabs are opened. Thunderbird 17.0.5, Ubuntu 13.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/927515 Title: Thunderbird stuck at 100% CPU Status in The Ubuntu Power Consumption Project: New Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Just received the automatic update last night. Ever since, thunderbird is using 20-50% CPU constantly, according to top. Turned off global search and indexing to no avail. This is really bad for me as it's driving up the temperature of my laptop, runs up the fan noise and reduces battery time. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 10.0+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 BuildID: 20120129183038 Date: Mon Feb 6 10:44:55 2012 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=nl_NL:nl:en PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0Locales: extensions.sqlite corrupt or missing Profile0Plugins: pluginreg.dat isn't available Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile0 - LastVersion=3.0.6/20100713193322 (Out of date) Profile1 (Default) - LastVersion=10.0/20120129183038 (Running) SourcePackage: thunderbird UpgradeStatus: Upgraded to oneiric on 2012-02-02 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/927515/+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 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync
** Tags added: precise -- 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/890337 Title: gvfs-gdu-volume-monitor high cpu usage during raid-resync Status in “gnome-disk-utility” package in Ubuntu: New Bug description: During a raid-resync cpu usage is high - in fact gvfs-gdu-volume- monitor was using 100% cpu on one core for the duration of resync. Killed it with -SEGV to get something that can be retraced. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 23:36:38 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SegvAnalysis: Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e PC (0x7fca9329a3c3) ok source 0x7fca9329a32e (0x7fca9329a32e) ok SP (0x7fff9b1adac0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgdu.so.0 ?? () from /usr/lib/libgdu.so.0 Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+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 859600] Re: Please convert gnome-keyring to multiarch
please fix for ubuntu 12.10 also, i have same bug for 1.5.27 wine versions too. -- 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/859600 Title: Please convert gnome-keyring to multiarch Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Precise: In Progress Status in “gnome-keyring” source package in Quantal: Confirmed Status in “gnome-keyring” source package in Raring: Fix Released Status in “gnome-keyring” package in Debian: New Bug description: [Impact] Several applications are relying on this package as seen in comments 5 and 6. [Test case] Attempt to install both i386/amd64 versions and preferably verify if the reported applications in this bug are able to run successfully [Regression Potential] Minimal, several rdepends build testing have been completed successfully and nothing in the keyring code is attempting to dlopen any hardcoded library paths. gnome-keyring is still installing libraries to /usr/lib instead of the multarch compatible /usr/lib/$(DEB_HOST_MULTIARCH) directory. The attached patch does the conversion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/859600/+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 1067732] Re: Gibber does not update and show current posts.
login not worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1067732 Title: Gibber does not update and show current posts. Status in “gwibber” package in Ubuntu: Expired Bug description: the posts are always days behind real time. Gibber does not update and it does not show my facebook friends posts. I really don't see any advantage to Gibber over just logging into facebook directly. Please expain just what Gibber is supposed to do? Gibber worked better with Ubuntu versions prior to 10.04. I am using Ubuntu 12.04LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1067732/+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 1045661] Re: High CPU usage
And also still in TB 17.0 (Ubuntu 12.10). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1045661 Title: High CPU usage Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Thunderbird CPU usage goes up to 100% and keep it that way after an unknown event. I tried using it in safe mode, but the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 15.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 BuildID: 20120827103657 Date: Tue Sep 4 08:44:15 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date) SourcePackage: thunderbird UpgradeStatus: Upgraded to precise on 2012-04-26 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1045661/+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 1081108] Re: Xorg crash after clicking on workspace in inkscape
Copypaste from wrong, old bug report (2012-12-03): last week (28th November) I was using inkscape without problems. I tried to downgrade all ubuntu packages that were upgraded last week, but without success. Now it does not work at all. My workaround is to use inkscape through VNC. Moreover, it seems not to be nvidia driver specific, but appears with nouveau drivers as well. xserver-xorg-video-nouveau version 1.0.2-0ubuntu3, Ubuntu 12.10. -- 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/1081108 Title: Xorg crash after clicking on workspace in inkscape Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Steps to reproduce on my machine: 1) open inkscape 2) click anywhere on workspace Result: X dies, back to login prompt Expected result: nothing should happen Details of my setup: I did not manage to get an Xorg backtrace yet as I don't have a second maching to do the remote SSH thing. This bug looks a lot like #1023004, I opened a new one because the old one is fix released with no-one assigned to. The install is fresh on a new laptop. I have since switched to the xorg-bleeding PPA, but this did not fix the problem. I am also now using the trunk PPA of inkscape, without change of behaviour. Please advise if more information is needed. Xorg.log: [ 42260.310] (EE) [ 42260.310] (EE) Backtrace: [ 42260.310] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f50040ffbd6] [ 42260.310] (EE) 1: /usr/bin/X (0x7f5003f57000+0x1aca09) [0x7f5004103a09] [ 42260.310] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f500327d000+0xfcb0) [0x7f500328ccb0] [ 42260.311] (EE) 3: /usr/bin/X (0x7f5003f57000+0x665da) [0x7f5003fbd5da] [ 42260.311] (EE) 4: /usr/bin/X (0x7f5003f57000+0x5ff43) [0x7f5003fb6f43] [ 42260.311] (EE) 5: /usr/bin/X (0x7f5003f57000+0x13dd32) [0x7f5004094d32] [ 42260.311] (EE) 6: /usr/bin/X (0x7f5003f57000+0x55a51) [0x7f5003faca51] [ 42260.311] (EE) 7: /usr/bin/X (0x7f5003f57000+0x4456a) [0x7f5003f9b56a] [ 42260.311] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f5001f0276d] [ 42260.312] (EE) 9: /usr/bin/X (0x7f5003f57000+0x448ad) [0x7f5003f9b8ad] [ 42260.312] (EE) [ 42260.312] (EE) Segmentation fault at address 0x28 [ 42260.312] Fatal server error: [ 42260.312] Caught signal 11 (Segmentation fault). Server aborting [ 42260.312] [ 42260.312] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 42260.312] (EE) Please also check the log file at /var/log/Xorg.0.log for additional information. [ 42260.312] (EE) [ 42260.328] (II) evdev: Power Button: Close [ 42260.328] (II) UnloadModule: evdev [ 42260.329] (II) evdev: Video Bus: Close [ 42260.329] (II) UnloadModule: evdev [ 42260.329] (II) evdev: Sleep Button: Close [ 42260.329] (II) UnloadModule: evdev [ 42260.330] (II) evdev: Integrated Camera: Close [ 42260.330] (II) UnloadModule: evdev [ 42260.330] (II) evdev: AT Translated Set 2 keyboard: Close [ 42260.331] (II) UnloadModule: evdev [ 42260.331] (II) evdev: TPPS/2 IBM TrackPoint: Close [ 42260.332] (II) UnloadModule: evdev [ 42260.332] (II) evdev: ThinkPad Extra Buttons: Close [ 42260.332] (II) UnloadModule: evdev [ 42260.333] (II) UnloadModule: synaptics [ 42260.333] (II) AIGLX: Suspending AIGLX clients for VT switch [ 42260.356] Server terminated with error (1). Closing log file. lsb_release -d Description: Ubuntu 12.10 apt-cache policy inkscape-trunk inkscape-trunk: Installed: 1:0.48+devel+11885+32~quantal1 Candidate: 1:0.48+devel+11885+32~quantal1 Version table: *** 1:0.48+devel+11885+32~quantal1 0 500 http://ppa.launchpad.net/inkscape.dev/trunk/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.0+git20120920.70e57668-0ubuntu0ricotz Candidate: 2:1.13.0+git20120920.70e57668-0ubuntu0ricotz Version table: *** 2:1.13.0+git20120920.70e57668-0ubuntu0ricotz 0 500 http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status 2:1.13.0-0ubuntu6 0 500 http://ch.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Nov 20 14:09:10 2012 InstallationDate: Installed on 2012-11-15 (5 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Desktop-packages] [Bug 1023004] Re: xorg crashes when clicking in inkscape work area
Last week (28th November) I was using inkscape without problems. I tried to downgrade all ubuntu packages that were upgraded last week, but without success. Now it does not work at all. My workaround is to use inkscape through VNC. -- 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/1023004 Title: xorg crashes when clicking in inkscape work area Status in Inkscape: A Vector Drawing Tool: Invalid Status in “xorg-server” package in Ubuntu: Fix Released Bug description: clicking on the workarea in any inkscape document crashes xorg and brings me to the login screen. this happens in all window managers (gnome and unity 2D3D). i am using the internal intel graphic card on a lenovo T520 with a i7-2670QM. this behaviour is always reproducable. syslog: gnome-session[2311]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.#012 Xorg.log: Backtrace: [ 5122.869] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7fb427f61996] [ 5122.869] 1: /usr/bin/X (0x7fb427dd9000+0x18c83a) [0x7fb427f6583a] [ 5122.869] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb4270ff000+0xfcb0) [0x7fb42710ecb0] [ 5122.869] 3: /usr/bin/X (0x7fb427dd9000+0x5e71a) [0x7fb427e3771a] [ 5122.869] 4: /usr/bin/X (0x7fb427dd9000+0x58070) [0x7fb427e31070] [ 5122.869] 5: /usr/bin/X (0x7fb427dd9000+0x1230ef) [0x7fb427efc0ef] [ 5122.869] 6: /usr/bin/X (0x7fb427dd9000+0x4e8b1) [0x7fb427e278b1] [ 5122.869] 7: /usr/bin/X (0x7fb427dd9000+0x3d6da) [0x7fb427e166da] [ 5122.869] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7fb425f9476d] [ 5122.869] 9: /usr/bin/X (0x7fb427dd9000+0x3d9d1) [0x7fb427e169d1] [ 5122.869] Segmentation fault at address 0x28 [ 5122.869] Caught signal 11 (Segmentation fault). Server aborting [ 5122.869] lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy xserver-xorg-core xserver-xorg-core: Installiert: 2:1.11.4-0ubuntu10.3 Kandidat:2:1.11.4-0ubuntu10.3 Versionstabelle: *** 2:1.11.4-0ubuntu10.3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.11.4-0ubuntu10 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installiert: 2:2.17.0-1ubuntu4 Kandidat:2:2.17.0-1ubuntu4 Versionstabelle: *** 2:2.17.0-1ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1023004/+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 1023004] Re: xorg crashes when clicking in inkscape work area
I am experiencing this bug only on my primary laptop screen. I can use inkscape if I use external screen. On that working setup I have laptop screen switched off and I am using two external monitors, one with DVI and one with VGA connection. -- 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/1023004 Title: xorg crashes when clicking in inkscape work area Status in Inkscape: A Vector Drawing Tool: Invalid Status in “xorg-server” package in Ubuntu: Fix Released Bug description: clicking on the workarea in any inkscape document crashes xorg and brings me to the login screen. this happens in all window managers (gnome and unity 2D3D). i am using the internal intel graphic card on a lenovo T520 with a i7-2670QM. this behaviour is always reproducable. syslog: gnome-session[2311]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.#012 Xorg.log: Backtrace: [ 5122.869] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7fb427f61996] [ 5122.869] 1: /usr/bin/X (0x7fb427dd9000+0x18c83a) [0x7fb427f6583a] [ 5122.869] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb4270ff000+0xfcb0) [0x7fb42710ecb0] [ 5122.869] 3: /usr/bin/X (0x7fb427dd9000+0x5e71a) [0x7fb427e3771a] [ 5122.869] 4: /usr/bin/X (0x7fb427dd9000+0x58070) [0x7fb427e31070] [ 5122.869] 5: /usr/bin/X (0x7fb427dd9000+0x1230ef) [0x7fb427efc0ef] [ 5122.869] 6: /usr/bin/X (0x7fb427dd9000+0x4e8b1) [0x7fb427e278b1] [ 5122.869] 7: /usr/bin/X (0x7fb427dd9000+0x3d6da) [0x7fb427e166da] [ 5122.869] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7fb425f9476d] [ 5122.869] 9: /usr/bin/X (0x7fb427dd9000+0x3d9d1) [0x7fb427e169d1] [ 5122.869] Segmentation fault at address 0x28 [ 5122.869] Caught signal 11 (Segmentation fault). Server aborting [ 5122.869] lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy xserver-xorg-core xserver-xorg-core: Installiert: 2:1.11.4-0ubuntu10.3 Kandidat:2:1.11.4-0ubuntu10.3 Versionstabelle: *** 2:1.11.4-0ubuntu10.3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.11.4-0ubuntu10 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installiert: 2:2.17.0-1ubuntu4 Kandidat:2:2.17.0-1ubuntu4 Versionstabelle: *** 2:2.17.0-1ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1023004/+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 1023004] Re: xorg crashes when clicking in inkscape work area
Moreover, it seems not to be nvidia driver specific, but appears with nouveau drivers as well. xserver-xorg-video-nouveau version 1.0.2-0ubuntu3, Ubuntu 12.10. -- 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/1023004 Title: xorg crashes when clicking in inkscape work area Status in Inkscape: A Vector Drawing Tool: Invalid Status in “xorg-server” package in Ubuntu: Fix Released Bug description: clicking on the workarea in any inkscape document crashes xorg and brings me to the login screen. this happens in all window managers (gnome and unity 2D3D). i am using the internal intel graphic card on a lenovo T520 with a i7-2670QM. this behaviour is always reproducable. syslog: gnome-session[2311]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.#012 Xorg.log: Backtrace: [ 5122.869] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7fb427f61996] [ 5122.869] 1: /usr/bin/X (0x7fb427dd9000+0x18c83a) [0x7fb427f6583a] [ 5122.869] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fb4270ff000+0xfcb0) [0x7fb42710ecb0] [ 5122.869] 3: /usr/bin/X (0x7fb427dd9000+0x5e71a) [0x7fb427e3771a] [ 5122.869] 4: /usr/bin/X (0x7fb427dd9000+0x58070) [0x7fb427e31070] [ 5122.869] 5: /usr/bin/X (0x7fb427dd9000+0x1230ef) [0x7fb427efc0ef] [ 5122.869] 6: /usr/bin/X (0x7fb427dd9000+0x4e8b1) [0x7fb427e278b1] [ 5122.869] 7: /usr/bin/X (0x7fb427dd9000+0x3d6da) [0x7fb427e166da] [ 5122.869] 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7fb425f9476d] [ 5122.869] 9: /usr/bin/X (0x7fb427dd9000+0x3d9d1) [0x7fb427e169d1] [ 5122.869] Segmentation fault at address 0x28 [ 5122.869] Caught signal 11 (Segmentation fault). Server aborting [ 5122.869] lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy xserver-xorg-core xserver-xorg-core: Installiert: 2:1.11.4-0ubuntu10.3 Kandidat:2:1.11.4-0ubuntu10.3 Versionstabelle: *** 2:1.11.4-0ubuntu10.3 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 2:1.11.4-0ubuntu10 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installiert: 2:2.17.0-1ubuntu4 Kandidat:2:2.17.0-1ubuntu4 Versionstabelle: *** 2:2.17.0-1ubuntu4 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1023004/+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 1045661] Re: High CPU usage
The bug still exists in TB 16.0.2 (Ubuntu 12.10). :E -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1045661 Title: High CPU usage Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Thunderbird CPU usage goes up to 100% and keep it that way after an unknown event. I tried using it in safe mode, but the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 15.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 BuildID: 20120827103657 Date: Tue Sep 4 08:44:15 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=Safe Mode/Safe Mode (Out of date) SourcePackage: thunderbird UpgradeStatus: Upgraded to precise on 2012-04-26 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1045661/+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 1018786] Re: Transport endpoint is not connected on Xubuntu quantal Alpha-2 (entire disk w/ encryption)
im updating 10.04 LTS to 12.10 LTS and install xubuntu packages. And i have a same errors with using xubuntu filemanager. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1018786 Title: Transport endpoint is not connected on Xubuntu quantal Alpha-2 (entire disk w/ encryption) Status in “gvfs” package in Ubuntu: Confirmed Bug description: When testing Xubuntu quantal Alpha-2 alternate install, entire disk with encryption (also chose to encrypt $HOME), I get an error message while opening Thunar: Failed to open directory jaska (that's my user). Error when getting information for file '/home/jaska/.gvfs': Transport endpoint is not connected. Thunar is unable to show the contents of $HOME. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1018786/+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 1024961] Re: Gimp causes session to close immediately
I can confirm this. /usr/bin/X encounters a segmentation fault and aborts. ** Changed in: gimp (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1024961 Title: Gimp causes session to close immediately Status in “gimp” package in Ubuntu: Confirmed Bug description: Whenever I use Gimp, with the first mouse click in the image (e.g. selecting a region or ANYTHING else) - my Ubuntu session is immediately killed - all windows disappear and I return to the login screen of Ubuntu. No matter what was running - it is closed and lost. There are no other signs I can see, simply nothing. I have never experienced anything like this before and I do only get this when using Gimp, no other programs cause problems! How can I track this down? I am using the regular Ubuntu version of Gimp 2.6 that comes from the repositories! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gimp 2.6.12-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sun Jul 15 16:03:05 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gimp UpgradeStatus: Upgraded to precise on 2012-04-30 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1024961/+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 1024961] Re: Gimp causes session to close immediately
** Attachment added: Xorg.log https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1024961/+attachment/3224112/+files/Xorg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1024961 Title: Gimp causes session to close immediately Status in “gimp” package in Ubuntu: Confirmed Bug description: Whenever I use Gimp, with the first mouse click in the image (e.g. selecting a region or ANYTHING else) - my Ubuntu session is immediately killed - all windows disappear and I return to the login screen of Ubuntu. No matter what was running - it is closed and lost. There are no other signs I can see, simply nothing. I have never experienced anything like this before and I do only get this when using Gimp, no other programs cause problems! How can I track this down? I am using the regular Ubuntu version of Gimp 2.6 that comes from the repositories! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gimp 2.6.12-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sun Jul 15 16:03:05 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gimp UpgradeStatus: Upgraded to precise on 2012-04-30 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1024961/+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 1024961] Re: Gimp causes session to close immediately
*** This bug is a duplicate of bug 1021517 *** https://bugs.launchpad.net/bugs/1021517 After browsing the bug database, I am quite sure that this particular bug is a duplicate of bug #1021517, so I am marking it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1021517 Xorg-server crashes reproducible with GIMP usage -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1024961 Title: Gimp causes session to close immediately Status in “gimp” package in Ubuntu: Confirmed Bug description: Whenever I use Gimp, with the first mouse click in the image (e.g. selecting a region or ANYTHING else) - my Ubuntu session is immediately killed - all windows disappear and I return to the login screen of Ubuntu. No matter what was running - it is closed and lost. There are no other signs I can see, simply nothing. I have never experienced anything like this before and I do only get this when using Gimp, no other programs cause problems! How can I track this down? I am using the regular Ubuntu version of Gimp 2.6 that comes from the repositories! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gimp 2.6.12-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu11 Architecture: amd64 Date: Sun Jul 15 16:03:05 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gimp UpgradeStatus: Upgraded to precise on 2012-04-30 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1024961/+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 896638] Re: Screen lock does not grab all keys
With Precise it seems that also Alt key-press events are going through the screen lock, i.e. the HUD opens, if Alt is pressed while screen is locked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/896638 Title: Screen lock does not grab all keys Status in “gnome-screensaver” package in Ubuntu: New Bug description: When screen is locked with gnome screensaver, it is still possible to send Win-key event to the underlaying desktop. I think there should be no way to interact with the underlaying desktop without unlocking. To reproduce: 1. Start from Unity session. Make sure that Dash is not open. 2. Lock screen from the top-right gear button 3. Press shift to make the unlock dialog appear 4. Press Windows key 5. Type in your password and unlock the screen What should happen: The desktop should be in the same state it was left before the locking. Dash should not be open. What happens: Dash has been opened, i.e. the Windows key event was passed to desktop although it was locked. Wonder if it is possible to pass through any other key events. Didn't find any though with a quick test. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 26 19:01:25 2011 EcryptfsInUse: Yes ProcEnviron: LC_TIME=en_DK.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+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 989606] [NEW] Flash black box
Public bug reported: Using adobe-flashplugin. Flash not working in firefox. see bug https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/968759 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/989606 Title: Flash black box Status in “firefox” package in Ubuntu: New Bug description: Using adobe-flashplugin. Flash not working in firefox. see bug https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/968759 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/989606/+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 799865] Re: Nautilus cannot handle gphoto2 locations
Same error with canon ixus40 in USB. i use a Ubuntu 10.04 lucid. if im use a command: gvfs-open gphoto2://[usb:003,002]/ error is Items ”gphoto2://[usb:003,002]/”can not be displayed. Error: DBus error org.freedesktop.DBus.Error.ServiceUnknown: The name :1.107 was not provided by any .service files Select another viewer and try again. naulilus not open folder but i get copy images f-spot . if im use a command nautilus gphoto2://[usb:003,002]/ error is: File type is unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/799865 Title: Nautilus cannot handle gphoto2 locations Status in “gvfs” package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus I've been trying to debug why Nautilus does nothing when my camera (Canon A1100IS) is connected via USB. The camera is accessible through Shotwell and under my Windows virtual machine but Nautilus does nothing. $ gphoto2 --auto-detect Model Port -- Canon PowerShot A1100 IS usb:002,009 $ nautilus gphoto2://[usb:002,009] Gives an error dialog: Could not display gphoto2://[usb:002,009]/. Nautilus cannot handle gphoto2 locations. This is a fresh install of Ubuntu 11.04. I'm positive this worked under my Ubuntu 10.10 system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/799865/+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 799865] Re: Nautilus cannot handle gphoto2 locations
if you choose to open a folder in a different way nautilus working. im use *USB cable to the camera *monitor brings up a menu to open the program *select open folder naulilus working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/799865 Title: Nautilus cannot handle gphoto2 locations Status in “gvfs” package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus I've been trying to debug why Nautilus does nothing when my camera (Canon A1100IS) is connected via USB. The camera is accessible through Shotwell and under my Windows virtual machine but Nautilus does nothing. $ gphoto2 --auto-detect Model Port -- Canon PowerShot A1100 IS usb:002,009 $ nautilus gphoto2://[usb:002,009] Gives an error dialog: Could not display gphoto2://[usb:002,009]/. Nautilus cannot handle gphoto2 locations. This is a fresh install of Ubuntu 11.04. I'm positive this worked under my Ubuntu 10.10 system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/799865/+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 941557] [NEW] libreoffice-help-fi package is broken
Public bug reported: dpkg: error handling /home/user/libreoffice-help-fi__3.5.0-1ubuntu3~lucid1_all.deb (--install): parsing file 'var/lib/dbkg/tmp.ci/control' near line 10 package 'libreoffice-help-fi': 'Conflicts' field, reference to liblucene2-java': error in version: version number does not start wiht digit ppa package is broken with Ubuntu lucid. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: fi help libreoffice -- 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/941557 Title: libreoffice-help-fi package is broken Status in “libreoffice” package in Ubuntu: New Bug description: dpkg: error handling /home/user/libreoffice-help-fi__3.5.0-1ubuntu3~lucid1_all.deb (--install): parsing file 'var/lib/dbkg/tmp.ci/control' near line 10 package 'libreoffice-help-fi': 'Conflicts' field, reference to liblucene2-java': error in version: version number does not start wiht digit ppa package is broken with Ubuntu lucid. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/941557/+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 908358] Re: software-center crashed with SIGSEGV on enabling universe
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/908358 Title: software-center crashed with SIGSEGV on enabling universe Status in “software-center” package in Ubuntu: New Bug description: Tried to enable universe repo, got crash notification. Oddly enough sfotware-center window did not disappear, so guess it was just a background process it is using. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: software-center 5.1.4 ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6 Uname: Linux 3.2.0-6-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 CasperVersion: 1.296 Date: Sat Dec 24 11:51:56 2011 ExecutablePath: /usr/share/software-center/software-center InterpreterPath: /usr/bin/python2.7 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20111223) PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4dbe38: mov0x8(%rbp),%rax PC (0x004dbe38) ok source 0x8(%rbp) (0x0008) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SoftwareCenterLog: 2011-12-24 11:51:33,506 - softwarecenter.ui.gtk3.em - INFO - EM's: 17 13 20 2011-12-24 11:51:33,960 - softwarecenter.backend.reviews - WARNING - Could not get usefulness from server, no username in config file 2011-12-24 11:51:34,117 - softwarecenter.ui.gtk3.utils - INFO - Softwarecenter style provider for ambiance Gtk theme: /usr/share/software-center/ui/gtk3/css/softwarecenter.css 2011-12-24 11:51:36,540 - softwarecenter.ui.gtk3.app - INFO - software-center-agent finished with status 0 SourcePackage: software-center StacktraceTop: ?? () ?? () ?? () ?? () Title: software-center crashed with SIGSEGV 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/software-center/+bug/908358/+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 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync
** Attachment added: cpu usage does not drop after several hours of raid resync, uses a lot of memory too https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+attachment/2609183/+files/after_resync_status.txt ** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/890337 Title: gvfs-gdu-volume-monitor high cpu usage during raid-resync Status in “gvfs” package in Ubuntu: New Bug description: During a raid-resync cpu usage is high - in fact gvfs-gdu-volume- monitor was using 100% cpu on one core for the duration of resync. Killed it with -SEGV to get something that can be retraced. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 23:36:38 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SegvAnalysis: Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e PC (0x7fca9329a3c3) ok source 0x7fca9329a32e (0x7fca9329a32e) ok SP (0x7fff9b1adac0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgdu.so.0 ?? () from /usr/lib/libgdu.so.0 Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/890337/+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 761478] Re: Enhancement: Prompt to check a busy file system on next reboot
Simply creating that file would not be entirely enough. As in while that seems to force the fsck, said file does not get removed automatically. And maybe even shouldn't be removed, unless it was created by gdu. -- 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/761478 Title: Enhancement: Prompt to check a busy file system on next reboot Status in “gnome-disk-utility” package in Ubuntu: Confirmed Status in Baltix GNU/Linux: New Bug description: Binary package hint: gnome-disk-utility When selecting Check File System on a file system which is is use, you currently get an error stating the device is busy. If a disk was busy, Disk Utility could prompt the user and ask if the file system should be scheduled for a check on the next reboot. I have just found out about the special file /forcefsck (http://www.cyberciti.biz/faq/linux-force-fsck-on-the-next-reboot-or- boot-sequence/) which forces the file system to be checked on the next reboot, and due to this I think this is a potentially simple implementation. Disk Utility would just have to prompt and create that file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/761478/+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 890337] Re: gvfs-gdu-volume-monitor high cpu usage during raid-resync
http://bazaar.launchpad.net/~vcs-imports/gnome-disk- utility/master/view/head:/src/gdu/gdu-linux-lvm2-volume- group.c?start_revid=930 has the following comment in find_pvs(): 187/* TODO: do incremental list management instead of recomputing on 188 * each add/remove/change event 189 */ So seems it is recomputing all LVM PVS's on every single change event. Raid resync likely generates a ton of those (resync status %). Do all of those change events get queued and then processed slowly, consuming change events at far lower rate than they are being generated? ** Package changed: gvfs (Ubuntu) = gnome-disk-utility (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/890337 Title: gvfs-gdu-volume-monitor high cpu usage during raid-resync Status in “gnome-disk-utility” package in Ubuntu: New Bug description: During a raid-resync cpu usage is high - in fact gvfs-gdu-volume- monitor was using 100% cpu on one core for the duration of resync. Killed it with -SEGV to get something that can be retraced. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 23:36:38 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcCmdline: /usr/lib/gvfs/gvfs-gdu-volume-monitor ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SegvAnalysis: Segfault happened at: 0x7fca9329a3c3:jg 0x7fca9329a32e PC (0x7fca9329a3c3) ok source 0x7fca9329a32e (0x7fca9329a32e) ok SP (0x7fff9b1adac0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_source_attach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_idle_add_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgdu.so.0 ?? () from /usr/lib/libgdu.so.0 Title: gvfs-gdu-volume-monitor crashed with SIGSEGV in g_source_attach() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/890337/+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 896638] [NEW] Screen lock does not grab all keys
Public bug reported: When screen is locked with gnome screensaver, it is still possible to send Win-key event to the underlaying desktop. I think there should be no way to interact with the underlaying desktop without unlocking. To reproduce: 1. Start from Unity session. Make sure that Dash is not open. 2. Lock screen from the top-right gear button 3. Press shift to make the unlock dialog appear 4. Press Windows key 5. Type in your password and unlock the screen What should happen: The desktop should be in the same state it was left before the locking. Dash should not be open. What happens: Dash has been opened, i.e. the Windows key event was passed to desktop although it was locked. Wonder if it is possible to pass through any other key events. Didn't find any though with a quick test. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 26 19:01:25 2011 EcryptfsInUse: Yes ProcEnviron: LC_TIME=en_DK.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/896638 Title: Screen lock does not grab all keys Status in “gnome-screensaver” package in Ubuntu: New Bug description: When screen is locked with gnome screensaver, it is still possible to send Win-key event to the underlaying desktop. I think there should be no way to interact with the underlaying desktop without unlocking. To reproduce: 1. Start from Unity session. Make sure that Dash is not open. 2. Lock screen from the top-right gear button 3. Press shift to make the unlock dialog appear 4. Press Windows key 5. Type in your password and unlock the screen What should happen: The desktop should be in the same state it was left before the locking. Dash should not be open. What happens: Dash has been opened, i.e. the Windows key event was passed to desktop although it was locked. Wonder if it is possible to pass through any other key events. Didn't find any though with a quick test. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 26 19:01:25 2011 EcryptfsInUse: Yes ProcEnviron: LC_TIME=en_DK.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+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 896638] Re: Screen lock does not grab all keys
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/896638 Title: Screen lock does not grab all keys Status in “gnome-screensaver” package in Ubuntu: New Bug description: When screen is locked with gnome screensaver, it is still possible to send Win-key event to the underlaying desktop. I think there should be no way to interact with the underlaying desktop without unlocking. To reproduce: 1. Start from Unity session. Make sure that Dash is not open. 2. Lock screen from the top-right gear button 3. Press shift to make the unlock dialog appear 4. Press Windows key 5. Type in your password and unlock the screen What should happen: The desktop should be in the same state it was left before the locking. Dash should not be open. What happens: Dash has been opened, i.e. the Windows key event was passed to desktop although it was locked. Wonder if it is possible to pass through any other key events. Didn't find any though with a quick test. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 26 19:01:25 2011 EcryptfsInUse: Yes ProcEnviron: LC_TIME=en_DK.UTF-8 LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to oneiric on 2011-10-28 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/896638/+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 889779] [NEW] gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-resync
Public bug reported: After running palimpsest during a raid-resync cpu usage seemed high - in fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an hour). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 12:40:49 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/889779 Title: gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid- resync Status in “gvfs” package in Ubuntu: New Bug description: After running palimpsest during a raid-resync cpu usage seemed high - in fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an hour). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 12:40:49 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/889779/+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 889779] Re: gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid-resync
https://bugzilla.redhat.com/show_bug.cgi?id=575381 may be related. ** Bug watch added: Red Hat Bugzilla #575381 https://bugzilla.redhat.com/show_bug.cgi?id=575381 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/889779 Title: gvfs-gdu-volume-monitor high cpu usage after palimpsest / during raid- resync Status in “gvfs” package in Ubuntu: New Bug description: After running palimpsest during a raid-resync cpu usage seemed high - in fact gvfs-gdu-volume-monitor was using 100% cpu (for more than an hour). ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gvfs 1.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-12.51-generic 2.6.38.8 Uname: Linux 2.6.38-12-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sun Nov 13 12:40:49 2011 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-gdu-volume-monitor InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427) ProcEnviron: SHELL=/bin/bash LANGUAGE=en_IE:en LANG=en_IE.UTF-8 SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/889779/+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 880703] Re: Accepting calendar invitations fails with Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object
-- 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/880703 Title: Accepting calendar invitations fails with Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19 Status in “evolution” package in Ubuntu: New Bug description: When clicking Accept button on incoming calendar invitation the first click does nothing. Second click on the Accept button gives an error message Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19. An interesting finding is that before accepting calendar invitation the e-calendar-factory process was running with PID 12376: uomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:30 evolution tuomjarv 12376 1 0 10:54 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12441 11483 0 10:56 pts/100:00:00 grep --color=auto evolution After clicking the accept button the e-calendar-factory process seems to be running with PID 12446: tuomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:31 evolution tuomjarv 12446 1 0 10:56 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12451 11483 0 10:56 pts/100:00:00 grep --color=auto evolution Perhaps e-calendar-factory crashes when adding calendar entry to the calendar? The calendar in question is a google calendar. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 24 10:48:06 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-19 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/880703/+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 880703] [NEW] Accepting calendar invitations fails with Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on objec
Public bug reported: When clicking Accept button on incoming calendar invitation the first click does nothing. Second click on the Accept button gives an error message Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19. An interesting finding is that before accepting calendar invitation the e-calendar-factory process was running with PID 12376: uomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:30 evolution tuomjarv 12376 1 0 10:54 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12441 11483 0 10:56 pts/100:00:00 grep --color=auto evolution After clicking the accept button the e-calendar-factory process seems to be running with PID 12446: tuomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:31 evolution tuomjarv 12446 1 0 10:56 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12451 11483 0 10:56 pts/100:00:00 grep --color=auto evolution Perhaps e-calendar-factory crashes when adding calendar entry to the calendar? The calendar in question is a google calendar. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 24 10:48:06 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-19 (5 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- 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/880703 Title: Accepting calendar invitations fails with Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19 Status in “evolution” package in Ubuntu: New Bug description: When clicking Accept button on incoming calendar invitation the first click does nothing. Second click on the Accept button gives an error message Unable to send item to calendar 'calendar-name'. No such interface `org.gnome.evolution.dataserver.Calendar' on object at path /org/gnome/evolution/dataserver/Calendar/12376/19. An interesting finding is that before accepting calendar invitation the e-calendar-factory process was running with PID 12376: uomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:30 evolution tuomjarv 12376 1 0 10:54 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12441 11483 0 10:56 pts/100:00:00 grep --color=auto evolution After clicking the accept button the e-calendar-factory process seems to be running with PID 12446: tuomjarv@L343:~$ ps -aef | grep evolution tuomjarv 2314 1 0 Oct21 ?00:00:13 /usr/lib/evolution/e-addressbook-factory tuomjarv 2421 1856 0 Oct21 ?00:00:13 /usr/lib/evolution/3.2/evolution-alarm-notify tuomjarv 2596 1 2 Oct21 ?01:59:31 evolution tuomjarv 12446 1 0 10:56 ?00:00:00 /usr/lib/evolution/e-calendar-factory tuomjarv 12451 11483 0 10:56 pts/100:00:00 grep --color=auto evolution Perhaps e-calendar-factory crashes when adding calendar entry to the calendar? The calendar in question is a google calendar. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 24 10:48:06 2011 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to oneiric on 2011-10-19 (5 days ago) To manage notifications about this bug go to:
