You are not logged in.

#1 2017-07-03 01:49:58

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

[SOLVED] Cant start Plasma after update

I Just restarted my computer after a daily update and now on login it just shows a box on top left with ”Could not sync environment to dbus”.

I use plasma and sddm and can use other ttys.


systemctl --state=failed tells me the unit user@1000.service failed

systemctl status user@1000.service:
● user@1000.service - User Manager for UID 1000
   Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled)
   Active: failed (Result: protocol) since Sun 2017-07-02 22:32:39 -03; 36min ago
  Process: 1124 ExecStart=/usr/lib/systemd/systemd --user (code=dumped, signal=ABRT)
Main PID: 1124 (code=dumped, signal=ABRT)

jul 02 22:32:39 note systemd[1]: Starting User Manager for UID 1000...
jul 02 22:32:39 note systemd[1124]: pam_unix(systemd-user:session): session opened for user ricardo by (uid=0)
jul 02 22:32:39 note systemd[1124]: Assertion 'startswith(line, "env=")' failed at src/basic/env-util.c:797, function deserialize_env
jul 02 22:32:39 note systemd[1]: Failed to start User Manager for UID 1000.
jul 02 22:32:39 note systemd[1]: user@1000.service: Unit entered failed state.
jul 02 22:32:39 note systemd[1]: user@1000.service: Failed with result 'protocol'.


Deleting ~/.config didnt solve.

Reinstalling all packages either.

Now I installed lxqt, it succeed to logon, but is all weird and bugged and when I launch lxqt-config-session it shows:
"QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ricardo'
LXQt::SingleApplication::SingleApplication(int&, char**, LXQt::SingleApplication::StartOptions) "Can't connect to the D-Bus session bus\nMake sure the D-Bus daemon is running"
QObject::connect: No such signal QDBusAbstractInterface::moduleStateChanged(QString,bool)"

Last edited by ricardoscar (2017-07-06 20:31:43)

Offline

#2 2017-07-03 01:55:55

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Cant start Plasma after update

Please don't post screenshots of text, paste the actual text.

Remove SDDM and Plasma from the equation and just get a working X session.



Moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2017-07-03 02:06:28

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

Ok, i got the X session working through sddm and lxqt.

When i try Plasma(Wayland) it just go back to sddm login screen.
Plasma with X give the problem describe on the original post.

on LXQT, when I try to open dolphin it shows:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ricardo'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ricardo'
"Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)"

when i try to poweroff or restart throgh lxpanel, it doesnt open the dialog box.

Im trying to find some more problem to find the root of the problem, the screenshot photo was taken because i wasnt able to copy and paste the terminal at that time.

Offline

#4 2017-07-03 02:11:55

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Cant start Plasma after update

Read your journal for errors in Wayland. And you can paste from the TTY with a paste client: https://wiki.archlinux.org/index.php/Li … in_clients


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#5 2017-07-03 02:36:08

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

Ok, i tried wayland again and it logged in, with lots of weird things, here is the journalctl from a logoff and a login from and to wayland: https://ptpb.pw/o0pc

Now ill try to make a journal with the plasma with X.

Offline

#6 2017-07-03 02:42:39

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

The systemd log from when I log in to plasma 5 with X:

jul 02 23:37:16 note sddm-greeter[2977]: Reading from "/usr/share/xsessions/plasma.desktop"
jul 02 23:37:16 note sddm[1933]: Message received from greeter: Login
jul 02 23:37:16 note sddm[1933]: Reading from "/usr/share/xsessions/plasma.desktop"
jul 02 23:37:16 note sddm[1933]: Reading from "/usr/share/xsessions/plasma.desktop"
jul 02 23:37:16 note sddm[1933]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
jul 02 23:37:16 note sddm-helper[2985]: [PAM] Starting...
jul 02 23:37:16 note sddm-helper[2985]: [PAM] Authenticating...
jul 02 23:37:16 note sddm-helper[2985]: [PAM] Preparing to converse...
jul 02 23:37:16 note sddm-helper[2985]: [PAM] Conversation with 1 messages
jul 02 23:37:16 note sddm-helper[2985]: [PAM] returning.
jul 02 23:37:16 note sddm[1933]: Authenticated successfully
jul 02 23:37:16 note sddm-greeter[2977]: Message received from daemon: LoginSucceeded
jul 02 23:37:16 note sddm-helper[2985]: pam_unix(sddm:session): session opened for user ricardo by (uid=0)
jul 02 23:37:16 note systemd[1]: Created slice User Slice of ricardo.
jul 02 23:37:16 note systemd[1]: Starting User Manager for UID 1000...
jul 02 23:37:16 note systemd-logind[678]: New session c13 of user ricardo.
jul 02 23:37:16 note systemd[2986]: pam_unix(systemd-user:session): session opened for user ricardo by (uid=0)
jul 02 23:37:16 note sddm-helper[2969]: pam_unix(sddm-greeter:session): session closed for user sddm
jul 02 23:37:16 note sddm-helper[2969]: [PAM] Closing session
jul 02 23:37:16 note systemd[1]: Started Session c13 of user ricardo.
jul 02 23:37:16 note sddm-helper[2969]: [PAM] Ended.
jul 02 23:37:16 note sddm[1933]: Auth: sddm-helper exited successfully
jul 02 23:37:16 note sddm[1933]: Greeter stopped.
jul 02 23:37:16 note systemd-logind[678]: Removed session c12.
jul 02 23:37:16 note systemd[1]: Removed slice User Slice of sddm.
jul 02 23:37:16 note systemd[2986]: Assertion 'startswith(line, "env=")' failed at src/basic/env-util.c:797, function deserialize_environment(). Aborting.
jul 02 23:37:16 note systemd[1]: Started Process Core Dump (PID 2990/UID 0).
jul 02 23:37:16 note systemd[2987]: pam_unix(systemd-user:session): session closed for user ricardo
jul 02 23:37:16 note systemd[1]: Failed to start User Manager for UID 1000.
jul 02 23:37:16 note systemd[1]: user@1000.service: Unit entered failed state.
jul 02 23:37:16 note systemd[1]: user@1000.service: Failed with result 'protocol'.
jul 02 23:37:16 note sddm-helper[2985]: pam_systemd(sddm:session): Failed to create session: Start job for unit user@1000.service failed with 'failed'
jul 02 23:37:16 note sddm-helper[2985]: Starting: "/usr/share/sddm/scripts/Xsession /usr/bin/startkde"
jul 02 23:37:16 note sddm-helper[2992]: Adding cookie to "/home/ricardo/.Xauthority"
jul 02 23:37:16 note sddm[1933]: Session started
jul 02 23:37:16 note systemd-coredump[2991]: Process 2986 (systemd) of user 1000 dumped core.
                                             
                                             Stack trace of thread 2986:
                                             #0  0x00007f22e52ec670 raise (libc.so.6)
                                             #1  0x00007f22e52edd00 abort (libc.so.6)
                                             #2  0x00007f22e6435962 log_assert_failed (libsystemd-shared-233.so)
                                             #3  0x00007f22e644094f deserialize_environment (libsystemd-shared-233.so)
                                             #4  0x00007f22e64409e8 n/a (libsystemd-shared-233.so)
                                             #5  0x00007f22e643e5ac execute_directories (libsystemd-shared-233.so)
                                             #6  0x000055bd8d94ec8b n/a (systemd)
                                             #7  0x000055bd8d94ca89 n/a (systemd)
                                             #8  0x00007f22e52d943a __libc_start_main (libc.so.6)
                                             #9  0x000055bd8d94df9a n/a (systemd)
jul 02 23:37:16 note ksplashqml[3012]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ricardo'

After this it just shows the dialog with ”Could not sync environment to dbus” and a useless "Okay" button.


And the LXQt login:

jul 02 23:44:02 note systemd[1]: Stopped Simple Desktop Display Manager.
jul 02 23:44:02 note systemd[1]: Started Simple Desktop Display Manager.
jul 02 23:44:02 note sddm[3377]: Initializing...
jul 02 23:44:02 note sddm[3377]: Starting...
jul 02 23:44:02 note sddm[3377]: Adding new display on vt 1 ...
jul 02 23:44:02 note sddm[3377]: Display server starting...
jul 02 23:44:02 note sddm[3377]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{501bc2c0-0f5a-4c8a-8a9c-20f24eae6cc5} -backgro
jul 02 23:44:03 note sddm[3377]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
jul 02 23:44:03 note sddm[3377]: Display server started.
jul 02 23:44:03 note sddm[3377]: Socket server starting...
jul 02 23:44:03 note sddm[3377]: Socket server started.
jul 02 23:44:03 note sddm[3377]: Greeter starting...
jul 02 23:44:03 note sddm[3377]: Adding cookie to "/var/run/sddm/{501bc2c0-0f5a-4c8a-8a9c-20f24eae6cc5}"
jul 02 23:44:03 note sddm[3377]: Display server started.
jul 02 23:44:03 note sddm[3377]: Socket server starting...
jul 02 23:44:03 note sddm[3377]: Socket server started.
jul 02 23:44:03 note sddm[3377]: Greeter starting...
jul 02 23:44:03 note sddm[3377]: Adding cookie to "/var/run/sddm/{501bc2c0-0f5a-4c8a-8a9c-20f24eae6cc5}"
jul 02 23:44:03 note sddm-helper[3385]: [PAM] Starting...
jul 02 23:44:03 note sddm-helper[3385]: [PAM] Authenticating...
jul 02 23:44:03 note sddm-helper[3385]: [PAM] returning.
jul 02 23:44:03 note sddm-helper[3385]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
jul 02 23:44:03 note systemd[1]: Created slice User Slice of sddm.
jul 02 23:44:03 note systemd[1]: Starting User Manager for UID 618...
jul 02 23:44:03 note systemd-logind[678]: New session c18 of user sddm.
jul 02 23:44:03 note systemd[1]: Started Session c18 of user sddm.
jul 02 23:44:03 note systemd[3387]: pam_unix(systemd-user:session): session opened for user sddm by (uid=0)
jul 02 23:44:03 note systemd[3387]: Assertion 'startswith(line, "env=")' failed at src/basic/env-util.c:797, function deserialize_envi
jul 02 23:44:03 note systemd[1]: Started Process Core Dump (PID 3391/UID 0).
jul 02 23:44:03 note systemd[3388]: pam_unix(systemd-user:session): session closed for user sddm
jul 02 23:44:03 note systemd[1]: Failed to start User Manager for UID 618.
jul 02 23:44:03 note systemd[1]: user@618.service: Unit entered failed state.
jul 02 23:44:03 note systemd[1]: user@618.service: Failed with result 'protocol'.
jul 02 23:44:03 note sddm-helper[3385]: pam_systemd(sddm-greeter:session): Failed to create session: Start job for unit user@618.servi
jul 02 23:44:03 note sddm[3377]: Greeter session started successfully
jul 02 23:44:03 note sddm-greeter[3393]: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-sddm'
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/kodi.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/lxqt.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/openbox-kde.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/openbox.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/plasma.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Reading from "/usr/share/wayland-sessions/plasmawayland.desktop"
jul 02 23:44:03 note sddm-greeter[3393]: Connected to the daemon.
jul 02 23:44:03 note sddm[3377]: Message received from greeter: Connect
jul 02 23:44:03 note sddm-greeter[3393]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
jul 02 23:44:03 note systemd-coredump[3392]: Process 3387 (systemd) of user 618 dumped core.
                                             
                                             Stack trace of thread 3387:
                                             #0  0x00007f4f5d150670 raise (libc.so.6)
                                             #1  0x00007f4f5d151d00 abort (libc.so.6)
                                             #2  0x00007f4f5e299962 log_assert_failed (libsystemd-shared-233.so)
                                             #3  0x00007f4f5e2a494f deserialize_environment (libsystemd-shared-233.so)
                                             #4  0x00007f4f5e2a49e8 n/a (libsystemd-shared-233.so)
                                             #5  0x00007f4f5e2a25ac execute_directories (libsystemd-shared-233.so)
                                             #6  0x0000564f80b2cc8b n/a (systemd)
                                             #7  0x0000564f80b2aa89 n/a (systemd)
                                             #8  0x00007f4f5d13d43a __libc_start_main (libc.so.6)
                                             #9  0x0000564f80b2bf9a n/a (systemd)
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject: Cannot create children for a parent that is in a different thread.
                                         (Parent is SDDM::GreeterApp(0x7ffd1d2a7e90), parent's thread is QThread(0x20e04c0), current t
jul 02 23:44:03 note sddm-greeter[3393]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
jul 02 23:44:03 note sddm-greeter[3393]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:20:1: module "QtQuick.Vir
jul 02 23:44:03 note sddm-greeter[3393]: Adding view for "LVDS1" QRect(0,0 1366x768)
jul 02 23:44:03 note sddm-greeter[3393]: Message received from daemon: Capabilities
jul 02 23:44:03 note sddm-greeter[3393]: Message received from daemon: HostName
jul 02 23:44:06 note sddm-greeter[3393]: Reading from "/usr/share/xsessions/lxqt.desktop"
jul 02 23:44:06 note sddm[3377]: Message received from greeter: Login
jul 02 23:44:06 note sddm[3377]: Reading from "/usr/share/xsessions/lxqt.desktop"
jul 02 23:44:06 note sddm[3377]: Reading from "/usr/share/xsessions/lxqt.desktop"
jul 02 23:44:06 note sddm[3377]: Session "/usr/share/xsessions/lxqt.desktop" selected, command: "startlxqt"
jul 02 23:44:07 note sddm-helper[3402]: [PAM] Starting...
jul 02 23:44:07 note sddm-helper[3402]: [PAM] Authenticating...
jul 02 23:44:07 note sddm-helper[3402]: [PAM] Preparing to converse...
jul 02 23:44:07 note sddm-helper[3402]: [PAM] Conversation with 1 messages
jul 02 23:44:07 note sddm-helper[3402]: [PAM] returning.
jul 02 23:44:07 note sddm[3377]: Authenticated successfully
jul 02 23:44:07 note sddm-greeter[3393]: Message received from daemon: LoginSucceeded
jul 02 23:44:07 note sddm-helper[3402]: pam_unix(sddm:session): session opened for user ricardo by (uid=0)
jul 02 23:44:07 note systemd-logind[678]: New session c19 of user ricardo.
jul 02 23:44:07 note systemd[1]: Started Session c19 of user ricardo.
jul 02 23:44:07 note sddm-helper[3402]: Starting: "/usr/share/sddm/scripts/Xsession startlxqt"
jul 02 23:44:07 note sddm-helper[3403]: Adding cookie to "/home/ricardo/.Xauthority"
jul 02 23:44:07 note sddm-helper[3385]: [PAM] Closing session
jul 02 23:44:07 note sddm-helper[3385]: pam_unix(sddm-greeter:session): session closed for user sddm
jul 02 23:44:07 note sddm-helper[3385]: [PAM] Ended.
jul 02 23:44:07 note sddm[3377]: Auth: sddm-helper exited successfully
jul 02 23:44:07 note sddm[3377]: Greeter stopped.
jul 02 23:44:07 note sddm[3377]: Session started
jul 02 23:44:07 note systemd-logind[678]: Removed session c18.
jul 02 23:44:07 note systemd[1]: Removed slice User Slice of sddm.
jul 02 23:44:07 note lxqt-runner[3435]: LXQt::SingleApplication::SingleApplication(int&, char**, LXQt::SingleApplication::StartOptions
jul 02 23:44:07 note lxqt-policykit-agent[3433]: New PolkitAgentListener  0xce26e0
jul 02 23:44:07 note lxqt-policykit-agent[3433]: Adding new listener  PolkitQt1::Agent::Listener(0x7fff45e57fa0) for  0xce26e0
jul 02 23:44:07 note polkitd[825]: Registered Authentication Agent for unix-session:c19 (system bus name :1.376 [lxqt-policykit-agent]
jul 02 23:44:07 note lxqt-notificationd[3431]: registerService failed: another service with 'org.freedesktop.Notifications' runs alrea
jul 02 23:44:07 note lxqt-notificationd[3431]: registerObject failed: another object with '/org/freedesktop/Notifications' runs alread
jul 02 23:44:07 note lxqt-runner[3435]: QObject::connect: Cannot connect (null)::activated() to Dialog::showHide()
jul 02 23:44:07 note lxqt-runner[3435]: QObject::connect: Cannot connect (null)::shortcutChanged(QString,QString) to Dialog::shortcutC
jul 02 23:44:07 note kgpg[3441]: "Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\ne
jul 02 23:44:07 note lxqt-panel[3432]: "Not connected to D-Bus server"
jul 02 23:44:07 note lxqt-panel[3432]: "Not connected to D-Bus server"
jul 02 23:44:07 note lxqt-panel[3432]: "Not connected to D-Bus server"
jul 02 23:44:07 note lxqt-panel[3432]: ()
jul 02 23:44:08 note lxqt-panel[3432]: WinIdChange 1200007 handle QWidgetWindow(0x21b0d60, name="LXQtPanel panel1Window") QScreen(0x1f
jul 02 23:44:08 note lxqt-panel[3432]: Systray started
jul 02 23:44:08 note lxqt-powermanagement[3476]: Unable to register 'org.lxqt.lxqt-powermanagement' service - is another instance of l
jul 02 23:44:08 note lxqt-panel[3432]:     * Error image is NULL
jul 02 23:44:08 note lxqt-panel[3432]:     * Error image is NULL
jul 02 23:44:10 note fontinst[1556]: 1499049850 exiting
jul 02 23:44:10 note fontinst[1556]: 1499049850
jul 02 23:44:10 note lxqt-panel[3432]: execAction "/usr/share/applications/qterminal.desktop"
jul 02 23:44:10 note qterminal[3480]: TRANSLATIONS_DIR: Loading translation file "qterminal_pt_BR.qm" from dir /usr/share/qterminal/tr
jul 02 23:44:10 note qterminal[3480]: load success: true
jul 02 23:44:10 note qterminal[3480]: Properties constructor called
jul 02 23:44:10 note qterminal[3480]: QDir::exists: Empty or null file name
jul 02 23:44:10 note qterminal[3480]: Canot open file "/home/ricardo/.config/qterminal.org/qterminal_bookmarks.xml"
jul 02 23:44:10 note qterminal[3480]: default KB_LAYOUT_DIR:  "/usr/share/qtermwidget5/kb-layouts"
jul 02 23:44:10 note qterminal[3480]: loadAllColorSchemes

Last edited by ricardoscar (2017-07-03 02:53:33)

Offline

#7 2017-07-03 02:47:09

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: [SOLVED] Cant start Plasma after update

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code


Something is profoundly broken. Please provide details of your card(s) and driver(s), versions of plasma, X, Wayland and your full pacman log.


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#8 2017-07-03 03:05:23

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

I have an i5 with an Nvidia GeForce 630m, its an optimus notebook. Im now with the nouveau driver for Nvidia, for Intel it uses the wiki recommended.
Plasma 5, X, and Wayland fully upgraded.

The pacman log is here: https://ptpb.pw/iJf0. At 2017-07-02 20:22 I did the update before rebooting.

Last edited by ricardoscar (2017-07-03 03:07:48)

Offline

#9 2017-07-03 03:55:24

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

Downgranding systemd fix it for now.

Offline

#10 2017-07-03 04:00:02

Scimmia
Fellow
Registered: 2012-09-01
Posts: 13,188

Re: [SOLVED] Cant start Plasma after update

Long shot: do you have anything gnupg related in ~/.config/systemd/user/*? Or anything gnupg related other than symlinks in /etc/systemd/user/*

Online

#11 2017-07-03 04:04:56

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

Scimmia wrote:

Long shot: do you have anything gnupg related in ~/.config/systemd/user/*? Or anything gnupg related other than symlinks in /etc/systemd/user/*

No

Offline

#12 2017-07-03 06:52:22

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,109

Re: [SOLVED] Cant start Plasma after update

Did you change anything in this direction?
https://wiki.archlinux.org/index.php/Sy … _variables

Offline

#13 2017-07-03 11:27:54

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

I have my ~/.config/user-dirs.dirs modified, does this apply?

Offline

#14 2017-07-03 12:45:13

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,109

Re: [SOLVED] Cant start Plasma after update

Possibly (if the session/logind tries to apply those vars globally - idk.)
Worth a shot, notably if there're invalid lines (inc. comments ...) in that file.

Offline

#15 2017-07-03 13:28:49

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

the content of the file is, what changes can i try?

cat ~/.config/user-dirs.dirs

# This file is written by xdg-user-dirs-update
# If you want to change or add directories, just edit the line you're
# interested in. All local changes will be retained on the next run
# Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped
# homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an
# absolute path. No other format is supported.
# 
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Modelos"
XDG_PUBLICSHARE_DIR="$HOME/Público"
XDG_DOCUMENTS_DIR="$HOME/Documentos"
XDG_MUSIC_DIR="$HOME/Música"
XDG_PICTURES_DIR="$HOME/Imagens"
XDG_VIDEOS_DIR="$HOME/Vídeos"

Some of these dirs are symlinks.

Last edited by ricardoscar (2017-07-03 13:30:05)

Offline

#16 2017-07-03 13:32:17

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 70,109

Re: [SOLVED] Cant start Plasma after update

I'd start by just moving it away to see whether it has any impact at all. Then dig further in case.

Offline

#17 2017-07-03 15:36:43

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

I deleted ~/.config/user-dirs.dirs, upgraded systemd and systemd-sysvcompat and the problems reappeared.

Offline

#18 2017-07-04 12:21:43

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

What could I do to dig futher?

Offline

#19 2017-07-04 14:00:49

DrDeath
Member
From: Greece
Registered: 2009-05-09
Posts: 29

Re: [SOLVED] Cant start Plasma after update

I got the same problem besides that downgrading systemd and systemd-sysvcompat did nothing. And I got back to until 233-4.
Also tried to downgrade kernel as well but then all I got was a flickering screen with the systemd version (no X).
Reverted back to be fully updated (systemd-233-7 and linux-4.11.7-1 and only LXQt managed to load (also tried gnome and xfce)

My system is Arch 64 on AMD FX8320 with 16GB RAM Samsung SSD 830 pro and GeForce 650ti Boost if that can help in any way.

@ricardoscar sorry for the hijack smile

P.S Openbox loads too

Last edited by DrDeath (2017-07-04 14:51:51)

Offline

#20 2017-07-04 15:51:18

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

DrDeath wrote:

I got the same problem besides that downgrading systemd and systemd-sysvcompat did nothing. And I got back to until 233-4.
Also tried to downgrade kernel as well but then all I got was a flickering screen with the systemd version (no X).
Reverted back to be fully updated (systemd-233-7 and linux-4.11.7-1 and only LXQt managed to load (also tried gnome and xfce)

My system is Arch 64 on AMD FX8320 with 16GB RAM Samsung SSD 830 pro and GeForce 650ti Boost if that can help in any way.

@ricardoscar sorry for the hijack smile

P.S Openbox loads too

I downgraded to systemd 232, and systemd sysv compat 232, i dont know if i need to downgrade both. I hope this helps.

Offline

#21 2017-07-04 15:59:05

loqs
Member
Registered: 2014-03-06
Posts: 18,655

Re: [SOLVED] Cant start Plasma after update

Could you check if it is the same issue as https://bbs.archlinux.org/viewtopic.php?id=227929 just different symptoms being observed please.
When logged in under systemd 233 is /run/user empty?

Offline

#22 2017-07-04 16:16:55

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

/run/user have a dir named 1000, but this dir is empty.
running dbus-monitos results in: "Failed to open connection to session bus: Using X11 for dbus-daemon autolaunch was disable at compile time, set your DBUS_SESSIONS_BUS_ADDRESS instead"

Offline

#23 2017-07-05 06:03:38

DrDeath
Member
From: Greece
Registered: 2009-05-09
Posts: 29

Re: [SOLVED] Cant start Plasma after update

@ricardoscar
downgrading to systemd 232 fixed it for now. I also tried 233-75 from testing with no luck.

Offline

#24 2017-07-05 07:42:52

evil.genius
Member
Registered: 2016-02-13
Posts: 10

Re: [SOLVED] Cant start Plasma after update

I have exactly the same problem. Downgrading to systemd 232 has fixed it for now.

Offline

#25 2017-07-05 11:11:26

ricardoscar
Member
Registered: 2015-03-26
Posts: 33

Re: [SOLVED] Cant start Plasma after update

Is there a possibility that we are using some obscure systemd configuration or .service?

Offline

Board footer

Powered by FluxBB