Bug#1060770: FTBFS: Missing dependency on libevdev-dev
Package: gnome-control-center Version: 1:46~alpha-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: Jararh Gosbell Dear Maintainer, In attempting to rebuild gnome-control-center for Mobian I noticed that the 46-alpha-2 version fails to build without adding a build-dep on libevdev-dev. I've reproduced this with `sbuild` with a fresh Debian Unstable chroot against debian/1%46_alpha-2. A patch is attached that fixes the issue for me. Thanks, Jarrah. -- System Information: Debian Release: 12.4 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.2-1.qubes.fc37.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-control-center depends on: pn accountsservice pn apg ii colord1.4.6-2.2 pn desktop-base ii desktop-file-utils0.26-1 pn gnome-control-center-data ii gnome-desktop3-data 43.2-2 pn gnome-settings-daemon ii gsettings-desktop-schemas 43.0-1 pn libaccountsservice0 ii libadwaita-1-01.2.2-1 ii libc6 2.36-9+deb12u3 ii libcairo2 1.16.0-7 pn libcolord-gtk4-1 ii libcolord21.4.6-2.2 ii libcups2 2.4.2-3+deb12u5 ii libepoxy0 1.5.10-1 ii libfontconfig12.14.1-4 ii libgcr-base-3-1 3.41.1-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 pn libgnome-bg-4-2 pn libgnome-bluetooth-ui-3.0-13 ii libgnome-desktop-4-2 43.2-2 pn libgnome-rr-4-2 ii libgnutls30 3.7.9-2+deb12u1 ii libgoa-1.0-0b 3.46.0-1 pn libgoa-backend-1.0-1 pn libgsound0 ii libgtk-3-03.24.38-2~deb12u1 ii libgtk-4-14.8.3+ds-2+deb12u1 pn libgtop-2.0-11 ii libgudev-1.0-0237-2 pn libibus-1.0-5 ii libkrb5-3 1.20.1-2+deb12u1 pn libmalcontent-0-0 ii libmm-glib0 1.20.4-1 ii libnm01.42.4-1 pn libnma-gtk4-0 ii libpango-1.0-01.50.12+ds-1 ii libpangocairo-1.0-0 1.50.12+ds-1 ii libpolkit-gobject-1-0 122-3 pn libpulse-mainloop-glib0 ii libpulse0 16.1+dfsg1-2+b1 pn libpwquality1 ii libsecret-1-0 0.20.5-3 ii libsmbclient 2:4.17.12+dfsg-0+deb12u1 pn libsnapd-glib-2-1 ii libudisks2-0 2.9.4-4 ii libupower-glib3 0.99.20-2 ii libwacom9 2.6.0-1 ii libx11-6 2:1.8.4-2+deb12u2 ii libxi62:1.8-1+b1 ii libxml2 2.9.14+dfsg-1.3~deb12u1 pn webp-pixbuf-loader Versions of packages gnome-control-center recommends: pn cracklib-runtime ii cups-pk-helper 0.2.6-1+b1 pn gkbd-capplet pn gnome-bluetooth-sendto pn gnome-online-accounts pn gnome-remote-desktop pn gnome-user-docs pn gnome-user-share ii iso-codes 4.15.0-1 pn libcanberra-pulse ii libnss-myhostname 252.19-1~deb12u1 pn libspa-0.2-bluetooth | pulseaudio-module-bluetooth pn malcontent-gui ii network-manager-gnome 1.30.0-2 ii polkitd 122-3 pn power-profiles-daemon pn realmd pn rygel | rygel-tracker ii system-config-printer-common1.5.18-1 Versions of packages gnome-control-center suggests: pn gnome-software | gnome-packagekit pn gstreamer1.0-pulseaudio ii pkexec 122-3 ii x11-xserver-utils 7.7+9+b1 >From 83c57e32bd527feae9d540f16c930444cfc3dd3e Mon Sep 17 00:00:00 2001 From: Jarrah Gosbell Date: Sun, 14 Jan 2024 02:03:09 + Subject: [PATCH] d/control: Add build-dep on libevdev-dev This fixes a build failure in dh_auto_configure. --- debian/control | 1 +
Bug#1060376: libgl1-mesa-dri: apps using llvmpipe crashes on RISCV
Package: libgl1-mesa-dri Version: 23.3.2-2 Severity: important X-Debbugs-Cc: csm.su...@gmail.com Dear Maintainer, * What led up to the situation? Run any OpenGL app via ssh -X hostname * What exactly did you do (or not do) that was effective (or ineffective)? 1) login on the remote host with ssh -X 2) run glxgears * What was the outcome of this action? SIGSEGV error if run gdb glxgears: (gdb) bt #0 0x003ff1db39ee in llvm::RuntimeDyldELF::computePlaceholderAddress(unsigned int, unsigned long) const () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #1 0x003ff1da6e6e in llvm::RuntimeDyldImpl::applyExternalSymbolRelocations(llvm::StringMapllvm::MallocAllocator>) () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #2 0x003ff1da3658 in llvm::RuntimeDyldImpl::resolveExternalSymbols() () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #3 0x003ff1da30d0 in llvm::RuntimeDyldImpl::resolveRelocations() () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #4 0x003ff1cf3970 in llvm::MCJIT::finalizeLoadedModules() () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #5 0x003ff1cf3d4a in llvm::MCJIT::finalizeObject() () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #6 0x003ff1c946ec in LLVMGetPointerToGlobal () from /lib/riscv64-linux-gnu/libLLVM-17.so.1 #7 0x003ff6981082 in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #8 0x003ff6a1231a in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #9 0x003ff6a0347c in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #10 0x003ff69e8702 in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #11 0x003ff6549d08 in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #12 0x003ff67661e4 in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #13 0x003ff6671b4c in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #14 0x003ff6699a8c in ?? () from /usr/lib/riscv64-linux-gnu/dri/swrast_dri.so #15 0x002ac57e in ?? () #16 0x002abf4a in main () * What outcome did you expect instead? Running OpenGL applications. Also if try GALLIUM_DRIVER=softpipe glxgears all works. -- Package-specific info: glxinfo: name of display: localhost:10.0 display: localhost:10 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_context_flush_control, GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_ATI_pixel_format_float, GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_swap_control, GLX_EXT_swap_control_tear, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_gl_interop, GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_NV_float_buffer, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_create_context, GLX_ARB_create_context_no_error, GLX_ARB_create_context_profile, GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float, GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_no_config_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_query_renderer, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa (0x)
Bug#1052371: game-data-packager: a crash while rebuilding quake2-full-data deb package
Package: game-data-packager
Version: 63
Severity: normal
Dear Maintainer,
when I tried to build quake2-full-data from the existing deb package gdb
crashed
game-data-packager quake2 quake2-full-data_63_all.deb
...
extracting ./usr/share/games/quake2/baseq2/pak2.pak from
/home/undef/debian/gdp/quake2-full-data_63_all.deb
extracting ./usr/share/games/quake2/baseq2/pak3.pak from
/home/undef/debian/gdp/quake2-full-data_63_all.deb
extracting
./usr/share/games/quake2/baseq2/players/crakhor/a_grenades.md2 from
/home/undef/debian/gdp/quake2-full-data_63_all.deb
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Traceback (most recent call last):
File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
exec(code, run_globals)
File
"/usr/share/games/game-data-packager/game_data_packager/command_line.py",
line 365, in
run_command_line()
File
"/usr/share/games/game-data-packager/game_data_packager/command_line.py",
line 362, in run_command_line
task.run_command_line(parsed)
File
"/usr/share/games/game-data-packager/game_data_packager/build.py", line
1688, in run_command_line
binary_executables=args.binary_executables)
File
"/usr/share/games/game-data-packager/game_data_packager/build.py", line
1614, in look_for_files
self.consider_file_or_dir(arg)
File
"/usr/share/games/game-data-packager/game_data_packager/build.py", line
465, in consider_file_or_dir
self.consider_file(path, True)
File
"/usr/share/games/game-data-packager/game_data_packager/build.py", line
424, in consider_file
self.consider_stream(path, tar)
File
"/usr/share/games/game-data-packager/game_data_packager/build.py", line
728, in consider_stream
info='extracting %s from %s' % (entry.name, name)),
File
"/usr/share/games/game-data-packager/game_data_packager/data.py", line
54, in from_file
return cls.from_concatenated_files(name, [f], write_to, size, progress)
File
"/usr/share/games/game-data-packager/game_data_packager/data.py", line
72, in from_concatenated_files
blob = f.read(io.DEFAULT_BUFFER_SIZE)
File "/usr/lib/python3.7/tarfile.py", line 706, in readinto
buf = self.read(len(b))
File "/usr/lib/python3.7/tarfile.py", line 694, in read
self.fileobj.seek(offset + (self.position - start))
File "/usr/lib/python3.7/tarfile.py", line 520, in seek
raise StreamError("seeking backwards is not allowed")
tarfile.StreamError: seeking backwards is not allowed
This issue is reproducible with gdp 63, 70, 76, master.
Bug#1051465: [Debian-on-mobile-maintainers] Bug#1051465: unl0kr: Lacks automated migration when osk-sdl is already installed
I seem to have dropped the BTS on reply, so including the history in this email. Another option I realized might work is to add a `breaks` and `replaces` osk-sdl in unl0kr then ship a link from the osk-sdl keyscript to the unl0kr one in unl0kr. I haven't tested anything at this point, but this would mean we don't have to modify people's crypttab. Some potential issues for this option: * It would require an update to osk-sdl to make sure the crypttab config isn't removed if unl0kr is also installed. * A user removing osk-sdl manually then installing unl0kr would need to configure things manually. Then again, neither would 3a below. On 9/9/23 21:04, Arnaud Ferraris wrote: Le 09/09/2023 à 11:27, undef via Debian-on-mobile-maintainers a écrit : Thanks for getting the ball rolling on this one. I think in the first instance we should switch c-s-m to unl0kr to catch new installs as you say. That'll stop the problem from getting worse. It would probably be a good idea to ask more technical users to make the switch too before making this type of change. Yes, I believe this should be done ASAP as I think currently there's only the 2 of us actively using unl0kr, so getting it into more hands will likely help catch bugs and make it more stable. After that, I have a couple of thoughts on the automated transition: 1. If unl0kr is installed while osk-sdl is it should probably do nothing. This avoids breaking working installs. This is fine for now, but I think it should be revisited at some point in the future (ideally pre-trixie release, see below). 2. If unl0kr is installed and osk-sdl isn't it should check for osk-sdl's debconf setting indicating that c-s-m or similar configured crypttab in the first place. If this is set unl0kr could attempt to add its keyscript to the crypttab. a. This probably also requires a release of osk-sdl with the inverse to: * Deconfigure itself * Configure unl0kr * Set unl0kr's debconf flag as osk-sdl's is. That sounds reasonable indeed. 3. A new install of unl0kr without osk-sdl ever having been installed could either: a. Do nothing, leaving the package installed in a dormant state as it is now. b. Prompt loudly using debconf then automatically attempt to configure (this is somewhat recommended against in debconf's docs). c. Just automatically attempt to configure (negating the need for 2). I'm somewhat reticent to do 3c as this will break installs that are non-standard (say someone's configured a TPM or yubikey unlock), but there is at least some desire for the package automatically configuring the system: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028554 I think that 3a is the best option here, as it basically matches the current behaviour of osk-sdl, which is just fine. That leaves the matter of how do we trigger the switch? Currently the only packages installed indicating FDE on Mobian devices are unl0kr and osk-sdl. I can't think of a neat way to cause one to be removed and replaced with the other without triggering the install on non-FDE devices. I'm leaving the "how" aside for now, rather discussing the "why" here: IIUC osk-sdl is now unmaintained and will likely stay that way; therefore, as it's a rather critical component (in the sense that it deals with secrets/encryption) I believe it shouldn't be part of the upcoming Trixie release. New installs (after the upcoming c-s-m changes are in) won't be affected, which is already a good thing; but I'm a bit reluctant to leave existing users with an unmaintained critical component, hence my belief that an automated migration would be nice. As suggested by the bug severity this isn't an urgent matter though, and the idea of dropping osk-sdl for trixie can also be discussed. Cheers, Arnaud PS: osk-sdl could be made a transitional package at some point, which would depend on unl0kr, and would take care of modifying the crypttab so unl0kr is used instead. ___ Debian-on-mobile-maintainers mailing list debian-on-mobile-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers ___ Debian-on-mobile-maintainers mailing list debian-on-mobile-maintain...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers
Bug#1016698: osk-sdl: does not show automatically not even the icon in the bottom right
forwarded 1016698 https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 This seems to be https://gitlab.com/postmarketOS/osk-sdl/-/issues/148 upstream. Upstream's current direction is to move to unl0kr instead of osk-sdl, so it's somewhat unlikely that that this will be fixed unless someone experiencing the issue tracks the bug down. I'd recommend testing whether unl0kr solves the issue if you're on Sid/Unstable.
Bug#757421: selinux-basics: selinux-activate doesn't install kernel args on extlinux
I've just tested this on Mobian Sid on PinePhone. Selinux still doesn't
seem to be configured by default with `selinux-basics` and
`selinux-policy-default` installed.
Placing the below file in /usr/share/u-boot-menu/conf.d/zz-selinux.conf
resolves the problem. Note the `zz-` prefix or one like it is mandatory
as this must be processed after the Mobian config which will always
overwrite the `U_BOOT_PARAMETERS` variable.
```
U_BOOT_PARAMETERS="${U_BOOT_PARAMETERS} selinux=1 security=selinux"
```
Thanks.
Bug#1040956: systemd: Internal USB devices disconnected when `udevadm settle` run in early boot
Bisect done (though between v253 and v253.5). Looks like it's the
following commit that breaks it.
88d8ab119df0239e70a5312f1f2c179c7f642dec is the first bad commit
commit 88d8ab119df0239e70a5312f1f2c179c7f642dec
Author: Dmitry V. Levin
Date: Thu Mar 16 08:00:00 2023 +
udev-rules: fix matching of token types that support alternative
patterns
For those token types that support matching of alternative patterns,
their token values are interpreted as nulstr, so make sure the parser
does the right thing and makes these token values terminated by two
subsequent NULs so they could be safely interpreted as nulstr.
Before this fix, the following rules would result to "echo foo"
invocation:
ENV{foo}=", RUN"
ENV{foo}=="bar", RUN+="echo foo"
because the value of `ENV{foo}` is treated as nulstr, and it used
to match
against alternative patterns, in this case `bar`, `, RUN`, and
`="echo foo`.
Fixes: 25de7aa7b90c ("udev: modernize udev-rules.c")
(cherry picked from commit c43ff248f94266cfc93e300a2d3d163ed805e55b)
Bug#1040956: systemd: Internal USB devices disconnected when `udevadm settle` run in early boot
Package: systemd Version: 253.5-1 Severity: important X-Debbugs-Cc: debian@undef.tools Dear Maintainer, On upgrade to systemd 253.5-1 the USB modem on my Librem5 stopped working. This also occurs on 252.11-1 (testing) but not on 252.6-1 (stable) or 253-3 (previously available in unstable. This only seems to happen in a very specific configuration: * Librem5 * Booting from eMMC * Using full disk encryption * Using an on-screen keyboard such as osk-sdl to unlock the device. Digging into the issue, it seems I can trigger it by adding an initramfs script which will run `udevadm settle` in the initramfs. This itself doesn't remove the USB device, but later in the boot the device will disappear. The following logs are found in dmesg: ``` [ 28.890890] usbcore: registered new interface driver option [ 28.890948] usbserial: USB Serial support registered for GSM modem (1-port) [ 28.960264] input: Librem 5 Headphones as /devices/platform/sound/sound/card0/input5 [ 29.080045] option 1-1.2:1.0: GSM modem (1-port) converter detected [ 29.080766] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB0 [ 29.091094] input: Librem 5 Headset Mic as /devices/platform/sound/sound/card0/input6 [ 29.092893] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517) [ 29.107724] option 1-1.2:1.1: GSM modem (1-port) converter detected [ 29.277461] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB1 [ 29.292653] option 1-1.2:1.2: GSM modem (1-port) converter detected [ 29.326085] imx-hdmi sound-hdmi: snd_soc_register_card failed (-517) [ 29.427883] usb 1-1.2: GSM modem (1-port) converter now attached to ttyUSB2 [ 29.457265] option 1-1.2:1.3: GSM modem (1-port) converter detected [...] [ 31.474866] usb 1-1.2: USB disconnect, device number 4 [ 31.475478] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0 [ 31.475542] option 1-1.2:1.0: device disconnected [ 31.482999] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1 [ 31.483071] option 1-1.2:1.1: device disconnected [ 31.507980] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2 [ 31.508439] option 1-1.2:1.2: device disconnected [ 31.552074] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3 [ 31.552146] option 1-1.2:1.3: device disconnected [ 31.552425] qmi_wwan 1-1.2:1.4 wwan0: unregister 'qmi_wwan' usb-xhci-hcd.4.auto-1.2, WWAN/QMI device ``` If `udevadm settle` or the on-screen disk encryption keyboard is not run in the initramfs the issue does not occur. Rolling back to systemd 252-3 or 252.6-1 works around the issue. I originally saw the issue on 252.11-1 but didn't report it as upgrading to systemd from unstable (253-3) fixed the issue. Additionally, using a keyfile such that running `udevadm settle` or equivalent is not required works around the issue (though makes disk encryption slightly pointless). -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.1-librem5 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl12.3.1-3 ii libaudit1 1:3.0.9-1 ii libblkid1 2.38.1-5+b1 ii libc6 2.37-5 ii libcap21:2.66-4 ii libcryptsetup122:2.6.1-4 ii libfdisk1 2.38.1-5+b1 ii libgcrypt201.10.2-2 ii libkmod2 30+20230519-1 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.1-0.2 ii libmount1 2.38.1-5+b1 ii libp11-kit00.24.1-2 ii libseccomp22.5.4-1+b3 ii libselinux13.4-1+b6 ii libssl33.0.9-1 ii libsystemd-shared 253.5-1 ii libsystemd0253.5-1 ii libzstd1 1.5.5+dfsg2-1 ii mount 2.38.1-5+b1 ii systemd-dev253.5-1 Versions of packages systemd recommends: ii chrony [time-daemon]4.3-4 ii dbus [default-dbus-system-bus] 1.14.8-1 ii dbus-broker [dbus-system-bus] 33-1 Versions of packages systemd suggests: ii libfido2-11.13.0-1 ii libqrencode4 4.1.1-1 pn libtss2-esys-3.0.2-0 pn libtss2-mu0 pn libtss2-rc0 ii polkitd 122-4 pn systemd-boot pn systemd-container pn systemd-homed ii systemd-resolved 253.5-1 pn systemd-userdbd Versions of packages systemd is related to: ii dbus-user-session 1.14.8-1 pn dracut ii initramfs-tools0.142 ii libnss-systemd 253.5-1 ii libpam-systemd 253.5-1 ii udev 253.5-1 -- no debconf information
Bug#1039896: systemd: Please consider enabling the BPF_FRAMEWORK config
Package: systemd Version: 252.6-1 Severity: wishlist X-Debbugs-Cc: Undef Dear Maintainer, This config, enabled by adding `-DBPF_FRAMEWORK=true` would allow settings such as `IPAddressAllow` and RestrictFileSystems` to be used to harden services on Debian systems. `CONFIG_BPF_LSM` seems to already be enabled in Debian's kernels so in theory the only change required should be adding the above setting to the Systemd build. Thank you for considering. -- Package-specific info: -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.35-1.qubes.fc32.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii libacl12.3.1-3 ii libaudit1 1:3.0.9-1 ii libblkid1 2.38.1-5+b1 ii libc6 2.36-9 ii libcap21:2.66-4 ii libcryptsetup122:2.6.1-4~deb12u1 ii libfdisk1 2.38.1-5+b1 ii libgcrypt201.10.1-3 ii libkmod2 30+20221128-1 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.1-0.2 ii libmount1 2.38.1-5+b1 ii libp11-kit00.24.1-2 ii libseccomp22.5.4-1+b3 ii libselinux13.4-1+b6 ii libssl33.0.9-1 ii libsystemd-shared 252.6-1 ii libsystemd0252.6-1 ii libzstd1 1.5.4+dfsg2-5 ii mount 2.38.1-5+b1 Versions of packages systemd recommends: ii dbus [default-dbus-system-bus] 1.14.6-1 ii systemd-timesyncd [time-daemon] 252.6-1 Versions of packages systemd suggests: ii libfido2-11.12.0-2+b1 ii libqrencode4 4.1.1-1 pn libtss2-esys-3.0.2-0 pn libtss2-mu0 pn libtss2-rc0 ii policykit-1 122-3 ii polkitd 122-3 pn systemd-boot ii systemd-container 252.6-1 pn systemd-homed ii systemd-resolved 252.6-1 pn systemd-userdbd Versions of packages systemd is related to: ii dbus-user-session 1.14.6-1 pn dracut ii initramfs-tools0.142 ii libnss-systemd 252.6-1 ii libpam-systemd 252.6-1 ii udev 252.6-1 -- no debconf information
Bug#1036546: bluez: Please consider changing the firmware load location to /lib/firmware
Package: bluez Version: 5.66.1 Severity: wishlist X-Debbugs-Cc: undef Dear Maintainer, `hciattach` and similar tools load firmware at runtime, however they currently look for this firmware in /etc/firmware. This then requires shipping a symlink to /lib/firmware where the firmware packages install it to enable functionality requiring firmware [1]. I'm not sure if there is an existing reason for loading firmware from /etc/firmware or if this is just the upstream default, but if not, could I request this package is build with `-DFIRMWARE_DIR=/lib/firmware`? [2]. [0] https://salsa.debian.org/bluetooth-team/bluez/-/blob/debian/sid/tools/hciattach.h#L44 [1] https://salsa.debian.org/Mobian-team/devices/librem5-tweaks/-/merge_requests/6#note_399904 [2] https://salsa.debian.org/bluetooth-team/bluez/-/commit/d9253248363b995e44c1f5e393ed1c7aa4ec81ce Thanks. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.28-1.qubes.fc32.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.6-1 ii init-system-helpers 1.65.2 ii kmod30+20221128-1 ii libasound2 1.2.8-1+b1 ii libc6 2.36-9 ii libdbus-1-3 1.14.6-1 ii libdw1 0.188-2.1 ii libglib2.0-02.74.6-2 ii libreadline88.2-1.3 ii libudev1252.6-1 ii lsb-base11.6 ii sysvinit-utils [lsb-base] 3.06-4 ii udev252.6-1 bluez recommends no packages. Versions of packages bluez suggests: pn pulseaudio-module-bluetooth
Bug#1032115: ITP: unl0kr -- Lightweight On-Screen-Keyboard based on LVGL
Package: wnpp Severity: wishlist Owner: Undef X-Debbugs-Cc: debian-de...@lists.debian.org, Undef * Package name: unl0kr Version : 3.1.0 Upstream Contact: JohannesMarbach * URL : https://gitlab.com/cherrypicker/unl0kr * License : GPL-3+, Apache-2, BSD-3-clause, Expat, MIT, Unlicense, Zlib Programming Lang: C Description : Lightweight framebuffer On-Screen-Keyboard based on LVGL This keyboard is designed to unlock encrypted root partitions on boot on mobile devices. It is automatically launched on boot, allowing the user to enter their disk encryption password. This package is upstream's planned replacement for osk-sdl. It allows users of mobile or otherwise touchscreen only devices to enter their full disk encryption passphrase during boot. Unlike osk-sdl, unl0kr is lightweight and requires minimal dependencies, making it far more suited to small initramfs deployments. This package will be maintained under the DebianOnMobile team.
Bug#1031599: bluez: Please provide a user service for mpris-proxy
Package: bluez Version: 5.66-1 Severity: normal Tags: patch X-Debbugs-Cc: debian@undef.tools Dear Maintainer, On my Mobian PinePhone Pro I have configured an "mpris-proxy.service" which allows the buttons on my bluetooth headset to control media on the device. Without this proxy, bluetooth controls are completely ineffective. Please consider including the attached systemd user service which will allow users to simply run `systemctl enable --user mpris-proxy` to use this functionality. Thank you. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: arm64 (aarch64) Kernel: Linux 6.1.12-rockchip-imxdebug (SMP w/6 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluez depends on: ii dbus [default-dbus-system-bus] 1.14.6-1 ii init-system-helpers 1.65.2 ii kmod30+20221128-1 ii libasound2 1.2.8-1+b1 ii libc6 2.36-8 ii libdbus-1-3 1.14.6-1 ii libdw1 0.188-2.1 ii libglib2.0-02.74.5-1 ii libreadline88.2-1.3 ii libudev1252.5-2 ii sysvinit-utils [lsb-base] 3.06-2 ii udev252.5-2 bluez recommends no packages. Versions of packages bluez suggests: ii pulseaudio-module-bluetooth 16.1+dfsg1-2+b1 -- no debconf information [Unit] Description=Forward bluetooth media controls to MPRIS [Service] Type=simple ExecStart=/usr/bin/mpris-proxy [Install] WantedBy=default.target
Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command
Given that upstream changes to this package haven't been integrated in years and this bug being pretty limiting to users, Mobian moved to systemd-repart. If it's possible for you I might recommend the same solution. Our experience has been that once implemented it is far more reliable. The switch can be seen at https://salsa.debian.org/Mobian-team/mobian-recipes/-/merge_requests/67/diffs Key parts: 1. Partitions need to be GPT 2. Partitions being resized need a specific "parttype" UUID configured on them. 3. A simple config file needs to be installed in /etc/repart.d.
Bug#1028554: [Debian-on-mobile-maintainers] Bug#1028554: osk-sdl: Missing initial configuration
On 1/13/23 03:48, /dev/fra via Debian-on-mobile-maintainers wrote: After installing osk-sdl I was expecting it to show up automatically at the next boot, but that was not the case. I had to edit /etc/crypttab, add the option "keyscript=/usr/share/initramfs-tools/scripts/osk-sdl-keyscript" and then update initramfs. Shouldn't this configuration step be performed automatically during the installation instead? Thanks for the bug report. I'm not sure I'd agree that this is the packages job to configure. In #1014393 we decided to remove config automatically, but that was a single very specific instance that always leaves the system unbootable. In this case the package would have to add the config, potentially breaking what the user was doing before. The basic version of this might be `sed -i "s:$:keyscript=/usr/share/initramfs-tools/scripts/osk-sdl-keyscript:" /etc/crypttab`, but this will break if the user is already using keyfiles for example. If you can think of a robust way of fixing this I'm happy to review/include a patch, I just worry that most solutions will break existing (and unknown) installs that were already bootable. Any solution should also ensure that if it changes the config the debconf flag to revert the change is also set.
Bug#1026910: calamares-settings-mobian: file conflicts with calamares-settings-debian
Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. Hi, Thanks for the bug report. dpkg: error processing archive /tmp/apt-dpkg-install-MPIdXZ/147-calamares-settings-mobian_0.2.6_all.deb (--unpack): trying to overwrite '/etc/calamares/modules/mount.conf', which is also in package calamares-settings-debian 12.0.3-1 I believe this here is the problem. Calamares-settings-mobian and calamares-settings-debian implement exactly the same functionality, though Mobian does it for devices with small touch-only screens. I'll add a `Conflicts:` to ensure the two are never installed at the same time.
Bug#1025517: ITP: firefox-esr-mobile-config -- Default mobile-friendly configuration for Firefox ESR
Package: wnpp Severity: wishlist Owner: Jarrah Gosbell X-Debbugs-Cc: debian-de...@lists.debian.org, undef * Package name: firefox-esr-mobile-config Version : 3.1.0 Upstream Author : Oliver Smith * URL : http://gitlab.com/postmarketOS/mobile-config-firefox * License : MPL Programming Lang: CSS, JS Description : Default mobile-friendly configuration for Firefox ESR This package provides a set of configuration files aimed at making Firefox ESR more mobile-friendly. It provides: * default preferences values * custom userChrome.css This package will be maintained under the Debian on Mobile team.
Bug#1025346: ITP: calamares-settings-mobian -- Calamares branding and configuration for Mobian
Package: wnpp Severity: wishlist Owner: undef X-Debbugs-Cc: debian-de...@lists.debian.org, undef * Package name: calamares-settings-mobian Version : 0.2.4 Upstream Author : Mobian-team * URL : https://salsa.debian.org/Mobian-team/calamares-settings-mobian * License : GPL3+ Programming Lang: sh Description : Calamares branding and configuration for Mobian This package contains the branding, configuration and scripts required to boot to calamares and install Mobian on a small, touch screen only device. This package will be maintained inside the Mobian team.
Bug#1023664: RFS: innoextract/1.9-0.1 [NMU] -- Tool for extracting data from an Inno Setup installer
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "innoextract": * Package name : innoextract Version : 1.9-0.1 Upstream contact : [fill in name and email of upstream] * URL : http://constexpr.org/innoextract/ * License : Zlib, BSD-3-clause * Vcs : https://salsa.debian.org/lhw-guest/innoextract Section : utils The source builds the following binary packages: innoextract - Tool for extracting data from an Inno Setup installer To access further information about this package, please visit the following URL: https://mentors.debian.net/package/innoextract/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/i/innoextract/innoextract_1.9-0.1.dsc Changes since the last upload: innoextract (1.9-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release. (Closes: #1018828) * debian/copyright: Update years. * debian/patches: Remove the last patch. * debian/watch: Update for the latest github changes. Regards,
Bug#1023036: [Debian-on-mobile-maintainers] Bug#1023036: osk-sdl: Pinephone with FDE can't boot with v0.67-2
Dear Maintainer, Hi, Thanks for the bug report. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... stty: standard Input: cannot perform all requested operations: Resource temporarily unavailable [13.466434] random: osk-sdl: uninitialized urandom read (16 bytes read) [13.969621] random: osk-sdl: uninitialized urandom read (16 bytes read) [24.870996] random: crng init done [41.955178] ps: disabling [41.958144] dc1sw: disablingup: uninitialized urandom read (4 bytes read) [41.961320] avdd-csi: disabling [41.964854] vcc-1v2-hsic: disabling [41.968634] usb0-vbus: disabling - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ...and booting does not progress past that. I have reverted to v0.67-1. I did a dist-upgrade October 28 and then tried v0.67-2 again and got the same result. This sounds very similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017842#5. Could you try deleting the final `cat > /dev/null` line in v0.67-2? If so, this bug will be fixed in 0.67.1-1 that I am currently preparing.
Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command
Package: cloud-initramfs-growroot Version: 0.18.debian8 Severity: important Tags: upstream X-Debbugs-Cc: debian@undef.tools Dear Maintainer, As part of the standard Mobian install proceedure, we use cloud-initramfs-growroot to expand the root partition on the device. Recent installs have been failing to resize with the following (debug) output: ``` + growpart /dev/mmcblk0 2 + out='failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found FAILED: Error while obtaining exclusive lock on /dev/mmcblk0' + echo 'GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found FAILED: Error while obtaining exclusive lock on /dev/mmcblk0' GROWROOT: WARNING: resize failed: failed [flock:127] flock -x 9 /sbin/growpart: line 714: flock: not found FAILED: Error while obtaining exclusive lock on /dev/mmcblk0 + udevadm settle --timeout 30 ``` I believe this issue is solved upstream where the hook has been re-written (https://git.launchpad.net/cloud-initramfs-tools/tree/growroot/hooks/growroot#n12). Without updating to the latest upstream version, simply adding `copy_exec /bin/flock /bin` to the growroot hook also solves the issue. Thank you for your consideration. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.18.7-rockchip (SMP w/6 CPU threads) Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cloud-initramfs-growroot depends on: pn cloud-utils ii fdisk 2.38-4 ii initramfs-tools 0.141 ii util-linux 2.38-4 cloud-initramfs-growroot recommends no packages. cloud-initramfs-growroot suggests no packages.
Bug#1008707: RFS: calamares-extensions/1.2.1-1 [ITP] -- Mobile module for Calamares installer framework
On 5/31/22 01:57, Bastian Germann wrote: On Thu, 31 Mar 2022 08:28:58 +1100 undef wrote: * Package name : calamares-extensions Version : 1.2.1-1 Upstream Author : Calamares * URL : https://github.com/calamares/calamares-extensions You have referenced some other website in d/control's Homepage field. Please use this GitHub URL instead. Thanks again. That was the old Mobian package location. Fixed now.
Bug#1011668: gnome-control-center: Hang on "cancelling" wired network settings panel
Package: gnome-control-center Version: 1:42.1-2 Severity: normal X-Debbugs-Cc: undef Dear Maintainer, Since at least Gnome Control Center 42 closing the network panel causes g-c-c to hang. The following steps reliably reproduce the issue: 1. Open g-c-c -> Network. 2. Select a network and edit it using the cog icon. 3. Without changing any setting, select cancel in the top left. 4. Observe the hang. The following error is printed on the console: (gnome-control-center:96744): Gtk-WARNING **: 03:34:34.701: Finalizing GtkCheckButton 0x5823a9488d70, but it still has children left: (gnome-control-center:96744): Gtk-WARNING **: 03:34:34.701:- GtkBox 0x5823aa4bafa0 (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.713: WirelessSecurityWPAEAP 0x5823aa68b180 has a parent GtkBox 0x5823aa473680 during dispose. Parents hold a reference, so this should not happen. Did you call g_object_unref() instead of gtk_widget_unparent()? (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.714: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed (gnome-control-center:96744): Gtk-CRITICAL **: 03:34:34.714: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed I have tested this on my Debian desktop machine and my Mobian mobile device (using Debian's g-c-c) to the same effect. A nearby Fedora 36 workstation prints the same two warnings, but not the critical messages and does not hang. Thank you. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.16.18-2.fc32.qubes.x86_64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-control-center depends on: ii accountsservice 22.07.5-1 ii apg 2.2.3.dfsg.1-5+b2 ii colord1.4.6-1 ii desktop-base 11.0.3 ii desktop-file-utils0.26-1 ii gnome-control-center-data 1:42.1-2 ii gnome-desktop3-data 42.1-1 ii gnome-settings-daemon 42.1-3 ii gsettings-desktop-schemas 42.0-1 ii libaccountsservice0 22.07.5-1 ii libadwaita-1-01.1.1-1 ii libc6 2.33-7 ii libcairo2 1.16.0-5 ii libcolord-gtk4-1 0.3.0-3 ii libcolord21.4.6-1 ii libcups2 2.4.1op1-2 ii libepoxy0 1.5.10-1 ii libfontconfig12.13.1-4.4 ii libgcr-base-3-1 3.40.0-4 ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1 ii libglib2.0-0 2.72.1-1 ii libgnome-bg-4-1 42.1-1 ii libgnome-bluetooth-ui-3.0-13 42.0-5 ii libgnome-desktop-4-1 42.1-1 ii libgnome-rr-4-1 42.1-1 ii libgnutls30 3.7.4-2 ii libgoa-1.0-0b 3.44.0-1 ii libgoa-backend-1.0-1 3.44.0-1 ii libgsound01.0.3-2 ii libgtk-3-03.24.33-2 ii libgtk-4-14.6.4+ds-3 ii libgtop-2.0-112.40.0-2 ii libgudev-1.0-0237-2 ii libibus-1.0-5 1.5.26-4 ii libkrb5-3 1.19.2-2+b1 ii libmalcontent-0-0 0.10.3-1 ii libmm-glib0 1.18.8-1 ii libnm01.38.0-2 ii libnma-gtk4-0 1.8.38-1 ii libpango-1.0-01.50.7+ds-1 ii libpangocairo-1.0-0 1.50.7+ds-1 ii libpolkit-gobject-1-0 0.105-33 ii libpulse-mainloop-glib0 15.0+dfsg1-4 ii libpulse0 15.0+dfsg1-4 ii libpwquality1 1.4.4-1+b1 ii libsecret-1-0 0.20.5-2 ii libsmbclient 2:4.16.1+dfsg-4 ii libudisks2-0 2.9.4-1 ii libupower-glib3 0.99.18-2 ii libwacom9 2.2.0-1 ii libx11-6 2:1.7.5-1 ii libxi62:1.8-1 ii libxml2 2.9.14+dfsg-1 Versions of packages gnome-control-center recommends: ii cracklib-runtime 2.9.6-4 ii cups-pk-helper0.2.6-1+b1 ii gkbd-capplet 3.26.1-2 ii gnome-online-accounts 3.44.0-1 ii gnome-user-docs 42.0-1 ii gnome-user-share 3.34.0-5 ii iso-codes 4.9.0-1 ii libnss-myhostname 250.4-1 ii malcontent-gui0.10.3-1 ii network-manager-gnome 1.26.0-1 ii policykit-1 0.105-33 ii power-profiles-daemon 0.10.1-3 ii pulseaudio-module-bluetooth 15.0+dfsg1-4 ii realmd0.17.0-1+b1 ii rygel 0.40.3-1+b1 ii system-config-printer-common 1.5.16-1 Versions of packages gnome-control-cen
Bug#1008707: RFS: calamares-extensions/1.2.1-1 [ITP] -- Mobile module for Calamares installer framework
Please keep the git repo updated as well. I held out pushing until I was happy with the upload, then promptly started something else. Pushed now.
Bug#1008707: RFS: calamares-extensions/1.2.1-1 [ITP] -- Mobile module for Calamares installer framework
control: tags -1 -moreinfo Hi, Thanks for having a look at calamares-extensions On 4/27/22 04:44, Bastian Germann wrote: Control: tags -1 moreinfo On Thu, 31 Mar 2022 08:28:58 +1100 undef wrote: Changes for the initial release: calamares-extensions (1.2.1-1) UNRELEASED; urgency=medium . * Initial Release (Closes: #998858) When you propose a team-maintained package, please ask the team for sponsorship first. If you have asked and they did not respond, please explain the details. I've discussed the package with the QT KDE Team on IRC. They were happy with me working on the package under their team but did not have the time to help with maintenance. As I have already been maintaining the package for Mobian outside of Debian I was happy with this. I have not had a response to my sponsorship requests over IRC. You have to target unstable or experimental with a new package. Please provide a new upload and untag moreinfo. Fixed in the latest version on Debian Mentors.
Bug#1008707: RFS: calamares-extensions/1.2.1-1 [ITP] -- Mobile module for Calamares installer framework
Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "calamares-extensions": * Package name : calamares-extensions Version : 1.2.1-1 Upstream Author : Calamares * URL : https://github.com/calamares/calamares-extensions * License : BSD-2-clause, BSD-3-clause, GPL-3+ * Vcs : https://salsa.debian.org/qt-kde-team/extras/calamares-extensions Section : utils This package provides additional functionality for calamares, such as a Mobile UI and rEFInd bootloader configuration module. The source builds the following binary packages: calamares-extensions - Mobile module for Calamares installer framework calamares-extensions-data - Mobile module for Calamares installer framework - data files To access further information about this package, please visit the following URL: https://mentors.debian.net/package/calamares-extensions/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/c/calamares-extensions/calamares-extensions_1.2.1-1.dsc Changes for the initial release: calamares-extensions (1.2.1-1) UNRELEASED; urgency=medium . * Initial Release (Closes: #998858) Thank you, Jarrah Gosbell
Bug#1006642: [Debian-on-mobile-maintainers] Bug#1006642: osk-sdl: autopkgtest failure (with gcc-12)
Source: osk-sdl Version: 0.66-4 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, The autopkgtest for you package fail (with gcc-12): Thanks for reporting this. I'm able to reproduce it locally and have forwarded it on to the upstream author. https://gitlab.com/postmarketOS/osk-sdl/-/issues/143 Regards, Undef.
Bug#1006668: u-boot-menu: Support for custom initrd configuration
Package: u-boot-menu
Version: 4.0.3
Severity: normal
Tags: patch
X-Debbugs-Cc: undef
Dear Maintainer,
Currently the initrd section of the generated extlinux.conf will only use
discovered
initrd.img-* files from /boot. However, some systems (discovered on the
PinePhone Pro,
but other reclaimed Android devices are affected) require a custom "miniramfs"
to be used.
Would it be possible to include the ability to manually set the initrd record in
/etc/default/u-boot? The attached patch allows a static configuration which
will be used
for all kernels. An alternative would be setting "/miniramfs-${_VERSION}".
Thanks for considering,
Undef.
-- System Information:
Debian Release: 11.2
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.11-1.fc32.qubes.x86_64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages u-boot-menu depends on:
ii linux-base 4.6
u-boot-menu recommends no packages.
Versions of packages u-boot-menu suggests:
pn flash-kernel
-- no debconf information
*** 0001-Allow-configuration-of-initrd-file.patch
>From 14daba63b9c1036b7672f144d29a848e306992b0 Mon Sep 17 00:00:00 2001
From: Undef
Date: Wed, 2 Mar 2022 00:02:12 +
Subject: [PATCH] Allow configuration of initrd file
Some devices have initrd requirements that cause the standard
initrd.img-${_VERSION} to fail to boot. For example, the PinePhone Pro
will fail to boot with large initrd files, solved by using a
miniramfs[0] to chainload the real initrd.
This allows specifying the INITRD manually in /etc/default/u-boot. If
the configuration is either not present or empty, the existing initrd
discovery functionality will continue to be used.
[0] https://gitlab.com/mobian1/miniramfs
---
u-boot-update | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/u-boot-update b/u-boot-update
index da92918..4d3b395 100755
--- a/u-boot-update
+++ b/u-boot-update
@@ -92,6 +92,7 @@ U_BOOT_TIMEOUT="${U_BOOT_TIMEOUT:-50}"
U_BOOT_MENU_LABEL="${U_BOOT_MENU_LABEL:-${PRETTY_NAME:-Debian GNU/Linux
kernel}}"
U_BOOT_PARAMETERS="${U_BOOT_PARAMETERS:-ro quiet}"
U_BOOT_FDT_DIR="${U_BOOT_FDT_DIR:-/usr/lib/linux-image-}"
+U_BOOT_INITRD="${U_BOOT_INITRD:-}"
# Find parameter for root from fstab
if [ -z "${U_BOOT_ROOT}" ]
@@ -169,7 +170,10 @@ do
_NUMBER="${_NUMBER:-0}"
_ENTRY="${_ENTRY:-1}"
- if [ -e /boot/initrd.img-${_VERSION} ]
+ if [ -n "${U_BOOT_INITRD}" ]
+ then
+ _INITRD="initrd ${U_BOOT_INITRD}"
+ elif [ -e /boot/initrd.img-${_VERSION} ]
then
_INITRD="initrd ${_BOOT_DIRECTORY}/initrd.img-${_VERSION}"
else
--
2.30.2
Bug#1001809: [Debian-on-mobile-maintainers] Bug#1001809: libsdl2/2.0.18 breaks osk-sdl autopkgtest: Testing osk toggle button and 'mouse' key input
Hi Simon, See https://github.com/libsdl-org/SDL/issues/5136 for further analysis. osk-sdl maintainers: you might want to consider applying and/or upstreaming some of the "test: ..." commits from https://gitlab.com/smcv/osk-sdl/-/commits/reproduce-sdl-regression to improve the ability to debug this unit test. I do not intend to upstream these myself; feel free to redo them if a modified version makes more sense to you (but please move my name to a Co-authored-by if you do that). Thanks for doing the analysis on this one, I've been meaning to get to it for a while now. I'll take a look at those commits early in the new year and see whether upstream is interested in them. They certainly look helpful for tracking this one down.
Bug#998858: ITP: calamares-extensions -- Extra modules for the Calamares installer framework.
Package: wnpp Severity: wishlist Owner: Jarrah Gosbell X-Debbugs-Cc: debian-de...@lists.debian.org, Jarrah Gosbell * Package name: calamares-extensions Version : 1.1.2 Upstream Author : Adriaan de Groot * URL : https://github.com/calamares/calamares-extensions * License : GPL, BSD, CC0 Programming Lang: C++, Python Description : Extra modules for the Calamares installer framework. Provides extra modules used by the Calamares installer framework such as the Mobile module to be used on handheld devices such as phones. This package is a dependancy for Mobian Installer, which provides features such as full disk encryption in a user friendly manner. Packaging already exists under Mobian. I will maintain this package under the KDE Extras Team. I am looking for a sponsor, both for upload and support in verifying the packaging, though it has been well tested in Mobian.
Bug#986017: unblock: osk-sdl/0.62.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: undef
Please unblock package osk-sdl
[ Reason ]
Help users understand the purpose of osk-sdl when the O.S.K appeas
during boot without specific context information.
[ Impact ]
Some users have been unable to use their device, not knowing that the
presented keyboard was for disk decryption.
[ Tests ]
This issue is fixed with a 50 line patch provided by upstream.
Manual tests by upstream, as well as with this package have
shown that the issue is fixed.
[ Risks ]
while the code change is non-trivial, it has been throughly tested
across two different Linux distributions. I consider the risk to be low.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock osk-sdl/0.62.1-2
diff -Nru osk-sdl-0.62.1/debian/changelog osk-sdl-0.62.1/debian/changelog
--- osk-sdl-0.62.1/debian/changelog 2021-01-22 21:32:26.0 +
+++ osk-sdl-0.62.1/debian/changelog 2021-03-16 08:14:26.0 +
@@ -1,3 +1,10 @@
+osk-sdl (0.62.1-2) unstable; urgency=medium
+
+ [ Jarrah Gosbell ]
+ * Backport tooltip from 0.64 (unreleased)
+
+ -- Jarrah Gosbell Tue, 16 Mar 2021 08:14:26 +
+
osk-sdl (0.62.1-1) unstable; urgency=medium
[ undef ]
diff -Nru
osk-sdl-0.62.1/debian/patches/0001-tooltip-add-support-for-specifying-the-type-of-toolt.patch
osk-sdl-0.62.1/debian/patches/0001-tooltip-add-support-for-specifying-the-type-of-toolt.patch
---
osk-sdl-0.62.1/debian/patches/0001-tooltip-add-support-for-specifying-the-type-of-toolt.patch
1970-01-01 00:00:00.0 +
+++
osk-sdl-0.62.1/debian/patches/0001-tooltip-add-support-for-specifying-the-type-of-toolt.patch
2021-03-16 08:14:26.0 +
@@ -0,0 +1,110 @@
+From 794d4fc5d4a6e38c56b826ce7cca8dc5a373fdcc Mon Sep 17 00:00:00 2001
+From: Clayton Craft
+Date: Thu, 4 Mar 2021 01:16:53 -0800
+Subject: [PATCH 1/3] tooltip: add support for specifying the type of tooltip
+ to render
+
+Tooltips can be themed/colored based on type with this change. Only two
+types ('info' and 'error') are introduced here.
+---
+ src/tooltip.cpp | 22 +-
+ src/tooltip.h | 9 -
+ 2 files changed, 25 insertions(+), 6 deletions(-)
+
+diff --git a/src/tooltip.cpp b/src/tooltip.cpp
+index 5d288e8..e07dfb9 100644
+--- a/src/tooltip.cpp
b/src/tooltip.cpp
+@@ -20,11 +20,12 @@ along with this program. If not, see
<http://www.gnu.org/licenses/>.
+ #include "tooltip.h"
+ #include "draw_helpers.h"
+
+-Tooltip::Tooltip(int width, int height, int cornerRadius, Config *config)
++Tooltip::Tooltip(TooltipType type, int width, int height, int cornerRadius,
Config *config)
+ : config(config)
+ , width(width)
+ , height(height)
+ , cornerRadius(cornerRadius)
++ , type(type)
+ {
+ }
+
+@@ -32,6 +33,7 @@ int Tooltip::init(SDL_Renderer *renderer, const std::string
)
+ {
+ SDL_Surface *surface;
+ Uint32 rmask, gmask, bmask, amask;
++ argb foregroundColor, backgroundColor;
+ // SDL interprets each pixel as a 32-bit number, so our masks must
depend
+ // on the endianness (byte order) of the machine
+ #if SDL_BYTEORDER == SDL_BIG_ENDIAN
+@@ -52,8 +54,19 @@ int Tooltip::init(SDL_Renderer *renderer, const std::string
)
+ return -1;
+ }
+
+- Uint32 background = SDL_MapRGB(surface->format,
config->inputBoxBackgroundError.r,
+- config->inputBoxBackgroundError.g,
config->inputBoxBackgroundError.b);
++ switch (type) {
++ case TooltipType::error:
++ foregroundColor = config->inputBoxForegroundError;
++ backgroundColor = config->inputBoxBackgroundError;
++ break;
++ case TooltipType::info:
++ default:
++ foregroundColor = config->inputBoxForeground;
++ backgroundColor = config->inputBoxBackground;
++ break;
++ }
++
++ Uint32 background = SDL_MapRGB(surface->format, backgroundColor.r,
backgroundColor.g, backgroundColor.b);
+ SDL_FillRect(surface, nullptr, background);
+
+ if (cornerRadius > 0) {
+@@ -63,8 +76,7 @@ int Tooltip::init(SDL_Renderer *renderer, const std::string
)
+
+ TTF_Font *font = TTF_OpenFont(config->keyboardFont.c_str(),
config->keyboardFontSize);
+ SDL_Surface *textSurface;
+- SDL_Color textColor = { config->inputBoxForegroundError.r,
config->inputBoxForegroundError.g,
+- config->inputBoxForegroundError.b,
config->inputBoxForegroundError.a };
++ SDL_Color textColor = { foregroundColor.r, foregroundColor.g,
foregroundColor.b, foregroundColor.a };
+ textSurface = TTF_RenderText_Blended(font, text.c_str(), textColor);
+
+ SDL_Rect textRect;
+diff --git
Bug#979870: RFS: osk-sdl/0.62-1 [ITP] -- Disk encryption initramfs on screen keyboard
Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package "osk-sdl": * Package name : osk-sdl Version : 0.62-1 Upstream Author : PostmarketOS - Clayton Craft * URL : https://gitlab.com/postmarketOS/osk-sdl * License : GPL-3+ * Vcs : https://salsa.debian.org/DebianOnMobile-team/osk-sdl Section : utils It builds those binary packages: osk-sdl - Disk encryption initramfs on screen keyboard To access further information about this package, please visit the following URL: https://salsa.debian.org/DebianOnMobile-team/osk-sdl Changes since the last upload: This package has not been uploaded before. Regards, -- Undef
Bug#972364: ITP: osk-sdl -- Onscreen keyboard for unlocking LUKS devices
Package: wnpp Severity: wishlist Owner: undef * Package name : osk-sdl Version : 0.58 Upstream Author : Oliver Smith * URL : https://gitlab.com/postmarketOS/osk-sdl * License : GPLv3 Programming Lang: C++ Description : Onscreen keyboard for unlocking LUKS devices An on-screen keyboard used to unlock the encrypted root partition on mobile devices. This package is a dependency for full disk encryption with user held passwords on devices which do not have a non-touchscreen input device. It implements the same functionality as cryptsetup-initramfs, but also includes the input device. The package will be maintained inside the Debian on Mobile team.
