[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
Yep, thanks cjwatson -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: New Bug description: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
@Kyle - in prep for an SRU - do you have steps to reproduce this e.g. with which Ubuntu based client/options one can easily send 1.99 on a connection attempt? -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: New Bug description: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed
Daniel.. anything else i should try to equip you with more info to debug this? 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/1864781 Title: System with GeForce GT 520 failed to boot when nvidia-390 was installed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: System booted OK with Nouveau driver. I used Driver Manager to apply change of "Using NVIDIA driver metapackage from nvidia- driver-390(proprietary,tested)". After the NVIDIA proprietary driver installation, system failed to boot. All i get was a blank screen, with a blinking cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 26 12:02:15 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: I don't know GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2] InstallationDate: Installed on 2020-02-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcEnviron: LANGUAGE=en_HK:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_HK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 887079] Re: Software Sources shows codenames not version numbers
This bug was fixed in the package software-properties - 0.98.7 --- software-properties (0.98.7) focal; urgency=medium * softwareproperties/gtk/SimpleGtkbuilderApp.py: Fix a typo in the keyboard interrupt handling code (LP: #1860143). * Updates tab: - replace checkboxes with a combobox (LP: #887079) - add a label for snap package updates frequency - center the contents of the tab and make padding/spacing more consistent -- Olivier Tilloy Thu, 27 Feb 2020 15:38:46 +0100 ** Changed in: software-properties (Ubuntu) Status: In Progress => Fix Released -- 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/887079 Title: Software Sources shows codenames not version numbers Status in software-properties package in Ubuntu: Fix Released Bug description: In the updates tab software-properties shows codenames such as 'oneiric-updates' and 'oneiric-proposed'. As I understand it we shouldn't really show the codename to the user. It also seems somewhat redundant, it's not like that screen would ever have anything other than $current_release-* in it. I can see why the 3rd party sources might display codenames as users may (for whatever reason) want to add the source for an older (or newer) release on a 3rd party site to get an app. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: software-properties-gtk 0.81.10 Uname: Linux 3.1.0-999-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Nov 7 11:20:31 2011 PackageArchitecture: all ProcEnviron: PATH=(custom, user) SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/887079/+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 1860143] Re: /usr/bin/software-properties-gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin/software-properties-gtk@101:run
This bug was fixed in the package software-properties - 0.98.7 --- software-properties (0.98.7) focal; urgency=medium * softwareproperties/gtk/SimpleGtkbuilderApp.py: Fix a typo in the keyboard interrupt handling code (LP: #1860143). * Updates tab: - replace checkboxes with a combobox (LP: #887079) - add a label for snap package updates frequency - center the contents of the tab and make padding/spacing more consistent -- Olivier Tilloy Thu, 27 Feb 2020 15:38:46 +0100 ** Changed in: software-properties (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1860143 Title: /usr/bin/software-properties- gtk:AttributeError:run:run:__exit__:register_sigint_fallback:/usr/bin /software-properties-gtk@101:run Status in software-properties package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.98.6, the problem page at https://errors.ubuntu.com/problem/7f35e34c316c48e756a0d4a38dd302dbcd8ebfae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1860143/+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 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package mysql-ocaml - 1.2.1-1ubuntu3 --- mysql-ocaml (1.2.1-1ubuntu3) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Gianfranco Costamagna Fri, 21 Feb 2020 08:51:18 +0100 ** Changed in: mysql-ocaml (Ubuntu) Status: In Progress => Fix Released -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: Fix Released Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: Fix Released Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: Fix Released Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1860770] Re: GDM fails to start at boot after removing LightDM
On 2020-01-24 13:42, Chris Halse Rogers wrote:
> debian/lightdm.prerm quite obviously attempts to remove itself from
> the display manager set.
Can it be that that script was not updated when we switched to systemd?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1860770
Title:
GDM fails to start at boot after removing LightDM
Status in lightdm package in Ubuntu:
Confirmed
Bug description:
I removed LightDM on the 14th and then didn't reboot until after
upgrading to Focal. The next reboot didn't launch a display manager at
all, and we tracked this down to /etc/systemd/system/display-
manager.service still pointing to lightdm.service. This is probably a
bug in lightdm {pre,post}rm?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic
5.3.13
Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 11:18:25 2020
InstallationDate: Installed on 2019-08-29 (148 days ago)
InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have confirmed that my Dell Inspiron 7590 with Realtek alc3254 also have the issue with built in microphone. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1860770] Re: GDM fails to start at boot after removing LightDM
** Changed in: lightdm (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1860770
Title:
GDM fails to start at boot after removing LightDM
Status in lightdm package in Ubuntu:
Confirmed
Bug description:
I removed LightDM on the 14th and then didn't reboot until after
upgrading to Focal. The next reboot didn't launch a display manager at
all, and we tracked this down to /etc/systemd/system/display-
manager.service still pointing to lightdm.service. This is probably a
bug in lightdm {pre,post}rm?
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm (not installed)
ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20200106.d763e8ab-1-generic
5.3.13
Uname: Linux 5.3.0+bcachefs.git20200106.d763e8ab-1-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 24 11:18:25 2020
InstallationDate: Installed on 2019-08-29 (148 days ago)
InstallationMedia: Ubuntu 19.10 bcachefs (20190828)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2020-01-20 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1860770/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same issue on HP Elitebook x360 1040 G6 with Ubuntu 18.04.04. Attaching Windows dump. I'll update with remaining information after rebooting to Ubuntu. ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5331731/+files/RtHDDump.txt -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
uname -a Linux piter-HP-EliteBook-x360-1040-G6 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached the xls because of the indentation problem. Here is the logind output in text (which is ok with indentation). ** Attachment added: "journal-logind.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+attachment/5331729/+files/journal-logind.txt -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1776622] Re: snapd updates on cosmic never finish installing. Can't install any other updates.
Experiencing the same issue running `apt upgrade` after a fresh Ubuntu 20.20 install. Running https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1776622/comments/5 helped complete the install. -- 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/1776622 Title: snapd updates on cosmic never finish installing. Can't install any other updates. Status in snapd: Expired Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Expired Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
also please attach text in *text* format, not excel. -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
can you just attach it so I can look at the entire log please? -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1865088] Re: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
I notice that the output from setupcon mentions loading the font twice.
That seems to correspond to this fragment of code in setupcon:
# FONTFILES
FONTFILES=''
if [ "$FONT" ]; then
for f in $FONT; do
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
It looks to me like this will add each font file to FONTFILES twice,
once in the first line of the loop body, and once in the last.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1865088
Title:
setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP:
Invalid argument"
Status in console-setup package in Ubuntu:
New
Bug description:
When I specify a large font file using the FONT variable in .console-
setup, setupcon fails to load the font, reporting "putfont: KDFONTOP:
Invalid argument". If I specify the same font by setting CODESET,
FONTFACE, and FONTSIZE, the setupcon loads it fine.
For instance, if I have the following files:
bjh21@sole:~$ tail .console-setup.test*
==> .console-setup.test1 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
CODESET="Uni2"
FONTFACE="Terminus"
FONTSIZE="32x16"
==> .console-setup.test2 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
FONT=Uni2-Terminus32x16.psf.gz
==> .console-setup.test3 <==
VERBOSE_OUTPUT="no"
ACTIVE_CONSOLES="/dev/tty[1-6]"
CHARMAP="UTF-8"
FONT=Uni2-Terminus16.psf.gz
Running "setupcon test1" correctly loads Uni2-Terminus32x16, but
"setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid
argument". "setupcon test3" works, demonstrating that not all uses of
FONT are broken.
I've attached the verbose output from "setupcon -v test2".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: console-setup 1.178ubuntu2.9
ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18
Uname: Linux 4.15.0-88-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: i386
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Feb 27 20:40:08 2020
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-motts-20100121-3
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-06-09 (3550 days ago)
InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary
20100121-21:52
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached an excel file of the ps -alx command. Regarding the other command, It is long because of the problem :) here is its content Feb 07 10:09:08 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:08 vps.server.local systemd-logind[122]: New seat seat0. Feb 07 10:09:08 vps.server.local systemd[1]: Started Login Service. Feb 07 10:09:19 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:09:19 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:09:33 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:33 vps.server.local systemd-logind[104]: New seat seat0. Feb 07 10:09:33 vps.server.local systemd[1]: Started Login Service. Feb 07 10:10:45 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:10:45 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:11:03 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:11:04 vps48064754.local systemd-logind[163]: New seat seat0. Feb 07 10:11:04 vps48064754.local systemd[1]: Started Login Service. Feb 07 10:13:53 vps48064754.local systemd-logind[163]: New session c1 of user root. Feb 07 10:15:34 vps48064754.local systemd[1]: /lib/systemd/system/systemd-logind.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service' Feb 07 10:17:54 vps48064754.local systemd-logind[163]: New session c2 of user debian-spamd. Feb 07 10:18:23 vps48064754.local systemd-logind[163]: New session c3 of user debian-spamd. Feb 07 10:21:08 vps48064754.local systemd-logind[163]: Removed session c1. Feb 07 10:21:08 vps48064754.local systemd[1]: Stopping Login Service... Feb 07 10:21:08 vps48064754.local systemd[1]: Stopped Login Service. Feb 07 10:21:36 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:21:36 vps48064754.local systemd-logind[151]: New seat seat0. Feb 07 10:21:36 vps48064754.local systemd[1]: Started Login Service. Then a lot of Feb 07 10:56:52 vps48064754.local systemd-logind[151]: New session cxxx of user domain. Then Feb 07 18:19:18 vps48064754.local systemd[1]: Stopping
[Touch-packages] [Bug 1865088] [NEW] setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument"
Public bug reported: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ** Attachment added: "Output from "setupcon -v test2"" https://bugs.launchpad.net/bugs/1865088/+attachment/5331723/+files/setupcon.out -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1865088 Title: setupcon cannot handle large fonts in FONT, "putfont: KDFONTOP: Invalid argument" Status in console-setup package in Ubuntu: New Bug description: When I specify a large font file using the FONT variable in .console- setup, setupcon fails to load the font, reporting "putfont: KDFONTOP: Invalid argument". If I specify the same font by setting CODESET, FONTFACE, and FONTSIZE, the setupcon loads it fine. For instance, if I have the following files: bjh21@sole:~$ tail .console-setup.test* ==> .console-setup.test1 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="32x16" ==> .console-setup.test2 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus32x16.psf.gz ==> .console-setup.test3 <== VERBOSE_OUTPUT="no" ACTIVE_CONSOLES="/dev/tty[1-6]" CHARMAP="UTF-8" FONT=Uni2-Terminus16.psf.gz Running "setupcon test1" correctly loads Uni2-Terminus32x16, but "setupcon test2" does not, reporting "putfont: KDFONTOP: Invalid argument". "setupcon test3" works, demonstrating that not all uses of FONT are broken. I've attached the verbose output from "setupcon -v test2". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.9 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: i386 CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Feb 27 20:40:08 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-motts-20100121-3 EcryptfsInUse: Yes InstallationDate: Installed on 2010-06-09 (3550 days ago) InstallationMedia: Ubuntu GNU/Linux 9.10 "Karmic" - Build i386 LIVE Binary 20100121-21:52 PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1865088/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Well launchpad really messed up the formatting of that output, didn't it :( If the journalctl output is large, you can attach the file to this bug, i.e.: $ journalctl -b -u systemd-logind > /tmp/journal-logind.txt then attach '/tmp/journal-logind.txt' -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1865079] Re: balance slider mutes sound on midle and left or rigth make loud for both ears
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1865079 Title: balance slider mutes sound on midle and left or rigth make loud for both ears Status in alsa-driver package in Ubuntu: New Bug description: when using headset audio is inaudible going to settings and putting balance to left or right works kinda like an audio slider with mute at the center and left/right as max for both ears (meaning regular balance functionality does not work) resets to center(mute) whenever plug or unplug regular system volume still works as expected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vin2991 F pulseaudio /dev/snd/pcmC0D0c: vin2991 F...m pulseaudio /dev/snd/pcmC0D0p: vin2991 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 16:39:32 2020 InstallationDate: Installed on 2019-04-19 (314 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: fev 27 15:16:09 vin-Aspire-VX5-591G dbus-daemon[1258]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.42' (uid=1001 pid=1542 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [Aspire VX5-591G, Realtek ALC255, Black Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1865079/+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 1865079] [NEW] balance slider mutes sound on midle and left or rigth make loud for both ears
You have been subscribed to a public bug: when using headset audio is inaudible going to settings and putting balance to left or right works kinda like an audio slider with mute at the center and left/right as max for both ears (meaning regular balance functionality does not work) resets to center(mute) whenever plug or unplug regular system volume still works as expected ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vin2991 F pulseaudio /dev/snd/pcmC0D0c: vin2991 F...m pulseaudio /dev/snd/pcmC0D0p: vin2991 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 27 16:39:32 2020 InstallationDate: Installed on 2019-04-19 (314 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: fev 27 15:16:09 vin-Aspire-VX5-591G dbus-daemon[1258]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.42' (uid=1001 pid=1542 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [Aspire VX5-591G, Realtek ALC255, Black Headphone Out, Front] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- balance slider mutes sound on midle and left or rigth make loud for both ears https://bugs.launchpad.net/bugs/1865079 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- 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 1864997] Re: System is running in low graphics mode
the logs look fine -- 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/1864997 Title: System is running in low graphics mode Status in xorg package in Ubuntu: New Bug description: Hi, I am receiving this error while booting System is running in low graphics mode. I am using Intel core gen 2 graphic card on my lenevo L430 Thinkpad, runnin gon 64 bit Linux Xenial 16.04 (LTS). Kindly help. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 27 17:42:25 2020 DistUpgraded: 2018-02-07 11:07:14,401 DEBUG /openCache(), new cache size 86347 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21f7] InstallationDate: Installed on 2017-01-23 (1129 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2466CV8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-174-generic root=UUID=88cc2d85-ce2f-4456-b022-dedcdd8398b9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-02-07 (750 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET36WW(1.10) dmi.board.asset.tag: Not Available dmi.board.name: 2466CV8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET36WW(1.10):bd06/20/2012:svnLENOVO:pn2466CV8:pvrThinkPadL430:rvnLENOVO:rn2466CV8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2466CV8 dmi.product.version: ThinkPad L430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Feb 27 17:37:28 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9020 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864997/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I'm having the same issue on my Lenovo T480s. I am able to use the mic on my bluetooth headset. However, the internal mic doesn't even show up as an Input Device in the pulse audio mixer. uname -a Linux chaos 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC257 Analog [ALC257 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1853312] Re: [20.04 FEAT] OpenSSL: Support CPACF enhancements - part 2
** Information type changed from Private to Public ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1853312 Title: [20.04 FEAT] OpenSSL: Support CPACF enhancements - part 2 Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Bug description: Support new crypto functions and improve security. Backport information will be provided. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1853312/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I did loginctl terminate-user domain before so now I have 47 such sessions. domain@domain:~$ ps -alx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 1 0 20 0 232712 10960 ep_pol Ss ?152:21 /lib/systemd/systemd --system --deserialize 12 1 0 2 1 20 0 0 0 kthrea S? 0:00 [kthreadd/79baa9] 1 0 3 2 20 0 0 0 kthrea S? 0:00 [khelper] 4 105 139 1 20 0 189016 988 poll_s Ssl ? 0:03 /usr/sbin/rsyslogd -n 4 0 149 1 20 0 88660 19704 ep_pol Ss ? 1:32 /lib/systemd/systemd-logind 4 0 152 1 20 0 28344 376 hrtime Ss ? 0:02 /usr/sbin/cron -f 4 100 153 1 20 0 48428 1944 ep_pol Ss ? 2:57 /usr/bin/dbus-daemon --system --address=systemd: --4 0 163 1 20 0 196840 18732 poll_s Ssl ? 0:00 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork -1 0 204 1 20 0 10096880 skb_wa Ss ? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix1 0 205 204 20 0 10096892 lock_f S? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix5 118 261 1 20 0 76184 15964 poll_s Ss ? 0:00 postgrey --pidfile=/var/run/postgrey/postgrey.pid -4 106 478 1 20 0 287428 12804 sigsus Ssl ? 0:00 /usr/sbin/named -f -u bind 4 0 489 1 20 0 184288 7800 poll_s Ssl ? 0:00 /usr/bin/python3 /usr/share/unattended-upgrades/una4 0 505 1 20 0 1036648 13412 poll_s Ssl ? 39:19 /usr/bin/python3 /usr/bin/fail2ban-server -xf start4 0 523 1 20 0 72288 916 poll_s Ss ? 0:00 /usr/sbin/sshd -D 0 999 526 1 20 0 4192092 693668 futex_ Sl ? 42:25 /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Djava.1 0 542 1 20 0 24176 256 poll_s Ss ? 0:00 /usr/sbin/xinetd -pidfile /run/xinetd.pid -stayaliv5 0 555 1 20 0 400524 16044 poll_s Ss ? 0:44 /usr/sbin/apache2 -k start 1 0 579 1 20 0 81052 18024 poll_s Ss ? 0:12 /usr/bin/perl /usr/share/usermin/miniserv.pl /etc/u1 0 581 1 20 0 87416 15492 poll_s Ss ? 0:34 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/we533 3714 555 20 0 400956 9468 ep_pol S? 0:00 /usr/sbin/apache2 -k start 533 3716 555 20 0 400892 9352 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 5194 1 20 0 76500 1740 ep_pol Ss ? 0:00 /lib/systemd/systemd --user 5 0 5195 5194 20 0 261960 7528 sigtim S? 0:00 (sd-pam) 4 0 5342 1 20 0 289044 2016 poll_s Ssl ? 0:07 /usr/lib/policykit-1/polkitd --no-debug 4 101 5968 1 20 0 71848 156 ep_pol Ss ? 0:00 /lib/systemd/systemd-networkd 4 0 5975 1 20 0 197976 49068 ep_pol Ss ? 0:12 /lib/systemd/systemd-journald 4 0 6087 1 20 0 42092 308 ep_pol Ss ? 0:00 /lib/systemd/systemd-udevd 5 114 6831 1 20 0 120580 2148 poll_s Ss ? 0:02 proftpd: (accepting connections) 4 0 9525 5194 20 0 90368 224 poll_s SLs ? 0:00 /usr/bin/gpg-agent --supervised 1 0 9928 1 20 0 90368 288 poll_s Ss ? 0:00 gpg-agent --homedir /root/.gnupg --use-standard-soc533 10880 555 20 0 400964 9324 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 113 11187 1 20 0 302396 6484 pause Ss ? 0:08 /usr/bin/freshclam -d --foreground=true 533 11901 555 20 0 400688 8748 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 13481 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear tty2 linux 4 0 13482 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud cons4 0 17557 523 20 0 101548 4356 poll_s Ss ? 0:00 sshd: domain [priv] 5 1000 17572 17557 20 0 101548 1960 poll_s R? 0:00 sshd: domain@pts/0 0 1000 17573 17572 20 0 18628 2128 wait Ss pts/0 0:00 -bash 0 1000 17583 17573 20 0 25936 1276 - R+ pts/0 0:00 ps -alx 4 0 18418 1 20 0 317440 1580 ep_pol Ss ? 0:34 php-fpm: master process (/etc/php/7.2/fpm/php-fpm.c533 18419 18418 20 0 317440 1452 skb_wa S? 0:00 php-fpm: pool www 533 18420 18418 20 0 317440 1448 skb_wa S? 0:00 php-fpm: pool www 533 22504 555 20 0 182440 5768 poll_s S? 0:00 /usr/sbin/apache2 -k start 533 23288 555 20 0 400988 9672 SYSC_s S? 0:00 /usr/sbin/apache2 -k start The command journalctl -b -u systemd-logind starts with Feb-07 so there are A LOT of records there. Maybe a grep of something will show only the important stuff? -- You
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
sorry, can you use -a instead of -e: $ ps -alx also would be useful to see: $ journalctl -b -u systemd-logind -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly
** Package changed: ubuntu => lightdm (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1864982 Title: Ubuntu desktop computer doesn't seem to lock correctly Status in lightdm package in Ubuntu: New Bug description: Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock Screen" it does lock if I use shortcut. If I use the "lock screen" button then anyone can unlock it by merely pressing "ctrl+alt+f7". The problem is not that I cannot lock my screen, the problem is I was under the impression that my computer was being locked when it was not. now that I know that the "Lock Screen" button doesn't work correctly I know of other ways to lock my computer still the lock screen button should work and it looks like it locked my screen,but if I press "ctrl+alt+f7" then it magically unlocks So it is a security incident. Thanks in Advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1864982/+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 1864982] [NEW] Ubuntu desktop computer doesn't seem to lock correctly
You have been subscribed to a public bug: Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock Screen" it does lock if I use shortcut. If I use the "lock screen" button then anyone can unlock it by merely pressing "ctrl+alt+f7". The problem is not that I cannot lock my screen, the problem is I was under the impression that my computer was being locked when it was not. now that I know that the "Lock Screen" button doesn't work correctly I know of other ways to lock my computer still the lock screen button should work and it looks like it locked my screen,but if I press "ctrl+alt+f7" then it magically unlocks So it is a security incident. Thanks in Advance. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu desktop computer doesn't seem to lock correctly https://bugs.launchpad.net/bugs/1864982 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- 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 1861472] Re: upgrade from fresh bionic to focal needlessly prompts user
** Also affects: openssh (Ubuntu Focal) Importance: High Assignee: Colin Watson (cjwatson) Status: Fix Committed ** Tags removed: rls-ff-incoming -- 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/1861472 Title: upgrade from fresh bionic to focal needlessly prompts user Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Focal: Fix Committed Status in openssh package in Debian: Fix Released Bug description: Upgrading from a fresh 18.04 LTS install to focal unexpectedly prompts for how to handle a change to /etc/ssh/sshd_config To reproduce the issue: lxc launch ubuntu:18.04 u18 lxc exec u18 -- bash # within container do-release-upgrade -d # select restart services when prompted Eventually you'll be prompted to accept changes to /etc/ssh/sshd_config or not because of "local changes". Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: openssh-server 1:8.1p1-5 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Fri Jan 31 03:37:55 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: openssh UpgradeStatus: Upgraded to focal on 2020-01-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1861472/+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 1861873] Re: apport-collect fails to run with python3.8
AIUI this is fixed in launchpadlib, and there is nothing to be done on apport itself. ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1861873 Title: apport-collect fails to run with python3.8 Status in launchpadlib : Fix Released Status in apport package in Ubuntu: Invalid Status in python-launchpadlib package in Ubuntu: Fix Released Bug description: errors out with: ERROR: connecting to Launchpad failed: module 'cgi' has no attribute 'parse_qs'\ To manage notifications about this bug go to: https://bugs.launchpad.net/launchpadlib/+bug/1861873/+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 1861250] Re: Apparmor error failed to start profiles
** Changed in: apparmor (Ubuntu) Status: New => Incomplete -- 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/1861250 Title: Apparmor error failed to start profiles Status in apparmor package in Ubuntu: Incomplete Bug description: OS Ubuntu focal fossa 20.04 On boot error message - Apparmor Failed to start profiles. Steps attempted to correct 1.sudo as status lee@lee-desktop:~$ sudo aa-status apparmor module is loaded. 53 profiles are loaded. 51 profiles are in enforce mode. /sbin/dhclient /snap/core/8268/usr/lib/snapd/snap-confine /snap/core/8268/usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/bin/evince /usr/bin/evince-previewer /usr/bin/evince-previewer//sanitized_helper /usr/bin/evince-thumbnailer /usr/bin/evince//sanitized_helper /usr/bin/man /usr/lib/NetworkManager/nm-dhcp-client.action /usr/lib/NetworkManager/nm-dhcp-helper /usr/lib/connman/scripts/dhclient-script /usr/lib/cups/backend/cups-pdf /usr/lib/lightdm/lightdm-guest-session /usr/lib/lightdm/lightdm-guest-session//chromium /usr/lib/snapd/snap-confine /usr/lib/snapd/snap-confine//mount-namespace-capture-helper /usr/lib/telepathy/mission-control-5 /usr/lib/telepathy/telepathy-* /usr/lib/telepathy/telepathy-*//pxgsettings /usr/lib/telepathy/telepathy-*//sanitized_helper /usr/lib/telepathy/telepathy-ofono /usr/sbin/cups-browsed /usr/sbin/cupsd /usr/sbin/cupsd//third_party /usr/sbin/ippusbxd /usr/sbin/tcpdump /usr/share/hplip/plugin.py /usr/share/hplip/sendfax.py /usr/share/hplip/setup.py /usr/share/hplip/systray.py /usr/share/hplip/toolbox.py libreoffice-senddoc libreoffice-soffice//gpg libreoffice-xpdfimport lsb_release man_filter man_groff nvidia_modprobe nvidia_modprobe//kmod snap-update-ns.core snap-update-ns.gnome-calculator snap-update-ns.gnome-characters snap-update-ns.gnome-logs snap-update-ns.gnome-system-monitor snap.core.hook.configure snap.gnome-calculator.gnome-calculator snap.gnome-characters.gnome-characters snap.gnome-logs.gnome-logs snap.gnome-system-monitor.gnome-system-monitor system_tor 2 profiles are in complain mode. libreoffice-oopslash libreoffice-soffice 3 processes have profiles defined. 3 processes are in enforce mode. /usr/lib/telepathy/mission-control-5 (3090) /usr/sbin/cupsd (1646) /usr/bin/tor (1861) system_tor 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. lee@lee-desktop:~$ 2.sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ 3.sudo rm -rf /etc/apparmor.d/cache/* 4. sudo /etc/init.d/apparmor restart lee@lee-desktop:~$ sudo /etc/init.d/apparmor restart Restarting apparmor (via systemctl): apparmor.serviceJob for apparmor.service failed because the control process exited with error code. See "systemctl status apparmor.service" and "journalctl -xe" for details. failed! lee@lee-desktop:~$ Thanks, Lee ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 23:19:19 2020 InstallationDate: Installed on 2013-08-08 (2365 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d2e1abc4-e044-467e-8cc2-57cbe4ef3115 ro drm.debug=0xe plymouth:debug SourcePackage: apparmor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1861250/+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 1865055] [NEW] package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-de
Public bug reported: Running standard upgrades in focal. Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 dpkg: considering deconfiguration of libip4tc-dev:amd64, which would be broken by installation of libiptc-dev:amd64 ... dpkg: yes, will deconfigure libip4tc-dev:amd64 (broken by libiptc-dev:amd64) Preparing to unpack .../08-libiptc-dev_1.8.4-3ubuntu1_amd64.deb ... De-configuring libip4tc-dev:amd64 (1.8.3-2ubuntu5) ... Left my system in this state... $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gobject-introspection : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed hplip : Depends: hplip-data (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: libhpmud0 (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed Depends: printer-driver-hpcups (= 3.19.12+dfsg0-4ubuntu1) but 3.19.12+dfsg0-3 is installed libcryptsetup-dev : Depends: libcryptsetup12 (= 2:2.2.2-3ubuntu1) but 2:2.2.2-2ubuntu1 is installed libgirepository1.0-dev : Depends: libgirepository-1.0-1 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-glib-2.0 (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed Depends: gir1.2-freedesktop (= 1.63.2-1) but 1.62.0-4ubuntu2 is installed libip4tc-dev : Depends: libip4tc2 (= 1.8.3-2ubuntu5) but 1.8.4-3ubuntu1 is installed libiptc-dev : Depends: libip4tc-dev (= 1.8.4-3ubuntu1) but 1.8.3-2ubuntu5 is installed Breaks: libip4tc-dev (< 1.8.4-2) but 1.8.3-2ubuntu5 is installed libnss-systemd : Depends: systemd (= 244.3-1ubuntu1) libpam-systemd : Depends: systemd (= 244.3-1ubuntu1) libsmbclient : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed libsystemd-dev : Depends: libsystemd0 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed libudev-dev : Depends: libudev1 (= 244.3-1ubuntu1) but 244.1-0ubuntu2 is installed python3-ldb : Depends: libldb2 (= 2:2.0.8-1ubuntu1) but 2:2.0.7-4 is installed python3-samba : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libldb2 (>= 2:2.0.8~) but 2:2.0.7-4 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed samba-common-bin : Depends: samba-libs (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed Depends: libwbclient0 (= 2:4.11.5+dfsg-1ubuntu2) but 2:4.11.1+dfsg-3ubuntu2 is installed systemd-sysv : Depends: systemd (= 244.3-1ubuntu1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libip4tc-dev 1.8.3-2ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Thu Feb 27 10:28:46 2020 ErrorMessage: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 InstallationDate: Installed on 2019-04-05 (327 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.8 SourcePackage: iptables Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 UpgradeStatus: Upgraded to focal on 2019-11-21 (97 days ago) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1865055 Title: package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-dev:amd64 1.8.3-2ubuntu5 Status in iptables package in Ubuntu: New Bug description: Running standard upgrades in focal. Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package
[Touch-packages] [Bug 1849714] Re: failure to install repos for raspberry pi
Are these libraries no longer needed? Or do I have to go back to Bionic in case I do VideoCore related stuff (e.g. for cam or other VC related projects)? -- 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/1849714 Title: failure to install repos for raspberry pi Status in software-properties package in Ubuntu: Invalid Bug description: following the directions about 1/5 down the page of https://wiki.ubuntu.com/ARM/RaspberryPi sudo add-apt-repository ppa:ubuntu-raspi2/ppa Cannot add PPA: 'ppa:~ubuntu-raspi2/ubuntu/ppa'. ERROR: '~ubuntu-raspi2' user or team does not exist. This seems like a failure to me. shire:~(13) lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1849714/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
I have time to maintain openssh in Debian, but in general I don't have cycles to deal with SRUs, so please could somebody else take care of that part? ** Changed in: openssh (Ubuntu Bionic) Assignee: Colin Watson (cjwatson) => (unassigned) -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: New Bug description: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
Assigned to cjwatson for now, but feel free to tell us you want us to drive the SRU for this and we can change it. -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: New Bug description: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3
Thanks Kyle for the great report and prepping a fix already. offending: 97f4d3083 is in >=1%7.6p1-1 fix: 9e9c4a7e5 is in >=1%7.7p1-1 fix: c9c1bba06 is in >=1%7.7p1-1 Matching that with versions in Ubuntu means only Bionic should be affected. openssh | 1:5.9p1-5ubuntu1| precise | source openssh | 1:5.9p1-5ubuntu1.10 | precise-security | source openssh | 1:5.9p1-5ubuntu1.10 | precise-updates | source openssh | 1:6.6p1-2ubuntu1| trusty | source openssh | 1:6.6p1-2ubuntu2.13 | trusty-security | source openssh | 1:6.6p1-2ubuntu2.13 | trusty-updates | source openssh | 1:7.2p2-4 | xenial | source openssh | 1:7.2p2-4ubuntu2.8 | xenial-security | source openssh | 1:7.2p2-4ubuntu2.8 | xenial-updates | source openssh | 1:7.2p2-4ubuntu2.9 | xenial-proposed | source openssh | 1:7.6p1-4 | bionic | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-security | source openssh | 1:7.6p1-4ubuntu0.3 | bionic-updates | source openssh | 1:7.6p1-4ubuntu0.4 | bionic-proposed | source openssh | 1:7.9p1-10 | disco| source openssh | 1:8.0p1-6build1 | eoan | source openssh | 1:8.0p1-6ubuntu0.1 | eoan-proposed| source openssh | 1:8.1p1-5 | focal| source openssh | 1:8.2p1-4 | focal-proposed | source @CJWatson - are you also doing the openssh SRUs or would you expect us to handle that? ** Tags added: server-next ** Also affects: openssh (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New => Fix Released ** Changed in: openssh (Ubuntu Bionic) Assignee: (unassigned) => Colin Watson (cjwatson) -- 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/1863930 Title: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3 Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Bionic: New Bug description: SSHD closes the connection and logs the error message below when a client presents a protoversion of "1.99": Protocol major versions differ for X.X.X.X port X: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX RFC 4253 only states that clients should treat a server's protoversion of "1.99" as equivalent to "2.0"; however, some backward-compatible clients send a protoversion of "1.99" and expect the server to treat it as "2.0". This regression was introduced in openssh-portable 7.6p1 from commit 97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06. I've attached a patch with both of those fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+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 1864207] Re: Update request: 0.8.0 released
Debian started on updating to 0.8: https://salsa.debian.org/ah/avahi -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1864207 Title: Update request: 0.8.0 released Status in avahi package in Ubuntu: New Bug description: Version 0.8.0 of Avahi got released: https://github.com/lathiat/avahi/releases/tag/v0.8 Would be great to have this in Ubuntu 20.04 LTS (Focal) -- The Avahi 0.8 release brings a number of new features and bug fix changes including a backward-compatible addition to the D-Bus API and the avahi-core API. The existing API is still fully supported however clients using the new API will not work with older Avahi releases. The avahi-client library is not affected. See the "API Changes" section for further details. New Features: New options for filtering reflected queries between networks (reflect-filter) New mainloop integration for Qt5 and libevent docs/THREADS: Information for multi-threaded avahi-client apps Listen on loopback interfaces by default, allowing local-only services to be consumed by the local machine New D-Bus V2 API and additions to the avahi-core API for splitting "New" calls into "Prepare" and "Start". See "API Changes" for more details. Notable Changes: avahi-autoipd: Initial IP selection based on MAC previously ignored first octet - this will cause all hosts to select a different link-local IP than previous versions based on the same MAC address avahi-daemon: Delay sending results on an object for 10ms in an attempt to give clients enough time to subscribe to signals from the new object after receiving it's path in response so the New call. See "API Changes" for more info Bug Fixes: avahi-python: Various Python 3 enhancements including encoding unicode strings as UTF-8 avahi-common: avahi_string_list_to_string will now escape embedded quotes, backslashes and control characters. avahi-daemon: Fix a crash when txt records have an empty value in .xml service files avahi-daemon: reflector: do not incorrectly cache responses on outgoing interfaces. Previously we would incorrectly cache responses reflected from one interface on the outgoing interface. These responses were later sent to clients on that network even if the original client had disappeared and could cause those clients to have a hostname conflict with themselves on restart. We no longer incorrectly cache such traffic. Security Fixes: Drop legacy unicast queries from address not on local link which can lead to UDP traffic amplification attacks (CVE-2017-6519) API Changes: The avahi-core API and D-Bus API have implemented a new API where a call to the "New" method can now be split into a "Prepare" and then "Start" method for some objects. The previous "New" API is still fully supported and there is no intention to deprecate it. This change affects the the following objects: AsyncAddressResolver, AsyncHostNameResolver, AsyncServiceResolver, DomainBrowser, RecordBrowser, ServiceBrowser, ServiceTypeBrowser This is because the D-Bus implementation in some languages would only bind to signals of an object after it was created and had received the new object's path. This led to such languages missing the initial results sent between the time the object was created and it had setup a filter to receive it's signals. This primarily occured in languages that create dynamic bindings for D-Bus objects using introspection such as Python. The avahi-client C api was not affected as it globally binds to all avahi signals without specifying individual object paths and still makes use of the V1 API. The v2 Prepare/Start API is available under the new org.freedesktop.Avahi.Server2 D-Bus interface and also has corresponding avahi_s_* calls for users of the embedded avahi-core library. The old org.freedesktop.Avahi.Server interface is still supported and there is no intention to remove this API. Additionally this problem has also been solved for old clients by adding a very small 10ms delay before we start sending results to give the client time to bind to the signals which should silently fix the issue in most cases without introducing a noticable or impactful delay. Clients implementing the new org.freedesktop.Avahi.Server2 D-Bus interface will not work with older Avahi daemons. It is suggested that clients may wish to either check for and fallback to the older API version, or continue to use the OLD API and rely on the 10ms timer to resolve the issue. Big thank-you to everyone contributing to the project through issues & pull requests, including the the following people who contributed changes to this release: Daniel S, David Kerr, Eric Bischoff, James Rudd, Jan Alexander Steffens (heftig), Karl Cronburg, Krzesimir Nowak, Mario Blättermann,
[Touch-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
Yes, we could close this bug since we have #1862776. Thx. ** Changed in: alsa-lib (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: Invalid Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Looks "quiet" but I have 1994 sessions in "loginctl list-sessions" domain@domain:~$ ps -elx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 5 1000 25901 25885 20 0 101548 1960 ? S? 0:00 sshd: domain@pts/0 0 1000 25902 25901 20 0 18628 2132 wait Ss pts/0 0:00 -bash USER=domain LOGNAME=domain HOME=/home/sto 0 1000 26403 25902 20 0 25936 1276 - R+ pts/0 0:00 ps -elx LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=4 domain@domain:~$ -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
Hey Hui, some comments about the report - you subscribed ubuntu-sponsors but there is no debdiff to sponsor there? - alsa-lib in focal has libasound2-data Recommends 'Recommends: alsa- ucm-conf, alsa-topology-conf' - to be installed by default the recommends need to be in main, that's bug #1862776 I guess the bug here can be closed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: New Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+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 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
> Regarding "ps -elx", just to make sure: you want me to run it while I connect (ssh) using domain user? Any user on the system is fine; it will show info about all processes. -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1863873] Re: Systemd fails to configure bridged network in LXC container
I have the same problem. -- 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/1863873 Title: Systemd fails to configure bridged network in LXC container Status in systemd package in Ubuntu: Incomplete Bug description: In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal Fossa, installing the latest systemd package results in losing network configuration. It is still possible to configure the network "by hand" with /usr/sbin/ip, but of course, the configuration is lost at reboot. An example is provided, followed by a complete procedure to reproduce the issue. Affected container distributions Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected Bionic Beaver systemd 237-3ubuntu10.39: BUGGY Disco Dingo systemd 240-6ubuntu5.8: OK, not affected Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected Eoan Ermine systemd 242-7ubuntu3.7: BUGGY Focal Fossa systemd 244.2-1ubuntu1: BUGGY Affected hosts == Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 kernel Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7) Example === Example host bridge configuration - 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: mtu 1500 qdisc mq master br0 state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff 3: eth1: mtu 1500 qdisc mq master br1 state DOWN group default qlen 1000 link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff 4: br0: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.252.24/24 brd 192.168.252.255 scope global br0 valid_lft forever preferred_lft forever inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1 valid_lft forever preferred_lft forever inet6 fe80::225:90ff:fe2b:f160/64 scope link valid_lft forever preferred_lft forever Example container network configuration --- lxc.net.0.type = veth lxc.net.0.veth.pair = vps525389 lxc.net.0.flags = up lxc.net.0.link = br0 lxc.net.0.hwaddr = 02:00:00:52:53:89 lxc.net.0.name = eth0 lxc.net.0.ipv4.gateway = 192.168.252.1 lxc.net.0.ipv4.address = 192.168.252.177/32 Example steps to reproduce, inside the container root@vps525389:~# lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 root@vps525389:~# apt-cache policy systemd systemd: Installed: 237-3ubuntu10.38 Candidate: 237-3ubuntu10.39 Version table: 237-3ubuntu10.39 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages *** 237-3ubuntu10.38 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages root@vps525389:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 1958: eth0@if1959: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:52:53:89 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 192.168.252.177/32 brd 255.255.255.255 scope global eth0 valid_lft forever preferred_lft forever inet6 ::x:xx::x:/128 scope global valid_lft forever preferred_lft forever inet6 ::xx::/64 scope link valid_lft forever preferred_lft forever root@vps525389:~# apt install systemd Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libnss-systemd libpam-systemd libsystemd0 Suggested packages: systemd-container policykit-1 The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd0 systemd 4 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Need to get 3330 kB of archives. After this operation, 7168 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I login to domain user using ssh from time to time... as a "bonus", Virtualmin open/close a session for that same user to do its stuff: https://www.cloudmin.com/node/54674 The above is causing the number of ghost sessions to grow even more rapidly Regarding "ps -elx", just to make sure: you want me to run it while I connect (ssh) using domain user? -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1864997] [NEW] System is running in low graphics mode
Public bug reported: Hi, I am receiving this error while booting System is running in low graphics mode. I am using Intel core gen 2 graphic card on my lenevo L430 Thinkpad, runnin gon 64 bit Linux Xenial 16.04 (LTS). Kindly help. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 27 17:42:25 2020 DistUpgraded: 2018-02-07 11:07:14,401 DEBUG /openCache(), new cache size 86347 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21f7] InstallationDate: Installed on 2017-01-23 (1129 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 2466CV8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-174-generic root=UUID=88cc2d85-ce2f-4456-b022-dedcdd8398b9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-02-07 (750 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G3ET36WW(1.10) dmi.board.asset.tag: Not Available dmi.board.name: 2466CV8 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG3ET36WW(1.10):bd06/20/2012:svnLENOVO:pn2466CV8:pvrThinkPadL430:rvnLENOVO:rn2466CV8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2466CV8 dmi.product.version: ThinkPad L430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Feb 27 17:37:28 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9020 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1864997 Title: System is running in low graphics mode Status in xorg package in Ubuntu: New Bug description: Hi, I am receiving this error while booting System is running in low graphics mode. I am using Intel core gen 2 graphic card on my lenevo L430 Thinkpad, runnin gon 64 bit Linux Xenial 16.04 (LTS). Kindly help. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Feb 27 17:42:25 2020 DistUpgraded: 2018-02-07 11:07:14,401 DEBUG /openCache(), new cache size 86347 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21f7] InstallationDate: Installed on 2017-01-23 (1129 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO
[Touch-packages] [Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
To clarify, you're not logging in yourself as 'domain' user, right? Also can you paste/attach the output of: $ ps -elx ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed Status in systemd package in Ubuntu: Incomplete Bug description: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re- logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+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 1864980] Re: using hebrew in a german basic setup
** Package changed: ubuntu => xorg (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/1864980 Title: using hebrew in a german basic setup Status in xorg package in Ubuntu: New Bug description: Hi! I was trying to use different languages/keyboards like german, english and hebrew in a german setup, meaning I put the basić language of my ubuntu into german and then wanted to use hebrew aswell, which was not possible and I also didn't find a workaround. When I put the basic language of ubuntu into hebrew it works (of course), and I realized that in english as basic language it also works to change between different languages/keyboards. Would be nice to have this option in a german environment aswell. You know, these two countries, they have enough issues already ;) Best regards Benedikt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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: Thu Feb 27 10:26:24 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f910] InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd11/27/2014:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCLUE-01W010GR:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.sku: PSCLUE dmi.product.version: PSCLUE-01W010GR dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1864980/+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 1862797] Re: Systemd does not allow hibernation when Chrome/chromium is running
While running chrome/chromium, please paste the output of: $ free $ cat /proc/swaps ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1862797 Title: Systemd does not allow hibernation when Chrome/chromium is running Status in systemd package in Ubuntu: Incomplete Bug description: 1/ Linux Mint 19.3/Ubuntu Bionic 18.04 LTS 2/ systemd: Installed: 237-3ubuntu10.38 3/ & 4/ Problem: hibernation stops working as soon as you start Chromium Steps to reproduce $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanSuspend s "yes" $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "yes" start chromium $ busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CanHibernate s "na" $ sudo systemctl hibernate Failed to hibernate system via logind: Sleep verb not supported When this happens Cinnamon/Gnome no longer show hibernate buttons of course. $ systemd-inhibit --list Who: ecotech (UID 1000/ecotech, PID 1607/csd-media-keys) What: handle-power-key:handle-suspend-key:handle-hibernate-key Why: Cinnamon handling keypresses Mode: block Who: ModemManager (UID 0/root, PID 996/ModemManager) What: sleep Why: ModemManager needs to reset devices Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: sleep Why: Cinnamon needs to lock the screen Mode: delay Who: ecotech (UID 1000/ecotech, PID 1656/csd-power) What: handle-lid-switch Why: Multiple displays attached Mode: block Who: NetworkManager (UID 0/root, PID 1012/NetworkManager) What: sleep Why: NetworkManager needs to turn off networks Mode: delay Who: UPower (UID 0/root, PID 1279/upowerd) What: sleep Why: Pause device polling Mode: delay Systemd-inhibit does not mention anything Chrome/Chromium related Stop Chromium and hibernation works again. Similar issues found: https://bugzilla.redhat.com/show_bug.cgi?id=1346908 $ cat /sys/power/state freeze mem disk $ cat /sys/power/disk [platform] shutdown reboot suspend test_resume Tried logind.conf default (all commented out) and below. No difference. $ cat /etc/systemd/logind.conf [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 HandlePowerKey=poweroff HandleSuspendKey=suspend HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchDocked=ignore PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s #IdleAction=ignore #IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 #UserTasksMax=33% Can also not file a bug @ https://github.com/systemd/system since my version is more than 2 versions older than the last version (2.44.1). Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862797/+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 1864980] [NEW] using hebrew in a german basic setup
You have been subscribed to a public bug: Hi! I was trying to use different languages/keyboards like german, english and hebrew in a german setup, meaning I put the basić language of my ubuntu into german and then wanted to use hebrew aswell, which was not possible and I also didn't find a workaround. When I put the basic language of ubuntu into hebrew it works (of course), and I realized that in english as basic language it also works to change between different languages/keyboards. Would be nice to have this option in a german environment aswell. You know, these two countries, they have enough issues already ;) Best regards Benedikt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-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: Thu Feb 27 10:26:24 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f910] InstallationDate: Installed on 2020-02-25 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: TOSHIBA SATELLITE C50-B ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd11/27/2014:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCLUE-01W010GR:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: SATELLITE C50-B dmi.product.sku: PSCLUE dmi.product.version: PSCLUE-01W010GR dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- using hebrew in a german basic setup https://bugs.launchpad.net/bugs/1864980 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- 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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello The incident is always present with the most recent ubuntu version. a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)" a@a:~$ a@a:~$ a@a:~$ sudo apt update Atteint :1 http://fr.archive.ubuntu.com/ubuntu focal InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu focal-updates InRelease Atteint :3 http://security.ubuntu.com/ubuntu focal-security InRelease Atteint :4 http://fr.archive.ubuntu.com/ubuntu focal-backports InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait Tous les paquets sont à jour. a@a:~$ -- 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/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "Trace of execution" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5331562/+files/Bug1857914-102-176-8192Mo-SDB10bis.txt -- 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/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT Status in e2fsprogs package in Ubuntu: New Bug description: 591/5000 Hello To try to understand this incident ( https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which systematically occurs in version 19.10 and which I cannot (yet?) reproduce in version 18.04.03, I made a test game. Using this test game consisting only of cp and diff commands, I caused a similar problem. The first visible consequence which seems serious to me: The copied file is not identical to the sending file. It seems that the blocks are shifted. It would be desirable for the user to be warned that the written files have become incorrect. Thank you for your advice. Journalctl says only janv. 26 13:29:35 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 uas_eh_abort_handler 0 uas-tag 17 inflight: OUT janv. 26 13:30:12 a kernel: sd 6:0:0:0: [sdb] tag#16 CDB: Write(10) 2a 00 00 0f ec 00 00 04 00 00 janv. 26 14:22:48 a kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) a@a:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.6
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.6) xenial; urgency=medium
* data/50unattended-upgrades.Ubuntu: add new ESM repositories (LP:
#1857051)
-- Balint Reczey Mon, 17 Feb 2020 12:39:28 +0100
--
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/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
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:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.14
---
unattended-upgrades (1.1ubuntu1.18.04.14) bionic; urgency=medium
* data/50unattended-upgrades.Ubuntu: add new ESM repositories (LP:
#1857051)
-- Balint Reczey Mon, 17 Feb 2020 12:37:03 +0100
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: unattended-upgrades (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
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:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1857051] Re: Please add ${distro_id}ESM:${distro_codename}-infra-security and ${distro_id}ESMApps:${distro_codename}-apps-security to allowed origins (on Ubuntu)
This bug was fixed in the package unattended-upgrades - 1.14ubuntu1.2
---
unattended-upgrades (1.14ubuntu1.2) eoan; urgency=medium
* data/50unattended-upgrades.Ubuntu: add new ESM repositories (LP: #1857051)
* Update md5sum of 50unattended-upgrades.Ubuntu
-- Balint Reczey Mon, 17 Feb 2020 12:29:17 +0100
** Changed in: unattended-upgrades (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
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:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1857051] Update Released
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1857051
Title:
Please add ${distro_id}ESM:${distro_codename}-infra-security and
${distro_id}ESMApps:${distro_codename}-apps-security to allowed
origins (on Ubuntu)
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Trusty:
Won't Fix
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:
[Impact]
* Changes to the ESM repo naming and the introduction of the new esm-infra
and esm-apps suites require an update to unattended-upgrades to ensure the
security pockets are used.
* This change will ensure users are actually receiving updates, where as
today they will not without making manual changes.
[Test Case]
* 1) Bionic and Xenial ESM-Apps/ESM-infra with Ubuntu Pro
* 2) Trusty ESM
[Regression Potential]
* This change is ensuring users actually receive security updates when using
ESM. Therefore, 1) users of ESM-apps on Ubuntu Pro and 2) ESM-infra on Trusty
will be the only users affected.
* The possible issue would be if/when users receive actual security updates
that then regress or cause issues to the system.
[Other Info]
Previous description:
ESM -infra-security and -apps-security will need to
participate in unattended upgrades.
Currently /etc/apt/apt.conf.d/50unattended-upgrades provides:
Unattended-Upgrade::Allowed-Origins {
"${distro_id}ESM:${distro_codename}";
}
Given that there have been ESM apt pocket renames over the last few
months, the above ESM allowed-origin should not apply anymore and can
be dropped or replaced.
See RT #C122697 and #C121067 for the pocket/suite renames related to
ESM
What is needed after the ESM apt pocket/suite renames:
Support for unattended upgrades for ESM for Infrastructure customers:
Unattended-Upgrade::Allowed-Origins {
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESM:${distro_codename}-infra-security";
"${distro_id}ESMApps:${distro_codename}-apps-security";
};
=== Confirmed proper origin on an attached Trusty instance with ESM-
infra enabled:
500 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main amd64 Packages
release
v=14.04,o=UbuntuESM,a=trusty-infra-security,n=trusty,l=UbuntuESM,c=main
=== Confirmed proper origins on Bionic for enabled ESM-infra and ESM-apps on
an AWS Ubuntu PRO instance:
500 https://esm.ubuntu.com/infra/ubuntu bionic-infra-security/main amd64
Packages
release
v=18.04,o=UbuntuESM,a=bionic-infra-security,n=bionic,l=UbuntuESM,c=main,b=amd64
500 https://esm.ubuntu.com/apps/ubuntu bionic-apps-security/main amd64
Packages
release
v=18.04,o=UbuntuESMApps,a=bionic-apps-security,n=bionic,l=UbuntuESMApps,c=main,b=amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1857051/+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 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package orthanc-mysql - 2.0-2ubuntu3 --- orthanc-mysql (2.0-2ubuntu3) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Fri, 21 Feb 2020 13:55:23 -0300 ** Changed in: orthanc-mysql (Ubuntu) Status: In Progress => Fix Released -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: Fix Released Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: Fix Released Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: Fix Released Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
** Changed in: ubuntu-themes (Ubuntu)
Assignee: Martin Wimpress (flexiondotorg) => (unassigned)
--
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/1478173
Title:
Ambiance & Radiance themes are missing a "background-color" for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in One Hundred Papercuts:
Confirmed
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance & Radiance GTK3 themes.
They're missing a "background-color" for the .tooltip {...} CSS rule
in their config files. They have a "tooltip_bg_color" variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the ".tooltip" CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+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 1641915] Re: GtkToolButtons clip and overlap
** Changed in: ubuntu-themes (Ubuntu Xenial) Assignee: Martin Wimpress (flexiondotorg) => (unassigned) -- 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/1641915 Title: GtkToolButtons clip and overlap Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Xenial: In Progress Bug description: [ Impact ] GtkToolButton styling causes buttons to clip and overlap each other. This can be seen in gnome-disks and the Ubiquity disk partitioner for Ubuntu 16.04.1. See the attached screenshot: * https://bugs.launchpad.net/ubuntu- themes/+bug/1641915/+attachment/4777652/+files/gtk-toolbutton- clipping.png [ Test Case ] Start a Ubuntu 16.04.1 live session and "Try Ubuntu". From the live Desktop click the Ubuntu logo in the launcher, search for Disks and start it. Select the hard disk from the side panel, then look at and hover over, the buttons beneath the representation of the disk partitions. You'll notice the buttons clip/overlap as illustrated in the screenshot above. Now double click the "Install Ubuntu 16.04.1 LTS" icon on the desktop. The Installer will start, click Continue, click Continue, check "Something else" and then the click Continue. Look at, and hover over, the buttons beneath the tree representing the disk partitions. You'll notice they clip/overlap as illustrated in the screenshot above. After the patched ubuntu-themes has been installed the buttons described in the steps above will no longer clip/overlap. [ Regression Potential ] None expected. [ Other Info ] This issue does not present in Yakkety or Zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1641915/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor
the solution under #108 fixed my problem as well. Thank you. You have to have the displaylink driver first https://www.displaylink.com/downloads/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/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in xorg package in Ubuntu: Incomplete Bug description: *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT* If you are having an issue and want it addressed, it is most helpful to file a new report. If you were led here by DisplayLink's website, you were led here in error as no useful debugging information has been provided by the original reporter, which is necessary to root cause, and solve the issue he reported. Posting comments about how you think you have the same problem isn't helpful here. My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I "Restore previous settings", after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1864974] [NEW] apt clash with python
Public bug reported: [code]Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Original exception was: Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 ... E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code[/code][code]:~$ apt policy apt apt: Installed: 1.9.11 Candidate: 1.9.11 Version table: *** 1.9.11 500 500 http://us.archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.9.10+0~202002252104~ubuntu20.04.1 500 500 http://ppa.launchpad.net/deity/sid/ubuntu devel/main amd64 Packages 1.9.10 500 500 http://us.archive.ubuntu.com/ubuntu devel/main amd64 Packages[/code] [code]apt (1.9.11) experimental; urgency=medium [ Tomáš Janoušek ] * bash completion: Add autopurge command [ Tris Emmy Wilson ] * apt-mark: don't lie about successful marks [ Julian Andres Klode ] * apt(8): Wait for lock (Closes: #754103) * policy: Implement pinning by source package (Closes: #166032) * Initialize libgcrypt on first use (Closes: #949074) * Fix various compiler warnings * Bump ABI to 6.0; update symbols file; cleanup ABI: - Merge various function overloads together - Make stuff that should be virtual virtual - Default to hidden visibility * Code removals: - Use a 32-bit djb VersionHash instead of CRC-16 - Remove CRC-16 implementation * Hardening: - tagfile: Check if memchr() returned null before using - tagfile: Check out-of-bounds access to Tags vector * Cache improvements: - Type safe cache: Replace map_pointer_t with map_pointer - Extensibility: Add d-pointers to groups, packages, versions, and files - Prepare for package hashtable removal: Swap locations of hashtables [ Nis Martensen ] * apt-pkg/srcrecords.cc: 'source' means 'deb-src' in error message [ David Kalnischkies ] * Parse records including empty tag names correctly -- Julian Andres Klode Wed, 26 Feb 2020 21:29:48 +0100[/code] ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1864974 Title: apt clash with python Status in apport package in Ubuntu: New Bug description: [code]Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as
[Touch-packages] [Bug 1864974] Re: apt clash with python
https://ubuntuforums.org/showthread.php?t=2437648=13935060#post13935060 -- 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/1864974 Title: apt clash with python Status in apport package in Ubuntu: New Bug description: [code]Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 63, in apport_excepthook from apport.fileutils import likely_packaged, get_recent_crashes File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 23, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 Original exception was: Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 8, in from CommandNotFound.db.creator import DbCreator File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 11, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-38-x86_64-linux-gnu.so: undefined symbol: _ZTI9pkgDPkgPM, version APTPKG_6.0 ... E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code[/code][code]:~$ apt policy apt apt: Installed: 1.9.11 Candidate: 1.9.11 Version table: *** 1.9.11 500 500 http://us.archive.ubuntu.com/ubuntu devel-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.9.10+0~202002252104~ubuntu20.04.1 500 500 http://ppa.launchpad.net/deity/sid/ubuntu devel/main amd64 Packages 1.9.10 500 500 http://us.archive.ubuntu.com/ubuntu devel/main amd64 Packages[/code] [code]apt (1.9.11) experimental; urgency=medium [ Tomáš Janoušek ] * bash completion: Add autopurge command [ Tris Emmy Wilson ] * apt-mark: don't lie about successful marks [ Julian Andres Klode ] * apt(8): Wait for lock (Closes: #754103) * policy: Implement pinning by source package (Closes: #166032) * Initialize libgcrypt on first use (Closes: #949074) * Fix various compiler warnings * Bump ABI to 6.0; update symbols file; cleanup ABI: - Merge various function overloads together - Make stuff that should be virtual virtual - Default to hidden visibility * Code removals: - Use a 32-bit djb VersionHash instead of CRC-16 - Remove CRC-16 implementation * Hardening: - tagfile: Check if memchr() returned null before using - tagfile: Check out-of-bounds access to Tags vector * Cache improvements: - Type safe cache: Replace map_pointer_t with map_pointer - Extensibility: Add d-pointers to groups, packages, versions, and files - Prepare for package hashtable removal: Swap locations of hashtables [ Nis Martensen ] * apt-pkg/srcrecords.cc: 'source' means 'deb-src' in error message [ David Kalnischkies ] * Parse records including empty tag names correctly -- Julian Andres Klode Wed, 26 Feb 2020 21:29:48 +0100[/code] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1864974/+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 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file
** Package changed: linux (Ubuntu) => kmod (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1864436 Title: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file Status in kmod package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 linux Ubuntu 5.4.0-14.17-generic 5.4.18 linux-modules-5.4.0-15-generic 5.4.0-15.18 Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated error messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864436/+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 1864436] [NEW] depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file
You have been subscribed to a public bug: Ubuntu 20.04 linux Ubuntu 5.4.0-14.17-generic 5.4.18 linux-modules-5.4.0-15-generic 5.4.0-15.18 Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated error messages: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin' ** Affects: kmod (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: focal -- depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file https://bugs.launchpad.net/bugs/1864436 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. -- 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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Tags added: oem-priority originate-from-1863233 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0
New kernel with a fix ?
Changelog
linux (5.4.0-16.19) focal; urgency=medium
* focal/linux: 5.4.0-16.19 -proposed tracker (LP: #1864889)
* system hang: i915 Resetting rcs0 for hang on rcs0 (LP: #1861395)
- drm/i915/execlists: Always force a context reload when rewinding RING_TAIL
I am not having any issues with drm-tip kernel.
I will try 5.4.0-16 later today.
--
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/1862865
Title:
i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Invalid
Status in linux source package in Focal:
Confirmed
Status in mesa source package in Focal:
Invalid
Bug description:
Hi,
Every now and again, my session locks up with the following logged:
| i915 :00:02.0: Resetting rcs0 for hang on rcs0
Most of the time, it recovers on it's own but sometimes locks up
completely requring a reboot. When that happens this is logged:
| Feb 2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54
[i915])
| Feb 2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting
chip for hang on rcs0
| Feb 2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL:
0001}
| Feb 2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in
chrome[5568968fd000+6abe000]
| Feb 2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in
chrome[55ac6372a000+6abe000]
| Feb 2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89
ef be 01 00 00 00 ff 50 58 04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03
01 80 bd 7f ff
| Feb 2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting
rcs0 for hang on rcs0
| Feb 2 10:38:09 dharkan kernel: [71064.575976] i915
[Touch-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package redland - 1.0.17-1.1ubuntu1 --- redland (1.0.17-1.1ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Fri, 14 Feb 2020 15:17:33 -0300 ** Changed in: redland (Ubuntu) Status: In Progress => Fix Released -- 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/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: Fix Committed Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: Fix Released Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: Fix Released Status in libgda5 package in Ubuntu: Fix Released Status in libodb-mysql package in Ubuntu: Fix Released Status in lyricue package in Ubuntu: Fix Released Status in motion package in Ubuntu: Fix Released Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: Fix Released Status in opendnssec package in Ubuntu: Fix Released Status in opensmtpd-extras package in Ubuntu: Fix Released Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: Fix Released Status in pvpgn package in Ubuntu: Fix Released Status in qt4-x11 package in Ubuntu: Fix Released Status in redland package in Ubuntu: Fix Released Status in tango package in Ubuntu: Fix Released Status in tntdb package in Ubuntu: Fix Released Status in voms-mysql-plugin package in Ubuntu: Fix Released Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: Fix Released Status in zoneminder package in Ubuntu: Fix Released Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
bionic pactl log as just boot, after plug headset and remove headset. ** Summary changed: - As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c + As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. ** Description changed: - There will be an dummy output in gnome-contol-center (g-c-c) if + The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. - Reprudced in bionic and focal. + However, in bionic, it will disappear as the headset is plugged and selected. + After it disappears, a reboot won't make it appear again. - In Focal, As the earphone is plugged, dummy output disappears. - As it's unplugged, it appears again. + In Focal, dummy output won't disappear. - Per test in focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + focal: + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Description changed: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. + bionic: + gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 + pulseaudio: 1:11.1-1ubuntu7.4 + In Focal, dummy output won't disappear. focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Attachment added: "pactl-logs.tar" https://bugs.launchpad.net/oem-priority/+bug/1864813/+attachment/5331500/+files/pactl-logs.tar -- 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/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. bionic: gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 pulseaudio: 1:11.1-1ubuntu7.4 In Focal, dummy output won't disappear. focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+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
