![]() ![]() Signal time=1689006452.780622 sender= -> destination=:1.22 serial=4 path=/org/freedesktop/DBus interface= member=NameLost Signal time=1689006452.780566 sender= -> destination=:1.22 serial=2 path=/org/freedesktop/DBus interface= member=NameAcquired If the first one prints nothing (showing the variable is not set) then try: Jul 10 09:53:56 leviathan polkit-agent-helper-1: pam_systemd_home(polkit-1:auth): systemd-homed is not availabl> Jul 10 09:51:22 leviathan login: LOGIN ON tty1 BY nikin Jul 10 09:51:22 leviathan systemd: Started Session 1 of User nikin. ├─1012 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 7 -isForBrowser -prefsLen 3> ├─ 918 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 6 -isForBrowser -prefsLen 3> ├─ 914 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 5 -isForBrowser -prefsLen 3> ![]() ├─ 911 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 4 -isForBrowser -prefsLen 3> ├─ 894 /usr/lib/firefox-developer-edition/firefox -contentproc -parentBuildID 20230707083005 -sandb> ├─ 830 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 3 -isForBrowser -prefsLen 3> ![]() ├─ 713 /usr/lib/firefox-developer-edition/firefox -contentproc -childID 1 -isForBrowser -prefsLen 2> ├─ 686 /usr/lib/firefox-developer-edition/firefox -contentproc -parentBuildID 20230707083005 -prefs> ├─ 574 /usr/lib/firefox-developer-edition/firefox ├─ 548 sh /home/nikin/.config/X11/xinitrc ├─ 527 /usr/lib/Xorg -nolisten tcp :0 vt1 -keeptty -auth /tmp/serverauth.9CXyVi47mO ├─ 526 xinit /home/nikin/.config/X11/xinitrc - /etc/X11/xinit/xserverrc :0 vt1 -keeptty -auth /tmp> ├─ 501 /bin/sh /usr/bin/startx /home/nikin/.config/X11/xinitrc Moreover, I couldn't find anything on the comments section of AUR. I found this post on the forums but it has been five years so I was not sure how much of it was relevant. I read on Reddit that this might be problem because of startx and I do use startx and use dwm. Jul 09 21:40:02 leviathan systemd: Started TeamViewer remote control daemon. Jul 09 21:40:02 leviathan systemd: rvice: Can't open PID file /run/teamviewerd.pid (yet?) after start: No such file or directory Jul 09 21:40:02 leviathan systemd: Starting TeamViewer remote control daemon. └─15945 /opt/teamviewer/tv_bin/teamviewerd -d Process: 15943 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)ĬGroup: /system.slice/rvice Loaded: loaded (/usr/lib/systemd/system/rvice disabled preset: disabled)Īctive: active (running) since Sun 21:40:02 +0545 7min ago rvice - TeamViewer remote control daemon.That being said, this is a lot better for my usage than having the daemon running all the time, every day, since I only use TeamViewer to occasionally provide tech help for family and friends. I haven't been able to figure out how to kill the TeamViewer daemon upon exiting the TeamViewer application. The only potential downside to this script is that the TeamViewer daemon remains running after the TeamViewer application is stopped. opt/teamviewer8/tv_bin/script/teamviewerįor standard Ubuntu users (also GNOME, XFCE or LXDE), replace the "kdesudo" line above with the following: Kdesudo -comment "Please enter your password to start the TeamViewer daemon:" -c "teamviewer -daemon start" I don't know how you do this in Ubuntu's Unity interface, so of someone wants to provide this step, that would be helpful. I do this in KDE by right-clicking the K menu and selecting "Edit Applications.", then replacing the command for "TeamViewer 8" with the path to the script I created. Then I just point the TeamViewer launch icon to the new script I created. ![]() Since I don't wish to have the TeamViewer daemon running all the time, I made a script that starts the daemon when I launch the TeamViewer application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |