Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: OpenSUSE Tumbleweed KDE not loading

  1. #11

    Default Re: OpenSUSE Tumbleweed KDE not loading

    Here is the output for

    Code:
    journalctl -b -u display-manager.service
    
    
    [0;1;38;5;185mJournal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.[0m
    -- Logs begin at Thu 2020-04-02 20:33:27 -03, end at Fri 2020-05-29 23:34:04 -03. --
    May 29 23:22:07 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:08 localhost systemd[1]: Starting X Display Manager...
    May 29 23:22:08 localhost display-manager[1573]: /etc/vconsole.conf available
    May 29 23:22:08 localhost display-manager[1573]: KEYMAP: us
    May 29 23:22:08 localhost display-manager[1573]: Command: localectl set-keymap us
    May 29 23:22:08 localhost display-manager[1573]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
    May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:10 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:11 localhost.localdomain lightdm[2087]: g_file_test: assertion 'filename != NULL' failed
    May 29 23:22:12 localhost.localdomain display-manager[1535]: Starting service lightdm..done
    May 29 23:22:12 localhost.localdomain systemd[1]: Started X Display Manager.
    May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: unable to locate daemon control file
    May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: stashed password to try later in open session
    The 'KDE theme' you mention is the login screen?
    Yes, is that what I meant.

  2. #12

    Default Re: OpenSUSE Tumbleweed KDE not loading

    I also ran
    Code:
    sudo journalctl --verify
    and the output was quite annoying. Maybe it can provide insights as well.

    Code:
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2625b1686be-fad6ffd20b120e84.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2668cf67eab-d599df1bcdfba086.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a269b9ed2a95-247951ff347f168e.journal~
    [0;1;31m604f48: Invalid entry item (8/29 offset: 000000[0m
    [0;1;31m604f48: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a27d97eec150-54ac79c96f46e6b3.journal~:604f48 (of 8388608 bytes, 75%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a27d97eec150-54ac79c96f46e6b3.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a28e70a2580b-73bf6a8b84b6285c.journal~
    [0;1;31m73be20: Invalid entry item (26/29 offset: 000000[0m
    [0;1;31m73be20: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2a78f12e0e5-073465d2f4b5f083.journal~:73be20 (of 8388608 bytes, 90%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2a78f12e0e5-073465d2f4b5f083.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2b83749b7bc-d0ba08d2fc046ea9.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2b97de1d5f4-88032fcde7b396f5.journal~
    [0;1;31m9ecff8: Invalid object[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2e11218926d-d2c59cbdc1b9ce5a.journal~:9ecff8 (of 16777216 bytes, 62%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2e11218926d-d2c59cbdc1b9ce5a.journal~ (Bad message)[0m
    [0;1;31m897e78: Invalid entry item (21/29 offset: 000000[0m
    [0;1;31m897e78: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3049d7ff67a-6ade40188f9916f4.journal~:897e78 (of 16777216 bytes, 53%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3049d7ff67a-6ade40188f9916f4.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a322b2bb0821-9044943040f64b85.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a32cad0d4691-0082c3a18921e316.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a33e804b1b15-d7f370a0e68e3636.journal~
    [0;1;31m5f8df0: Invalid entry item (29/33 offset: 000000[0m
    [0;1;31m5f8df0: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a343e4aa378b-895fffdc4c279432.journal~:5f8df0 (of 8388608 bytes, 74%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a343e4aa378b-895fffdc4c279432.journal~ (Bad message)[0m
    [0;1;31m88afa8: Invalid hash (3fa7a96d26c13a73 vs. dcd0ed7ae0c07ef9[0m
    [0;1;31m88afa8: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3550823a3c2-e0511232b7324ea5.journal~:88afa8 (of 16777216 bytes, 53%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3550823a3c2-e0511232b7324ea5.journal~ (Bad message)[0m
    [0;1;31m462fb8: Invalid hash (87a522932156435a vs. f0c87223d498e866[0m
    [0;1;31m462fb8: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3568a6df9e2-06188e8bdd11c384.journal~:462fb8 (of 8388608 bytes, 54%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3568a6df9e2-06188e8bdd11c384.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3a5dda97d11-e63bbe18343cc14a.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3a7945e1236-357eff059724d31d.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3ae8ce770fe-2295c1e617b37ec2.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3cfa9b68696-95818a736427d689.journal~
    [0;1;31m46aef8: Invalid entry item (13/29 offset: 000000[0m
    [0;1;31m46aef8: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3d0971a56d5-b102932b6239cf24.journal~:46aef8 (of 8388608 bytes, 55%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3d0971a56d5-b102932b6239cf24.journal~ (Bad message)[0m
    [0;1;31m574000: Invalid object[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e1a13334bd-de6a99e213f8fe33.journal~:574000 (of 8388608 bytes, 68%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e1a13334bd-de6a99e213f8fe33.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e88294f3f1-a560b8b90f3d5bee.journal~
    [0;1;31m5bef10: Invalid entry item (11/32 offset: 000000[0m
    [0;1;31m5bef10: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f5a385f591-16a93acfadf499e9.journal~:5bef10 (of 8388608 bytes, 71%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f5a385f591-16a93acfadf499e9.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f74e1cd40d-d89071f0c5e5f54c.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f836679175-a10f425bc55d2dfa.journal~
    [0;1;31m625ea0: Invalid entry item (18/32 offset: 000000[0m
    [0;1;31m625ea0: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a40a85beef25-ba0aa46fddb3f59f.journal~:625ea0 (of 8388608 bytes, 76%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a40a85beef25-ba0aa46fddb3f59f.journal~ (Bad message)[0m
    [0;1;31m1af0e30: Invalid entry item (25/29 offset: 000000[0m
    [0;1;31m1af0e30: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44be59abc44-b1516c61a2868f92.journal~:1af0e30 (of 33554432 bytes, 84%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44be59abc44-b1516c61a2868f92.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44eca91330e-e1ac6148ec8ddc90.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4502da0a728-bcbc3054c03583d8.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4512ae5f52b-4824b1310f099f3e.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4585a13bdb2-3151b206ae51583e.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b4b8997392-6e50b9218c881ae9.journal~
    [0;1;31m405e00: Invalid entry item (28/29 offset: 000000[0m
    [0;1;31m405e00: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b578d853bf-ab2d4254a09b441b.journal~:405e00 (of 8388608 bytes, 50%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b578d853bf-ab2d4254a09b441b.journal~ (Bad message)[0m
    [0;1;31m97df40: Invalid entry item (8/29 offset: 000000[0m
    [0;1;31m97df40: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4d1fba28572-85784d2af900199e.journal~:97df40 (of 16777216 bytes, 59%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4d1fba28572-85784d2af900199e.journal~ (Bad message)[0m
    [0;1;31m68be60: Invalid entry item (22/29 offset: 000000[0m
    [0;1;31m68be60: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4e7142806e4-9e5560eb5e4600a5.journal~:68be60 (of 8388608 bytes, 81%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4e7142806e4-9e5560eb5e4600a5.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4fafd806876-c3bec826dfab5662.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a501fffdde39-d6633dfe912aacc4.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a504baaf2c39-57b836ea86a53f9e.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a511d1f6c0a2-a18bb65eafd553c0.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a52b7a5a7a5e-26ff5b9a37004f37.journal~
    [0;1;38;5;185m5c4ff0: Unused data (entry_offset==0)[0m
    [0;1;31m5c4ff0: Invalid hash (00000000 vs. def73f721dd8bb68[0m
    [0;1;31m5c4ff0: Invalid object contents: Bad message[0m
    [0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a539e80bdf9b-0eaa616aa4e6c7e3.journal~:5c4ff0 (of 8388608 bytes, 72%).[0m
    [0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a539e80bdf9b-0eaa616aa4e6c7e3.journal~ (Bad message)[0m
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a53d44d7f0c4-2e6062508f2957e6.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a541c74801a2-4b7ddbc7921a271c.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a5a4500bb7a7-a040e0b6e9eee295.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a5cdca30139d-da03f4fb4bb23066.journal~
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0ac1294d6c314f0583bd6f221332e055-00000000000006b5-0005a5cdca2fc1a9.journal
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0ac1294d6c314f0583bd6f221332e055-0000000000003057-0005a61356cf7c06.journal
    PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000.journal

  3. #13

    Default Re: OpenSUSE Tumbleweed KDE not loading

    Here is the output for
    Code:
    sudo journalctl -b -u display-manager.service
    Code:
                    Journal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.                      
    
    -- Logs begin at Thu 2020-04-02 20:33:27 -03, end at Fri 2020-05-29 23:34:04 -03. --
    May 29 23:22:07 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:08 localhost systemd[1]: Starting X Display Manager...
    May 29 23:22:08 localhost display-manager[1573]: /etc/vconsole.conf available
    May 29 23:22:08 localhost display-manager[1573]: KEYMAP: us
    May 29 23:22:08 localhost display-manager[1573]: Command: localectl set-keymap us
    May 29 23:22:08 localhost display-manager[1573]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
    May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:10 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.
    May 29 23:22:11 localhost.localdomain lightdm[2087]: g_file_test: assertion 'filename != NULL' failed
    May 29 23:22:12 localhost.localdomain display-manager[1535]: Starting service lightdm..done
    May 29 23:22:12 localhost.localdomain systemd[1]: Started X Display Manager.
    May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: unable to locate daemon control file
    May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: stashed password to try later in open session
    Journal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.
    The 'KDE theme' you mention is the login screen?
    Yes.

  4. #14
    Join Date
    Mar 2020
    Location
    São Leopoldo, RS, Brazil
    Posts
    159

    Default Re: OpenSUSE Tumbleweed KDE not loading

    Somehow SDDM got replaced by LightDM. Re-enable it:

    Code:
    sudo systemctl --force enable sddm.service
    openSUSE Tumbleweed

  5. #15

    Default Re: OpenSUSE Tumbleweed KDE not loading

    Uow, how did you realize it? (based on the info I provided)

    Probably I blindly agreed to it during that python installation.

    Your suggestion didn't work, somehow sddm doesn't exist.
    Here is the output for the command :

    Code:
    sudo systemctl --force enable sddm.service
    Failed to enable unit: Unit file sddm.service does not exist.
    Funny because the system says the opposite:

    Code:
    whereis sddm
    sddm: /usr/share/sddm
    I also tried to reinstall (restore) sddm and the theme I was using based on this thread with

    Code:
    sudo apt-get install --reinstall sddm-theme-maldives
    But no provider was found.

    Overall I removed lightDM

    Code:
    sudo apt-get purge lighdm
    But SDDM not "automatically replaced it" (I still can't login as before)

    Now and I'm trying to redefine SDDM as my default display-manager.
    This is the output for

    Code:
    systemctl status display-manager
    
          
    Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)
    Active: active (running) since Sat 2020-05-30 18:12:35 -03; 1h 34min ago
    Main PID: 2085 (xdm)
    Tasks: 20 (limit: 4915)
    Memory: 192.6M
    CGroup: /system.slice/display-manager.service
    ├─2085 /usr/bin/xdm
    ├─2087 /usr/bin/X -nolisten tcp -br vt7 -keeptty -auth /var/lib/xdm/authdir/authfiles/A:0-lTLaBR
    └─2121 /usr/bin/xconsole -notify -nostdin -verbose -exitOnFail
    May 30 18:12:35 localhost.localdomain root[2049]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
    May 30 18:12:35 localhost.localdomain display-manager[1533]: Starting service xdm..done
    May 30 18:12:35 localhost.localdomain systemd[1]: Started X Display Manager.
    May 30 18:13:02 localhost.localdomain xdm[2108]: gkr-pam: unable to locate daemon control file
    May 30 18:13:02 localhost.localdomain xdm[2108]: gkr-pam: stashed password to try later in open session
    May 30 18:13:02 localhost.localdomain xdm[2108]: pam_unix(xdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=drawbridge
    May 30 18:13:04 localhost.localdomain xdm[2108]: LOGIN FAILURE ON :0, drawbridge
    May 30 18:13:17 localhost.localdomain xdm[2108]: gkr-pam: unable to locate daemon control file
    May 30 18:13:17 localhost.localdomain xdm[2108]: gkr-pam: stashed password to try later in open session
    May 30 18:13:17 localhost.localdomain xdm[2108]: pam_unix(xdm:session): session opened for user drawbridge(uid=1000) by (uid=0)
    display-manager.service - X Display Manager

    • gkr-pam: unable to locate daemon control file (this error is reported constantly in log verifications)
    • LOGIN FAILURE ON :0, drawbridge (Apparently in somewhere is defined that [drawbridge, my user] can't succeed at the login)


    I hope it can provide more informinsights.
    Thank you so much for all your support so far.

  6. #16

    Default Re: OpenSUSE Tumbleweed KDE not loading

    [ERRATUM] I still unable to login through SDDM display manager.

    Since ligthDM is gone now, "Failed to start section" is no longer the issue here.

    The login screen now is an openSUSE default one, and I'm able to successfully login as well.
    After succeeding at login, I only have a small CLI widow and no (fancy)GUI at all.

    I'm also able to open vscode, firefox, and other applications through CLI commands.

    We're about to make it happen.

    o//

  7. #17

    Talking Re: OpenSUSE Tumbleweed KDE not loading

    "Today is a happy day."
    Me.


    Hey folks, the problem was solved!

    I just had to force install SDDM with zypper:

    Code:
    sudo zypper in -f sddm
    and so I did with my Desktop Environment:

    Code:
    sudo zypper in -t pattern kde kde_plasma 
    
    and then
    
    sudo zypper install plasma5-session
    Everything is working as before (AFAIK).

    I appreciate all efforts in this thread.
    When I introduced the problem (2-3 weeks ago) I was a complete Linux newbie, now I still as before just slightly less like.

    Thank you all folks.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •