Octopi and other no in systemtray #64

Astate commented 2024年02月14日 20:54:55 +01:00 (Migrated from github.com)

Submission type

• Bug report
• Feature Request

Package name & version you are having issues with or have a request for

2024.01 ISO

Used repositories

iso from sourceforge

Expected behaviour

have octopi-notifier in systemtray

Actual behaviour

no icon of octopi in systemtray but the process are running
$ ps -aux | grep octopi-notifier
user 1105 0.0 1.4 1069776 115800 ? Ssl 14:00 0:00 /usr/bin/octopi-notifier
user 2223 0.0 0.0 9088 2388 pts/0 S+ 14:37 0:00 grep --color=tty -d skip octopi-notifier

journalctl -b --no-pager | grep -i sni
fév 14 14:01:20 laptopkaos octopi-notifier[1105]: kf.statusnotifieritem: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP

Steps to reproduce the problem

• I downloaded the ISO a second time and made the checksum
• I completely reinstall 3 times KaOs. it's always same.
  In first test , i install Kaos, remove some things, do update, add software and no Octopi-Notifier
  In the second test , i install Kaos minimal, in first boot, i do update, and after I started Octopi-Notifier
  In last test, i install Kaos minimal, in first boot, before doing anything, I started Octopi-Notifier

System info link created by Octopi > Tools > SysInfo

https://paste.ee/p/gEsEd

#### Submission type - [X] Bug report - [ ] Feature Request #### Package name & version you are having issues with or have a request for > 2024.01 ISO #### Used repositories > iso from sourceforge #### Expected behaviour have octopi-notifier in systemtray #### Actual behaviour no icon of octopi in systemtray but the process are running $ ps -aux | grep octopi-notifier user 1105 0.0 1.4 1069776 115800 ? Ssl 14:00 0:00 /usr/bin/octopi-notifier user 2223 0.0 0.0 9088 2388 pts/0 S+ 14:37 0:00 grep --color=tty -d skip octopi-notifier journalctl -b --no-pager | grep -i sni fév 14 14:01:20 laptopkaos octopi-notifier[1105]: kf.statusnotifieritem: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP #### Steps to reproduce the problem - I downloaded the ISO a second time and made the checksum - I completely reinstall 3 times KaOs. it's always same. In first test , i install Kaos, remove some things, do update, add software and no Octopi-Notifier In the second test , i install Kaos minimal, in first boot, i do update, and after I started Octopi-Notifier In last test, i install Kaos minimal, in first boot, before doing anything, I started Octopi-Notifier #### System info link created by Octopi > Tools > SysInfo https://paste.ee/p/gEsEd

demmm commented 2024年02月14日 21:06:20 +01:00 (Migrated from github.com)

Not an issue for main, but will leave it here for now, this is clearly about applications, so needs to be under Apps:
https://github.com/KaOSx/apps/issues

Does the octopi-notifier show in Live mode? Does it show on first boot into new install?
If so, then what theme is in use after the update and the notifier no longer showing? Is it a matter of no icon for the notifier, so just an empty space in the panel?

Not an issue for main, but will leave it here for now, this is clearly about applications, so needs to be under Apps: https://github.com/KaOSx/apps/issues Does the octopi-notifier show in Live mode? Does it show on first boot into new install? If so, then what theme is in use after the update and the notifier no longer showing? Is it a matter of no icon for the notifier, so just an empty space in the panel?

Astate commented 2024年02月14日 21:22:38 +01:00 (Migrated from github.com)

After the installation I closed Crosedo without modifying anything and I tested the notification problem.
This is not only a problem with Octopi, I had the same problem with the Flatpak client NextCloud application.
it's not only probleme of icons, i dont have empty space.

After the installation I closed Crosedo without modifying anything and I tested the notification problem. This is not only a problem with Octopi, I had the same problem with the Flatpak client NextCloud application. it's not only probleme of icons, i dont have empty space.

demmm commented 2024年02月14日 21:27:04 +01:00 (Migrated from github.com)

Asking one more time, did you have the issue in live mode? Did you have the issue on booting into the new install? So before updating/installing anything. Flatpak is not part of a default install.

Asking one more time, did you have the issue in live mode? Did you have the issue on booting into the new install? So before updating/installing anything. Flatpak is not part of a default install.

Astate commented 2024年02月14日 21:30:01 +01:00 (Migrated from github.com)

Same proplem on live iso -> https://i.imgur.com/BPk34xc.png

Same proplem on live iso -> https://i.imgur.com/BPk34xc.png

Astate commented 2024年02月14日 21:36:21 +01:00 (Migrated from github.com)

Asking one more time, did you have the issue in live mode? yes https://i.imgur.com/BPk34xc.png
Did you have the issue on booting into the new install? So before updating/installing anything. Yes
Flatpak is not part of a default install. it's because i wanted to tell you that it is not only Octopi who is in a problem. I could easily do tests with Octopi via a fresh installation

Asking one more time, did you have the issue in live mode? **yes** https://i.imgur.com/BPk34xc.png Did you have the issue on booting into the new install? So before updating/installing anything. **Yes** Flatpak is not part of a default install. it's because i wanted to tell you that it is not only Octopi who is in a problem. I could easily do tests with Octopi via a fresh installation

demmm commented 2024年02月14日 21:52:44 +01:00 (Migrated from github.com)

What happens if you don't use the the autostart .desktop file, but start the notifier manually?

killall octopi-notifier

/usb/bin/octopi-notifier

What happens if you don't use the the autostart .desktop file, but start the notifier manually? ``` killall octopi-notifier ``` ``` /usb/bin/octopi-notifier ```

Astate commented 2024年02月14日 21:56:57 +01:00 (Migrated from github.com)

it's work when i start it manualy

it's work when i start it manualy

demmm commented 2024年02月14日 21:59:03 +01:00 (Migrated from github.com)

One more killall octopi-notifier, and now start it from the menu.

One more `killall octopi-notifier`, and now start it from the menu.

Astate commented 2024年02月14日 22:02:16 +01:00 (Migrated from github.com)

it's also work.

it's also work.

demmm commented 2024年02月14日 22:03:19 +01:00 (Migrated from github.com)

OK, so the bug is in either autostart or the .desktop file set in autostart

OK, so the bug is in either autostart or the .desktop file set in autostart

Astate commented 2024年02月14日 22:05:11 +01:00 (Migrated from github.com)

It also explains the problem of NextCloud-Client I also added in "Automatic start" in Config Panel

It also explains the problem of NextCloud-Client I also added in "Automatic start" in Config Panel

demmm commented 2024年02月14日 22:10:04 +01:00 (Migrated from github.com)

I can replicate with a new entry in autostart (used stacer), it runs on reboot, but no systemtray entry (it does have an empty space, but not clickable), so it is an autostart issue.
I'll have to check upstream bug reports for this (or you can help), this most probably is not a packaging issue but rather an upstream bug. KaOS can only correct packaging issues for bugs, not correct bugs in code.

I can replicate with a new entry in autostart (used stacer), it runs on reboot, but no systemtray entry (it does have an empty space, but not clickable), so it is an autostart issue. I'll have to check upstream bug reports for this (or you can help), this most probably is not a packaging issue but rather an upstream bug. KaOS can only correct packaging issues for bugs, not correct bugs in code.

Astate commented 2024年02月14日 22:17:18 +01:00 (Migrated from github.com)

thank you for your work !

thank you for your work !

Astate commented 2024年02月19日 01:28:11 +01:00 (Migrated from github.com)

.

.

demmm commented 2024年02月22日 09:39:19 +01:00 (Migrated from github.com)

Looks like it is /was kdeconnect-kde blocking any sni during startup, removing kdeconnect-kde fixes autostart apps.
Removing was needed for the RC2 currently in stable, testing the final Megarelease here now with kdeconnect-kde 24.02.0 has the fix.
Issue will be closed once 24.02 is released next week.

Looks like it is /was kdeconnect-kde blocking any sni during startup, removing kdeconnect-kde fixes autostart apps. Removing was needed for the RC2 currently in stable, testing the final Megarelease here now with kdeconnect-kde 24.02.0 has the fix. Issue will be closed once 24.02 is released next week.

NoSavvy commented 2024年02月25日 13:38:47 +01:00 (Migrated from github.com)

Could this be only on older/slower machines. I have and an older PC and cannot get the problem to arise, no matter how many times I reboot or whatever theme I use. Two separate installations. It fails on both my fast Intel PCs.
Just a thought.

Could this be only on older/slower machines. I have and an older PC and cannot get the problem to arise, no matter how many times I reboot or whatever theme I use. Two separate installations. It fails on both my fast Intel PCs. Just a thought.

demmm commented 2024年02月25日 13:56:10 +01:00 (Migrated from github.com)

Please check again after Wednesday. Then Megarelease final will become available to all users. Here on early testing of that release, issue is gone.

Please check again after Wednesday. Then Megarelease final will become available to all users. Here on early testing of that release, issue is gone.

Astate commented 2024年03月06日 13:44:09 +01:00 (Migrated from github.com)

Yes issue is gone with update !

Yes issue is gone with update !