[Touch-packages] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1264543 Title: Trusty sometimes boots with inactive keyboard . Status in lightdm package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing ++F2 and withing the terminal. Logout and login from the terminal followed by ++F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago. WORKAROUND: Works in Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-all 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.7-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 CurrentDesktop: Unity CurrentDmesg: [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 550.563790] audit_printk_skb: 138 callbacks suppressed [ 550.563794] type=1400 audit(1388145574.597:67): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2772 comm="apparmor_parser" [ 550.563802] type=1400 audit(1388145574.597:68): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" [ 550.564387] type=1400 audit(1388145574.597:69): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" Date: Fri Dec 27 16:23:05 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9901] InstallationDate: Installed on 2013-10-21 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A55M-VG3 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.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3: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.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Fri Dec 27 11:50:49 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1264543/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1264543 Title: Trusty sometimes boots with inactive keyboard . Status in lightdm package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing ++F2 and withing the terminal. Logout and login from the terminal followed by ++F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago. WORKAROUND: Works in Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-all 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.7-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 CurrentDesktop: Unity CurrentDmesg: [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 550.563790] audit_printk_skb: 138 callbacks suppressed [ 550.563794] type=1400 audit(1388145574.597:67): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2772 comm="apparmor_parser" [ 550.563802] type=1400 audit(1388145574.597:68): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" [ 550.564387] type=1400 audit(1388145574.597:69): apparmor="STATUS" operation="profile_replace" parent=2768 profile="unconfined" name="/usr/sbin/cupsd" pid=2772 comm="apparmor_parser" Date: Fri Dec 27 16:23:05 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9901] InstallationDate: Installed on 2013-10-21 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A55M-VG3 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.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3: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.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Fri Dec 27 11:50:49 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1264543/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1311965] Re: UI scaling inconsistent when using new display scaling option
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1311965 Title: UI scaling inconsistent when using new display scaling option Status in xorg package in Ubuntu: Expired Bug description: Just installed Ubuntu 14.04 on a Lenovo Yoga 2 Pro, which has a 3200x1800 display. Consequently, I need to scale up everything in the system to have anything render at a reasonable size. I found the new "Scale for menu and title bars" option in the Display Settings, and set it it 2.25. This, for the most part, did what I wanted. * Unity interface is scaled * Text is scaled * Many builtin applications seem to scale correctly However, there's some funky inconsistencies as to what has scaled: * Depending on what the mouse is over, it either renders at the larger (correct) size, or a smaller (incorrect) size. Examples of things which render the mouse incorrectly include the global/window bars, unity application selector, most applications (firefox and most of software center are notable exceptions), and sometimes right-click menus. * Some (GTK provided?) widgets (most notably checkboxes, radio buttons, scroll bars, and ) render too small. This is visible in most third-party applications, which are otherwise correctly sized. Firefox and CompizConfig are examples of this, even after layout.css.devPixelsPerPx was changed in Firefox to match the display setting. * The change occasionally doesn't correctly register with some or all applications (regardless of whether they were open at the time). Adjusting the slider always changes the unity global ui correctly, but sometimes the settings manager or nautillus would not actually render at an increased size, even after a reboot. Other times it would register fine even without a reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 23 22:30:31 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-04-24 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=22977ed7-bb41-4448-98c8-bcf44422165e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 23 22:00:49 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to:
[Touch-packages] [Bug 1352374] Re: changing backlight color on saitek eclipse 2 keyboard causes mouse failure
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1352374 Title: changing backlight color on saitek eclipse 2 keyboard causes mouse failure Status in xorg package in Ubuntu: Expired Bug description: This has apparently been ongoing for a long time. I have a Saitek Eclipse ii keyboard and I and others report that when you click the keyboard button to change the back light color, it triggers mouse events. These end up disabling the mouse, in my case Microsoft Intellimouse. Unplugging and replugging the USB cable for the keyboard resets function to normal with the default blue back light color. If you try to change the color, the problem returns. I am now running 64 bit 14.04 and the problem has been with me since at least 12.04. If I change the backlight color while the system is booting up but before the log in screen appears, I can select the color I want the keyboard to be, but if I wait till after the log in screen appears, then the mouse is non-functional when the desktop loads until I log off and back on. Here is some relevant data from a report on Ubuntu forums (http://ubuntuforums.org/showthread.php?t=2174670) about this exact problem... /dev/input/event5 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input0" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP /dev/input/event6 bustype : BUS_USB vendor : 0x6a3 product : 0x8021 version : 273 name : "Chicony Saitek Eclipse II Keyboa" phys : "usb-:00:1d.0-1/input1" uniq : "" bits ev : EV_SYN EV_KEY EV_MSC The feature that causes the problem here is the button to turn on/off/change the kb backlight color. input-events for /dev/input/event6: First press (backlight off->blue): emulates left click 19:43:40.885931: EV_MSC MSC_SCAN -16646143 19:43:40.885936: EV_KEY BTN_0 (0x100) pressed 19:43:40.885941: EV_MSC MSC_SCAN -16646140 19:43:40.885942: EV_KEY BTN_3 (0x103) released 19:43:40.885943: EV_SYN code=0 value=0 Second press (blue->red): emulates middle click 19:43:43.101984: EV_MSC MSC_SCAN -16646143 19:43:43.101989: EV_KEY BTN_0 (0x100) released 19:43:43.101992: EV_MSC MSC_SCAN -16646142 19:43:43.101992: EV_KEY BTN_1 (0x101) pressed 19:43:43.101996: EV_SYN code=0 value=0 Third press (red->purple): emulates right click 19:43:38.005865: EV_MSC MSC_SCAN -16646142 19:43:38.005869: EV_KEY BTN_1 (0x101) released 19:43:38.005871: EV_MSC MSC_SCAN -16646141 19:43:38.005872: EV_KEY BTN_2 (0x102) pressed 19:43:38.005874: EV_SYN code=0 value=0 Fourth press (purple->off) emulates ??? 19:43:39.765915: EV_MSC MSC_SCAN -16646141 19:43:39.765921: EV_KEY BTN_2 (0x102) released 19:43:39.765925: EV_MSC MSC_SCAN -1664614019 19:43:39.765926: EV_KEY BTN_3 (0x103) pressed 19:43:39.765928: EV_SYN code=0 value=0 So, the backlight changing on a keyboard act as different types of mouse clicks based on what color you switch to. Apparently this problem is also present in PCLinuxOS. Is this possibly a Udev issue? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,snap,move,vpswitch,regex,place,animation,session,imgpng,grid,gnomecompat,wall,resize,expo,unitymtgrabhandles,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Aug 4 09:47:36 2014 DistUpgraded: 2014-08-02 23:43:24,960 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:1556] InstallationDate: Installed on 2009-11-04 (1733 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine:
[Touch-packages] [Bug 1376017] Re: Dell 1908fpt VGA monitor has max resolution of 1280 x 768
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1376017 Title: Dell 1908fpt VGA monitor has max resolution of 1280 x 768 Status in xorg package in Ubuntu: Expired Bug description: My Dell 1908fpt monitor connected via VGA has a max resolution of 1280 x 768. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None CurrentDesktop: GNOME Date: Tue Sep 30 23:27:42 2014 DistUpgraded: 2014-09-28 23:56:30,883 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-36-generic, i686: installed GraphicsCard: Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3039] InstallationDate: Installed on 2014-09-25 (5 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=cabc1f0e-dcf0-472a-aa34-db7305dbf8a5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-09-28 (1 days ago) dmi.bios.date: 08/20/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 2RKT54AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr2RKT54AUS:bd08/20/2008:svnLENOVO:pn6071BFG:pvrThinkCentreM57:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6071BFG dmi.product.version: ThinkCentre M57 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Sep 30 23:11:48 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1376017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1403336] Re: swrast.so is broken in Ubuntu 14.04
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1403336 Title: swrast.so is broken in Ubuntu 14.04 Status in xorg package in Ubuntu: Expired Bug description: I have Ubuntu 14.04 64x. I need to use libGL for a project. LibGL uses (dlopen) swrast_dri.so. Both of these are maintained by Ubuntu as specified in the package repository. When i try to run glxinfo I get: name of display: :0 libGL: screen 0 does not appear to be DRI3 capable libGL: screen 0 does not appear to be DRI2 capable libGL: OpenDriver: trying /usr/lib/fglrx/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/fglrx/dri/swrast_dri.so libGL: driver does not expose __driDriverGetExtensions_swrast(): /usr/lib/fglrx/dri/swrast_dri.so: undefined symbol: __driDriverGetExtensions_swrast libGL: Can't open configuration file /home/nikos/.drirc: No such file or directory. libGL: Can't open configuration file /home/nikos/.drirc: No such file or directory. libGL error: failed to load driver: swrast This is with mesa 10.1.3. Unresolved symbols in swrast seem to go back to mesa 10.1.1. Are there any updates/patches for 14.04? Failing that, where can i dind a version that doesn't have these problems and where can I download its sources? TIA, Nikos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404332] Re: Touchpad cursor loses precision after VGA monitor plugged in
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1404332 Title: Touchpad cursor loses precision after VGA monitor plugged in Status in xorg package in Ubuntu: Expired Bug description: I just plug in the VGA cable. The external monitor is detected acc.to dmesg. A USB mouse works OK. The problem lies somewhere with synaptic driver. If I simply put down a finger on the touchpad and hold it still, the cursor still fidgets in random directions by a couple millimeter increments. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Dec 19 19:12:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:14f7] InstallationDate: Installed on 2014-10-02 (78 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:1721): WARNING **: Failed to load user image: Failed to open file '/home/developer23/.face': No such file or directory ** (lightdm-gtk-greeter:1721): WARNING **: Failed to load user image: Failed to open file '/home/default2/.face': Permission denied LightdmGreeterLogOld: ** (lightdm-gtk-greeter:7293): WARNING **: Failed to load user image: Failed to open file '/home/developer23/.face': No such file or directory (lightdm-gtk-greeter:7293): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. MachineType: ASUSTeK COMPUTER INC. X401A1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=720d9c60-9be6-4623-a0c4-42a8f269bb44 ro persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X401A1.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X401A1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX401A1.212:bd12/03/2012:svnASUSTeKCOMPUTERINC.:pnX401A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX401A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X401A1 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Dec 14 19:25:35 2014 xserver.configfile: default xserver.errors: ETPS/2 Elantech Touchpad: Read error 19 ETPS/2 Elantech Touchpad: Read error 19 ETPS/2 Elantech Touchpad: Read error 19 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5234 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.5 --- .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded:
[Touch-packages] [Bug 1432234] Re: Reboot after quick and dirty openFrameworks workaround
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1432234
Title:
Reboot after quick and dirty openFrameworks workaround
Status in xorg package in Ubuntu:
Expired
Bug description:
$ uname -a
Linux nil-NV57H 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14
UTC 2015 x86 64 x86_64 GNU/Linux
The laptop trackpad has ceased its functioning after the steps outlined
below. I have attempted reloading the psmouse module via
modprobe -r !$ && modprobe !$ ;
to no avail. Ubuntu still responds to the left/0 button, however.
egrep "Name|Handlers" /proc/bus/input/devices ;
Defines
Name="ETPS/2 Elantech Touchpad"
Handlers=mouse0 event6
as the mouse handler.
//
FOOT NOTE ON INSTALLING OPENFRAMEWORKS
openFrame works shell script at
"${ofRoot}/scripts/linux/ubuntu/install_dependancies.sh" WILL NOT RUN in the
manner defined by the openFrameworks documentation:
sudo ./install_dependancies.sh ;
The error message suggested that my internet connection may be failing;
however, this was not true, so I installed the gstreamer plug-ins in the final
if block (of the referenced script, snippet to follow) via apt-get
install;
apt-get update
GSTREAMER_VERSION=0.10
GSTREAMER_FFMPEG=gstreamer${GSTREAMER_VERSION}-ffmpeg
echo "detecting latest gstreamer version"
apt-cache show libgstreamer1.0-dev
exit_code=$?
if [ $exit_code = 0 ]; then
echo selecting gstreamer 1.0
GSTREAMER_VERSION=1.0
GSTREAMER_FFMPEG=gstreamer${GSTREAMER_VERSION}-libav
fi
# {...}
echo "installing gstreamer"
apt-get install libgstreamer${GSTREAMER_VERSION}-dev
libgstreamer-plugins-base${GSTREAMER_VERSION}-dev ${GSTREAMER_FFMPEG}
gstreamer${GSTREAMER_VERSION}-pulseaudio gstreamer${GSTREAMER_VERSION}-x
gstreamer${GSTREAMER_VERSION}-plugins-bad gstreamer${GSTREAMER_VERSION}-alsa
gstreamer${GSTREAMER_VERSION}-plugins-base
gstreamer${GSTREAMER_VERSION}-plugins-good
exit_code=$?
if [ $exit_code != 0 ]; then
echo "error installing gstreamer, there could be an error with your
internet connection"
echo "if the error persists, please report an issue in github:
http://github.com/openframeworks/openFrameworks/issues;
exit $exit_code
fi
I installed gstreamer 1.0, and (of course, to my chagrin) that did not
solve the dependancy issue. I attempted to install each of the
dependancies with apt-get individually (the ones in this if block,
where i thought the problem was), and found that gstreamer0.10-ffmpeg
package is not available in the standard repositories. I did install
the gstreamer0.10-ffmpeg package from a third party. However, the
script still did not recognize that all of the dependancies were
installed!
A clever person on the openFrameworks community forum announced that
if you (fix broken and install the packages freeglut3 freeglut3-dev
freeglut3-dbg) via synaptic install_dependancies.sh runs without
errors. By some freak twist of package manangement abstraction the
script only worked properly after that operation. I did just go ahead
and install synaptic to replicate the experiment accurately: I do not
know if I could have just installed those packages through apt-get
without broken dependancies. If so, openFrameworks should know that
freeglut3 et al should be in their
linux/ubuntu/install_dependancies.sh script.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Mar 14 15:34:04 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device [1025:0511]
InstallationDate: Installed on 2015-03-13 (1 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64
(20150218.1)
Lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b2dc Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 8087:0024 Intel Corp.
[Touch-packages] [Bug 1518653] Re: Custom xorg input device configurations are not honored
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1518653 Title: Custom xorg input device configurations are not honored Status in xorg package in Ubuntu: Expired Bug description: Ubuntu release: Ubuntu 14.04.3 LTS xorg package version: 1:7.7+1ubuntu8.1 No matter where I put my custom mouse input device xorg config, I cannot get the settings to be used. I tried putting my file (90-razer- lachesis.conf) in various places (/etc/X11/xorg.conf.d/, /usr/share/X11/xorg.conf.d/ and even copied the content of my file into /etc/xorg.conf), but nothing works. The custom config seems to be picked up by by Xorg, as can be found in the /var/log/Xorg.0.log file, but nonetheless the configuration defined in the config is not respected. Here's the config file (90-razer-lachesis.conf); it should merely inverts the left and right buttons, to be used as a left hand mouse: Section "InputClass" Identifier "Razer Lachesis Mouse" MatchUSBID "1532:000c" MatchIsPointer "True" Option "ButtonMapping" "3 2 1" EndSection Here's the log from Xorg when I plug the mouse in: [ 1455.588] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/mouse0) [ 1455.588] (**) Razer Razer Lachesis: Applying InputClass "Razer Lachesis Mouse" [ 1455.588] (II) No input driver specified, ignoring this device. [ 1455.588] (II) This device may have been added with another device file. [ 1455.590] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event2) [ 1455.590] (**) Razer Razer Lachesis: Applying InputClass "evdev pointer catchall" [ 1455.590] (**) Razer Razer Lachesis: Applying InputClass "Razer Lachesis Mouse" [ 1455.590] (II) Using input driver 'evdev' for 'Razer Razer Lachesis' [ 1455.590] (**) Razer Razer Lachesis: always reports core events [ 1455.590] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event2" [ 1455.652] (**) evdev: Razer Razer Lachesis: ButtonMapping '3 2 1' [ 1455.652] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc [ 1455.652] (--) evdev: Razer Razer Lachesis: Found 12 mouse buttons [ 1455.652] (--) evdev: Razer Razer Lachesis: Found scroll wheel(s) [ 1455.652] (--) evdev: Razer Razer Lachesis: Found relative axes [ 1455.652] (--) evdev: Razer Razer Lachesis: Found x and y relative axes [ 1455.652] (II) evdev: Razer Razer Lachesis: Configuring as mouse [ 1455.652] (II) evdev: Razer Razer Lachesis: Adding scrollwheel support [ 1455.652] (**) evdev: Razer Razer Lachesis: YAxisMapping: buttons 4 and 5 [ 1455.652] (**) evdev: Razer Razer Lachesis: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 1455.652] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:1532:000C.0008/input/input24/event2" [ 1455.652] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: MOUSE, id 8) [ 1455.652] (II) evdev: Razer Razer Lachesis: initialized for relative axes. [ 1455.652] (**) Razer Razer Lachesis: (accel) keeping acceleration scheme 1 [ 1455.652] (**) Razer Razer Lachesis: (accel) acceleration profile 0 [ 1455.652] (**) Razer Razer Lachesis: (accel) acceleration factor: 2.000 [ 1455.652] (**) Razer Razer Lachesis: (accel) acceleration threshold: 4 [ 1455.652] (II) config/udev: Adding input device Razer Razer Lachesis (/dev/input/event3) [ 1455.652] (**) Razer Razer Lachesis: Applying InputClass "evdev keyboard catchall" [ 1455.652] (II) Using input driver 'evdev' for 'Razer Razer Lachesis' [ 1455.652] (**) Razer Razer Lachesis: always reports core events [ 1455.652] (**) evdev: Razer Razer Lachesis: Device: "/dev/input/event3" [ 1455.652] (--) evdev: Razer Razer Lachesis: Vendor 0x1532 Product 0xc [ 1455.652] (--) evdev: Razer Razer Lachesis: Found keys [ 1455.652] (II) evdev: Razer Razer Lachesis: Configuring as keyboard [ 1455.652] (**) Option "config_info" "udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:1532:000C.0009/input/input25/event3" [ 1455.652] (II) XINPUT: Adding extended input device "Razer Razer Lachesis" (type: KEYBOARD, id 9) [ 1455.652] (**) Option "xkb_rules" "evdev" [ 1455.652] (**) Option "xkb_model" "pc105" [ 1455.652] (**) Option "xkb_layout" "us" [ 1455.661] (II) XKB: reuse xkmfile /var/lib/xkb/server-214897094EF3487F6600C13FDFE2B6CB9A6493EF.xkm ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64
[Touch-packages] [Bug 1523057] Re: Xinput: no way to map absolute input to whole screen
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1523057 Title: Xinput: no way to map absolute input to whole screen Status in xorg package in Ubuntu: Expired Bug description: By default, absolute input devices like tablets or touchscreens are mapped across the user's full screen. This can then be changed to single screen by, for example: xinput map-to-output DeviceNum VGA0 This is all well and good, but it appears there is no way to map the input back to the spanned screen. It would be great if there was a way to do this, e.g. xinput map-to-output DeviceName "Screen 0" Alternatively, if I have missed something obvious, consider this a documentation bug because I can't find any way to do this mentioned in man pages or help. Using xinput 1.6.1. Jarrad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1523057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581411] Re: Xorg freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1581411 Title: Xorg freeze Status in xorg package in Ubuntu: Expired Bug description: Everytime it keeps freezing... mouse and keyboard not responding. --- .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: armhf CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Lsusb: Bus 001 Device 005: ID 046d:c315 Logitech, Inc. Classic Keyboard 200 Bus 001 Device 004: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: armhf ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: 8250.nr_uarts=0 dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1360 bcm2708_fb.fbheight=768 bcm2709.boardrev=0xa22082 bcm2709.serial=0x28fac8a2 smsc95xx.macaddr=B8:27:EB:FA:C8:A2 bcm2708_fb.fbdepth=32 bcm2708_fb.fbswap=1 bcm2709.uart_clock=4800 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait quiet splash Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.14-v7+ armv7l UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629161] Re: X server stopped loading with "Number of created screens does not match number of detected devices."
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1629161 Title: X server stopped loading with "Number of created screens does not match number of detected devices." Status in xorg package in Ubuntu: Expired Bug description: Basically, it says that "number of created screens does not match number of detected devices." I tinkered with Nvidia drivers, and re-installed xorg without any success. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 30 05:31:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM107 [GeForce GTX 750 Ti] [1462:8a9b] InstallationDate: Installed on 2016-08-14 (46 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: MSI MS-7996 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=b01f563b-7260-4e71-9128-819de8ab8e84 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD (MS-7996) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd07/27/2016:svnMSI:pnMS-7996:pvr1.0:rvnMSI:rnH110MPRO-VD(MS-7996):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7996 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Sep 30 05:15:09 2016 xserver.configfile: /root/xorg.conf.new xserver.devices: xserver.errors: dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory) Unknown chipset: NV117 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1629161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633802] Re: Blank screen amdgpu - Ubuntu 16.04 - Mainline kernel 4.8.1
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1633802 Title: Blank screen amdgpu - Ubuntu 16.04 - Mainline kernel 4.8.1 Status in xorg package in Ubuntu: Expired Bug description: AMD APU A10-8700p + R6 M360 GRUB_CMDLINE_LINUX_DEFAULT="quiet iommu=pt client splash acpi_backlight=vendor i8042.dumbkbd=1" Laptop HP firmware folders amdgpu and radeon cloned from git Using padoka ppa drivers Blank screen after few minutes in unity session ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.8.1-040801-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 16 00:05:41 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b5] InstallationDate: Installed on 2016-04-22 (177 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: HP HP Pavilion Notebook ProcEnviron: LANGUAGE=es_CL:es TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.1-040801-generic root=UUID=93369433-cd13-4e94-9f0c-0193dfeca58e ro quiet iommu=pt client splash acpi_backlight=vendor i8042.dumbkbd=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B5 dmi.board.vendor: HP dmi.board.version: 81.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.19:bd05/27/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1610081859.a44c9c3~x~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:12.1~git161008214900.185be15~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:12.1~git161008214900.185be15~x~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.99+git1609301659.3fc839f~x~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1610081915.696f58f~x~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12+git1607251455.6473b68~x~padoka0 xserver.bootTime: Sun Oct 16 02:57:26 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633802/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646178] Re: video problems
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1646178 Title: video problems Status in xorg package in Ubuntu: Expired Bug description: Running 16.04, after update, new Nvidia driver (304.132) caused login loop - resorted to nouveau driver and have arbitrary crashes and weird boot issues. Have not been able to reinstall old Nvidia (304.131). Have been checking the forum and see similar problems, nothing seems to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30 Uname: Linux 4.4.0-51-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 30 11:19:56 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a58] InstallationDate: Installed on 2013-01-01 (1428 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Lsusb: Bus 001 Device 003: ID 0bda:0111 Realtek Semiconductor Corp. RTS5111 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 04fc:05d8 Sunplus Technology Co., Ltd Wireless keyboard/mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GX614AA-ABA a6330f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-51-generic root=UUID=1ede16fa-23c2-4f4d-8b28-b9318d2ff433 ro splash quiet Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnGX614AA-ABAa6330f:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: GX614AA-ABA a6330f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Nov 30 10:40:59 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMLK wireless combo KEYBOARD, id 8 inputMLK wireless combo KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1646178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639627] Re: Garbled graphic ("zoomed in effect") in fullscreen 3D applications if other window opens
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1639627
Title:
Garbled graphic ("zoomed in effect") in fullscreen 3D applications if
other window opens
Status in xorg package in Ubuntu:
Expired
Bug description:
I've a problem with full screen apps since ages (using ubuntu 14.04
and 16.04 64 bit and gnome flashback+compiz). they are liked "zoomed
in", so I see only 75% if there is other window layered over it
(e.g.skype messages or apport)...
If I disable unredirect_fullscreen_windows completly fullscreen
windows are always distorted in this way. I both tried the original
xorg drivers and the ones from
http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu . And also the
mainline kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639627/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644142] Re: Intel graphics card error
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644142 Title: Intel graphics card error Status in xorg package in Ubuntu: Expired Bug description: Dont recognize webGL ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Nov 23 10:17:39 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.20, 4.4.0-45-generic, x86_64: installed vboxhost, 5.0.20, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053d] InstallationDate: Installed on 2016-05-20 (186 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude E5530 non-vPro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=37d61e6c-8d00-479b-8749-77e82d82d95f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 05GRXT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd10/08/2012:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5530 non-vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Nov 21 09:28:38 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8685 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1644142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639643] Re: radeon driver; many screen blackouts after booting
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1639643 Title: radeon driver; many screen blackouts after booting Status in xorg package in Ubuntu: Expired Bug description: lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 apt-cache policy ubuntu 16.04 lubuntu-artwork-16-04: Installiert: (keine) Installationskandidat: 0.61.1 Versionstabelle: 0.61.1 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages 0.61 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe i386 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Nov 6 23:08:19 2016 DistUpgraded: 2016-08-03 14:28:28,465 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] R420 [Radeon X800 PRO/GTO AGP] [1002:4a49] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2011-05-12 (2005 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: FUJITSU SIEMENS MS-7071 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=2c3bd1f5-d73c-48ea-b680-cf3190450e33 ro plymouth:debug nopat drm.debug=0xe quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-08-03 (95 days ago) dmi.bios.date: 02/06/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7071 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: 1.00 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/06/2006:svnFUJITSUSIEMENS:pnMS-7071:pvr1.00:rvnFUJITSUSIEMENS:rnMS-7071:rvr1.00:cvn:ct3:cvr: dmi.product.name: MS-7071 dmi.product.version: 1.00 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Aug 3 13:41:27 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Generic Wheel Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658695] Re: Segfault in r300_dri when 2 monitors connected - Ubuntu 16.04.1
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1658695 Title: Segfault in r300_dri when 2 monitors connected - Ubuntu 16.04.1 Status in xorg package in Ubuntu: Expired Bug description: Hi, I try to connect 2 monitors on an Xpress 1100/1150 video card, VGA and DVI output. If I connect one monitor all is good, doesn't matter on which output it is connected. If I connect 2 monitors, in graphical mode, desktop is launched, background picture appears but nothing more: no desktop icons nor application launcher. The mouse cursor appears, goes normally from one screen to the other but no clic working. In console mode, output is on both monitors. In dmesg I see: compiz segfault at 8 ip sp other error 4 in r300_dri.so Ubuntu 16.04.1 LTS Thanks for your support Daniel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 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] Date: Mon Jan 23 14:53:13 2017 DistUpgraded: 2014-05-24 19:25:09,660 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-36-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] [1002:5974] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company DC5750 Microtower [103c:280a] Subsystem: Hewlett-Packard Company RS480 [Radeon Xpress 1150] (Secondary) [103c:280b] InstallationDate: Installed on 2013-03-26 (1398 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP Compaq dc5750 Small Form Factor ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=895610a5-c3a6-42dc-ac6a-d14e99ef6b67 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2014-05-24 (974 days ago) dmi.bios.date: 01/25/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786E3 v02.10 dmi.board.name: 0A64h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: CZC8061JND dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786E3v02.10:bd01/25/2007:svnHewlett-Packard:pnHPCompaqdc5750SmallFormFactor:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq dc5750 Small Form Factor dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jan 23 12:59:48 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1658695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661038] Re: Problem with dell inspiron 3000 video driver
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1661038 Title: Problem with dell inspiron 3000 video driver Status in xorg package in Ubuntu: Expired Bug description: my laptop dell inspiron 15 3000 fix problem with video driver. My display fade on/off sometime. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 1 11:29:28 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Broadwell-U Integrated Graphics [1028:06b0] InstallationDate: Installed on 2017-01-30 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3558 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic root=UUID=d34a28f3-c10e-48e2-942b-6ec24f5105f5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0F70GR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd12/15/2015:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0F70GR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Jan 31 22:32:57 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4332 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1661038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1866347] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_ad
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1866347 Title: /usr/share/apport/whoopsie-upload- all:AssertionError:/usr/share/apport/whoopsie-upload- all@168:collect_info:process_report:add_gdb_info:crash_signature_addresses:_address_to_offset:_build_proc_maps_cache Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Confirmed Bug description: [ Impact ] The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.11-0ubuntu17, the problem page at https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. As of 2022-11-24, 33,559 crashes of this type were reported in Ubuntu 18.04 (bionic). [ Test Plan ] Check that the fixed version does not appear on https://errors.ubuntu.com/problem/5cc81a1cde2a921ad2adcc00e2f8d13f2c9f76e8. [ Where problems could occur ] Worst case - in any part of the bug reporting/collection procedure, since that is what's changing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1866347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006793] Re: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Hello, my guess is your /boot filesystem is out of space. You might be able to free up enough space by running: sudo apt autoremove If that doesn't make enough free space, you might want to ask for help on https://askubuntu.com or #ubuntu on https://libera.chat Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2006793 Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Its says a system error occurred - I've been getting these for a year now - and I have no idea where it's coming from. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 9 17:11:23 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-04-05 (675 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006793] Re: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2006793 Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Its says a system error occurred - I've been getting these for a year now - and I have no idea where it's coming from. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 9 17:11:23 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-04-05 (675 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006793] Re: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2006793 Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Its says a system error occurred - I've been getting these for a year now - and I have no idea where it's coming from. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-58.64~20.04.1-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Feb 9 17:11:23 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-04-05 (675 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-60-generic 5.15.0-60.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006793/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
@Daniel, The same Ubuntu Core image works as expected on the Thinkpad E15 and x86 Mac. Why would the lack of "some extra privileges" impact how it runs on the Dell system, but not Thinkpad and Mac? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006954] Re: openssl: merge unstable's 3.0.8-1
** Tags added: fr-3408 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
Thanks, Simon, I must have missed it. When I use --mode=non-interactive on lxc and -l on tcpdump, I don't see the issue at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in tcpdump package in Ubuntu: Confirmed Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904068] Re: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d)
Gabriel Kaufmann (info-typoworx) wrote on 2022-08-24 (last edit on 2022-08-24): > Also affects me. But instead of "only" source-packages all updates fail with Unauthorized 401. ESM is unusable in fact working like that! In my case Ubuntu 16.04 is affected which still should work for ESM Updates and there are about 300 updates proposed for me, but I'm not able to download them. Hello, Gabriel To have access to the esm repositories you need an Ubuntu Pro subscription (https://ubuntu.com/pro). If you are attached to a subscription, `pro enable esm-infra` will give you access. If you still get 401s when the service is enabled, please open a bug against `ubuntu-advantage-tools` (https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage- tools/+filebug) so we can help you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904068 Title: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d) Status in apt package in Ubuntu: Confirmed Bug description: I have configured apt-src access to the private ESM PPAs via entries in /etc/apt/sources.list.d/ubuntu-security.list as follows: deb-src https://private-ppa.launchpad.net/ubuntu-esm/esm-infra- security/ubuntu trusty main and then added credentials as follows to /etc/apt/auth.conf.d/ubuntu- security.conf: machine private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu login alexmurray password Running apt-get update then succeeds - but if I then try and run `apt- get source` to download from the PPA it fails: $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Err:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] Err:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.dsc 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch some archives. However if I edit /etc/apt/sources.list.d/ubuntu-security.list above to specify the credentials in-line then it succeeds: deb-src https://alexmurray:x...@private-ppa.launchpad.net/ubuntu- esm/esm-infra-security/ubuntu trusty main $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Get:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) [3,446 kB] Get:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) [1,604 B] Fetched 3,447 kB in 5s (657 kB/s) dpkg-source: info: extracting intel-microcode in intel-microcode-3.20201110.0ubuntu0.14.04.2 dpkg-source: info: unpacking intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz However now apt(-get) update complains about having credentials manually listed in the apt sources: $ sudo apt update ... N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu' ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop:
[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
@georgiag, the behaviour changes when you tell tcpdump to do line buffering (`-l`). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in tcpdump package in Ubuntu: Confirmed Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006645] Re: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open
I don't know if it's a regression. I'm not that technical and didn't even know what Mesa was until I ran into this bug. All I know is it's present in the Mesa shipped with Jammy but fixed in 22.3.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2006645 Title: Death Stranding(Video Game) crashes consistenly when moving right control stick with map open Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Jammy: New Status in mesa source package in Kinetic: New Bug description: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7735#note_1674704 99% sure it's this bug on Mesa's gitlab. Installing the kisak-mesa PPA fixed the issue for me. Any chance of a backport for the fix? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr
** Description changed: + [ Impact ] + + Users that run tcpdump from an SSH session inside a container cannot + see the output because tcpdump tries to write to /dev/pts/, which is + not allowed by the AppArmor policy. + + This upload fixes the bug by allowing read/write access to the devices + under /dev/pts/ in the AppArmor policy. + + [ Test Plan ] + + Create a lxd container. In this example we are using version 20.04, + but the issue is reproducible in all versions. + + lxc launch ubuntu:20.04 + + SSH into the container and run the following command + + tcpdump -i eth0 -nn not tcp port 22 + + In a different window, ping the IP of the container. Notice that + there's no output on the tcpdump window, even after you press Ctrl+C. + + Check the kernel logs and you will see a DENIED message like the one + below + + [ 575.438349] audit: type=1400 audit(1676055298.285:164): + apparmor="DENIED" operation="file_inherit" namespace="root//lxd- + peaceful-rattler_" profile="/usr/sbin/tcpdump" + name="/dev/pts/1" pid=7922 comm="tcpdump" requested_mask="wr" + denied_mask="wr" fsuid=100 ouid=100 + + [ Where problems could occur ] + + The SRU broadens the AppArmor policy for tcpdump, so if there was + ever an exploit on tcpdump that allowed a malicious agent to + write to /dev/pts/*, this could be used to write to the + terminal. With that said, the risk of this hapenning is low. + + [ Other Info ] + + The SRU for bionic, focal, jammy, kinetic and lunar can be found in + https://launchpad.net/~georgiag/+archive/ubuntu/lp1667016 + + Tcpdump from inside the container needs to be updated to use the + version with the fix in the AppArmor policy. + + + + - ORIGINAL DESCRIPTION -- + [ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0] If you ssh into an lxd container as a normal user, and inside that container run "sudo tcpdump", the tcpdump process is blocked from writing to stdout/stderr. This appears to be due to apparmor: disabling apparmor for tcpdump makes the problem go away. - ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ + ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/ Note: this is a different bug from #1641236. In that bug, the user did "lxc exec bash" to get a shell in the container; the stdout fd was being passed from the outer host to the container. But in this case, the pty is being created entirely inside the container by sshd. Details copied from https://github.com/lxc/lxd/issues/2930 # Steps to reproduce 1. Create two Ubuntu 16.04 lxd containers, one privileged, one not. 2. ssh into each one, and then use `sudo -s` to get root. (Do not use `lxc exec` because of issue #1641236) 3. Inside one run `tcpdump -i eth0 -nn not tcp port 22`, and ping from the other. tcpdump in the privileged container works just fine. tcpdump in the unprivileged container does not show any output. But if I run strace on it I see errors attempting to access stdout and stderr: ~~~ ioctl(1, TCGETS, 0x7fff97c8d680)= -1 ENOTTY (Inappropriate ioctl for device) ... write(2, "tcpdump: verbose output suppress"..., 75) = -1 EACCES (Permission denied) write(2, "listening on eth0, link-type EN1"..., 74) = -1 EACCES (Permission denied) ~~~ This is very weird. Even more weird: the following command *does* capture packets: ~~~ tcpdump -i eth0 -nn -w foo.pcap ~~~ The file foo.pcap grows. This proves it's nothing to do with network capture perms. But the following command shows no output: ~~~ tcpdump -r foo.pcap -nn ~~~ And again it's because it can't write to stdout: ~~~ fstat(1, 0x7ffe2fb5eb10)= -1 EACCES (Permission denied) read(3, "", 4096) = 0 write(1, "14:34:30.618180 IP6 fe80::c609:6"..., 1740) = -1 EACCES (Permission denied) ~~~ I had originally thought this was to do with capabilities. But if I run `capsh --print` inside both containers, they both have `cap_net_raw` and `cap_net_admin`. In fact, the unprivileged container has two additional capabilities! (`cap_mac_override` and `cap_mac_admin`) So now I suspect that apparmor is at fault. dmesg dmesg output generated by the following steps: * start tcpdump * wait 5 seconds * send 1 ping from other side * wait 5 seconds * stop tcpdump ~~~ [429020.685987] audit: type=1400 audit(1487774339.708:3597): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001 [429020.686000] audit: type=1400 audit(1487774339.708:3598): apparmor="DENIED" operation="file_inherit" namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump"
[Touch-packages] [Bug 1904068] Re: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d)
I noticed that too yesterday but it's hard to make this right I think. Maybe the default permissions should give read access to the auth.conf snippet for users in the admin group or whatever it's called. Because the problem to guard against are shared systems where credentials for Pro shouldn't leak to unprivileged users, so there's always gonna be users unable to use apt download. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904068 Title: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d) Status in apt package in Ubuntu: Confirmed Bug description: I have configured apt-src access to the private ESM PPAs via entries in /etc/apt/sources.list.d/ubuntu-security.list as follows: deb-src https://private-ppa.launchpad.net/ubuntu-esm/esm-infra- security/ubuntu trusty main and then added credentials as follows to /etc/apt/auth.conf.d/ubuntu- security.conf: machine private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu login alexmurray password Running apt-get update then succeeds - but if I then try and run `apt- get source` to download from the PPA it fails: $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Err:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] Err:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.dsc 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch some archives. However if I edit /etc/apt/sources.list.d/ubuntu-security.list above to specify the credentials in-line then it succeeds: deb-src https://alexmurray:x...@private-ppa.launchpad.net/ubuntu- esm/esm-infra-security/ubuntu trusty main $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Get:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) [3,446 kB] Get:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) [1,604 B] Fetched 3,447 kB in 5s (657 kB/s) dpkg-source: info: extracting intel-microcode in intel-microcode-3.20201110.0ubuntu0.14.04.2 dpkg-source: info: unpacking intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz However now apt(-get) update complains about having credentials manually listed in the apt sources: $ sudo apt update ... N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu' ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 09:09:54 2020 InstallationDate: Installed on 2020-10-11 (32 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904068/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1904068] Re: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d)
Could you try changing the permissions back to something more strict (maybe 0600), and then changing ownership to the `apt` user/group? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904068 Title: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d) Status in apt package in Ubuntu: Confirmed Bug description: I have configured apt-src access to the private ESM PPAs via entries in /etc/apt/sources.list.d/ubuntu-security.list as follows: deb-src https://private-ppa.launchpad.net/ubuntu-esm/esm-infra- security/ubuntu trusty main and then added credentials as follows to /etc/apt/auth.conf.d/ubuntu- security.conf: machine private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu login alexmurray password Running apt-get update then succeeds - but if I then try and run `apt- get source` to download from the PPA it fails: $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Err:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] Err:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.dsc 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch some archives. However if I edit /etc/apt/sources.list.d/ubuntu-security.list above to specify the credentials in-line then it succeeds: deb-src https://alexmurray:x...@private-ppa.launchpad.net/ubuntu- esm/esm-infra-security/ubuntu trusty main $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Get:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) [3,446 kB] Get:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) [1,604 B] Fetched 3,447 kB in 5s (657 kB/s) dpkg-source: info: extracting intel-microcode in intel-microcode-3.20201110.0ubuntu0.14.04.2 dpkg-source: info: unpacking intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz However now apt(-get) update complains about having credentials manually listed in the apt sources: $ sudo apt update ... N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu' ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 09:09:54 2020 InstallationDate: Installed on 2020-10-11 (32 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904068] Re: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d)
This seems to be a simple permission problem. The user is not allowed to read /etc/apt/auth.conf.d/90ubuntu-advantage So instead of: apt-get source --only-source intel-microcode/trusty use: sudo apt-get source --only-source intel-microcode/trusty If you need to run it as a user fix the permissions of /etc/apt/auth.conf.d/90ubuntu-advantage Example: sudo chmod 644 /etc/apt/auth.conf.d/90ubuntu-advantage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1904068 Title: apt(-get) source fails to use credentials from /etc/apt/auth.conf(.d) Status in apt package in Ubuntu: Confirmed Bug description: I have configured apt-src access to the private ESM PPAs via entries in /etc/apt/sources.list.d/ubuntu-security.list as follows: deb-src https://private-ppa.launchpad.net/ubuntu-esm/esm-infra- security/ubuntu trusty main and then added credentials as follows to /etc/apt/auth.conf.d/ubuntu- security.conf: machine private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu login alexmurray password Running apt-get update then succeeds - but if I then try and run `apt- get source` to download from the PPA it fails: $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Err:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] Err:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu/pool/main/i/intel-microcode/intel-microcode_3.20201110.0ubuntu0.14.04.2.dsc 401 Unauthorized [IP: 2001:67c:1560:8008::15 443] E: Failed to fetch some archives. However if I edit /etc/apt/sources.list.d/ubuntu-security.list above to specify the credentials in-line then it succeeds: deb-src https://alexmurray:x...@private-ppa.launchpad.net/ubuntu- esm/esm-infra-security/ubuntu trusty main $ apt-get source --only-source intel-microcode/trusty Reading package lists... Done Selected version '3.20201110.0ubuntu0.14.04.2' (trusty) for intel-microcode NOTICE: 'intel-microcode' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/hmh/intel-microcode.git Please use: git clone https://salsa.debian.org/hmh/intel-microcode.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 3,447 kB of source archives. Get:1 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (tar) [3,446 kB] Get:2 https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu trusty/main intel-microcode 3.20201110.0ubuntu0.14.04.2 (dsc) [1,604 B] Fetched 3,447 kB in 5s (657 kB/s) dpkg-source: info: extracting intel-microcode in intel-microcode-3.20201110.0ubuntu0.14.04.2 dpkg-source: info: unpacking intel-microcode_3.20201110.0ubuntu0.14.04.2.tar.xz However now apt(-get) update complains about having credentials manually listed in the apt sources: $ sudo apt update ... N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'https://private-ppa.launchpad.net/ubuntu-esm/esm-infra-security/ubuntu' ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: apt 2.1.10 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 09:09:54 2020 InstallationDate: Installed on 2020-10-11 (32 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
I was able to confirm that this bug is present in Jammy, Kinetic, and Lunar. Focal does not have this bug. Thanks for the test case! ** Also affects: systemd (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Jammy) Status: New => Triaged ** Changed in: systemd (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Kinetic) Status: New => Triaged ** Changed in: systemd (Ubuntu Kinetic) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: Triaged Bug description: RFC3442 specifies option 121 (Classless Static Routes) that allow a DHCP server to push arbitrary routes to a client. It has a Local Subnet Routes section expliciting the behavior of routes with a null (0.0.0.0) gateway. Such routes are to be installed on the interface with a Link scope, to mark them as directly available on the link without any gateway. Networkd currently drops those routes, which is against the RFC, as Linux has proper support for such routes. This has been observed as broken on Ubuntu Jammy 22.04 LTS, but working in previous LTS (Focall 20.04 and Bionic 18.04 tested). 1. Ubuntu release: 22.04.1 LTS 2. Systemd release: 249.11-0ubuntu3.6 3. Expected behavior: routes from DHCP option 121 with a gateway set to 0.0.0.0 to be installed as "scope link" 4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp client (actually logged with a debug level, effectively silently with the default configuration) I wrote a fix that has been accepted in upstream systemd: https://github.com/systemd/systemd/pull/26234, which applies cleanly to the current package's sources obtained through apt-get source. As this is a fix for something that is an actual regression, can it be backported to Ubuntu 22.04's systemd tree? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641236] Re: Confined processes inside container cannot fully access host pty device passed in by lxc exec
I tried reproducing the issue on a 22.04 VM with a 22.04 container and I got some weird behavior, not consistent to what was reported in the comments, so I appreciate if anyone can also take a look. What I found is that I can only reproduce the issue when running tcpdump in --mode=non-interactive, regardless of AppArmor - I also didn't see any AppArmor denials in the logs when running the test. I have pasted my steps in https://pastebin.canonical.com/p/8NZngJF6nm/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641236 Title: Confined processes inside container cannot fully access host pty device passed in by lxc exec Status in apparmor package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in tcpdump package in Ubuntu: Confirmed Bug description: Now that AppArmor policy namespaces and profile stacking is in place, I noticed odd stdout buffering behavior when running confined processes via lxc exec. Much more data stdout data is buffered before getting flushed when the program is confined by an AppArmor profile inside of the container. I see that lxd is calling openpty(3) in the host environment, using the returned fd as stdout, and then executing the command inside of the container. This results in an AppArmor denial because the file descriptor returned by openpty(3) originates outside of the namespace used by the container. The denial is likely from glibc calling fstat(), from inside the container, on the file descriptor associated with stdout to make a decision on how much buffering to use. The fstat() is denied by AppArmor and glibc ends up handling the buffering differently than it would if the fstat() would have been successful. Steps to reproduce (using an up-to-date 16.04 amd64 VM): Create a 16.04 container $ lxc launch ubuntu-daily:16.04 x Run tcpdump in one terminal and generate traffic in another terminal (wget google.com) $ lxc exec x -- tcpdump -i eth0 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 47 packets captured 48 packets received by filter 1 packet dropped by kernel Note that everything above was printed immediately because it was printed to stderr. , which is printed to stdout, was not printed until you pressed ctrl-c and the buffers were flushed thanks to the program terminating. Also, this AppArmor denial shows up in the logs: audit: type=1400 audit(1478902710.025:440): apparmor="DENIED" operation="getattr" info="Failed name lookup - disconnected path" error=-13 namespace="root//lxd-x_" profile="/usr/sbin/tcpdump" name="dev/pts/12" pid=15530 comm="tcpdump" requested_mask="r" denied_mask="r" fsuid=165536 ouid=165536 Now run tcpdump unconfined and take note that is printed immediately, before you terminate tcpdump. Also, there are no AppArmor denials. $ lxc exec x -- aa-exec -p unconfined -- tcpdump -i eth0 ... Now run tcpdump confined but in lxc exec's non-interactive mode and note that is printed immediately and no AppArmor denials are present. (Looking at the lxd code in lxd/container_exec.go, openpty(3) is only called in interactive mode) $ lxc exec x --mode=non-interactive -- tcpdump -i eth0 ... Applications that manually call fflush(stdout) are not affected by this as manually flushing stdout works fine. The problem seems to be caused by glibc not being able to fstat() the /dev/pts/12 fd from the host's namespace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1641236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)
what does that mean for me?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/2004533
Title:
Gtk-WARNING ... drawing failure for widget ... invalid value
(typically too big)
Status in GTK+:
Unknown
Status in cairo package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
Triaged
Bug description:
A tiny sample of of my logs starting with the subject of this thread:
gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on
because it needs an allocation.
others
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite
surface size not supported
gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing
failure for widget 'GtkImage': invalid value (typically too big) for the size
of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too
big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically
too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
Feb 1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **:
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value
(typically too big) for the size of the input (surface, pattern, etc.)
st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout
("…")] which is not in the stage.
gnome-shell[15376]: Window manager warning: Buggy client sent a
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
Feb 1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage
0x556a2f5a5b70, but it still has children left:
Feb 1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
Feb 1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 1 23:40:47 2023
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'disable-user-extensions' b'true'
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
InstallationDate: Installed on 2021-01-17 (745 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43.0-1ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2004533/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002445] Re: udev NIC renaming race with mlx5_core driver
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/437150 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2002445 Title: udev NIC renaming race with mlx5_core driver Status in systemd package in Ubuntu: New Status in systemd source package in Focal: Triaged Status in systemd source package in Jammy: Triaged Status in systemd source package in Kinetic: New Status in systemd source package in Lunar: New Bug description: [Impact] On systems with mellanox NICs, udev's NIC renaming races with the mlx5_core driver's own configuration of subordinate interfaces. When the kernel wins this race, the device cannot be renamed as udev has attempted, and this causes systemd-network-online.target to timeout waiting for links to be configured. This ultimately results in boot being delayed by about 2 minutes. [Test Plan] Since this is a race condition, we need to boot many instances before we see the issue. The Ubuntu Server team will help coordinate the testing at scale to confirm the fix. [Where problems could occur] The patches effectively make it so that if a interface cannot be renamed from udev, then the new name is left as an alternative name as a fallback. If problems occur, it would be related to device renaming, and particularly related to the devices alternative names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2002445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006959] Re: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2006959 Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't have any further information. I got this message when I started using my machine for the day, without having interacted with the package manager recently. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1057-oem 5.14.0-1057.64 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 10 09:03:27 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (488 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006959] [NEW] package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: I don't have any further information. I got this message when I started using my machine for the day, without having interacted with the package manager recently. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1057-oem 5.14.0-1057.64 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 10 09:03:27 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (488 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2006959 Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: I don't have any further information. I got this message when I started using my machine for the day, without having interacted with the package manager recently. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1057-oem 5.14.0-1057.64 ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Feb 10 09:03:27 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-10-09 (488 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1057-oem 5.14.0-1057.64 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2006959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Checking in.
I've had an `apt-get update` running in a while loop since Feb 6 on a
machine: no luck getting it to stall.
Halfway, I added a `iptables -A INPUT -m statistic --mode random
--probability 0.05 -j DROP` but this did not affect anything.
But, in the mean time, on production I have had two more of these since
filing this bug report...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
New
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe
154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe
154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe
154026,apt-get,6r
http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe
154026,apt-get,12w
http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe
154026,apt-get,7r
gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe
154026,apt-get,14w
gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe
154026,apt-get,9r
```
So:
- apt-get is waiting for any data written by any of its four children (at fd
5/6/7/9)
- http and gpgv are waiting for any data written by their parent (at their
respective fd 0)
Parent backtrace:
```
#0 0x7f420116a74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f420153fb5d in pkgAcquire::Run(int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int)
()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4 0x7f42016d127b in DoUpdate (CmdL=...)
at ./apt-private/private-update.cc:73
#5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch
const*, bool) ()
from
[Touch-packages] [Bug 1987631] Re: Screencast only records one second
If gstreamer is fixed then any pipewire combination should work I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006955] [NEW] Screens not detected anymore
Public bug reported: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed 5.15.0-58-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 10 11:00:59 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-57-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1462:3816] InstallationDate: Installed on 2021-01-27 (743 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.20 dmi.board.name: B550 Phantom Gaming 4 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.20:bd08/13/2020:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB550PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: 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 N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2006955 Title: Screens not detected anymore Status in xorg package in Ubuntu: New Bug description: I have 3 monitors, but since very recently (yesterday or so), only 1 of them seems to be detected. In the Settings app, under "Screen Display", I used to have a place where I can move my monitors relatively to each other, and adjust each of their settings. Now, I no longer have the monitor drag-and-drop zone, I only have one detected "Unknown display", fixed at 1920x1080 77.00 Hz (physically, it's a 1920x1080 144Hz) and I cannot change any setting except orientation, scaling, and fractional scaling. The bug started happening just when the kernel was auto-updated to 5.15.0-60-generic from 5.15.0-58-generic. `uname -a` reports: `Linux user-desktop 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux`. When I reboot with 5.15.0-58-generic, all of my 3 displays are detected and working fine. I also noticed the same problem happened when I installed
[Touch-packages] [Bug 2006954] [NEW] openssl: merge unstable's 3.0.8-1
Public bug reported: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2006954 Title: openssl: merge unstable's 3.0.8-1 Status in openssl package in Ubuntu: New Bug description: Openssl 3.0.8 has been released. Unstable now contains 3.0.8-1 which we can merge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2006954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987631] Re: Screencast only records one second
The situation is a bit unclear there, the pipewire SRU got superseeded by a revert right, does that resolve the issue? Or is the request still trying to address the initially problem? Which component do you request to be updated exactly? pipewire with the previous failed SRU + extra fixes and gstreamers? Did anyone verify the impact on gnome-shell as pointed in #38? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in gst-plugins-base1.0 source package in Jammy: In Progress Status in gstreamer1.0 source package in Jammy: In Progress Status in pipewire source package in Jammy: In Progress Bug description: [Impact] When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5585 This issue is caused by the new two patches in 0.3.48-1ubuntu2 which is fixed the Cheese preview stuck issue on jammy * d/p/0001-buffers-ensure-buffer-size-does-not-exceed-maxsize.patch d/p/0002-gst-dequeue-a-shared-buffer-instead-of-original-pool.patch - Camera output freeze when using pipewiresrc (LP: #1985057) Here is a comment from https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1985057/comments/51 . === So that's a regression of one of the cherrypicked commits, details are in https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/d32c03488 the issue is fixed in Kinetic through a combination of the shell fix and a new pipewire. In 22.04 the shell issue is fixed in the recent 42.5 update but we will need to cherrypick https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525 in pipewire to be working. === [Test Plan] 1. Install Jammy on the hardware issue reported, and hardware didn't report the issue to avoid the regression hardware list: a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD b. 0c45:6747 Microdia Integrated_Webcam_HD c. 0c45:6a14 Microdia Integrated_Webcam_HD d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera f. 0408:545a Quanta Computer, Inc. HP 5MP Camera g. 0408:5483 Quanta Computer, Inc. HP HD Camera h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4) i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a) j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD 2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2) 3. $ sudo reboot 4. Check if gst-launch-1.0 work a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest gst-launch-1.0 command b. $ gst-launch-1.0 pipewiresrc path= ! ! decodebin ! videoconvert ! glimagesink c. Check if the result ok 5. Check the screencast function by pressing 'prt sc' a. the screenshot of all screen/selected region should work good b. the screenrecord of all screen/selected region should work good 6. Check that video recording in gnome-shell works - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, verify that there is a new entry in ~/Video 7. Check that screen sharing is working - go to settings, screen sharing and enable the feature - try to connect using rdp/vnc from another client do those steps under wayland and unset X [Where problems could occur] The patches try to dequeue the shared buffer, instead of pool buffer to prevent the pool buffer being corrupted. it might cause some camera preview failed if shared buffer is corrupted. It is from upstream and there is no regression found, so the risk is low. [Other Info] Upstream commits for pipewire: https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92 https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525c1ac946a915599c6bee813e88e8cee12 Upstream commits for gstreamer: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/3b900e1fa4fd888012dc005fa26ae2532a89b7a7 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
Thanks for the head's up! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: New Bug description: RFC3442 specifies option 121 (Classless Static Routes) that allow a DHCP server to push arbitrary routes to a client. It has a Local Subnet Routes section expliciting the behavior of routes with a null (0.0.0.0) gateway. Such routes are to be installed on the interface with a Link scope, to mark them as directly available on the link without any gateway. Networkd currently drops those routes, which is against the RFC, as Linux has proper support for such routes. This has been observed as broken on Ubuntu Jammy 22.04 LTS, but working in previous LTS (Focall 20.04 and Bionic 18.04 tested). 1. Ubuntu release: 22.04.1 LTS 2. Systemd release: 249.11-0ubuntu3.6 3. Expected behavior: routes from DHCP option 121 with a gateway set to 0.0.0.0 to be installed as "scope link" 4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp client (actually logged with a debug level, effectively silently with the default configuration) I wrote a fix that has been accepted in upstream systemd: https://github.com/systemd/systemd/pull/26234, which applies cleanly to the current package's sources obtained through apt-get source. As this is a fix for something that is an actual regression, can it be backported to Ubuntu 22.04's systemd tree? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
I haven't had time to test yet, but I will look into this and include the patch in the next Jammy SRU if needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: New Bug description: RFC3442 specifies option 121 (Classless Static Routes) that allow a DHCP server to push arbitrary routes to a client. It has a Local Subnet Routes section expliciting the behavior of routes with a null (0.0.0.0) gateway. Such routes are to be installed on the interface with a Link scope, to mark them as directly available on the link without any gateway. Networkd currently drops those routes, which is against the RFC, as Linux has proper support for such routes. This has been observed as broken on Ubuntu Jammy 22.04 LTS, but working in previous LTS (Focall 20.04 and Bionic 18.04 tested). 1. Ubuntu release: 22.04.1 LTS 2. Systemd release: 249.11-0ubuntu3.6 3. Expected behavior: routes from DHCP option 121 with a gateway set to 0.0.0.0 to be installed as "scope link" 4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp client (actually logged with a debug level, effectively silently with the default configuration) I wrote a fix that has been accepted in upstream systemd: https://github.com/systemd/systemd/pull/26234, which applies cleanly to the current package's sources obtained through apt-get source. As this is a fix for something that is an actual regression, can it be backported to Ubuntu 22.04's systemd tree? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562477] Re: apport-retrace crashed with TypeError in error(): not enough arguments for format string
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1562477 Title: apport-retrace crashed with TypeError in error(): not enough arguments for format string Status in Apport: Fix Released Status in apport package in Ubuntu: Triaged Bug description: Retracing the crash of window-buttons applet produced this error. ``` Traceback (most recent call last): File "/usr/bin/apport-retrace", line 301, in options.dynamic_origins) File "/usr/lib/python2.7/dist-packages/apport/sandboxutils.py", line 204, in make_sandbox apport.fatal(str(e)) File "/usr/lib/python2.7/dist-packages/apport/__init__.py", line 35, in fatal error(msg, *args) File "/usr/lib/python2.7/dist-packages/apport/__init__.py", line 44, in error sys.stderr.write(msg % args) TypeError: not enough arguments for format string ``` ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-retrace 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Mar 27 17:32:09 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/apport-retrace InstallationDate: Installed on 2015-09-28 (180 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/apport-retrace -S system -C /home/username/.cache/apport/retrace -v --gdb /var/crash/_usr_lib_gnome-window-applets_windowbuttons.1000.crash PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '/home/username/.cache/apport/retrace', '-v', '--gdb', '/var/crash/_usr_lib_gnome-window-applets_windowbuttons.1000.crash'] SourcePackage: apport Title: apport-retrace crashed with TypeError in error(): not enough arguments for format string UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kismet libvirtd lp lpadmin lxd mail mythtv plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1562477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1724623 Title: Update ubuntu cloud info Status in Apport: Fix Released Status in apport package in Ubuntu: New Status in cloud-init package in Ubuntu: Incomplete Bug description: add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul. Issues: - Using the presence of cloud-init to flag an image as a cloud image is incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images) - Using the presence of EC2 metadata source is incorrect as many non-EC2 clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are tagged as an 'ec2-images' bug which are clearly on openstack - Marking all bugs that have cloud-init but no EC2 metadata source as an 'uec-images' bug uses a name that no longer has meaning. Solution: - If cloud-init is present, check for /etc/cloud/build.info to indicate an Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial from that file into the bug comments. - If cloud-init is present, check for the presence of /run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type. Add the datasource used to the bug comment. I have filed bug #1724626 to ask cloud-init development to surface more information from ds-identify to help ID the cloud so that we can better tag/annotate the bug. There may also be some info we can get to indicate the image ID on more clouds than just AWS. At a minimum I would like to see dsidentify make the EC2 platform it found available for consumers in cloud.cfg. This would allow us to identify AWS EC2 from look-alike datasources so that we can tag a bug as ec2-images for bug really on AWS and add EC2 specific fields to the description/attachments. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1724623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56
** Changed in: apport
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1996040
Title:
apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
decode byte 0xfc in position 56
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Triaged
Status in apport source package in Kinetic:
New
Bug description:
Impact
==
apport-unpack and whoopsie-upload-all can crash when fed with a
malformed problem report. They should print a proper error message
instead of crashing. This bug does not happen that often, but the fix
for this bug is the foundation for the fix for bug #1995100.
Test Plan
=
1. Create malformed report:
```
printf 'AB\xfc:CD\n' > malformed.crash
```
2. Try to unpack it:
```
apport-unpack malformed.crash unpack
```
It should print an error message instead of a stack trace.
Where problems could occur
==
The patch touches the problem report handling and therefore can affect
apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
with tests and apport has a test suite running during build and as
autopkgtest.
Original report
===
The latest GitKraken client (8.10.2 x64) is crashed every minute in
cycle when you doing a rebase. When I try to inspect crash log to find
the reason, the apport-unpack is not be able to process it:
/var/lib/apport/coredump$ sudo apport-unpack
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
unpack
[sudo] пароль для mingun:
Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 59, in
pr.load(f, binary=False)
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
key = key.decode('ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56:
ordinal not in range(128)
Unfortunately, crash file is too big (~9GB) and does not compress
further
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1996040/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003098] Re: whoopsie-upload-all: package specific hooks not run
** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/2003098 Title: whoopsie-upload-all: package specific hooks not run Status in Apport: Fix Released Status in apport package in Ubuntu: Triaged Bug description: Commit f8edc7280d492e710218c193e53542f1f86cfa91 (for fixing bug #1983481) introduces a regression: The package specific hooks are not run in whoopsie-upload-all because add_hooks_info is called with ui=None. add_hooks_info will raise an AssertionError for ui=None. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/2003098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004478] Re: systemd-networkd's dhcp4 client ignores local subnet routes
Gentle ping? :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2004478 Title: systemd-networkd's dhcp4 client ignores local subnet routes Status in systemd package in Ubuntu: New Bug description: RFC3442 specifies option 121 (Classless Static Routes) that allow a DHCP server to push arbitrary routes to a client. It has a Local Subnet Routes section expliciting the behavior of routes with a null (0.0.0.0) gateway. Such routes are to be installed on the interface with a Link scope, to mark them as directly available on the link without any gateway. Networkd currently drops those routes, which is against the RFC, as Linux has proper support for such routes. This has been observed as broken on Ubuntu Jammy 22.04 LTS, but working in previous LTS (Focall 20.04 and Bionic 18.04 tested). 1. Ubuntu release: 22.04.1 LTS 2. Systemd release: 249.11-0ubuntu3.6 3. Expected behavior: routes from DHCP option 121 with a gateway set to 0.0.0.0 to be installed as "scope link" 4. Observed behavior: routes are silently dropped by systemd-networkd's dhcp client (actually logged with a debug level, effectively silently with the default configuration) I wrote a fix that has been accepted in upstream systemd: https://github.com/systemd/systemd/pull/26234, which applies cleanly to the current package's sources obtained through apt-get source. As this is a fix for something that is an actual regression, can it be backported to Ubuntu 22.04's systemd tree? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2004478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004039] Re: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes
Hello Tobias, or anyone else affected, Accepted libunwind into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libunwind/1.6.2-0ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libunwind (Ubuntu) Status: New => Fix Released ** Changed in: libunwind (Ubuntu Kinetic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/2004039 Title: libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with bigger page sizes Status in libunwind package in Ubuntu: Fix Released Status in libunwind source package in Kinetic: Fix Committed Bug description: [ Impact ] * On kernels with page size > 4K Xorg (and presumably other applications relying on libunwind) crashes on startup. This affects anyone running the official arm64 generic-64k kernel or custom non 4k kernels (as used by e.g. apple silicon). The exact error I am seeing in the logs is: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab456ca998] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) unw_get_proc_info failed: no unwind info found [-10] Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Segmentation fault at address 0x0 Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Fatal server error: Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Caught signal 11 (Segmentation fault). Server aborting Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: Please consult the The X.Org Foundation support Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: at http://wiki.x.org Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: for help. Jan 30 11:16:20 ubuntu /usr/libexec/gdm-x-session[3199]: (EE) I have not found a workaround other than using wayland (which has other limitations). To reproduce use a kernel configured with a page size of 16K (CONFIG_ARM64_16K_PAGES=y or CONFIG_ARM64_64K_PAGES=y or) and try to start "Ubuntu on Xorg" in gdm. [ Test Plan ] * Make sure Xorg doesn't crash on 4K, 16K and 64K kernels. [ Where problems could occur ] * We will have to make sure the fixed version still works with 4k kernels. The patch is already widely in use so the risk seems low if we test properly. [ Other Info ] * The lunar version ships the bug fix synced from debian * Debian bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1026217 * Upstream fix: https://github.com/libunwind/libunwind/commit/e85b65cec757ef589f28957d0c6c21c498a03bdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/2004039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784116] Re: ubuntu-bug reports the package from other arch as not installed
** Changed in: apport Milestone: 2.25.0 => 2.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1784116 Title: ubuntu-bug reports the package from other arch as not installed Status in Apport: Triaged Status in apport package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Minimal (+++) ubuntu-bug steam returns package not installed: -steam/bionic,now 1:1.0.0.54+repack-5ubuntu1 i386 [installed] -se attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1784116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006940] Re: PIN validation affects interface even if the manual token button is selected
** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/437144 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006940 Title: PIN validation affects interface even if the manual token button is selected Status in software-properties package in Ubuntu: In Progress Bug description: 1. software-properties-gtk 2. Go to Ubuntu Pro 3. Go to Enable Ubuntu Pro 4. Press "Or add token manually button" radio 5. Go to ubuntu.com/pro/attach and submit the PIN Expected: Nothing happens until the user clicks "Enter code..." radio. Observed: UI is locked with "Valid token" message next to the manual token field, which won't allow to attach the token received from PIN validation. Similar issue happens when PIN expires instead of being validated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006931] Re: /usr/bin/software-properties-gtk:TypeError:on_confirm_clicked:attach:__call__:call_async
** Merge proposal linked: https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/437143 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006931 Title: /usr/bin/software-properties- gtk:TypeError:on_confirm_clicked:attach:__call__:call_async Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/ad46a4f47c7f151d8719cb12227f57011b622f37 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006940] [NEW] PIN validation affects interface even if the manual token button is selected
Public bug reported: 1. software-properties-gtk 2. Go to Ubuntu Pro 3. Go to Enable Ubuntu Pro 4. Press "Or add token manually button" radio 5. Go to ubuntu.com/pro/attach and submit the PIN Expected: Nothing happens until the user clicks "Enter code..." radio. Observed: UI is locked with "Valid token" message next to the manual token field, which won't allow to attach the token received from PIN validation. Similar issue happens when PIN expires instead of being validated. ** Affects: software-properties (Ubuntu) Importance: High Assignee: Nathan Teodosio (nteodosio) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006940 Title: PIN validation affects interface even if the manual token button is selected Status in software-properties package in Ubuntu: In Progress Bug description: 1. software-properties-gtk 2. Go to Ubuntu Pro 3. Go to Enable Ubuntu Pro 4. Press "Or add token manually button" radio 5. Go to ubuntu.com/pro/attach and submit the PIN Expected: Nothing happens until the user clicks "Enter code..." radio. Observed: UI is locked with "Valid token" message next to the manual token field, which won't allow to attach the token received from PIN validation. Similar issue happens when PIN expires instead of being validated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006931] Re: /usr/bin/software-properties-gtk:TypeError:on_confirm_clicked:attach:__call__:call_async
I can reproduce the traceback by inserting token=None in attach(), so there must be a interaction path that will allow the user to try to attach even with such a token. ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Nathan Teodosio (nteodosio) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006931 Title: /usr/bin/software-properties- gtk:TypeError:on_confirm_clicked:attach:__call__:call_async Status in software-properties package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/ad46a4f47c7f151d8719cb12227f57011b622f37 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006931] [NEW] /usr/bin/software-properties-gtk:TypeError:on_confirm_clicked:attach:__call__:call_async
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/ad46a4f47c7f151d8719cb12227f57011b622f37 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2006931 Title: /usr/bin/software-properties- gtk:TypeError:on_confirm_clicked:attach:__call__:call_async Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22.5, the problem page at https://errors.ubuntu.com/problem/ad46a4f47c7f151d8719cb12227f57011b622f37 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2006931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2006925] [NEW] python architecture-dependant packages installed incorrectly
Public bug reported: postinst script in python2 packages generates __init__.py files for namespace packages. Since version 5.20211016 (commit 08ab39dfd34accb9220a087832b121279bbd9d98) arch is appended to package name to postinst script. However pycompile can't find namespace file with such package name -> namespace packages cannot be used in python2 (and python << 3.3). ** Affects: dh-python (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dh-python in Ubuntu. https://bugs.launchpad.net/bugs/2006925 Title: python architecture-dependant packages installed incorrectly Status in dh-python package in Ubuntu: New Bug description: postinst script in python2 packages generates __init__.py files for namespace packages. Since version 5.20211016 (commit 08ab39dfd34accb9220a087832b121279bbd9d98) arch is appended to package name to postinst script. However pycompile can't find namespace file with such package name -> namespace packages cannot be used in python2 (and python << 3.3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/2006925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
