[Touch-packages] [Bug 1539689] Re: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I think mine is the same. Problem with LVM2. Information as follows: Setting up lvm2 (2.03.07-1ubuntu1) ... update-initramfs: deferring update (trigger activated) Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked. invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed. ● lvm2-lvmpolld.service - LVM2 poll daemon Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor p reset: enabled) Active: inactive (dead) Docs: man:lvmpolld(8) dpkg: error processing package lvm2 (--configure): installed lvm2 package post-installation script subprocess returned error exit status 1 Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-7629-generic Errors were encountered while processing: lvm2 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1539689 Title: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in lvm2 package in Ubuntu: Triaged Bug description: I was trying to upgrade the system to see new updates on the Ubuntu 16.04. But it couldn't be finished because the operation stopped while upgrading lvm2. So I guess it broke the OS because I can't do the "apt-get upgrade" anymore. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu4 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CasperVersion: 1.366 Date: Fri Jan 29 16:32:35 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160128) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.1.10 SourcePackage: lvm2 Title: package lvm2 2.02.133-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1539689/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665
** Also affects: mesa (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Status: New => Won't Fix ** Changed in: mesa (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in Mutter: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Status in mesa source package in Focal: New Status in mutter source package in Focal: Won't Fix Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
[Touch-packages] [Bug 1881044] Re: wrong wayland dmabuf format selection with Intel iris
*** This bug is a duplicate of bug 1868520 *** https://bugs.launchpad.net/bugs/1868520 ** This bug has been marked a duplicate of bug 1868520 Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) -- 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/1881044 Title: wrong wayland dmabuf format selection with Intel iris Status in mesa package in Ubuntu: New Bug description: On Mesa 20.0.4, the Intel Iris driver is affected by an issue with selecting the appropriate dma buffer format on Wayland (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4869). This issue will prevent using most OpenGL applications on Wayland. You can check if you are affected by this issue by running `es2gears_wayland`. On affected systems, this will fail with `error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784`. This issue has been fixed in Mesa 20.0.7. Please consider backporting this version to Ubuntu 20.04 and 18.04.5. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgl1-mesa-dri 20.0.4-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 28 01:12:44 2020 DistUpgraded: 2020-04-26 01:28:24,019 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5034] MachineType: LENOVO 20BUS15H00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=d1694733-96aa-4a12-9c6f-2ed18308ab56 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to focal on 2020-04-26 (31 days ago) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS15H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BUS15H00:pvrThinkPadT450:rvnLENOVO:rn20BUS15H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS15H00 dmi.product.sku: LENOVO_MT_20BU_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1881044/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665
** No longer affects: mutter (Ubuntu) ** No longer affects: mutter (Ubuntu Focal) -- 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/1868520 Title: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010]) Status in Mesa: Fix Released Status in MPV: Unknown Status in Mutter: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: New Bug description: [Impact] Wayland apps fail to start in focal with: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 [Test Case] Just run: es2gears_wayland [Regression Potential] Medium/unknown. The fix is quite new. [Other Info] When attempting to run es2gears_wayland against GNOME Shell, it fails with: EGL_VERSION = 1.5 vertex shader info: fragment shader info: info: [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported buffer format 808669784 The full wayland protocol trace is: [3104432.914] -> wl_display@1.get_registry(new id wl_registry@2) [3104432.972] -> wl_disp...@1.sync(new id wl_callback@3) [3104433.139] wl_display@1.delete_id(3) [3104433.175] wl_registry@2.global(1, "wl_drm", 2) [3104433.207] wl_registry@2.global(2, "wl_compositor", 4) [3104433.240] -> wl_regis...@2.bind(2, "wl_compositor", 1, new id [unknown]@4) [3104433.285] wl_registry@2.global(3, "wl_shm", 1) [3104433.316] wl_registry@2.global(4, "wl_output", 2) [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3) [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3) [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 1) [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1) [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2) [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1) [3104433.513] wl_registry@2.global(11, "wl_shell", 1) [3104433.542] -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5) [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3) [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1) [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1) [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1) [3104433.699] wl_registry@2.global(16, "wl_seat", 5) [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1) [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1) [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1) [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1) [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3) [3104433.875] wl_registry@2.global(22, "zwp_keyboard_shortcuts_inhibit_manager_v1", 1) [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1) [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1) [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1) [3104433.991] wl_callb...@3.done(3421) [3104436.266] -> wl_display@1.get_registry(new id wl_registry@3) [3104436.279] -> wl_disp...@1.sync(new id wl_callback@6) [3104436.647] wl_display@1.delete_id(6) [3104436.672] wl_registry@3.global(1, "wl_drm", 2) [3104436.726] -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7) [3104436.744] wl_registry@3.global(2, "wl_compositor", 4) [3104436.780] wl_registry@3.global(3, "wl_shm", 1) [3104436.790] wl_registry@3.global(4, "wl_output", 2) [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3) [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3) [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 1) [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1) [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2) [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1) [3104436.925] wl_registry@3.global(11, "wl_shell", 1) [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3) [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1) [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1) [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1) [3104436.990] wl_registry@3.global(16, "wl_seat", 5) [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1) [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1) [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1) [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1) [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3) [3104437.066] -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id [unknown]@8) [3104437.083] wl_registry@3.global(22,
[Touch-packages] [Bug 1877183] Re: segfault in mysql_server_end() from libmysqlclient.so.21
*** This bug is a duplicate of bug 1877504 *** https://bugs.launchpad.net/bugs/1877504 The bug started to trigger after an update to libmysqlclient21 from 8.0.19 to 8.0.20. This is Oracle MySQL being backwards incompatible with any earlier version of MySQL or MariaDB. Please don't imply that the MariaDB packaging in any way caused this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1877183 Title: segfault in mysql_server_end() from libmysqlclient.so.21 Status in mysql-8.0 package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: libmysqlclient.so.21 causes a segfault on shutdown. Test case attached ==> "Removed database" will not be reported. Backtrace: #0 0x714c330f in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #1 0x714c8823 in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #2 0x71466243 in mysql_server_end () from /lib/x86_64-linux-gnu/libmysqlclient.so.21 #3 0x71b4d0ee in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #4 0x71b4d10d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so #5 0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #6 0x778e588e in QSqlDatabase::~QSqlDatabase() () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #7 0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5 #8 0x5579 in cause_segfault () at main.cpp:16 #9 0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed May 6 21:40:58 2020 InstallationDate: Installed on 2020-04-27 (9 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1877183/+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 1877017] Re: package vim-runtime 2:8.1.2269-1ubuntu5 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted
*** This bug is a duplicate of bug 1877024 *** https://bugs.launchpad.net/bugs/1877024 ** This bug has been marked a duplicate of bug 1877024 package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: unable to open '/usr/lib/libreoffice/share/gallery/environment.sdg.dpkg-new': Operation not permitted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1877017 Title: package vim-runtime 2:8.1.2269-1ubuntu5 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted Status in vim package in Ubuntu: New Bug description: Installing vim via cli, and came back with error. Ran again with no errors. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: vim-runtime 2:8.1.2269-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: vim-runtime:amd64: Install vim:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 5 20:45:35 2020 ErrorMessage: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted InstallationDate: Installed on 2020-05-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: vim Title: package vim-runtime 2:8.1.2269-1ubuntu5 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/vim-runtime.list-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1877017/+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 1876952] Re: missing a package hook for linux-raspi and linux-raspi2
This bug was fixed in the package apport - 2.20.11-0ubuntu27.2 --- apport (2.20.11-0ubuntu27.2) focal; urgency=medium * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) apport (2.20.11-0ubuntu27.1) focal; urgency=medium * debian/apport.install: Add in a source package hook for linux-meta-raspi which provides linux-raspi and linux-raspi2. (LP: #1876952) * data/general-hooks/ubuntu.py: collect ImageMediaBuild information which exists on preinstalled RPi images. (LP: #1876945) * Add in a source package hook symlink for linux-firmware. (LP: #1872059) * debian/tests/control: Depend on python3-twisted, not python-twisted-core -- Brian Murray Tue, 12 May 2020 15:34:22 -0700 ** Changed in: apport (Ubuntu Focal) 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/1876952 Title: missing a package hook for linux-raspi and linux-raspi2 Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Apport does not include a source package hook for the linux-raspi or linux-raspi2 kernels which are used on the Raspberry Pi images, subsequently if 'ubuntu-bug linux-raspi' is used valuable information will not be collected. Test Case - 1) On a Raspberry Pi run 'ubuntu-bug linux-raspi'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Repeat the test case for 'linux-raspi2'. Regression Potential None, as we are just adding a symlink from linux-meta-raspi to the linux source package hook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876952/+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 1774843] Re: apport python exception for python versions which python-apt is not built on
** Changed in: apport (Ubuntu Focal) Status: Invalid => New -- 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/1774843 Title: apport python exception for python versions which python-apt is not built on Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Invalid Status in python3.8 package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Won't Fix Status in python3.8 source package in Bionic: Won't Fix Status in apport source package in Eoan: Fix Released Status in python3.7 source package in Eoan: Won't Fix Status in python3.8 source package in Eoan: Won't Fix Status in apport source package in Focal: New Status in python3.7 source package in Focal: Invalid Status in python3.8 source package in Focal: Invalid Bug description: [Impact] apport's python crash handler runs for every installed version of python e.g. on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an interpreter. However, python apt modules are only available for the the supported version of python so the crash handler generates an exception which is annoying. [Test Case] 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 LTS. 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2. [Regression Potential] Its possible the crash handler change is incorrect so it should be confirmed that we still get python crashes about the system version of python. One way to do this is to run 'apport-cli coreutils < /dev/null'. [NOTE] It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only python3.8 available, so I haven't. [Original Description] it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >> import apt_pkg Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'apt_pkg' To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1774843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on
This bug was fixed in the package apport - 2.20.9-0ubuntu7.15 --- apport (2.20.9-0ubuntu7.15) bionic; urgency=medium * apport_python_hook.py: if python apt modules are not built for the python version then do capture the crash. (LP: #1774843) -- Brian Murray Wed, 13 May 2020 15:12:14 -0700 ** Changed in: apport (Ubuntu Bionic) 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/1774843 Title: apport python exception for python versions which python-apt is not built on Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Invalid Status in python3.8 package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Won't Fix Status in python3.8 source package in Bionic: Won't Fix Status in apport source package in Eoan: Fix Released Status in python3.7 source package in Eoan: Won't Fix Status in python3.8 source package in Eoan: Won't Fix Status in apport source package in Focal: New Status in python3.7 source package in Focal: Invalid Status in python3.8 source package in Focal: Invalid Bug description: [Impact] apport's python crash handler runs for every installed version of python e.g. on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an interpreter. However, python apt modules are only available for the the supported version of python so the crash handler generates an exception which is annoying. [Test Case] 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 LTS. 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2. [Regression Potential] Its possible the crash handler change is incorrect so it should be confirmed that we still get python crashes about the system version of python. One way to do this is to run 'apport-cli coreutils < /dev/null'. [NOTE] It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only python3.8 available, so I haven't. [Original Description] it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>
[Touch-packages] [Bug 1774843] Re: apport python exception for python versions which python-apt is not built on
This bug was fixed in the package apport - 2.20.11-0ubuntu8.9 --- apport (2.20.11-0ubuntu8.9) eoan; urgency=medium * apport_python_hook.py: if python apt modules are not built for the python version then do capture the crash. (LP: #1774843) -- Brian Murray Wed, 13 May 2020 14:09:52 -0700 ** Changed in: apport (Ubuntu Eoan) 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/1774843 Title: apport python exception for python versions which python-apt is not built on Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Invalid Status in python3.8 package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Won't Fix Status in python3.8 source package in Bionic: Won't Fix Status in apport source package in Eoan: Fix Released Status in python3.7 source package in Eoan: Won't Fix Status in python3.8 source package in Eoan: Won't Fix Status in apport source package in Focal: New Status in python3.7 source package in Focal: Invalid Status in python3.8 source package in Focal: Invalid Bug description: [Impact] apport's python crash handler runs for every installed version of python e.g. on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an interpreter. However, python apt modules are only available for the the supported version of python so the crash handler generates an exception which is annoying. [Test Case] 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 LTS. 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2. [Regression Potential] Its possible the crash handler change is incorrect so it should be confirmed that we still get python crashes about the system version of python. One way to do this is to run 'apport-cli coreutils < /dev/null'. [NOTE] It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only python3.8 available, so I haven't. [Original Description] it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>
[Touch-packages] [Bug 1774843] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1774843 Title: apport python exception for python versions which python-apt is not built on Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in python3.7 package in Ubuntu: Invalid Status in python3.8 package in Ubuntu: Invalid Status in apport source package in Bionic: Fix Released Status in python3.7 source package in Bionic: Won't Fix Status in python3.8 source package in Bionic: Won't Fix Status in apport source package in Eoan: Fix Released Status in python3.7 source package in Eoan: Won't Fix Status in python3.8 source package in Eoan: Won't Fix Status in apport source package in Focal: New Status in python3.7 source package in Focal: Invalid Status in python3.8 source package in Focal: Invalid Bug description: [Impact] apport's python crash handler runs for every installed version of python e.g. on Ubuntu 18.04 LTS it will run for crashes with python3.6 or python3.7 as an interpreter. However, python apt modules are only available for the the supported version of python so the crash handler generates an exception which is annoying. [Test Case] 1) Install the non-default version of python3 e.g. python3.7 on Ubuntu 18.04 LTS. 2) Run 'python3.7 -c 'print hello' and observe a Traceback re apt_pkg not being found. With the version of python3-apport from -proposed you'll not receive the Traceback from step # 2. [Regression Potential] Its possible the crash handler change is incorrect so it should be confirmed that we still get python crashes about the system version of python. One way to do this is to run 'apport-cli coreutils < /dev/null'. [NOTE] It isn't necessary to fix this in Ubuntu 20.04 LTS, as there is only python3.8 available, so I haven't. [Original Description] it seems apport installs an exception hook whenever running python3. This hook is apparently installed for python3.7 too. This exception handler has a dependency on apt_pkg, which is a binary that is not compatible with python3.7 it seems (you can't import it, see below) As a result, whenever I run a python3.7 script and run into an exception (which happens often when writing code), I get an additional exception in the exception handler + a copy of the original exception, so three stacktraces in total. A solution would be to only install the exception hook for the system python i.e. python3.6 $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apport: 2.20.9-0ubuntu7 python-apt: 1.6.0 python3.7: 3.7.0~b3-1 Demo with a trivial error: $ python3 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? $ python3.7 -c 'print hello' File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 24, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ModuleNotFoundError: No module named 'apt_pkg' Original exception was: File "", line 1 print hello ^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(hello)? Python 3.6.5 (default, Apr 1 2018, 05:46:30) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sys >>> sys.excepthook >>> import apt_pkg >>> apt_pkg.__file__ '/usr/lib/python3/dist-packages/apt_pkg.cpython-36m-x86_64-linux-gnu.so' >>> Python 3.7.0b3 (default, Mar 30 2018, 04:35:22) [GCC 7.3.0] on linux Type "help", "copyright", "credits" or "license" for
[Touch-packages] [Bug 708516] Re: Mesa alternative on libGL not set in natty
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
--
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/708516
Title:
Mesa alternative on libGL not set in natty
Status in mesa package in Ubuntu:
Invalid
Bug description:
In the changelog of mesa, it says:
"
- rules, libgl1-mesa-{glx,dev,swx11,swx11-dev}.install,
libgl1-mesa-{glx,swx11}.{postinst,prerm}, libgl1-mesa-dev.links:
Install libGL.so* in /usr/lib/mesa to allow things to work with
alternatives.
"
However, I do not have any libGL.so* symlink in /usr/lib/ and there is
no reference to libGL in alternatives.
This breaks some software which are expecting libGL in /usr/lib/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/708516/+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 1844775] Re: HDR support for Ubuntu
** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu Status in ffmpeg package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in weston package in Ubuntu: Confirmed Bug description: This is a tracker bug for getting HDR support integrated in Ubuntu. Kernel i915: - 5.3 (Ice Lake) - plus at least https://patchwork.freedesktop.org/series/65656/ - gen4+ needs https://patchwork.freedesktop.org/series/63373/ - so anything beyond initial Ice Lake support will not be in 5.4 Mesa - needs current git master plus https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942 Mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/804 Weston: https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: Confirmed => Invalid
--
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/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
Status in NVIDIA Drivers Ubuntu:
New
Status in mesa package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
Invalid
Status in pyqt5 package in Ubuntu:
Invalid
Status in python-qt4 package in Ubuntu:
Invalid
Bug description:
I'm having trouble with a combination of NVIDIA + Python + Qt +
Opengl.
I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and
errors like this these:
QGLShader: could not create shader
Vertex shader for simpleShaderProg (MainVertexShader
) failed to compile
This is an example application triggering the problem:
http://pastebin.com/R0aa8ejs
The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this
error when trying the original demo application from python-qt4-doc. Also,
calling
QtGui.QApplication.setGraphicsSystem("opengl")
produces the same errors.
I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
provided nvidia drivers (where 12.04 includes the most recent driver
for now). After installing the driver using the original NVidia
installer, the applications work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 647731] Re: java SIGSEGV in libGL.so.1
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/647731 Title: java SIGSEGV in libGL.so.1 Status in mesa package in Ubuntu: Invalid Bug description: Java crashes when opengl is enabled (using sun-java-6-jdk with -Dsun.java2d.opengl=true). OpenJDK seems to have the same problem. using integrated Intel GMA 4500MHD: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f67dc346ff9, pid=29619, tid=140083940497168 # # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode linux-amd64 ) # Problematic frame: # C [libGL.so.1+0x4bff9] # # An error report file with more information is saved as: # /home/simon/hs_err_pid29619.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # using discrete ATI Mobility Radeon HD 3470 graphics, not using fglrx: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f6623c7c38e, pid=27532, tid=140077664519952 # # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode linux-amd64 ) # Problematic frame: # C [libGL.so.1+0x5b38e] XF86DRIQueryVersion+0xae # # An error report file with more information is saved as: # /home/simon/hs_err_pid27532.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # I saved both error report files, I'll post them if you need them. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libgl1-mesa-glx 7.9~git20100909-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1440x900 1440x900 1280x854 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480 edid-base64: AP///wAwrjZRAQOAHhN46s11kVVPiyYhUFQBAQEBAQEBAQEBAQEBAQEBrCeghFGEGjAwIDYAL74QAAAZ1SGg+FCEfjAwIDYAL74QAAAZDwCVCjKVCigZCQBMo1dU/gBMVE4xNDFCVDA0MDAyAL4= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: Date: Sat Sep 25 22:07:12 2010 DkmsStatus: tp-smapi, 0.40, 2.6.35-22-generic, x86_64: installed vboxdrv, 3.2.8, 2.6.35-22-generic, x86_64: installed vboxnetflt, 3.2.8, 2.6.35-22-generic, x86_64: installed vboxnetadp, 3.2.8, 2.6.35-22-generic, x86_64: installed fglrx, 8.780, 2.6.35-22-generic, x86_64: installed InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100831.2) MachineType: LENOVO 276552G PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic root=/dev/mapper/LVM--Thor-root ro quiet splash ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: mesa dmi.bios.date: 07/30/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7VET87WW (3.17 ) dmi.board.name: 276552G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7VET87WW(3.17):bd07/30/2010:svnLENOVO:pn276552G:pvrThinkPadT400:rvnLENOVO:rn276552G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 276552G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO glxinfo: Error: command ['glxinfo'] failed with exit code -11: system: distro: Ubuntu codename: maverick architecture: x86_64 kernel: 2.6.35-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/647731/+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 1224940] Re: [r600] unity_support_test crashed with SIGSEGV in do_winsys_init()
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/1224940 Title: [r600] unity_support_test crashed with SIGSEGV in do_winsys_init() Status in mesa package in Ubuntu: Invalid Bug description: Upgraded from 13.04 to 13.10. Running on Xen 4.2 with Openswitch. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: nux-tools 4.0.2+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0 Uname: Linux 3.11.0-7-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: (process:5483): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. (process:5483): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: (process:5481): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. (process:5481): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. true CrashCounter: 1 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Sep 13 08:03:06 2013 DistUpgraded: 2013-04-01 12:10:36,712 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: blktap, 2.0.93, 3.11.0-7-generic, x86_64: installed blktap, 2.0.93, 3.8.0-26-generic, x86_64: installed blktap, 2.0.93, 3.8.0-27-generic, x86_64: installed blktap, 2.0.93, 3.8.0-30-generic, x86_64: installed openvswitch, 1.10.2: added ExecutablePath: /usr/lib/nux/unity_support_test GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126] InstallationDate: Installed on 2013-04-01 (164 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC MarkForUpload: True ProcCmdline: /usr/lib/nux/unity_support_test ProcEnviron: LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: placeholder root=/dev/mapper/ubuntu-root ro quiet splash SegvAnalysis: Segfault happened at: 0x7f70f6d32549 : mov (%rax),%r8d PC (0x7f70f6d32549) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%r8d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nux StacktraceTop: radeon_drm_winsys_create () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 Title: unity_support_test crashed with SIGSEGV in radeon_drm_winsys_create() UpgradeStatus: Upgraded to saucy on 2013-04-01 (164 days ago) UserGroups: sudo XsessionErrors: (process:3487): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. (process:3487): dconf-CRITICAL **: unable to create file '/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied. dconf will not work properly. dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.asset.tag: 2UA125069Q dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA125069Q dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)
Thanks a lot for the fix! How about a SRU for focal? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in lvm2 package in Ubuntu: Fix Released Bug description: Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871154/+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 1544699] Re: package libgl1-mesa-glx 11.0.2-1ubuntu4 failed to install/upgrade: 0:subprocess installed post-installation script returned error exit status 2
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1544699 Title: package libgl1-mesa-glx 11.0.2-1ubuntu4 failed to install/upgrade: 0:subprocess installed post-installation script returned error exit status 2 Status in mesa package in Ubuntu: Invalid Bug description: n/a ProblemType: Package DistroRelease: Ubuntu 15.10 Package: libgl1-mesa-glx 11.0.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 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 Feb 10 22:48:04 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-glx:11.0.2-1ubuntu4:0:subprocess installed post-installation script returned error exit status 2 ErrorMessage: 0:subprocess installed post-installation script returned error exit status 2 GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3117] InstallationDate: Installed on 2011-11-16 (1547 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Gigabyte Technology Co., Ltd. EP45-UD3R ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=d7c5c03a-9573-4fb2-8d56-bd7a922b7a5f ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: mesa Title: package libgl1-mesa-glx 11.0.2-1ubuntu4 failed to install/upgrade: 0:subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6 dmi.board.name: EP45-UD3R dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/13/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3R dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Feb 11 10:17:42 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 8 inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9 inputLogitech M325MOUSE, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1544699/+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 1494375] Re: package libegl1-mesa:amd64 10.1.3-0ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1494375 Title: package libegl1-mesa:amd64 10.1.3-0ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in mesa package in Ubuntu: Invalid Bug description: Hey Dood ya got me. Just a routing update to 14.04 (Kubuntu actually) and this is how it turned out. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libegl1-mesa:amd64 10.1.3-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Uname: Linux 3.13.0-63-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: amd64 Date: Thu Sep 10 11:11:20 2015 DuplicateSignature: package:libegl1-mesa:amd64:10.1.3-0ubuntu0.4:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2015-01-22 (230 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: mesa Title: package libegl1-mesa:amd64 10.1.3-0ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1494375/+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 1871185] Re: urls in ubuntu-bug's dialog not really clickable
This bug was fixed in the package apport - 2.20.11-0ubuntu27.2 --- apport (2.20.11-0ubuntu27.2) focal; urgency=medium * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) apport (2.20.11-0ubuntu27.1) focal; urgency=medium * debian/apport.install: Add in a source package hook for linux-meta-raspi which provides linux-raspi and linux-raspi2. (LP: #1876952) * data/general-hooks/ubuntu.py: collect ImageMediaBuild information which exists on preinstalled RPi images. (LP: #1876945) * Add in a source package hook symlink for linux-firmware. (LP: #1872059) * debian/tests/control: Depend on python3-twisted, not python-twisted-core -- Brian Murray Tue, 12 May 2020 15:34:22 -0700 ** Changed in: apport (Ubuntu Focal) 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/1871185 Title: urls in ubuntu-bug's dialog not really clickable Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. Test Case - 1) On an Ubuntu 20.04 LTS system run 'ubuntu-bug chromium' 2) Observe a "the problem cannot be reported" message with a link that is not fully highlighted With the version of apport from -proposed the link will be fully highlighted and will be clickable. Regression Potential The re for what constitutes a url is just improved and the snap dialog is the only one I can find with a url in it. Given that url highlighting is "broken" there isn't any potential for regression. Original Description ProblemType: BugDistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1422799] Re: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1422799 Title: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in mesa package in Ubuntu: Invalid Bug description: To be honest this bug has not harmed the computer as far as I can see, the system runs anyway but keeps on telling me there is an error?? ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-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 Date: Tue Feb 17 12:39:01 2015 DistUpgraded: 2014-08-13 01:19:26,147 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-glx:amd64:10.1.3-0ubuntu0.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fc31] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fc31] InstallationDate: Installed on 2012-05-18 (1004 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: TOSHIBA SATELLITE P755 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=02a795c8-a998-48fa-a9b7-f7624e8b0580 ro quiet splash vt.handoff=7 SourcePackage: mesa Title: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-08-13 (188 days ago) dmi.bios.date: 03/28/2011 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.80 dmi.board.asset.tag: NULL dmi.board.name: PEQAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr1.80:bd03/28/2011:svnTOSHIBA:pnSATELLITEP755:pvrPSAY3E-01C00QIT:rvnTOSHIBA:rnPEQAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: SATELLITE P755 dmi.product.version: PSAY3E-01C00QIT dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Feb 17 13:03:23 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 732 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1422799/+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 1426213] Re: package libgl1-mesa-glx 10.3.2-0ubuntu0.1 failed to install/upgrade: 65.8474:subprocess installed post-installation script returned error exit status 2
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1426213 Title: package libgl1-mesa-glx 10.3.2-0ubuntu0.1 failed to install/upgrade: 65.8474:subprocess installed post-installation script returned error exit status 2 Status in mesa package in Ubuntu: Invalid Bug description: On upgrade from 14.04 to 14.10, libgl1-mesa-glx:amd64 caused everything to fail. What I did to fix was run: sudo dpkg --force-all --configure libgl1-mesa-glx but it gave me an error that it couldn't delete /etc/ati because it was a directory. Deleted that directory, tried again, worked. Continued with: sudo dpkg --configure -a and all seems well now. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libgl1-mesa-glx 10.3.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.2 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: Thu Feb 26 22:13:54 2015 DistUpgraded: 2015-02-26 22:18:27,898 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-glx:10.3.2-0ubuntu0.1:65.8474:subprocess installed post-installation script returned error exit status 2 ErrorMessage: 65.8474:subprocess installed post-installation script returned error exit status 2 ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] [1002:6798] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:3001] MachineType: Gigabyte Technology Co., Ltd. Z87X-D3H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=737851bb-3454-41c1-b6fc-dbef93f93d6d ro quiet splash nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: mesa Title: package libgl1-mesa-glx 10.3.2-0ubuntu0.1 failed to install/upgrade: 65.8474:subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to utopic on 2015-02-27 (0 days ago) dmi.bios.date: 08/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/02/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Feb 26 16:40:29 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1426213/+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 927168] Re: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTex
** Changed in: mesa (Ubuntu) Importance: High => Wishlist -- 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/927168 Title: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry() Status in Compiz: Fix Released Status in Compiz Core: Confirmed Status in Mesa: Unknown Status in compiz package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in compiz source package in Quantal: Fix Released Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 Date: Sun Feb 5 12:47:01 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (2029.1) ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x558360: movdqu (%eax),%xmm0 PC (0x00558360) ok source "(%eax)" (0x81577fc0) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: compiz crashed with SIGSEGV UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/927168/+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 977804] Re: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device)
is this still an issue on 20.04? ** Changed in: mesa (Ubuntu) Importance: High => Low ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/977804 Title: Unity crashes when many windows are opened (intel_do_flush_locked failed: No space left on device) Status in Unity: Confirmed Status in mesa package in Ubuntu: Incomplete Status in unity package in Ubuntu: Confirmed Status in Debian: New Status in mesa package in Fedora: Won't Fix Bug description: Unity 5.8.0 (Ubuntu 12.04 Beta) crashes (or hanged up) on Fujitsu-Siemens S7020 (Intel 915GM Express Chipset) very often during attempt to use Dash or switch between applications when many winsows are opened with following error: intel_do_flush_locked failed: No space left on device ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic-pae 3.2.14 Uname: Linux 3.2.0-22-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 2.0-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Tue Apr 10 11:25:45 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120314) MachineType: FUJITSU SIEMENS LIFEBOOK S7020 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-22-generic-pae root=UUID=e6a4deb8-3e53-4afb-aed8-997537309262 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2005 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.07 dmi.board.name: FJNB19C dmi.board.vendor: FUJITSU dmi.board.version: CP234410-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7020 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.07:bd09/16/2005:svnFUJITSUSIEMENS:pnLIFEBOOKS7020:pvr:rvnFUJITSU:rnFJNB19C:rvrCP234410-02:cvnFUJITSUSIEMENS:ct10:cvrS7020: dmi.product.name: LIFEBOOK S7020 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/977804/+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 1516342] Re: package libgbm1 10.1.3-0ubuntu0.4 failed to install/upgrade: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1516342 Title: package libgbm1 10.1.3-0ubuntu0.4 failed to install/upgrade: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory Status in mesa package in Ubuntu: Invalid Bug description: When I start install or download some thing then I'm facing this Issue. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.4 ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-53-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 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 Nov 15 10:26:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../libgbm1_10.1.3-0ubuntu0.5_amd64.deb ... Unpacking libgbm1:amd64 (10.1.3-0ubuntu0.5) over (10.1.3-0ubuntu0.4) ... dpkg: error processing archive /var/cache/apt/archives/libgbm1_10.1.3-0ubuntu0.5_amd64.deb (--unpack): unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory DuplicateSignature: package:libgbm1:10.1.3-0ubuntu0.4:unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory ErrorMessage: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0606] InstallationDate: Installed on 2015-03-26 (233 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Latitude 3440 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-53-generic root=UUID=dd15110f-88bb-4d1a-ae0b-deb3d80f639b ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: mesa Title: package libgbm1 10.1.3-0ubuntu0.4 failed to install/upgrade: unable to install (supposed) new info file `/var/lib/dpkg/tmp.ci/symbols': Is a directory UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0X0J08 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd08/11/2014:svnDellInc.:pnLatitude3440:pvrNotSpecified:rvnDellInc.:rn0X0J08:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Latitude 3440 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Nov 15 09:38:17 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12604 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1516342/+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 1876952] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876952 Title: missing a package hook for linux-raspi and linux-raspi2 Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Apport does not include a source package hook for the linux-raspi or linux-raspi2 kernels which are used on the Raspberry Pi images, subsequently if 'ubuntu-bug linux-raspi' is used valuable information will not be collected. Test Case - 1) On a Raspberry Pi run 'ubuntu-bug linux-raspi'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Repeat the test case for 'linux-raspi2'. Regression Potential None, as we are just adding a symlink from linux-meta-raspi to the linux source package hook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876952/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
This bug was fixed in the package apport - 2.20.11-0ubuntu27.2 --- apport (2.20.11-0ubuntu27.2) focal; urgency=medium * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) apport (2.20.11-0ubuntu27.1) focal; urgency=medium * debian/apport.install: Add in a source package hook for linux-meta-raspi which provides linux-raspi and linux-raspi2. (LP: #1876952) * data/general-hooks/ubuntu.py: collect ImageMediaBuild information which exists on preinstalled RPi images. (LP: #1876945) * Add in a source package hook symlink for linux-firmware. (LP: #1872059) * debian/tests/control: Depend on python3-twisted, not python-twisted-core -- Brian Murray Tue, 12 May 2020 15:34:22 -0700 ** Changed in: apport (Ubuntu Focal) 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1876945] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1876945 Title: collect '/.disk/info' from RPi preinstalled systems Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Apport should collect the image build information from a system on which it is being ran. Test Case - 1) On a Raspberry Pi run 'ubuntu-bug linux-raspi'. 2) Choose 'View report' 3) Observe that 'ImageMediaBuild' is not collected With the version of apport from -proposed 'ImageMediaBuild' will be in the report and will have the same contents as '/.disk/info'. Regression Potential Apport's hooktutils.py is fault tolerant and will not crash if the system does not have a '/.disk/info' file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876945/+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 1872059] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Invalid Status in apport source package in Focal: Fix Released Status in linux-firmware source package in Focal: Invalid Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. Test Case - 1) On an Ubuntu 20.04 LTS system run 'apport-cli linux-firmware'. 2) Choose 'View report' 3) Observe that 'ProcFB' is not collected With the version of apport from -proposed 'ProcFB' will be in the report. Regression Potential None, as we are just adding a symlink from linux-firmware to the linux source package hook. Original Description ProblemType: BugDistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: allSourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1876945] Re: collect '/.disk/info' from RPi preinstalled systems
This bug was fixed in the package apport - 2.20.11-0ubuntu27.2 --- apport (2.20.11-0ubuntu27.2) focal; urgency=medium * gtk/apport-gtk: upgrade regular expression used to match URLs in free text (LP: #1871185) apport (2.20.11-0ubuntu27.1) focal; urgency=medium * debian/apport.install: Add in a source package hook for linux-meta-raspi which provides linux-raspi and linux-raspi2. (LP: #1876952) * data/general-hooks/ubuntu.py: collect ImageMediaBuild information which exists on preinstalled RPi images. (LP: #1876945) * Add in a source package hook symlink for linux-firmware. (LP: #1872059) * debian/tests/control: Depend on python3-twisted, not python-twisted-core -- Brian Murray Tue, 12 May 2020 15:34:22 -0700 ** Changed in: apport (Ubuntu Focal) 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/1876945 Title: collect '/.disk/info' from RPi preinstalled systems Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: Apport should collect the image build information from a system on which it is being ran. Test Case - 1) On a Raspberry Pi run 'ubuntu-bug linux-raspi'. 2) Choose 'View report' 3) Observe that 'ImageMediaBuild' is not collected With the version of apport from -proposed 'ImageMediaBuild' will be in the report and will have the same contents as '/.disk/info'. Regression Potential Apport's hooktutils.py is fault tolerant and will not crash if the system does not have a '/.disk/info' file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1876945/+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 1871185] Update Released
The verification of the Stable Release Update for apport has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1871185 Title: urls in ubuntu-bug's dialog not really clickable Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Fix Released Bug description: when ubuntu-bug report suggests filing a bug report directly in launchpad for snap packages, the displayed url is clickable but the url stops at the first + symbol. see attachment. Test Case - 1) On an Ubuntu 20.04 LTS system run 'ubuntu-bug chromium' 2) Observe a "the problem cannot be reported" message with a link that is not fully highlighted With the version of apport from -proposed the link will be fully highlighted and will be clickable. Regression Potential The re for what constitutes a url is just improved and the snap dialog is the only one I can find with a url in it. Given that url highlighting is "broken" there isn't any potential for regression. Original Description ProblemType: BugDistroRelease: Ubuntu 19.10 Package: apport 2.20.11-0ubuntu8.8 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashReports: 640:1000:124:8919925:2020-03-29 20:16:13.456640958 +0200:2020-03-29 20:16:14.456640958 +0200:/var/crash/_usr_bin_python3.7.1000.crash CurrentDesktop: XFCE Date: Mon Apr 6 19:50:16 2020 InstallationDate: Installed on 2020-03-18 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1871185/+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 1329206] Re: package libxatracker2 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libxatracker.so.2.1.0 », qui appartient aus
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1329206 Title: package libxatracker2 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux- gnu/libxatracker.so.2.1.0 », qui appartient aussi au paquet libxatracker1:amd64 10.1~git1402021930.81144c+curaga~gd~s Status in mesa package in Ubuntu: Invalid Bug description: This bug ocured when i log in to ubuntu. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libxatracker2 (not installed) ProcVersionSignature: Ubuntu 3.11.0-23.40-generic 3.11.10.10 Uname: Linux 3.11.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 11 17:14:39 2014 DistUpgraded: 2014-06-11 15:00:16,559 DEBUG disabling apt cron job (0755) DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: package:libxatracker2:(not installed):tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libxatracker.so.2.1.0 », qui appartient aussi au paquet libxatracker1:amd64 10.1~git1402021930.81144c+curaga~gd~s ErrorMessage: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libxatracker.so.2.1.0 », qui appartient aussi au paquet libxatracker1:amd64 10.1~git1402021930.81144c+curaga~gd~s GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0400] Subsystem: Dell Device [1028:0400] InstallationDate: Installed on 2012-04-27 (775 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MachineType: Dell Inc. OptiPlex 380 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-23-generic root=UUID=6bfba058-7d32-4780-a790-5f3afba6ad60 ro quiet splash vt.handoff=7 SourcePackage: mesa Title: package libxatracker2 (not installed) failed to install/upgrade: tentative de remplacement de « /usr/lib/x86_64-linux-gnu/libxatracker.so.2.1.0 », qui appartient aussi au paquet libxatracker1:amd64 10.1~git1402021930.81144c+curaga~gd~s UpgradeStatus: Upgraded to saucy on 2014-06-11 (0 days ago) dmi.bios.date: 02/24/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HN7XN dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/24/2011:svnDellInc.:pnOptiPlex380:pvr:rvnDellInc.:rn0HN7XN:rvrA01:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 380 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54+git1405200630.8fc62c~gd~s version.libgl1-mesa-dri: libgl1-mesa-dri 10.3~git1406110730.0d8944~gd~s version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3~git1406110730.0d8944~gd~s 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 N/A 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: Thu Jun 12 08:40:08 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell QuietKey Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 inputDell WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 53302 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1329206/+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 1416629] Re: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1416629 Title: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in mesa package in Ubuntu: Invalid Bug description: Other than dual-booting into Ubuntu from Windows 7 today, this error really hasn't ever popped up before. I think it could either be a burp in the system, or maybe my Video Card threw an exception. I really don't have very much to go on here, as it's never happened before, and I've been using Ubuntu on this computer now for over 6 months (dual-boot) without any issues. Running $ ubuntu-bug mesa tells me that the package isn't even installed. Might have been uninstalled with a recent apt-get purge or something. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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 Jan 25 16:00:11 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-glx:amd64:10.1.3-0ubuntu0.3:subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] [1002:6719] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b00] InstallationDate: Installed on 2014-07-22 (193 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 001 Device 002: ID 03f0:8d07 Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 046d:c051 Logitech, Inc. G3 (MX518) Optical Mouse Bus 002 Device 002: ID 041e:3225 Creative Technology, Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=75e77f58-c41e-41f7-a0cd-905c3ac03616 ro quiet splash vt.handoff=7 SourcePackage: mesa Title: package libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2010 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 1204 dmi.board.name: P5N-D dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision1204:bd01/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 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: Sat Jan 31 03:00:10 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1416629/+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 1037411] Re: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/1037411 Title: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7 Status in Compiz: Fix Released Status in Mesa: Won't Fix Status in compiz package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Invalid Status in compiz source package in Precise: Invalid Status in mesa source package in Precise: Invalid Status in compiz source package in Quantal: Fix Released Status in mesa source package in Quantal: Won't Fix Bug description: (This is no longer the primary performance regression bug for compiz 0.9.8.0. Look at bug 1024304 instead) TEST CASE: 1. CCSM > OpenGL > framebuffer_object = OFF vertex_buffer_object = OFF always_swap_buffers = OFF 2. Run graphics benchmarks. Expected: Similar results to compiz 0.9.7 Observed: Much lower results than compiz 0.9.7 ORIGINAL DESCRIPTION: Comparing graphics performance in a two-monitor configuration, I find the gles2 branch is 25-40% slower than trunk. This would not normally be surprising, however the slowdown REMAINS even when I turn off the new rendering features in the gles2 branch: framebuffer_object, vertex_buffer_object, always_swap_buffers So both branches should be using the same code path. But gles2 is still dramatically slower than trunk using two monitors. The good news is that this bug only affects benchmark results and seemingly a little lag. The physical frame rate achieved with two monitors still seems to be higher using the gles2 branch, meaning it drops from 60Hz to 30Hz much less often than trunk does. NOTE 1: This regression was allowed in compiz 0.9.8.0 because it is generally only visible in benchmark results. Meanwhile, physical compiz rendering performance (as reported by the compiz Benchmark plugin) is higher in compiz 0.9.8.0 than previous versions, in most cases. NOTE 2: If you're just worried about fullscreen game performance, then you don't need to wait for this bug to be resolved. You can get optimal graphics performance with unredirect mode. But see bug 980663 first. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037411/+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 1366556] Re: PPC: libgl1-mesa-dri doesn't provide 3D acceleration
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/1366556 Title: PPC: libgl1-mesa-dri doesn't provide 3D acceleration Status in mesa package in Ubuntu: Won't Fix Bug description: Hi, libgl1-mesa-dri doesn't provide 3D acceleration. Package: libgl1-mesa-dri 10.2.6-1ubuntu3 (Lubuntu 14.10 beta PowerPC) System specification: http://www.xenosoft.de/pastebin_AmigaOne_X1000 Tested graphics cards: AMD CYPRESS, and AMD BARTS Preliminary solution: http://forum.hyperion- entertainment.biz/viewtopic.php?f=35=2614 LIBGL_DEBUG=verbose glxinfo name of display: :0 libGL: screen 0 does not appear to be DRI3 capable libGL: pci id for fd 4: 1002:6738, driver r600 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/r600_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/r600_dri.so libGL: driver does not expose __driDriverGetExtensions_r600(): /usr/lib/powerpc-linux-gnu/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600 libGL: Can't open configuration file /home/christian/.drirc: No such file or directory. libGL: Can't open configuration file /home/christian/.drirc: No such file or directory. libGL error: failed to load driver: r600 libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/tls/swrast_dri.so libGL: OpenDriver: trying /usr/lib/powerpc-linux-gnu/dri/swrast_dri.so libGL: Can't open configuration file /home/christian/.drirc: No such file or directory. libGL error: failed to load driver: swrast Error: couldn't find RGB GLX visual or fbconfig dmesg | grep radeon [0.620345] [drm] radeon kernel modesetting enabled. [0.789281] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [0.789296] radeon :01:00.0: GTT: 1024M 0x4000 - 0x7FFF [0.789440] [drm] radeon: 1024M of VRAM memory ready [0.789448] [drm] radeon: 1024M of GTT memory ready. [0.820700] radeon :01:00.0: WB enabled [0.820712] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0xc00276ab2c00 [0.820728] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc00276ab2c0c [0.834239] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xd800901b2118 [0.834318] radeon :01:00.0: radeon: using MSI. [0.834362] [drm] radeon: irq initialized. [1.191354] [drm] radeon: power management initialized [1.561110] radeon :01:00.0: fb0: radeondrmfb frame buffer device [1.561516] radeon :01:00.0: registered panic notifier [1.561844] [drm] Initialized radeon 2.36.0 20080528 for :01:00.0 on minor 0 dmesg | grep drm [0.620278] [drm] Initialized drm 1.1.0 20060810 [0.620345] [drm] radeon kernel modesetting enabled. [0.620786] [drm] initializing kernel modesetting (BARTS 0x1002:0x6738 0x1682:0x3107). [0.620806] [drm] register mmio base: 0xA002 [0.620812] [drm] register mmio size: 131072 [0.789305] [drm] Detected VRAM RAM=1024M, BAR=256M [0.789312] [drm] RAM width 256bits DDR [0.789440] [drm] radeon: 1024M of VRAM memory ready [0.789448] [drm] radeon: 1024M of GTT memory ready. [0.789472] [drm] Loading BARTS Microcode [0.789566] [drm] GART: num cpu pages 262144, num gpu pages 262144 [0.820556] [drm] PCIE GART of 1024M enabled (table at 0x00273000). [0.834254] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [0.834261] [drm] Driver supports precise vblank timestamp query. [0.834362] [drm] radeon: irq initialized. [0.851016] [drm] ring test on 0 succeeded in 3 usecs [0.851092] [drm] ring test on 3 succeeded in 2 usecs [1.036506] [drm] ring test on 5 succeeded in 2 usecs [1.036518] [drm] UVD initialized successfully. [1.036876] [drm] Enabling audio 0 support [1.036938] [drm] ib test on ring 0 succeeded in 0 usecs [1.036995] [drm] ib test on ring 3 succeeded in 0 usecs [1.187983] [drm] ib test on ring 5 succeeded [1.190274] [drm] Radeon Display Connectors [1.190283] [drm] Connector 0: [1.190289] [drm] DP-1 [1.190293] [drm] HPD4 [1.190300] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [1.190307] [drm] Encoders: [1.190312] [drm] DFP1: INTERNAL_UNIPHY2 [1.190318] [drm] Connector 1: [1.190323] [drm] DP-2 [1.190327] [drm] HPD5 [1.190333] [drm] DDC: 0x6440
[Touch-packages] [Bug 1393238] Re: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1393238 Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux- gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so .dpkg-new': fin de fichero o de flujo inesperado Status in mesa package in Ubuntu: Invalid Bug description: i don't know (automatic generated report) ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/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.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 15 15:39:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:10.1.3-0ubuntu0.2:no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado ErrorMessage: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3629] InstallationDate: Installed on 2014-09-29 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. M85M-US2H ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=950b265a-1846-43c2-89b8-a3d488cefc08 ro quiet splash SourcePackage: mesa Title: package libgl1-mesa-dri 10.1.3-0ubuntu0.2 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so' a '/usr/lib/x86_64-linux-gnu/dri/vmwgfx_dri.so.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: M85M-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd09/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnM85M-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM85M-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: M85M-US2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 16 20:32:48 2014 xserver.configfile: /etc/X11/xorg.conf 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/mesa/+bug/1393238/+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 1784240] Re: Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update
is it still an issue on 20.04? ** No longer affects: mesa (Ubuntu) ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1784240 Title: Driver doesn't correctly probe Samsung U28D590D 28-inch 4k after recent update Status in linux package in Ubuntu: Incomplete Bug description: This monitor was correctly detected and worked properly at maximum resolution for the last 2 years, but X no longer correctly identifies the monitor and now only proposes a maximum display resolution of 1368x768 since a recent update. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 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: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jul 29 11:10:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:67ef] (rev cf) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:9460] InstallationDate: Installed on 2016-05-20 (800 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/Whiteygu-lvm--root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 29 09:18:04 2018 xserver.configfile: default xserver.errors: AMDGPU(0): Failed to open amdgpu hybrid version xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784240/+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 1881094] [NEW] Support kernel 5.4 Intel sound driver
Public bug reported: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1881094/+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 32042] Re: OpenGL subroutine man pages missing
provided by opengl-4-man-doc ** Changed in: mesa (Ubuntu) Status: Triaged => Invalid ** No longer affects: mesa (Debian) -- 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/32042 Title: OpenGL subroutine man pages missing Status in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: As a convenience issue it seems that the man pages for programming openGL aren't installed with any of the development or documentation packages for X or mesa. From various sites I have gathered that these generally come with the development files for X.org but Im not sure... I have installed the KDE development metapackage and I get the kdevelop doc .toc file for opengl but it is useless without the man pages installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/32042/+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 534719] Re: [unichrome] netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed.
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/534719 Title: [unichrome] netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Status in Mesa: Unknown Status in mesa package in Ubuntu: Invalid Status in netbook-launcher package in Ubuntu: Invalid Status in mesa package in Debian: Fix Released Bug description: Binary package hint: netbook-launcher Started Lucid Alpha3 Netbook Edition (i386) on a VIA Epia system, booted from USB stick. It booted and can be used basically, but the whole "desktop" area does not react to clicks, and after a few minutes running it the Apport symbol came up for this crash. No idea what really caused this or what the netbook-launcher does. Currently, the "desktop" can be displayed but still does not react to clicks. ProblemType: Crash Architecture: i386 AssertionMessage: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Date: Mon Mar 8 22:33:57 2010 DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] No such file or directory ExecutablePath: /usr/bin/netbook-launcher GConfNonDefault: /apps/netbook-launcher/disable_single_instance=false /apps/netbook-launcher/force_low_graphics=false LiveMediaBuild: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100224.3) MachineType: VIA Technologies, Inc. VT8623-8235 Package: netbook-launcher 1:2.1.13-0ubuntu1 ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname-netbook.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de ProcCmdline: netbook-launcher --show-favorites ProcEnviron: LANG=de_DE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-generic RelatedPackageVersions: xserver-xorg 1:7.5+1ubuntu8 libgl1-mesa-glx 7.7-3ubuntu1 libdrm2 2.4.18-1ubuntu2 xserver-xorg-video-intel 2:2.9.1-1ubuntu6 Signal: 6 SourcePackage: netbook-launcher StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 __assert_fail () from /lib/tls/i686/cmov/libc.so.6 viaSwapOutWork () from /usr/lib/dri/unichrome_dri.so Title: netbook-launcher assert failure: netbook-launcher: via_tex.c:427: viaSwapOutWork: Assertion `sz == vmesa->total_alloc[heap]' failed. Uname: Linux 2.6.32-14-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 05/19/2004 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: 6.00 PG dmi.board.name: EPIA-M dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvr6.00PG:bd05/19/2004:svnVIATechnologies,Inc.:pnVT8623-8235:pvr:rvn:rnEPIA-M:rvr:cvn:ct3:cvr: dmi.product.name: VT8623-8235 dmi.sys.vendor: VIA Technologies, Inc. glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu architecture: i686kernel: 2.6.32-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/534719/+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 1173787] Re: Delay selection in blender - ubuntu 13.04 - ati 4250
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/1173787 Title: Delay selection in blender - ubuntu 13.04 - ati 4250 Status in Mesa: Won't Fix Status in blender package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: Delay selection in blender - ubuntu 13.04 - ati 4250 When you select an object in Blender 2.66a, selection is slow. As if delay. No matter the complexity of the object, it is slow when selecting objects. (Blender installed from the ubuntu software center) My pc is an Acer Aspire 5552-6829 with integrated ATI HD4250 video with "Gallium 0.4 on AMD RS880" driver. This "error" occurs after installing Ubuntu 13.04 with Unity, but also occurs in Ubuntu GNOME 13.04. (all 64 bit) ... Previously not happen with Ubuntu 12.04 (kernel 3.2 / 5). Since there is an apparent problem or tangible and also am a newbie with this from the bugs, I would like to know what I have to analyze with "ubuntu-bug" I'm not sure it's the composer of windows or X.org. * Summary details: Ubuntu 13.04 64bit Blender 2.66a Ati HD4250 Gallium 0.4 on AMD RS880 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1173787/+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 763461] Re: [natty intel 945gme kde] Xorg crashes when exiting fullscreen with KDE set to suspend effects for fullscreen windows
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/763461 Title: [natty intel 945gme kde] Xorg crashes when exiting fullscreen with KDE set to suspend effects for fullscreen windows Status in mesa package in Ubuntu: Invalid Bug description: Kubuntu natty, packages up-to-date as of 2011-04-17. No ppas added, so mesa packages are version 7.10.2-0ubuntu1, xorg-server packages are version 1.10.0.902-1ubuntu1, -video-intel is version 2.14.0-4ubuntu7 and KDE packages are version 4.6.2-0ubuntu1. Please reassign bug if the bug is not in mesa. When exiting a fullscreen window (eg Flash, fullscreen games) with KDE's desktop effects set to suspend effects when any such are fullscreened, Xorg crashes. Reproducible everytime and stops happening if that option is disabled in the Advanced tab of the Desktop Effects kcm module, perhaps to the detriment of performance. Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80a531b] 1: /usr/bin/X (0x8048000+0x60808) [0x80a8808] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xbbf40c] 3: /usr/lib/dri/i915_dri.so (intelClearWithBlit+0x162) [0x41b742] 4: /usr/lib/dri/i915_dri.so (0x3fc000+0x18670) [0x414670] 5: /usr/lib/dri/libdricore.so (_mesa_Clear+0x172) [0x1015512] 6: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x7fd9) [0x364fd9] 7: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x351b0) [0x3921b0] 8: /usr/lib/xorg/modules/extensions/libglx.so (0x35d000+0x3813f) [0x39513f] 9: /usr/bin/X (0x8048000+0x282c7) [0x80702c7] 10: /usr/bin/X (0x8048000+0x1a81c) [0x806281c] 11: /lib/i386-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x1b8e37] 12: /usr/bin/X (0x8048000+0x1a411) [0x8062411] Segmentation fault at address 0x30 Even with -dbg packages installed I could not get a better backtrace. How to reproduce: 1. Enable KDE's desktop effects if not already enabled 2. Go to System Settings -> Desktop Effects, Advanced tab and check Suspend desktop effects for fullscreen windows 3. Open a browser (Chromium in this case) 4. Navigate to a youtube clip 5. Play and hit fullscreen 6. Exit fullscreen 7. Observe complete Xorg crash As Xorg crashes you're returned to the kdm login screen - however a "broken" kded remains in memory, which prevents new wireless connections being established. It won't exit by itself, it won't exit when sent SIGTERM, has to be sent SIGKILL. That is perhaps a different bug, but worthy of mention to emphasize bug importance. The user has to reboot to be able to use Xorg again with a wireless connection, alternatively switch to a tty and kill the kded process before logging in again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/763461/+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 1876320] Re: Port parameter sshd_config is 22 AND whatever you specify
The upstream bug now has a patch attached, so I'm tagging this server- next. ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1876320 Title: Port parameter sshd_config is 22 AND whatever you specify Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Status in openssh source package in Focal: Triaged Bug description: On my Ubuntu Server 20.04 LTS with OpenSSH 1:8.2p1-4, I have TWO sshd deamons. One (on port 22) is for internal use, accepts passwords etc. The second (on port 7722) does not allow PAM use and no passwords, allows only one user(name) and uses an alternative autorized_keys file (that only root can edit). Any parameter FIRST encountered in sshd_config is the one that is accepted; others do not override (like in many other config files). There is one exception: 'Port', which is accumulative. To make life easier, I set the more restrictive parameters for port 7722 first and next include the system-default /etc/ssh/sshd_config. The /etc/ssh/sshd_config file(s) in Ubuntu Server 20.04 DO NOT specify 'Port' anywhere - the default is 22. But: it is obviously still accumulative: Setting 'Port' to 7722 makes sshd listen on port 7722 AND 22. This is unwanted. Proposed solution: Remove the accumulative behavior for 'Port' and REQUIRE the 'Port' parameter like before (and maybe have second and later parameters override the earlier ones, like 'everyone else'). Regards, Adriaan PS Searching for solutions, I found that specifying 'ListenAddress 0.0.0.0:7722' stops sshd from listening to port 22. This, however, is not documented in 'man 5 sshd_config' and may be an unreliable side- effect. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1876320/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I had already applied the temporary fix as per comment #39 but I upgraded to version 0.96.24.32.13 in -proposed anyway. Attempting to check/uncheck any of the options on the 'Other Software' tab displayed a prompt to enter the 'admin' password. So I can also verify the issue will be fixed with this update. -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact Changes on the 'Other Software tab' sometime fail to ask for credential and fail to apply as a consequence * Test Case - start software-properties-gtk - got to the 'Other Software Tab' - try to change the value of a checkbox The change should prompt for a password and be active * Regression potential the change is a small sleep workaround to avoid trying to get the focus while GTK still has it, outside of a tiny delay in the active it should have no consequence --- On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+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 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+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 1180646] Re: cairo-dock rendering issues using openGL backend on intel GPU
** Changed in: mesa (Ubuntu) Status: Triaged => Fix Released -- 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/1180646 Title: cairo-dock rendering issues using openGL backend on intel GPU Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Bug description: what is this bug ? when i had ubuntu 11.10 , i had a big slow motion that affect even the youtube videos and overall performance . and the error was the opengl, i know that because its version name was missing on 11.10 , any way after upgrade to 12.04 i though the error gone, and it does , my laptop was 10x faster . but i can't run cairo-dock in opengl mode !!!. the ghost came back :( old ubuntu 11.10 bug http://imageshack.us/photo/my-images/259/xorg.png/ new ubuntu 12.04 bug (the one i have right now ) http://imageshack.us/photo/my-images/844/screenshotfrom201305160.png/ my additional drivers pic here before upgrade from ubuntu 11.10 to 12.04 http://img94.imageshack.us/img94/8410/delldrivers.png after the upgrade http://imageshack.us/photo/my-images/39/screenshotfrom201305160.png/ - i have posted on the cairo-dock forums and they responded that this a common eror on hd 4000 and they sent me that link https://bugs.freedesktop.org/show_bug.cgi?id=55036 i looked at it and i found """Component:Drivers/DRI/i965""" i have read some on the report uploaded and i feel like i have mix between i915 and i965 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-43.68-generic 3.2.42 Uname: Linux 3.2.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None Date: Thu May 16 05:17:18 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-oneiric-amd64-2016-1 DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0569] InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 2016-18:24 MachineType: Dell Inc. Inspiron 5520 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-43-generic root=UUID=8b64b4b3-8de9-43d7-b1c8-7f9ff701ac70 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to precise on 2013-05-05 (10 days ago) dmi.bios.date: 08/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 04G65K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/13/2012:svnDellInc.:pnInspiron5520:pvrA09:rvnDellInc.:rn04G65K:rvrA02:cvnDellInc.:ct8:cvrA09: dmi.product.name: Inspiron 5520 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1~precise version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0.1-0ubuntu1~precise version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1~precise version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.0-0ubuntu0~precise1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1180646/+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 1307709] Re: webbrowser-app does not start in Unity 8 preview session
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/1307709 Title: webbrowser-app does not start in Unity 8 preview session Status in Oxide: Fix Released Status in mesa package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: The webbrowser app does not start when invoked from the Dash in Unity8 in the preview session. Upon clicking the icon the screen quickly flickers and returns to the Dash. You can get some more information when running the terminal app. You can make this app usable by uncommenting X-Ubuntu-StageHint=SideStage. From the terminal, run: webbrowser-app --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop This takes me back to the Dash, return to the terminal to find: libEGL warning: unsupported platform (null) libEGL warning: unsupported platform (null) Segmentation fault (core dumped) I am attaching one of the crash dumps To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1307709/+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 1060986] Re: kwin_opengl_test crashed with SIGSEGV in r600_bind_blend_state_internal()
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1060986 Title: kwin_opengl_test crashed with SIGSEGV in r600_bind_blend_state_internal() Status in mesa package in Ubuntu: Invalid Bug description: kwin_opengl_test crashed with SIGSEGV in r600_bind_ps_state() ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: kde-window-manager-common 4:4.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Wed Oct 3 16:01:36 2012 ExecutablePath: /usr/lib/kde4/libexec/kwin_opengl_test InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcCmdline: /usr/lib/kde4/libexec/kwin_opengl_test SegvAnalysis: Segfault happened at: 0xb6d2cce6 :mov (%eax),%eax PC (0xb6d2cce6) ok source "(%eax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: kde-workspace StacktraceTop: r600_bind_ps_state (ctx=0x9d78090, state=0x0) at r600_state_common.c:866 r600_create_context (screen=0x9d737c8, priv=0x0) at r600_pipe.c:312 st_api_create_context (stapi=0xb7146380 , smapi=0x9d734c8, attribs=0xbfccdc14, error=0xbfccdc10, shared_stctxi=0x0) at ../../../../src/mesa/state_tracker/st_manager.c:633 dri_create_context (api=API_OPENGL, visual=0x9d76280, cPriv=0x9d737a8, major_version=1, minor_version=0, flags=0, error=0xbfccdcdc, sharedContextPrivate=0x0) at dri_context.c:119 dri2CreateContextAttribs (screen=screen@entry=0x9d73410, api=api@entry=0, config=config@entry=0x9d76280, shared=shared@entry=0x0, num_attribs=num_attribs@entry=0, attribs=attribs@entry=0x0, error=error@entry=0xbfccdcdc, data=data@entry=0x9d77d60) at ../../../../src/mesa/drivers/dri/common/dri_util.c:287 Title: kwin_opengl_test crashed with SIGSEGV in r600_bind_ps_state() UpgradeStatus: Upgraded to quantal on 2012-09-12 (21 days ago) UserGroups: adm cdrom dip lpadmin netdev plugdev root sambashare sudo www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1060986/+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 1042211] Re: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works)
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/1042211 Title: [quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works) Status in Compiz: Invalid Status in Mesa: Invalid Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Bug description: WORKAROUND: Download and install the old Mesa 8.0.4 packages for quantal from: https://launchpad.net/ubuntu/+source/mesa/8.0.4-1ubuntu1 or add the Unity staging PPA: sudo add-apt-repository ppa:unity-team/staging ORIGINAL DESCRIPTION: After installing the latest updates on Quantal, desktop fails to repaint correctly: - moving a window leave trails - plain color is displayed instead of custom background - menus are flickering ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8+bzr3319-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2 Uname: Linux 3.5.0-12-generic i686 ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 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 Aug 27 10:38:41 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] Subsystem: ASUSTeK Computer Inc. Device [1043:83ac] InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209) MachineType: ASUSTeK Computer INC. 1015PE PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-12-generic root=UUID=014cdf46-1d84-4e78-a68e-5d6de3419ad9 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/31/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PE dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2 version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1042211/+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 1130175] Re: [8xx mesa] Unity can't start on laptop
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/1130175 Title: [8xx mesa] Unity can't start on laptop Status in Compiz: New Status in mesa package in Ubuntu: Won't Fix Bug description: Unity can't start on laptop on 13.04 and there are no windows borders on windows. If I boot into Gnome2 without compiz - everything is normal. Ubuntu 12.10 Unity is working normal. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Tue Feb 19 17:16:11 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0071] Subsystem: Acer Incorporated [ALI] Device [1025:0071] InstallationDate: Installed on 2013-02-19 (0 days ago) InstallationMedia: 13.04-x86 13.04 - Release i386 Lsusb: Bus 001 Device 002: ID 8564:1000 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer TravelMate 2350 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=4a347fe8-6dd7-4d1c-a8b7-59532b55ebaa ro noresume ipv6.disable=1 SourcePackage: xorg Symptom: display UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Serial number of failed request: 32 Current serial number in output stream: 33 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/03/2005 dmi.bios.vendor: Acer dmi.bios.version: V1.70 dmi.board.name: TravelMate 2350 dmi.board.vendor: Acer dmi.board.version: A0 dmi.chassis.asset.tag: modem dmi.chassis.type: 8 dmi.chassis.vendor: Acer dmi.chassis.version: A1 dmi.modalias: dmi:bvnAcer:bvrV1.70:bd01/03/2005:svnAcer:pnTravelMate2350:pvr290:rvnAcer:rnTravelMate2350:rvrA0:cvnAcer:ct8:cvrA1: dmi.product.name: TravelMate 2350 dmi.product.version: 290 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1 version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Tue Feb 19 16:59:39 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.2-0ubuntu2 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1130175/+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 1881094] Re: Support kernel 5.4 Intel sound driver
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
The problem is that the code that reads the state reads it into the
depcache.
--
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/1713219
Title:
'apt-mark showauto' and 'apt show' is slow
Status in apt package in Ubuntu:
Triaged
Bug description:
$ time apt-mark showauto >/dev/null
real 0m0.587s
user 0m0.552s
sys 0m0.016s
When I run the command first time, it is even much slower.
I could do the job in fraction of a time using awk in POSIX shell
script:
auto_file='/var/lib/apt/extended_states'
eval $(apt-config shell auto_file Dir::State::extended_states/f)
awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
}' "$auto_file" | CL_ALL=C sort -u
real 0m0.019s
user 0m0.008s
sys 0m0.000s
That prints architecture for every package and shows entries in
slightly different order, though. And the file could be out of date
showing packages that are not installed?!?
Similarly
apt show
is slow. (It also shows whether a package is manually or automatically
installed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.17
ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 26 12:59:00 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (1070 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apt: [modified]
modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
mtime.conffile..etc.kernel.postinst.d.apt.auto.removal:
2017-06-01T14:39:39.236080
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+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 574287] Re: tasksel: forcefully removes packages when tasks overlap
The easiest way out would be to just remove tasksel once the d-i images are gone, and it's no longer needed. -- 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/574287 Title: tasksel: forcefully removes packages when tasks overlap Status in apt package in Ubuntu: Invalid Status in tasksel package in Ubuntu: Confirmed Status in tasksel package in Debian: Fix Released Bug description: TEST CASE 1. Boot Lucid LiveCD 2. run "sudo tasksel" and select "virtual machine host" 3. run "sudo tasksel" and deselect "virtual machine host" 4. watch how tasksel uninstalls your system OBSERVATIONS What seems to happen is that apt vengefully removes ALL of the items associated with one task, including several base dependencies of other tasks (e.g. ubuntu-desktop) One illustrative example is the openssh-server task: This one includes the packages openssh-server, tcpd and libwrap0. From a normal ubuntu-desktop (e.g. ~liveCD) both tcpd and libwrap0 are already installed, and the task-install pulls in only openssh-server. However when the task is removed, all these three packages (openssh-server, tcpd and libwrap0) are forcefully removed. Since libwrap0 is a core dependency of gnome, a large part of gnome will be removed alongside the removal of the task. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/574287/+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 1881094] Re: Support kernel 5.4 Intel sound driver
** Description changed: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot + + * install updated linux-firmware and pulseaudio +$ sudo add-apt-repository ppa:kchsieh/training +$ sudo apt-get update +$ sudo apt install linux-firmware +$ sudo apt install pulseaudio +$ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1404696] Re: No vdpau for the utopic xstack in trusty
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/1404696 Title: No vdpau for the utopic xstack in trusty Status in mesa package in Ubuntu: Won't Fix Bug description: Hello, I have tested the utopic xstack in trusty in the Canonical X Staging ppa https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging?field.series_filter=trusty . It installs fine with; LC_ALL=C apt-get install -V libglapi-mesa-lts-utopic libgl1-mesa-glx- lts-utopic xserver-xorg-lts-utopic xserver-xorg-input-all-lts-utopic xserver-xorg-video-all-lts-utopic libgl1-mesa-dri-lts-utopic libglapi- mesa-lts-utopic:i386 libgl1-mesa-dri-lts-utopic:i386 libgl1-mesa-glx- lts-utopic:i386 libgles2-mesa-lts-utopic libglapi-mesa-lts-utopic mesa-vdpau-drivers-lts-utopic libegl1-mesa-drivers-lts-utopic libwayland-egl1-mesa-lts-utopic But under vdpauinfo there are no decoder capabilities for a AMD Radeon 5550 (r600); Decoder capabilities: name level macbs width height --- With stock xstack; Decoder capabilities: name level macbs width height --- MPEG1 0 9216 2048 1152 MPEG2_SIMPLE 3 9216 2048 1152 MPEG2_MAIN3 9216 2048 1152 H264_BASELINE41 9216 2048 1152 H264_MAIN41 9216 2048 1152 H264_HIGH41 9216 2048 1152 VC1_SIMPLE1 9216 2048 1152 VC1_MAIN 2 9216 2048 1152 VC1_ADVANCED 4 9216 2048 1152 The total output of vdpauinfo is attached. Best regards, Bernhard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1404696/+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 599125] Re: [mach64] unsupported Rage Mobility P/M AGP 2x
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/599125 Title: [mach64] unsupported Rage Mobility P/M AGP 2x Status in mesa package in Ubuntu: Invalid Bug description: Binary package hint: xserver-xorg-video-ati I tried to use a Microsoft Windows program through Wine. I got the below error messages: - err:winediag:X11DRV_WineGL_InitOpenglInfo The Mesa OpenGL driver is using software rendering, most likely your OpenGL drivers haven't been installed correctly fixme:d3d_caps:wined3d_guess_card No card selector available for GL vendor 4 and card vendor . fixme:win:EnumDisplayDevicesW ((null),0,0x32e250,0x), stub! fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x19e078,0x19e000): stub fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy fixme:bitblt:client_side_dib_copy potential optimization: client-side color-index mode DIB copy fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xdece40,0xc8df78): stub fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0xdece40,0xc8df78): stub - ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-ati 1:6.13.0-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 CurrentDmesg: Date: Sun Jun 27 21:56:43 2010 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type InstallationMedia: Xubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1) Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Sony Corporation PCG-FX301(FR) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=cc325b47-77d9-4b57-98af-0db1393969c6 ro quiet splash ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-ati dmi.bios.date: 07/04/2001 dmi.bios.vendor: Sony Corporation dmi.bios.version: R0104K5 dmi.board.name: QII-Project dmi.board.vendor: Sony Corporation dmi.board.version: 1A dmi.chassis.asset.tag: 962C8394A0505800 dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnSonyCorporation:bvrR0104K5:bd07/04/2001:svnSonyCorporation:pnPCG-FX301(FR):pvr01:rvnSonyCorporation:rnQII-Project:rvr1A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: PCG-FX301(FR) dmi.product.version: 01 dmi.sys.vendor: Sony Corporation glxinfo: Error: [Errno 2] Aucun fichier ou dossier de ce type system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/599125/+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 565658] Re: Desktop effects do not work because of software rendering
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/565658 Title: Desktop effects do not work because of software rendering Status in mesa package in Ubuntu: Invalid Bug description: Binary package hint: xorg When I am trying to run compiz manually, it complains about fatal error: software rendering. In Xorg.0.log I see (WW) RADEON(0): Direct rendering disabled But, strange enough, glxinfo says direct rendering: Yes Most probably Xorg.0.log is right, because the display is somewhat slow and desktop effects cannot be enabled. In 9.10 everything was fine. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-powerpc64-smp 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-powerpc64-smp ppc64 Architecture: powerpc Date: Sat Apr 17 23:51:33 2010 DkmsStatus: Error: [Errno 2] No such file or directory ProcCmdLine: root=/dev/sda3 ro ramdisk_size=8192 quiet splash ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: xserver-xorg 1:7.5+5ubuntu1 libgl1-mesa-glx 7.7.1-1ubuntu2 libdrm2 2.4.18-1ubuntu3 xserver-xorg-video-ati 1:6.13.0-1ubuntu5 xserver-xorg-video-nouveau N/A SourcePackage: xorg Symptom: display system: distro: Ubuntu codename: lucid architecture: ppc64 kernel: 2.6.32-21-powerpc64-smp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/565658/+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 905972] Re: cheese crashed with SIGSEGV in parseOptInfoAttr()
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/905972 Title: cheese crashed with SIGSEGV in parseOptInfoAttr() Status in mesa package in Ubuntu: Invalid Bug description: Additional information foor the Cheese crash report. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.2.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Dec 18 15:43:28 2011 ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: System Manufacturer System Name ProcCmdline: cheese RelatedPackageVersions: cheese3.2.0-0ubuntu2 cheese-common 3.2.0-0ubuntu2 SegvAnalysis: Segfault happened at: 0x723a126: mov0x19c(%eax),%eax PC (0x0723a126) ok source "0x19c(%eax)" (0x019c) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cheese StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so intelMakeCurrent () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1 Title: cheese crashed with SIGSEGV in intelMakeCurrent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 11/28/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS P4BGL-VM ACPI BIOS Revision 1006 Beta 002 dmi.board.name: P4BGL-VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSP4BGL-VMACPIBIOSRevision1006Beta002:bd11/28/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP4BGL-VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 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 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 04c8:0720 Konica Corp. Digital Color Camera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/905972/+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 696427] Re: Unity visual glitches and freeze (libgl1-dri-mesa-experimental)
** Changed in: mesa (Ubuntu) Status: Incomplete => Invalid -- 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/696427 Title: Unity visual glitches and freeze (libgl1-dri-mesa-experimental) Status in Mesa: New Status in Nouveau Xorg driver: New Status in Unity: Incomplete Status in mesa package in Ubuntu: Invalid Status in unity package in Ubuntu: Incomplete Bug description: Binary package hint: unity Using Nouveau drivers and libgl1-dri-mesa-experimental package on a Nvidia 250GTS I get visual artefacts in Unity and a total freeze of the system (I've to hard reset PC). Sorry for low quality images but print screen doesn't work! ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.2.8-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 Uname: Linux 2.6.37-11-generic i686 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins' Date: Sun Jan 2 10:19:28 2011 MachineType: System manufacturer System Product Name PciDisplay: 02:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) ProcEnviron: LANGUAGE=it_IT:it:en_GB:en LANG=it_IT.UTF-8 LC_MESSAGES=it_IT.utf8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-11-generic root=UUID=0a53d971-02eb-421b-8e6c-a3b9a0033ad2 ro vt.handoff=7 splash quiet ProcVersionSignature_: Ubuntu 2.6.37-11.25-generic 2.6.37-rc7 RelatedPackageVersions: xserver-xorg 1:7.5+6ubuntu6 libgl1-mesa-glx 7.9+repack-1ubuntu3 libdrm2 2.4.22-2ubuntu1 xserver-xorg-video-intel 2:2.13.901-2ubuntu2 xserver-xorg-video-ati 1:6.13.2-1ubuntu2 SourcePackage: unity XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 05/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1401 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N78 SE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1401:bd05/07/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N78SE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer glxinfo: Error: [Errno 2] No such file or directory system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-11-generic To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/696427/+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 573196] Re: Launch command "cairo-dock -O" : ubuntu's session crashes and restarts
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/573196 Title: Launch command "cairo-dock -O" : ubuntu's session crashes and restarts Status in mesa package in Ubuntu: Invalid Bug description: Architecture: i386 DistroRelease: Ubuntu 10.04 Package: 2.1.4-0beta1-20100426-0ubuntu1~ppa0~lucid ProblemType: Session crash ProcCmdline: cairo-dock -O Window Manager: Compiz Desktop Environment: Gnome Video Card: Ati M R X300 So, when I launch the command "cairo-dock -O" (-O for use indirect rendering), ubuntu's session crashes and restarts. On the contrary, "cairo-dock -c" works properly (the dock appears correctly with cairo backend) and "cairo-dock -o" too but with some graphical problems (openGL backend, other bug with ati driver). You can found different logs (/var/log/Xorg.0* , /var/log/Xorg.failsafe.log* and ~/.xsession-errors*) here --> http://dl.free.fr/pu0g0saQK Thanks ! --- Architecture: i386 CurrentDmesg: [ 39.502144] ppdev: user-space parallel port driver [ 40.816175] b44: eth0: Link is up at 100 Mbps, full duplex. [ 40.816179] b44: eth0: Flow control is off for TX and off for RX. [ 40.816456] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 51.504027] eth0: no IPv6 routers present DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type MachineType: Acer, inc. Aspire 1650 Package: mesa (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=UUID=310300e1-4cf9-4c18-aefa-7ed72b740cca ro quiet splash vga=771 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/31/05 dmi.bios.vendor: Acer dmi.bios.version: 3A33 dmi.board.name: Crane II dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A33:bd08/31/05:svnAcer,inc.:pnAspire1650:pvrNotApplicable:rvnAcer,Inc.:rnCraneII:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 1650 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic --- Architecture: i386 CurrentDmesg: [ 39.502144] ppdev: user-space parallel port driver [ 40.816175] b44: eth0: Link is up at 100 Mbps, full duplex. [ 40.816179] b44: eth0: Flow control is off for TX and off for RX. [ 40.816456] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 51.504027] eth0: no IPv6 routers present DistroRelease: Ubuntu 10.04 DkmsStatus: Error: [Errno 2] Aucun fichier ou dossier de ce type MachineType: Acer, inc. Aspire 1650 Package: mesa (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: root=UUID=310300e1-4cf9-4c18-aefa-7ed72b740cca ro quiet splash vga=771 ProcEnviron: LANGUAGE=fr_FR:fr:en_GB:en LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Tags: lucid lucid Uname: Linux 2.6.32-21-generic i686 UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/31/05 dmi.bios.vendor: Acer dmi.bios.version: 3A33 dmi.board.name: Crane II dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: , Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvr3A33:bd08/31/05:svnAcer,inc.:pnAspire1650:pvrNotApplicable:rvnAcer,Inc.:rnCraneII:rvrNotApplicable:cvn,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 1650 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/573196/+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 292010] Re: opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed.
** Changed in: mesa (Ubuntu) Status: Triaged => Won't Fix -- 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/292010 Title: opengl error with i830_vtbl.c:465: i830_emit_state: Assertion `0' failed. Status in mesa package in Ubuntu: Won't Fix Bug description: Binary package hint: libgl1-mesa-dri this happens with my own OpenGL program on 8.10. I have been porting the program from Windows and from a more capable graphics card to Ubuntu and not so powerful Intel graphics chip, so it is quite possible that my program still has bugs in it. Still this failure is not proper way for OpenGL to behave. I probably should go with this directly to Mesa people? Eero [lspci] 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface [8086:2570] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:12bc] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) Subsystem: Hewlett-Packard Company Device [103c:12bc] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/292010/+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 1681129] Re: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1681129 Title: debsums report /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0 mismatch Status in mesa package in Ubuntu: Invalid Bug description: Running debsums on my machine report that /usr/lib/x86_64-linux- gnu/old.libgbm.so.1.0.0 has changed. Sadly even running "apt-get install --reinstall libgbm1-lts-wily:amd64 libgbm1:amd64" does not fix the problem. (BTW, I cannot report this against the libgbm1 package, because Launchpad is saying that '"libgbm1" does not exist in Ubuntu.') ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgbm1 10.1.3-0ubuntu0.6 [modified: usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0] ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Apr 8 11:44:48 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: isgx, 0.10, 4.2.0-27-generic, x86_64: installed (WARNING! Diff between built and installed module!) isgx, 0.10, 4.2.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:06fd] InstallationDate: Installed on 2016-05-02 (340 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 13-7359 ProcEnviron: TERM=rxvt PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed root=UUID=bc09f41a-6b3d-47f9-b01d-9ac1dce625eb ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0110N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0110N8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Feb 23 08:37:58 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 34381 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1681129/+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 455954] Re: [K8M800] AntSpotlight screensaver causes system to lock up immediately
** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix -- 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/455954 Title: [K8M800] AntSpotlight screensaver causes system to lock up immediately Status in linux package in Ubuntu: Won't Fix Status in mesa package in Ubuntu: Won't Fix Status in xserver-xorg-video-openchrome package in Ubuntu: Fix Released Bug description: Note: this bug just reappeared in Xubuntu 11.10. I filed this as a new bug #871471. Binary package hint: xscreensaver Selecting AntSpotlight in either xscreensaver or Gnome Screensaver causes this system to freeze immediately. Ubuntu version and kernel version, etc. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=9.10 DISTRIB_CODENAME=karmic DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)" Linux cupid 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux model name: Mobile AMD Sempron(tm) Processor 2800+ At the moment, neither xscreensaver nor Gnome Screensaver is installed, but the package containing this screensaver (xscreensaver- gl) is still installed. (I am about to remove it). Since memory may be an issue, I'll enclose a copy of /proc/meminfo ProblemType: Bug Architecture: i386 Date: Mon Oct 19 18:07:43 2009 DistroRelease: Ubuntu 9.10 Package: xscreensaver-gl 5.08-0ubuntu5 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: xscreensaver Uname: Linux 2.6.31-14-generic i686 XsessionErrors: (gnome-settings-daemon:2256): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2332): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2313): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/455954/+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 1881100] [NEW] package linux-image-5.4.0-33-lowlatency 5.4.0-33.37 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: boot volume ran out of space. There was no warning prior to the fail. Nothing important crashed and apt-get autoremove resolved problem for now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-lowlatency 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34 Uname: Linux 5.4.0-31-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dlannom4213 F pulseaudio /dev/snd/controlC2: dlannom4213 F pulseaudio /dev/snd/controlC1: dlannom4213 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 28 06:16:10 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-05 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp7s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EX58-UD4P ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-lowlatency root=UUID=7a86a84c-dcf7-490d-810c-352b13d9c873 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-33-lowlatency 5.4.0-33.37 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) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: EX58-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd03/11/2010:svnGigabyteTechnologyCo.,Ltd.:pnEX58-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEX58-UD4P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EX58-UD4P dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** 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/1881100 Title: package linux-image-5.4.0-33-lowlatency 5.4.0-33.37 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: boot volume ran out of space. There was no warning prior to the fail. Nothing important crashed and apt-get autoremove resolved problem for now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-lowlatency 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34 Uname: Linux 5.4.0-31-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dlannom4213 F pulseaudio /dev/snd/controlC2: dlannom4213 F pulseaudio /dev/snd/controlC1: dlannom4213 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 28 06:16:10 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-05-05 (23 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp7s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EX58-UD4P ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-lowlatency root=UUID=7a86a84c-dcf7-490d-810c-352b13d9c873 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-33-lowlatency 5.4.0-33.37 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) dmi.bios.date: 03/11/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: EX58-UD4P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3
[Touch-packages] [Bug 1713219] Re: 'apt-mark showauto' and 'apt show' is slow
I'm not going to add a second independent reader to apt just so that
apt-mark runs a bit faster.
--
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/1713219
Title:
'apt-mark showauto' and 'apt show' is slow
Status in apt package in Ubuntu:
Triaged
Bug description:
$ time apt-mark showauto >/dev/null
real 0m0.587s
user 0m0.552s
sys 0m0.016s
When I run the command first time, it is even much slower.
I could do the job in fraction of a time using awk in POSIX shell
script:
auto_file='/var/lib/apt/extended_states'
eval $(apt-config shell auto_file Dir::State::extended_states/f)
awk '/^Package:/ {
pkg=$2
getline; arch=$2
getline
if($2==1) print pkg ":" arch
}' "$auto_file" | CL_ALL=C sort -u
real 0m0.019s
user 0m0.008s
sys 0m0.000s
That prints architecture for every package and shows entries in
slightly different order, though. And the file could be out of date
showing packages that are not installed?!?
Similarly
apt show
is slow. (It also shows whether a package is manually or automatically
installed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apt 1.0.1ubuntu2.17
ProcVersionSignature: Ubuntu 4.4.0-92.115~14.04.1-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Aug 26 12:59:00 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-09-21 (1070 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.1)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.cron.daily.apt: [modified]
modified.conffile..etc.kernel.postinst.d.apt.auto.removal: [modified]
mtime.conffile..etc.cron.daily.apt: 2017-05-03T10:27:27.617839
mtime.conffile..etc.kernel.postinst.d.apt.auto.removal:
2017-06-01T14:39:39.236080
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1713219/+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 1057309] Re: gnome-control-center crashed with SIGSEGV in intelDestroyContext()
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1057309 Title: gnome-control-center crashed with SIGSEGV in intelDestroyContext() Status in mesa package in Ubuntu: Invalid Bug description: gnome-control-center crashed when i upgrade ubuntu from 12.04 into 12.10 beta ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu15 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 CrashCounter: 1 Date: Thu Sep 27 14:33:24 2012 Disassembly: => 0x37838dff: Cannot access memory at address 0x37838dff ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_US:en LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x37838dff:Cannot access memory at address 0x37838dff PC (0x37838dff) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () intelDestroyContext () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/i915_dri.so Title: gnome-control-center crashed with SIGSEGV in intelDestroyContext() UpgradeStatus: Upgraded to quantal on 2012-09-25 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XsessionErrors: gnome-session[1326]: WARNING: Session 'gnome' runnable check failed: Child process exited with code 1 (gnome-settings-daemon:1441): color-plugin-WARNING **: failed to get edid: unable to get EDID for output (gnome-panel:1603): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed (gnome-settings-daemon:1441): color-plugin-WARNING **: unable to get EDID for xrandr-VGA1: unable to get EDID for output (gnome-panel:1603): Gtk-CRITICAL **: gtk_accelerator_parse_with_keycode: assertion `accelerator != NULL' failed usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.17-0ubuntu1 indicator-datetime 12.10.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1057309/+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 1054624] Re: compiz crashed with SIGILL in llvm_pipeline_generic() from llvm_middle_end_linear_run() from vsplit_segment_simple_linear() from vsplit_run_linear() from draw_pt_arr
** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1054624 Title: compiz crashed with SIGILL in llvm_pipeline_generic() from llvm_middle_end_linear_run() from vsplit_segment_simple_linear() from vsplit_run_linear() from draw_pt_arrays() from draw_vbo() Status in mesa package in Ubuntu: Invalid Bug description: Running from virtualbox - immediately after login ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: compiz-core 1:0.9.8.2+bzr3377-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 37.342717] init: plymouth-stop pre-start process (1230) terminated with status 1 Date: Sat Sep 22 11:16:18 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20120922) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: Compiz ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-15-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 Signal: 4 SourcePackage: compiz StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so Title: compiz crashed with SIGILL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8.2+bzr3377-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120917.7cfd42ce-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120917.7cfd42ce-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.8-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1054624/+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 1881094] Re: Support kernel 5.4 Intel sound driver
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from S3 5. 1, 2, 3 works fine after resume from S2idle [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1881094] Re: Support kernel 5.4 Intel sound driver
** Changed in: pulseaudio (Ubuntu) Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned) ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Description changed: [Impact] - * Some Intel platform bionic user audio function will be broken after + * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 - * pulseaudio can't find working profile, since card name is changed in + * pulseaudio can't find working profile, since card name is changed in kernel 5.4 - [Test Case] - * install kernel 5.4 and check audio function -$ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 -$ sudo apt-get update -$ sudo apt install linux-header-5.4.0-31-generic -$ sudo apt install linux-image-generic-hwe-18.04-wip -$ sudo reboot + * install kernel 5.4 and check audio function + $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 + $ sudo apt-get update + $ sudo apt install linux-header-5.4.0-31-generic + $ sudo apt install linux-image-generic-hwe-18.04-wip + $ sudo reboot - * test items -1. check internal speaker/mic to playback and record audio -2. plug headset and check headset functions -3. plug HDMI from external monitor/TV, and check audio functions -4. 1, 2, 3 works fine after resume from S3 -5. 1, 2, 3 works fine after resume from S2idle + * test items + 1. check internal speaker/mic to playback and record audio + 2. plug headset and check headset functions + 3. plug HDMI from external monitor/TV, and check audio functions + 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] - * The updated pulseaudio breaks audio function on old kernel + * The updated pulseaudio breaks audio function on old kernel [Scope] - * Need for bionic only + * Need for bionic only [Bug Discussion] - - * https://bugs.launchpad.net/timbuktu/+bug/1880632 - * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 + + * https://bugs.launchpad.net/timbuktu/+bug/1880632 + * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881094 Title: Support kernel 5.4 Intel sound driver Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: New Bug description: [Impact] * Some Intel platform bionic user audio function will be broken after upgrade to kernel 5.4 * pulseaudio can't find working profile, since card name is changed in kernel 5.4 [Test Case] * install kernel 5.4 and check audio function $ sudo add-apt-repository ppa:arighi/bionic-hwe-edge-5.4 $ sudo apt-get update $ sudo apt install linux-header-5.4.0-31-generic $ sudo apt install linux-image-generic-hwe-18.04-wip $ sudo reboot * install updated linux-firmware and pulseaudio $ sudo add-apt-repository ppa:kchsieh/training $ sudo apt-get update $ sudo apt install linux-firmware $ sudo apt install pulseaudio $ sudo reboot * test items 1. check internal speaker/mic to playback and record audio 2. plug headset and check headset functions 3. plug HDMI from external monitor/TV, and check audio functions 4. 1, 2, 3 works fine after resume from suspend [Regression Potential] * The updated pulseaudio breaks audio function on old kernel [Scope] * Need for bionic only [Bug Discussion] * https://bugs.launchpad.net/timbuktu/+bug/1880632 * MP: https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1881122] [NEW] [Ubuntu Audio Settings] Audio device switching not working correctly
Public bug reported: In Ubuntu 18.04 switching between audio devices worked flawlessly. After upgrading to 20.04 not so much: When I try to switch between Logitech G930 and Soundblaster X-FI Audio devices, either the system sounds and/or programs which are already started do not playback any sounds. In some cases, system sounds (incl. the sound test) do not play, but programs do. It is really weird and I have a hard time reproducing the issue as well as the solution. Sometimes I play around with alsamixer and switch between the selected sound devices there and afterwards switch the device in the settings panel. It then more often than not works again as intended. If you have any suggestions on how to run down further details for this bug to enable you to bugfix this, tell me and I will try to provide further info. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 14:36:05 2020 InstallationDate: Installed on 2020-02-13 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - Logitech G930 Headset, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881122 Title: [Ubuntu Audio Settings] Audio device switching not working correctly Status in alsa-driver package in Ubuntu: New Bug description: In Ubuntu 18.04 switching between audio devices worked flawlessly. After upgrading to 20.04 not so much: When I try to switch between Logitech G930 and Soundblaster X-FI Audio devices, either the system sounds and/or programs which are already started do not playback any sounds. In some cases, system sounds (incl. the sound test) do not play, but programs do. It is really weird and I have a hard time reproducing the issue as well as the solution. Sometimes I play around with alsamixer and switch between the selected sound devices there and afterwards switch the device in the settings panel. It then more often than not works again as intended. If you have any suggestions on how to run down further details for this bug to enable you to bugfix this, tell me and I will try to provide further info. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 14:36:05 2020 InstallationDate: Installed on 2020-02-13 (105 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [USB-Audio - Logitech G930 Headset, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock
[Touch-packages] [Bug 1748667] Re: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar
me neither ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1748667 Title: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar Status in mesa package in Ubuntu: Invalid Bug description: nothing i know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Feb 7 06:24:32 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ErrorMessage: problemas de dependencias - se deja sin configurar GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7600G] [1002:9908] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Trinity [Radeon HD 7600G] [1025:0756] InstallationDate: Installed on 2018-02-02 (8 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Acer Aspire V5-551 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mesa Title: package libgl1-mesa-glx:i386 17.2.4-0ubuntu1~16.04.4 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Havok dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd09/06/2012:svnAcer:pnAspireV5-551:pvrV2.06:rvnAcer:rnHavok:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Aspire V5-551 dmi.product.version: V2.06 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Feb 10 16:25:08 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1748667/+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 1881142] [NEW] Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcsc-cyberjack (Ubuntu) Importance: Undecided Status: New ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28
[Touch-packages] [Bug 1860366] Re: Unable to install group of packages with `sudo apt install language-pack-*` (star or asterisk at the end of package names)
** Also affects: apt Importance: Undecided Status: New -- 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/1860366 Title: Unable to install group of packages with `sudo apt install language- pack-*` (star or asterisk at the end of package names) Status in APT: New Status in apt package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Try to execute the installation of packages with similar names, i.e. sudo apt install language-pack-* Expected result: * APT installs all packages started with `language-pack-`. Actual results: * APT does not install packages started with `language-pack-`, shows error instead: $ sudo apt install language-pack-* Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package language-pack-* --- Note: the `sudo apt-get install language-pack-*` works as expected, will install 391 packages. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 1.9.7 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Jan 20 22:33:41 2020 InstallationDate: Installed on 2020-01-19 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200119) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1860366/+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 1879770] Re: Renaming interfaces using *.link file does not work
I experiencing the same problem. My two Ethernet interfaces does not get renamed. I want to accomplish the following. eth0 => eth1 eth1 => eth0 Basically switching names between the Ethernet interfaces. I had the same exact setup on 18.04 which worked. You can find some information about my system below. Please let me know if I should provide more information. == networkctl(1) == # networkctl status eth0 WARNING: systemd-networkd is not running, output will be incomplete. Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found. ● 2: eth0 Link File: n/a Network File: n/a Type: ether State: n/a (unmanaged) HW Address: e0:d5:5e:43:7e:52 (GIGA-BYTE TECHNOLOGY CO.,LTD.) MTU: 1500 (min: 68, max: 9000) Queue Length (Tx/Rx): 1/1 Auto negotiation: yes Speed: 1Gbps Duplex: full Port: tp Address: 10.88.130.28 fe80::e2d5:5eff:fe43:7e52 Gateway: 10.88.0.1 (Hewlett Packard) May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth0: Failed to rename network interface 2 from 'eth0' to 'eth1': File exists May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth0: Failed to process device, ignoring: File exists # networkctl status eth1 WARNING: systemd-networkd is not running, output will be incomplete. Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not found. ● 3: eth1 Link File: n/a Network File: n/a Type: ether State: n/a (unmanaged) HW Address: 68:05:ca:75:3d:65 (Intel Corporate) MTU: 1500 (min: 68, max: 9212) Queue Length (Tx/Rx): 1/1 Auto negotiation: yes Speed: n/a Port: tp May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth1: Failed to rename network interface 3 from 'eth1' to 'eth0': File exists May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth1: Failed to process device, ignoring: File exists == systemd.link(5) == # ls -l /etc/systemd/network total 8 -rw-r--r-- 1 root root 55 May 28 14:23 70-eth0.link -rw-r--r-- 1 root root 55 May 28 14:23 70-eth1.link # cat /etc/systemd/network/70-eth0.link [Match] MACAddress=68:05:ca:75:3d:65 [Link] Name=eth0 # cat /etc/systemd/network/70-eth1.link [Match] MACAddress=e0:d5:5e:43:7e:52 [Link] Name=eth1 # find / -iname "*.link" /usr/lib/systemd/network/73-usb-net-by-mac.link /usr/lib/systemd/network/99-default.link /etc/systemd/network/70-eth1.link /etc/systemd/network/70-eth0.link == netplan(5) == # ls -l /etc/netplan/ total 4 -rw-r--r-- 1 root root 104 May 28 14:23 01-network-manager-all.yaml # cat /etc/netplan/01-network-manager-all.yaml # Let NetworkManager manage all devices on this system network: version: 2 renderer: NetworkManager == interfaces(5) == # cat /etc/network/interfaces auto lo eth0 eth1 iface lo inet loopback iface eth1 inet dhcp wpa-driver wired wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf iface eth0 inet static address 192.168.0.1 netmask 255.255.255.0 == systemd.network(5) == # systemctl is-active systemd-network inactive -- 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/1879770 Title: Renaming interfaces using *.link file does not work Status in systemd package in Ubuntu: Incomplete Bug description: Dear Ubuntu team, I wanted to use "systemd-networkd" intead of "udev" to rename network interface like this: (replace MAC by real one) echo '[Match] MACAddress=12:34:56:78:90:11 [Link] Name=myname123' | sudo tee '/etc/systemd/network/myname123.link' (and reboot) But it does not work. And it should work based on the systemd documentation. I googled the issue but I didn't find anything interesting instead that I should run
[Touch-packages] [Bug 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
The issue should be reassigned to libifd-cyberjack6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+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 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
Successfully verified fixes on xenial, bionic, and eoan. The autopkgtest regressions on xenial were due to flaky tests on i386 and armhf; these have been re-run successfully. The regressions on bionic look like a transient network failure (would be grateful if someone could attempt a re-run on those). The same is true of one of the regressions on eoan; the other *may* be (would be grateful if someone could attempt a re-run of those too). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+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 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
@Ludovic Rousseau (ludovic-rousseau-gmail) You are right, but they share the same source package https://packages.ubuntu.com/source/focal/pcsc-cyberjack . For me here the main question is - which application creates `pcscd` group first time? Or it should be created by user manually on first time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+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 1874953] Re: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127
Hi! I agree, this: less (551-1) sid; urgency=low * move binaries back to /usr/bin (closes: #500092) is almost certainly related. If during the upgrade process the new 'less' package is unpacked but not configured yet, there's a window where the pager alternative points to the wrong location. I can't see an easy way to fix this. What the linked Debian bug suggests, that is: make dpkg fallback to more(1) if $PAGER is not available, is probably the right balance between making dpkg solid and not adding an overly complex logic for what basically is a one-off failure. ** Summary changed: - package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 + dpkg: conffile difference visualizer subprocess returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1874953 Title: dpkg: conffile difference visualizer subprocess returned error exit status 127 Status in dpkg package in Ubuntu: Triaged Status in less package in Ubuntu: Confirmed Status in smartmontools package in Ubuntu: Invalid Status in dpkg package in Debian: Unknown Bug description: Issue occurred on upgrade from 19.10 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: smartmontools 7.1-1build1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 24 21:33:08 2020 ErrorMessage: conffile difference visualizer subprocess returned error exit status 127 InstallationDate: Installed on 2011-06-18 (3233 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: smartmontools Title: package smartmontools 7.1-1build1 failed to install/upgrade: conffile difference visualizer subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago) mtime.conffile..etc.default.smartmontools: 2017-12-08T19:12:02.064375 mtime.conffile..etc.smartd.conf: 2017-12-08T20:27:28.727282 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1874953/+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 1881129] Re: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug
** Tags removed: need-duplicate-check -- 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/1881129 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug Status in lightdm package in Ubuntu: New Bug description: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1881129/+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 1743179] Re: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current s
** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1743179 Title: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in mesa package in Ubuntu: Invalid Bug description: I dont know further about this issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Sat Jan 13 15:21:58 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 libglapi-mesa 17.2.4-0ubuntu1~16.04.2 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libgles2-mesa:amd64:17.2.4-0ubuntu1~16.04.2 Processing triggers for fontconfig (2.11.94-0ubuntu1.1) ... dpkg: error processing package libgles2-mesa:amd64 (--configure): package libgles2-mesa:amd64 is not ready for configuration ErrorMessage: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:81eb] InstallationDate: Installed on 2017-12-01 (43 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b56c Chicony Electronics Co., Ltd Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic.efi.signed root=UUID=4a5683fe-8ecb-454c-a223-c9217cacacfd ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: mesa Title: package libgles2-mesa:amd64 17.2.4-0ubuntu1~16.04.2 failed to install/upgrade: package libgles2-mesa:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EB dmi.board.vendor: HP dmi.board.version: 61.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/05/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EB:rvr61.41:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId 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.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Jan 14 09:23:45 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1671 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743179/+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 1730065] Re: Hedgewars crashing starting a game on artful
assuming it's fixed by now ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1730065 Title: Hedgewars crashing starting a game on artful Status in mesa package in Ubuntu: Invalid Bug description: After I upgraded to Artful I noticed the Hedgewars game crashing while starting a new game. After some debugging I found this happens in the following library: Program received signal SIGSEGV, Segmentation fault. 0xb0fd2a75 in ?? () from /usr/lib/i386-linux-gnu/dri/i965_dri.so It is from libgl1-mesa-dri package (version 17.2.2-0ubuntu1). So I decided to roll this package back to previous version. I downloaded and installed the following packages from Zesty: - libgl1-mesa-dri_17.0.3-1ubuntu1_i386.deb - libegl1-mesa_17.0.3-1ubuntu1_i386.deb - libgbm1_17.0.3-1ubuntu1_i386.deb - libllvm4.0_4.0-1ubuntu1_i386.deb And this solved the issue. Below some technical details. Please let me know if you need something else. Distro: Ubuntu 17.10 Architecture: i386 MachineType: Acer Extensa 5620 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (primary) [1025:011f] Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1025:011f] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1730065/+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 1749449] Re: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is
I believe this was a bug in apt/dpkg ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid -- 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/1749449 Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1 -mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 Status in mesa package in Ubuntu: Invalid Bug description: Error occurred when running the software updater this morning. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 Feb 14 08:00:48 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed DuplicateSignature: package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1 Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over (17.2.8-0ubuntu0~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] [1002:682b] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3] InstallationDate: Installed on 2014-09-06 (1256 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: HP 510-p127c ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: mesa Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: CNV64609PD dmi.board.name: 822A dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV64609PD dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-p127c 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.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jan 28 01:00:43 2018 xserver.configfile: default xserver.errors: RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749449/+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 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/95 -- 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/1880541 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1 Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: New Bug description: During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to configure interrupting the upgrade. dpkg complained that kvm already exist but it is not a system group. From what I saw my user was the only member of kvm group I don't recall installing kvm manually but I do have Android emulator installed so it is possible that it is related. Removing kvm group via groupdel kvm allowed dpkg --configure -a to succeed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules Date: Mon May 25 11:01:36 2020 ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2017-10-18 (949 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.80 dmi.board.name: X370 Taichi 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.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880541/+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 1881129] [NEW] package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug
Public bug reported: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1881129 Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug Status in lightdm package in Ubuntu: New Bug description: u ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic i686 ApportVersion: 2.14.1-0ubuntu3.29 AptOrdering: lubuntu-desktop: Purge lubuntu-default-session: Purge lubuntu-core: Purge lubuntu-default-settings: Purge lightdm: Purge Architecture: i386 Date: Thu May 28 13:54:09 2020 DuplicateSignature: package:lightdm:1.10.6-0ubuntu1:subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug ErrorMessage: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug InstallationDate: Installed on 2014-09-27 (2069 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2) LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user=marleen autologin-user-timeout=0 autologin-session=lightdm-autologin LightdmGreeterLog: ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1399): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/user/.face’ mislukt: Bestand of map bestaat niet ** (lightdm-gtk-greeter:1195): WARNING **: Failed to load user image: Openen van bestand ‘/home/marleen/.face’ mislukt: Bestand of map bestaat niet g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.24 SourcePackage: lightdm Title: package lightdm 1.10.6-0ubuntu1 failed to install/upgrade: subproces post-removal script geïnstalleerd gaf een foutwaarde 1 terug UpgradeStatus: Upgraded to trusty on 2020-05-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1881129/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive
I can confirm this bug on a life-system xubuntu 20.04. In addition to the increase of one month in date modified, sometimes the date accessed shows "1979-12-31 00:00:00" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: New Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1875300] Re: [Ubuntu 20.04 s390] Failed to install os from CD
This is now available in groovy daily-live isos. This is change in other os components rather than subiquity itself. Hence opening tasks against the other packages that we had to fix up. Cause we have fixes in busybox, initramfs-tools, lvm2, casper to make this to work. ** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Also affects: casper (Ubuntu) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu) Importance: Undecided => Wishlist ** Also affects: lvm2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: casper (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: lvm2 (Ubuntu Groovy) Importance: Wishlist Status: New ** Also affects: casper (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: lvm2 (Ubuntu Groovy) Status: New => Fix Released ** Changed in: casper (Ubuntu Groovy) Status: New => Fix Released ** Changed in: casper (Ubuntu Focal) Status: New => Confirmed ** Changed in: lvm2 (Ubuntu Focal) Status: New => Confirmed ** Changed in: casper (Ubuntu Focal) Importance: Undecided => High ** Changed in: lvm2 (Ubuntu Focal) Importance: Undecided => High ** Changed in: subiquity Status: Incomplete => Invalid ** Changed in: ubuntu-z-systems Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1875300 Title: [Ubuntu 20.04 s390] Failed to install os from CD Status in subiquity: Invalid Status in Ubuntu on IBM z Systems: Confirmed Status in casper package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in casper source package in Focal: Confirmed Status in lvm2 source package in Focal: Confirmed Status in casper source package in Groovy: Fix Released Status in lvm2 source package in Groovy: Fix Released Bug description: Failed to install os from CD ---Installation Media--- ubuntu-20.04-live-server-s390x.iso ---Machine type --- model: 8561 - T01 ---Steps--- Login to HMC Load CD via 'Load from Removable media or Serer' Select FTP After loaded successfully Get following message in Operating System Messages and installation failed: ln: /tmp/mountroot-fail-hooks.d//scripts/init-premount/lvm2: No such file or dir ectory To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1875300/+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 1881142] Re: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring"
On old system I see that `pcscd` group GID was 145. So the simple command below will fix the issue: ``` sudo groupadd -g 145 pcscd ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1881142 Title: Installation on clean 20.04 LTS system results in "/usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring" Status in pcsc-cyberjack package in Ubuntu: New Status in pcsc-lite package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install "libifd-cyberjack6" package 3. Reload udev Expected results: * log contains no errors or warnings Actual results: * log contains messages: May 28 18:03:19 focal systemd[1]: Stopping udev Kernel Device Manager... May 28 18:03:19 focal systemd[1]: systemd-udevd.service: Succeeded. May 28 18:03:19 focal systemd[1]: Stopped udev Kernel Device Manager. May 28 18:03:19 focal systemd[1]: Starting udev Kernel Device Manager... May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:6 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:7 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:8 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:9 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:10 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:11 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:12 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:13 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:14 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:15 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:16 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:17 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:18 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:19 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:20 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:21 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:22 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:23 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd-udevd[11464]: /usr/lib/udev/rules.d/60-libifd-cyberjack6.rules:24 Unknown group 'pcscd', ignoring May 28 18:03:19 focal systemd[1]: Started udev Kernel Device Manager. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libifd-cyberjack6 3.99.5final.sp13+dfsg-2build1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Thu May 28 18:06:52 2020 InstallationDate: Installed on 2020-04-23 (34 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pcsc-cyberjack UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-cyberjack/+bug/1881142/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 Thank you Simon Déziel you saved my life!!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
** Also affects: apport (Ubuntu Groovy) Importance: Low Status: Triaged ** Tags removed: rls-gg-incoming -- 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/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Triaged Status in apport source package in Xenial: Triaged Status in apport source package in Groovy: Triaged Bug description: When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1833174] Re: Shadowing the vim-window results in vim-gtk3 crash
** Also affects: vim (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: vim (Ubuntu Groovy) Importance: High Status: Triaged ** Changed in: vim (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 ** Changed in: vim (Ubuntu Focal) Importance: Undecided => High ** Changed in: vim (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1833174 Title: Shadowing the vim-window results in vim-gtk3 crash Status in vim: Unknown Status in vim package in Ubuntu: Triaged Status in vim source package in Focal: Triaged Status in vim source package in Groovy: Triaged Bug description: With XFCE when I try to "shadow" the vim-gtk3 window (just to show only the title bar) it results in a vim crash and the window just disappears without any core dump neither .swp files on. The only message I get on the terminal is BadMatch (invalid parameter attributes) Vim: Got X error Vim: Finished. This behaviour started from Xubuntu 18.04. The vim-gtk package is not suffering from this problem. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: vim-gtk3 2:8.1.0320-1ubuntu3.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 18 09:10:38 2019 InstallationDate: Installed on 2019-04-23 (55 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1833174/+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 1311056] Re: [SRU] apt-add-repository adds duplicate commented/disabled source lines
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1311056 Title: [SRU] apt-add-repository adds duplicate commented/disabled source lines Status in python-apt package in Ubuntu: Fix Released Status in python-apt source package in Xenial: Fix Committed Status in python-apt source package in Bionic: Fix Committed Status in python-apt source package in Eoan: Fix Committed Bug description: Impact == Under most circumstances, the impact is minimal (a few extra redundant comment lines in apt sources. However, if users are automating source removal / addition on a machine (as in comment 11), there is the potential to wind up with an excessively large (and thus slow to parse) apt sources configuration. Test packages for the supported releases are available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/python-apt Built from the source which can be found in the following branches: https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-xenial https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-bionic https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git /python-apt/+ref/sru-dupe-ppa-eoan Test Case = * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the presence of one uncommented "deb" line, and one commented "deb-src" line * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note the uncommented "deb" line is still there but the commented "deb-src" line has now been duplicated * sudo add-apt-repository ppa:waveform/python-apt * sudo apt upgrade # update python-apt to fixed version * sudo add-apt-repository -y ppa:deadsnakes/ppa * cat /etc/apt/sources.list.d/deadsnakes*.list * Note there has been no further duplication of the commented "deb-src" line Regression Potential Minimal; test cases have been added to cover the duplication case, and to cover the enabling of sources (which was not covered by existing tests, but was part of the code altered to fix the duplication case), and insertion of sources at a position (again, not covered by existing tests but modified as part of the fix). The test case has been used successfully on all targeted releases (xenial, bionic, and eoan). Original Description Trusty Tahr 14.04 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y ppa:aims/aims-desktop gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) OK 0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main 0 root@osprey:/etc/apt/sources.list.d# That deb-src line should have stayed commented out, and not been duplicated. (Commented deb lines should of course be uncommented, as already fixed per https://bugs.launchpad.net/ubuntu/+source/python- apt/+bug/1042916 .) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1311056/+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 1880250] Re: disk check progress no longer visible
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Groovy) Importance: Undecided Status: Incomplete ** Also affects: systemd (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: plymouth (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Tags removed: champagne rls-ff-incoming rls-gg-incoming ** Changed in: plymouth (Ubuntu Groovy) Status: Incomplete => Invalid ** Changed in: plymouth (Ubuntu Focal) Status: New => Invalid ** Tags added: papercut -- 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/1880250 Title: disk check progress no longer visible Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in plymouth source package in Focal: Invalid Status in systemd source package in Focal: New Status in plymouth source package in Groovy: Invalid Status in systemd source package in Groovy: New Bug description: It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1
** Tags removed: rls-ff-incoming ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Milestone: None => ubuntu-20.04.1 -- 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/1880541 Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1 Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Focal: New Bug description: During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to configure interrupting the upgrade. dpkg complained that kvm already exist but it is not a system group. From what I saw my user was the only member of kvm group I don't recall installing kvm manually but I do have Android emulator installed so it is possible that it is related. Removing kvm group via groupdel kvm allowed dpkg --configure -a to succeed ProblemType: Package DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules Date: Mon May 25 11:01:36 2020 ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 InstallationDate: Installed on 2017-10-18 (949 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: systemd Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1 UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago) dmi.bios.date: 07/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.80 dmi.board.name: X370 Taichi 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.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1880541/+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 1880250] Re: disk check progress no longer visible
So i think this is what happens: systemd-fsckd starts, flashes the message on how to skip it. Realiases there are no fscks to run, and exits, without clearing the Ctrl+C imaage. Then we freeze that output until gdm starts. Previously, we only flashed "Ctrl+C message" upon receiving the first update from fsck, and cleared it after fsckd exits. This is not happening anymore. I'm not sure if fsckd is sending the wrong messages, or if plymouth is not processing them correctly. ** Changed in: plymouth (Ubuntu Focal) Status: Invalid => New ** Changed in: plymouth (Ubuntu Groovy) Status: Invalid => New -- 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/1880250 Title: disk check progress no longer visible Status in plymouth package in Ubuntu: New Status in systemd package in Ubuntu: New Status in plymouth source package in Focal: New Status in systemd source package in Focal: New Status in plymouth source package in Groovy: New Status in systemd source package in Groovy: New Bug description: It seems the transition to bgrt lost something with Ubuntu's disk check details. The only thing I see on my screen during a long disk check is the "press Ctrl-C to stop all in progress disk checks" with no progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
** Tags removed: rls-ff-incoming ** Also affects: glibc (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: btrfs-progs (Ubuntu Focal) Importance: Undecided Status: New -- 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/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: New Status in glibc package in Ubuntu: New Status in initramfs-tools package in Ubuntu: New Status in btrfs-progs source package in Focal: New Status in glibc source package in Focal: New Status in initramfs-tools source package in Focal: New Bug description: With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket
I did change the status by accident. Don't know how to correct it. Sorry. ** Changed in: dbus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1854314 Title: Legacy directory /var/run in /lib/systemd/system/dbus.socket Status in D-Bus: New Status in dbus package in Ubuntu: Fix Released Status in dbus package in Debian: Fix Released Bug description: dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64 Re(o)curring after each new upgrade of dbus, for quite some time and still... $ dmesg|grep accordingly systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Originally: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/var/run/dbus/system_bus_socket After change: $cat /lib/systemd/system/dbus.socket [Unit] Description=D-Bus System Message Bus Socket [Socket] ListenStream=/run/dbus/system_bus_socket To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1854314/+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 1881199] [NEW] [SoundCore mini, playback] No sound at all from Rhythmbox
Public bug reported: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET40W(1.14):bd04/18/2016:svnLENOVO:pn20FQCTO1WW:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FQCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FQCTO1WW dmi.product.sku: LENOVO_MT_20FQ_BU_Think_FM_ThinkPad X1 Yoga 1st dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881199 Title: [SoundCore mini, playback] No sound at all from Rhythmbox Status in pulseaudio package in Ubuntu: New Bug description: After connecting via bluetooth the Soundcore Mini, I can get sound to play through it just fine from e.g. the Chromium browser, but not from Rhythmbox, which instead always plays from the laptop's internal speakrs. In the bluetooth settings, Soundcore Mini is connected. In the sound settings, Soundcore Mini is selected, and the "Test" button opens an UI that lets me play test sounds, and it works. And indeed it works for e.g. Google Chrome for a youtube video. But Rhythmbox plays through the internal speakers no matter what. I've tried restarting Rhythmbox, removing the ~/.pulse_secure/pulse/ folder with settings and then running "pulseaudio -k", and then restarting Rhythmbox, to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 28 22:00:38 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1434 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SoundCore mini Symptom_DevicesInUse: Cannot stat file /proc/43906/fd/6: Permission denied USERPID ACCESS COMMAND /dev/snd/controlC0: albert120462 F pulseaudio /dev/snd/pcmC0D0c: albert120462 F...m pulseaudio Symptom_Type: No sound at all Title: [SoundCore mini, playback] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-20 (8 days ago) dmi.bios.date: 04/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET40W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FQCTO1WW dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist
There is actually an SRU in progress for libseccomp: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1868720 Title: backport time64 syscalls whitelist Status in docker.io package in Ubuntu: New Status in libseccomp package in Ubuntu: Fix Released Status in docker.io source package in Bionic: New Status in libseccomp source package in Bionic: Triaged Status in docker.io source package in Disco: Won't Fix Status in libseccomp source package in Disco: Won't Fix Status in docker.io source package in Eoan: New Status in libseccomp source package in Eoan: Triaged Status in docker.io source package in Focal: New Status in libseccomp source package in Focal: Fix Released Bug description: A number of new *time64 syscalls are introduced in newer kernel series (>=5.1.x): 403: clock_gettime64 404: clock_settime64 405: clock_adjtime64 406: clock_getres_time64 407: clock_nanosleep_time64 408: timer_gettime64 409: timer_settime64 410: timerfd_gettime64 411: timerfd_settime64 412: utimensat_time64 413: pselect6_time64 414: ppoll_time64 In particular utimensat_time64 is now used inside glibc>=2.31 In turn ubuntu with has trouble running docker images of newer distros. This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not focal. See a similar report at Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1770154 A solution could be to backport the related changes from 2.4.2 similarly to what happened for the statx whitelisting (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1868720/+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 1876055] Re: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libseccomp (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Xenial: Confirmed Status in libseccomp source package in Bionic: Confirmed Status in libseccomp source package in Eoan: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case of *this* SRU, we are only doing a micro-version upgrade from 2.4.1 to 2.4.3 so this carries even less change of regressions. Any possible regressions may include applications now seeing correct system call
[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libseccomp (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876055 Title: SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base Status in libseccomp package in Ubuntu: Confirmed Status in libseccomp source package in Xenial: Confirmed Status in libseccomp source package in Bionic: Confirmed Status in libseccomp source package in Eoan: Confirmed Status in libseccomp source package in Focal: Confirmed Status in libseccomp source package in Groovy: Confirmed Bug description: [Impact] The combination of snap-confine and snap-seccomp from snapd uses libseccomp to filter various system calls for confinement. The current version in eoan/bionic/xenial (2.4.1) is missing knowledge of various system calls for various architectures. As such this causes strange issues like python snaps segfaulting (https://github.com/snapcore/core20/issues/48) or the inadvertent denial of system calls which should be permitted by the base policy (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal- arm64/17237). libseccomp in groovy is using the latest upstream base release (2.4.3) plus it includes a patch to add some missing aarch64 system calls (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633). SRUing this version back to older stable releases allows libseccomp to operate correctly on all supported architectures. Included as part of this SRU are test-suite reliability improvements - currently the xenial libseccomp package overrides test-suite failures at build time to ignore failures. This masks the fact that on ppc64el and s390x there are currently test suite failures at build time for xenial - these failures occur since libseccomp now includes knowledge of system calls for these architectures but which the linux-libc-dev package for xenial does not actually define (since this is based of the 4.4 kernel in xenial whereas libseccomp 2.4.1 in xenial has knowledge of all system calls up to 5.4). In this SRU I have instead fixed the test suite failures for xenial by including a local (test-suite specific) set of architecture specific kernel headers from the linux-libc-dev in focal for all releases. These are just the headers which define the system call numbers for each architecture *and* these are added to tests/include/$ARCH in the source package (and tests/Makefile.am is then updated to include these new headers only). As such this ensures the actual build of libseccomp or any of the tools does not reference these headers. This allows the test suite in libseccomp to then be aware of theses system calls and so all unit tests for all architectures now pass. In any future updates for libseccomp to add new system calls, we can then similarly update these local headers to ensure the unit tests continue to work as expected. [Test Case] libseccomp includes a significant unit test suite that is run during the build and as part of autopkgtests. To verify the new aarch64 system calls are resolved as expected the scmp_sys_resolver command can be used as well: $ scmp_sys_resolver -a aarch64 getrlimit 163 (whereas in the current version in focal this returns -10180 as libseccomp was not aware of this system-call at compile-time). As part of this SRU, the test suite in libseccomp has been patched to include a local copy of the architecture-specific kernel headers from the 5.4 kernel in focal *for all releases*, so that all system calls which are defined for the 5.4 kernel are known about *for the libseccomp test suite*. This allows all unit tests to pass on older releases as well and defaults the build to fail on unit test failures (whereas currently in xenial this has been overridden to ignore failures). [Regression Potential] This has a low regression potential due to significant testing with many packages that depend on libseccomp (lxc, qemu, snapd, apt, man etc) and none have shown any regression using this new version. The re-enablement of build failure on test failure at build time also ensures that we can reliably detect FTBFS issues in the future. No symbols have been removed (or added) with this update in version so there is no chance of regression due to ABI change etc. In the past, the security team has performed more significant version upgrades for libseccomp (2.2, 2.3, 2.4) -> 2.4.1 without major incident. In the case of *this* SRU, we are only doing a micro-version upgrade from 2.4.1 to 2.4.3 so this carries even less change of regressions. Any possible regressions may include applications now seeing correct system call
