[Desktop-packages] [Bug 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
With the revert, the network-manager ADT tests work again. https://autopkgtest.ubuntu.com/results/autopkgtest- jammy/jammy/amd64/n/network-manager/20220505_053118_fb2db@/log.gz ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
** Also affects: network-manager (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in network-manager source package in Jammy: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
This seems to be related to: "rfkill: make new event layout opt-in" in the -28 kernel. When I revert that a local reproduction run starts to work again. However I never got the same error pattern as in the ADT logs (those seem to get random data back from trying to read the MAC address). So a little doubt remains. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1971418] [NEW] network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
Public bug reported: This is a scripted bug report about ADT failures while running network- manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Invalid ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1971418 Title: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Invalid Bug description: This is a scripted bug report about ADT failures while running network-manager tests for linux/5.15.0-28.29 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/n/network-manager/20220503_090742_432dd@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/n/network-manager/20220429_062345_345a3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/n/network-manager/20220429_060513_fc2a9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971418/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Fix Committed
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
I am adding the block-proposed-bionic before this falls in between cracks. Right now we ended up in a situation where the nvidia-440 modules were added to the kernel lrm package build but the version used for the nvidia-390 modules was not updated to the proposed version. The hope is that having the meta from the driver package held back in proposed is less risk than releasing user-space for everything and not having the right modules in lrm. ** Tags added: block-proposed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux source package in Eoan: New Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR)
[Desktop-packages] [Bug 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()
Confirmed to be fixed. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1862169/+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 1862169] Re: rhythmbox crashed with SIGSEGV in build_flavored_key()
** Tags added: champagne -- 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/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in rhythmbox package in Ubuntu: Confirmed Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1862169/+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 1862169] [NEW] rhythmbox crashed with SIGSEGV in build_flavored_key()
Public bug reported: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6: movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: rhythmbox (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-crash focal -- 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/1862169 Title: rhythmbox crashed with SIGSEGV in build_flavored_key() Status in rhythmbox package in Ubuntu: Confirmed Bug description: Fresh Focal installation (amd64 deCusktop), after enabling the grilo framework from the plugins dialog. Currently every attempt to start rhythmbox again results in an immedate crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 6 14:30:21 2020 ExecutablePath: /usr/bin/rhythmbox InstallationDate: Installed on 2020-02-04 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) ProcCmdline: rhythmbox SegvAnalysis: Segfault happened at: 0x7fc7aade7dd6:movzbl (%rax),%eax PC (0x7fc7aade7dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: rhythmbox crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1862169/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
I did at least check the dkms install step on a trusty VM with lts- xenial kernel installed and the nvidia-304 driver installed. That did succeed. Similar testing for nvidia-340 and -384 but those were done for xenial VMs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1573508/+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 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
I am not convinced this is a ducplicate of bug #1797945. If I read that report correctly it is about upgraded Thunderbird with the external add- ons used. I *do* have both lightning and gcal provider from the Ubuntu archive (repeating from the description): xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) ** This bug is no longer a duplicate of bug 1797945 Lightning incompatible with Thunderbird 60.2.1 -- 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/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: Confirmed Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+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 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
Above is from apt upgrade log. So both went from 1:52.9.* to 1:60.2* -- 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/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: Confirmed Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+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 1798090] [NEW] Xenial update of thunderbird seems to have broken lightning/gdata provider
Public bug reported: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-07-09 (1559 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.2.1/20181010142946 (In use) RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-12-27 (658 days ago) dmi.bios.date: 10/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ZH77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7758 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider Status in thunderbird package in Ubuntu: New Bug description: After an update this morning (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) I seem to no longer have access to google calendars from lightning (both also upgraded) xul-ext-lightning:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) xul-ext-gdata-provider:amd64 (1:52.9.1+build3-0ubuntu0.16.04.1, 1:60.2.1+build1-0ubuntu0.16.04.4) When starting thunderbird on the command-line I get: [calBackendLoader] Using Thunderbird's builtin libical backend (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:34: Expected ')' in color definition (thunderbird:17633): Gtk-WARNING **: Theme parsing error: :1:77: Expected ')' in color definition JavaScript error: chrome://global/content/bindings/tree.xml, line 1285: TypeError: this.parentNode is null JavaScript error: chrome://messenger/content/mailWidgets.xml, line 2728: TypeError: this._parentMenupopup is null ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:60.2.1+build1-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: smb4703 F...m pulseaudio /dev/snd/controlC1: smb4703 F pulseaudio /dev/snd/pcmC0D0p: smb4703 F...m pulseaudio /dev/snd/controlC0: smb4703 F pulseaudio BuildID: 20181010142946 Channel: Unavailable CurrentDesktop: GNOME Date: Tue Oct 16 14:46:04 2018 EcryptfsInUse: Yes Extensions: extensions.sqlite
[Desktop-packages] [Bug 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu
Since we no longer produce i386 images, this would be hard to reproduce.
I could imagine the issue still exists but nobody is or will care.
Essentially a difference of what features are reported via cpuid and
what actually is implemented in the cpu emulation. Will close at least
the Ubuntu side.
** Changed in: llvm-toolchain-3.6 (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: qemu (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1448985
Title:
llvmpipe i386 crashes when running on qemu64 cpu
Status in QEMU:
Incomplete
Status in llvm-toolchain-3.6 package in Ubuntu:
Won't Fix
Status in qemu package in Ubuntu:
Won't Fix
Bug description:
STEPS TO REPRODUCE:
1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all
updates (it is a host system).
2. Download one (or all) isos:
* Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM =
a8a14f1f92c1ef35dae4966a2ae1a264).
* Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM =
4a3c4b8421af51c29c84fb6f4b3fe109)
* Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM =
6ea04093b767ad6778aa245d53625612)
3. Boot one (or all) isos with as QEMU-KVM guest with the following
commands:
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std
* sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware
* or from usb-creator-gtk via "Test disk" button
4. Click on "Try Ubuntu"
EXPECTED RESULTS:
ISO is booted to Unity desktop, user can test and use it.
ACTUAL RESULTS:
In 14.04 and 14.10 guests can see empty purple desktop or purple desktop
with two shortcuts ("Examples" and "Install Ubuntu ...").
15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740).
The reason for this is that unity requires gfx acceleration which is
done via llvmpipe on non accelerated gfx chipsets (as VMs use by
default). The error message is hidden away but is:
LLVM ERROR: Do not know how to split the result of this operator!
The cause is that KVM VMs by default use the qemu64 cpu model which
seems to be inconsistent in some way between claimed features and
actual results when using those features. A work-around for running
i386 isos is to use a cpu model like core2duo or kvm64.
This bug should be confirmed and fixed.
Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1448985/+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 1758366] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-38.43
test_wpa2_ip4 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv4 ... ok
test_wpa2_ip6 (__main__.ColdplugWifi)
WPA2, 802.11g, IPv6 with only RA ... ok
test_auto_detect_ap (__main__.Hotplug)
new AP is being detected automatically within 30s ... expected failure
test_auto_detect_eth (__main__.Hotplug)
new eth router is being detected automatically within 30s ... Cannot find
device "eth0"
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
from gi.repository import NetworkManager, NMClient, GLib
/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm:23: PyGIWarning: NMClient
was imported without specifying a version first. Use
gi.require_version('NMClient', '1.0') before import to ensure that the right
version gets loaded.
from gi.repository import NetworkManager, NMClient, GLib
expected failure
==
FAIL: test_wpa1_ip4 (__main__.ColdplugWifi)
WPA1, 802.11g, IPv4
--
Traceback (most recent call last):
File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 466, in
test_wpa1_ip4
''' % SSID, None, 54000, '12345678')
File
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line
359, in wrapped
args[0].wrap_process(fn, *args, **kwargs)
File
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line
263, in wrap_process
self.fail(f.read())
AssertionError: Traceback (most recent call last):
File
"/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/network_test_base.py", line
252, in wrap_process
fn(*args, **kwargs)
File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 540, in
do_test
ap = self.wait_ap(timeout=100)
File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 229, in
wait_ap
timeout=timeout)
File "/tmp/autopkgtest.7PohOa/build.MGv/src/debian/tests/nm", line 184, in
assertEventually
self.fail(message or 'timed out waiting for ' + str(condition))
File "/usr/lib/python3.6/unittest/case.py", line 670, in fail
raise self.failureException(msg)
AssertionError: timed out waiting for AP to be detected
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1758366
Title:
network-manager 1.8.4-1ubuntu3 ADT test failure with linux
4.13.0-38.43
Status in network-manager package in Ubuntu:
New
Bug description:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1758366/+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 1758366] [NEW] network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-38.43
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1758366 Title: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.13.0-38.43 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/n/network-manager/20180323_105026_adff0@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1758366/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: ubuntu-fan (Ubuntu)
Status: In Progress => Fix Committed
--
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/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
New
Status in chrony package in Ubuntu:
New
Status in clamav package in Ubuntu:
New
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
New
Status in ifmetric package in Ubuntu:
New
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
New
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Committed
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
New
Status in vzctl package in Ubuntu:
New
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
** Changed in: ubuntu-fan (Ubuntu)
Importance: Undecided => Medium
** Changed in: ubuntu-fan (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Stefan Bader (smb)
--
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/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
New
Status in chrony package in Ubuntu:
New
Status in clamav package in Ubuntu:
New
Status in controlaula package in Ubuntu:
New
Status in epoptes package in Ubuntu:
New
Status in ethtool package in Ubuntu:
New
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
New
Status in ifmetric package in Ubuntu:
New
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
New
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
New
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
New
Status in openssh package in Ubuntu:
New
Status in openvpn package in Ubuntu:
New
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
In Progress
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
New
Status in vzctl package in Ubuntu:
New
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1448985] Re: llvmpipe i386 crashes when running on qemu64 cpu
Since a simple work-around exists I think the importance can be lowered. ** Summary changed: - Ubuntu 14.04 LTS, 14.10, 15.04, 15.10 guests do not boot to Unity from QEMU-KVM Ubuntu 14.04 LTS, 14.10, 15.04 hosts + llvmpipe i386 crashes when running on qemu64 cpu ** Description changed: STEPS TO REPRODUCE: 1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all updates (it is a host system). 2. Download one (or all) isos: * Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = a8a14f1f92c1ef35dae4966a2ae1a264). * Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM = 4a3c4b8421af51c29c84fb6f4b3fe109) * Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM = 6ea04093b767ad6778aa245d53625612) 3. Boot one (or all) isos with as QEMU-KVM guest with the following commands: * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware * or from usb-creator-gtk via Test disk button 4. Click on Try Ubuntu EXPECTED RESULTS: ISO is booted to Unity desktop, user can test and use it. ACTUAL RESULTS: In 14.04 and 14.10 guests can see empty purple desktop or purple desktop with two shortcuts (Examples and Install Ubuntu ...). 15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740). + The reason for this is that unity requires gfx acceleration which is + done via llvmpipe on non accelerated gfx chipsets (as VMs use by + default). The error message is hidden away but is: + + LLVM ERROR: Do not know how to split the result of this operator! + + The cause is that KVM VMs by default use the qemu64 cpu model which + seems to be inconsistent in some way between claimed features and actual + results when using those features. A work-around for running i386 isos + is to use a cpu model like core2duo or kvm64. + This bug should be confirmed and fixed. Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox. ** Also affects: llvm-toolchain-3.6 (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Importance: High = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu. https://bugs.launchpad.net/bugs/1448985 Title: llvmpipe i386 crashes when running on qemu64 cpu Status in QEMU: New Status in llvm-toolchain-3.6 package in Ubuntu: New Status in qemu package in Ubuntu: Confirmed Bug description: STEPS TO REPRODUCE: 1. Install Ubuntu 14.04.2 LTS or Ubuntu 14.10 or Ubuntu 15.04 with all updates (it is a host system). 2. Download one (or all) isos: * Ubuntu 14.0.4.2 i386 iso (ubuntu-14.04.2-desktop-i386.iso, MD5SUM = a8a14f1f92c1ef35dae4966a2ae1a264). * Ubuntu 14.10 i386 iso (ubuntu-14.10-desktop-i386.iso, MD5SUM = 4a3c4b8421af51c29c84fb6f4b3fe109) * Ubuntu 15.04 i386 iso (ubuntu-15.04-desktop-i386.iso, MD5SUM = 6ea04093b767ad6778aa245d53625612) 3. Boot one (or all) isos with as QEMU-KVM guest with the following commands: * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga std * sudo kvm -m 1536 -cdrom ubuntu-*-desktop-i386.iso -vga vmware * or from usb-creator-gtk via Test disk button 4. Click on Try Ubuntu EXPECTED RESULTS: ISO is booted to Unity desktop, user can test and use it. ACTUAL RESULTS: In 14.04 and 14.10 guests can see empty purple desktop or purple desktop with two shortcuts (Examples and Install Ubuntu ...). 15.10 guest does not boot or boot to safe graphic mode (it is bug 1437740). The reason for this is that unity requires gfx acceleration which is done via llvmpipe on non accelerated gfx chipsets (as VMs use by default). The error message is hidden away but is: LLVM ERROR: Do not know how to split the result of this operator! The cause is that KVM VMs by default use the qemu64 cpu model which seems to be inconsistent in some way between claimed features and actual results when using those features. A work-around for running i386 isos is to use a cpu model like core2duo or kvm64. This bug should be confirmed and fixed. Users may want to run Ubuntu in QEMU/KVM, not just VirtualBox. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1448985/+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 1481294] Re: 14.04.3: in kvm install full disk from the i386 install when you go to login it returns you to the login page
*** This bug is a duplicate of bug 1448985 *** https://bugs.launchpad.net/bugs/1448985 Or actually kvm64 as model. I would be duping this bug report against the one I was looking into before as I think we got more details in that by now. ** This bug has been marked a duplicate of bug 1448985 llvmpipe i386 crashes when running on qemu64 cpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.6 in Ubuntu. https://bugs.launchpad.net/bugs/1481294 Title: 14.04.3: in kvm install full disk from the i386 install when you go to login it returns you to the login page Status in llvm-toolchain-3.6 package in Ubuntu: New Status in qemu package in Ubuntu: New Bug description: STEPS: 1. Grab the latest i386 image from http://cdimages.ubuntu.com/trusty/daily-live/current/ 2. Use qemu to create a cow2 image file for hdd 3. Run kvm -m 2048 -hda ubuntu-hda.qcow2 -cdrom trusty-desktop-i386.iso -boot d -vga vmware 4. Do a standard full disk install 5. Up on install close the session and change the command to kvm -m 2048 -hda ubuntu-hda.qcow2 -cdrom trusty-desktop-i386.iso -boot c -vga vmware 6. On the installed system try an login EXPECTED: I expect the system to login and display the Ubuntu desktop ACTUAL: You type in your password hit enter and the system briefly shows the ubuntu and dots page from start up and then returns you to the login page VERSIONS: http://cdimages.ubuntu.com/trusty/daily-live/current/trusty-desktop-i386.iso 252cb80c2ea1e5907369c0ed5fe0c57a *trusty-desktop-i386.iso To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1481294/+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 1473347] [NEW] Invalid MediaBox height when converting svg to pdf on i386
Public bug reported: When converting the example svg file into pdf on i386 there is a bug which causes the resulting MediaBox element to have an incredibly large height (looks like this might be an integer overflow). The expected height is around 423 which the 64bit test run is correctly producing. Testcase: attached script Results from i386 chroots: Precise:overflow Trusty: overflow Utopic: height ok (but text misplaced) Vivid: height ok (but text misplaced) Wily: overflow For Utopic and Vivid this seems only to result in visually unusable results (because text in some boxes is rendered all on one line) but for the other releases this would break the build of another package which tried to import the resulting pdf images into its auto-generated documentation. ** Affects: inkscape (Ubuntu) Importance: Undecided Status: New ** Attachment added: inkscape-test https://bugs.launchpad.net/bugs/1473347/+attachment/4427342/+files/inkscape-test -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1473347 Title: Invalid MediaBox height when converting svg to pdf on i386 Status in inkscape package in Ubuntu: New Bug description: When converting the example svg file into pdf on i386 there is a bug which causes the resulting MediaBox element to have an incredibly large height (looks like this might be an integer overflow). The expected height is around 423 which the 64bit test run is correctly producing. Testcase: attached script Results from i386 chroots: Precise: overflow Trusty: overflow Utopic: height ok (but text misplaced) Vivid:height ok (but text misplaced) Wily: overflow For Utopic and Vivid this seems only to result in visually unusable results (because text in some boxes is rendered all on one line) but for the other releases this would break the build of another package which tried to import the resulting pdf images into its auto-generated documentation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1473347/+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 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Alberto is rolling this back into older releases over time. To be fair it is an annoying issue but not one that is so fatal one would not be able to recover a system. In the majority of cases this ends up being just a false system issue notification. Because on kernel update the parallel builds are actually started 3 times. By now I just made it a habit of doing the following whenever kernel updates come in: - run dkms status to see whether both nvidia modules appear for the latest kernel (bbswitch is always there) - if one(or both) is missing, do sudo dkms install -m module -v module version -k kernel version (the name and versions taken from the dkms status report) - sudo rm /var/crash/*nvidia* to ignore the build failures before When the fixed version of the driver hits this can be noticed by having only one module reported by dkms for nvidia. The *-uvm one will be gone and the module it produced will be part of the remaining dkms module which then produces two kernel modules. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-346-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Trusty: Triaged Status in nvidia-graphics-drivers-331-updates source package in Trusty: Triaged Status in nvidia-graphics-drivers-340 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-340-updates source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346 source package in Trusty: Confirmed Status in nvidia-graphics-drivers-346-updates source package in Trusty: Confirmed Bug description: Filing this against the 340-updates version but possibly the same applies to older versions, too. The nvidia source package produces two individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm. The problem is that the DKMS build of the nvidia-uvm module runs compile steps inside the nvidia modules build directory. This is violating the DKMS assumption that each module can be build independently (there is no way of describing cross-modules dependencies and even more important, the autoinstall step after a new kernel is installed will run the modules build in parallel). Since nvidia and nvidia-uvm are very dependent on each other the right course of action seems to be to combine both sources in one DKMS module that produces two kernel modules (this is supported by DKMS). For the transition this resulting dkms package needs to have a breaks/replaces for the nvidia-uvm package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1374002] Re: After installing nvidia binary drivers lightdm does not start after reboot
That was actually a bug in udev (now part of systemd) which dropped an upstart script for the case of alternate graphics devices. This was fixed now. ** Changed in: lightdm (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1374002 Title: After installing nvidia binary drivers lightdm does not start after reboot Status in “lightdm” package in Ubuntu: Fix Released Bug description: Could be a duplicate of bug #873495 which has not, yet, gone past triaged status. But it has not been updated since last year and this just happened to me trying 14.10 (Utopic). Before installing the binary drivers, the nouveau driver was in use and lightdm started automatically. But then would crash the whole system somehow related to fading in popup menues. But that is another problem. Since the binary drivers are installed the system only boots into text mode. But is more stable after manually starting lightdm. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Sep 25 17:00:53 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1374002/+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 1375652] Re: [Utopic] nouveau flush timeout lockups
[ 6732.868007] mce: [Hardware Error]: CPU 0: Machine Check Exception: 4 Bank 4: b2070f0f [ 6732.868007] mce: [Hardware Error]: TSC 71912a367e5 [ 6732.868007] mce: [Hardware Error]: PROCESSOR 2:10ff0 TIME 1412263116 SOCKET 0 APIC 0 microcode 41 [ 6732.868007] mce: [Hardware Error]: Run the above through 'mcelog --ascii' [ 6732.868007] mce: [Hardware Error]: Machine check: Processor context corrupt [ 6732.868007] Kernel panic - not syncing: Fatal machine check on current CPU [ 6732.868007] Kernel Offset: 0x0 from 0xc100 (relocation range: 0xc000-0xf83fdfff) Just as additional data, this happened when trying to reboot via serial console. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1375652 Title: [Utopic] nouveau flush timeout lockups Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Needs more investigation but the system feels sluggish (video operations not always smooth). This morning I had a crash in firefox (may not be related) and it does not always seem to be reproducible. Yesterday I was able to run glxgears and play a video stream through firefox for quite some time without issues. So HW failure from old age might be a reason, too. With the initial install the lockups always seemed to happen when opening a selection dropbox (like the timeout for blanking the screen in the settings). Yesterday (after getting console to be a serial one) the lockup happened on the youtube front-page. After a reboot it did not happen again and today (after dist-upgrading) it just happened again (on some youtube page). For yesterday and today, mouse still moved but gui was not responding. Also would not allow to switch to any vt. Serial console was still working and showed: nouveau [W_PCIEGART] [:01:00.0] flush timeout, 0x0002 Today also (after a while): nouveau E[Xorg[1500]] failed to idle channel 0x [Xorg[1500]] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 30 10:40:50 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2a0c] InstallationDate: Installed on 2014-09-25 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) Lsusb: Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller Bus 002 Device 002: ID 8054:0001 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic root=/dev/mapper/username--vg-root ro priority=low hpet=force console=ttyS0,115200n8 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1006 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1006:bd03/03/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3
[Desktop-packages] [Bug 1375652] Re: [Utopic] nouveau flush timeout lockups
After a cold boot today. Things looked relatively good for quite a while
(menus, youtube and glmark2). But while running glmark2 (for several
iterations):
[ 5792.435913] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.515102] nouveau E[Xorg[1377]] cal_space: -16
[ 5792.597439] nouveau E[Xorg[1377]] cal_space: -16
[ 5919.120788] nouveau E[ DRM] GPU lockup - switching to software fbcon
[ 5954.064011] nouveau E[Xorg[1377]] failed to idle channel 0x
[Xorg[1377]]
[ 5969.076012] nouveau E[Xorg[1377]] failed to idle channel 0x
[Xorg[1377]]
[ 5984.404012] nouveau E[glmark2[3468]] failed to idle channel 0x
[glmark2[3468]]
[ 5999.504012] nouveau E[glmark2[3468]] failed to idle channel 0x
[glmark2[3468]]
[ 5999.515772] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x02fc data 0x0003
[ 5999.525983] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x0300 data 0x000a
[ 5999.536167] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x0304 data 0x0d001000
[ 5999.546339] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x0308 data 0x0f49
[ 5999.556519] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x030c data 0x017f
[ 5999.566688] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0300 data 0x
[ 5999.576862] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0304 data 0x0026000a
[ 5999.587045] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0308 data 0x001a0320
[ 5999.597221] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x030c data 0x01824000
[ 5999.607402] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0300 data 0x001a
[ 5999.617569] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0304 data 0x000a
[ 5999.627750] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 4 mthd 0x0308 data 0x023e0320
[ 5999.637918] nouveau E[ PFIFO][:01:00.0] CACHE_ERROR - ch 1
[Xorg[3591]] subc 2 mthd 0x030c data 0x017f
[ 6014.740012] nouveau E[compiz[2101]] failed to idle channel 0x
[compiz[2101]]
[ 6029.756013] nouveau E[compiz[2101]] failed to idle channel 0x
[compiz[2101]]
[ 6030.088616] ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 6030.095694] ata7.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392
in
[ 6030.095694] res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4
(timeout)
[ 6030.110361] ata7.00: status: { DRDY }
The ata timeout seems to be recovered. but after first falling back to a
textual console, I ended with something that is random colourful garbage
on screen. Serial console and ssh, still up. So this might be a
completely different failure caused by me using glmark2 (which I had not
before). And with the initial case(s) the lockup was complete and ssh
would not work anymore.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1375652
Title:
[Utopic] nouveau flush timeout lockups
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
New
Bug description:
Needs more investigation but the system feels sluggish (video operations not
always smooth). This morning I had a crash in firefox (may not be related) and
it does not always seem to be reproducible. Yesterday I was able to run
glxgears and play a video stream through firefox for quite some time without
issues. So HW failure from old age might be a reason, too.
With the initial install the lockups always seemed to happen when opening a
selection dropbox (like the timeout for blanking the screen in the settings).
Yesterday (after getting console to be a serial one) the lockup happened on the
youtube front-page. After a reboot it did not happen again and today (after
dist-upgrading) it just happened again (on some youtube page).
For yesterday and today, mouse still moved but gui was not responding.
Also would not allow to switch to any vt. Serial console was still
working and showed:
nouveau [W_PCIEGART] [:01:00.0] flush timeout, 0x0002
Today also (after a while):
nouveau E[Xorg[1500]] failed to idle channel 0x [Xorg[1500]]
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
Uname: Linux 3.16.0-18-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
[Desktop-packages] [Bug 1375652] Re: [Utopic] nouveau flush timeout lockups
Ok, so the same happens when running a glmark2 loop with a 3.13 kernel. So not related to the problem I initially had. I would say that was quicker to trigger and seems to be gone with the latest kernels in Utopic. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1375652 Title: [Utopic] nouveau flush timeout lockups Status in “xserver-xorg-video-nouveau” package in Ubuntu: Fix Released Bug description: Needs more investigation but the system feels sluggish (video operations not always smooth). This morning I had a crash in firefox (may not be related) and it does not always seem to be reproducible. Yesterday I was able to run glxgears and play a video stream through firefox for quite some time without issues. So HW failure from old age might be a reason, too. With the initial install the lockups always seemed to happen when opening a selection dropbox (like the timeout for blanking the screen in the settings). Yesterday (after getting console to be a serial one) the lockup happened on the youtube front-page. After a reboot it did not happen again and today (after dist-upgrading) it just happened again (on some youtube page). For yesterday and today, mouse still moved but gui was not responding. Also would not allow to switch to any vt. Serial console was still working and showed: nouveau [W_PCIEGART] [:01:00.0] flush timeout, 0x0002 Today also (after a while): nouveau E[Xorg[1500]] failed to idle channel 0x [Xorg[1500]] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 30 10:40:50 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2a0c] InstallationDate: Installed on 2014-09-25 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) Lsusb: Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller Bus 002 Device 002: ID 8054:0001 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic root=/dev/mapper/username--vg-root ro priority=low hpet=force console=ttyS0,115200n8 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1006 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1006:bd03/03/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Sep 30 10:39:42 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04d9:1400KEYBOARD, id 8 inputHID 04d9:1400
[Desktop-packages] [Bug 1375652] [NEW] [Utopic] nouveau flush timeout lockups
Public bug reported: Needs more investigation but the system feels sluggish (video operations not always smooth). This morning I had a crash in firefox (may not be related) and it does not always seem to be reproducible. Yesterday I was able to run glxgears and play a video stream through firefox for quite some time without issues. So HW failure from old age might be a reason, too. With the initial install the lockups always seemed to happen when opening a selection dropbox (like the timeout for blanking the screen in the settings). Yesterday (after getting console to be a serial one) the lockup happened on the youtube front-page. After a reboot it did not happen again and today (after dist-upgrading) it just happened again (on some youtube page). For yesterday and today, mouse still moved but gui was not responding. Also would not allow to switch to any vt. Serial console was still working and showed: nouveau [W_PCIEGART] [:01:00.0] flush timeout, 0x0002 Today also (after a while): nouveau E[Xorg[1500]] failed to idle channel 0x [Xorg[1500]] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 30 10:40:50 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation NV41 [GeForce 6800] [10de:00c1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:2a0c] InstallationDate: Installed on 2014-09-25 (4 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) Lsusb: Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:1400 Holtek Semiconductor, Inc. PS/2 keyboard + mouse controller Bus 002 Device 002: ID 8054:0001 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-18-generic root=/dev/mapper/username--vg-root ro priority=low hpet=force console=ttyS0,115200n8 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS A8N-SLI DELUXE ACPI BIOS Revision 1006 dmi.board.name: A8N-SLI DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSA8N-SLIDELUXEACPIBIOSRevision1006:bd03/03/2005:svnSystemmanufacturer:pnSystemname:pvr1.XX:rvnASUSTeKComputerINC.:rnA8N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System name dmi.product.version: 1.XX dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Sep 30 10:39:42 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04d9:1400KEYBOARD, id 8 inputHID 04d9:1400KEYBOARD, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: nouveau ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1375652 Title: [Utopic] nouveau flush timeout lockups Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Needs more investigation but
[Desktop-packages] [Bug 1374002] [NEW] After installing nvidia binary drivers lightdm does not start after reboot
Public bug reported: Could be a duplicate of bug #873495 which has not, yet, gone past triaged status. But it has not been updated since last year and this just happened to me trying 14.10 (Utopic). Before installing the binary drivers, the nouveau driver was in use and lightdm started automatically. But then would crash the whole system somehow related to fading in popup menues. But that is another problem. Since the binary drivers are installed the system only boots into text mode. But is more stable after manually starting lightdm. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Sep 25 17:00:53 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1374002 Title: After installing nvidia binary drivers lightdm does not start after reboot Status in “lightdm” package in Ubuntu: New Bug description: Could be a duplicate of bug #873495 which has not, yet, gone past triaged status. But it has not been updated since last year and this just happened to me trying 14.10 (Utopic). Before installing the binary drivers, the nouveau driver was in use and lightdm started automatically. But then would crash the whole system somehow related to fading in popup menues. But that is another problem. Since the binary drivers are installed the system only boots into text mode. But is more stable after manually starting lightdm. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Sep 25 17:00:53 2014 InstallationDate: Installed on 2014-09-25 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha i386 (20140923) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1374002/+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 1369575] Re: Regression/Trusty: Ultron un-1 most keys no longer recognized
** Package changed: ubuntu = ibus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1369575 Title: Regression/Trusty: Ultron un-1 most keys no longer recognized Status in “ibus” package in Ubuntu: New Bug description: Device: Ultron un-1 (USB Calculator/numerical keypad) [0603:0002] The keypad was working on 12.04 (Precise) but on 14.04 (Trusty) most keys do not work under Unity. They do work in the password dialog of lightdm and when switching to VT console. I am attaching input-events output from a shell window under Unity and running from the VT. It appears to me like the device tries to enforce num-lock status on each keypress and on the console this causes a led event as feedback. This seems to be missing when doing the same under Unity for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1369575/+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 1292467] Re: Dual screen greeter can break 3D acceleration
Hi Patricia, that was only the release-notes task. So we just noted wrote down there that this can happen and how to work around it. I have not seen or heard anyone fixing (or even looking at) the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in Release Notes for Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). WORKAROUND: * Plug in external monitor after login (1) * Boot with video=LVDS-1:d (2) (1) Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. (2) This will completely disable the internal screen for that boot. It cannot be enabled through the settings dialogue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+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 1342094] Re: Audio extraction into mp3 ignores profiles
Setting package to rhythmbox to have a starting point. It probably is wrong and should be some part of the gstreamer set. But I don't know which one. ** Package changed: ubuntu = rhythmbox (Ubuntu) -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] Re: Audio extraction into mp3 ignores profiles
apport information ** Tags added: apport-collected trusty ** Description changed: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). - Regardless of the profile, this always produces VBR encoded MP3 files - which also lack Xing header information which will lead to incorrect - runtime display on some players. I believe the problem lies in the - gstreamer filters used and rhythmbox is just one of the applications - affected. The problem exists for quite a while now, though older - releases would sometime not even have any profiles selectable in the - GUI. + Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2014-07-09 (6 days ago) + InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) + Package: rhythmbox 3.0.2-0ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 + Tags: trusty + Uname: Linux 3.13.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo + _MarkForUpload: True ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1342094/+attachment/4153328/+files/Dependencies.txt -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1342094/+attachment/4153332/+files/XorgLog.txt -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] GstreamerVersions.txt
apport information ** Attachment added: GstreamerVersions.txt https://bugs.launchpad.net/bugs/1342094/+attachment/4153329/+files/GstreamerVersions.txt -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1342094/+attachment/4153331/+files/ProcEnviron.txt -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] LogAlsaMixer.txt
apport information ** Attachment added: LogAlsaMixer.txt https://bugs.launchpad.net/bugs/1342094/+attachment/4153330/+files/LogAlsaMixer.txt -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1342094] Re: Audio extraction into mp3 ignores profiles
Reading that file it looks like I would be unsure again whether it is a problem with the interface or other. Though both options seem to keep the bug reported against rhythmbox. So in doubt I ran apport- collect and selected other. -- 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/1342094 Title: Audio extraction into mp3 ignores profiles Status in “rhythmbox” package in Ubuntu: New Bug description: Up-to-date 14.04 (Trusty) desktop installation (64bit), used enable 3rd party software when installing Testcase: Using rhythmbox to extract audio tracks from a audio CD into the library as mp3. The GUI shows several profiles (default, ubuntu, vbr, cbr). Regardless of the profile, this always produces VBR encoded MP3 files which also lack Xing header information which will lead to incorrect runtime display on some players. I believe the problem lies in the gstreamer filters used and rhythmbox is just one of the applications affected. The problem exists for quite a while now, though older releases would sometime not even have any profiles selectable in the GUI. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (6 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: rhythmbox 3.0.2-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Tags: trusty Uname: Linux 3.13.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1342094/+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 1319061] [NEW] Printing pdf documents from firefox embedded viewer results in empty pages
Public bug reported: This is on updated 12.04.4 (Precise) 64bit. Not sure exactly since when but it had been working at some point. Testcase: Open a pdf document in Firefox with the browser set to embedded display (so Firefox uses its own viewer). Select print (either the toolbar in the viewer or from the Firefox menu, it did not matter. As a result only empty pages will be produced (tested with a Samsung CLP-325 and a HP LaserJet 1522). Printing does work when using evince. Note: Beside of the now completely failing print there seems to be an additional issue which always produces an additional empty page. IOW same doc has two pages when printing from Firefox but one when printing from evince. The problem seemed to have started with the additional blank page and now ended in all pages being blank. ** 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/1319061 Title: Printing pdf documents from firefox embedded viewer results in empty pages Status in “firefox” package in Ubuntu: New Bug description: This is on updated 12.04.4 (Precise) 64bit. Not sure exactly since when but it had been working at some point. Testcase: Open a pdf document in Firefox with the browser set to embedded display (so Firefox uses its own viewer). Select print (either the toolbar in the viewer or from the Firefox menu, it did not matter. As a result only empty pages will be produced (tested with a Samsung CLP-325 and a HP LaserJet 1522). Printing does work when using evince. Note: Beside of the now completely failing print there seems to be an additional issue which always produces an additional empty page. IOW same doc has two pages when printing from Firefox but one when printing from evince. The problem seemed to have started with the additional blank page and now ended in all pages being blank. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1319061/+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 1319061] Re: Printing pdf documents from firefox embedded viewer results in empty pages
Same happens on an updated 14.04 system. So very much related to the Firefox version. -- 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/1319061 Title: Printing pdf documents from firefox embedded viewer results in empty pages Status in “firefox” package in Ubuntu: New Bug description: This is on updated 12.04.4 (Precise) 64bit. Not sure exactly since when but it had been working at some point. Testcase: Open a pdf document in Firefox with the browser set to embedded display (so Firefox uses its own viewer). Select print (either the toolbar in the viewer or from the Firefox menu, it did not matter. As a result only empty pages will be produced (tested with a Samsung CLP-325 and a HP LaserJet 1522). Printing does work when using evince. Note: Beside of the now completely failing print there seems to be an additional issue which always produces an additional empty page. IOW same doc has two pages when printing from Firefox but one when printing from evince. The problem seemed to have started with the additional blank page and now ended in all pages being blank. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1319061/+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 1292467] Re: Dual screen greeter can break 3D acceleration
** Description changed: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side-by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). - Booting with only the internal screen and then plugging in the external - one after login seems to handle this better (although I probably need to - remove any previous config to get into a kind of vanilla state again). - Also it seems to be ok when I had the dual monitor boot and lightdm - coming up side-by-side, when unplugging the external monitor before - logging in. + WORKAROUND: + * Plug in external monitor after login (1) + * Boot with video=LVDS-1:d (2) - So logging in with the dual-monitor side-by-side setup causes 3D - acceleration to be broken for that session (even when it switches to - single monitor by configuration). However going back to lightdm, - unplugging the external monitor, then log in and reconnect the external - monitor is ok. + (1) Booting with only the internal screen and then plugging in the + external one after login seems to handle this better (although I + probably need to remove any previous config to get into a kind of + vanilla state again). Also it seems to be ok when I had the dual monitor + boot and lightdm coming up side-by-side, when unplugging the external + monitor before logging in. + + (2) This will completely disable the internal screen for that boot. It + cannot be enabled through the settings dialogue. ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in Release Notes for Ubuntu: New Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). WORKAROUND: * Plug in external monitor after login (1) * Boot with video=LVDS-1:d (2) (1) Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. (2) This will completely disable the internal screen for that boot. It cannot be enabled through the settings dialogue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1292467/+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 1298517] Re: Rendering issues in unity with xserver-modeset
And oddly its only gnome-term. Xterm is ok. -- 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/1298517 Title: Rendering issues in unity with xserver-modeset Status in “mesa” package in Ubuntu: Triaged Bug description: Starting to report this against unity, feel free to re-assign against the correct package (the xserver or llvm-pipe?). With the current Trusty image (64bit) installed into a VM (KVM or Xen) that uses the default Cirrus graphics (using virt-managers VNC viewer), I see at least two issues: 1. Occasionally (not sure how to force it to happen) the mouse pointer will not be rendered while input grab is active. This leaves no indication about where the mouse pointer is. In some cases it seemed to help when I switched to a text console and back. 2. Near to unreadable gnome terminal sessions. Background seems half transparent, half unset. Text barely readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1298517/+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 1298517] Re: Rendering issues in unity with xserver-modeset
I tested today with Xen and cirrus or svga and both show the same bug. ** Attachment added: Screenshot from 2014-04-16 18:37:17.png https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1298517/+attachment/4085585/+files/Screenshot%20from%202014-04-16%2018%3A37%3A17.png -- 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/1298517 Title: Rendering issues in unity with xserver-modeset Status in “mesa” package in Ubuntu: Triaged Bug description: Starting to report this against unity, feel free to re-assign against the correct package (the xserver or llvm-pipe?). With the current Trusty image (64bit) installed into a VM (KVM or Xen) that uses the default Cirrus graphics (using virt-managers VNC viewer), I see at least two issues: 1. Occasionally (not sure how to force it to happen) the mouse pointer will not be rendered while input grab is active. This leaves no indication about where the mouse pointer is. In some cases it seemed to help when I switched to a text console and back. 2. Near to unreadable gnome terminal sessions. Background seems half transparent, half unset. Text barely readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1298517/+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 1292467] Re: Dual screen greeter can break 3D acceleration
** Summary changed: - Duel screen greeter can break 3D acceleration + Dual screen greeter can break 3D acceleration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1292467/+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 1292467] Re: Dual screen greeter can break 3D acceleration
Should we add something to the release notes? Maybe like this: Some laptops or netbooks with older graphics can experience bad graphical performance when starting with a high resolution external monitor attached. The reason for this is that some graphics cards (like the Intel 945GSE for example) cannot support accelerated 3D graphics when the combined width of both screens exceeds a certain threshold (2048 pixels in the example above). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Dual screen greeter can break 3D acceleration Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1292467/+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 1272312] Re: [Trusty] Auto-download dialog does not find current mp3 plugins
Verified with a current Trusty iso. Looks to be fixed now. ** Changed in: rhythmbox (Ubuntu) Status: Incomplete = Fix Released -- 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/1272312 Title: [Trusty] Auto-download dialog does not find current mp3 plugins Status in “rhythmbox” package in Ubuntu: Fix Released Bug description: After a fresh install, adding any source that is in mp3 encoding, the dialog that offers to download the plugin will fail to find it. Manually installing gstreamer1.0-fluendo-mp3 does make mp3 sources play. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 07:42:03 2014 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1272312/+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 1298517] [NEW] Rendering issues in unity with xserver-modeset
Public bug reported: Starting to report this against unity, feel free to re-assign against the correct package (the xserver or llvm-pipe?). With the current Trusty image (64bit) installed into a VM (KVM or Xen) that uses the default Cirrus graphics (using virt-managers VNC viewer), I see at least two issues: 1. Occasionally (not sure how to force it to happen) the mouse pointer will not be rendered while input grab is active. This leaves no indication about where the mouse pointer is. In some cases it seemed to help when I switched to a text console and back. 2. Near to unreadable gnome terminal sessions. Background seems half transparent, half unset. Text barely readable. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1298517 Title: Rendering issues in unity with xserver-modeset Status in “unity” package in Ubuntu: New Bug description: Starting to report this against unity, feel free to re-assign against the correct package (the xserver or llvm-pipe?). With the current Trusty image (64bit) installed into a VM (KVM or Xen) that uses the default Cirrus graphics (using virt-managers VNC viewer), I see at least two issues: 1. Occasionally (not sure how to force it to happen) the mouse pointer will not be rendered while input grab is active. This leaves no indication about where the mouse pointer is. In some cases it seemed to help when I switched to a text console and back. 2. Near to unreadable gnome terminal sessions. Background seems half transparent, half unset. Text barely readable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298517/+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 1292467] Re: Lightdm on dual-screens can break 3D acceleration
** Changed in: lightdm (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Lightdm on dual-screens can break 3D acceleration Status in “lightdm” package in Ubuntu: New Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292467/+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 1292467] [NEW] Lightdm on dual-screens can break 3D acceleration
Public bug reported: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side-by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1292467 Title: Lightdm on dual-screens can break 3D acceleration Status in “lightdm” package in Ubuntu: New Bug description: When booting with two screens (internal LVDS and VGA), lightdm comes up in a mode where it displays separate screen content on both displays (so no mirror mode). These screens seem to be arranged side- by-side regardless of the fact that (like in my case) the combined width can be greater than 2048 and that is not supported with 3D acceleration at least on that older i945GME graphics. This results in very poor graphics performance and compiz using a lot of cpu cycles (which are rather limited on this Atom N270 anyways). Even worse, this does not get resolved when changing the setup in system settings to either only having one screen active or arranging them on top of each other). Booting with only the internal screen and then plugging in the external one after login seems to handle this better (although I probably need to remove any previous config to get into a kind of vanilla state again). Also it seems to be ok when I had the dual monitor boot and lightdm coming up side-by-side, when unplugging the external monitor before logging in. So logging in with the dual-monitor side-by-side setup causes 3D acceleration to be broken for that session (even when it switches to single monitor by configuration). However going back to lightdm, unplugging the external monitor, then log in and reconnect the external monitor is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1292467/+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 1291930] [NEW] Menus do not work while VNC screen of virt-manager is active
Public bug reported: Release: Trusty (updated 2013-03-13 11:00 UTC) Architecture: amd64 Testcase: Start virt-manager and launch a VM guest. While the VNC graphical terminal is active, the menus do not work (neither top bar, nor window bar). When switching away from graphical screen (the window has a kind of tools bar, from that for example the blue info/config button brings up config details) the menus start working. And fail again when the graphical screen is brought back. ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1291930 Title: Menus do not work while VNC screen of virt-manager is active Status in “unity” package in Ubuntu: Confirmed Bug description: Release: Trusty (updated 2013-03-13 11:00 UTC) Architecture: amd64 Testcase: Start virt-manager and launch a VM guest. While the VNC graphical terminal is active, the menus do not work (neither top bar, nor window bar). When switching away from graphical screen (the window has a kind of tools bar, from that for example the blue info/config button brings up config details) the menus start working. And fail again when the graphical screen is brought back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291930/+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 1291942] [NEW] One time short-cuts doalog has close button without function
Public bug reported: The latest updates cause a short-cuts dialogue to appear automatically on the next login. Unlike the similar box which appears on holding the super key long, this one has a decoration that looks like a dismissal button. But it does nothing when clicking to it. It seems the window goes away automatically after a bit but it is confusing. ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1291942 Title: One time short-cuts doalog has close button without function Status in “unity” package in Ubuntu: Confirmed Bug description: The latest updates cause a short-cuts dialogue to appear automatically on the next login. Unlike the similar box which appears on holding the super key long, this one has a decoration that looks like a dismissal button. But it does nothing when clicking to it. It seems the window goes away automatically after a bit but it is confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1291942/+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 1272312] [NEW] [Trusty] Auto-download dialog does not find current mp3 plugins
Public bug reported: After a fresh install, adding any source that is in mp3 encoding, the dialog that offers to download the plugin will fail to find it. Manually installing gstreamer1.0-fluendo-mp3 does make mp3 sources play. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 07:42:03 2014 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1272312 Title: [Trusty] Auto-download dialog does not find current mp3 plugins Status in “rhythmbox” package in Ubuntu: New Bug description: After a fresh install, adding any source that is in mp3 encoding, the dialog that offers to download the plugin will fail to find it. Manually installing gstreamer1.0-fluendo-mp3 does make mp3 sources play. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 24 07:42:03 2014 SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1272312/+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 1222602] Re: [gen3] Bad performance on GMA950 and GMA3150
Just to confirm that the work-around described in the upstream bug (set MESA_GL_VERSION_OVERRIDE=1.4 in /etc/environment) works on my GMA950 based netbook). -- 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/1222602 Title: [gen3] Bad performance on GMA950 and GMA3150 Status in Mesa: Unknown Status in “mesa” package in Ubuntu: Confirmed Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1170023] [NEW] [Regression] Rhythmbox does not play m3u link
Public bug reported: In Raring, the following link (http://mp3-live.swr3.de/swr3_m.m3u) added as a radio station will show (paused) in the title as soon as playback is pressed (32bit and 64bit). This did work at least back in Precise. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Wed Apr 17 17:38:58 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-28 (384 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120323) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: Upgraded to raring on 2013-01-10 (96 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring third-party-packages -- 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/1170023 Title: [Regression] Rhythmbox does not play m3u link Status in “rhythmbox” package in Ubuntu: New Bug description: In Raring, the following link (http://mp3-live.swr3.de/swr3_m.m3u) added as a radio station will show (paused) in the title as soon as playback is pressed (32bit and 64bit). This did work at least back in Precise. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: rhythmbox 2.98-0ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Wed Apr 17 17:38:58 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-03-28 (384 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120323) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: Upgraded to raring on 2013-01-10 (96 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1170023/+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 1086345] Re: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot
Here you go... ** Attachment added: Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1086345/+attachment/3451966/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1086345 Title: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot Status in “lightdm” package in Ubuntu: New Bug description: Hardware is an Hashwell SDP with an Intel SSD. Fresh install from 12.04.1 alternate image, then added the quantal-lts kernel and the x-stack (ppa:ubuntu-x-swat/q-lts-backport, pulled via xserver-xorg- lts-quantal meta package). Monitor is connected to VGA. With the new stack graphics on VGA does actually work and the system snaps from the grub-efi prompt to lightdm in a blink (2s at most which probably can be attributed to the Intel SSD). Everything is fine and the system definitely is running in a high resolution mode. However when shutting down or rebooting, the system drops into a screen telling me it is running in low-resolution mode instead of showing plymouth (or the terminal). The system will continue to shut down or reboot even without pressing the ok button, but it can be done for a bit and then would show the next screen about how to resolve the issue. I was not quick or daring enough to go on from the second screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: plymouth 0.8.2-2ubuntu30 ProcVersionSignature: Ubuntu 3.5.0-20.31~hswv4-generic 3.5.7 Uname: Linux 3.5.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Tue Dec 4 12:44:55 2012 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) Lsusb: Bus 001 Device 002: ID 0b39:cd02 Omnidirectional Control Technology, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Intel Corporation Shark Bay Client platform MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2012 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0086.R00.1208052028 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0086.R00.1208052028:bd08/05/2012:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1086345/+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 1080588] Re: jockey suggests not installable packages on renamed stack
While I did not find the package uploaded to proposed, yet, I took the packages from the link posted in PM and can confirm that it fixes the regression I saw. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Re: jockey suggests not installable packages on renamed stack
After upgrading to the proposed version jockey-text -l (for example) starts failing for me. The 0.9.7-0ubuntu7.4 version does work. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Re: jockey suggests not installable packages on renamed stack
.tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz DistUpgraded: 2012-02-24 11:29:43,553 DEBUG enabling apt cron job DistroCodename: precise DistroRelease: Ubuntu 12.04 DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.2.0-34-generic, x86_64: installed virtualbox, 4.1.12, 3.2.0-33-generic, x86_64: installed virtualbox, 4.1.12, 3.2.0-34-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices [AMD] nee ATI Cedar PRO [Radeon HD 5450] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device [174b:e157] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) JockeyStatus: kmod:fglrx_experimental_9 - Experimental AMD binary Xorg driver and kernel module (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Disabled, Not in use) xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True NonfreeKernelModules: fglrx Package: nvidia-graphics-drivers-updates (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-34-generic root=UUID=2eab68c5-c6fa-405d-a360-1f6f1690bbb3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Tags: precise running-unity precise running-unity ubuntu referred-by-support compiz-0.9 Uname: Linux 3.2.0-34-generic x86_64 UpgradeStatus: Upgraded to precise on 2012-02-24 (272 days ago) UserGroups: adm admin cdrom chroot dialout floppy libvirtd lp lpadmin plugdev sambashare sbuild sudo video dmi.bios.date: 12/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: M3A-GLAN dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/21/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A-GLAN:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Tags added: apport-collected compiz-0.9 precise referred-by-support running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an
[Desktop-packages] [Bug 1080588] .var.log.jockey.log.txt
apport information ** Attachment added: .var.log.jockey.log.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441886/+files/.var.log.jockey.log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441889/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] BootLog.gz
apport information ** Attachment added: BootLog.gz https://bugs.launchpad.net/bugs/1080588/+attachment/3441888/+files/BootLog.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Devices.txt
apport information ** Attachment added: Devices.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441890/+files/Devices.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] LightdmLog.txt
apport information ** Attachment added: LightdmLog.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441893/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441894/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441895/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] GconfCompiz.txt
apport information ** Attachment added: GconfCompiz.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441892/+files/GconfCompiz.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] DpkgLog.txt
apport information ** Attachment added: DpkgLog.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441891/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441898/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] MonitorsUser.xml.txt
apport information ** Attachment added: MonitorsUser.xml.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441896/+files/MonitorsUser.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441897/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441899/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441900/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441901/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441902/+files/UdevLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] UnitySupportTest.txt
apport information ** Attachment added: UnitySupportTest.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441903/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] XorgConf.txt
apport information ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441904/+files/XorgConf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441907/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441908/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441905/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1080588] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/1080588/+attachment/3441906/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1080588/+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 1043513] Re: Xorg crashed with SIGABRT in memcpy() via cirRefreshArea() under KVM virtual machine
Things also became better with the Cirrus driver and VMs. After being able to login I noticed that my KVM VM (which runs on a rather power efficient, iow not too fast, machine) still has occasional crashes of this type. And there you can see (and have to wait) every graphical goodness like fading in and out or docking. While the host I run the Xen VM (which uses the same cirrus emulation) runs rather smoothly (because it has more CPU power) and I think I did not see any crash, yet. That somehow leads me to believe this could be a problem (in the cirrus case) of the communication between X driver, llvm-pipe and the emulated card being overrun in some way. Not sure how this relates to the nouveau case. I would not think the X driver could be too fast for the 3D pipe in hardware. But maybe this gives X driver people a hint. -- 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/1043513 Title: Xorg crashed with SIGABRT in memcpy() via cirRefreshArea() under KVM virtual machine Status in “xorg-server” package in Ubuntu: Confirmed Bug description: No login possible on KVM-based virtual machine (with virt-manager) and network settings Source device: Host device eth2 : macvtap Device model: virtio Source mode: VEPA With source mode set to Default it works. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.12.99.905-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDmesg: [3.809292] init: plymouth-stop pre-start process (1197) terminated with status 1 [5.314446] hda-intel: Invalid position buffer, using LPIB read method instead. [9.269441] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Wed Aug 29 22:04:57 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-13-generic root=UUID=2258d315-c1f3-4f2c-b925-01ab5cdf448d ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 cirRefreshArea () from /usr/lib/xorg/modules/drivers/cirrus_drv.so ?? () from /usr/lib/xorg/modules/libshadowfb.so ?? () ?? () Title: Xorg crashed with SIGABRT in cirRefreshArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1043513/+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 1029582] Re: Unusable graphics with ATI RS690M
Ok, seems that the problem is somewhere in the radeon driver in the kernel as installing a 3.2 kernel would boot with usable graphics. Though frankly that is still X guys kinda domain to me. ** Attachment added: dmesg from 3.2 (12.04 kernel) https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1029582/+attachment/3337979/+files/dmesg.p ** Package changed: xserver-xorg-video-ati (Ubuntu) = linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1029582 Title: Unusable graphics with ATI RS690M Status in “linux” package in Ubuntu: Confirmed Bug description: Release: Quantal (20120726/alpha3) Architecture: i386 (but also seen on amd64) Using the alternate CD installation works ok, but rebooting into the install I am lucky if I get anything on the screen that resembles the lightdm screen (screenshot of that case will be attached). There were also cases of just white or just black. Login is impossible and occasionally everything goes downhill. Ssh login is possible or booting into textual mode. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic i686 ApportVersion: 2.4-0ubuntu5 Architecture: i386 CurrentDmesg: [ 23.804204] b44 ssb1:0: eth0: Flow control is off for TX and off for RX [ 23.804504] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Thu Jul 26 19:24:26 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01fc] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.3) MachineType: Dell Inc. Inspiron 1521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=4ec19e6c-f6cc-4b34-9605-fef3559ebfdd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0GU163 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/16/2007:svnDellInc.:pnInspiron1521:pvr:rvnDellInc.:rn0GU163:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1521 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2 version.libdrm2: libdrm2 2.4.37-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.1.902-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~really6.14.4-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1029582/+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 1032622] Re: [quantal] ctrl+alt+l fail to start screenserver
Not seeing this with a machine updated today (2012-09-18) which should have the new stack by now. So probably fixed along the process. Closing. ** Changed in: xorg (Ubuntu) Status: Incomplete = Fix Released -- 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/1032622 Title: [quantal] ctrl+alt+l fail to start screenserver Status in “xorg” package in Ubuntu: Fix Released Bug description: Not sure which package to files this against. But it seems to be related to activating quantal-proposed (which has the new X stack). Now ctrl+alt+l fails to bring up the screensaver (while a laptop that is on quantal but not proposed does work). The shortcut looks still to be present in the keyboard shortcuts dialog box and pressing the key while a shell window is open does play the error sound (so it gets the key). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0 Uname: Linux 3.5.0-7-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Fri Aug 3 15:04:11 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01fc] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.3) MachineType: Dell Inc. Inspiron 1521 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-7-generic root=UUID=4ec19e6c-f6cc-4b34-9605-fef3559ebfdd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section Screen Identifier Default Screen Option NoAccel EndSection XorgLogOld: dmi.bios.date: 05/16/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0GU163 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/16/2007:svnDellInc.:pnInspiron1521:pvr:rvnDellInc.:rn0GU163:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1521 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu2 version.libdrm2: libdrm2 2.4.37-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.902-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-2~ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.2-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1032622/+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 950717] [NEW] rhythmbox: Problems when unpausing a daapd source after long pause
Public bug reported: I find that the following scenario gives weird behaviour: 1. music files are on another host running forked-daapd (precise) 2. daapd source added locally to rhythmbox and playing 3. pause playback (indicator or application) 4. wait (not sure about the minimum here, about 1 hour?) 5. resume playback I had various effects here: - playback resumes for the current song, then stops about the end. Interface still looks like playing (pause icon display in the app) - In order to revive playback, I pressed pause and playback.. Then suddenly there was a search running to get a html/text plugin. After that failed any song I try to start will get the invalid marker (one way sign). - playback resumes for a short time, then suddenly another song is tried to start and another one, and so on in rapid succession. At some point rhythmbox crashed but that time I did not have the debug packages installed. Feels like after a while forked-daapd may reset the connection and present a text error message which is not handled. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.95-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Fri Mar 9 11:40:55 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: SHELL=/bin/bash LC_MESSAGES=en_US.UTF-8 PATH=(custom, user) LANGUAGE=en LANG=de_DE.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-02-24 (14 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi precise -- 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/950717 Title: rhythmbox: Problems when unpausing a daapd source after long pause Status in “rhythmbox” package in Ubuntu: New Bug description: I find that the following scenario gives weird behaviour: 1. music files are on another host running forked-daapd (precise) 2. daapd source added locally to rhythmbox and playing 3. pause playback (indicator or application) 4. wait (not sure about the minimum here, about 1 hour?) 5. resume playback I had various effects here: - playback resumes for the current song, then stops about the end. Interface still looks like playing (pause icon display in the app) - In order to revive playback, I pressed pause and playback.. Then suddenly there was a search running to get a html/text plugin. After that failed any song I try to start will get the invalid marker (one way sign). - playback resumes for a short time, then suddenly another song is tried to start and another one, and so on in rapid succession. At some point rhythmbox crashed but that time I did not have the debug packages installed. Feels like after a while forked-daapd may reset the connection and present a text error message which is not handled. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.95-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Fri Mar 9 11:40:55 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: SHELL=/bin/bash LC_MESSAGES=en_US.UTF-8 PATH=(custom, user) LANGUAGE=en LANG=de_DE.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-02-24 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/950717/+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 950717] Re: rhythmbox: Problems when unpausing a daapd source after long pause
-- 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/950717 Title: rhythmbox: Problems when unpausing a daapd source after long pause Status in “rhythmbox” package in Ubuntu: New Bug description: I find that the following scenario gives weird behaviour: 1. music files are on another host running forked-daapd (precise) 2. daapd source added locally to rhythmbox and playing 3. pause playback (indicator or application) 4. wait (not sure about the minimum here, about 1 hour?) 5. resume playback I had various effects here: - playback resumes for the current song, then stops about the end. Interface still looks like playing (pause icon display in the app) - In order to revive playback, I pressed pause and playback.. Then suddenly there was a search running to get a html/text plugin. After that failed any song I try to start will get the invalid marker (one way sign). - playback resumes for a short time, then suddenly another song is tried to start and another one, and so on in rapid succession. At some point rhythmbox crashed but that time I did not have the debug packages installed. Feels like after a while forked-daapd may reset the connection and present a text error message which is not handled. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.95-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Fri Mar 9 11:40:55 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: SHELL=/bin/bash LC_MESSAGES=en_US.UTF-8 PATH=(custom, user) LANGUAGE=en LANG=de_DE.UTF-8 SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-02-24 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/950717/+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 941846] Re: Duplicate entries in keyboard shortcuts for screenshots
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/941846 Title: Duplicate entries in keyboard shortcuts for screenshots Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Not sure whether gnome-settings-daemon is really the right package to file this agains. Just noticed that the entries for screenshot and schreenshot of a window seem to be duplicated in the top an bottom area of the shortcuts dialog. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 11:14:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to precise on 2012-02-24 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/941846/+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 941846] Re: Duplicate entries in keyboard shortcuts for screenshots
** Attachment added: Screenshot at 2012-02-27 11:12:00.png https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/941846/+attachment/2787407/+files/Screenshot%20at%202012-02-27%2011%3A12%3A00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/941846 Title: Duplicate entries in keyboard shortcuts for screenshots Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Not sure whether gnome-settings-daemon is really the right package to file this agains. Just noticed that the entries for screenshot and schreenshot of a window seem to be duplicated in the top an bottom area of the shortcuts dialog. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 11:14:22 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to precise on 2012-02-24 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/941846/+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 842066] Re: Softwarecenter title text rendering broken on netbooks
** Attachment added: Screenshot taken https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/842066/+attachment/2358224/+files/Screenshot%2520at%25202011-09-05%252020%253A44%253A47.png -- 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/842066 Title: Softwarecenter title text rendering broken on netbooks Status in “software-center” package in Ubuntu: New Bug description: Release: Oneiric Architecture: i386 Software-Center Version: 4.1.21 Text in the title area seems duplicated two more times when started on a netbook with 1024x600 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/842066/+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
