Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng
On 5/30/23 19:39, Dennis Heddicke wrote: Hello, i have a problem with "apt update", everytime i execute the command, i get the following error messages: Get:1 http://security.debian.org/debian-security bookworm-security InRelease [48,0 kB] Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB] Err:1 http://security.debian.org/debian-security bookworm-security InRelease The following signatures were invalid: BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key (10/buster) Err:2 http://deb.debian.org/debian bookworm InRelease The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster) Fetched 241 kB in 0s (507 kB/s) Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.debian.org/debian-security bookworm-security InRelease: The following signatures were invalid: BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key (10/buster) W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bookworm InRelease: The following signatures were invalid: BADSIG 648ACFD622F3D 138 Debian Archive Automatic Signing Key (10/buster) W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian Archive Automatic Signing Key (10/buster) W: Failed to fetch http://security.debian.org/debian-security/dists/bookworm-security/InRelease The following signatures were invalid: BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key (10/buster) W: Some index files failed to download. They have been ignored, or old ones used instead. I use Debian 12. The only changes i did before the problem occurred, were the installation of apt-cacher-ng and i ran "mach bootstrap" in a chroot. If you remove apt-cacher-ng, does it work at all? -- John Doe
Problem with apt maybe related to installation/configuration of apt-cacher-ng
Hello,
i have a problem with "apt update", everytime i execute the command, i
get the following error messages:
Get:1 http://security.debian.org/debian-security bookworm-security
InRelease [48,0 kB]
Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB]
Err:1 http://security.debian.org/debian-security bookworm-security
InRelease
The following signatures were invalid: BADSIG 112695A0E562B32A Debian
Security Archive Automatic Signing Key (10/buster)
Err:2 http://deb.debian.org/debian bookworm InRelease
The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian
Archive Automatic Signing Key (10/buster)
Fetched 241 kB in 0s (507 kB/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://security.debian.org/debian-security bookworm-security
InRelease: The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster)
W: An error occurred during the signature verification. The repository
is not updated and the previous index files will be used.
GPG error: http://deb.debian.org/debian bookworm InRelease: The
following signatures were invalid: BADSIG 648ACFD622F3D
138 Debian Archive Automatic Signing Key (10/buster)
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease
The following signatures were invalid: BADSIG 648ACFD622F3D138
Debian Archive Automatic Signing Key (10/buster)
W: Failed to fetch
http://security.debian.org/debian-security/dists/bookworm-security/InRelease
The following signatures were invalid:
BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
(10/buster)
W: Some index files failed to download. They have been ignored, or old
ones used instead.
I use Debian 12. The only changes i did before the problem occurred,
were the installation of apt-cacher-ng and i ran "mach bootstrap" in a
chroot. I don't think, the last thing would change this much the
operating system, although it was a stupid idea. Even more stupid, since
the solution for my problem was the installation of "sudo" in the
chroot. 🙁 So maybe the first one is responsible for the problem.
So far I tried the following configurations for apt-cacher-ng, to
resolve the problem:
Acquire::http::proxy "http://localhost:3142";;
Acquire::https::proxy "https://";;
and
Acquire::http {Proxy "http://127.0.0.1:3142";; };
Acquire::https {Proxy "https://";; };
but none solved it.
I hope someone can help me with my problem. Thank you in advance.
Best Regards
Dennis
Re: Bookworm soft lockup
On Wed, 17 May 2023 02:12:32 +0100, Philip Wyett wrote: A little research shows that this is not that uncommon. A suggested workaround is to disable the power management for the device as follows. Create a file (such as): /etc/modprobe.d/snd-intel-disable-power-management.conf Add the following line: options snd_hda_intel power_save=0 Reboot. Hopefully this may assist. I tried: $ ls -l /etc/modprobe.d/snd-intel-disable-power-management.conf -rw-r- 1 root root 36 May 23 10:01 /etc/modprobe.d/snd-intel-disable-power-management.conf $ sudo cat /etc/modprobe.d/snd-intel-disable-power-management.conf options snd_hda_intel power_save=0 Nevertheless, this morning I arrived to the locked-up state. Journalctl output: May 31 04:17:01 gar CRON[2175]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) May 31 04:17:01 gar CRON[2174]: pam_unix(cron:session): session closed for user root May 31 05:12:00 gar kernel: snd_hda_intel :04:00.0: Unable to change power state from D3hot to D0, device inaccessible May 31 05:12:03 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* render: timed out waiting for forcewake ack to clear. May 31 05:12:03 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:07 gar kernel: INFO: NMI handler (perf_event_nmi_handler) took too long to run: 84.155 msecs May 31 05:12:07 gar kernel: perf: interrupt took too long (657458 > 2500), lowering kernel.perf_event_max_sample_rate to 250 May 31 05:12:07 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* render: timed out waiting for forcewake ack to clear. May 31 05:12:07 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:11 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* render: timed out waiting for forcewake ack to clear. May 31 05:12:11 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:15 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* gt: timed out waiting for forcewake ack to clear. May 31 05:12:15 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:16 gar kernel: i915 :03:00.0: [drm] *ERROR* CT: Corrupted descriptor head=4294967295 tail=4294967295 status=0xf> May 31 05:12:27 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* render: timed out waiting for forcewake ack to clear. May 31 05:12:27 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:27 gar kernel: [drm:fw_domains_get_with_fallback [i915]] *ERROR* gt: timed out waiting for forcewake ack to clear. May 31 05:12:27 gar kernel: i915 :03:00.0: [drm:add_taint_for_CI [i915]] CI tainted:0x9 by fw_domains_get_with_fallback+0x20c/0x> May 31 05:12:27 gar kernel: watchdog: BUG: soft lockup - CPU#14 stuck for 26s! [kworker/14:2:2123] May 31 05:12:27 gar kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nfsv3 nfs_acl rpcsec_gss_krb5 auth_r> May 31 05:12:27 gar kernel: intel_uncore wmi_bmof ee1004 pcspkr watchdog soundcore intel_vsec serial_multi_instantiate intel_pmc_co> May 31 05:12:27 gar kernel: CPU: 14 PID: 2123 Comm: kworker/14:2 Tainted: G U W 6.1.0-9-amd64 #1 Debian 6.1.27-1 May 31 05:12:27 gar kernel: Hardware name: Micro-Star International Co., Ltd. MS-7E02/PRO B760M-P DDR4 (MS-7E02), BIOS 1.00 10/21/20> May 31 05:12:27 gar kernel: Workqueue: pm pm_runtime_work May 31 05:12:27 gar kernel: RIP: 0010:pci_mmcfg_read+0xb0/0xe0 May 31 05:12:27 gar kernel: Code: 5d 41 5e 41 5f c3 cc cc cc cc 4c 01 e0 66 8b 00 0f b7 c0 89 45 00 eb dc 4c 01 e0 8a 00 0f b6 c0 89> May 31 05:12:27 gar kernel: RSP: 0018:b5ce87b9bcc0 EFLAGS: 0286 May 31 05:12:27 gar kernel: RAX: RBX: 0040 RCX: 0ffc May 31 05:12:27 gar kernel: RDX: 00ff RSI: 0004 RDI: May 31 05:12:27 gar kernel: RBP: b5ce87b9bcfc R08: 0004 R09: b5ce87b9bcfc May 31 05:12:27 gar kernel: R10: 0004 R11: b19a70a0 R12: 0ffc May 31 05:12:27 gar kernel: R13: R14: 0004 R15: May 31 05:12:27 gar kernel: FS: () GS:9c641fb8() knlGS: May 31 05:12:27 gar kernel: CS: 0010 DS: ES: CR0: 80050033 May 31 05:12:27 gar kernel: CR2: 7f78df2005c9 CR3: 00010571e005 CR4: 00770ee0 May 31 05:12:27 gar kernel: PKRU: 5554 May 31 05:12:27 gar kernel: Call Trace: May 31 05:12:27 gar kernel: May 31 05:12:27 gar kernel: pci_bus_read_config_dword+0x46/0x80 May 31 05:12:27 gar kernel: pci_find_next_ext_capability+0x82/0xe
Re: no pwm
Replying to me directly is snowballing... On 5/29/23 20:36, Aleix Piulachs wrote: mar, 30 may 2023 a las 5:30, David Christensen On 5/29/23 19:56, Aleix Piulachs wrote: El El lun, 29 may 2023 a las 9:59, David Christensen On 5/28/23 19:27, Aleix Piulachs wrote: i use an hp with bullseye7-386 and it does not support pwm. what can i use instead of pwm because it gets very hot Computer hp compaq 6830s intel pentium dual cpu t3400 Looking at the "HP Compaq 6830s Notebook PC Maintenance and Service Guide" and the figure "Computer major components" (page 16), it looks like that laptop has one fan and one heat sink/ heat pipe: https://support.hp.com/us-en/product/hp-compaq-6830s-notebook-pc/3688712/manuals The fan runs from windows7 because stays in ram but from bullseye no and the temperature is over 55 or so degrees Again, please "Reply to list" instead of replying to me directly. What do you mean by "because stays in ram"? Looking at the "Computer Setup User Guide" -> "System Configuration menu" -> "Device Configurations" (page 9), I see one option for the fan: Enable/disable fan always on while connected to an AC outlet (enabled by default). Please connect the computer power adapter, verify that the above Setup setting is enabled, and test for fan operation with both Windows 7 and with Debian 11. Again, please answer the following questions: * Under what operating conditions does the processor get hot? * Have you cleaned the fan, heat sink, and chassis internals with a vacuum cleaner? On 5/29/23 20:47, Aleix Piulachs wrote: And I can’t find b43/ucode15.fw and b43-open/ucode15.fw free firmware files either Searching package directories for "b32": https://www.debian.org/distrib/packages I see 3 results: * b43-fwcutter * firmware-b43-installer * firmware-b43legacy-installer All three are "contrib" packages, which means your need to edit /etc/apt/sources.list and add "contrib". Here is my sources.list FYI: 2023-05-29 20:59:17 dpchrist@taz ~/src/perl/Dpchrist-Lib5/lib/Dpchrist/Lib5 $ cat /etc/apt/sources.list deb http://deb.debian.org/debian/ bullseye main contrib non-free deb http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb-src http://deb.debian.org/debian/ bullseye main contrib non-free deb-src http://deb.debian.org/debian/ bullseye-updates main contrib non-free deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free Then run: # apt-get update I am unsure which package is correct. I would try installing firmware-b43-installer: # apt-get install firmware-b43-installer Then reboot and test. If that does not work, I would try installing firmware-b43legacy-installer: # apt-get remove firmware-b43-installer # apt-get install firmware-b43legacy-installer Then reboot and test. David
Re: There appears to be a problem with openbox-menu for my installation from "Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46"
"Susmita/Rajib" wrote: > Then there are: > /etc/xdg/menus/kf5-applications.menu > /etc/xdg/menus/lxlauncher-applications.menu > /etc/xdg/menus/lxde-applications.menu > > Then there is also another directory by name > /etc/xdg/menus/applications-merged with a .menu file > ~/.config/menus/debian-menu.menu You can choose the menu layout you prefer. Run it like this for example: openbox-menu kf5-applications.menu By default it's looking for applications.menu with paths set in $XDG_CONFIG_DIRS. To add it to the Openbox menu, edit ~/.config/openbox/menu.xml and replace: with: For the questions related to the main menu in LXDE, I don't know.
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
On Tue, May 30, 2023 at 05:58:01PM +0100, debian-u...@howorth.org.uk wrote: > wrote: [avoiding pulseaudio...] > > [1] in spite of stubborn applications: firefox, I'm looking at you. > > Using apulse solves that for me for now :) You got it :) Cheers -- t signature.asc Description: PGP signature
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
On Tue, May 30, 2023 at 8:25 AM wrote: > > On Tue, May 30, 2023 at 09:20:47PM +0900, Byung-Hee HWANG (황병희) wrote: > > [...] > > > Also i'm using old things such as old smartphone(s) made by LG, and old > > book <>, and old Tractor > > (my day job is farmer in South Korea). > > Farmers are the most important people: they feed us. A close second: cooks. Truckers get my vote for second. Jeff
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
wrote: > On Tue, May 30, 2023 at 02:04:01PM +0200, Nicolas George wrote: > > to...@tuxteam.de (12023-05-30): > > > > > Rajib. In the future, all most GUI desktop(s) will run under > > > > > Wayland. So i suggest that you have to adapt to change, > > > > > IMHO. > > > I'm still hoping I give up on computers before that happens ;-) > > > > The most likely is that Freedesktop will introduce something that > > obsoletes Wayland and something that obsoletes that thing that > > obsoletes Wayland before the move to Wayland is complete. > > I think that's called "leapfrogging". Having successfully avoided > pulseaudio up to now [1], I'm seriously looking into pipewire... You're braver than I am. Let me/us know how it goes. > Cheers > > [1] in spite of stubborn applications: firefox, I'm looking at you. Using apulse solves that for me for now :)
Re: root password of debian live cd?
Timothy M Butterworth writes: > On Tue, May 30, 2023 at 2:03 AM hlyg wrote: > > > On 5/30/23 12:37, to...@tuxteam.de wrote: > > > > This seems to have been discussed like eight years ago: > > > > https://lists.debian.org/debian-live/2015/05/msg00081.html > > > > Perhaps it should go into a FAQ. > > > > Cheers > > > Thank tomas! > > many packages break because of empty password? some other distro > have no > password for live cd, they don't break? > > i have tried latest deb11 live cd for i386/gnome, live or Live > aren't > correct passwords > > > The Live CD has no root password you have to use sudo. Someone here suggested using live-config as a command line parameter in Grub. https://forums.debian.net/viewtopic.php?t=102937 If you are logged in as user you can use: sudo bash To get a root command prompt and set the root passwd using passwd
Re: root password of debian live cd?
On Tue, 2023-05-30 at 00:05 -0400, Timothy M Butterworth wrote: > > > On Tue, May 30, 2023 at 12:02 AM hlyg wrote: > > Thank bw! internet search also shows that live is password, but > > it's not > > correct > > > > > Live is the password you use with sudo as there is no root password > set. > > > i have rebooted, > > > > > probably something like this > > > https://en.wikipedia.org/wiki/Principle_of_least_privilege > > > > > > . > > i think they disclaim all responsibilities, they can use empty > > password, > > as some other distro do > > > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄⠀⠀ I don't mean to clog up this thread with an unnecessary post, but I just wanted to note that I (unfortunately) have had to use (as recently as 2023-05-28): debian-live-11.7.0-amd64-gnome+nonfree.iso a number of times recently, due to flatpak being a corpulent space hog, obnoxiously trying very hard to fill up my /var partition (10Gb, as originally set by the Debian installer). But that is just a side issue. (Note: this is the Gnome Live image that has the non-free extra drivers, etc., not the "standard" Debian Live image. Perhaps the standard Debian Live image works differently; I never use it. And note, this is Debian 11.7 (Bullseye), Debian 12 (Bookworm) may also act differently. I can state that in my experience, unequivocally, it boots into a Gnome DE without any password needed. If administrative permission is needed to do something, "sudo " works, without having to enter any password. Example: sudo apt install timeshift This post is just a FWIW. Feel free to disregard.
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
On Tue, May 30, 2023 at 09:20:47PM +0900, Byung-Hee HWANG (황병희) wrote: [...] > Also i'm using old things such as old smartphone(s) made by LG, and old > book <>, and old Tractor > (my day job is farmer in South Korea). Farmers are the most important people: they feed us. A close second: cooks. Cheers -- t signature.asc Description: PGP signature
Re: There appears to be a problem with openbox-menu for my installation from "Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46"
On Tue, May 30, 2023 at 08:12:28PM +0800, t...@dkinbox.com wrote: > > > > Dear Illustrious Leaders and Senior Members of Debian Users ML, > > > > Out of intuition, after I extensively gathered information on LXDE and > > OpenBox, I checked the OpenBox installation from the LXDE ISO, > > `Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46`. > > > > what's OpenBox in debian world? sudo apt-get install openbox Cheers -- t signature.asc Description: PGP signature
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
On Tue, May 30, 2023 at 02:04:01PM +0200, Nicolas George wrote: > to...@tuxteam.de (12023-05-30): > > > > Rajib. In the future, all most GUI desktop(s) will run under Wayland. > > > > So i suggest that you have to adapt to change, IMHO. > > I'm still hoping I give up on computers before that happens ;-) > > The most likely is that Freedesktop will introduce something that > obsoletes Wayland and something that obsoletes that thing that obsoletes > Wayland before the move to Wayland is complete. I think that's called "leapfrogging". Having successfully avoided pulseaudio up to now [1], I'm seriously looking into pipewire... Cheers [1] in spite of stubborn applications: firefox, I'm looking at you. -- tomás signature.asc Description: PGP signature
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
debian-u...@howorth.org.uk writes: > Byung-Hee HWANG (황병희) wrote: >> > (...) >> > I have begun to dislike Gnome when it switched over to wayland >> > desktop environment. I don't like it. (...) >> >> Rajib. In the future, all most GUI desktop(s) will run under Wayland. >> So i suggest that you have to adapt to change, IMHO. > > It won't be for a considerable time yet, if at all, so there's no need > to opt for the pain now if he doesn't want. > Thanks! You are right. Also i'm using old things such as old smartphone(s) made by LG, and old book <>, and old Tractor (my day job is farmer in South Korea). By the way, really i like Gnome Desktop ^^^ Sincerely, Byung-Hee -- ^고맙습니다 _布德天下_ 감사합니다_^))//
Re: There appears to be a problem with openbox-menu for my installation from "Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46"
> Dear Illustrious Leaders and Senior Members of Debian Users ML, > > Out of intuition, after I extensively gathered information on LXDE and > OpenBox, I checked the OpenBox installation from the LXDE ISO, > `Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46`. > what's OpenBox in debian world? > -- Sent from https://dkinbox.com/
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
to...@tuxteam.de (12023-05-30): > > > Rajib. In the future, all most GUI desktop(s) will run under Wayland. > > > So i suggest that you have to adapt to change, IMHO. > I'm still hoping I give up on computers before that happens ;-) The most likely is that Freedesktop will introduce something that obsoletes Wayland and something that obsoletes that thing that obsoletes Wayland before the move to Wayland is complete. Regards, -- Nicolas George
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
On Tue, May 30, 2023 at 12:42:12PM +0100, debian-u...@howorth.org.uk wrote: > Byung-Hee HWANG (황병희) wrote: > > > (...) > > > I have begun to dislike Gnome when it switched over to wayland > > > desktop environment. I don't like it. (...) > > > > Rajib. In the future, all most GUI desktop(s) will run under Wayland. > > So i suggest that you have to adapt to change, IMHO. > > It won't be for a considerable time yet, if at all, so there's no need > to opt for the pain now if he doesn't want. I'm still hoping I give up on computers before that happens ;-) Cheers -- t signature.asc Description: PGP signature
Re: Isn't KDE Live ISO accompanied by an ultra-light Windows Manager, like OpenBox is with LXDE?
Byung-Hee HWANG (황병희) wrote: > > (...) > > I have begun to dislike Gnome when it switched over to wayland > > desktop environment. I don't like it. (...) > > Rajib. In the future, all most GUI desktop(s) will run under Wayland. > So i suggest that you have to adapt to change, IMHO. It won't be for a considerable time yet, if at all, so there's no need to opt for the pain now if he doesn't want.
Re: There appears to be a problem with openbox-menu for my installation from "Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46"
From: Pierre Tomon Date: Tue, 30 May 2023 09:14:11 +0200 Message-id: <[🔎] 4qvkcn2zj8zmp...@smtp-2-0001.mail.infomaniak.ch> [ ... ] You need an application menu layout. cp /etc/xdg/menus/lxde-applications.menu ~/.config/menus/applications.menu [ ... ] But Mr. Tomon, what about the menus built at: /etc/xdg/menus/debian-menu.menu (shortcut leading to) /var/lib/menu-xdg/menus/debian-menu.menu, with its almost identical menu file exists at ~/.config/menus/debian-menu.menu. Except the line: `/var/lib/menu-xdg/applications ` and the line: /var/lib/menu-xdg/desktop-directories/menu-xdg replaced by: ~/.local/share/desktop-directories/menu-xdg It appears as if some menu building application used the template directory /var/lib/menu-xdg/desktop-directories/menu-xdg to create the desktop configuration files at ~/.local/share/desktop-directories/menu-xdg Then there are: /etc/xdg/menus/kf5-applications.menu /etc/xdg/menus/lxlauncher-applications.menu /etc/xdg/menus/lxde-applications.menu Then there is also another directory by name /etc/xdg/menus/applications-merged with a .menu file ~/.config/menus/debian-menu.menu Now what about the complete application .desktop files for individual programs installed that form the sub-menus, sub-sub-menus and so on under the main Start Menu of lxde, lying at /usr/share/applications/ ? There is also another set of .desktop files for individual programs at /home/rajib/.local/share/applications/menu-xdg I can't blindly follow commands unless I can have the complete picture, of what lxde does, before me.
buster docker has issue with bookworm container
Hello,
I had a few issues with building a bookworm container using the
debian:bookworm image (problems with repository signatures and lzma
decompression errors) on a buster docker host.
The buster and bullseye containers seem to work like a charm though.
So I went the bullseye -> upgrade to bookworm path with the Dockerfile
below. I apply a work-around in the Dockerfile ("fixing" the error with the
cleaning of the apt archives in /etc/apt/apt.conf.d/docker-clean), and
it fixed the repository GPG errors (it seems the /etc/apt/sources.list
in the debian:bookworm has direct key references that do not exist/do
not contain the correct keys).
But, the apparently last problem I can't seem to fix is the following:
dpkg-deb (subprocess): decompressing archive
'/var/cache/apt/archives/util-linux_2.38.1-5+b1_amd64.deb' (size=1176996)
member 'control.tar': lzma error: Cannot allocate memory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
dpkg-deb: error: tar subprocess returned error exit status 2
dpkg: error processing archive
/var/cache/apt/archives/util-linux_2.38.1-5+b1_amd64.deb (--unpack): dpkg-deb
--control subprocess returned error exit status 2
dpkg-deb (subprocess): decompressing archive
'/var/cache/apt/archives/util-linux-extra_2.38.1-5+b1_amd64.deb' (size=110520)
member 'control.tar': lzma error: Cannot allocate memory
tar: This does not look like a tar archive
This is reproducible, this is not a transient error.
It seems as if libzma does not have enough RAM to do the decompression
here. I found notably an issue with 32 bit address space, but this is
amd64.
Also, the container has no specific limits (it is not better with
docker build -m 100g), and free reports:
totalusedfree shared buff/cache available
Mem: 4024628 940056 208924 16012 3152384 3084572
Swap:7811068 2 7755516
So, is this some libzma config somewhere, or maybe a missing / changed
syscall which makes libzma thinks it does not have enough memory?
If I try to decompress, manually, with ar, then xz the above util-linux
downloaded deb, on a buster and bullseye container and there is no
issue, which seems to exclude a problem with cgroup limitations that I
didn't see.
Do you have maybe any idea (except upgrading the host to bullseye or
bookworm)?
Thank you.
FROM debian:bullseye
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update && apt-get -y dist-upgrade \
&& sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list \
&& rm -f /etc/apt/apt.conf.d/docker-clean \
&& apt-get update && apt-get -y upgrade \
&& echo update/upgrade done \
&& apt-get --purge -y autoremove \
&& echo purge done \
&& apt-get -y install procps \
&& free \
&& apt-get -y -u dist-upgrade \
&& echo dist-upgrade done \
&& apt-get install -y openssh-server rsyslog debian-goodies sudo vim
wget \
&& echo install done \
&& apt-get clean \
&& echo clean done
# disable klogd
RUN sed -i 's/^\(module.load="imklog"\)/#\1/' /etc/rsyslog.conf
# remove the privake key, will be generated by ds-admin ssh-base
# post-conf
# so that it is different for each VM
RUN rm /etc/ssh/ssh_host_*
COPY rc.local /etc/rc.local
RUN chmod 755 /etc/rc.local
# documentation
EXPOSE 22/tcp
CMD /etc/rc.local && tail -f /dev/null
Re: There appears to be a problem with openbox-menu for my installation from "Official Debian GNU/Linux Live 11.6.0 lxde 2022-12-17T11:46"
"Susmita/Rajib" wrote: >A package `openbox-menu` was found. Invoked the command on the >terminal. Output: > >`File $XDG_CONFIG_DIRS/applications.menu doesn't exist. Can't create >menu.` > >Any inputs please? You need an application menu layout. For example you can do: cp /etc/xdg/menus/lxde-applications.menu ~/.config/menus/applications.menu
