[Touch-packages] [Bug 1970374] [NEW] package linux-image-unsigned-5.14.0-1032-oem (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: It has been one month that I cannot update my kernel and I get this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.14.0-1032-oem (not installed) ProcVersionSignature: Ubuntu 5.14.0-1029.32-oem 5.14.21 Uname: Linux 5.14.0-1029-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 AptOrdering: linux-image-5.14.0-1032-oem:amd64: Remove linux-image-unsigned-5.14.0-1032-oem:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 25 09:29:36 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-unsigned-5.14.0-1032-oem (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1970374 Title: package linux-image-unsigned-5.14.0-1032-oem (not installed) 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: It has been one month that I cannot update my kernel and I get this error. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-unsigned-5.14.0-1032-oem (not installed) ProcVersionSignature: Ubuntu 5.14.0-1029.32-oem 5.14.21 Uname: Linux 5.14.0-1029-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 AptOrdering: linux-image-5.14.0-1032-oem:amd64: Remove linux-image-unsigned-5.14.0-1032-oem:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 25 09:29:36 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-unsigned-5.14.0-1032-oem (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970374/+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 1956469] [NEW] GPU related problems after kernel update
Public bug reported: After the last stable kernel update, my system is slow, browsers fail to start and crash and dmesg is full of gpu related error messages. Loading the previous kernel does not result in any problems. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 14:57:16 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-22-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-23-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2021-07-16 (172 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr:sku8KX18EA#ABD: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1956469 Title: GPU related problems after kernel update Status in xorg package in Ubuntu: New Bug description: After the last stable kernel update, my system is slow, browsers fail to start and crash and dmesg is full of gpu related error messages. Loading the previous kernel does not result in any problems. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 5 14:57:16 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.5, 5.13.0-22-generic, x86_64: installed v4l2loopback, 0.12.5, 5.13.0-23-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-22-generic, x86_64: installed virtualbox, 6.1.26, 5.13.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2021-07-16 (172 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210715) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2019 dmi.bios.
[Touch-packages] [Bug 1477106] Re: Cups directive "Browsing Off" ignored by print dialog
Since the bug report is very old, the original cause for what is described here may have changed. But on a focal system, the gtk print dialog populates the printer list on its own. Even if cups is not running locally, it queries avahi-daemon and produces a list of printers. This is causing a number of issues, including printer duplicates, printer entries that don't work, printers that are labeled in a weird way etc. It is silly that such broken behaviour cannot be turned off. In any case, until this improves, users may choose to use a patched version of gtk3 where the broken avahi lookup is removed from the printer dialog: https://launchpad.net/~launchpad-weyland/+archive/ubuntu/libgtk3-no- avahi/ Also see lp:1379359 and lp:1753509 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1477106 Title: Cups directive "Browsing Off" ignored by print dialog Status in gtk+3.0 package in Ubuntu: New Bug description: On Ubuntu 15.04, I have cups configured with the "Browsing Off" option in the /etc/cups/cupsd.conf to disallow listing non local printers (I'm on a huge network where there are many printers). This works well with non Gnome applications (LibreOffice, Adobe Reader for example). But the print dialog of Gnome GTK3 applications seems to ignore the "Browsing Off" directive and lists a lot of remote printers... The same problem arises with Gnome GTK2 applications... cups version: 2.0.2-1ubuntu3.2 gtk3 version: 3.14.13-0ubuntu1 gtk2 version: 2.24.27-0ubuntu1 The package cups-browsed is not installed. Here is the content of my cupsd.conf: # # Configuration file for the CUPS scheduler. See "man cupsd.conf" for a # complete description of this file. # # Log general information in error_log - change "warn" to "debug" # for troubleshooting... LogLevel warn PageLogFormat # Deactivate CUPS' internal logrotating, as we provide a better one, especially # LogLevel debug2 gets usable now MaxLogSize 0 # Only listen for connections from the local machine. Listen localhost:631 Listen /var/run/cups/cups.sock # Show shared printers on the local network. Browsing Off BrowseLocalProtocols dnssd # Default authentication type, when authentication is required... DefaultAuthType Basic # Web interface setting... WebInterface Yes # Restrict access to the server... Order allow,deny # Restrict access to the admin pages... Order allow,deny # Restrict access to configuration files... AuthType Default Require user @SYSTEM Order allow,deny # Set the default printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... Order deny,allow Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # All printer operations require a printer operator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... Require user @OWNER @SYSTEM Order deny,allow Order deny,allow # Set the authenticated printer/job policies... # Job/subscription privacy... JobPrivateAccess default JobPrivateValues default SubscriptionPrivateAccess default SubscriptionPrivateValues default # Job-related operations must be done by the owner or an administrator... AuthType Default Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow # All administration operations require an administrator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # All printer operations require a printer operator to authenticate... AuthType Default Require user @SYSTEM Order deny,allow # Only the owner or an administrator can cancel or authenticate a job... AuthType Default Require user @OWNER @SYSTEM Order deny,allow Order deny,allow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1477106/+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 1942427] Re: Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
Unplugging the docking station and running with one external display via hdmi works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in xorg package in Ubuntu: New Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942427/+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 1942427] Re: Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
Also, switching to an "Ubuntu" session instead of "Ubuntu with Xorg" made no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in xorg package in Ubuntu: New Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1942427/+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 1942427] [NEW] Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915
Public bug reported: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S30S00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN24ET60W(1.35):bd08/10/2020:br1.35:efr1.20:svnLENOVO:pn20L6S30S00:pvrThinkPadT480:rvnLENOVO:rn20L6S30S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S30S00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1942427 Title: Upgrade to 5.11.0-31-generic #33 breaks use of external displays with i915 Status in xorg package in Ubuntu: New Bug description: upgrading to latest packages, my setup with 3 displays (internal plus 2 external, plugged into Lenovo USB-c base station) no longer works. the Settings -> Displays app does find all displays, but the system only displays on the internal one. Attempting to enable all displays fails, the third disappears from view in the Displays app just before it presents the "Keep settings" dialog. However no output appears on any of the external displays other than the display's own firmware messages. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CompositorRunning: None Date: Thu Sep 2 10:54:09 2021 DistUpgraded: 2021-06-14 13:24:54,764 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-08-13 (384 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20L6S30S00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-14 (79 days ago) dmi.bios.date: 08/10/2020 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET60W (1.35 ) dmi.board.asset.tag: Not Availa
[Touch-packages] [Bug 1928763] [NEW] Ubuntu does not recognize the touchpad
Public bug reported: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928763 Title: Ubuntu does not recognize the touchpad Status in xorg package in Ubuntu: New Bug description: The device in question is a Lenovo IdeaPad 5 15ARE05. Using the touchpad does not work in Ubuntu. Input does not get recognized. Using an external USB mouse works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 18 10:07:58 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2021-03-24 (54 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210322) MachineType: LENOVO 81YQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=216cd85a-60ae-4f84-b68c-ba90f8154877 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2021 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN39WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvrE7CN39WW:bd01/14/2021:br1.39:efr1.39:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.pr
[Touch-packages] [Bug 1876267] Re: Changing sound left/right balance impacts on front/back
Thanks Sebastien - i have reported it there to. https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1045 No Problems with pavucontrol. Thats my workaround atm. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1045 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1045 -- 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/1876267 Title: Changing sound left/right balance impacts on front/back Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-23 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card
Hi Hui, Thanks! The fix resolve the problem with the mode selector. Now I can switch between stereo and 5.1 without falling back to the default audio device. The problem with the sliders is still there... BR, Mathias -- 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/1876267 Title: Audio settings strange behaviour with ASUS STXII sound card Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-23 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1876267/+attachment/5364324/+files/ProcCpuinfoMinimal.txt -- 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/1876267 Title: Audio settings strange behaviour with ASUS STXII sound card Status in gnome-control-center package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-23 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio PackageArchitecture: amd64 ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876267/+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 1876267] Re: Audio settings strange behaviour with ASUS STXII sound card
apport information ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. + The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf + In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) - Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. - + Lfe slider should work. BR, Mathias ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1-1ubuntu5) Expected behavior: It should be possible to select the sound card and the setting should be retained even if the speaker configuration is changed. Furthermore, the balance sliders should not influence each other. - Lfe slider should work. + Lfe slider should work. (And in a perfect world this would also activate lfe remixing and gives the user a cross over frequency option, but this is just an idea :) BR, Mathias ** Tags added: apport-collected ** Description changed: What happens: If an Asus STXII 7.1 sound card is installed and another output device is present, there is a strange behavior in the Gnome audio settings. After the first start of Ubuntu the Asus soundcard is not the default device. This can be selected in the Gnome settings. If a different speaker configuration is selected now. E.g. stereo instead of 5.1 or vice versa, the selection jumps from the Asus output device back to the original output device. The Asus sound card can then be selected again and the corresponding speaker configuration will fit now. If 5.1 is selected as the mode, there is a second problem. Moving the balance slider (left / right) moves the slider (front / back) slightly as well. The slider for lfe is grayed out, even when I enable the lfe remixing in /etc/pulse/daemon.conf In the speaker test, all 5.1 channels work fine, including the lfe. For better illustration I made a screen video. (see attachment) This is probably a general bug in Gnome - it has been occurring since Ubuntu 18.x and affects all distros that use Gnome since then. Unfortunately I was not able to make a report in Gnome, because the registration on the Gnome site does not work anymore... Maybe you have a good contact to the Gnome team? Ubuntu 20.04 LTS (Release 20.04) Package: gnome-control-center (1:3.36.1
[Touch-packages] [Bug 1847904] [NEW] intel grafic
Public bug reported: cant install intel grafic drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 14:59:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:15bd] InstallationDate: Installed on 2019-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1d57:fa01 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX200MA.504:bd11/13/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X200MA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1847904 Title: intel grafic Status in xorg package in Ubuntu: New Bug description: cant install intel grafic drivers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 13 14:59:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1043:15bd] InstallationDate: Installed on 2019-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1d57:fa01 Xenta Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X200MA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X200MA.504 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X200MA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset
[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
On my system there are more missing or broken options (not only the duplex problem) in the qt print dialog. On my bionic system i found the following other problems: - the printers are always on color mode, instead of gray-scale. - the option to select the input tray is missing. - the borders can't set smaller then the default. it would be good if not only the duplex option would be fixed. -- 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/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 11 10:23:53 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (1641 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: qtbase-opensource-src UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1788321] Re: swapon failed: invalid argument
Swapon is not working with swap file or swap partion. Mkswap with Kernel 4.15.0-30-gernic and swapon with Kernel 4.15.0-33-gernic is even not working. VMware ESXi 6.0 + Ubuntu 18.04 (32Bit) - Linux 4.15.0-33-generic (i686) affected VMware ESXi 6.0 + Ubuntu 18.04 (32Bit) - Linux 4.15.0-30-generic (i686) not affected VMware ESXi 6.0 + Ubuntu 18.04 (64Bit) - Linux 4.15.0-33-generic (x86_64) not affected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1732030] Re: 'apt update' dies with seccomp error
Had the same issue, but wihtout libnss-libvirt installed. Switching to
the mirror method also triggers the error.
# sed -i
's/http:\/\/archive.ubuntu.com\/ubuntu\//mirror:\/\/mirrors.ubuntu.com\/mirrors.txt/g'
/etc/apt/sources.list
# apt update
0% [Working]
Seccomp prevented execution of syscall 78 on architecture amd64
Reading package lists... Done
E: Method mirror has died unexpectedly!
E: Sub-process mirror returned an error code (31)
--
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/1732030
Title:
'apt update' dies with seccomp error
Status in apt package in Ubuntu:
Confirmed
Status in libvirt package in Ubuntu:
Triaged
Bug description:
$ apt-get update
0% [Working]
Seccomp prevented execution of syscall 78 on architecture amd64
Reading package lists... Done
E: Method mirror has died unexpectedly!
E: Sub-process mirror returned an error code (31)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apt 1.6~alpha5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
Date: Mon Nov 13 23:10:57 2017
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: apt
UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1643481] Re: Hardware freeze when going fullscreen in certain applications with Wayland
I'm still running into that problem with 3.22.4-1ubuntu1 on Wayland. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1643481 Title: Hardware freeze when going fullscreen in certain applications with Wayland Status in Ubuntu GNOME: Fix Committed Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Every time I press "F11" in Firefox or use "F" in VLC to go into fullscreen mode my laptop will freeze, only leaving the audio playing with a frozen image, without the ability to use my keyboard or move my touch pad or mouse, forcing me to restart my computer by holding down my power button. How to reproduce the bug in Ubuntu Gnome 17.04 on Wayland: - Press "F11" by default in Firefox to go into fullscreen mode. - Press "F" by default in VLC to go into and/or leave fullscreen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1643481/+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 1635391] [NEW] [Regression] Avahi-daemon nss-mdns hostname resolution is deactivated since 16.10 resulting in "Unable to locate printer"
Public bug reported: Since 16.10 Avahi-daemon nss-mdns hostname resolution for network printer is deactivated. This causes that print jobs against these printers fail with the error "Unable to locate printer". As a reminder, before 16.10, it hostname resolution worked perfectly. As a workaround change the existing config entry in "/etc/nsswitch.conf" from: hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns to: hosts: files mdns_minimal [NOTFOUND=return] dns myhostname as described here: https://wiki.archlinux.org/index.php/Avahi#Hostname_resolution ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 20 21:31:12 2016 InstallationDate: Installed on 2016-10-16 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1635391 Title: [Regression] Avahi-daemon nss-mdns hostname resolution is deactivated since 16.10 resulting in "Unable to locate printer" Status in avahi package in Ubuntu: New Bug description: Since 16.10 Avahi-daemon nss-mdns hostname resolution for network printer is deactivated. This causes that print jobs against these printers fail with the error "Unable to locate printer". As a reminder, before 16.10, it hostname resolution worked perfectly. As a workaround change the existing config entry in "/etc/nsswitch.conf" from: hosts: files resolve [!UNAVAIL=return] mdns4_minimal [NOTFOUND=return] dns to: hosts: files mdns_minimal [NOTFOUND=return] dns myhostname as described here: https://wiki.archlinux.org/index.php/Avahi#Hostname_resolution ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 20 21:31:12 2016 InstallationDate: Installed on 2016-10-16 (4 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1635391/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
The reboot only helps once. Next attempt to connect will fail. Usually. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
I believe this most likely is a race, when two paired devices try to reestablish the connection at the same time: When entering the car, but the HMI and the phone indicate they try connecting and it usually fails. Still after some minutes it happens, that only one side tries to initiate the connection (didn't check who actually does, car or phone) and then the connection usually gets established. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1539123] [NEW] Quick photos from lock screen
Public bug reported: It's almost impossible to take quick snapshots with locked phone: Swiping, pine code, launching the photo app just takes way too long. The fascinating scene you wanted to photograph is long gone until the photo app is ready. Therefore the lock screen should contain an easy to hit button that instantly starts the photo app, ready for taking the snapshot of the year. Android and iOS show how to do this. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1539123 Title: Quick photos from lock screen Status in camera-app package in Ubuntu: New Bug description: It's almost impossible to take quick snapshots with locked phone: Swiping, pine code, launching the photo app just takes way too long. The fascinating scene you wanted to photograph is long gone until the photo app is ready. Therefore the lock screen should contain an easy to hit button that instantly starts the photo app, ready for taking the snapshot of the year. Android and iOS show how to do this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1539123/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Could this error about "Not enough free handles to register service" be relevant? $ grep ^Nov\ 24\ 16:4.*bluetooth syslog Nov 24 16:44:15 ubuntu-phablet kernel: [6.701176]init: bluetooth-touch main process (621) terminated with status 1 Nov 24 16:44:15 ubuntu-phablet bluetoothd[655]: Bluetooth daemon 5.35 Nov 24 16:44:15 ubuntu-phablet bluetoothd[655]: Starting SDP server Nov 24 16:44:15 ubuntu-phablet bluetoothd[655]: Bluetooth management interface 1.10 initialized Nov 24 16:44:17 ubuntu-phablet kernel: [ 8.389612][BT-MOD-INIT][I]do_bluetooth_drv_init:start to do bluetooth driver init normal boot 0 Nov 24 16:44:17 ubuntu-phablet kernel: [ 8.418972][BT-MOD-INIT][I]do_bluetooth_drv_init:finish bluetooth driver init, i_ret:0 Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Failed to obtain handles for "Service Changed" characteristic Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Not enough free handles to register service Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Error adding Link Loss service Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Not enough free handles to register service Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: message repeated 2 times: [ Not enough free handles to register service] Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Current Time Service could not be registered Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: gatt-time-server: Input/output error (5) Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Not enough free handles to register service Nov 24 16:44:20 ubuntu-phablet NetworkManager[1355]: Loaded device plugin: /usr/lib/arm-linux-gnueabihf/NetworkManager/libnm-device-plugin-bluetooth.so Nov 24 16:44:19 ubuntu-phablet bluetoothd[655]: Not enough free handles to register service Nov 24 16:44:23 ubuntu-phablet bluetoothd[655]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSource Nov 24 16:44:23 ubuntu-phablet bluetoothd[655]: Endpoint registered: sender=:1.50 path=/MediaEndpoint/A2DPSink Nov 24 16:44:30 ubuntu-phablet bluetoothd[655]: Player registered: sender=:1.39 path=/_1_54 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Ok, installed rc-proposed and situation is worse with MyFord Touch (Sync2): Neither phone nor head unit see each other. Still device discovery doesn't seem entirely broken: Can see other people's phones around, can pair with iPad and Ubuntu laptop. Still after pairing no interaction is possible. File transfers simply timeout. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1501825] Re: Bq Aquaris e5 HD bluetooth problem
Duplicate of 1435040? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1501825 Title: Bq Aquaris e5 HD bluetooth problem Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: I hawe bq Aquaris e5 hd problem conect bluetooth with caraudio Clarion on Nissan Tiida. Pairing takes place in order. Near the radio display Conect fail and disconnected cell phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1501825/+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 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
Confirming for MyFord Touch in Ford Galaxy III. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1421140] [NEW] package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdpto
Public bug reported: I Can't run updates anymore. But this fixed my issues why the computer didn't shut down correctly ha-ha. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 11 12:40:32 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd]:paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. ErrorMessage: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. InstallationDate: Installed on 2014-10-30 (104 days ago) InstallationMedia: Ubuntu-Kylin 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) InterestingModules: bnep bluetooth MachineType: Packard Bell ixtreme M5120 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2bdb6c19-a5b0-4249-bdbc-4521237350cf ro quiet splash SourcePackage: bluez Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: RS740 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd03/05/2010:svnPackardBell:pnixtremeM5120:pvr:rvnPackardBell:rnRS740:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: ixtreme M5120 dmi.sys.vendor: Packard Bell hciconfig: mtime.conffile..etc.bluetooth.main.conf: 2014-11-24T14:45:25.460596 mtime.conffile..etc.dbus.1.system.d.bluetooth.conf: 2014-11-24T14:45:09.868596 rfkill: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1421140 Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. Status in bluez package in Ubuntu: New Bug description: I Can't run updates anymore. But this fixed my issues why the computer didn't shut down correctly ha-ha. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Wed Feb 11 12:40:32 2015 DuplicateSignature: package:bluez:4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd]:paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. ErrorMessage: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. InstallationDate: Installed on 2014-10-30 (104 days ago) InstallationMedia: Ubuntu-Kylin 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.1) InterestingModules: bnep bluetooth MachineType: Packard Bell ixtreme M5120 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=2bdb6c19-a5b0-4249-bdbc-4521237350cf ro quiet splash SourcePackage: bluez Title: package bluez 4.101-0ubuntu13 [modified: lib/udev/hid2hci usr/bin/ciptool usr/bin/hcitool usr/bin/l2ping usr/bin/l2test usr/bin/rctest usr/bin/rfcomm usr/bin/sdptool usr/sbin/bluetoothd] failed to install/upgrade: paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker ta bort det. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/05/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
As stated in #64, I can also confirm this bug for 14.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1396184] Re: Launching an Application via Unity results in Unity hang
No, I can't and I don't want. I left Ubuntu and switched to Manjaro because I had plenty of bugs where non of them were fixed. I will close this bug now. ** Changed in: unity Status: Incomplete => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1396184 Title: Launching an Application via Unity results in Unity hang Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: This happens rarely but it makes Unity hang. You need to restart it via another VT which results in pretty poor performance. 1. Hit Meta-Key select an application and launch Actual Result: Unity opens the application window and freezes Proposed Result: The application just opens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 25 15:46:33 2014 DistUpgraded: 2014-10-24 09:10:03,805 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17a9] InstallationDate: Installed on 2013-11-01 (389 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6570b ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-24 (32 days ago) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.43 dmi.board.name: 17A7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1103:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6570b dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 25 09:44:48 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1396184/+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 1396184] [NEW] Launching an Application via Unity results in Unity hang
Public bug reported: This happens rarely but it makes Unity hang. You need to restart it via another VT which results in pretty poor performance. 1. Hit Meta-Key select an application and launch Actual Result: Unity opens the application window and freezes Proposed Result: The application just opens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 25 15:46:33 2014 DistUpgraded: 2014-10-24 09:10:03,805 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17a9] InstallationDate: Installed on 2013-11-01 (389 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6570b ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-24 (32 days ago) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.43 dmi.board.name: 17A7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.43:bd07/16/2013:svnHewlett-Packard:pnHPProBook6570b:pvrA1029D1103:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.36:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6570b dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard 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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Nov 25 09:44:48 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1396184 Title: Launching an Application via Unity results in Unity hang Status in “unity” package in Ubuntu: New Bug description: This happens rarely but it makes Unity hang. You need to restart it via another VT which results in pretty poor performance. 1. Hit Meta-Key select an application and launch Actual Result: Unity opens the application window and freezes Proposed Result: The application just opens. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 25 15:46:33 2014 DistUpgraded: 2014-10-24 09:10:03,805 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7550M/7570M/7650M] [1002:6841] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17a9] InstallationDate: Installed on 2013-11-01 (389 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ProBook 6570b ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-24 (32 days ago)
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
This bug occured to me also in Utopic (14.10). Running dual monitor setup using radeonsi. After multiple screen locks and unlocks the bug reappeared. Is this bug supposed to be fixed in Unity 7.3.1 on Utopic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid
Same here on 14.10 coming from 14.04. I also updated the tags to reflect the affected releases. ** Tags added: trusty ** Tags added: utopic -- 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/1240336 Title: Not authorized to perform operation / Unable to determine the session we are in: No session for pid Status in “gdm” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lxdm” package in Ubuntu: Confirmed Status in “policykit-desktop-privileges” package in Ubuntu: Confirmed Bug description: After a new install of 64 bit Ubuntu 13.10 on my second partition, I used dpkg to reinstall all the same packages I had on my 32 bit 13.04 partition. I copied all my home directory files over and updated all the packages. I now find that I don't have permissions to change the network settings; I can't mount my other hard drive or any USB stick using nautilus, or (udisks without using sudo)' I can't run synaptic by clicking on the GUI (I have to go to a terminal and sudo synaptic); etc. I can't find any documentation on the configuration of policykit-desktop-privileges, so I'm filing this bug. For me it appears to be totally broken. Maybe someone can help me out. Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+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 1383008] [NEW] Xorg server crashes with radeonsi drivers during surfing
Public bug reported: Xorg crashes for a few seconds and screen turns black during normal desktop activity, running on Radeonsi drivers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 19 20:07:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e271] InstallationDate: Installed on 2014-10-18 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141016) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H81M-HDS dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/02/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH81M-HDS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.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.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Oct 19 19:27:53 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 046a:0021KEYBOARD, id 8 inputHID 046a:0021KEYBOARD, id 9 inputMicrosoft Microsoft® Comfort Mouse 4500 KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1383008 Title: Xorg server crashes with radeonsi drivers during surfing Status in “xorg” package in Ubuntu: New Bug description: Xorg crashes for a few seconds and screen turns black during normal desktop activity, running on Radeonsi drivers. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Oct 19 20:07:40 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] [1002:6810] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e271] InstallationDate: Installed on 2014-10-18 (1 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141016) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcK
[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
We're already on 14.04.1 and this bug is still open. I don't know what Canonical is thinking. They don't even care for their own stuff, developed inhouse. All this is no problem in Xfce or KDE. In Unity, even the basic things are broken and not fixed for months... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="" # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 1273201] Re: bridge_ignore_without_connections.patch breaks NM created bridge at boot
** Changed in: network-manager (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1273201 Title: bridge_ignore_without_connections.patch breaks NM created bridge at boot Status in “network-manager” package in Ubuntu: Confirmed Bug description: I've created a bridge with network-manager-gnome, the bridge slave physical device is eth0. After a reboot the bridge is brought up, but eth0 isn't attached. First test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0 and remove all other connections. After a reboot the bridge is brought up, but eth0 isn't attached. When I open /etc/NetworkManager/NetworkManager.conf and save it without any modification, eth0 is instantly added to my bridge. Strange! Second test-case: Created a bridge with network-manager-gnome with the bridge slave physical device is eth0. Disable the "autoconnect" of the default wired network. After a reboot the bridge is brought up, but eth0 isn't attached. Instead eth0 is brought up and full configured. After compiling and testing different upstream versions, i could track the problem down to bridge_ignore_without_connections.patch. A network-manager package without this specific patch, brings my bridge up at boot and adds eth0 to the bridge in both test-cases. I've checked the behaviour on my ubuntu 13.10 box with network-manager (0.9.8.0-0ubuntu22) and the trusty version network-manager (0.9.8.8-0ubuntu1) . Till now i couldn't encounter any sideeffects of removing this patch with the bridge created by libvirt. Regards Mathias Kresin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1273201/+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
