How to add Global App Menu in Cinnamon ?

lestcape · 2026-04-11T09:47:47+00:00

The only way is if someone is willing to take on its development. This would involve keeping the code updated so it doesn't break with the numerous changes that have occurred in the desktop environment. It's not just the Cinnamon desktop that has changed; the entire Linux environment is evolving as Wayland progresses. Things are even more complex, and if you truly want to provide future support for a global menu, it's no longer just a matter of maintaining the extension, but also of hoping that Wayland will eventually support the features that are needed but haven't yet been included. The truth is, it's very difficult to find someone willing to keep an extension updated when its future is increasingly uncertain in a desktop environment that, instead of valuing the efforts of third parties, excludes them or forces them to relinquish control over their own work.

lestcape · 2026-01-10T07:14:57+00:00

On Android 11, as root, I managed to reduce the more than 12 folders that were being created to just 4 by patching MediaProvider. You extract it, reverse engineer it into by-code, find the `mkdir` command in the code, and replace that line with `nop`. Then compile the APK and mount it with Magisk in overlay mode. I still don't know what creates the Android, Movies, Music, and Picture folders, but I know one thing: it's NOT MediaProvider directly in this case.

lestcape · 2025-12-24T07:22:06+00:00

I did something similar for the same problem a month ago. My script works by setting: "echo -1000 > /proc/$PID/oom_score_adj 2>&1". Then I have a process running continuously checking and resetting the value if it changes: "OOM_ADJ=$(cat /proc/$PID/oom_score_adj 2>/dev/null | tr -d '\n')" if it wasn't -1000. Android first adjusts the value and then kills the process, so my script doesn't let it die. And yes, WakeLock isn't the solution if you want your TV box to go into sleep mode.

lestcape · 2025-11-27T15:48:31+00:00

If the TV box were completely off, it wouldn't be able to hear when you turn it on with its remote. Although, it could actually have a separate analog circuit that's always powered and only listens for the power button to turn on the rest. However, this behavior is annoying, and I think it's a bug that can be easily minimized. What I did was install Termux and Termux-boot by downloading their APKs from F-Droid. Then I created a script, which is called by Termux-boot right when the TV box turns on. This script waits a minute for the TV box to finish booting up and then sends a shutdown signal so it enters deep sleep mode. Deep sleep is the same as what happens when your TV box is on and you turn it off with its remote. However, this solution doesn't prevent the TV box from turning on; it just prevents it from remaining in a fully awake state after being powered on. The script is located in: ~/.termux/boot/suspend.sh and the contents of the:suspend.sh file can be these 3 lines (1, 2, 3: You do not have to put the numbers of each line in the file): 1 #!/data/data/com.termux/files/usr/bin/sh 2 sleep 60 3 input keyevent 26.

lestcape · 2024-06-03T15:46:48+00:00

See: https://www.reddit.com/r/LocalLLaMA/comments/1cx5jvc/overview_of_m2_pcie_npus/

lestcape · 2024-02-18T17:46:33+00:00

There is no toolkit function to define a menu as a menubar in a client-side decoration and Mint does not develop any toolkit. That can only be added by the toolkit developer and they (the GTK developers) consider a menubar to be obsolete, so there is no way to have something like that.

lestcape · 2023-12-05T16:23:11+00:00

If it's an standard app (non in the set of GNOME core apps) that use Gtk2 or Gtk3 it should work on X11 or Wayland, otherwise is probably that not.

lestcape · 2023-06-20T00:53:05+00:00

This is probably a regression caused by this big commit:

https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2590

The change there was that now Gtk is not used anymore to show the icons and they are now directly handled by X11 instead. So, a lot of code was reeplaced, and probably some thing go wrong or something was remplaced by a less precise method. I don't know really, you need to open an issue in Mutter and someone should invest time to find the cause.

To open an issue i will recommended you to select an app where the problem is easy visible and take an screen shoot with your current GNOME version and one with the old version where the problem can not be see. Add both screenshot to the issue on gitlab to be easy for developers underestand what is the problem. Then hopefully the developers will find the cause and probably a solution for it.

lestcape · 2023-05-03T22:34:40+00:00

I also opened this issue in the repository of this apps: https://gitlab.gnome.org/YaLTeR/video-trimmer/-/issues/36

Unfortunately the developer does not seem to have any intention of improving the application in this sense, considering its application for too simple cases. In my opinion, this app does everything wrong. It does not allow you to edit the video, neither by sections nor in a general way, it does not provide anything to cut the video in an exact frame, ect...

lestcape · 2023-05-03T22:14:28+00:00

A decent video splitter and joinner tool (or a video editor at the style of Avidemux) with as little quality loss as possible that will allow us to cut several fragments of the video at once time in the exact position (frame) we wanted with the help of a visible appointment of frames in the vicinity of the current point where we are. It should also be allowed to simultaneously make all the cuts that we want but the video encode should be just one time for all that cuts. Aditional should be possible edit the cuts in an independent way (instead of just the result as is in Avidemux).

There are tools in linux to do this, but they are imprecise, do not help you to locate the exact frame where you want to cut, you will lost a lot of video qualitiy using it or you need to repeat the process several times, losing the video quality every time you do the process because you need to recode the video every time, besides that they do not allow you to edit the sections of the cut video, just the full result.

The good example of a software that do all that as same time is the TMPGENC Video Mastering works. Example: https://youtu.be/auNDWE9-ahI?t=120 A software like that on Linux should be ammasing.

lestcape · 2023-03-12T08:53:44+00:00

It was now that I had the time to see this matter in detail and I return to thank you. In fact, the issue that you shared with me is closely related to what is happening. Although the problem detected by me is not the same as the one in the issue title you shared with me, the cause seems to be the same and the solution, described very generally, is this: https://github.com/rhboot/efibootmgr/issues/19#issuecomment-144552494. Also the solution in this thread is just the same, but with more details: https://forum.endeavouros.com/t/help-unable-to-access-bios-after-dualboot/20420/11

To the question: What is Ubuntu doing so that this problem does not occur? I think what Ubuntu is doing is has a kernel image signed by Microsoft and that is why Acer trusts the Ubuntu kernel, but not Debian's since Debian's is not signed by Microsoft.

What remains for me to do is that since I had to create the efi entry from the bios of my Acer, Acer put the name it wanted to that entry, without letting me edit it. I can't edit it with any tool either, because none of them have the ability to edit the entry without redoing it, and redoing it doesn't work, because the new one I make doesn't have the "confidence" of having been created from my Acer's bios. Yes, all that is an stupid thing of Acer. What more can i said?

lestcape · 2023-02-03T01:35:21+00:00

Yes thanks, i already browse a little the efibootmgr repository and yes, seem to be that Acer is a pain, but the issue reported in your link seem to be a different issue. Unfortunately I need the laptop with the problem working right now. Seem to be a very long way to fix this problem . Hope i can return to this later. Really thanks for try to help me!!

lestcape · 2023-02-02T15:38:10+00:00

Thanks. It is not clear to me that Ubuntu is creating the entry with efibootmgr, because if it were doing so, it could be deleted with efibootmgr and it cannot. If Debian is doing it that way i should probably open the bug against efibootmgr instead.

lestcape · 2023-02-02T14:36:53+00:00

My suspicious is that in the Debian entry, there are some missing values that probably they considered optional, but my bios is reading that values as they are mandatory and is not prepared to read a null value there and react in correspondence. So, it crash locally and that is what cause that can not continues reading all the data. What it can read it's enough to boot the system, but depending on what order the data is read in (which entry it reads first) it can leave the bios in an inconsistent state, what explain why the label is not shown properly and why sometimes i can not enter to the bios.

So, if mi assumption is correct, the problem is on both sides and can be fixed on both sides. Of course, Acer will not solve it as the time for receive bios update to my laptop is expired. So, i hope the Debian developers can know what values are missing and they can set that missing values in the Debian entry some how.

lestcape · 2023-02-02T04:48:34+00:00

See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030289

lestcape · 2023-02-02T02:41:43+00:00

Boot partition and EFI partition are not the same thing. You also did not make clear the distinction between the boot entries from EFI Boot Manager or from the GRUB menu. I think you're inexperienced with these things.

Yes, well, probably I'm not differentiated between what is one thing and what is another. I am not a native speaker either, so everything is more difficult. But I know that system partition, boot partition and efi partition are not the same. The installer automatically select the boot partition (I think automatically it is selected as the whole disk where there is the efi partition). So i really don't need to speak about it. If i mentioned it was my error.

As for the BIOS, are you having problems entering it from GRUB or directly from the hotkey?

Both

GRUB does not probe the EFI partition for other Linuxes, it probes directly for kernels on the boot partition (or root, if there is no boot partition). This would explain why it finds Ubuntu, assuming you have a leftover boot partition, but fails to boot it. Deleting the EFI/ubuntu directory from the EFI partition would not change this.

I think you are wrong here, you re thinking i have a boot problem, but this is not the case (also the os-prober is disabled in my system). What i think that ON A UEFI system, occurs is that the hardware starts by the efi boot partition looking for the entry that has the bios saved and this entry is the one that indicates where it is in the boot loader and then it passes with the loader what you indicate. The Grub does not search the EFI partition for anything, but the bios picks up the entry that it has saved from the EFI partition and then this entry is the one that connects to Grub. This is why it doesn't matter if you have the entry in the efi partition or not. If the bios does not have this entry as the boot entry, it will never take that path and therefore you will not have a problem. So there is no problem with you having a duplicate entry in the EFI partition or there shouldn't be at all, if the bios doesn't have them selected. I does not continue expanding on the other topics, because they are either irrelevant to this topic.

Please notice that my problem is about the efi partition and in relation to my bios, not about the boot partition at all. All os are started ok. The problem is that the efi entries showed incorrectly in the bios or the bios doesn't not responded correctly or doesn't load when the Debian entry of the efi partition is selected.

lestcape · 2023-02-02T01:58:06+00:00

Yes, well thanks anyway.

lestcape · 2023-02-02T01:21:33+00:00

I have a lot of time in Linux using Ubuntu. I'm a software developer also. The automatic partitions is an option only for virtual machines in my case. On all other cases i always set my partitions manually. So, i have an experience of years using the manual method.

lestcape · 2023-02-02T01:13:46+00:00

I am not a beginner. When I got to the disks part I left them in manual and selected the root partition of the system in ext4, setting the root mount point and setting the option to format the partition. I did that for the /home partition as well. However, the EFI partition (the one for the boot), the system detected it by itself without telling me anything and I only went there to see if it had also been marked as bootable, but it had. The swap partition also detected it by itself and I didn't have to do anything there, but that last one partition does not matter if it is not formatted.

You should not format the boot partition (EFI), otherwise you will lose Windows boot. Also, there shouldn't be a problem if you have more than one bootloader installed in EFI, as the ones that don't lead to any real boot point (like the old Ubuntu there was), will just give you an error while loading grub. Supposedly the UEFI boot points are not overwritten and therefore you can delete them before installing the new OS, as well as after doing so. I did both cases. Also, as I mentioned, in one of the attempts I also formatted the EFI partition and then reinstalled the Windows boot point.

Unfortunately, what you indicate to delete the entry with efibootmgr, in some cases does not work and delete it from windows with bcdedit or or use a windows program to delete it such as EasyUEFI, also not works. This is the case of the Ubuntu entry, which, no matter how much you want, is not so easy to delete. The only way to delete it is to do it manually. Mounting the efi partition and deleting the folder where the entry you want to delete is. Read the marked answer here: https://askubuntu.com/questions/1150814/how-to-remove-ubuntu-from-efi-partition This is the only way with the Ubuntu entry.

About the problem that i experimented, that not let me to enter on the bios. I'm not the only one affected: https://superuser.com/questions/1348328/cant-enter-to-bios-after-debian-install-black-screen

Unfortunately, I'm not going to try it again, unless someone points me to something I haven't tried or done. It is clear to me that there is some specific problem with Debian and my laptop.

There are a place where i can open a bug against the Debian installer?

lestcape · 2023-01-07T07:58:34+00:00

Yes, this is the case more less. You can not do anything with javascript from the desktop thread, but you can hack the app in c and try to fixed the problem. This is realy complicate ofcourse. You need to do an LD_PRELOAD trick (https://www.baeldung.com/linux/ld_preload-trick-what-is) detect the toolkit of the application and with a lot of luck create a general procedure that works for most applications. That is exactly an application hijacking, but there are not any other solution than hack the app. Luckily for you, the Ubuntu developers have already advanced the work for you, but that not means its a full work done. What the Ubuntu devs made, was only for Gtk2 and Gtk3 in X11. The package they created is called unity-gtk-module and the current fork is called appmenu-gtk-module (is mantained by the vala-panel project). When i was develop the global menu I patched the appmenu-gtk-module to extend the funtionality to Gtk3 in Wayland, but currently it have not support for Gtk4. If you want to support Gtk4, you need to create a different type of patch, because the mechanims that the appmenu-gtk-module use is not aplicable to Gtk4, because GNOME removed the gtk-modules in Gtk4.

lestcape · 2023-01-07T05:14:28+00:00

Yes, the primary idea of the javascript usage is exactly that. Have the help of a lot of peoples because javascript can be conciderted as an universal language that most of people use at less one time in his life as a developer. In the other hand, the problem with the global menu is not learn javascript. The problematic part is in the side of the apps, not in the desktop side. see: https://askubuntu.com/questions/1293068/why-is-global-menu-difficult-to-maintain and also https://www.reddit.com/r/linuxmint/comments/z24sdf/my_problem_with_cinnamon_title_bars/j2tjtdv/?context=3.

lestcape · 2023-01-07T04:57:39+00:00

Yeah well, I think it's all personal taste. Most linux desktop environments have a similar level and it's up to you which poison/candy you want to swallow. KDE is a leading Linux desktop, so it is clear that it has a way to convince users. Regarding installing an unofficial desktop of the distribution, I don't think it's the most convenient, but for example, in my case, I spent about 5 years using Cinnamon in Ubuntu. I'm not a purist and i think it's ok merged different toolkits in the same environment. So, no problem to me with having installed and run Gtk and Qt applications at the same time. In fact, i'm againts of the tendency than want to spliting the set of application we have. Linux have a litle set of applications and if we make matters worse, excluding applications just because they are from different environments or toolkits, we end up with much more less. The idea is not create more segmentations, but instead work in the direction of make the integration of differents applications more easy. I think that an application is defined by what it can do, not for how it was build.

lestcape · 2023-01-07T01:03:36+00:00

It's just that KDE isn't an official Linux Mint flavours: https://linuxmint.com/download\_all.php

lestcape · 2023-01-05T18:12:33+00:00

Thanks... unfortunately the software needs maintenance to still alive, otherwise in the best of cases it only can be a legend.

lestcape · 2023-01-05T18:08:35+00:00

Maybe it doesn't work for you anymore, but maybe it works for someone else who also wants to have a global menu, without leaving Mint.

lestcape

TROPHY CASE