[Touch-packages] [Bug 1900335] Re: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Relevant lines from DpkgTerminalLog.txt: Setting up linux-firmware (1.187.3) ... update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic [..] cp: cannot stat '/etc/ykluks.cfg': No such file or directory E: /usr/share/initramfs-tools/hooks/yubikey-luks failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-51-generic with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 You have yubikey-luks installed, which hooks into update-initramfs and attempts to load a configuration file /etc/ykluks.cfg - which does not exist. As a result, the hook, update-initramfs, and configuring the linux-firmware package (which triggers an update-initramfs) fail. This is probably a configuration issue. It could also *possibly* be a bug in yubikey-luks (*may* want to just warn if this configuration file is missing), so I'm reassigning to that for now. Note that yubikey-luks is in universe, so community maintained. ** Package changed: initramfs-tools (Ubuntu) => yubikey-luks (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1900335 Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in yubikey-luks package in Ubuntu: New Bug description: This happened during an upgrade from Ubuntu LTS 18.04 to 20.04. A `dpkg --configure -a` afterwards worked without trouble - bad interaction of install scripts? ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.3 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jkloos 1861 F pulseaudio CasperMD5CheckResult: skip Date: Sun Oct 18 15:31:24 2020 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-02 (230 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 13 7390 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.4 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-18 (0 days ago) dmi.bios.date: 07/07/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/07/2020:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yubikey-luks/+bug/1900335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790205] Re: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.
So, as has been previously stated here, and as is documented in section 5 of the journald.conf man page (install man-db, run 'man 5 journald.conf'), journald will, by default, limit the journals' disk allocation to either a maximum of 10% of available disk space, or to the absolute size of 4GB, whichever is lower. Example 1: You have a 120 GB disk, 70 GB are in use, leaving 50 GB. 10% of 50 GB are 5 GB, but the absolute value of 4 GB is lower, so journald will at most take 4 GB storage on this system (and dynamically less, if the disk grows fuller). Example 2: You have a 20 GB disk, 12 GB are in use, leaving 8 GB. 10% of 8 GB are 800 MB, which is less than 4 GB, so journald will at most take 800 MB storage on this system (and dynamically more or less, if disk allocation changes). Benjamin is now reporting 4.1 GB allocated, which is more than 4 GB, and with the details above, this is unexpected. What could be the reason? These limits are applied both when journald starts, and when vacuuming takes place. So if Benjamins' logs have grown by 100 MB since journald started, this can easily explain this situation. They will be reduced to 4 GB (or less, if the disk runs full) again next time vacuuming takes place (such as when journald is restarted). So unless these limits are considered a problem (why? disk space is cheap, and you can modify them as needed if you're on a special (embedded?) platform), I don't see a problem here. -- 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/1790205 Title: systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is. Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? . as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343 ** Bug watch added: Linux Kernel Bug Tracker #204343 https://bugzilla.kernel.org/show_bug.cgi?id=204343 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc
There is no easy way to gracefully handle weak crypto. It has been known for more than five years that 1024 bit (or rather <2048 bit) DH primes need to be considered weak and should not be used - https://weakdh.org/ - GnuTLS > 3.2 does the right thing in having services which still have not taken action to use contemporary (non weak) crypto fail by default, so that users will become aware of the fact they are (were) connecting insecurely, and these services can be more easily identified and fixed. In some cases, using clients (and software versions of client) which support higher TLS protocol versions can work around this problem (if remote servers support strong ciphers on higher TLS protocol versions; example: https://www.ssllabs.com/ssltest/analyze.html?d=mail.nhs.net=on ). It *may* be possible to continue to allow for insecure connections by setting the GnuTLS priority string to include LEGACY as per https://gnutls.org/manual/html_node/Priority-Strings.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1860461 Title: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnutls28 package in Ubuntu: Confirmed Bug description: After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client with the following error: "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough)." I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and to install 19.10 dependency libhogweed4 3.4.1-1 to fix it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgnutls30 3.6.9-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Tue Jan 21 17:48:39 2020 InstallationDate: Installed on 2017-06-21 (943 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnutls28 UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
** Changed in: gnome-terminal
Importance: Medium => Unknown
** Changed in: gnome-terminal
Status: Confirmed => Unknown
** Changed in: gnome-terminal
Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Unknown
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1191895] Re: networking eventually brought down due to inactivity
Is this something which could be supported by now? gnome-control-center -> power seems to offer a setting to manage wi-fi power saving but in the end this is just a wi-fi on/off switch which immediately brings the device down/up (bug 1751954). Looking through the details of an existing NM wireless configuration profile there are no related (power saving) features exposed on the GUI. "nmcli connection show $UUID" lists a 802-11-wireless.powersave (default: 0) setting. https://developer.gnome.org/NetworkManager/stable/settings-802-11-wireless.html Is this what brings the interface down after some ~ 10 minutes of user input inactivity / ~ 5 minutes of blank screen? If so, could this be exposed on the GUI? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1191895 Title: networking eventually brought down due to inactivity Status in network-manager package in Ubuntu: Confirmed Bug description: For various reasons, I like to be able to ssh in to my nexus 4. I have noticed with current saucy (and raring before it), after some time of inactivity the screen goes blank (fine), but then occasionally after some more time after that, networking is brought down (wifi) if there is no network activity. If I continuously ping the device, networking stays up. If I keep the screen from blanking, networking stays up. The current behavior is different than the behavior on android, where I can get various notifications for facebook, email, etc when the screen is blank. HARDWARE=mako JENKINS_BUILD=saucy-11 UBUNTU=ubuntu-touch-saucy-armhf ubuntu/platform-api=:68 hybris=0.1.0+git20130606+c5d897a-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1191895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848900] Re: blank display with Eoan Ermine live DVD on Rysen 2200G
** Attachment added: ""journalctl -b -1" (failed boot) for other user" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log ** Summary changed: - blank display with Eoan Ermine live DVD on Rysen 2200G + Blank display with Eoan Ermine live DVD on Ryzen 3 2200G -- 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/1848900 Title: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg package in Ubuntu: New Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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 xserver.bootTime: Sat Oct 19 23:52:52 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0
[Touch-packages] [Bug 1848900] Re: blank display with Eoan Ermine live DVD on Rysen 2200G
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G (Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2 08/08/2018) today, whose log of a failed (standard) boot (to black screen) showed kernel: WARNING: CPU: 2 PID: 255 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:932 dcn10_verify_allow_pstate_change_high.cold+0xc/0x23d [amdgpu] which seems to be discussed at https://bugs.freedesktop.org/show_bug.cgi?id=109628 ** Bug watch added: freedesktop.org Bugzilla #109628 https://bugs.freedesktop.org/show_bug.cgi?id=109628 -- 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/1848900 Title: Blank display with Eoan Ermine live DVD on Ryzen 3 2200G Status in xorg package in Ubuntu: New Bug description: Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and 55-75 Hz monitor. Booting Xubuntu 19.10 live iso with safe graphics options did give a stable desktop display, but xubuntu@xubuntu:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080 default connected 1920x1080+0+0 0mm x 0mm 1920x1080 77.00* xubuntu@xubuntu:~$ The monitor is only supposed to have a maximum vertical refresh rate of 75 Hz. Xrandr reports 77 Hz as the only choice. The monitor reports 60 Hz, not that I trust the monitor. Swapping monitors and running many reboots the situation seems to be... Old versions of Ubuntu (Bionic and Dingo) can handle the hardware. Standard boot sometimes gives a blank screen. Standard boot sometimes gives a badly pixelated display (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it). Connecting a 144 Hz monitor convinces something (the firmware?) that fast refreshes are OK on a slow monitor, or at least it fails to reread and abide by the slow monitor's limitations when swapping back. Something, I don't know what, convinces the computer to run the display at 60 Hz, sometimes. The motherboard has three video ports; DP, HDMI and VGA (using an onboard DP? to VGA converter chip). The fast monitor has DP, HDMI and VGA ports, but I only experimented with the DP connection. The slow monitor has VGA and DVI-D ports. I experimented with VGA to VGA and HDMI via a passive adapter to DVI. When running in the badly pixelated mode xorg seems to think that the VGA port is "DP-1". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: XFCE Date: Sun Oct 20 00:17:34 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash nomodeset --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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
[Touch-packages] [Bug 1792643] Re: apport does not upload wayland or gnome-shell crash data
This issue seems to have occurred to me today (and several times previously) - when I returned to my computer after a while (the screen had entered power saving mode), the gnome-shell process (on XWayland) failed. Neither after logging in to gnome-shell / Xwayland nor after logging out and back into gnome-shell / Xorg was I prompted to submit a bug report about it, even though there was /var/crash/_usr_bin_gnome- shell.1000.crash. Killing and restarting whoopsie and update-notifier did not change it. Manually generating and submitting the report using apport-cli /var/crash/_usr_bin_gnome-shell.1000.crashdid succeed for me, however (however the automation to do so failed). -- 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/1792643 Title: apport does not upload wayland or gnome-shell crash data Status in apport package in Ubuntu: Confirmed Bug description: uname -a Linux smeagol 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 In trying to upload .crash data for bug 1789962 "gnome-shell segfaults in Wayland when display is turned off while Kodi running" I determined that apport-cli and friends were never able to upload the .crash files. The URL where they should appear is: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 Earlier, I did upload the .crash files directly and was told by the defect reviewer that: _usr_bin_Xwayland.1000.crash: Stack trace mostly unreadable (missing symbols) _usr_bin_gnome-shell.1000.crash: Stack trace is missing You can see the other bug for details, here is the last comment that I added (so far): I deleted all entries in /var/crash and /var/lib/whoopsie. I recreated the problem ls -l /var/crash total 92136 -rw-r- 1 fbacher whoopsie 40426131 Sep 14 14:52 _usr_bin_gnome-shell.1000.crash -rw-r- 1 fbacher whoopsie 6167683 Sep 14 14:53 _usr_bin_Xwayland.1000.crash -rw-r- 1 fbacher whoopsie 47750972 Sep 14 14:53 _usr_lib_x86_64-linux-gnu_kodi_kodi-wayland.1000.crash fbacher@smeagol$ apport-cli _usr_bin_gnome-shell.1000.crash *** Error: Invalid problem report No such file or directory Press any key to continue... fbacher@smeagol$ apport-cli /var/crash/_usr_bin_gnome-shell.1000.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (40.6 MB) E: Examine locally V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/E/V/K/I/C): S *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. < Deleted lots and lots of ellipsis > echo $? 0 total 4 ls -l /var/lib/whoopsie -rw--- 1 root root 128 Sep 13 18:39 whoopsie-id sudo cat /var/lib/whoopsie/whoopsie-id 39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 Checked the URL: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 No entries since 08/11. None for wayland, gnome-shell or Kodi. I checked for over 5 minutes. So perhaps something is going bad on my end, but I just don't know what or how to debug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1792643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
Hi. I am just a fellow Ubuntu user, but I am afraid this bug report is most likely not something anyone could solve, because so many different chipsets and issues are being discussed here (I assume this is also why no developers felt inclined to touch it so far). I very much recommend that anyone still experiencing wireless issues should (look for, and if none exists) file a new bug against their wireless driver, and anyone with Ethernet issues should (look for, and if none exists) file a new bug against their Ethernet driver. Your drivers will usually be listed in the output of one of these commands: lspci -knn lsusb You are also welcome to check back with community support to check whether a fix (or a workaround) is already available for your very issue, or just to get help with filing a bug report that is specific and can get handled more easily. https://ubuntu.com/support/community-support If TylerKinkade's issue (where both Wireless and Ethernet disconnect at the same time, on a now supported Ubuntu version) persists then it is more likely a platform (hardware / mainboard / ACPI / firmware) specific issue and should be treated as such, affecting Inspiron 5567 with this specific Ubuntu version (was 16.04.1 originally). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric
[Touch-packages] [Bug 1836236] Re: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131
This command was reported to successfully work around this bug: sudo sed -i 's/^Automatically/# Automatically/g' /var/lib/dpkg/info /base-files.postinst It changes any lines starting with "Automatically" into comments, which lets the script finish properly when you run: sudo dpkg --configure base-files Or just run this afterwards: sudo apt -f install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1836236 Title: 9.4ubuntu4.9: Broken package because of missing "#" @ /var/lib/dpkg/info/base-files.postinst +131 Status in base-files package in Ubuntu: Confirmed Bug description: Trying to install this on xenial results in: Setting up base-files (9.4ubuntu4.9) ... /var/lib/dpkg/info/base-files.postinst: 131: /var/lib/dpkg/info/base-files.postinst: Automatically: not found dpkg: error processing package base-files (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: base-files E: Sub-process /usr/bin/dpkg returned an error code (1) Because there is a missing comment "#" at the beginning of line 131 of /var/lib/dpkg/info/base-files.postinst, ie: Automatically added by dh_systemd_start ^-- # ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1836236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835095] Re: Lubuntu initrd images leaking cryptographic secret when disk encryption is used
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835095 Title: Lubuntu initrd images leaking cryptographic secret when disk encryption is used Status in initramfs-tools package in Ubuntu: New Bug description: Hello! I've had a short discussion about this issue on lubuntu irc, and I was asked to open a bug report. Basically I only tested this on lubuntu 19.04 x64 live image on a UEFI system, I haven't tested other ubuntu flavors. Anyway, I was poking around with disk encryption, and I noticed that lubuntu live image uses a graphical installation tool called Calamares. This tool has an option to encrypt the hard disk during installation, and the encryption setup that is used is the newer one with /boot folder as part of the encrypted rootfs. Traditionally the installers used to setup encryption where there is a main LUKS- encrypted rootfs volume on the HDD and a separate unencrypted /boot partition where the grub config files, the kernel and the initrd images reside. Ever since grub2 added support for LUKS several distros have apparently moved to the newer scheme which is very similar to the one that was first described by Pavel Kogan in his blog. A) https://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/ B) https://www.pavelkogan.com/2015/01/25/linux-mint-encryption/ This new scheme stores the rootfs (including the /boot folder) on a single LUKS-encrypted partition with two keyslots in use. One of the keyslots is normally a passphrase that is used in the first stage by the grub2 EFI image as pre-boot authentication. It serves to decrypt the rootfs, access the contents of /boot and copy the config, kernel and initrd image to RAM. Once done, grub2 then forgets the passphrase and closes the encrypted volume. The system will continue to boot, but at this point the rootfs will now have to be decrypted a second time - this time by the kernel/initrd so it can be mounted. Normally this is the point where the user would be asked to enter a passphrase for the second time, but for convenience reasons (to automate the process) a second LUKS keyslot and a keyfile are used instead. The file /crypto_keyfile.bin is generated during the installation phase. This is the secret keyfile that is used to unlock the other LUKS keyslot and decrypt the rootfs. It is properly protected with owner set to root:root and file permissions 600 (-rw---). Unfortunately the key is not of much use while it resides inside the encrypted volume that it is supposed to decrypt. This is where initramfs-tools comes into play. I believe there is a special hook inside /usr/share/initramfs-tools/hooks that is responsible for copying this crypto_keyfile.bin file into appropriate initrd image. This image that now contains the secret keyfile is copied into RAM during the first decryption stage by the grub2. While the original secret keyfile /crypto_keyfile.bin is protected: $ ls -l / ... -rw--- 1 root root 2048 jul 2 18:34 crypto_keyfile.bin ... $ sha1sum /crypto_keyfile.bin sha1sum: /crypto_keyfille.bin: Permission denied $ sudo sha1sum /crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /crypto_keyfile.bin The second copy (the one inside initramfs image) is not: $ ls -l /boot ... -rw-r--r-- 1 root root 68149041 jul 2 18:35 initrd.img-5.0.0-13-generic As you can see, the initramfs images that are generated by mkinitramfs will have the user:group set to root:root, but their access flags will be 644 (-rw-r--r--). This means that any user or even a script that has read access to the file system can read and extract the secret keyfile from an initramfs image. Run as user: $ unmkinitramfs /boot/initrd.img-5.0.0-13-generic /tmp $ sha1sum /tmp/main/crypto_keyfile.bin 7a1c44fd036510cc02e32c094bd16b4a76a7f14c /tmp/main/crypto_keyfile.bin Would there be any adverse effects, if we were to set mkinitramfs (i.e. via a hook) to always set file permissions of initramfs images to 600 whenever this type of disk encryption is used? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833829] Re: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
** Summary changed: - High memory usage by Xorg. + High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 -- 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/1833829 Title: High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390 Status in xorg package in Ubuntu: New Bug description: After some continued use of the system (Kubuntu (18.04)) Xorg accumulates a lot of RAM space. From that the space only increments and doesn't decrease. Hardware Specs : 1. Intel core-i5 6300 HQ 2. Nvidia GTX 960M Software Specs : 1. Kubuntu 18.04 2. KDE Plasma shell version 5.12.7 Something interesting to note is that I have not experienced the same behavior from Xorg when I switch the GPU to Intel's Integrated graphics. It is entirely possible that I might not have been able to trigger those situation with Intel, because after seeing logs I couldn't make out why this was happening. Also for the timeline I have used the system for over an year without any such issue arising. It was the second week of June 2019 to present day I have seen this problem. Xorg log : http://paste.ubuntu.com/p/nc3pMF4xsb/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sun Jun 23 05:06:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:0706] Subsystem: Dell GM107M [GeForce GTX 960M] [1028:0706] InstallationDate: Installed on 2019-06-21 (1 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 1bcf:28b0 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 413c:301a Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7559 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=f046965f-7377-42b2-86ba-febdbcabfc9b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.7 dmi.board.name: 0H87XC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.7:bd12/13/2017:svnDellInc.:pnInspiron7559:pvr1.2.7:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1833829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833593] [NEW] fstrim.timer always triggers at 00:00, use RandomizedDelaySec
Public bug reported: fstrim.timer always triggers at 00:00: $ systemctl list-timers fstrim.timer NEXT LEFTLAST PASSED UNIT ACTIVATES Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days ago fstrim.timer fstrim.service 1 timers listed. Pass --all to see loaded but inactive timers, too. This can be an issue if concurrent runs cause increased I/O load on multiple servers which are part of the same system architecture (I have no hard facts via monitoring on this, but assume this can be an issue). /lib/systemd/system/fstrim.timer does not try to randomize the start time. systemd.timer(5) suggests that RandomizedDelaySec can be used to introduce variable start times, allowing for balancing out the (suspected increased) I/O load across multiple systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 19:52:17 2019 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1833593 Title: fstrim.timer always triggers at 00:00, use RandomizedDelaySec Status in util-linux package in Ubuntu: New Bug description: fstrim.timer always triggers at 00:00: $ systemctl list-timers fstrim.timer NEXT LEFTLAST PASSED UNIT ACTIVATES Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days ago fstrim.timer fstrim.service 1 timers listed. Pass --all to see loaded but inactive timers, too. This can be an issue if concurrent runs cause increased I/O load on multiple servers which are part of the same system architecture (I have no hard facts via monitoring on this, but assume this can be an issue). /lib/systemd/system/fstrim.timer does not try to randomize the start time. systemd.timer(5) suggests that RandomizedDelaySec can be used to introduce variable start times, allowing for balancing out the (suspected increased) I/O load across multiple systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.3 ProcVersionSignature: Ubuntu 5.0.0-17.18~18.04.1-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 20 19:52:17 2019 SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1833593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832802] Re: disco: curl error while loading shared libraries: libssl.so.1.0.0
*** This bug is a duplicate of bug 1832801 *** https://bugs.launchpad.net/bugs/1832801 ** This bug has been marked a duplicate of bug 1832801 disco: curl error while loading shared libraries: libssl.so.1.0.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1832802 Title: disco: curl error while loading shared libraries: libssl.so.1.0.0 Status in curl package in Ubuntu: New Bug description: Linux 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:52:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DISTRIB_RELEASE=19.04 DISTRIB_DESCRIPTION="Ubuntu 19.04" curl: Installed: 7.64.0-2ubuntu1.1 Candidate: 7.64.0-2ubuntu1.1 Version table: *** 7.64.0-2ubuntu1.1 1001 1001 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.64.0-2ubuntu1 1001 1001 http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/main amd64 Packages When I run curl, I get the following error: curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory On other disco machines I'm not experiencing this issue. I apt purged openssl/libssl/curl and re-installed, but the error persists. I'm sure my system has some issue, but I'm unable to figure it out, and this felt like a bug as curl was working before upgrade to disco. I tried proposed packages to see if openssl 1.1.1b-1ubuntu2.2 instead of 1.1.1b-1ubuntu2 would make any difference, but the error persists. me@mbp:/usr/lib/x86_64-linux-gnu$ curl curl: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory me@mbp:/usr/lib/x86_64-linux-gnu$ which curl /usr/bin/curl me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep curl ii curl 7.64.0-2ubuntu1.1 amd64command line tool for transferring data with URL syntax ii libcurl3-gnutls:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4:amd64 7.64.0-2ubuntu1.1 amd64easy-to-use client-side URL transfer library (OpenSSL flavour) ii python3-pycurl 7.43.0.2-0.1 amd64Python bindings to libcurl (Python 3) me@mbp:/usr/lib/x86_64-linux-gnu$ sudo dpkg -l | grep ssl ii android-libboringssl8.1.0+r23-2 amd64Google's internal fork of OpenSSL for the Android SDK rc docbook-dsssl 1.79-9.1 all modular DocBook DSSSL stylesheets, for print and HTML ii libflac++6v5:amd64 1.3.2-3 amd64Free Lossless Audio Codec - C++ runtime library ii libflac8:amd64 1.3.2-3 amd64Free Lossless Audio Codec - runtime C library ii libflac8:i386 1.3.2-3 i386 Free Lossless Audio Codec - runtime C library ii libio-socket-ssl-perl 2.060-3 all Perl module implementing object oriented interface to SSL sockets ii libnet-smtp-ssl-perl1.04-1 all Perl module providing SSL support to Net::SMTP ii libnet-ssleay-perl 1.85-2ubuntu3 amd64Perl module for Secure Sockets Layer (SSL) ii libssl-dev:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - development files ii libssl1.1:amd64 1.1.1b-1ubuntu2.2 amd64Secure Sockets Layer toolkit - shared libraries ii libssl1.1:i386 1.1.1b-1ubuntu2.2 i386 Secure Sockets Layer toolkit - shared libraries ii libwavpack1:amd64 5.1.0-5ubuntu0.1amd64audio codec (lossy and lossless) - library ii libwavpack1:i386 5.1.0-5ubuntu0.1
[Touch-packages] [Bug 1831351] Re: Please provide option to continue bug report from different computer
Thanks for explaning that it is possible to create a bug report on one system, then manually copy it to another computer where the bug report can then be submitted using ubuntu-bug. This is not exactly as convenient as being able to run apport on one system to gather debugging info, submit this to Launchpad (but not create the bug, yet), then access the URL printed from another computer which then allows for SSO authentication and bug submission from this other computer. So a bit of a different use case, too. But, yes, it is mostly nice-to-have - (not having reviewed the code) it just seems like it should be easy to implement since this is what ubuntu-bug already does when it is unable to create its GUI. -- 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/1831351 Title: Please provide option to continue bug report from different computer Status in apport package in Ubuntu: Incomplete Bug description: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu-bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552577] Re: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123]
I do not know how priorities in bug handling are set, but I do wonder what may be the reason to not handle this rather common (30 dupes) critical (crash) bug on a 'main' package for the past three years - could someone explain this to me? Thanks in advance. -- 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/1552577 Title: apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] Status in Apport: New Status in GTK+: Expired Status in apport package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/92c580cf48dae63a366ee45b28a16be710f70347 --- Crash displayed after logging in. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 1 22:13:24 2016 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2016-02-21 (10 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160208 InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk SegvAnalysis: Segfault happened at: 0x7f3a0219cb89:mov(%rbx),%rdi PC (0x7f3a0219cb89) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1552577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831351] [NEW] Please provide option to continue bug report from different computer
Public bug reported: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu- bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1831351 Title: Please provide option to continue bug report from different computer Status in apport package in Ubuntu: New Bug description: There are some situations where it is desirable to gather debugging information on a system affected by a bug, but to login (to Launchpad/Ubuntu SSO) and complete editing this bug report from a different system. This is already implemented for situations where the affected system runs headless, i.e. servers without a graphical display. However, this should also be a user choice exposed as a command line option to ubuntu-bug (which, at least according to --help it currently is not). A common use case where this would be nice to have is testing software in a VM, but not wanting to expose Ubuntu SSO credentials to this VM (e.g. for security concerns). Another use case is a need to report a serious bug in the default web browser where this web browser is unable to access any websites. There is a workaround: DISPLAY= ubuntu-bug somepackage Unfortunately this means the debugging data collection phase will provide a text-only UI instead of the nicer / more user-friendly GTK one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.6 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 01:24:07 2019 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-01-17T11:47:59.939850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831025] Re: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
Dear Adam, the log you provided does not seem to indicate an issue with acquiring data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does not support your Ubuntu release (18.04 / bionic). So this appears to not be a bug, just use of an incompatible PPA, making this more of a support request. I'm therefore changing the status to "invalid" - should I have missed relevant facts you are welcome to undo this change. Should you need further support with this, please consider one of the following options: https://www.ubuntu.com/support https://www.ubuntu.com/support/community-support Thanks, Tom -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1831025 Title: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list Status in apt package in Ubuntu: Invalid Bug description: The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu- keepass-bionic.list: deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main causes sudo apt update to fail for this entry with the error: 404 Not Found [IP: 91.189.95.83 80] Full transcript: $ sudo apt update Hit:1 http://deb.playonlinux.com bionic InRelease Hit:2 http://pl.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/bookworm-team/bookworm/ubuntu bionic InRelease Hit:4 http://pl.archive.ubuntu.com/ubuntu bionic-updates InRelease Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease Hit:6 http://pl.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 Release Hit:8 http://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease Hit:9 http://pl.archive.ubuntu.com/ubuntu bionic-proposed InRelease Ign:10 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic InRelease Hit:11 https://repo.skype.com/deb stable InRelease Hit:12 http://ppa.launchpad.net/elementary-os/stable/ubuntu bionic InRelease Hit:13 http://ppa.launchpad.net/fixnix/netspeed/ubuntu bionic InRelease Hit:14 http://dl.winehq.org/wine-builds/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:16 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease Hit:18 http://ppa.launchpad.net/noobslab/themes/ubuntu bionic InRelease Hit:20 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease Hit:21 http://ppa.launchpad.net/unity7maintainers/unity7-desktop/ubuntu bionic InRelease Hit:22 http://ppa.launchpad.net/yktooo/ppa/ubuntu bionic InRelease Err:23 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release 404 Not Found
[Touch-packages] [Bug 1830616] Re: $ ubuntu-bug xorg
Thanks for your report. I'm not a developer, just having a quick glance on your logs: Your system log shows I/O errors on /dev/sdb, a 1.00 TB storage. This can be due to bad cabling / connectors or due to a bad disk. Additionally, the USB connection to the WD My Passport 25E1 drive was reset twice (this may be a follow-up issue). Your system log refers to several "Firmware Bug", "ACPI Warning" and "ACPI Error" events. Some of these refer to your graphics card / chipset. Firmware bugs can sometimes be worked around by Linux, but the better approach is a firmware upgrade. Your system currently runs BIOS 40CN28WW(V2.14) 10/07/2011 BIOS version 40CN33WW (released on 02 Sep 2012) is the latest version available: https://pcsupport.lenovo.com/de/en/products/LAPTOPS-AND-NETBOOKS/LENOVO-G-SERIES-LAPTOPS/LENOVO-G570-NOTEBOOK/downloads/DS018378 The X graphics server (which provides the foundation to make your graphical desktop work) seems to start up fine with radeon (AMD/ATI graphics) acceleration. Summing up, at this point, these seem to be hardware / firmware specific issues, not bugs in Ubuntu. Because of this, I will mark this bug as "incomplete". If you can solve these hardware / firmware issues and the system still fails to boot properly, please update this bug report and reset the status to "new" (or file a new bug). If you would like further support, both professional (commercial) and volunteer / community support are available: https://www.ubuntu.com/support https://www.ubuntu.com/support/community-support ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1830616 Title: $ ubuntu-bug xorg Status in xorg package in Ubuntu: Incomplete Bug description: My system was not loading and it is showing the black screen while turning on and I need to switch off and switch on the laptop several times to turn on my laptop this might be an issue with the graphic card. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 27 18:11:18 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu 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:397a] Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] [1002:68e4] (prog-if 00 [VGA controller]) Subsystem: Lenovo Radeon HD 6370M/7370M [17aa:397a] InstallationDate: Installed on 2019-04-25 (31 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20079 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=14d2a429-ed18-409f-a9ea-dc0593e5aa1b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 40CN28WW(V2.14) dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: LENOVO dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvr40CN28WW(V2.14):bd10/07/2011:svnLENOVO:pn20079:pvrLenovoG570:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: IDEAPAD dmi.product.name: 20079 dmi.product.sku: HuronRiver_CRB dmi.product.version: Lenovo G570 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1826735] [NEW] .uuid files in font directories not removed during purge
Public bug reported: On Ubuntu 19.04 (amd64): Removing fonts-liberation2 (2.00.5-1) ... dpkg: warning: while removing fonts-liberation2, directory '/usr/share/fonts/truetype/liberation2' not empty so not removed Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ... dpkg: warning: while removing fonts-opensymbol, directory '/usr/share/fonts/truetype/openoffice' not empty so not removed ls -a against these directories shows there's still .uuid files in there which dpkg -S is unaware of. Upstream bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=897040 ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Affects: fontconfig (Debian) Importance: Unknown Status: Unknown ** Tags: disco ** Bug watch added: Debian Bug tracker #897040 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 ** Also affects: fontconfig (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897040 Importance: Unknown Status: Unknown ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1826735 Title: .uuid files in font directories not removed during purge Status in fontconfig package in Ubuntu: New Status in fontconfig package in Debian: Unknown Bug description: On Ubuntu 19.04 (amd64): Removing fonts-liberation2 (2.00.5-1) ... dpkg: warning: while removing fonts-liberation2, directory '/usr/share/fonts/truetype/liberation2' not empty so not removed Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ... dpkg: warning: while removing fonts-opensymbol, directory '/usr/share/fonts/truetype/openoffice' not empty so not removed ls -a against these directories shows there's still .uuid files in there which dpkg -S is unaware of. Upstream bug report: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=897040 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1826735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822736] Re: Passwords longer than 255 characters break authentication
It is yet unclear what the root cause of this issue is - libpam, crypt, passwd and sudo seem like primary suspects. The 256 character password is hashed to a value which still allows a TTY login to succeed. Also, passwd run by a different user in the context of the affected user (using sudo) still works. So apparently it only breaks for the logged-in user. This may help identify the root cause. pam_unix(8) (on bionic) states: The maximum length of a password supported by the pam_unix module via the helper binary is PAM_MAX_RESP_SIZE - currently 512 bytes. The rest of the password provided by the conversation function to the module will be ignored. Regarding passwd, I was told this on IRC: passwd uses getpass() to read the password from the user, and testing just getpass() alone shows it will return up to 4095 bytes long (i.e. truncates at that length). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1822736 Title: Passwords longer than 255 characters break authentication Status in pam package in Ubuntu: Confirmed Bug description: DISCUSSION When a password longer than 255 characters is set for any user account, this user will become unable to authenticate when running 'sudo' or 'passwd'. IMPACT This affects 18.04.2 systems, whether they were installed using Desktop (ubiquity) or Server (subiquity) installers. It may also affect other releases - this is yet untested. Tagged 'security' since these utilities then deny service to this user. REPRODUCTION # Add user 'test' with password 'testtest' sudo adduser --gecos '' test # Add user 'test' to the 'sudo' group sudo adduser test sudo # Become user 'test' sudo -iu test # Verify user 'test' can run commands via sudo sudo whoami # Change password of 'test' to this 255 character long password: 123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345 passwd # Verify user 'test' can run commands via sudo with the new password set sudo -k sudo whoami# should report "root" # Change password of 'test' to 'testtest': passwd # Verify user 'test' can run commands via sudo with the new password set sudo -k sudo whoami# should report "root" # Change password of 'test' to this 256 character long password: 1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456 passwd # Verify user 'test' can run commands via sudo with the new password set sudo -k sudo whoami# should report "root" # This authentication fails, as sudo does not accept the 256 character password. # Attempting to change this password to a different value also fails: passwd # Effectively, user 'test' is now unable to use sudo, or to change their password. # The 'login' command, run by root, does, however, still enable user 'test' to login using the newly set 256 character password. # At the same time, a different restricted user who is a member of the 'sudo' group can still set a new password for 'test' (after authenticating to sudo with their own password) by supplying the current 256 character password using: sudo -u test passwd # Finally, to clean up sudo deluser --remove-home test ADDITIONAL OBSERVATIONS * A root-initiated 'login' command still allows this user to authenticate. * A different restricted user who is a member of the 'sudo' group can still set a new password for for this users' account (after authenticating to sudo with their own password) by supplying the >=256 character password CREDIT This was originally reported by 'Fieldy', I just reproduced it / filed this bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpam0g 1.1.8-3.6ubuntu2.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 2 09:39:39 2019 SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1822736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically
Not breached here: $ journalctl -b -u systemd-journald.service -n 1 -- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38 CET. -- Mar 20 13:32:03 debby2017 systemd-journald[699]: System journal (/var/log/journal/f8b692c8bb791fe2804f3d5a5905148b) is 1.8G, max 1.8G, 0B free. $ journalctl --disk-usage Archived and active journals take up 1.8G in the file system. However, with systemd-journald persistence enabled, and classic logging daemons not removed (and still logging) on upgrades, you can end up with much data stored in /var/log, a lot more than there used to be in the past, which could cause problems, also (but not only) if combined with bug 1785321. -- 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/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically Status in systemd package in Ubuntu: Incomplete Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically
So I wasn't aware of this size hard limit on persistent storage - I just noticed that it is 'already' allocating 1.8GB, but this is indeed less than the 10% of the file system the man page says it will consume. So from my personal point of view this is a non-issue then (ideally Benjamin will also provide feedback, though) - but the new behavior may be worth discussing in release notes. -- 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/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically Status in systemd package in Ubuntu: Incomplete Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically
$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage 2>/dev/null -37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon 2018-09-10 08:05:57 CEST Archived and active journals take up 1.8G in the file system. My interpretation is my systems' situation is that 37 sessions were recorded, starting Sept 10, 2018 (~ three months ago), and that logs consume 1.8 GB altogether. I don't know for sure whether rotation does (not) take place, but it doesn't look kike it does, and I think 3 months of full logs are too much. If, however, it's intentional, then this would mean changed system requirements (higher storage capacity on the root file system (/)) for Ubuntu since introduction of systemd-journald (which should go into the release notes at least). -- 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/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically Status in systemd package in Ubuntu: Confirmed Bug description: After running Bionic for 3 months, I had 2.6 GB of journals. I would not expect from a normal desktop user that they should have to run commands like `sudo journalctl --vacuum-time=10d`. I would nominate this command as a sane default to have running at each reboot to ensure that logs do not exceed 500 MB: sudo journalctl --vacuum-size=500M Supposedly, a server should by default retain more logs, so perhaps this should be implemented through a configuration package "systemd- configuration-desktop" as a dependency of the ubuntu-desktop meta package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798990] [NEW] apport-gtk segfaults when pointed to invalid X window
Public bug reported: Pointing ubuntu-bug to a non-existing X window makes apport-gtk segfault: myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused Segmentation fault (core dumped) myrestricteduser@ubuntu1804amd64~$ This affects at least bionic and cosmic (crash reports were uploaded). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportLog: ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: called for pid 7617, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: script: /usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.6 (command line "/usr/bin/python3 /usr/share/apport/apport-gtk ubiquity") ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: debug: session gdbus call: (true,) ERROR: apport (pid 7619) Sat Oct 20 20:09:23 2018: wrote report /var/crash/_usr_share_apport_apport-gtk.1000.crash ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:120:7268297:2018-10-20 20:11:08.434944152 +0200:2018-10-20 20:11:09.434944152 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 664:1000:120:0:2018-10-20 20:11:18.930962176 +0200:2018-10-20 20:11:18.930962176 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 20:12:03 2018 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-15 (66 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1798990 Title: apport-gtk segfaults when pointed to invalid X window Status in apport package in Ubuntu: New Bug description: Pointing ubuntu-bug to a non-existing X window makes apport-gtk segfault: myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity Unable to init server: Could not connect: Connection refused Unable to init server: Could not connect: Connection refused Segmentation fault (core dumped) myrestricteduser@ubuntu1804amd64~$ This affects at least bionic and cosmic (crash reports were uploaded). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportLog: ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: called for pid 7617, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: script: /usr/share/apport/apport-gtk, interpreted by /usr/bin/python3.6 (command line "/usr/bin/python3 /usr/share/apport/apport-gtk ubiquity") ERROR: apport (pid 7619) Sat Oct 20 20:09:19 2018: debug: session gdbus call: (true,) ERROR: apport (pid 7619) Sat Oct 20 20:09:23 2018: wrote report /var/crash/_usr_share_apport_apport-gtk.1000.crash ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CrashReports: 640:1000:120:7268297:2018-10-20 20:11:08.434944152 +0200:2018-10-20 20:11:09.434944152 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.crash 664:1000:120:0:2018-10-20 20:11:18.930962176 +0200:2018-10-20 20:11:18.930962176 +0200:/var/crash/_usr_share_apport_apport-gtk.1000.upload CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 20:12:03 2018 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to bionic on 2018-08-15 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1798990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
TJ is right, I also confirmed this issue on a freshly installed 18.04.1 x86_64 Desktop VM last night. After enabling 'proposed' and installing all pending updates, 'groups' in a terminal returned just the users primary group. I then restored a snapshot taken right after the 18.04 installation (but with 'proposed' already enabled), and installed all pending updates again, this time one by one, but could not reproduce it then. I don't have any indication that the outcome would have been any different without 'proposed'. So it remains unclear to me how to reproduce this reliably. It is clear that it is possible to reproduce this (occasionally) on a fresh 18.04.1 installation. And also on 16.04.5. So I do think it will affect many. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
I observe what is likely the same problem on XUbuntu 16.04.5, running these commands in xfce4-terminal: user1@mysystem:~$ lsb_release -ds;cat /proc/version;echo $SHELL;groups;groups $(whoami) Ubuntu 16.04.5 LTS Linux version 4.15.0-29-generic (buildd@lcy01-amd64-024) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 /bin/bash user1 user1 : user1 adm disk fax cdrom sudo dip plugdev users lxd lpadmin sambashare libvirtd vboxusers user1@mysystem:~$ ps f PID TTY STAT TIME COMMAND 3544 pts/2Ss 0:00 bash 3582 pts/2R+ 0:00 \_ ps f user1@mysystem:~$ cat /proc/3544/loginuid;echo 4294967295 Everything behaves correctly on tty1 or after sudo login + login as user1 on the terminal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
** Summary changed: - No network connectivity after upgrade from 16.04 to 16.10 + No network connectivity (NIC unmanaged) after upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine
The file I'm testing with has a "H264 - MPEG-4 AVC (part 10) (avc1)" video track. -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Confirmed Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574354] Re: playing .mp4 in VLC freezes machine
I'm on Ubuntu 16.04.3 with mainline kernel Linux version 4.13.2-041302-generic (kernel@tangerine) (gcc version 7.2.0 (Ubuntu 7.2.0-3ubuntu1)) #201709132057 SMP Thu Sep 14 00:59:32 UTC 2017 and mesa 1:17.3~git170914191100.7ffd4d2~x~padoka0 and X from the Padoka PPA. OpenGL renderer string: Radeon RX 580 Series (POLARIS10 / DRM 3.18.0 / 4.13.2-041302-generic, LLVM 6.0.0) With default VLC configuration (default Ubuntu package) I see the symptoms Donald describes in #18. While discussing this in #radeon on Freenode, it was suggested to me to try a different video output driver in VLC. It turns out it default to "automatic", which is, in this configuration, VDPAU output. And this causes said problems. Switching to "OpenGL GLX video output (XCB)" works around the issue. So this seems to be an issue with VDPAU, but I could not tell on which end. Does this workaround (switching to a different video output driver) work for you, too? -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Confirmed Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
This is apparently a bug, more precisely a regression (#8) in either Ubuntu's accountservice or lightdm. This also affects trusty (as I have tested), so adding tag. There is no patch, yet, removing tag (set in #21), renaming image in #21. ~alisalama has not handled this bug since April, I assume it is not a person, so removing assignment. Hopefully ~ubuntu-desktop can take a look at this bug sooner or later. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: Confirmed Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Confirmed Status in ifmail package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in netqmail package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Fix Released Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667113] Re: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types)
** Tags removed: patch ** Tags added: trusty ** Changed in: libvirt (Ubuntu) Assignee: ali salama (alisalama) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1667113 Title: System users appears in Ligthdm and user switcher (Accountsservice has no filter for shell types) Status in accountsservice package in Ubuntu: Confirmed Status in base-passwd package in Ubuntu: Invalid Status in ceph package in Ubuntu: Confirmed Status in ifmail package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in netqmail package in Ubuntu: Confirmed Status in sddm package in Ubuntu: Fix Released Bug description: "Technical" user libvirt Qemu appears in the list of user in Ligthdm, among the real regular users. It probably shouldn't ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libvirt-bin 2.5.0-3ubuntu2 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Wed Feb 22 22:09:24 2017 InstallationDate: Installed on 2017-02-01 (21 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170201) KernLog: SourcePackage: libvirt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1667113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
This is not fixed. What we have is a reliable workaround to a bug which apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session package installed. Flatpak packages provided by the PPA at https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly others) indirectly depend on this package and cause it to be installed (but this issue which seems to be a bug in Ubuntu 16.04 is not this PPA's fault). $ apt-rdepends --reverse dbus-user-session Reading package lists... Done Building dependency tree Reading state information... Done dbus-user-session Reverse Depends: xdg-desktop-portal (0.8-0alexlarsson2~xenial) Reverse Depends: xdg-desktop-portal-gtk (0.7-0alexlarsson2~xenial) xdg-desktop-portal Reverse Depends: xdg-desktop-portal-gtk (0.7-0alexlarsson2~xenial) xdg-desktop-portal-gtk ** Also affects: dbus (Ubuntu) Importance: Undecided Status: New -- 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/1689825 Title: gnome-keyring not unlocked on boot Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: New Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
