Topics

Universal Blue•3mo ago

Ptyxis opening on startup

I'm having an issue where ptyxis opens upon logging into KDE every single time without me having changed any setting to make it do so. I can't remember exactly when this started happening but it was a month or two ago. I've tried resetting all dconf settings I could see related to it in dconf editor, I've tried looking through my autostart settings in KDE, I've looked in my bash_profile and other files that could make things start up on login, I've changed my default terminal to konsole, and still I just can't seem to diagnose why this is happening. If anyone could help it would be very much appreciated.

39 Replies

DevilFish303•3mo ago

would you say this started happening after you switched the default terminal to konsole? not implying that is the issue, but would be a good hint to figure out how this could've happened. i switched back to konsole myself with the now hidden ujust command, but never experienced this before. Can you print out the contents of /etc/xdg/autostart? ls -la /etc/xdg/autostart | fpaste

Daph•3mo ago

Thanks for the response. It started before I switched the default terminal if I remember correctly. I do remember switching it to konsole afterwards to see if that would solve the issue but it didn't. Here's the contents of that directory: https://paste.centos.org/view/81de7d56

DevilFish303•3mo ago

nothing stands out, i’ll compare it to my start up files. If you reboot and ptyxis comes up, what is it displaying? just a new terminal session? without closing it, does it have a parent pid? if you look at it from htop can you see what parent process owns it? have you also checked if it’s not being started via a cronjob?

Daph•3mo ago

When I open it it's just a blank terminal session. Not sure if I'm looking at the right thing in htop/btop but it says the parent process is systemd I think. I can't see it in /etc/crontab either

DevilFish303•3mo ago

okay so we need to check what systemd services you have that run on startup systemctl list-unit-files --type=service --state=enabled | fpaste please as for htop, you just enter htop make sure its set to tree view and then it should look something like this

Daph•3mo ago

In the tree view it seems to be under systemd. It launches at /usr/bin/ptyxis --gapplication-service

DevilFish303•3mo ago

okay so its definitely a systemd service, we can find the culprit with a find command

Daph•3mo ago

https://paste.centos.org/view/cefa0094

DevilFish303•3mo ago

these are the ones i do not have:

lactd.service enabled disabled mullvad-daemon.service enabled disabled mullvad-early-boot-blocking.service enabled disabled sunshine-workaround.service enabled disabled

unlikely to be sunshine or lactd, can you do systemctl on mullvad-daemon.service and mullvad-early-boot-block.service and open their unit files to look at the contents?

Daph•3mo ago

emi@bazzite:/var/home/emi$ cat /usr/lib/systemd/system/mullvad-daemon.service 
# Systemd service unit file for the Mullvad VPN daemon
# testing if new changes are added

[Unit]
Description=Mullvad VPN daemon
Before=network-online.target
After=mullvad-early-boot-blocking.service NetworkManager.service systemd-resolved.service

StartLimitBurst=5
StartLimitIntervalSec=20
RequiresMountsFor=/opt/Mullvad\x20VPN/resources/

[Service]
Restart=always
RestartSec=1
ExecStart=/usr/bin/mullvad-daemon -v --disable-stdout-timestamps
Environment="MULLVAD_RESOURCE_DIR=/opt/Mullvad VPN/resources/"

[Install]
WantedBy=multi-user.target

emi@bazzite:/var/home/emi$ cat /usr/lib/systemd/system/mullvad-daemon.service 
# Systemd service unit file for the Mullvad VPN daemon
# testing if new changes are added

[Unit]
Description=Mullvad VPN daemon
Before=network-online.target
After=mullvad-early-boot-blocking.service NetworkManager.service systemd-resolved.service

StartLimitBurst=5
StartLimitIntervalSec=20
RequiresMountsFor=/opt/Mullvad\x20VPN/resources/

[Service]
Restart=always
RestartSec=1
ExecStart=/usr/bin/mullvad-daemon -v --disable-stdout-timestamps
Environment="MULLVAD_RESOURCE_DIR=/opt/Mullvad VPN/resources/"

[Install]
WantedBy=multi-user.target

emi@bazzite:/var/home/emi$ cat /usr/lib/systemd/system/mullvad-early-boot-blocking.service 
# Systemd service unit file to block all traffic during early boot.
# This is required since almost no distributions use a `network-pre.target`,
# which implies it's difficult to ensure that the daemon will start and block
# traffic before any network configuration will be applied.
#
[Unit]
Description=Mullvad early boot network blocker
DefaultDependencies=no
Before=basic.target mullvad-daemon.service

[Service]
Type=oneshot
ExecStart=/usr/bin/mullvad-daemon --initialize-early-boot-firewall

[Install]
WantedBy=mullvad-daemon.service

emi@bazzite:/var/home/emi$ cat /usr/lib/systemd/system/mullvad-early-boot-blocking.service 
# Systemd service unit file to block all traffic during early boot.
# This is required since almost no distributions use a `network-pre.target`,
# which implies it's difficult to ensure that the daemon will start and block
# traffic before any network configuration will be applied.
#
[Unit]
Description=Mullvad early boot network blocker
DefaultDependencies=no
Before=basic.target mullvad-daemon.service

[Service]
Type=oneshot
ExecStart=/usr/bin/mullvad-daemon --initialize-early-boot-firewall

[Install]
WantedBy=mullvad-daemon.service

DevilFish303•3mo ago

okay try this: sudo find / -type f -exec grep -l '/usr/bin/ptyxis --gapplication-service' {} +

Daph•3mo ago

seems to be stuck

emi@bazzite:/var/home/emi$ sudo find / -type f -exec grep -l '/usr/bin/ptyxis --gapplication-service' {} +
grep: /proc/sys/fs/binfmt_misc/register: Invalid argument
grep: /proc/sys/net/ipv4/route/flush: Permission denied
grep: /proc/sys/net/ipv6/conf/all/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/default/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/enp14s0/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/lo/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/wg0-mullvad/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/wlp15s0/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/route/flush: Permission denied
grep: /proc/sys/vm/compact_memory: Permission denied
grep: /proc/sys/vm/drop_caches: Permission denied

emi@bazzite:/var/home/emi$ sudo find / -type f -exec grep -l '/usr/bin/ptyxis --gapplication-service' {} +
grep: /proc/sys/fs/binfmt_misc/register: Invalid argument
grep: /proc/sys/net/ipv4/route/flush: Permission denied
grep: /proc/sys/net/ipv6/conf/all/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/default/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/enp14s0/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/lo/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/wg0-mullvad/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/conf/wlp15s0/stable_secret: Input/output error
grep: /proc/sys/net/ipv6/route/flush: Permission denied
grep: /proc/sys/vm/compact_memory: Permission denied
grep: /proc/sys/vm/drop_caches: Permission denied

DevilFish303•3mo ago

it takes a while that command is searching everywhere

Daph•3mo ago

alright thanks for the help so far btw

DevilFish303•3mo ago

this might be better: sudo find / -type f -exec grep -Hn 'ptyxis' {} + there's a way to exclude /proc and maybe /sys, but i don't remember how atm 😅

Daph•3mo ago

that's alright I don't mind waiting

DevilFish303•3mo ago

finally had a chance to check this list, it looks identical to mine

Daph•3mo ago

hopefully that's a good thing those find commands are still running

DevilFish303•3mo ago

if its taking too long for comfort you can try executing them like: sudo find /etc -type f -exec grep -Hn 'ptyxis' {} + sudo find /usr -type f -exec grep -Hn 'ptyxis' {} + those would be the two places where i would expect the systemd service that is running on boot up to live oh! i thought of something else systemctl --user list-unit-files --type=service --state=enabled your user specific systemd services that are running on startup

Daph•3mo ago

here's the output of that:

UNIT FILE                      STATE   PRESET  
bazzite-user-setup.service     enabled disabled
dbus-broker.service            enabled enabled 
obex.service                   enabled enabled 
systemd-tmpfiles-setup.service enabled enabled 
wireplumber.service            enabled enabled 

5 unit files listed.

UNIT FILE                      STATE   PRESET  
bazzite-user-setup.service     enabled disabled
dbus-broker.service            enabled enabled 
obex.service                   enabled enabled 
systemd-tmpfiles-setup.service enabled enabled 
wireplumber.service            enabled enabled 

5 unit files listed.

DevilFish303•3mo ago

yea they look exactly like mine T_T nothing in ~/.config/autostart? and here ~/.config/plasma-workspace/env or here: ~/.config/plasma-workspace/shutdown

Daph•3mo ago

i have these in ~/.config/autostart mullvad-vpn.desktop ublue-firstboot.desktop but none in either of the others

DevilFish303•3mo ago

what are the contents of mullvad-vpn? im starting to get suspicious it has something to do with that, that seems to be the discrepancy between your setup and mine

Daph•3mo ago

[Desktop Entry]
Categories=Network;
Comment=Mullvad VPN client
Exec="/opt/Mullvad VPN/mullvad-vpn" %U
Icon=mullvad-vpn
Name=Mullvad VPN
StartupWMClass=Mullvad VPN
Terminal=false
Type=Application

[Desktop Entry]
Categories=Network;
Comment=Mullvad VPN client
Exec="/opt/Mullvad VPN/mullvad-vpn" %U
Icon=mullvad-vpn
Name=Mullvad VPN
StartupWMClass=Mullvad VPN
Terminal=false
Type=Application

it could be this, although i have another computer with mullvad autostarting and ptyxis doesnt' show up on there

DevilFish303•3mo ago

if you were to temporarily remove it, just copy it to you home directory, and maybe disable the systemd services for mullvad, and see if that fixes it

Daph•3mo ago

i'll try that Just rebooted and it still opened

DevilFish303•3mo ago

this was after disabling all mullvad systemd services? what about turning off lact and sunshine systemd services, that was also the discrepancy i found with systemd startup services between yours and mine, but thought they were fine

Daph•3mo ago

I can try that it was after disabling all mullvad stuff

DevilFish303•3mo ago

btw i found this after digging through my PC, so i changed the default terminal for my user account, but for root, i think it may be using this etc/kdeglobals, never seen this file before

No description

DevilFish303•3mo ago

i was thinking if it is a systemd service, most likely its a process running as root, and its reading the TerminalApplication from somewhere global, and found this

Daph•3mo ago

I'll check that I just rebooted after disabling all those services and it still opened My result looks the same as yours

DevilFish303•3mo ago

a crap okay im a bit out of ideas, the only thing i can think of at this point is try making a throw away user account, login as that and see if it still opens, if it does not, it may be an issue with your existing user account, but i am stumped at this point 😦

Daph•3mo ago

i'll try that. Thanks for your help, I'll keep researching doesn't happen on a second user account

DevilFish303•3mo ago

okay silver lining! but now to find out why, one idea is you could replace the dot files from this second account over on your primary account (making sure you back them up first), sudo chown -R them to your old account and then log back in to your old account and see if that fixes it this is what i usually resort to when i want to take advantage of KDE updates without having to reimage, it will reset your desktop customizations and other user settings, but other than that it should be okay to proceed

Daph•3mo ago

i'll definitely keep that in mind, but i think I'll do a bit more research first because I don't want to reset everything unless I can't find another solution. I'd just rather not have to set up everything from scratch again if I can avoid it

DevilFish303•3mo ago

understandable! it’s a total drag resetting, i’ll chime in again if i think of anything

wolfyreload•3mo ago

Do you have the Desktop Session >> Session Restore >> "When Session was manually saved" by any chance? That has messed me around a lot with KDE in the past and I kept having firefox starting with the laptop.... was super annoying...

No description

Daph•3mo ago

Thanks for the suggestion. It wasn't set to that, it was "on last logout". But setting it to "start with an empty session" fixed it!!! Thanks so much!

wolfyreload•3mo ago

Glad that helped

Universal Blue Join

9KMembers

View on Discord

Want results from more Discord servers?

Add your server