[Desktop-packages] [Bug 1428121]
Another instance in the wild: https://www.reddit.com/r/debian/comments/14lje8f/comment/jpwmckm/?context=3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 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.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
Also note that there is no requirement to have Secure Boot enabled in Cyber Essentials. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987162] Re: 43: New Device Security feature is confusing and unhelpful currently
@billdietrich444 Note: my comment is a trolling attempt, and hopefully an obvious one due to the choice of an obviously unimplementable-in-a-useful-way standard. Please take only 10% seriously. It may be a good idea to stop talking about pure security according to our own set of criteria (because it's up to discussion what's good enough) and start talking about compliance to recognized standards. We can start with the UK standard named Cyber Essentials, which is required for all organizations that need to deal with the UK government. The standard itself is available at https://www.ncsc.gov.uk/files/Cyber- Essentials-Requirements-for-Infrastructure-v3-0-January-2022.pdf It has the following testable requirements related to technical controls: * Firewalls - we can check that the firewall is installed and configured to "block unauthenticated inbound connections by default". * Secure configuration - this also includes removing unneeded or unused services (and this means that it is forbidden to run the SSH server unless there is a documented business need) and uninstalling unused software. So we might want to display when each piece of software was last used so that to ease the audit. Another testable requirement is that any auto-run feature is disabled or configured to "ask". And also there are some checkable requirements related to device unlocking. * User access control - we could list administrative accounts. Also, if a fingerprint reader is detected, or another form of 2FA is available, we can list all all non-enrolled accounts as non-compliant. We can also check if the password quality requirements are implemented and the mandatory unsuccessful login throttling (or lock-out) policy is enforced by PAM. * Malware protection - with specific requirements, related to on-access scanning of all files (including those on network shares, so sorry, ClamAV is not compliant) and web pages. This was the reason I had to tell one of my clients that they have to stop using Linux or stop dealing with the UK government. * Security update management - we can check Ubuntu-specific settings related to the freshness of the database, whether a reboot is needed for something to apply (e.g. are there running copies of deleted and replaced binaries, or do they use deleted libraries), and whether the updates are configured to install automatically. * Backups - we can test whether they configured through known backup applications. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987162 Title: 43: New Device Security feature is confusing and unhelpful currently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: GNOME 43 added a new Device Security feature in the Settings app. You can access it in gnome-control-center 1:43~beta-1ubuntu1 1. Open the Settings app 2. Click Privacy then Device Security The Security Events aren't clickable. A default Ubuntu install only gets us "Security Level 1". The highest level is "Security Level 3". There isn't anything an Ubuntu user can do to get to a higher security level from the Device Security screen. If a user attempts to get their system to a higher security level, I think they could break their system since this isn't something we currently support. Therefore, I think we ought to hide/disable the screen for Ubuntu 22.10. We can work towards better integrating this screen for Ubuntu in future releases. I'm attaching several screenshots although it's worth trying out the feature for yourself too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1428121]
"intel_iommu=on intremap=off" yields no sound. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 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.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1428121]
Another instance of this bug: https://www.reddit.com/r/archlinux/comments/ghozc1/cantt_get_audio_from_intel_graphics_hdmi_out/ Dear maintainers, maybe it's time to fix the IOMMU driver? Or, if IOMMU maintainers are indeed unreachable, maybe ALSA maintainers can detect this condition (iommu on, Haswell HDMI) and at least emit a warning in the log referencing this bug and a possible workaround? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 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.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6: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. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Ping - did I follow the instructions correctly? ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg-server package in Ubuntu: New Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
I have tried to follow the instructions, but not sure if I did it correctly. Does this link help? https://errors.ubuntu.com/oops/d2e06dde- a9d9-11e9-a2e9-fa163e6cac46 -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg-server package in Ubuntu: Incomplete Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate ** Bug watch added: Red Hat Bugzilla #1652274 https://bugzilla.redhat.com/show_bug.cgi?id=1652274 ** Also affects: xorg (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1652274 Importance: Unknown Status: Unknown -- 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/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg package in Ubuntu: New Status in xorg package in Fedora: Unknown Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Public bug reported: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc Status in xorg package in Ubuntu: New Bug description: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: c
[Desktop-packages] [Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
It works. -- 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/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: I am running a KVM virtual machine with 3D acceleration (virgl). The host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the session started crashing just after the login. In xorg logs, I see this: [15.338] (WW) modeset(0): Page flip failed: Invalid argument [15.338] (EE) modeset(0): present flip failed [15.397] (WW) modeset(0): Page flip failed: Invalid argument [15.397] (EE) modeset(0): present flip failed [15.418] (WW) modeset(0): Page flip failed: Invalid argument [15.419] (EE) modeset(0): present flip failed [15.440] (WW) modeset(0): Page flip failed: Invalid argument [15.440] (EE) modeset(0): present flip failed [15.460] (WW) modeset(0): Page flip failed: Invalid argument [15.460] (EE) modeset(0): present flip failed [15.975] (WW) modeset(0): Page flip failed: Invalid argument [15.976] (EE) modeset(0): present flip failed [16.039] (WW) modeset(0): Page flip failed: Invalid argument [16.040] (EE) modeset(0): present flip failed [16.064] (WW) modeset(0): Page flip failed: Invalid argument [16.064] (EE) modeset(0): present flip failed [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared 0:11(2): error: value of type vec4 cannot be assigned to variable of type error 0:12(2): error: `color1' undeclared 0:12(2): error: value of type vec4 cannot be assigned to variable of type error [16.096] Program source: #ifdef GL_ES precision mediump float; #endif #define ATLAS_DIM_INV 0.0009765625 varying vec2 glyph_pos; uniform vec4 fg; uniform sampler2D atlas; void main() { vec4 mask = texture2D(atlas, glyph_pos); vec4 source = fg; color0 = source * mask; color1 = source.a * mask; } [16.096] (EE) Fatal server error: [16.096] (EE) GLSL compile failure Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to 18.0.0~rc5-1ubuntu1 helps. Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there. On the host, the GPU is Intel Haswell: 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) The CPU is Intel(R) Core(TM) i7-4770S CPU. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 16 20:52:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bu
[Desktop-packages] [Bug 1836772] [NEW] Xorg crash on 3d-enabled virgl (Haswell host)
Public bug reported: I am running a KVM virtual machine with 3D acceleration (virgl). The host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the session started crashing just after the login. In xorg logs, I see this: [15.338] (WW) modeset(0): Page flip failed: Invalid argument [15.338] (EE) modeset(0): present flip failed [15.397] (WW) modeset(0): Page flip failed: Invalid argument [15.397] (EE) modeset(0): present flip failed [15.418] (WW) modeset(0): Page flip failed: Invalid argument [15.419] (EE) modeset(0): present flip failed [15.440] (WW) modeset(0): Page flip failed: Invalid argument [15.440] (EE) modeset(0): present flip failed [15.460] (WW) modeset(0): Page flip failed: Invalid argument [15.460] (EE) modeset(0): present flip failed [15.975] (WW) modeset(0): Page flip failed: Invalid argument [15.976] (EE) modeset(0): present flip failed [16.039] (WW) modeset(0): Page flip failed: Invalid argument [16.040] (EE) modeset(0): present flip failed [16.064] (WW) modeset(0): Page flip failed: Invalid argument [16.064] (EE) modeset(0): present flip failed [16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared 0:11(2): error: value of type vec4 cannot be assigned to variable of type error 0:12(2): error: `color1' undeclared 0:12(2): error: value of type vec4 cannot be assigned to variable of type error [16.096] Program source: #ifdef GL_ES precision mediump float; #endif #define ATLAS_DIM_INV 0.0009765625 varying vec2 glyph_pos; uniform vec4 fg; uniform sampler2D atlas; void main() { vec4 mask = texture2D(atlas, glyph_pos); vec4 source = fg; color0 = source * mask; color1 = source.a * mask; } [16.096] (EE) Fatal server error: [16.096] (EE) GLSL compile failure Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to 18.0.0~rc5-1ubuntu1 helps. Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there. On the host, the GPU is Intel Haswell: 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) The CPU is Intel(R) Core(TM) i7-4770S CPU. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 16 20:52:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu ** Attachment added: "Xorg.0.log.old" https://bugs.launchpad.net/bugs/1836772/+attachment/5277429/+files/Xorg.0.log.old -- 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/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) Status in xorg package in Ubuntu: New Bug description: I am running a KVM virtual machine with 3D acceleration (virgl). The host is Arch Linux, the guest
[Desktop-packages] [Bug 881046]
No news, the bug is still reproducible, and it is not clear what information is needed. -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in xorg-server source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
No news, the bug is still reproducible, and it is not clear what information is needed. -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Precise: Fix Released Status in xorg-server source package in Quantal: Fix Released Status in xorg-server source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1271358] Re: Update to 3.18 (remove controls needed for Unity and other desktops)
Note that Vino 3.8.1 bundles a very old libvncserver, with significant image quality problems. One example is attached to https://github.com/novnc/noVNC/issues/737 I do not object to forking 3.8.1, as long as the fork is updated to use the latest libvncserver. ** Bug watch added: github.com/novnc/noVNC/issues #737 https://github.com/novnc/noVNC/issues/737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1271358 Title: Update to 3.18 (remove controls needed for Unity and other desktops) Status in vino package in Ubuntu: Triaged Bug description: Update to 3.16. A big change in this release is to remove the preferences dialog, not sure if this is a problem for us. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1271358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1605953] Re: skylake Modesetting Driver on X failure
Please describe what desktop environment and window manager you use, and whether compositing is enabled in the window manager settings. I am asking because the same bug exists on Haswell in Arch Linux with Marco window manager (in MATE), and is fixable by installing and running compiz. -- 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/1605953 Title: skylake Modesetting Driver on X failure Status in xorg-server package in Ubuntu: New Bug description: with the change away from the intel driver to modeset I get a lot of tearing. This video shows the problem. https://goo.gl/photos/rXNBQ5KR6ZMnhazB9 And the video capture is done in 240fps so its possible to see what is happening more clearly. The test video itself is just a short test video with alternating red/green pictures in 60Hz. What you should see is a somewhat flickering screen but the color should be a consistent orange hue. there should be no pulsing of colors that is more green then back to more red and so on then something is wrong. I have attached the video. if you are uncertain how it should look try to play it directly on a TV. that is with the TV own player not with a computer as that has a lot higher probability of not having any issues with vsync and frame updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
Retested with the latest git. The patch indeed breaks constraining the mouse on the right side when keystone correction is active. However, the whole "keystone correction" feature is already so horribly broken that I'd just propose to drop it. The breakage is that, if you click something, the click will not go into a point that you intended to click. I.e. you can't even undo the damage using the xkeystone GUI. -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
Retested with the latest git. The patch indeed breaks constraining the mouse on the right side when keystone correction is active. However, the whole "keystone correction" feature is already so horribly broken that I'd just propose to drop it. The breakage is that, if you click something, the click will not go into a point that you intended to click. I.e. you can't even undo the damage using the xkeystone GUI. -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
Today I talked about this bug with Keith Packard. As a result of our testing, I have to state that, with the patch, the pointer is not constrained properly on the right side if one applies keystone correction. That's with xorg-server 1.16.1, will now retest with the latest git. -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
Today I talked about this bug with Keith Packard. As a result of our testing, I have to state that, with the patch, the pointer is not constrained properly on the right side if one applies keystone correction. That's with xorg-server 1.16.1, will now retest with the latest git. -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299499]
That new bug is probably https://bugs.gentoo.org/show_bug.cgi?id=513500 -- 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/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled Status in Mesa: Fix Released Status in “mesa” package in Ubuntu: Fix Released Bug description: kwin reports a crash while starting up, and desktop effects are not enabled for the session. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kde-window-manager 4:4.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed. CrashCounter: 1 CurrentDesktop: KDE Date: Sat Mar 29 11:11:04 2014 ExecutablePath: /usr/bin/kwin InstallationDate: Installed on 2014-02-03 (53 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcCmdline: /usr/bin/kwin --crashes 2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: kde-workspace StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 __assert_fail_base (fmt=0x7f7a0d7c2718 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f79edba7a63 "brw->hw_ctx != ((void *)0)", file=file@entry=0x7f79edba7a28 "../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c", line=line@entry=43, function=function@entry=0x7f79edba7a80 "brw_get_graphics_reset_status") at assert.c:92 __GI___assert_fail (assertion=0x7f79edba7a63 "brw->hw_ctx != ((void *)0)", file=0x7f79edba7a28 "../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c", line=43, function=0x7f79edba7a80 "brw_get_graphics_reset_status") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: kwin assert failure: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed. UpgradeStatus: Upgraded to trusty on 2014-03-03 (26 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
Why is this bug still in the NEEDINFO state? I.e. what info is needed before someone reviews the patch? -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
The bug is also relevant to scaling. You can test it (assuming a 1920x1200 monitor) with the following example commands: xrandr --fb 3840x2400 xrandr --output DVI-I-1 --scale 2x2 The example has no purpose as written, except to illustrate the bug, but similar "xrandr --scale" commands are useful if one wants to mirror a 1366x768 laptop screen and a 1920x1080 projector for a presentation. -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 883319]
The bug is also relevant to scaling. You can test it (assuming a 1920x1200 monitor) with the following example commands: xrandr --fb 3840x2400 xrandr --output DVI-I-1 --scale 2x2 The example has no purpose as written, except to illustrate the bug, but similar "xrandr --scale" commands are useful if one wants to mirror a 1366x768 laptop screen and a 1920x1080 projector for a presentation. -- 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/883319 Title: xrandr --scale restricts area in which mouse moves Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Bug description: SRU Request: [IMPACT] A bug in the version of xorg-server in precise prevents users from scaling screen resolution. When attempting to do so, as was possible in Natty and earlier, and which is possible in Quantal+, the mouse pointer remains locked inside the old resolution. This prevents users of small screens such as netbooks from scaling to a greater screen resolution. [Test Case] - On a netbook with intel chipset, such as a Dell Mini 9 or 10, scale the display by using the following command: xrandr --output LVDS1 --panning 1280x750 --scale 1.25x1.25 See if the mouse moves correctly to all screen extremities, and is not confined by a transparent border at 1024x600 [Regression Potential] This is fixed with a patch backported from the xorg-server version in Quantal. In theory it should just affect screen which are scaled and panned, which is uncommon. If so, the patch can be backed out. Original Bug Description: in kubuntu (and ubuntu) 11.04 i used to enlarge my laptop screen like so xrandr --output LVDS1 --scale 1.2x1.2 this worked fine: the desktop scaled to larger size correctly . After upgrading to 11.10, in kde the desktop still resizes correctly, but the movement of the mouse is restricted to an area equal to the screen size *before* issuing the scaling command. .. Ie let's say the mode is 1366x768 and I do xrandr --output LVDS1 --scale 1.2x1.2 the screen size changes to 1640x922 but the mouse moves in an area the size of 1366x768 in the top left of the screen and then 'hits a wall' preventing it to move. I also tried ubuntu 11.10 with gnome: here the screen also resizes, but I have the same issue with the mouse, and the extended area of the desktop is black... Some time ago there was a similar issue, which was resolved later. Now it seems to be back... jos@samsungsucks:~$ lsb_release -rd Description:Ubuntu 11.10 Release:11.10 jos@samsungsucks:~$ xrandr --version xrandr program version 1.3.5 Server reports RandR version 1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881046]
Why is this bug still in the NEEDINFO state? I.e. what info is needed before someone reviews the patch? -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 Status in X.Org X server: Incomplete Status in “xorg-server” package in Ubuntu: Triaged Status in “xorg-server” source package in Precise: Triaged Bug description: When I go for a virtual monitor by issuing command "xrandr --output LVDS1 --fb 1600x1200 --panning 1600x1200" on a monitor working at resolution 1024x768 (as I did before upgrading from Ubuntu 11.04 to Ubuntu 11.10), the WM bars on top and left side of the screen (in Unity) look like extending to the new area, but I cannot move the pointer to the new extra area and so I cannot pan. As far as I understood by reading around, this *could* be a bug in package "xorg- server" rather than in "xrandr" and *could* be related to the boundaries set for cursor position. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] CompositorRunning: compiz Date: Mon Oct 24 20:40:14 2011 DistUpgraded: Log time: 2011-10-22 12:17:44.515205 DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: dahdi, 2.4.1+dfsg-1ubuntu2, 2.6.38-11-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-generic, i686: installed (WARNING! Diff between built and installed module!) dahdi, 2.4.1+dfsg-1ubuntu2, 3.0.0-12-virtual, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0182] Subsystem: Dell Device [1028:0182] MachineType: Dell Inc. Latitude D610 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: 3.3V 32-bit PC Card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=it_IT.UTF-8 LANGUAGE=it_IT:it:en_GB:en ProcKernelCmdLine: root=UUID=35d17829-2597-405b-afdd-6b1d94a4dedd ro quiet splash rootdelay=15 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-10-22 (2 days ago) dmi.bios.date: 03/02/2005 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0D4571 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/02/2005:svnDellInc.:pnLatitudeD610:pvr:rvnDellInc.:rn0D4571:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D610 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu3 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1299499]
*** Bug 77391 has been marked as a duplicate of this bug. *** -- 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/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled Status in Mesa: Confirmed Status in “mesa” package in Ubuntu: Fix Released Bug description: kwin reports a crash while starting up, and desktop effects are not enabled for the session. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: kde-window-manager 4:4.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AssertionMessage: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed. CrashCounter: 1 CurrentDesktop: KDE Date: Sat Mar 29 11:11:04 2014 ExecutablePath: /usr/bin/kwin InstallationDate: Installed on 2014-02-03 (53 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcCmdline: /usr/bin/kwin --crashes 2 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: kde-workspace StacktraceTop: __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 __GI_abort () at abort.c:89 __assert_fail_base (fmt=0x7f7a0d7c2718 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f79edba7a63 "brw->hw_ctx != ((void *)0)", file=file@entry=0x7f79edba7a28 "../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c", line=line@entry=43, function=function@entry=0x7f79edba7a80 "brw_get_graphics_reset_status") at assert.c:92 __GI___assert_fail (assertion=0x7f79edba7a63 "brw->hw_ctx != ((void *)0)", file=0x7f79edba7a28 "../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c", line=43, function=0x7f79edba7a80 "brw_get_graphics_reset_status") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so Title: kwin assert failure: kwin: ../../../../../../../src/mesa/drivers/dri/i965/brw_reset.c:43: brw_get_graphics_reset_status: Assertion `brw->hw_ctx != ((void *)0)' failed. UpgradeStatus: Upgraded to trusty on 2014-03-03 (26 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp