[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files
It looks as if the source of this problem has been identified. How long
should it take to get the fix pushed into Ubuntu updates? I assume that
it will be.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not deleting autosave files
Status in Evolution:
Unknown
Status in evolution package in Ubuntu:
In Progress
Status in libcanberra package in Ubuntu:
Triaged
Bug description:
Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
was installed with the distribution on a new system and received
settings imported from an earlier version on another computer.
When composing an email, if the process takes long enough an autosave
file is created as ~/.local/share/evolution/.evolution-
composer.autosave-xx ("xx" is a random 6 character string).
When the email is successfully sent, the autosave file SHOULD be
deleted. It's not. When evolution is shut down and restarted I'm asked
if I want to recover an unfinished email. Answering No to this will
delete the autosave file, but otherwise it persists and the recovery
query recurs the next time I open evolution.
Other people are having the same issue, see
https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
people aren't dealing with it, perhaps considering it a distro-
specific bug.
On a system used by many people this is a potential security issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1983794/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987929] [NEW] 22.04 jammy ships perl-base 5.34.0 which contains a broken debugger
Public bug reported: perl 5.34.0 coming with 22.04 jammy has a serious bug in the debugger: https://github.com/Perl/perl5/pull/18900 afaik this was fixed in 5.34.1 This should be fixed in ubuntu, too. ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: perl perl-base ** Description changed: - perl 5.34.0 coming with 22.04 jammy has a serius bug in the debugger: + perl 5.34.0 coming with 22.04 jammy has a serious bug in the debugger: https://github.com/Perl/perl5/pull/18900 afaik this was fixed in 5.34.1 This should be fixed in ubuntu, too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1987929 Title: 22.04 jammy ships perl-base 5.34.0 which contains a broken debugger Status in perl package in Ubuntu: New Bug description: perl 5.34.0 coming with 22.04 jammy has a serious bug in the debugger: https://github.com/Perl/perl5/pull/18900 afaik this was fixed in 5.34.1 This should be fixed in ubuntu, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1987929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1073372] Re: Xorg produces high CPU usage, slow gnome-terminal
Hi, I'm on xubuntu 22.04.1 nvidia driver 515.65.01, nvidia on-demand profile lags ... I saw xauth list defaults to display :0 , and according to nvidia- settings, nvidia on-demamd profile uses screen 256, not screen 0. So i tried this: $ xauth add localhost:256 . $(xxd -l 16 -p /dev/urandom) after above command: xauth list, and the hexkey is there But, i noticed no diff without these commands Any idea?? Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1073372 Title: Xorg produces high CPU usage, slow gnome-terminal Status in cairo package in Ubuntu: Invalid Bug description: Thinkpad X220 (Intel video, chipsets, etc) After a few days of uptime and usage on this laptop, the xorg process will start randomly (but consistently over time) producing high CPU usage, even with all applications closed. CPU according to top will vary between about 10% and 90%, and at high CPU times, the system fans will be running rather high. Also, the UIs will slow down and there will be a lot of latency on keypresses (sometimes up to 1 second), with the occasional loss of keypresses. In gnome-terminal, this has the effect of feeling like you're over a cellular modem, even on a local terminal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,vpswitch,move,gnomecompat,compiztoolbox,imgpng,mousepoll,regex,place,snap,unitymtgrabhandles,resize,grid,session,animation,workarounds,expo,wall,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Tue Oct 30 16:30:09 2012 DistUpgraded: 2012-09-15 22:41:29,902 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lsusb: Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. Bluetooth Controller MachineType: LENOVO 4286CTO ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to quantal on 2012-09-16 (44 days ago) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET61WW (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET61WW(1.31):bd04/25/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.4-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1073372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987624] Re: Temporarily hold evolution-data-server in -proposed
** Changed in: evolution-data-server (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Fix Released Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987304] Re: gtk3 fails to build from source in kinetic
This bug was fixed in the package gtk+3.0 - 3.24.34-3ubuntu2 --- gtk+3.0 (3.24.34-3ubuntu2) kinetic; urgency=medium * Re-enable and adapt reftest-known-fail.patch (lp: #1987304) -- Nathan Pratta Teodosio Wed, 24 Aug 2022 10:11:03 -0300 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1987304 Title: gtk3 fails to build from source in kinetic Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: gtk3 has build test failures in kinetic but not in Debian Unstable. (It built on riscv64 because we skip the build tests there). My initial impression is that this is a reftest issue. The reftests are frustrating because dependency changes can lead to images that vary by as little as one pixel and fail the test. And upstream doesn't provide a precise list of dependency versions they are using either. https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.34-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1987304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987624] Re: Temporarily hold evolution-data-server in -proposed
** No longer affects: gnome-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1987624 Title: Temporarily hold evolution-data-server in -proposed Status in evolution-data-server package in Ubuntu: Triaged Bug description: Maybe I needed to add more explicit Breaks in the packaging? But if evolution-data-server smoothly migrates, I fear that several packages including key ones like gnome-shell won't run because apps can't use both libsoup2 and libsoup3 in the same process. So I'm filing a blocker bug for now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1987624/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987920] [NEW] indicator-datetime fails to build with default gcc (gcc-12)
Public bug reported: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 ** Affects: indicator-datetime (Ubuntu) Importance: High Status: New ** Affects: indicator-datetime (Ubuntu Kinetic) Importance: High Status: New ** Tags: ftbfs kinetic ** Also affects: indicator-datetime (Ubuntu Kinetic) Importance: High Status: New ** Description changed: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- - datetime) which are maintained and are able to complete their build - tests successfully. + datetime) which are maintained and are able to build successfully with + the default compiler. See https://launchpad.net/bugs/1983374 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1987920 Title: indicator-datetime fails to build with default gcc (gcc-12) Status in indicator-datetime package in Ubuntu: New Status in indicator-datetime source package in Kinetic: New Bug description: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1987920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian
Removing packages from kinetic: wpewebkit 2.36.6-1 in kinetic libwpewebkit-1.0-doc 2.36.6-1 in kinetic amd64 libwpewebkit-1.0-doc 2.36.6-1 in kinetic arm64 libwpewebkit-1.0-doc 2.36.6-1 in kinetic armhf libwpewebkit-1.0-doc 2.36.6-1 in kinetic i386 libwpewebkit-1.0-doc 2.36.6-1 in kinetic ppc64el libwpewebkit-1.0-doc 2.36.6-1 in kinetic riscv64 libwpewebkit-1.0-doc 2.36.6-1 in kinetic s390x libwpewebkit-1.1-0 2.36.6-1 in kinetic amd64 libwpewebkit-1.1-0 2.36.6-1 in kinetic arm64 libwpewebkit-1.1-0 2.36.6-1 in kinetic armhf libwpewebkit-1.1-0 2.36.6-1 in kinetic ppc64el libwpewebkit-1.1-0 2.36.6-1 in kinetic riscv64 libwpewebkit-1.1-0 2.36.6-1 in kinetic s390x libwpewebkit-1.1-dev 2.36.6-1 in kinetic amd64 libwpewebkit-1.1-dev 2.36.6-1 in kinetic arm64 libwpewebkit-1.1-dev 2.36.6-1 in kinetic armhf libwpewebkit-1.1-dev 2.36.6-1 in kinetic ppc64el libwpewebkit-1.1-dev 2.36.6-1 in kinetic riscv64 libwpewebkit-1.1-dev 2.36.6-1 in kinetic s390x wpewebkit-driver 2.36.6-1 in kinetic amd64 wpewebkit-driver 2.36.6-1 in kinetic arm64 wpewebkit-driver 2.36.6-1 in kinetic armhf wpewebkit-driver 2.36.6-1 in kinetic ppc64el wpewebkit-driver 2.36.6-1 in kinetic riscv64 wpewebkit-driver 2.36.6-1 in kinetic s390x Comment: Unmaintained web engine, security concerns; LP: #1981592 1 package successfully removed. ** Changed in: wpewebkit (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in wpewebkit package in Ubuntu: Fix Released Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian
(and blacklisted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in wpewebkit package in Ubuntu: Fix Released Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian
Removing packages from kinetic: cog 0.14.0-1 in kinetic cog 0.14.0-1 in kinetic amd64 cog 0.14.0-1 in kinetic arm64 cog 0.14.0-1 in kinetic armhf cog 0.14.0-1 in kinetic ppc64el cog 0.14.0-1 in kinetic riscv64 cog 0.14.0-1 in kinetic s390x Comment: Depends on wpewebkit which is a security concern; no reverse-dependencies. LP: #1981592 1 package successfully removed. ** Changed in: cog (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in wpewebkit package in Ubuntu: Fix Released Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
I bare good news, On 22.10 current build for desktop, this issue no longer is valid as it will be resolved! No more garbled mess. I have been looking about but perhaps the fixes there can be applied to jammy. Been testing 22.10 :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978988] Re: [USB-Audio - USB Audio, recording] Recording problem
For Alsa UCM related issuse: - https://github.com/alsa-project/alsa-ucm-conf/issues/172 - https://github.com/alsa-project/alsa-ucm-conf/issues/186 - https://github.com/alsa-project/alsa-ucm-conf/issues/189 ** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #172 https://github.com/alsa-project/alsa-ucm-conf/issues/172 ** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #186 https://github.com/alsa-project/alsa-ucm-conf/issues/186 ** Bug watch added: github.com/alsa-project/alsa-ucm-conf/issues #189 https://github.com/alsa-project/alsa-ucm-conf/issues/189 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1978988 Title: [USB-Audio - USB Audio, recording] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: My Motherboard is MSI X570S and output audio works fine but: - Motherboard microphone plug is not work. - Frontal microphone plug is not work. - When change output from gnome settings to hdmi audio does not work, the audio continues to play in the plug and not in the monitor. - When I change the input or output from digital to analog or sinput it does not change at all. - The strangest thing is that the microphone input captures the audio that is heard in the system as if it were the output, audacious records the audio from the desktop when it tries to monitor the microphone. - When plugging or unplugging the microphone, the system detects this change and tries to change the audio input automatically, but it does not capture the microphone and the desktop continues to be heard. My alsa data: http://alsa- project.org/db/?f=df4d1f6c126260eabc5f159e64cff37efa064a38 MSI have not audio drivers for linux. I can't stream with this motherboard because the microphone doesn't work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: whk1940 F pulseaudio /dev/snd/pcmC1D0c: whk1940 F...m pulseaudio /dev/snd/pcmC1D0p: whk1940 F...m pulseaudio /dev/snd/controlC0: whk1940 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 16 13:13:20 2022 InstallationDate: Installed on 2022-06-13 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: HDA-Intel - HD-Audio Generic Symptom_Type: Only some of inputs are working Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd05/19/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D53 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1978988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1978988] Re: [USB-Audio - USB Audio, recording] Recording problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1978988 Title: [USB-Audio - USB Audio, recording] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: My Motherboard is MSI X570S and output audio works fine but: - Motherboard microphone plug is not work. - Frontal microphone plug is not work. - When change output from gnome settings to hdmi audio does not work, the audio continues to play in the plug and not in the monitor. - When I change the input or output from digital to analog or sinput it does not change at all. - The strangest thing is that the microphone input captures the audio that is heard in the system as if it were the output, audacious records the audio from the desktop when it tries to monitor the microphone. - When plugging or unplugging the microphone, the system detects this change and tries to change the audio input automatically, but it does not capture the microphone and the desktop continues to be heard. My alsa data: http://alsa- project.org/db/?f=df4d1f6c126260eabc5f159e64cff37efa064a38 MSI have not audio drivers for linux. I can't stream with this motherboard because the microphone doesn't work. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: whk1940 F pulseaudio /dev/snd/pcmC1D0c: whk1940 F...m pulseaudio /dev/snd/pcmC1D0p: whk1940 F...m pulseaudio /dev/snd/controlC0: whk1940 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 16 13:13:20 2022 InstallationDate: Installed on 2022-06-13 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed Symptom_Card: HDA-Intel - HD-Audio Generic Symptom_Type: Only some of inputs are working Title: [USB-Audio - USB Audio, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MPG X570S EDGE MAX WIFI (MS-7D53) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.31:bd05/19/2022:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D53:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570SEDGEMAXWIFI(MS-7D53):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D53 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1978988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1982523] Re: error in commented-out NAME_REGEX
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adduser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1982523 Title: error in commented-out NAME_REGEX Status in adduser package in Ubuntu: Confirmed Bug description: The default /etc/adduser.conf contains the line: #NAME_REGEX="^[a-z][-.a-z0-9_]*\$" Commenting this out in preparation of updating it does not work as expected: pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser NAME_REGEX="^[a-z][-a-z0-9_]*\$" adduser: Please enter a username matching the regular expression configured via the NAME_REGEX[_SYSTEM] configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. pra@PABELN-X1E:~$ This is due to the overeager escaping of the dollar sign, which has the undesired effect of requring that usernames end in `$`: pra@PABELN-X1E:~$ sudo adduser testuser$ Adding user `testuser$' ... Adding new group `testuser$' (1002) ... Adding new user `testuser$' (1002) with group `testuser$' ... Creating home directory `/home/testuser$' ... Copying files from `/etc/skel' ... New password: Removing the backslash escaping the terminal `$` corrects the issue: pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser NAME_REGEX="^[a-z][-a-z0-9_]*$" Adding user `testuser' ... Adding new group `testuser' (1002) ... Adding new user `testuser' (1002) with group `testuser' ... Creating home directory `/home/testuser' ... Copying files from `/etc/skel' ... New password: I reported this for the `adduser` package because it seemed the closest match. The file /etc/adduser.conf is not owned by any package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: adduser 3.118ubuntu5 Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Thu Jul 21 19:56:02 2022 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: adduser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1982523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987340] Re: Please merge lvm2 2.03.16-1 from Debian unstable.
This bug was fixed in the package lvm2 - 2.03.16-1ubuntu1 --- lvm2 (2.03.16-1ubuntu1) kinetic; urgency=medium * Merge from Debian unstable (LP: #1987340). Remaining changes: - Lower libdevmapper1.02.1's Depends: dmsetup to a Recommends:. This breaks the circular dependency that causes upgrade failures. As dmsetup is "Priority: required", this has no other practical consequences. (Closes: #586424, LP: #1032823) - Add debian/initramfs-tools/lvm2/scripts/init-bottom/lvm2: We cannot properly synthesize LVM LV change events with udevadm trigger, so if we use LVM, we need to let it finish; otherwise we get missing LV symlinks. - Add enable-issue-discards.patch: Enable "issue_discards" option by default to trim SSDs when changing PVs. This option has no effect if the kernel or the drive does not support trimming, so it's safe to enable by default. (Debian #717313) - debian/rules: - Copy .po file to .pot file for Rosetta (Ubuntu specific). - debian/initramfs-tools/lvm2/hooks/lvm2: depend on udev since we ship udev rules. - Do not start lvm2-monitor in containers (LP: #1576341) - Fix patch of systemd-run in 69-lvm-metad.rules - d/control: add thin-provisioning-tools build-dep as configure wants it around for some checks at build time. - Disable lto build. Other distros build it with lto, however Debian has an old work around from 2015 for an ABI break. See #791888. - Don't build udeb targets. * Removed obsolete patches/changes: - debian/control: add dmsetup-udeb to libdevmapper1.02.1-udeb recommends. - debian/dmsetup-udeb.install: install udev rules in udebs (Debian #504341). - Ship correct udev rules in lvm2-udeb package. - Enable udev-sync in udeb build as it is used by partman when partitioning devicemapper devices. - Define PYTHON_PREFIX in make.tmpl.in for new ax-python. * Removed patches obsoleted/merged by upstream: - Fix file mode of debian/initramfs-tools/lvm2/hooks/lvm2 (LP: #1915579) lvm2 (2.03.16-1) unstable; urgency=medium * New upstream release. * Disable systemd usage in udeb. (closes: #1015174) lvm2 (2.03.15-2) unstable; urgency=medium * Actually fix filename in lvm2 initamfs-tools integration, fixing installation error. (closes: #1014314) lvm2 (2.03.15-1) unstable; urgency=medium * New upstream release. * Remove traces of systemd generator. * Fix installation of lvmdbusd. * Support new udev activation without systemd. -- Dave Jones Mon, 22 Aug 2022 21:35:55 +0100 ** Changed in: lvm2 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1987340 Title: Please merge lvm2 2.03.16-1 from Debian unstable. Status in lvm2 package in Ubuntu: Fix Released Bug description: Please merge lvm2 2.03.16-1 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1987340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1987625] Re: lxc: FTBFS against glibc 2.36.0
Yup, I cherry-picked the patches already, thanks for those :). I'm tracking down a build failure on ppc64el that's presumably caused by gcc-12 on -O3, and once I have a solve (other than forcing -O2) I'll post it all here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1987625 Title: lxc: FTBFS against glibc 2.36.0 Status in lxc package in Ubuntu: Confirmed Bug description: Hi, lxc currently fails to build against glibc 2.36, which also affects its autopkgtests. Here's an excerpt of the failed build logs containing the first error detected: gcc -DHAVE_CONFIG_H -I. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -Wvla -std=gnu11 -fms-extensions -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -Wstrict-prototypes -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -fcf-protection -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Warray-bounds -Wrestrict -Wreturn-local-addr -Wstringop-overflow -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/include -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wvla -std=gnu11 -fms-extensions -Werror -c -o conf.o conf.c conf.c: In function ‘__lxc_idmapped_mounts_child’: conf.c:2993:37: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 2993 | , | ^ | | | struct lxc_mount_attr * In file included from conf.c:22: /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ conf.c:3016:41: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3016 | , | ^ | | | struct lxc_mount_attr * /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ conf.c: In function ‘lxc_idmapped_mounts_parent’: conf.c:4130:37: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 4130 | , sizeof(attr)); | ^ | | | struct lxc_mount_attr * /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ I believe the following upstream PR should fix the issue: https://github.com/lxc/lxc/pull/4181 I'll be testing a patched version shortly and will post a debdiff if it pans out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1987625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I forgot to add SYSTEM INFO: $ cat /proc/version Linux version 5.15.0-46-generic (buildd@lcy02-amd64-115) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022 $ uname -r 5.15.0-46-generic $ hostnamectl | grep Kernel Kernel: Linux 5.15.0-46-generic $ sudo lscpu Architecture:x86_64 CPU op-mode(s):32-bit, 64-bit Address sizes: 39 bits physical, 48 bits virtual Byte Order:Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Vendor ID: GenuineIntel Model name:Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987625] Re: lxc: FTBFS against glibc 2.36.0
We've fixed those upstream already and will be in the next upstream point release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1987625 Title: lxc: FTBFS against glibc 2.36.0 Status in lxc package in Ubuntu: Confirmed Bug description: Hi, lxc currently fails to build against glibc 2.36, which also affects its autopkgtests. Here's an excerpt of the failed build logs containing the first error detected: gcc -DHAVE_CONFIG_H -I. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -Wvla -std=gnu11 -fms-extensions -fdiagnostics-color -Wimplicit-fallthrough=5 -Wcast-align -Wstrict-prototypes -fno-strict-aliasing -fstack-clash-protection -fstack-protector-strong --param=ssp-buffer-size=4 -g -fcf-protection -Werror=implicit-function-declaration -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Winit-self -Wunused-but-set-variable -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=return-type -Werror=incompatible-pointer-types -Wformat=2 -Wshadow -Wendif-labels -Werror=overflow -fdiagnostics-show-option -Werror=shift-count-overflow -Werror=shift-overflow=2 -Wdate-time -Wnested-externs -fasynchronous-unwind-tables -pipe -fexceptions -Warray-bounds -Wrestrict -Wreturn-local-addr -Wstringop-overflow -DLXCROOTFSMOUNT=\"/usr/lib/x86_64-linux-gnu/lxc\" -DLXCPATH=\"/var/lib/lxc\" -DLXC_GLOBAL_CONF=\"/etc/lxc/lxc.conf\" -DLXCINITDIR=\"/usr/lib/x86_64-linux-gnu\" -DLIBEXECDIR=\"/usr/lib/x86_64-linux-gnu\" -DLXCTEMPLATEDIR=\"/usr/share/lxc/templates\" -DLXCTEMPLATECONFIG=\"/usr/share/lxc/config\" -DLOGPATH=\"/var/log/lxc\" -DLXC_DEFAULT_CONFIG=\"/etc/lxc/default.conf\" -DLXC_USERNIC_DB=\"/run/lxc/nics\" -DLXC_USERNIC_CONF=\"/etc/lxc/lxc-usernet\" -DDEFAULT_CGROUP_PATTERN=\"\" -DRUNTIME_PATH=\"/run\" -DSBINDIR=\"/usr/sbin\" -DAPPARMOR_CACHE_DIR=\"/var/cache/lxc/apparmor\" -I ../../src -I ../../src/include -I ../../src/lxc -I ../../src/lxc/storage -I ../../src/lxc/cgroups -DHAVE_APPARMOR -DHAVE_SECCOMP -DHAVE_SELINUX -g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wvla -std=gnu11 -fms-extensions -Werror -c -o conf.o conf.c conf.c: In function ‘__lxc_idmapped_mounts_child’: conf.c:2993:37: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 2993 | , | ^ | | | struct lxc_mount_attr * In file included from conf.c:22: /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ conf.c:3016:41: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 3016 | , | ^ | | | struct lxc_mount_attr * /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ conf.c: In function ‘lxc_idmapped_mounts_parent’: conf.c:4130:37: error: passing argument 4 of ‘mount_setattr’ from incompatible pointer type [-Werror=incompatible-pointer-types] 4130 | , sizeof(attr)); | ^ | | | struct lxc_mount_attr * /usr/include/x86_64-linux-gnu/sys/mount.h:317:46: note: expected ‘struct mount_attr *’ but argument is of type ‘struct lxc_mount_attr *’ 317 | struct mount_attr *__uattr, size_t __usize) | ~~~^~~ I believe the following upstream PR should fix the issue: https://github.com/lxc/lxc/pull/4181 I'll be testing a patched version shortly and will post a debdiff if it pans out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1987625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987706] Re: [FFe] Should preinstall network-manager-openconnect-gnome
** Description changed: The ubuntu-desktop package should recommend network-manager-openconnect- gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. - I believe this deserves a feature freeze exception because it adds support to UBuntu for several types of - enterprise VPNs in wide use. + I believe this deserves a feature freeze exception because it adds + support to Ubuntu for several types of enterprise VPNs in wide use. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1987706 Title: [FFe] Should preinstall network-manager-openconnect-gnome Status in ubuntu-meta package in Ubuntu: Incomplete Bug description: The ubuntu-desktop package should recommend network-manager- openconnect-gnome, that is undergoing a main inclusion review (MIR) at bug #1986592. I believe this deserves a feature freeze exception because it adds support to Ubuntu for several types of enterprise VPNs in wide use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1987706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
I upgraded to Ubuntu 22.04 yesterday and this bug now affects me. Also, I have Mint Linux (20.3) Cinnamon (5.2.7) on another machine and its been like that since day 1 of the install. In both versions of the operating system, when using a browser to right- click a file and "save as", the Save As Dialogue box does not get focus. This means, you can't just type the name of the file you want, you have to force focus on the Save As Dialogue box to use it by clicking it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1986619] Re: Fail to install base-passwd
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: base-passwd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1986619 Title: Fail to install base-passwd Status in base-passwd package in Ubuntu: Confirmed Bug description: /home/frank/Downloads# dpkg -i base-passwd_3.5.52build1_amd64.deb (Reading database ... 236425 files and directories currently installed.) Preparing to unpack base-passwd_3.5.52build1_amd64.deb ... Unpacking base-passwd (3.5.52build1) over (3.5.52build1) ... Setting up base-passwd (3.5.52build1) ... Changing home-directory of irc from /var/run/ircd to /run/ircd 1 changes have been made, rewriting files Writing passwd-file to /etc/passwd Failed to open passwd-file /etc/passwd.upwd-write for writing: Permission denied dpkg: error processing package base-passwd (--install): installed base-passwd package post-installation script subprocess returned error exit status 4 Errors were encountered while processing: base-passwd root@CNQDSX:/home/frank/Downloads# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1986619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hey Jeremy,
Understood; thanks for clarifying!
I thought that maybe having upstream input could be helpful
(as Julian mentioned to avoid diverging further), but if it
is so much different nowadays, as you mentioned, it likely
won't be that helpful anyway.
By the way, appreciate that "newbie" statement.. after all
this work/analysis/patches, I couldn't think that of you :)
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi Mauricio,
From the patch set in this ticket:
```
+0129-Try-to-pick-better-locations-for-kernel-and-initrd.patch
+0130-x86-efi-Use-bounce-buffers-for-reading-to-addresses-.patch
+0131-x86-efi-Re-arrange-grub_cmd_linux-a-little-bit.patch
+0132-x86-efi-Make-our-own-allocator-for-kernel-stuff.patch
+0133-x86-efi-Allow-initrd-params-cmdline-allocations-abov.patch
+0134-linuxefi-fail-kernel-validation-without-shim-protoco.patch
+0135-Fix-4GB-memory-be-filtered-out-by-filter_memory_map.patch
```
0129-0133 are the key patches to support the >4G memory allocation which made
by vathpela and I didn't see they are upstreamed.
From my point of view, it won't upstream because upstream has different
approach to allocate memory for kernel and initramfs.
Therefore, the last time I debug this issue is based on ubuntu code
base.
Indeed, I should take a look to see if upstream version whether has this issue.
However, I learned from Julian that upstream refactored the MM part. (says, the
patches will likely be dropped after 2.12 grub)
I can give it a try but it takes time because I'm a newbie in the grub.
Even if there is a patch on upstream, it need to based on the refactored MM
which might not easy to land in LTS version as users expected.
I suggest to consider to carry these patches in ubuntu to unblock the ubuntu
users first.
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c”
[Touch-packages] [Bug 1987001] Re: netplan.io autopkgtest failures with NetworkManager 1.39.90
This bug was fixed in the package network-manager - 1.39.90-1ubuntu3 --- network-manager (1.39.90-1ubuntu3) kinetic; urgency=medium * Cherry-pick 2 patches to fix bonding regressions discovered with failing netplan autopkgtests. Thanks Lukas Märdian. (LP: #1987001) -- Jeremy Bicha Thu, 25 Aug 2022 13:26:02 -0400 ** Changed in: network-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1987001 Title: netplan.io autopkgtest failures with NetworkManager 1.39.90 Status in NetworkManager: Unknown Status in netplan.io package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Fix Released Bug description: netplan.io's autopkgtests are failing with NetworkManager 1.40 RC1 (1.39.90). https://autopkgtest.ubuntu.com/packages/n/netplan.io/kinetic/amd64 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-40/NEWS log excerpt: == FAIL: test_bond_mode_8023ad_adselect (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 147, in test_bond_mode_8023ad_adselect self.assertEqual(f.read().strip(), 'bandwidth 1') AssertionError: 'stable 0' != 'bandwidth 1' - stable 0 + bandwidth 1 == FAIL: test_bond_mode_balance_tlb_learn_interval (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.iNCkRv/build.oDI/src/tests/integration/bonds.py", line 670, in test_bond_mode_balance_tlb_learn_interval self.assertEqual(f.read().strip(), '15') AssertionError: '1' != '15' - 1 + 15 ? + To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1987001/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910273] Re: Upgrade to groovy breaks DNS resolution
*** This bug is a duplicate of bug 1907878 *** https://bugs.launchpad.net/bugs/1907878 I've run into the same problem on a server upgraded from 18.04 to 20.04 and 22.04. After the last upgrade step, DNS did not work anymore. It seems that DNS information does not get properly propagated from ifupdown configuration (/etc/network/interfaces) to systemd-resolved. The main issue seems to be this error: ``` /etc/network/if-up.d/resolved: 70: DNS: not found ``` It seems that the state files e.g. /run/network/ifupdown-inet-eth0 contain the following string: ``` "DNS"="" When the script tries to source the file around line 78, this fails. I fixed it by removing the quotes around $DNS and $DOMAINS on line 47 and 51. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1910273 Title: Upgrade to groovy breaks DNS resolution Status in ifupdown package in Ubuntu: Confirmed Bug description: ~# lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~# apt-cache policy ifupdown ifupdown: Instalēts: 0.8.35ubuntu2 Kandidāts: 0.8.35ubuntu2 Versiju tabula: *** 0.8.35ubuntu2 500 500 http://mirrors.digitalocean.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ~# Problem: Upon upgrade from Ubuntu 20.04 to Ubuntu 20.10, I expected name resolution upon reboot to work as usual. What happened: a) /var/log/syslog sprinkled with error messages: - /etc/network/if-up.d/resolved: 12: mystatedir: not found - /etc/network/if-up.d/resolved: 70: DNS: not found - /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-eth0: DNS=8.8.8.8 8.8.4.4: not found b) resolvectl dns returning no name servers Investigation: Recently changed /etc/network/if-up.d/resolved and /etc/network/if-down.d/resolved files contain programming errors. See https://git.launchpad.net/ubuntu/+source/ifupdown/commit/?id=54fec5eedfd59adaffe9021c271914578dd05d1b . Fix: $ diff /Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-down.d/resolved if-down.d_resolved 12c12 < mystatedir statedir ifindex interface --- > # local mystatedir statedir ifindex interface $ diff /Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-up.d/resolved if-up.d_resolved 12c12 < mystatedir statedir ifindex interface --- > # local mystatedir statedir ifindex interface 39,40c39,40 < DNS=DNS < DOMAINS=DOMAINS --- > DNS=$DNS > DOMAINS=$DOMAINS 42,43c42,43 < DNS=DNS6 < DOMAINS=DOMAINS6 --- > DNS=$DNS6 > DOMAINS=$DOMAINS6 47c47 < "$DNS"="$NEW_DNS" --- > DNS="$NEW_DNS" 51c51 < "$DOMAINS"="$NEW_DOMAINS" --- > DOMAINS="$NEW_DOMAINS" 70c70 < DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE --- > # local DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)
Anyone tell me how to fix it?
I'm new user using ubuntu
--
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/1981622
Title:
mtd device must be supplied (device name is empty)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Triaged
Status in systemd source package in Jammy:
Triaged
Bug description:
[WORKAROUND]
This will NOT fix a system that is not booting, because the "mtd
device must be supplied (device name is empty)" message is not the
cause of failed boots. This work around is only for those who are
annoyed by the error message, but are otherwise not experiencing any
issues.
If you are not able to boot your system, but you see this error
message, please open a separate bug with your journalctl and dmesg
logs.
# cp /{lib,etc}/systemd/system/systemd-pstore.service
# sed -i 's/modprobe@mtdpstore.service //'
/etc/systemd/system/systemd-pstore.service
# systemctl daemon-reload
[Impact]
Due to mtdpstore not being properly configured as a pstore backend,
when systemd-pstore.service tries to load the module, users get the
following error in dmesg:
[ 18.453473] systemd[1]: Starting Load Kernel Module mtdpstore...
[ 18.462685] mtd device must be supplied (device name is empty)
This is a distracting error for users trying to diagnose other system
issues, especially if their system does not boot after a kernel crash
and this is the only message displayed on the console.
[Test Plan]
* Force a kernel crash to populate /sys/fs/pstore, thus causing
systemd-pstore.service to start on the subsequent boot:
# echo 1 > /proc/sys/kernel/sysrq
# echo 1 > /proc/sys/kernel/panic
# echo c > /proc/sysrq-trigger
* When the system reboots, observe the error in dmesg:
# dmesg | grep mtd
[Where problems could occur]
If a system was relying on this pstore backend, and mtdpstore is built
as a module, it is possible for systemd-pstore.service to trigger
before mtdpstore is loaded, causing systemd-pstore to not copy the
contents of /sys/fs/pstore. Note however that before the patched
introduced as a result of bug 1978079, systemd-pstore.service would
not attempt to load *any* kernel modules.
[Original Description]
After updating my 22.04 system (possibly caused by Systemd update).
And now booting, dmesg has two errors:
'mtd device must be supplied (device name is empty)'.
See line 8 and 134 in the included logfile.
The system are booting as it should though, and the system are working
like it should no errors at all.
Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?
I have an EFI mounted at boot but it isn't used because I have
installed my system in legacy BIOS mode.
Is this maybe the culprit?
I could ignore the message but it isn't nice though.
Regards
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1981592] Re: Please remove wpewebkit and block syncs from Debian
** Changed in: wpewebkit (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1981592 Title: Please remove wpewebkit and block syncs from Debian Status in cog package in Ubuntu: New Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in wpewebkit package in Ubuntu: New Bug description: The wpewebkit package contains a whole webkit browser engine. It is currently not used by anything of substance in Ubuntu: $ reverse-depends src:wpewebkit Reverse-Depends * cog (for libwpewebkit-1.1-0) * gstreamer1.0-wpe (for libwpewebkit-1.1-0) cog is a single-window browser for embedded devices that is not used by anything else in the archive. gstreamer1.0-wpe is a plugin based on wpewebkit that is not used by anything else in the archive. Using this browser engine on the Internet is very risky as it it not currently maintained and contains hundreds of security flaws, and maintaining it requires a tremendous amount of work. As such, I don't believe this package is suitable for the Ubuntu archive. I recommend we disable the build in gstreamer and remove both cog and wpewebkit, and put on block on syncs from Debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cog/+bug/1981592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
I think this is to do with the hardware (probably 3D) acceleration under OpenGL since the effect is reproducable by installing virt-manager, setting the type to SPICE instead of VNC and then enabling OpenGL hadware accelerated rendering (3d acceleration as it might be called.) Thus, I believe that this is not limited to just webkit. You may also need to make sure that your MESA_GL_VERSION_OVERRIDE environment variable is set to 3.2 of you are experiancing issues related to "failed to create a GL context" as totem and other apps will experiance this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the jammy Pi desktop, under a wayland session, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987736] Re: ssh-sk-helper undefined symbol fido_cred_set_clientdata
My apologies for the noise, I was referencing an old local compiled fido2 library instead of the package: libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000) Bug can be closed. ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1987736 Title: ssh-sk-helper undefined symbol fido_cred_set_clientdata Status in openssh package in Ubuntu: Invalid Bug description: I'm trying to create a resident key on my (SOMU) fido2 key using the following command: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id -O verify-required Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: libcbor.so.0: cannot open shared object file: No such file or directory ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error To start, /usr/lib/openssh/ssh-sk-helper references the shared library libcbor by libcbor.so.0, which is not created by the libcbor0.8 package. After creating a symbolic link for libcbor.so.0 to libcbor.so.0.8, ssh-sk-helper continues, but now fails on an undefined symbol: fido_cred_set_clientdata: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: symbol lookup error: /usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error Which is confirmed by the output of ldd: $ ldd -r /usr/lib/openssh/ssh-sk-helper linux-vdso.so.1 (0x7ffe4af2e000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fb8621e7000) libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb861f95000) libcbor.so.0 => /lib/x86_64-linux-gnu/libcbor.so.0 (0x7fb861f87000) libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x7fb861cac000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7fb861c82000) /lib64/ld-linux-x86-64.so.2 (0x7fb862672000) undefined symbol: fido_cred_set_clientdata (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_get_touch_status (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_cred_set_prot(/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_assert_set_clientdata (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_cred_prot(/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_supports_cred_prot (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_get_touch_begin (/usr/lib/openssh/ssh-sk-helper) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1987736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1987792] [NEW] Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Public bug reported: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39. [mpeg2video @ 0x7fd5d4087d80] Slice 16 data buffer (7664 bytes) is 0x3a. [mpeg2video @ 0x7fd5d4087d80] Slice 17 param buffer (48 bytes) is 0x3b. [mpeg2video @ 0x7fd5d4087d80] Slice 17 data buffer (1387 bytes) is 0x3c. [mpeg2video @ 0x7fd5d4087d80] Slice 18 param buffer (48 bytes) is 0x3d. [mpeg2video @ 0x7fd5d4087d80] Slice 18 data buffer (7428 bytes) is 0x3e. [mpeg2video @ 0x7fd5d4087d80] Slice 19 param buffer (48 bytes) is 0x3f. [mpeg2video @ 0x7fd5d4087d80] Slice 19 data
[Touch-packages] [Bug 1987736] [NEW] ssh-sk-helper undefined symbol fido_cred_set_clientdata
Public bug reported: I'm trying to create a resident key on my (SOMU) fido2 key using the following command: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id -O verify-required Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: libcbor.so.0: cannot open shared object file: No such file or directory ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error To start, /usr/lib/openssh/ssh-sk-helper references the shared library libcbor by libcbor.so.0, which is not created by the libcbor0.8 package. After creating a symbolic link for libcbor.so.0 to libcbor.so.0.8, ssh- sk-helper continues, but now fails on an undefined symbol: fido_cred_set_clientdata: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: symbol lookup error: /usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error Which is confirmed by the output of ldd: $ ldd -r /usr/lib/openssh/ssh-sk-helper linux-vdso.so.1 (0x7ffe4af2e000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fb8621e7000) libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fb861f95000) libcbor.so.0 => /lib/x86_64-linux-gnu/libcbor.so.0 (0x7fb861f87000) libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x7fb861cac000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7fb861c82000) /lib64/ld-linux-x86-64.so.2 (0x7fb862672000) undefined symbol: fido_cred_set_clientdata (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_get_touch_status (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_cred_set_prot(/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_assert_set_clientdata(/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_cred_prot(/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_supports_cred_prot (/usr/lib/openssh/ssh-sk-helper) undefined symbol: fido_dev_get_touch_begin (/usr/lib/openssh/ssh-sk-helper) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1987736 Title: ssh-sk-helper undefined symbol fido_cred_set_clientdata Status in openssh package in Ubuntu: New Bug description: I'm trying to create a resident key on my (SOMU) fido2 key using the following command: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id -O verify-required Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: error while loading shared libraries: libcbor.so.0: cannot open shared object file: No such file or directory ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error To start, /usr/lib/openssh/ssh-sk-helper references the shared library libcbor by libcbor.so.0, which is not created by the libcbor0.8 package. After creating a symbolic link for libcbor.so.0 to libcbor.so.0.8, ssh-sk-helper continues, but now fails on an undefined symbol: fido_cred_set_clientdata: $ ssh-keygen -t ed25519-sk -O resident -f ~/.ssh/somu_id Generating public/private ed25519-sk key pair. You may need to touch your authenticator to authorize key generation. Enter PIN for authenticator: /usr/lib/openssh/ssh-sk-helper: symbol lookup error: /usr/lib/openssh/ssh-sk-helper: undefined symbol: fido_cred_set_clientdata ssh_msg_recv: read header: Connection reset by peer client_converse: receive: unexpected internal error reap_helper: helper exited with non-zero exit status Key enrollment failed: unexpected internal error Which is confirmed by the output of ldd: $ ldd -r /usr/lib/openssh/ssh-sk-helper linux-vdso.so.1 (0x7ffe4af2e000) libcrypto.so.3 => /lib/x86_64-linux-gnu/libcrypto.so.3 (0x7fb8621e7000) libfido2.so.1 => /usr/local/lib/libfido2.so.1 (0x7fb8621bd000)
