Botspot / pi-apps

Raspberry Pi App Store for Open Source Projects
GNU General Public License v3.0
1.99k stars 205 forks source link

Ulauncher has huge frames #2249

Closed Rak1ta closed 1 year ago

Rak1ta commented 1 year ago

Confirmations

What happened?

Black borders around the edges of the program window

Description

The problem is described here, but I don't want to break anything. Безымянный

What are your system specs (run the following command in your terminal)?

OS: Raspbian GNU/Linux 10 (buster)
OS architecture: 32-bit
Last updated Pi-Apps on: 01/21/2023
Latest Pi-Apps version: 01/21/2023
Kernel: armv7l 5.10.103-v7l+
Device model: Raspberry Pi 4 Model B Rev 1.2 
Cpu name: Cortex-A72
Ram size: 3.65 GB
Raspberry Pi OS image version: 2021-05-07
Language: en_US.UTF-8

(Recommended) Error log? Terminal output? Debug messages?

pi@raspberrypi:~ $ env GDK_BACKEND=x11 /usr/bin/ulauncher --hide-window
DBus name already taken. Ulauncher is probably backgrounded. Did you mean `ulauncher-toggle`?
theofficialgman commented 1 year ago

oh yeah the default piOS DE on buster (lxde) doesn't come with a compositing window manager. I assume when you run wite this --no-window-shadow there are no issues?

Rak1ta commented 1 year ago

@theofficialgman It got better, but the black frame is not completely gone. Безымянный

theofficialgman commented 1 year ago

yeah thats as good as its going to get thats simply the window border

Rak1ta commented 1 year ago

@theofficialgman When uninstalling, I noticed that the program remains in a running state, but there is no longer any benefit from it. If possible, when deleting, make it close. Thanks!

Botspot commented 1 year ago

I think raspi-config has an option for enabling xcompmgr. That should fix it.

Botspot commented 1 year ago

@theofficialgman When uninstalling, I noticed that the program remains in a running state, but there is no longer any benefit from it. If possible, when deleting, make it close. Thanks!

This is the case for most programs. For only a few apps have I explicitly told an app's uninstall script to kill any running instances of any app. Is there any particular reason why you feel the need for that to happen here, @Rak1ta?

Rak1ta commented 1 year ago

@Botspot The search command still works after removal, but does not work. But there is no problem in the taskbar to close the application. Looks ugly.

Botspot commented 1 year ago

This seems like standard behavior to me. But I understand it would be more intuitive for programs to close on uninstall.

If you would like to change all Pi-Apps uninstall scripts to do this, feel free to make a Pull Request!

Rak1ta commented 1 year ago

@Botspot If you can open a request? Frame issue not resolved.

Botspot commented 1 year ago

@Botspot If you can open a request? Frame issue not resolved.

Did enabling xcompmgr from raspi-config not fix it?

Rak1ta commented 1 year ago

@Botspot The file that raspi-config creates /etc/xdg/autostart/xcompmgr.desktop was already in my possession since I installed Debian. Frames are removed only with the --no-window-shadow command.

Botspot commented 1 year ago

@Rak1ta, I recall there being issues with default Raspbian Buster's xcompmgr config. Many people said that even when enabled in raspi-config, xcompmgr did not seem to do anything.

Here is one of many such reports: https://forums.raspberrypi.com/viewtopic.php?p=1844926&hilit=xcompmgr+buster#p1844961

Try disabling xcompmgr in raspi-config, then run xcompmgr in a terminal without any flags. I predict this will fix transparency for you.

Rak1ta commented 1 year ago

@Botspot If you remove the -aR arguments in /usr/lib/raspi-config/cmstart.sh, then transparency works fine. And in the terminal, when I try to run it, it shows that xcompmgr is already running. But I do not know how it can affect performance (when rebooting, I noticed a gray screen before displaying the desktop). Sorry if you received a lot of notifications. I deleted the post a couple of times. Безымянный

with argument R

pi@raspberrypi:~ $ xcompmgr
error 140: BadRegion request 138 minor 14 serial 12090
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 13863
...

no arguments

pi@raspberrypi:~ $ xcompmgr
Another composite manager is already running (xcompmgr)
-a
      Use automatic server-side compositing. Faster, but no special effects.
   -R
      Run, but do not explicitly register compositing manager with X.

Is customization possible for individual applications?