[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start
downgrading python3-276 to python3-271 helped! since then GTK is opening
up again.
https://discourse.ubuntu.com/t/spec-apt-deb822-sources-by-default/29333
fthx
Feb 16
FYI I did revert to this one:
https://launchpad.net/ubuntu/+source/python-apt/2.7.1~ubuntu1/+build/27047450/+files/python3-apt_2.7.1~ubuntu1_amd64.deb
12
(I do use old sources format).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2053228
Title:
software-properties-gtk does not start
Status in software-properties package in Ubuntu:
Fix Committed
Bug description:
On a new install with the new format sources.list software-properties-gtk
does not start:
corrado@corrado-n4-nn-0215:~$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
^^^
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
109, in __init__
self.backup_sourceslist()
File
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509,
in __init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
corrado@corrado-n4-nn-0215:~$
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: software-properties-gtk 0.99.42
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 15 10:07:43 2024
InstallationDate: Installed on 2024-02-15 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+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 1881180] Re: drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
Awesome! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1881180
Title:
drop suru-icon-theme (and use UBports' suru-icon-theme as upstream)
Status in ubuntu-themes package in Ubuntu:
Fix Released
Bug description:
As part of the initiative of packaging Lomiri (former Unity8) for
Debian, I have just created a standalone source project for suru-icon-
theme [1]. This will soon be packaged for and uploaded to Debian
unstable.
The UBports developers have added several changes to "their" suru-
icon-theme which makes it impossible to use suru-icon-theme from the
ubuntu-theme src:pkg on Ubuntu Touch. On the other hand, UBports'
suru-icon-theme should still be good to go with on Ubuntu.
Furthermore, for Debian upload, I preferred not to package the ubuntu
specific artwork as a whole. The solution at UBports upstream was
providing suru-icon-theme as a standalone upstream project.
Thus, I'd like to suggest dropping suru-icon-theme from Ubuntu Theme
(at least the bin:pkg) and use the suru-icon-theme package being
available in Debian soon('ish (dependening on NEW queue processing)).
The UBports devs are open to merge requests if that is required from
time to time.
Thanks+Greets,
Mike (aka sunweaver at debian.org)
[1] https://gitlab.com/ubports/core/suru-icon-theme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1881180/+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 1808421] Re: gparted produces unusual results when ZFS partitios exist
Upstream root cause and fix: * util-linux issue 918 - "blkid reports disk as zfs_member if it has a zfs_member partition" https://github.com/util-linux/util-linux/issues/918 * Fixed by commit "libblkid: (zfs) don't probe whole-disk areas covered by partitions" https://github.com/util-linux/util-linux/commit/f6e182078a3f05af3ce3b5e5a2d1956d4b9677e2 * First included in util-linux v2.35 released Jan 21 2020 https://github.com/util-linux/util-linux/blob/master/Documentation/releases/v2.35-ReleaseNotes#L231 https://github.com/util-linux/util-linux/releases/tag/v2.35 ** Bug watch added: github.com/util-linux/util-linux/issues #918 https://github.com/util-linux/util-linux/issues/918 -- 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/1808421 Title: gparted produces unusual results when ZFS partitios exist Status in GParted: New Status in gparted package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Run gparted on a disk that has ZFS partitions. It shows one entire partition. Parted seems to display correctly. gparted image attached. hbarta@saugage:~$ sudo parted /dev/sda GNU Parted 3.2 Using /dev/sda Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) p Model: ATA Samsung SSD 850 (scsi) Disk /dev/sda: 1000GB Sector size (logical/physical): 512B/512B Partition Table: gpt Disk Flags: Number Start EndSizeFile system Name Flags 1 1049kB 538MB 537MB fat32 boot, esp 2 538MB 555MB 16.8MB zfs Microsoft reserved partition msftres 3 555MB 105GB 105GB ntfs Basic data partition msftdata 4 105GB 420GB 315GB zfs rpool (parted) q hbarta@saugage:~$ hbarta@saugage:~$ sudo sgdisk -p /dev/sda Disk /dev/sda: 1953525168 sectors, 931.5 GiB Model: Samsung SSD 850 Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): EBA09D2E-0F70-4D11-8E37-C1C170CFD9DD Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 1953525134 Partitions will be aligned on 2048-sector boundaries Total free space is 1133243757 sectors (540.4 GiB) Number Start (sector)End (sector) Size Code Name 12048 1050623 512.0 MiB EF00 2 1050624 1083391 16.0 MiB0C01 Microsoft reserved ... 3 1083392 205883391 97.7 GiB0700 Basic data partition 4 205883392 820283391 293.0 GiB 8300 rpool hbarta@saugage:~$ hbarta@saugage:~$ lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 hbarta@saugage:~$ Reproduce: 1) Configure (perhaps install) Ubuntu on a drive with a ZFS partition. 2) Open gparted. Note: Same issue happens with gparted on the 18.04.1 desktop install USB. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gparted 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 13 15:05:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago) mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693 To manage notifications about this bug go to: https://bugs.launchpad.net/gparted/+bug/1808421/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
This still needs "LightDM" to work with this for Noble. That is the default DM for Mate. This is still broken in the Noble Mate Dailys, and is not close yet. Is there something else you all want us to test, try, or tweak to help get this fixed? We are willing to help, if you direct us in a direction. We have also tried other things to try to get this to work in Mate. RE: https://ubuntuforums.org/showthread.php?t=2495023 It's not like the Noble 'lightdm' package is completely broken. It works with other flavors, such as (straight-up) Ubuntu. I've installed it on Noble Ubuntu with gnome-sessions, and that works fine, with no errors. This has something to do with the combination of LightDM and the Noble Mate Desktop image. If I toggle over to a vtty, and give it startx, it brings up the Mate Desktop. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
Interesting thought. After the switch to Wayland all has been well so far. I will update if this changes, but if the issue is indeed RAM and temps related, then there is another factor to consider, it is "winter" now, ambient temperature is between 19-21 degrees vs. 23-25 for the summer (when I reported the issue). I've installed psensor to monitor temps as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
With 'apparmor=0' as a boot parameter, it boots in less than 1/3 the time, but still fails on bringing up LightDM in vtty7. When I toggle to vtty-1 it, instead of the normal cursor, waititng on the DM (LightDM), was at the console login prompt. 'startx' brings up the DE. So not bringing up the the DM at all. Let me check something... >>> mafoelffen@noble-mate-01:~$ journalctl -b -u lightdm --no-pager Feb 06 06:58:17 noble-mate-01 systemd[1]: Starting lightdm.service - Light Display Manager... Feb 06 06:58:17 noble-mate-01 lightdm[1243]: Seat type 'xlocal' is deprecated, use 'type=local' instead Feb 06 06:58:17 noble-mate-01 systemd[1]: Started lightdm.service - Light Display Manager. Feb 06 06:58:18 noble-mate-01 lightdm[1439]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=112) by (uid=0) Feb 06 06:58:18 noble-mate-01 lightdm[1439]: gkr-pam: couldn't unlock the login keyring. Feb 06 06:58:18 noble-mate-01 lightdm[1439]: pam_env(lightdm-greeter:session): deprecated reading of user environment enabled >>> Doesn't it usually get that error if an autologin failed? Having to do with gnome-keyring-daemon.serrvice? I don't see gnome-keyring-daemon.service there. Did that get replaced with something else? GDM3 also uses the same keyring... Installing just to test. I can see that might not work right either... Hmmm. Output from the end of that: >>> Creating config file /etc/gdm3/greeter.dconf-defaults with new version update-alternatives: using /etc/pam.d/gdm-smartcard-sssd-exclusive to provide /etc/pam.d/gdm-smartcar d (gdm-smartcard) in auto mode gdm.service is not active, cannot reload. invoke-rc.d: initscript gdm3, action "reload" failed. Setting up gnome-control-center (1:46~alpha-2ubuntu2) ... Processing triggers for rygel (0.42.5-1ubuntu1) ... Processing triggers for libc-bin (2.38-3ubuntu1) ... >>> sudo systemctl restart gdm >>> Success. Reboot went to GDM3 and was able to login... But >>> sudo dpkg-reconfigure lightdm reboot >>> On reboot, Lightdm fails to start LightDM and results in Black Screen. Is that enough to go off of? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Confirmed Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
LOL. Yes. I did see snap confine in the logs also... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: Confirmed Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Permissions problem wit LightDM? >>> mafoelffen@noble-mate-01:~$ sudo systemctl status lightdm --no-pager -l ● lightdm.service - Light Display Manager Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; preset: enabled) Active: active (running) since Mon 2024-02-05 21:24:19 PST; 3min 39s ago Docs: man:lightdm(1) Process: 6243 ExecStartPre=/bin/sh -c [ "$(basename $(cat /etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, status=0/SUCCESS) Main PID: 6246 (lightdm) Tasks: 6 (limit: 4559) Memory: 14.2M CPU: 99ms CGroup: /system.slice/lightdm.service ├─6246 /usr/sbin/lightdm └─6253 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch Feb 05 21:24:19 noble-mate-01 systemd[1]: Starting lightdm.service - Light Display Manager... Feb 05 21:24:19 noble-mate-01 lightdm[6246]: Seat type 'xlocal' is deprecated, use 'type=local' instead Feb 05 21:24:19 noble-mate-01 systemd[1]: Started lightdm.service - Light Display Manager. Feb 05 21:24:19 noble-mate-01 lightdm[6262]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=112) by (uid=0) Feb 05 21:24:19 noble-mate-01 lightdm[6262]: gkr-pam: couldn't unlock the login keyring. Feb 05 21:24:19 noble-mate-01 lightdm[6262]: pam_env(lightdm-greeter:session): deprecated reading of user environment enabled >>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Reinstalling lightdm and trying to start it manually, brings it right to the same failure point, where it hangs on a black screen. I think there is a problem with LightDM not displaying on this install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
** Attachment added: "_usr_lib_xorg_Xorg.0.crash" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744811/+files/_usr_lib_xorg_Xorg.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
If I reinstalled apparmor thorugh apt, then reinstalled snapd-desktop integration... Then gave it >>> startx >>> Then the desktop come up. But it will not boot to the Mate Desktop. Wait one. Reinstalled lightdm. Still boots to black screen. If you give it a nomodeset boot parameter, it boots to an init 3 console prompt(?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
That was the first boot. Machine was KVM VM: i9-138900K, 4GB RAM 25 GB vDisk, UEFI, SecureBoot off. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] Re: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Had to collect report remotely to my workstation: ** Attachment added: "apport.apparmor.2jwsui89.apport" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+attachment/5744810/+files/apport.apparmor.2jwsui89.apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2052489] [NEW] Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration
Public bug reported: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2052489 Title: Mate Daily Graphic Layer does not come up - apparmor denied snap desktop integration Status in apparmor package in Ubuntu: New Bug description: Noble Mate Daily 20230205 ISO Boots up past Splash to black screen. Last errors in logs are about apparmor denied on snap desktop integration... So the graphics layer is being denied because of an apparmor error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2052489/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
Hello, RAM: not ECC, 4x32GB @2133MHz, nothing fancy. It has been happening regularly, often enough to drive me to set up an account here and report it, however it does happen any more. At some point it has stopped. The pc in question is still using the same kernel and the same version of liblzma. I think that at some point after I reported the bug I have switched from wayland to x11, however I may be misremembering. It could also be an irrelevant change (not sure what the link would be), but I will try to verify and switch back to wayland this week and see if the error returns. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 2032577] Re: xz crashed with SIGSEGV in lzma_lzma_optimum_normal
Hi, correction to the above. The issue does NOT happen any more. It has been happening regularly, often enough to drive me to set up an account here and report it, however it does **NOT** happen any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xz-utils in Ubuntu. https://bugs.launchpad.net/bugs/2032577 Title: xz crashed with SIGSEGV in lzma_lzma_optimum_normal Status in xz-utils package in Ubuntu: New Bug description: xz segfaults. More details in https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2032379 From Dmesg.txt on that report [114838.184191] xz[431483]: segfault at 7f9a93f3701a ip 7f9b3f780c1a sp 7f9a957baa50 error 4 in liblzma.so.5.2.5[7f9b3f771000+1b000] ProblemType: Crash ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown DistroRelease: Ubuntu 22.04 ExecutablePath: /usr/bin/xz ExecutableTimestamp: 1649422298 InstallationDate: Installed on 2021-04-09 (863 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xz-utils 5.2.5-2ubuntu1 ProcCmdline: xz --check=crc32 --threads=0 -c /var/tmp/mkinitramfs-MAIN_E1GbD9 ProcCwd: / ProcEnviron: LC_CTYPE=C.UTF-8 TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17 SegvAnalysis: Segfault happened at: 0x7f9b3f780c1a:movzbl (%rdi,%r8,1),%r10d PC (0x7f9b3f780c1a) ok source "(%rdi,%r8,1)" (0x7f9a93f3701a) in non-readable VMA region: 0x7f9a90021000-0x7f9a9400 ---p None destination "%r10d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading VMA None Signal: 11 SourcePackage: xz-utils Uname: Linux 5.19.0-38-generic x86_64 UpgradeStatus: Upgraded to jammy on 2023-01-29 (204 days ago) UserGroups: N/A StacktraceTop: bt_find_func (len_limit=64, pos=9137198, cur=0x7f9a943edc3d "", cur_match=4194304, depth=24, son=son@entry=0x7f9a8afbd010, cyclic_pos=748589, cyclic_size=8388609, matches=0x7f9adc0ec324, len_best=11) at ../../../../src/liblzma/lz/lz_encoder_mf.c:483 lzma_mf_bt4_find (mf=0x7f9a9c70, matches=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:721 lzma_mf_find (mf=mf@entry=0x7f9a9c70, count_ptr=count_ptr@entry=0x7f9adc0ecb94, matches=matches@entry=0x7f9adc0ec304) at ../../../../src/liblzma/lz/lz_encoder_mf.c:28 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:846 lzma_lzma_optimum_normal (position=, len_res=, back_res=, mf=, coder=) at ../../../../src/liblzma/lzma/lzma_encoder_optimum_normal.c:804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2032577/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
I said my initial piece and recommendation here: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2046470/comments/2 It carries through here... This was brought up as a recommendation in Launchpad (here in this bug report) back in 2019, In that bug report, I questioned why this had been ignored, and not discussed much since then. It didn't go away, and it was discussed as it should have been. I was embarrassed that it had been that way for 4 years. Since then: By then Debian had already removed it from being installed as a default. Ubuntu kept it. even after that bug report... RedHat had removed it from being default installed. SUSE, is a special case, where they kept it for their Enterprise Server Lineup... Because they have different tuning settings for them, versus their desktops and other product images. But then on page 16 of their Performance Analysis, Tuning and Tools Guide (https://documentation.suse.com/sbp/server-linux/pdf/SBP-performance-tuning_en.pdf), that chapter starts out with this quote: >>> A correct IRQ configuration – above all in multi-core architecture and >>> multi-thread >>> applications– can have a profound impact on throughput and latency >>> performance ...and further says that the first step to get there is to disable irqbalance (where they give the instructions to disable the service) and how to go through irq configuration from there. Applications vendors, which we have in our repo's, such as Vlave Steam and CpuFrq, currently recommend removing irqbalance, if installed. RE: https://github.com/ValveSoftware/Proton/issues/3243 http://konkor.github.io/cpufreq/faq/ Additional to the blog article linked to in the last comment above, I found this blog (https://blogs.oracle.com/linux/post/irqbalance-design-and-internals), that goes into how it makes decisions in load balancing and is best summed up in it's conclusion: >>> This article described the internals of the irqbalance daemon. The >>> information provided >>> here can be used to debug and better understand load balance decisions >>> taken by irqbalance. The question I have is, if Ubuntu is Debian Branch, and we long ago went from having different kernels for desktop & server in ubuntu-base, but do have ubuntu-server packages and ubuntu-desktop packages, where things could be different, why is this still a broad sweep as a default install? I am happy that this is getting discussed properly now so that we can relook at this ad what it means to us today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 2046639] [NEW] qt DialogMirror.py argument 1 has unexpected type 'float' while selecting best mirror
Public bug reported:
While selecting the best mirror in software-properties-qt, there's a
traceback:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py",
line 227, in on_report_progress
self.dialog.setValue(frac*100)
TypeError: setValue(self, progress: int): argument 1 has unexpected type 'float'
I didn't investigate thoroughly, but it looks like maybe someone updated
how progress was being updated but didn't check types or test all the
way through before releasing. It can be fixed with a simple patch:
diff --git a/softwareproperties/qt/DialogMirror.py
b/softwareproperties/qt/DialogMirror.py
index 972c4fb..4d1c150 100644
--- a/softwareproperties/qt/DialogMirror.py
+++ b/softwareproperties/qt/DialogMirror.py
@@ -223,7 +223,7 @@ class DialogMirror(QDialog):
def on_report_progress(self, current, max, borders=(0,1), mod=(0,0)):
#self.dialog.setLabelText(_("Completed %s of %s tests") % \
# (current + mod[0], max + mod[1]))
- frac = borders[0] + (borders[1] - borders[0]) / max * current
+ frac = int(borders[0] + (borders[1] - borders[0]) / max * current)
self.dialog.setValue(frac*100)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 23.10
Release:23.10
Codename: mantic
$ apt-cache policy pkgname software-properties-qt
software-properties-qt:
Installed: 0.99.39
Candidate: 0.99.39
Version table:
*** 0.99.39 500
500 https://mirror.it.ubc.ca/ubuntu mantic/universe amd64 Packages
100 /var/lib/dpkg/status
N: Unable to locate package pkgname
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "patch to cast float to int for progress dialog"
https://bugs.launchpad.net/bugs/2046639/+attachment/5729851/+files/qt_DialogMirror_unexpected_float.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2046639
Title:
qt DialogMirror.py argument 1 has unexpected type 'float' while
selecting best mirror
Status in software-properties package in Ubuntu:
New
Bug description:
While selecting the best mirror in software-properties-qt, there's a
traceback:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line
227, in on_report_progress
self.dialog.setValue(frac*100)
TypeError: setValue(self, progress: int): argument 1 has unexpected type
'float'
I didn't investigate thoroughly, but it looks like maybe someone
updated how progress was being updated but didn't check types or test
all the way through before releasing. It can be fixed with a simple
patch:
diff --git a/softwareproperties/qt/DialogMirror.py
b/softwareproperties/qt/DialogMirror.py
index 972c4fb..4d1c150 100644
--- a/softwareproperties/qt/DialogMirror.py
+++ b/softwareproperties/qt/DialogMirror.py
@@ -223,7 +223,7 @@ class DialogMirror(QDialog):
def on_report_progress(self, current, max, borders=(0,1), mod=(0,0)):
#self.dialog.setLabelText(_("Completed %s of %s tests") % \
# (current + mod[0], max + mod[1]))
- frac = borders[0] + (borders[1] - borders[0]) / max * current
+ frac = int(borders[0] + (borders[1] - borders[0]) / max * current)
self.dialog.setValue(frac*100)
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.10
Release: 23.10
Codename: mantic
$ apt-cache policy pkgname software-properties-qt
software-properties-qt:
Installed: 0.99.39
Candidate: 0.99.39
Version table:
*** 0.99.39 500
500 https://mirror.it.ubc.ca/ubuntu mantic/universe amd64 Packages
100 /var/lib/dpkg/status
N: Unable to locate package pkgname
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2046639/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
In the kernel 5.15.x and up the modem X5 is working in the MBIM mode, so the updated udev script attached. ** Attachment added: "99-hp-lt4120-test.rules" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5715918/+files/99-hp-lt4120-test.rules -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 2041737] [NEW] apport-collect permission error on retrieving boot.log
Public bug reported:
RE: Bug Report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2041736
While reviewing this Bug Report, to add a comment to help explain something for
this user, i noticed this error from apport collect:
...
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
...
This file is needed by Launchpad for diagnostics.
Just this week, I helped a Forum user review his boot.log files, so I am
familiar with this. The permissions and ownership of the boot.log.X files are
currently:
mafoelffen@Mikes-B460M:~$ ls -l /var/log/boot*
-rw--- 1 root root 0 Oct 16 00:00 /var/log/boot.log
-rw--- 1 root root 101106 Oct 16 00:00 /var/log/boot.log.1
-rw--- 1 root root 50432 Oct 14 00:00 /var/log/boot.log.2
-rw--- 1 root root 201696 Oct 12 00:00 /var/log/boot.log.3
-rw--- 1 root root 50375 Oct 10 00:00 /var/log/boot.log.4
-rw--- 1 root root 50497 Oct 9 00:00 /var/log/boot.log.5
-rw--- 1 root root 1598 Sep 29 00:00 /var/log/boot.log.6
-rw--- 1 root root 26496 Sep 28 19:10 /var/log/boot.log.7
-rw-r--r-- 1 root root 108494 Apr 19 2022 /var/log/bootstrap.log
...
Which means the 'root' is only user that can open or view them.
Examples:
...
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ awk 'NR>3{exit} {print $0}'
/var/log/boot.log
awk: fatal: cannot open file `/var/log/boot.log' for reading: Permission denied
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ sudo awk 'NR>3{exit} {print $0}'
/var/log/boot.log
Sat Jul 22 00:27:04 PDT 2023
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password R…s to Plymouth Directory Watch.
...
That is why I think apport-collect is getting permissions errors and
failing to retrieve the user boot.log for upload.
Expected behavior:
apport-collect should upload the boot.log successfully.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon
znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Oct 28 20:44:58 2023
InstallationDate: Installed on 2021-09-23 (765 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to jammy on 2022-08-17 (438 days ago)
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2041737
Title:
apport-collect permission error on retrieving boot.log
Status in apport package in Ubuntu:
New
Bug description:
RE: Bug Report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2041736
While reviewing this Bug Report, to add a comment to help explain something
for this user, i noticed this error from apport collect:
...
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
...
This file is needed by Launchpad for diagnostics.
Just this week, I helped a Forum user review his boot.log files, so I am
familiar with this. The permissions and ownership of the boot.log.X files are
currently:
mafoelffen@Mikes-B460M:~$ ls -l /var/log/boot*
-rw--- 1 root root 0 Oct 16 00:00 /var/log/boot.log
-rw--- 1 root root 101106 Oct 16 00:00 /var/log/boot.log.1
-rw--- 1 root root 50432 Oct 14 00:00 /var/log/boot.log.2
-rw--- 1 root root 201696 Oct 12 00:00 /var/log/boot.log.3
-rw--- 1 root root 50375 Oct 10 00:00 /var/log/boot.log.4
-rw--- 1 root root 50497 Oct 9 00:00 /var/log/boot.log.5
-rw--- 1 root root 1598 Sep 29 00:00 /var/log/boot.log.6
-rw--- 1 root root 26496 Sep 28 19:10 /var/log/boot.log.7
-rw-r--r-- 1 root root 108494 Apr 19 2022 /var/log/bootstrap.log
...
Which means the 'root' is only user that can open or view them.
Examples:
...
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ awk 'NR>3{exit} {print $0}'
/var/log/boot.log
awk: fatal: cannot open file `/var/log/boot.log' for reading: Permission
denied
mafoelffen@Mikes-ThinkPad-T520:~/Downloads$ sudo awk 'NR>3{exit} {print $0}'
/var/log/boot.log
Sat Jul 22 00:27:04 PDT 2023
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password R…s to Plymouth Directory Watch.
...
That is why I think apport-collect is getting permissions errors and
failing to retrieve the user boot.log for upload.
Expected behavior:
apport-collect should upload the boot.log successfully.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux
[Touch-packages] [Bug 2039592] Re: no connection via SIM card
I had been helping this user on Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2491572 "English" is not this user's primary language, so let me help him explain this here. This worked for him in 20.04. It is not working since he upgraded to 22.04. For some unknown reason, lshw -C Network is not producing expected results on that device, so not a lot of human-friendly readable information is being shown. His system sees his WWAN card as you can see in his attached WifiSyslog.txt: жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: new high-speed USB device number 4 using xhci_hcd жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device found, idVendor=03f0, idProduct=521d, bcdDevice= 0.01 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device strings: Mfr=5, Product=4, SerialNumber=0 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Product: HP hs3110 HSPA+ Mobile Broadband Device жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Manufacturer: Hewlett-Packard What isn't showing up there in that log, is anything about a driver being attached to that device. In the attached RfKill.txt, that device does not even show up in the list. But his syslogs say this: Code:13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3159] manager: rfkill: WWAN hardware radio set enabled 12:37:51 NetworkManager: [1696757871.8350] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file 12:37:51 NetworkManager: [1696757871.8190] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) 12:37:51 NetworkManager: [1696757871.8124] manager[0x55e016153040]: rfkill: WWAN hardware radio set disabled So rfkill is seeing it and addressing it, the NNWwanFactory module is being loaded, but the device is not being left as enabled... That is what I know about it. Is anyone going to triage this soon? It has been 5 days now... When I refer a user to file a bug report, it's because I have faith that when I do, it's the correct thing to do for the improvement of Ubuntu, that something is wrong, it is not working as expected, that can possibly be corrected. -- 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/2039592 Title: no connection via SIM card Status in network-manager package in Ubuntu: New Bug description: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started
[Touch-packages] [Bug 2039592] Re: no connection via SIM card
I had been helping this user on Ubuntu Forums: https://ubuntuforums.org/showthread.php?t=2491572 "English" is not this user's primary language, so let me help him explain this here. This worked for him in 20.04. It is not working since he upgraded to 22.04. For some unknown reason, lshw -C Network is not producing expected results on that device, so not a lot of human-friendly readable information is being shown. His system sees his WWAN card as you can see in his attached WifiSyslog.txt: жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: new high-speed USB device number 4 using xhci_hcd жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device found, idVendor=03f0, idProduct=521d, bcdDevice= 0.01 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: New USB device strings: Mfr=5, Product=4, SerialNumber=0 жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Product: HP hs3110 HSPA+ Mobile Broadband Device жов 17 19:36:29 denis-HP-EliteBook-840-G1 kernel: usb 2-6: Manufacturer: Hewlett-Packard What isn't showing up there in that log, is anything about a driver being attached to that device. In the attached RfKill.txt, that device does not even show up in the list. But his syslogs say this: Code:13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3166] audit: op="radio-control" arg="wwan-enabledn" pid=2374 uid=1000 result="success" 13:26:44 NetworkManager: [1696760804.3159] manager: rfkill: WWAN hardware radio set enabled 12:37:51 NetworkManager: [1696757871.8350] manager: rfkill: WWAN enabled by radio killswitch; disabled by state file 12:37:51 NetworkManager: [1696757871.8190] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) 12:37:51 NetworkManager: [1696757871.8124] manager[0x55e016153040]: rfkill: WWAN hardware radio set disabled So rfkill is seeing it and addressing it, the NNWwanFactory module is being loaded, but the device is not being left as enabled... That is what I know about it. Is anyone going to triage this soon? It has been 5 days now... When I refer a user to file a bug report, it's because I have faith that when I do, it's the correct thing to do for the improvement of Ubuntu, that something is wrong, it is not working as expected, that can possibly be corrected. -- 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/2039592 Title: no connection via SIM card Status in network-manager package in Ubuntu: New Bug description: Ubuntu 22.04 I can’t connect to the Internet via a SIM card. I can see how the Measurement Manager is being developed and the plugin is installed.. I'll add a module: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so) manager: rfkill: WWAN is jammed with radio; I'll become a file. the driver does not load!!! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager 1.36.6-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 19:40:10 2023 InstallationDate: Installed on 2023-10-03 (13 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) IpRoute: default via 192.168.43.63 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlo1 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/3 ONEPLUS_A5000_co_aptsvo 174d782e-8952-4921-b779-adbd0266fe27 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s25 ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.6 connected started
[Touch-packages] [Bug 2038857] Re: Mantic Daily Text Editor Crashed Xorg
Note: When I was looking for changed/modified files, that was related
to:
https://answers.launchpad.net/ubuntu/+source/subiquity/+question/708132,
which is still unanswered...
--
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/2038857
Title:
Mantic Daily Text Editor Crashed Xorg
Status in xorg package in Ubuntu:
New
Bug description:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and
had no way to navigate to folders... Selected menu in top bar of
editor... Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer
restarted. Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:58:20 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid,
480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2038857/+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 2038857] [NEW] Mantic Daily Text Editor Crashed Xorg
Public bug reported:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and had
no way to navigate to folders... Selected menu in top bar of editor...
Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer restarted.
Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 17:58:20 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 05) (prog-if 00
[VGA controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz
layerfs-path=minimal.standard.live.squashfs --- quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/06/2015
dmi.bios.release: 0.0
dmi.bios.vendor: EFI Development Kit II / OVMF
dmi.bios.version: 0.0.0
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-6.2
dmi.modalias:
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-6.2
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic 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/2038857
Title:
Mantic Daily Text Editor Crashed Xorg
Status in xorg package in Ubuntu:
New
Bug description:
In testing Mantic Daily ISO. Dl'ed today and updated to current git in
installer. After selecting "Erase All and Install Ubuntu: Experimental
ZFS > Next... Jumped out to system and started gnome-terminal.
Created file of all modified files within the last 5 minutes. Opened
Text Editor > Open... Text editor could not see any recent files and
had no way to navigate to folders... Selected menu in top bar of
editor... Scree when blank, then to lock-screen.
On getting back through lockscreen, ubuntu-desktop-installer
restarted. Went to "try". apport said that Xorg had crashed.
On choosing report bug, apport crashed. Submitted report via 'ubuntu-
bug'.
Here we are.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform:
[Touch-packages] [Bug 2024320] Re: systemd-resolved: returns SERVFAIL for uknown domain
Upstream has closed the issue, but I think they have misunderstood the
bug report.
The problem is that contrary to standard resolvers, systemd-resolved is
returning SERVFAIL for this case instead of NXDOMAIN.
Nobody is asking for the query to be forwarded, only for the response
code to be right.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2024320
Title:
systemd-resolved: returns SERVFAIL for uknown domain
Status in systemd:
Unknown
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Ubuntu 22.04.2 amd64
systemd: 249.11-0ubuntu3.9
when I ask for non-existing domain, systemd-resolved replies with
SERVFAIL. I believe that correct answer should be NXDOMAIN (this is
reply from public DNS servers, like 1.1.1.1, 8.8.8.8, 9.9.9.9 and
others).
DEMO, I use `khost` utility from package `knot-host`:
CloudFlare DNS, reference, I believe this is expected answer:
$ khost oops. 1.1.1.1
Host oops. type A error: NXDOMAIN
Host oops. type error: NXDOMAIN
Host oops. type MX error: NXDOMAIN
systemd-resolved, the bug (and the reply is not consistent, MX record
has different error):
$ khost oops.
Host oops. type A error: SERVFAIL
Host oops. type error: SERVFAIL
Host oops. type MX error: NXDOMAIN
$ khost -v oops.
;; ->>HEADER<<- opcode: QUERY; status: SERVFAIL; id: 15468
;; Flags: qr aa rd ra; QUERY: 1; ANSWER: 0; AUTHORITY: 0; ADDITIONAL: 0
;;oops. IN A
;; Received 22 B
;; Time 2023-06-18 18:27:02 UTC
;; From 127.0.0.53@53(UDP) in 0.0 ms
;; ->>HEADER<<- opcode: QUERY; status: SERVFAIL; id: 55107
;; Flags: qr aa rd ra; QUERY: 1; ANSWER: 0; AUTHORITY: 0; ADDITIONAL: 0
;;oops. IN
;; Received 22 B
;; Time 2023-06-18 18:27:02 UTC
;; From 127.0.0.53@53(UDP) in 0.0 ms
;; ->>HEADER<<- opcode: QUERY; status: NXDOMAIN; id: 46585
;; Flags: qr rd ra; QUERY: 1; ANSWER: 0; AUTHORITY: 1; ADDITIONAL: 0
;;oops. IN MX
. 1390IN SOA a.root-servers.net.
nstld.verisign-grs.com. 2023061800 1800 900 604800 86400
;; Received 97 B
;; Time 2023-06-18 18:27:02 UTC
;; From 127.0.0.53@53(UDP) in 3.4 ms
Check that DNS is served by systemd-resolved:
$ sudo ss -nlp | grep ":53 "
udp UNCONN 0 0 127.0.0.53%lo:53
0.0.0.0:*users:(("systemd-resolve",pid=586,fd=13))
tcp LISTEN 0 4096127.0.0.53%lo:53
0.0.0.0:*users:(("systemd-resolve",pid=586,fd=14))
Check version
$ resolvectl --version
systemd 249 (249.11-0ubuntu3.9)
+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL
+ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP
+LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD
-XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/2024320/+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 2028170] Re: curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt-name
Talking to Wordpress and they think I might have a different issue. If that's not it I'll come back. Sorry about the confusion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2028170 Title: curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt- name Status in curl package in Ubuntu: Invalid Status in curl source package in Focal: Invalid Status in curl source package in Jammy: Fix Released Status in curl source package in Kinetic: Invalid Status in curl source package in Lunar: Invalid Status in curl source package in Mantic: Invalid Bug description: With the latest curl 7.81.0-1ubuntu1.11 on ubuntu 22.04, I'm getting the following: curl -v https://raw.githubusercontent.com * Trying 185.199.108.133:443... * Connected to raw.githubusercontent.com (185.199.108.133) port 443 (#0) [...] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.github.io * start date: Feb 21 00:00:00 2023 GMT * expire date: Mar 20 23:59:59 2024 GMT * subjectAltName does not match raw.githubusercontent.com * SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' curl: (60) SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. -- The alt name looks proper when looking at the cert w/ s_client: openssl s_client -connect raw.githubusercontent.com:443 /dev/null | openssl x509 -noout -text X509v3 Subject Alternative Name: DNS:*.github.io, DNS:github.io, DNS:*.github.com, DNS:github.com, DNS:www.github.com, DNS:*.githubusercontent.com, DNS:githubusercontent.com Previous versions of curl work as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028170/+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 2028170] Re: curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt-name
Is this fixed for all use cases? I have the 7.81.0-1ubuntu1.13 versions and I'm still getting "no alternative certificate subject name matches target host name" messages for Wordpress beta updates and with a couple of other curl scripts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/2028170 Title: curl 7.81.0-1ubuntu1.11 fails verifying proper ssl cert w/ subj-alt- name Status in curl package in Ubuntu: Invalid Status in curl source package in Focal: Invalid Status in curl source package in Jammy: Fix Released Status in curl source package in Kinetic: Invalid Status in curl source package in Lunar: Invalid Status in curl source package in Mantic: Invalid Bug description: With the latest curl 7.81.0-1ubuntu1.11 on ubuntu 22.04, I'm getting the following: curl -v https://raw.githubusercontent.com * Trying 185.199.108.133:443... * Connected to raw.githubusercontent.com (185.199.108.133) port 443 (#0) [...] * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: C=US; ST=California; L=San Francisco; O=GitHub, Inc.; CN=*.github.io * start date: Feb 21 00:00:00 2023 GMT * expire date: Mar 20 23:59:59 2024 GMT * subjectAltName does not match raw.githubusercontent.com * SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' curl: (60) SSL: no alternative certificate subject name matches target host name 'raw.githubusercontent.com' More details here: https://curl.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. To learn more about this situation and how to fix it, please visit the web page mentioned above. -- The alt name looks proper when looking at the cert w/ s_client: openssl s_client -connect raw.githubusercontent.com:443 /dev/null | openssl x509 -noout -text X509v3 Subject Alternative Name: DNS:*.github.io, DNS:github.io, DNS:*.github.com, DNS:github.com, DNS:www.github.com, DNS:*.githubusercontent.com, DNS:githubusercontent.com Previous versions of curl work as intended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2028170/+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 2025965] Re: aptsources deb822 Section constructor fails on valid .sources file
Also, if it helps, here's a minimal example python file, triggering the error (requires attached `00ubuntu.sources` to be in cwd) ** Attachment added: "Minimal example of error (requires other attached `00ubuntu.sources` file)" https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2025965/+attachment/5683961/+files/cnf-debug.py ** Also affects: command-not-found (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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 2025965] Re: aptsources deb822 Section constructor fails on valid .sources file
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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 2025965] [NEW] aptsources deb822 Section constructor fails on valid .sources file
Public bug reported: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The .sources file causing this error." https://bugs.launchpad.net/bugs/2025965/+attachment/5683960/+files/00ubuntu.sources -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/2025965 Title: aptsources deb822 Section constructor fails on valid .sources file Status in command-not-found package in Ubuntu: New Status in python-apt package in Ubuntu: New Bug description: When attempting to parse (what I believe is) a perfectly valid deb822-formated `.sources` file, the library's `_deb822.Section` constructor parses my file incorrectly, resulting in an exception being thrown. At a low level, the error is `ValueError: Unable to parse section data` and is thrown in the `_deb822.Section` constructor, located at line 41 of `aptsources/_deb822.py`. The error was caused by the evaluation of `apt_pkg.TagSection(trimmed_section)` on that line with `trimmed_section` being an empty string. At a high level, based on a cursory debug, it seems the parser incorrectly considers the first three lines of my `.sources` file -- which are, in fact, comments -- to be a stanza, and is trying to instantiate an object for them, despite them having no non-ignored content. Notably, -- supporting my conclusion -- this issue disappears entirely if I remove the first blank line in the file (located after those comments and before the first stanza). I am attaching my .sources file for reference. Notes: - FWIW, I don't use this library directly; the code at issue gets invoked by the `command-not-found` package/bash handler. (The warnings therefore show up every time I mistype a command.) In any case, I traced the issue down to this package. - My python3-apt package is version 2.5.3ubuntu1 from lunar/main. - This error began for me upon an upgrade from jammy to lunar. This sources file was unchanged during the upgrade (except for renaming `jammy` to `lunar`, and changing `Enabled` to `no` in the `partner` stanza). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/2025965/+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 2023289] [NEW] System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04
Public bug reported: I'm trying to launch Qt5 project with QML UI with .mesh 3D objects. This project works normally on old, grand-daddy's laptop Asus X555D, with Radeon R6 M340DX 2GB graphics, 8GB RAM and AMD A10 6th gen. But when i try to launch this project on the same Ubuntu version, on my other laptop (it's specs are listed below), i have absolute blacked out window instead of application and system freeze for about 1 minute with project (sometimes even QTCreator) crash. Here is my troubled Asus's specs: Laptop: ASUSTeK VivoBook 15 X513EAN_K513EA Graphics: Mesa Intel® Xe Graphics (TGL GT2) CPU: 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz × 8 RAM: 16,0 GB OS: Ubuntu 22.04.2 LTS, 64 bit Gnome: 42.5 Display server: x11 OpenGl ver: 4.6 (Compatibility Profile) Mesa 22.2.5 I've tried to update xinerama's libs, checked missing libs, tried to update OpenGL, tried this method but for 22.04 and, to be honest, i've lost the count of solutions that i've tried. I will be grateful for any help with information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-1013.13-oem 6.1.25 Uname: Linux 6.1.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 8 14:49:52 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TigerLake-LP GT2 [Iris Xe Graphics] [1043:1c22] InstallationDate: Installed on 2023-04-19 (50 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:30d4 Quanta Computer, Inc. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 09da:2403 A4Tech Co., Ltd. 2.4G Device Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1013-oem root=UUID=9fdae802-1912-4c11-b382-7a593209ef38 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: X513EAN.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513EAN 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:bvnAmericanMegatrendsInternational,LLC.:bvrX513EAN.302:bd04/21/2022:br5.19:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513EAN_K513EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513EAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513EAN_K513EA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.115+git2305120500.98e1db~oibaf~j version.libgl1-mesa-dri: libgl1-mesa-dri 23.2~git2306080600.96cf45~oibaf~j version.libgl1-mesa-glx: libgl1-mesa-glx 23.2~git2306080600.96cf45~oibaf~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages 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/2023289 Title: System permanent freeze via running Qt5 QML + .mesh project on Ubuntu 22.04 Status in xorg package in Ubuntu: New Bug description: I'm trying to launch Qt5 project with QML UI with .mesh 3D objects. This project works normally on old, grand-daddy's laptop Asus X555D, with Radeon R6 M340DX 2GB graphics, 8GB RAM and AMD A10 6th gen. But when i try to launch this project on the same Ubuntu version, on my other laptop (it's specs are listed below), i have absolute blacked out window instead of application and system freeze for about 1 minute with project (sometimes even QTCreator) crash. Here is my troubled Asus's specs: Laptop: ASUSTeK VivoBook 15 X513EAN_K513EA
[Touch-packages] [Bug 2022916] [NEW] gdbusconnection: Explicitly destroy an idle source on cleanup
Public bug reported: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022916 Title: gdbusconnection: Explicitly destroy an idle source on cleanup Status in glib2.0 package in Ubuntu: New Bug description: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2022916/+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 2022916] Re: gdbusconnection: Explicitly destroy an idle source on cleanup
See UT issue discussion here: https://gitlab.com/ubports/development/core/lomiri-app- launch/-/merge_requests/49 ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022916 Title: gdbusconnection: Explicitly destroy an idle source on cleanup Status in glib2.0 package in Ubuntu: New Bug description: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2022916/+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 972077] Re: apt repository disk format has race conditions
I'm also affected by this (a Hashicorp repo): ``` Get:14 https://apt.releases.hashicorp.com jammy/main i386 Packages [31,3 kB] Err:14 https://apt.releases.hashicorp.com jammy/main i386 Packages File has unexpected size (31295 != 31290). Mirror sync in progress? [IP: 18.173.5.94 443] Hashes of expected file: - Filesize:31290 [weak] - SHA256:a1aba716abdbf9f2e3bc13d25734ff9fcc58a399698795ebc98f7cec76146d2e - SHA1:20e1b9792e678e5223d1387e4e5effaf5a4ca24f [weak] - MD5Sum:647502cff7f79ac8a4641b6519696b30 [weak] Release file created at: Wed, 03 May 2023 21:28:51 + ``` and in the summary: ``` Reading package lists... Done E: Failed to fetch https://apt.releases.hashicorp.com/dists/jammy/main/binary-i386/Packages.bz2 File has unexpected size (31295 != 31290). Mirror sync in progress? [IP: 18.173.5.94 443] Hashes of expected file: - Filesize:31290 [weak] - SHA256:a1aba716abdbf9f2e3bc13d25734ff9fcc58a399698795ebc98f7cec76146d2e - SHA1:20e1b9792e678e5223d1387e4e5effaf5a4ca24f [weak] - MD5Sum:647502cff7f79ac8a4641b6519696b30 [weak] Release file created at: Wed, 03 May 2023 21:28:51 + E: Some index files failed to download. They have been ignored, or old ones used instead. ``` -- 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/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 1982218] Re: wait-online does not correctly identify managed links
Apologies for the late response:
Yes, we have a Ubuntu 22.04 LTS image that we use across a set of
machines, some of which have multiple Ethernet ports, but for which we
only connect a single port. For this image we use the following Netplan
configuration (/etc/netplan/ethernet.yaml):
network:
ethernets:
en:
match:
name: en*
dhcp4: true
version: 2
Which places _all_ Ethernet interfaces under systemd-networkd
management, allowing us to bring up at least one interface via DHCP
without needing to know the exact interface name (which depends on the
exact hardware) and enables us to use any of the available Ethernet
ports on the machine.
As part of this image we also have a boot-time systemd service that
requires functional network connectivity in order to successfully start.
The unit file for this service depends on the network-online target
("Wants=network-online.target"). For example purposes you could replace
this service with a remote NFS mount specified in /etc/fstab, since
boot-time NFS mounts implicitly depend on the network-online target as
well.
The default behavior of systemd-networkd-wait-online is to wait until
all networkd-managed interfaces are routable before the network-online
target is started, but since we only ever connect a single Ethernet
interface to the network, we override its behavior here in our image
(/etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf):
[Service]
ExecStart=
ExecStart=/usr/local/lib/systemd-networkd-wait-online --any --timeout=0
Now, the problem introduced by the UBUNTU-wait-online-exit-if-no-links-
are-managed patch is that it places us in a race against our DHCP
server. During a successful boot, where networkd is able to obtain an
address via DHCP _before_ the wait-online service is reached, networkctl
reports this status:
$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 enp0s1 etherroutableconfigured
3 enp0s2 etherno-carrier configuring
Since the second interface (enp0s1) is in the configured state and is
routable, systemd-networkd-wait-online behaves correctly by exiting
immediately. However, during an unsuccessful boot, where networkd has
yet to obtain an address via DHCP at the time the wait-online service is
reached, networkctl reports this status:
$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 enp0s1 etherdegradedconfiguring
3 enp0s2 etherno-carrier configuring
Here, both of the managed Ethernet interfaces are still in the
configuring state. Since UBUNTU-wait-online-exit-if-no-links-are-
managed doesn't check if managed interfaces are in this state, only
configured, it assumes those links are unmanaged and systemd-networkd-
wait-online also exits immediately. This results in failure of our
network-dependent service to start (or equivalently, failure of the
remote NFS volume to mount).
With the provided patch, systemd-networkd-wait-online identifies two
managed interfaces in the configuring state and waits until at least one
of them becomes routable, and thus waits until the network is functional
before continuing to boot.
I hope this example better illustrates the issue. Thanks!
** Changed in: systemd (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1982218
Title:
wait-online does not correctly identify managed links
Status in systemd package in Ubuntu:
New
Bug description:
Ubuntu's packaging of systemd-networkd-wait-online includes a patch
(UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if
none of the present links are managed by systemd-networkd. However,
the patch fails to identify links in the "configuring" state, which
implies they are managed, but not yet fully online. This undermines
the purpose of systemd-networkd-wait-online with the --any option,
since at the time the systemd-networkd-wait-online service is started,
managed links are _likely_ in a configuring, but-not-yet-configured
state.
Please see the attached patch. Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+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 2007621] [NEW] gio open exits with success even though the underlying exec failed
Public bug reported: This is a sort of annoyingly complex interaction, so bear with me. The observed problem is that xdg-open does not exit with a non-zero exit code when it fails to open. ``` $ unset DISPLAY $ xdg-open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` It turns out to not exactly be xdg-open's fault, though: ``` $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10 + return 0 + open_xfce http://example.com + exo-open --help + gio help open + gio open http://example.com exo-open: Cannot open display: . + [ 0 -eq 0 ] + exit_success + [ 0 -gt 0 ] + exit 0 ``` So, from this we see that xdg-open uses `exo-open --help` to see if exo- open works, but it fails due to the DISPLAY, so it falls back to gio open. gio open ends up turning around and calling exo-open again, but gio swallows the exit code, so xdg-open thinks it worked. ``` $ exo-open http://example.com exo-open: Cannot open display: . $ echo $? 1 $ gio open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` Versions: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ xdg-open --version xdg-open 1.1.3 $ exo-open --version | head -n1 exo-open 4.16.3 $ gio --version 2.72.4 Specifically: exo-utils: Installed: 4.16.3-1 Candidate: 4.16.3-1 Version table: *** 4.16.3-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status libglib2.0-bin: Installed: 2.72.4-0ubuntu1 Candidate: 2.72.4-0ubuntu1 Version table: *** 2.72.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.72.1-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages xdg-utils: Installed: 1.1.3-4.1ubuntu3~22.04.1 Candidate: 1.1.3-4.1ubuntu3~22.04.1 Version table: *** 1.1.3-4.1ubuntu3~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 1.1.3-4.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2007621 Title: gio open exits with success even though the underlying exec failed Status in glib2.0 package in Ubuntu: New Bug description: This is a sort of annoyingly complex interaction, so bear with me. The observed problem is that xdg-open does not exit with a non-zero exit code when it fails to open. ``` $ unset DISPLAY $ xdg-open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` It turns out to not exactly be xdg-open's fault, though: ``` $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10 + return 0 + open_xfce http://example.com + exo-open --help + gio help open + gio open http://example.com exo-open: Cannot open display: . + [ 0 -eq 0 ] + exit_success + [ 0 -gt 0 ] + exit 0 ``` So, from this we see that xdg-open uses `exo-open --help` to see if exo-open works, but it fails due to the DISPLAY, so it falls back to gio open. gio open ends up turning around and calling exo-open again, but gio swallows the exit code, so xdg-open thinks it worked. ``` $ exo-open http://example.com exo-open: Cannot open display: . $ echo $? 1 $ gio open http://example.com exo-open: Cannot open display: . $ echo $? 0 ``` Versions: $ lsb_release -rd Description:Ubuntu 22.04.1 LTS Release:22.04 $ xdg-open --version xdg-open 1.1.3 $ exo-open --version | head -n1 exo-open 4.16.3 $ gio --version 2.72.4 Specifically: exo-utils: Installed: 4.16.3-1 Candidate: 4.16.3-1 Version table: *** 4.16.3-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status libglib2.0-bin: Installed: 2.72.4-0ubuntu1 Candidate: 2.72.4-0ubuntu1 Version table: *** 2.72.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 2.72.1-1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages xdg-utils: Installed: 1.1.3-4.1ubuntu3~22.04.1 Candidate: 1.1.3-4.1ubuntu3~22.04.1 Version table: *** 1.1.3-4.1ubuntu3~22.04.1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status
[Touch-packages] [Bug 2006078] [NEW] [WH-1000XM4, playback] Sound is distorted
Public bug reported: The bluetooth drivers that come with Ubuntu have very poor audio quality which are not suitable for playing music. Apparently thousands of people on stackoverflow have the exact same problem: https://askubuntu.com/questions/676853/bluetooth-headset-with-poor-sound-quality-on-ubuntu A2DP was not an option for the WH-1000XM4 bluetooth headphones, so the first upvoted answer should absolutely be the default for people who have A2DP - but that won't fix this exact ticket. Sony devices and other high end Bluetooth audio devices would greatly benefit from having pulse audio installed and enabled by default: https://askubuntu.com/a/1100224 -> https://tutorials.technology/tutorials/Bluetooth-headset-playing-low-quality-on-ubuntu-18.html If `pulseaudio pulseaudio-utils pavucontrol pulseaudio-module-bluetooth` packages are added to the default desktop and A2DP is enabled then the average desktop user will be happy with wonderful crisp audio in line with osx and windows. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mike 1691 F pulseaudio /dev/snd/controlC0: mike 1691 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Pantheon Date: Sun Feb 5 20:55:26 2023 InstallationDate: Installed on 2023-02-04 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM4 Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [WH-1000XM4, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2607 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2607:bd08/14/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2006078 Title: [WH-1000XM4, playback] Sound is distorted Status in pulseaudio package in Ubuntu: New Bug description: The bluetooth drivers that come with Ubuntu have very poor audio quality which are not suitable for playing music. Apparently thousands of people on stackoverflow have the exact same problem: https://askubuntu.com/questions/676853/bluetooth-headset-with-poor-sound-quality-on-ubuntu A2DP was not an option for the WH-1000XM4 bluetooth headphones, so the first upvoted answer should absolutely be the default for people who have A2DP - but that won't fix this exact ticket. Sony devices and other high end Bluetooth audio devices would greatly benefit from having pulse audio installed and enabled by default: https://askubuntu.com/a/1100224 -> https://tutorials.technology/tutorials/Bluetooth-headset-playing-low-quality-on-ubuntu-18.html If `pulseaudio pulseaudio-utils pavucontrol pulseaudio-module-bluetooth` packages are added to the default desktop and A2DP is enabled then the average desktop user will be happy with wonderful crisp audio in line with osx and windows. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mike 1691 F pulseaudio /dev/snd/controlC0: mike 1691 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Pantheon Date: Sun Feb 5 20:55:26 2023 InstallationDate: Installed on 2023-02-04 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM4 Symptom_Type: Digital clip
[Touch-packages] [Bug 1981623] Re: Save As Dialog Box does not allow filename change
Is there any work around for this? Other than not using MATE desktop.
It's driving me crazy.
--
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/1981623
Title:
Save As Dialog Box does not allow filename change
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
as expected, but do not permit changing the filename. Text entry
triggers the find function as opposed to file rename.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1981623/+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 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)
my 5 cents: ``` # apt list --upgradable Listing... Done ubuntu-wallpapers-kinetic/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1] ubuntu-wallpapers/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1] ``` -- 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/193 Title: The following packages have been kept back (ubuntu-wallpapers) Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu version: 22.10 Version of the packages: ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate: 22.10.2ubuntu1-0ubuntu1 What is expected to happen: upgrade packages via apt-get upgrade. What happened instead: packages not upgrading, with a message saying "the following packages have been kept back: ubuntu-wallpapers ubuntu- wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu- wallpapers-kinetic or other workarounds don't work as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/193/+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 1915910] Re: evince does not print (apparmor, pxgsettings)
The proposed packages evince and evince-common versions 42.3-0ubuntu3 from jammy-proposed fixes the problem for me on MATE 22.04. Much obliged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1915910 Title: evince does not print (apparmor, pxgsettings) Status in evince package in Ubuntu: Fix Released Status in libproxy package in Ubuntu: Invalid Status in evince source package in Jammy: Fix Committed Status in evince source package in Kinetic: Fix Committed Status in evince package in Debian: New Bug description: * Impact Evince hangs when opening the printing dialog for some users with a remote printer configured and connected * Test case - configure a remote printer and turn it on - open a pdf - try to print the document the print dialog shouldn't freeze the viewer * What could go wrong The change is only allowing access to one extra system binary from the apparmor profile so shouldn't really have an impact on the software behaviour. If the syntax or content of the change was incorrect it could make the apparmor profile not been loaded anymore or block access to thing that should be allowed, so ensure that opening documents, printing and thumbnailing are still working -- audit: type=1400 audit(1613557537.646:81): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500 comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 It seems that evince has no rights to print if I understand this correctly Printing the same pdf-file from the same origin/folder works with OCULAR The error is reproduceable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1915910/+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 1919185] Re: Bash completion breaks the content of $_ variable
This bug can lead to data loss: $ echo aaa > aaa $ echo bbb > bbb $ mkdir tmp $ mv a $_ $ mv b $_ Now the directory tmp is empty and there is bbb has been renamed _filedir. The file aaa is nowhere to be found. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1919185 Title: Bash completion breaks the content of $_ variable Status in bash package in Ubuntu: Confirmed Bug description: In bash, the $_ variable ought to contain the last parameter of previous command. For example: $ touch aaa bbb $ cat aaa $ cat bbb $_ the last line is equivalent to "cat bbb aaa". However, if I use bash completion to fill some other parameter like this: $ cat bb $_ (where denotes hitting the TAB key), the value of the $_ variable is overwritten with some mess, so that the result is: "cat: _filedir: No such file or directory" I expect this variable not to be overwritten and still contain the value "aaa", co that the command prints out the files bbb and aaa. This bug seems to be version-wide and usage-wide. I encounter this for many Ubuntu releases, for example, using Kubuntu 20.10. It can be reproduced even in terminal with no Xorg running. The resulting error message differs according to what is being TAB-completed, for example with git command it says: "error: pathspec '__git_main' did not match any file(s) known to git". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1919185/+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 1995097] [NEW] systemd
Public bug reported: Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: systemd systemd-timesyncd libpam-systemd:amd64 systemd-oomd snapd systemd-sysv libnss-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1995097 Title: systemd Status in systemd package in Ubuntu: New Bug description: Processing triggers for libc-bin (2.35-0ubuntu3.1) ... Errors were encountered while processing: systemd systemd-timesyncd libpam-systemd:amd64 systemd-oomd snapd systemd-sysv libnss-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1995097/+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 1988563] Re: package libudev-dev dependency conflict
Just to confirm Justas' fix in comment #4 temporarily works around the issue for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1988563 Title: package libudev-dev dependency conflict Status in systemd package in Ubuntu: Confirmed Bug description: I am not sure if this is the right place to file this, but we are getting the following error when installing libudev-dev on bionic Installing libudev-dev fails for bionic with the following error: ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed E: Unable to correct problems, you have held broken packages. ``` Steps to reproduce: ``` docker run -it --rm ubuntu:bionic apt update apt install libudev-dev ``` Complete log: ``` ~$ docker run -it --rm ubuntu:bionic Unable to find image 'ubuntu:bionic' locally bionic: Pulling from library/ubuntu dad0f37c70a6: Pull complete Digest: sha256:3aa2ccb021969aadb28381fee1b247422e845b176e241cd1540c4b6831e000bb Status: Downloaded newer image for ubuntu:bionic root@391196612b51:/# apt update Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://security.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [1114 kB] Get:4 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [22.8 kB] Get:5 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [2953 kB] Get:6 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [1540 kB] Get:7 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:8 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:9 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB] Get:10 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB] Get:11 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1344 kB] Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [29.9 kB] Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [1162 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [2318 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [3390 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [12.9 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic-backports/main amd64 Packages [12.2 kB] Fetched 25.9 MB in 2s (10.4 MB/s) Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@391196612b51:/# apt install libudev-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libudev-dev : Depends: libudev1 (= 237-3ubuntu10.53) but 237-3ubuntu10.54 is to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988563/+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 1982218] [NEW] wait-online does not correctly identify managed links
Public bug reported: Ubuntu's packaging of systemd-networkd-wait-online includes a patch (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if none of the present links are managed by systemd-networkd. However, the patch fails to identify links in the "configuring" state, which implies they are managed, but not yet fully online. This undermines the purpose of systemd-networkd-wait-online with the --any option, since at the time the systemd-networkd-wait-online service is started, managed links are _likely_ in a configuring, but-not-yet-configured state. Please see the attached patch. Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-wait-online-Check-if-links-are-in-the-configuring-st.patch" https://bugs.launchpad.net/bugs/1982218/+attachment/5604130/+files/0001-wait-online-Check-if-links-are-in-the-configuring-st.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1982218 Title: wait-online does not correctly identify managed links Status in systemd package in Ubuntu: New Bug description: Ubuntu's packaging of systemd-networkd-wait-online includes a patch (UBUNTU-wait-online-exit-if-no-links-are-managed) intended to exit if none of the present links are managed by systemd-networkd. However, the patch fails to identify links in the "configuring" state, which implies they are managed, but not yet fully online. This undermines the purpose of systemd-networkd-wait-online with the --any option, since at the time the systemd-networkd-wait-online service is started, managed links are _likely_ in a configuring, but-not-yet-configured state. Please see the attached patch. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
This is not a NetworkManager problem. It is also reported by me in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385 and it is probably kernel bug. The problem is described by ModemManager's developer in our discussion: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/463#note_1157289 as a broken USB communication. According to diagnosis from kernel 5.1x the qmi_wwan module resets modem firmware in endless loop: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/463#note_1157919 although it was worked flawlessly earlier in kernel 5.8.x The workaround is to use udev script for a modem to switch it to the MBIM mode which works ok under ModemManager & NetworkManager. Reboot. Recreate connection profile for modem in Network Manager Mobile Broadband Settings for your GSM Network Provider to make it binded with new MBiM devid config. Tested on kernels 5.8, 5,11, 5.13. Place the attached udev script file in: /etc/udev/rules.d instead of any old one. It uses usb_modeswitch to do the "magic" correctly. ** Attachment removed: "Udev script for switching modem" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5541060/+files/99-hp-lt4120.rules ** Attachment added: "udev script for modem" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5541062/+files/99-hp-lt4120.rules -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
This is not a NetworkManager problem. It is also reported by me in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950385 and it is probably kernel bug. The problem is described by ModemManager's developer in our discussion: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/463#note_1157289 as a broken USB communication. According to diagnosis from kernel 5.1x the qmi_wwan module resets modem firmware in endless loop: https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/463#note_1157919 although it was worked flawlessly earlier in kernel 5.8.x The workaround is to use udev script for a modem to switch it to the MBIM mode which works ok under ModemManager & NetworkManager. Tested on kernels 5.8, 5,11, 5.13. Place the attached config file in: /etc/udev/rules.d instead of any old one. It uses usb_modeswitch to do the "magic" correctly. ** Bug watch added: gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues #463 https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues/463 ** Attachment added: "Udev script for switching modem" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5541060/+files/99-hp-lt4120.rules -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1939504] [NEW] HAS A TENDASE TO DROP LETTERS WHEN TYPING
Public bug reported: WHEN TYPING ORE OPENING PROGRAM ITS SOME TIMES DROPS LETTERS ORE FLICKERS ON A PROGRAM ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 11 13:35:36 2021 DistUpgraded: 2021-06-08 13:49:04,305 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] InstallationDate: Installed on 2017-03-25 (1599 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=df7102e4-c436-4f79-8d84-04a48f05c02e ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to hirsute on 2021-06-08 (63 days ago) dmi.bios.date: 12/24/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: B75 Pro3-M 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:bd12/24/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB75Pro3-M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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 xserver.bootTime: Sat Apr 6 15:04:58 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages 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/1939504 Title: HAS A TENDASE TO DROP LETTERS WHEN TYPING Status in xorg package in Ubuntu: New Bug description: WHEN TYPING ORE OPENING PROGRAM ITS SOME TIMES DROPS LETTERS ORE FLICKERS ON A PROGRAM ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 11 13:35:36 2021 DistUpgraded: 2021-06-08 13:49:04,305 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102] InstallationDate: Installed on 2017-03-25 (1599 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=df7102e4-c436-4f79-8d84-04a48f05c02e ro drm.debug=0xe plymouth:debug
[Touch-packages] [Bug 1886653] Re: cups-pki-expired
i am having the same issue on my HP Deskjet 3630 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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
Re: [Touch-packages] [Bug 1472288] Re: missing attributes in /etc/os-release
On 4/6/21 5:33 PM, Alexander Scheel wrote: > This is a debdiff for Hirsute, applicable against 11ubuntu18 to add > CPE_NAME. I ended up quoting it to follow what Fedora does but from what > I (and ShellCheck) can tell from testing the resulting .deb with bash > and sh, it doesn't strictly need to be quoted. > > Per discussion with Steve Beattie (~sbeattie), we'd be interested in > pursuing a Feature Exception request for this prior to doing backports > for older releases. Does that sound OK? > > ** Patch added: "2-11ubuntu19.debdiff" > > https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+attachment/5484958/+files/2-11ubuntu19.debdiff > Not sure what a "feature exception" is. But whatever you deem best (since you did the work). Ty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1472288 Title: missing attributes in /etc/os-release Status in base-files package in Ubuntu: Confirmed Bug description: Please add 'CPE_NAME' and 'BUILD_ID' to /etc/os-release. More at http://www.freedesktop.org/software/systemd/man/os- release.html. I'm not sure BUILD_ID should be something like 'vivid' etc, but it would be a nice use. Or introduce a new attribute/value pair like NICKNAME_ID="vivid" No rush. Thanks for adopting this convention so quickly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: base-files 7.2ubuntu9 Uname: Linux 4.1.0-rc5carif-7-ga8b253b x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 7 10:26:02 2015 Dependencies: InstallationDate: Installed on 2014-11-04 (245 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: Upgraded to vivid on 2015-04-25 (73 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1472288/+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 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
Here's some output that perhaps is helpful # Normal orientation with tearing: $ xrandr Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1366x768 60.06*+ 40.04 1280x720 60.06 1024x768 60.06 800x600 60.06 640x480 60.06 HDMI-A-0 disconnected (normal left inverted right x axis y axis) # Workaround configuration $ xrandr Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP connected primary 1366x768+0+0 inverted X and Y axis (normal left inverted right x axis y axis) 344mm x 193mm 1366x768 60.06*+ 40.04 1280x720 60.06 1024x768 60.06 800x600 60.06 640x480 60.06 HDMI-A-0 disconnected (normal left inverted right x axis y axis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+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 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
A little investigation and the following implements johnnyl33-k's workaround from the command line. $ xrandr --output eDP --reflect xy --rotate inverted --mode 1366x768 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+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 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
I have the same issue. As mentioned in reddit thread in OP, the login screen displays properly at 1366x768. I'm running MATE so I'm not sure how to implement the workaround @johnnyl33-k mentions for Xubuntu since there are no reflection options. I will note setting rotation to 'upside-down' in Control Center->Monitor Preference does not suffer from the tearing the 'normal' rotation does. It's just hard to work upside down! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+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 1910471] [NEW] [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all
Public bug reported: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description:Ubuntu 20.04.1 LTS Release:20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 focal uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1910471 Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Running Ubuntu Mate 20.04 on Raspberry Pi 4 with Dual Monitor Set-up Description: Ubuntu 20.04.1 LTS Release: 20.04 Packages involved: Unknown Issue: I can choose either 2 HDMI monitors or sound but not both Expected: Sound works with both monitors plugged in (1) No sound from headphone jack or HDMI in two monitor configuration (2) If I unplug 2nd monitor and reboot, sound works fine in HDMI or headphone jack (3) If I plug in second monitor while Pi is running, no picture in second monitor but sound still works (4) Sound works normally in Raspbian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1025.28-raspi 5.4.73 Uname: Linux 5.4.0-1025-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio /dev/snd/pcmC2D0p: loreleiandmike 1211 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 6 19:45:47 2021 ImageMediaBuild: 20200812 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:b1 failed Symptom_Card: Built-in Audio - bcm2835 Headphones Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: loreleiandmike 1211 F pulseaudio Symptom_Type: No sound at all Title: [bcm2835_hdmi - bcm2835 HDMI 1, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1910471/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Perhaps the best hope is that Pipewire develops quickly and replaces Pulseaudio: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 ** Bug watch added: gitlab.freedesktop.org/pipewire/pipewire/-/issues #249 https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 -- 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/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1877762] Re: 1360x768 Vega graphics display staggered
This bug still seems to be active: https://forums.gentoo.org/viewtopic-p-8537062.html#8537062 It is still happening on my machine except the interference seems to be more corrupt along the lines of Simon's image. I believe it briefly stopped some time ago but by the time I started checking the new versions, it started up again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877762 Title: 1360x768 Vega graphics display staggered Status in Ubuntu MATE: New Status in mesa package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: This was the go-to resolution pre-update. All of the other modes seem to work. Release 20.04 LTS (Focal Fossa) 64-bit Kernel Linux 5.4.0-29-generic x86_64 MATE 1.24.0 Processor: AMD Ryzen 3 2200G with Radeon Vega Graphics × 4 Graphics: AMD RAVEN (DRM 3.35.0, 5.4.0-29-generic, LLVM 9.0.1) lspci output: 38:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8) As you can see from the attached image, the display shifts to the right every few lines. Still working on installing the full amdgpu package (libffs 6 required, 7 installed so I'm working on the bits). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1877762/+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 1892108] Re: ping prints ip address octets backwards on host redirect
I'm afraid it likely runs a bit deeper than just being "printed in reverse order". I had a Redirect Host of 192.168.107.65 print backwards and actually name resolve w192.z065107168.sea-wa.dsl.cnc.net (65.107.168.192) and thereafter ping returns ceased, ostensibly because it tried to route my private addresses through some dsl client in Seattle. It's now November, and a fresh install of Focal 20.04.1 still has this problem, reported in August. It might be obscure, but it's not trivial. I hope someone is working on this. Thanks, -MikeB -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1892108 Title: ping prints ip address octets backwards on host redirect Status in iputils package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Just noticed a weird thing with ping on Ubuntu 20.04, which I recently updated to. This is what I get when pinging a host on my network: user@ubuntu2004:~$ ping 10.156.0.63 PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data. From 10.15.0.1 icmp_seq=2 Redirect Host(New nexthop: 2.0.15.10) The ubuntu2004 machine is located in the 10.15.0.x network. 10.15.0.1 is a DSL router. 10.15.0.2 is a firewall between multiple networks. 10.156.0.63 is a machine on a different local network. All traffic not destined for the internet is routed from 10.15.0.1 to 10.15.0.2, so I would expect the printout to read "New nexthop: 10.15.0.2". However, as you can see this is not the case. Instead the octets are printed in reverse order. To verify this I tried the same on another machine in the same network, running Ubuntu 18.04: user@ubuntu1804:~$ ping 10.156.0.63 PING 10.156.0.63 (10.156.0.63) 56(84) bytes of data. From 10.15.0.1: icmp_seq=2 Redirect Host(New nexthop: 10.15.0.2) As you can see, the printout is correct here: "New nexthop: 10.15.0.2" I further verified the discrepancy by using tcpdump to interpret the ICMP packets on the ubuntu2004 machine, and there seems to be no problem for tcpdump to display the correct IP address. My assumption is that there is something wrong in the print function which displays the IP address for a host redirect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1892108/+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 1889013] [NEW] Xorg freeze
Public bug reported: Everything is running smooth, I enjoy this software, but it all freezes up randomly. Sometimes I can still move the cursor, other times I cannot do anything but a hard reset. Do not know why, or haven't figured out what specifically I am doing when this happens. Usually just browsing the net or something simple like that when it happens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 14:01:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:099d] InstallationDate: Installed on 2020-07-13 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire E5-532 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=eb592001-0986-4e81-8bae-52faaa85ba41 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/13/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_BA dmi.board.vendor: Acer dmi.board.version: V1.16 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.16:bd11/13/2015:svnAcer:pnAspireE5-532:pvrV1.16:rvnAcer:rnZoro_BA:rvrV1.16:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: Aspire E5-532 dmi.product.sku: Aspire E5-532_099D_1.16 dmi.product.version: V1.16 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1889013 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Everything is running smooth, I enjoy this software, but it all freezes up randomly. Sometimes I can still move the cursor, other times I cannot do anything but a hard reset. Do not know why, or haven't figured out what specifically I am doing when this happens. Usually just browsing the net or something simple like that when it happens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 26 14:01:10 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1025:099d] InstallationDate: Installed on 2020-07-13 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
[Touch-packages] [Bug 1881554] Re: PCI/internal sound card not detected
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881554 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: No sound ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 1 15:11:24 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 0DG5G3 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd05/14/2018:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0DG5G3:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-06-01T14:54:04.434257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881554/+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 1885015] [NEW] replace gnutls with openssl
Public bug reported: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: curl gnutls openssl -- 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/1885015 Title: replace gnutls with openssl Status in network-manager package in Ubuntu: New Bug description: compile with openssl Simply change --with-crypto=gnutls in rules file Openssl is currently much more tested crypto library than gnutls... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1885015/+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 1883495] Re: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1883495 Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in openssh package in Ubuntu: New Bug description: since months 0penssh can not be installed - not at all tried many times - tried to deinstall using terminal reinstall - no way - something totally broken ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 AptOrdering: libwinpr-pool0.1: Install openssh-server: Configure libwinpr-pool0.1: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon Jun 15 06:19:25 2020 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-10-13 (1340 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 111: Bad configuration option: sudo /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 [modified: usr/lib/tmpfiles.d/sshd.conf] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1883495/+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 1872896] Re: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04)
Installing vim package resolves the issue of `vi empty`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1872896 Title: terminfo file xterm-256color has entries that make vi unusable when sshing in from last lts (18.04) Status in ncurses package in Ubuntu: Confirmed Bug description: This happens on a 20.04 LTS (Focal Fossa) beta system, specifically, the xubuntu-20.04-beta-desktop-amd64.iso as downloaded on Apr 14. When sshing into the 20.04 system, from the previous LTS (18.04), entering/exiting insert mode in vi emits what looks like CSI>4;m resp. CSI>4;2m. Both sequences aren't recognized by the 18.04 terminal, resulting in garbled output and vi being unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1872896/+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 1873794] Re: Unattended upgrades fixes missing from security repo
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1873794 Title: Unattended upgrades fixes missing from security repo Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Eoan: Fix Released Bug description: Critical unattended upgrades fixes are missing from the bionic security repo, which means that if you are using an installation of Ubuntu using only 'bionic' and 'bionic-security' you can stop unattended-upgrades from working just by doing a 'rmdir /var/cache/apt/archives/partial'. This is because the 'rootdir' parameter on the main function is set to "" rather than "/" - which disables the required directories and files check. I'm presuming here that the *-updates pocket is still 'recommended' rather than 'required'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 12:44:35 2020 InstallationDate: Installed on 2016-04-28 (1452 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to bionic on 2018-08-19 (610 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-17T10:50:46.904847 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1873794/+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 1872259] Re: software-properties-gtk crashed with gi.repository.GLib.GError in __init__(): g-io-error-quark: Se alcanzó el tiempo de expiración (24)
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1872259 Title: software-properties-gtk crashed with gi.repository.GLib.GError in __init__(): g-io-error-quark: Se alcanzó el tiempo de expiración (24) Status in software-properties package in Ubuntu: New Bug description: livepatch ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 20:23:24 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 ProcEnviron: SHELL=/bin/bash LANGUAGE=es_CO:es LANG=es_CO.UTF-8 XDG_RUNTIME_DIR= PATH=(custom, no user) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with gi.repository.GLib.GError in __init__(): g-io-error-quark: Se alcanzó el tiempo de expiración (24) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872259/+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 1873559] Re: O audio do meu Ubuntu não esta funcionando
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1873559 Title: O audio do meu Ubuntu não esta funcionando Status in alsa-driver package in Ubuntu: New Bug description: Conectei os fones de ouvido no meu Ubuntu e depois de um tempo ou um som parar de funcionar, tanto com os fones quanto com o falante automático To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873559/+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 1870932] Re: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list
I can't see a way to close the bug report. Feel free to close if desired. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1870932 Title: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list Status in openssh package in Ubuntu: New Bug description: Example of behavior: ``` mikemol@kaylee:~$ ssh-add -L The agent has no identities. mikemol@kaylee:~$ echo $? 1 mikemol@kaylee:~$ ``` I expected an exit code of 0 if the agent was running. I don't need the list of identities; I'm trying to validate that the agent is running, accessible, and operational. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sun Apr 5 10:38:25 2020 InstallationDate: Installed on 2018-12-16 (475 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1870932/+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 1870932] Re: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list
This did eventually work around my problem: https://gist.github.com/mikemol/084759d9bbbaf818ecbb0688d4cc0f5c I suppose the difference between the exit code of 1 and 2 was sufficiently useful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1870932 Title: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list Status in openssh package in Ubuntu: New Bug description: Example of behavior: ``` mikemol@kaylee:~$ ssh-add -L The agent has no identities. mikemol@kaylee:~$ echo $? 1 mikemol@kaylee:~$ ``` I expected an exit code of 0 if the agent was running. I don't need the list of identities; I'm trying to validate that the agent is running, accessible, and operational. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sun Apr 5 10:38:25 2020 InstallationDate: Installed on 2018-12-16 (475 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1870932/+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 1870932] [NEW] ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list
Public bug reported: Example of behavior: ``` mikemol@kaylee:~$ ssh-add -L The agent has no identities. mikemol@kaylee:~$ echo $? 1 mikemol@kaylee:~$ ``` I expected an exit code of 0 if the agent was running. I don't need the list of identities; I'm trying to validate that the agent is running, accessible, and operational. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sun Apr 5 10:38:25 2020 InstallationDate: Installed on 2018-12-16 (475 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1870932 Title: ssh-add -L incorrectly reports a failure when successfully retrieving an empty identity list Status in openssh package in Ubuntu: New Bug description: Example of behavior: ``` mikemol@kaylee:~$ ssh-add -L The agent has no identities. mikemol@kaylee:~$ echo $? 1 mikemol@kaylee:~$ ``` I expected an exit code of 0 if the agent was running. I don't need the list of identities; I'm trying to validate that the agent is running, accessible, and operational. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openssh-client 1:7.6p1-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18 Uname: Linux 4.15.0-69-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sun Apr 5 10:38:25 2020 InstallationDate: Installed on 2018-12-16 (475 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1870932/+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 1858883] Re: date utility format unexpectedly changed after upgrade from bionic to focal
Thanks for taking a look. Yes, it looks like the `date` utility now observes locale-based defaults, such as the new default: $ date Wed 25 Mar 2020 09:47:47 AM PDT Here are some other combinations I tried: $ LC_TIME="" date Wed 25 Mar 2020 09:47:53 AM PDT (setting LC_TIME to an empty string has no effect; the LC_TIME value most likely obtains a default value based on a different setting.) The following variations produce the (formerly, at least) expected output: $ LC_TIME="C" date Wed Mar 25 09:47:59 PDT 2020 $ LC_ALL="C" date Wed Mar 25 09:48:25 PDT 2020 $ LANG="C" date Wed Mar 25 09:52:08 PDT 2020 This post suggests that LC_ALL should be set to C if the output of these utilities is meant to be read by computers: https://unix.stackexchange.com/a/87763/4295 So while this new default does have the potential to cause regressions in users' scripts (and could be considered a regression in that sense), the fix is to correctly set LC_ALL=C in when the `date` utility is invoked in situations where its output is intended to be parsed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1858883 Title: date utility format unexpectedly changed after upgrade from bionic to focal Status in coreutils package in Ubuntu: New Bug description: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. EXPECTED BEHAVIOR = I expected to see the same date format that can be seen on Ubuntu releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1858883/+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 1868780] [NEW] Xubuntu 20.04 - Blank screen after login
Public bug reported: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible single-occurrence 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/1868780 Title: Xubuntu 20.04 - Blank screen after login Status in xorg package in Ubuntu: New Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1,
[Touch-packages] [Bug 1863771] Re: apt update continued to update after I said "n" at the prompt
I just found an update for Chrome, told it "n" and it stopped. Tried it several times. Looks like it was a fluke, or I somehow did something wrong. Thank you for looking into this. I am never going back to Micro$haft! :D ** Changed in: apt (Ubuntu) Status: Incomplete => Invalid -- 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/1863771 Title: apt update continued to update after I said "n" at the prompt Status in apt package in Ubuntu: Invalid Bug description: I ran "apt update" and see there were packages that needed update, I wanted to see wihch ones, so I ran "apt upgrade", looked at the packages needing to be upgraded, realized it would take too long and I was already running behind so I said NO to the prompt to continue. It then proceeded to complete the updates as if I had said yes. See attached screen shot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863771/+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 1863771] Re: apt update continued to update after I said "n" at the prompt
I'll try it again when more updates are available. It's not a problem for me, I was just surprised when it happened. I've had very few issues with Ubuntu, and thought this might be something not many people have tried before. I usually use the --y switch anyway. -- 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/1863771 Title: apt update continued to update after I said "n" at the prompt Status in apt package in Ubuntu: Invalid Bug description: I ran "apt update" and see there were packages that needed update, I wanted to see wihch ones, so I ran "apt upgrade", looked at the packages needing to be upgraded, realized it would take too long and I was already running behind so I said NO to the prompt to continue. It then proceeded to complete the updates as if I had said yes. See attached screen shot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863771/+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 1863771] [NEW] apt update continued to update after I said "n" at the prompt
Public bug reported: I ran "apt update" and see there were packages that needed update, I wanted to see wihch ones, so I ran "apt upgrade", looked at the packages needing to be upgraded, realized it would take too long and I was already running behind so I said NO to the prompt to continue. It then proceeded to complete the updates as if I had said yes. See attached screen shot. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screen shot of apt doing the upgrade after I told it no" https://bugs.launchpad.net/bugs/1863771/+attachment/5329328/+files/Screenshot%20from%202020-02-18%2011-25-16.png -- 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/1863771 Title: apt update continued to update after I said "n" at the prompt Status in apt package in Ubuntu: New Bug description: I ran "apt update" and see there were packages that needed update, I wanted to see wihch ones, so I ran "apt upgrade", looked at the packages needing to be upgraded, realized it would take too long and I was already running behind so I said NO to the prompt to continue. It then proceeded to complete the updates as if I had said yes. See attached screen shot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1863771/+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 1863370] Re: problem opening settings
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863370 Title: problem opening settings Status in xorg package in Ubuntu: New Bug description: i Have problem opening settings in ubuntu disco 19 destop ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CompositorRunning: None Date: Fri Feb 14 14:05:32 2020 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Microsoft Corporation Haswell-ULT Integrated Graphics Controller [1414:0005] InstallationDate: Installed on 2020-02-11 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181115) MachineType: Microsoft Corporation Surface Pro 3 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=a63a3048-e668-4ab7-afe7-71e98c06872b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2650 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2650:bd04/30/2019:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.sku: Surface_Pro_3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863370/+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 1860947] [NEW] package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a
Public bug reported: na ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:41:03 2020 DuplicateSignature: package:libqt4-sql:amd64:4:4.8.7+dfsg-7ubuntu3 Preparing to unpack .../03-libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Log started: 2020-01-26 19:41:03 dpkg: error processing package libqt4-sql:amd64 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2019-05-05 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: qt4-x11 Title: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qt4-x11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1860947 Title: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal Status in qt4-x11 package in Ubuntu: New Bug description: na ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:41:03 2020 DuplicateSignature: package:libqt4-sql:amd64:4:4.8.7+dfsg-7ubuntu3 Preparing to unpack .../03-libqtcore4_4%3a4.8.7+dfsg-7ubuntu1_amd64.deb ... Log started: 2020-01-26 19:41:03 dpkg: error processing package libqt4-sql:amd64 (--remove): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2019-05-05 (266 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: qt4-x11 Title: package libqt4-sql:amd64 4:4.8.7+dfsg-7ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1860947/+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 1858883] [NEW] date utility format unexpectedly changed after upgrade from bionic to focal
Public bug reported: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. EXPECTED BEHAVIOR = I expected to see the same date format that can be seen on Ubuntu releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-bug.txt" https://bugs.launchpad.net/bugs/1858883/+attachment/5318665/+files/ubuntu-bug.txt ** Description changed: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. - EXPECTED BEHAVIOR = - The date format seen below can be seen on Ubuntu releases from Trusty - through Bionic: + I expected to see the same date format that can be seen on Ubuntu + releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 - ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). - FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1858883 Title: date utility format unexpectedly changed after upgrade from bionic to focal Status in coreutils package in Ubuntu: New Bug description: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. EXPECTED BEHAVIOR = I expected to see the same date format that can be seen on Ubuntu releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1858883/+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 1852907] Re: booting problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852907 Title: booting problem Status in xorg package in Ubuntu: New Bug description: the booting problem was sometimes solved by turn the laptop off and wait for few minutes to turn it on again. but it was not always worked. my laptop was preinstalled with windows 8 and upgraded into windows 10. then i chosed to erased all data and install ubuntu 18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 19:08:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb71] InstallationDate: Installed on 2018-07-21 (484 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite P845t ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=fa82f47e-1fa8-4ba5-8e85-89c92962e160 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 6.50 dmi.board.asset.tag: NULL dmi.board.name: TOSHIBA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr6.50:bd09/26/2012:svnTOSHIBA:pnSatelliteP845t:pvrPSPJ5U-009002:rvnTOSHIBA:rnTOSHIBA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite P845t dmi.product.version: PSPJ5U-009002 dmi.sys.vendor: TOSHIBA 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852907/+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 1847347] [NEW] 1.42.13-1ubuntu1.1 breaks debootstrap in Xenial
Public bug reported: At my company we prepare system disk images which start from deboostrap pointing at an internal mirror containing packages from xenial, xenial- updates, and elsewhere. As of September 30, our image preparation begun failing during the initial debootstrap. We narrowed it down to this update— when we remove version 1.42.13-1ubuntu1.1 of this package from our mirror, everything works as before. Apologies that I don't have more details at this time, as we're still digging. But just wanted to get the ball rolling on a discussion here. ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1847347 Title: 1.42.13-1ubuntu1.1 breaks debootstrap in Xenial Status in e2fsprogs package in Ubuntu: New Bug description: At my company we prepare system disk images which start from deboostrap pointing at an internal mirror containing packages from xenial, xenial-updates, and elsewhere. As of September 30, our image preparation begun failing during the initial debootstrap. We narrowed it down to this update— when we remove version 1.42.13-1ubuntu1.1 of this package from our mirror, everything works as before. Apologies that I don't have more details at this time, as we're still digging. But just wanted to get the ball rolling on a discussion here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1847347/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
Posted alsa-info.sh to http://alsa- project.org/db/?f=aea8019642712707b206b1ebf30ceada504b58c2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
OK, stopped working again today. I think I undid everything I've been testing with hdajackretask (i.e. removed boot override) yesterday while it was still working and double-checked it today. Here are the results from hdajacksensetest: mclark ~ sudo hdajacksensetest -a //no headphones Pin 0x12 (Internal Mic, Mobile-In): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No mclark ~ sudo hdajacksensetest -a //headphones Pin 0x12 (Internal Mic, Mobile-In): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Black Mic, Right side): present = No Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = Yes Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Right side): present = No If I'm interpreting this correctly, I only have a pin active on 0x1b. Wonder if I need to specify that in some config file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
Just an FYI, the netcat -U /var/run/acpid.socket is now seeing the headphone jack event. Everything appears to be working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1839097] [NEW] [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Public bug reported: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic drivers radeon 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/1839097 Title: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in xorg package in Ubuntu: New Bug description: Purged Open source PPA and problem persists: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 6 10:54:51 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (226 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1839097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1838959] [NEW] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Public bug reported: 3rd party PPA Mesaremoved, and problem stil persist in dmesg: [ 52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 12:20:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (225 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1+git1907231930.c7ed12~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1907241930.6f4972~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1906080730.ec2b45~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic problem radeon third-party-packages 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/1838959 Title: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in xorg package in Ubuntu: New Bug description: 3rd party PPA Mesaremoved, and problem stil persist in dmesg: [ 52.313240] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 12:20:11 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (225 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1+git1907231930.c7ed12~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1907241930.6f4972~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Touch-packages] [Bug 1838945] [NEW] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0
Public bug reported: Description:Ubuntu 18.04.2 LTS Release:18.04 How to solve this dmesg: [ 50.990513] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 I use dual port(DVI/HDMI) AGP Radeon HD4650 with DVI port connected to LCD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 09:59:52 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (225 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1+git1907231930.c7ed12~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1907241930.6f4972~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16+git1906080730.ec2b45~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic graphics radeon third-party-packages 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/1838945 Title: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 Status in xorg package in Ubuntu: New Bug description: Description: Ubuntu 18.04.2 LTS Release: 18.04 How to solve this dmesg: [ 50.990513] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0 I use dual port(DVI/HDMI) AGP Radeon HD4650 with DVI port connected to LCD. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 5 09:59:52 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] [1002:9495] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP [1002:0028] InstallationDate: Installed on 2018-12-22 (225 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Touch-packages] [Bug 1838585] Re: [CR650, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1838585 Title: [CR650, ATI R6xx HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Suite à l'instalation, le son ne fonctionnait pas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois 1122 F pulseaudio /dev/snd/pcmC0D3p: francois 1122 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 1 02:34:59 2019 InstallationDate: Installed on 2019-07-31 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Audio interne - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois 1122 F pulseaudio /dev/snd/pcmC0D3p: francois 1122 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [CR650, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GNAMS.50A dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GN dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GNAMS.50A:bd10/16/2012:svnMicro-StarInternationalCo.,Ltd.:pnCR650:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GN:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: CR650 dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838585/+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 1838145] Re: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org
*** This bug is a duplicate of bug 1838146 *** https://bugs.launchpad.net/bugs/1838146 Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** This bug has been marked a duplicate of bug 1838146 ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1838145 Title: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org Status in ntp package in Ubuntu: New Bug description: When you install 'ntp' the /etc/ntp.conf it writes refers to the following: - *.ubuntu.ntp.org This hostname name and subdomain doesn't exist, it would be better if you just import and write http://ntp.snails.email/v1/ntp.conf alternatively make a file that randomly selects the pool and server from http://ntp.snails.email/v1/online.json --> so you download the .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it will and randomly compile alist of pool items from the .json --> this will stop chronologistic buffering convulsive environments... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1838145/+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 1838023] Re: package libicu55:amd64 55.1-7 failed to install/upgrade: pacote libicu55:amd64 não está pronto para configuração não posso configurar (estado atual 'half-installed'
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1838023 Title: package libicu55:amd64 55.1-7 failed to install/upgrade: pacote libicu55:amd64 não está pronto para configuração não posso configurar (estado atual 'half-installed') Status in icu package in Ubuntu: New Bug description: ao acessar o sistema aparece a mensagem de erro no sistema e não consigo corrigir ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libicu55:amd64 55.1-7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Jul 25 15:51:51 2019 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.10 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu11 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.10 ErrorMessage: pacote libicu55:amd64 não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2019-07-24 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29ubuntu0.1 SourcePackage: icu Title: package libicu55:amd64 55.1-7 failed to install/upgrade: pacote libicu55:amd64 não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1838023/+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 1838142] Re: mouse not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1838142 Title: mouse not working Status in xorg package in Ubuntu: New Bug description: I was using my mouse and it was 100 functional, then when I took the usb wireless divice out, it stoppped working. I have a sculpt confort desktop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 10:56:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:382c] InstallationDate: Installed on 2019-02-03 (173 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=1d781a49-22b9-4932-8b1b-dfba2bf00d1f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN21WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN21WW(V2.02):bd10/24/2016:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UD dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1838142/+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 1833527] Re: in gnome settings audio section does not see any sound card
also before restart i need to run pulseaudio -k pulseaudio -D and then restart computer -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
Unfortunately it is a recurring bug, and yet again I have no sound detected in gnome settings @Daniel van Vugt -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
I just realised that removing chrome remote desktop config isn't enough. Like I mentioned on my PC i had the same issue. I had to remove .config/pulse too and restart to make it work -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
Thanks Daniel, I have reported another bug with the same issue this time with alsa running. https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1815526 solution is exactly the same -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: Incomplete Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
Ok I managed to fix it rm -rf ~/.config/chrome-remote-desktop/pulse* Looks like chrome remote desktop app (which i was using) took over my sound card in gnome settings, weird :/ -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833534] Re: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Ok I managed to fix it rm -rf ~/.config/chrome-remote-desktop/pulse* Looks like chrome remote desktop app (which i was using) took over my sound card in gnome settings, weird :/ -- 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/1833534 Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 13:01:11 2019 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+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 1833534] [NEW] [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 13:01:11 2019 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1833534 Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 13:01:11 2019 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+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 1833534] Re: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card
i only see chrome device as output device after manually running pulseaudio -D and pulseaudio --check ** Attachment added: "Screenshot from 2019-06-20 12-58-29.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+attachment/5271795/+files/Screenshot%20from%202019-06-20%2012-58-29.png -- 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/1833534 Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 13:01:11 2019 SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [ZenBook Pro 15 UX550GEX_UX580GE, Realtek ALC295, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833534/+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 1833527] Re: in gnome settings audio section does not see any sound card
** Attachment added: "after run pulseaudio -D and pulseaudio --check" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271788/+files/Screenshot%20from%202019-06-20%2012-58-29.png -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
More info after i run pulseaudio --check i can see an output device but its not my sound card, another screenshot attached -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] Re: in gnome settings audio section does not see any sound card
** Attachment added: "Screenshot from 2019-06-20 12-46-32.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+attachment/5271783/+files/Screenshot%20from%202019-06-20%2012-46-32.png -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1833527/+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 1833527] [NEW] in gnome settings audio section does not see any sound card
Public bug reported: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Description changed: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely - different than my laptops one + different than my laptops one. + + All the problems started recently, after upgrading to 19.04 some time + later one of the updates destroyed all sound ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 12:28:49 2019 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to disco on 2019-04-29 (51 days ago) dmi.bios.date: 10/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550GEX.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550GEX 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.:bvrUX550GEX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GEX_UX580GE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GEX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook Pro dmi.product.name: ZenBook Pro 15 UX550GEX_UX580GE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. -- 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/1833527 Title: in gnome settings audio section does not see any sound card Status in pulseaudio package in Ubuntu: New Bug description: in gnome settings audio section does not see any sound card. if i run alsamixer it can detect the sound card and all works fine. in gnome sound settings everything seems to be disabled. I have excatly same problem on PC where configuration is completely different than my laptops one. All the problems started recently, after upgrading to 19.04 some time later one of the updates destroyed all sound ProblemType: Bug DistroRelease:
[Touch-packages] [Bug 1832337] [NEW] Require password when starting usb-creator
Public bug reported: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. ** Affects: policykit-desktop-privileges (Ubuntu) Importance: Undecided Assignee: Ubuntu Security Team (ubuntu-security) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1832337 Title: Require password when starting usb-creator Status in policykit-desktop-privileges package in Ubuntu: New Bug description: Because usb-creator performs privileged actions, it should require authentication prior to starting. policykit-desktop-privileges should be modified so that usb-creator requires password authentication prior to starting. While it was a deliberate design decision to allow usb-creator to perform mounting and writing without authentication (see https://bugs.launchpad.net/ubuntu/+source/policykit-desktop- privileges/+bug/1568149), this decision should be revisited. Allowing the use of usb-creator without authentication presents an unnecessary security risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1832337/+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
