KDE Failed in Solydxk 10 buster - SOLVED

Questions specific to the KDE DE go here
UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

KDE Failed in Solydxk 10 buster - SOLVED

Postby UncleSam » 20 Nov 2019 00:24

I logged in to Solydxk Debian 10 buster twice today, before lunch, and after lunch.
Before lunch I had no problems logging in, running applications, reading and writing
files, and shutting down my computer.
After lunch, when I tried to log in as user (same account), instead of my normal KDE Desktop,
an error viewport appeared, with a white X button on a square red background in the upper left and an
OK button on a blue background in the viewport's lower right. The text in the viewport read,
"The following installation problem was detected while trying to start KDE:
Temp directory (/tmp) is out of disk space
KDE is unable to start."


When I clicked the OK button, a black & white viewport popped up that covered the left half of my
screen. The Left side of the viewport had a vertical grayish bar. It had only one oval Okay button in the lower
left The text read, "Could no start ksmserver. Check your installation.
When I clicked the Okay button, nothing happened.

I rebooted and discovered that I could log in as root. YAY!

I could also view my user /home/user files in a Konsole. YAY!

However, when I tried to run Firefox-ESR, a viewport popped up displaying the Firefox icon
in the upper left corner titled "Profile Missing". The text in the viewport read,
"Your Firefox profile cannot be loaded. It may be missing or inaccessible.", with a
white vertical line inside a square gold box to the left of the text and an OK button in the lower right.

This was the first time I ever tried to run Firefox-ESR as root.

So I rebooted and restarted my computer using a SoldXK 9 live DVD in order to write this message.

Does anybody know an idea what might have happened when I tried to log in as user? And how
I might fix it, seeing that I can log in as root ?

User avatar
ilu
Posts: 2541
Joined: 09 Oct 2013 12:45

Re: KDE Failed in Solydxk 10 buster

Postby ilu » 20 Nov 2019 21:41

You cannot start firefox as root because that is a severe security risk and there are provisions in place to stop you from doing this by mistake.

Your main problem seems to be lack of (disk or memory) space. Since we don't know how you organized your system, boot into your system and login as root like you did before (or open a console with ctrl-alt-F1 instead of logging into KDE) and post the output of these commands to provide us with more information. It would be easoer if you could save the output to a file - if your disks are full, you'd need to mount a pen drive or similar.

Code: Select all

inxi -Fxz > log.txt
fdisk -l >> log.txt
cat /etc/fstab >> log.txt
journalctl -p err > log1.txt
If you don't manage to do so, boot the live system and mount your system partition (and cat the right fstab please, not the one from the live DVD). Journal won't be helpfull in that case though.

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 21 Nov 2019 01:22

I did what you said to do. Here are the results:

Code: Select all

solydxk@solydxk:~$ cat log.txt                                                                                 
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors                                              
Disk model: WDC WD10EZEX-22M                                                                                   
Units: sectors of 1 * 512 = 512 bytes                                                                          
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xc387964f

Device     Boot    Start        End    Sectors   Size Id Type
/dev/sdb1           2048   14682111   14680064     7G 83 Linux
/dev/sdb2  *    14682112   48236543   33554432    16G 83 Linux
/dev/sdb3       48236544 1953523711 1905287168 908.5G 83 Linux


Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: WDC WD2500JB-00R
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0009c1a6

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1        2048 488396799 488394752 232.9G 83 Linux




Disk /dev/sdc: 931.5 GiB, 1000204883968 bytes, 1953525164 sectors
Disk model: External USB 3.0
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xd2514d8b

Device     Boot  Start        End    Sectors   Size Id Type
/dev/sdc1       206848 1953520064 1953313217 931.4G 83 Linux
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
UUID=ace18def-4f61-43e4-a652-e3c2a60f1f6e       /       ext4    defaults        0       1
UUID=bafa5160-764a-44ed-9d27-bdded9d7d70b       /home   ext4    defaults        0       2
UUID=b09e6105-bf90-403c-ab3e-61676da9bdf7       swap    swap    sw      0       0
The two hard drives are marked WDC for Western Digital Co. My main drive
that I boot to is the WDC 931.5 GiB hard drive. It was installed new last May.
The WDC 239.9 GiB hard drive is one I use for backup irregularly and rarely.
It worked last time I tried it, but that was several years ago.

Code: Select all

solydxk@solydxk:~$ cat log1.txt
-- Logs begin at Wed 2019-11-20 18:20:30 EST, end at Wed 2019-11-20 18:22:52 EST. --
Nov 20 18:20:35 solydk ntpd[727]: format error frequency file /var/lib/ntp/ntp.drift
Nov 20 18:20:36 solydk ntpd[727]: error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
Nov 20 18:20:37 solydk ntpd[727]: error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
Nov 20 18:20:39 solydk ntpd[727]: bind(24) AF_INET6 fe80::3402:3bf2:e2ba:7695%2#123 flags 0x11 failed: Cannot assign requested address
Nov 20 18:20:39 solydk ntpd[727]: unable to create socket on enp1s0 (5) for fe80::3402:3bf2:e2ba:7695%2#123
Did I get the correct /etc/fstab ? I ran the command after logging in to my hard drive as
root, so yes, I believe so.

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 21 Nov 2019 07:47

I'd like to see all available space on your system:

Code: Select all

df -h


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 21 Nov 2019 17:04

In creating the two log files using the four command lines ilu provided, I should mention that I got an STDERR message from one of the commands. I thought I had written it down, but I cannot find where I wrote it. Do you want me to redo that set of commands again and write down the error message?

After booting from the 931.5 GiB hard drive and logging in as root,

Code: Select all

#whoami
root
#ls list
#list
#less list
#mv list bash/    #a  bash script I had previously written and wanted to save
#df -h >list
#less list
After copying this list to an external USB 3.0 ext3 filesystem, I rebooted from the Solydxk 9 Live CD in
order to post it here:

Code: Select all

solydxk@solydxk:~$ cat list
Filesystem      Size  Used Avail Use% Mounted on
udev            3.4G     0  3.4G   0% /dev
tmpfs           708M   11M  698M   2% /run
/dev/sdb2        16G   15G     0 100% /
tmpfs           3.5G  2.7M  3.5G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           3.5G     0  3.5G   0% /sys/fs/cgroup
/dev/sdb3       894G  113G  735G  14% /home
tmpfs           708M  8.0K  708M   1% /run/user/0
I remember wiping out the /tmp from my /home/user directory earlier in the week while logged in as
user. I don't remember the rsync command I used to do that. It might, however, still be in user's
history buffer since I have been logging in as root since KDE failed. I believe that bash history FIFO
buffer is saved from session to session during normal logout/shutdown. Do you want me to examine it?
If yes, is it called /home/user/history or is it stored somewhere else?

Thank you for your reminders regarding security. I will follow them to the best of my ability.

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 22 Nov 2019 13:35

This line shows the problem:

Code: Select all

Filesystem      Size  Used Avail Use% Mounted on
/dev/sdb2        16G   15G     0 100% /
So, you have no space available on root.

I personally recommend to increase the size of the root partition by shrinking the home partition.

In a live session, backup your home partition before you start the process. Then, in GParted you can shrink /dev/sdb3 by at least 10G and use that to increase the size of /dev/sdb2. This may take a while.


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 22 Nov 2019 15:01

Okay, Arjen, I will decrease my /home partition by 10 GiB and then increase my / partition by the same amount, using gparted from the Live DVD. Thank you for pointing this out to me.

First, before backing up my files, I have a question about ownership of my user files
on the external USB3.1-connected zip drive.

I wrote rsync scripts to backup my ext4 files on /home to my external
USB3.1-connected media, which are formatted as ext3. The scripts work fine as
1-way weekly incremental backups.

From Dolphin on the Solydxk 9 live DVD, my /home/sam files appear as
User: solydxk
Group: solydxk
whereas on my hard drive the same files appeared as
User: sam
Group: users
IIRC.

A typical rsync call in my backup script is:

Code: Select all

rsync -aghprtuvz --progress --stats --exclude-from=rsync.excludefiles bash/  $DRIVE/bash/
(Note there is whitespace between bash/ and $DRIVE)

where $DRIVE is the external medium and bash is the name of the subdirectory at /home/sam that I want to backup to another /bash/ subdirectory on the external medium, which mounts to /media/sam/56f70575-dff8-4df2-bcd6-0269f07f1e88/ when run as user sam from my hard drive.

I always run these backups as user sam, and rsync.excludefiles is:

Code: Select all

*.bk?
*~
*~~
*.deb
*.o
*.so
*.bak
*.iso
*.exe
temp*
tmp*
a.out
*.tar.gz
*.backup
*_backup
ee/ee/*
ee/pcb2
ee/PCB-abandoned-folder/
ee/pcb_backup
Is there an option to apply to the rsync call so that the ownership/group
associated with each of the files copied remain sam/users on the external medium?
Or will the Solydxk 9 Live DVD automatically let the file ownership/group unchanged for some reason I don't foresee?

I only ask because I never ran my backup script as superuser, only as user. If you don't know the answer, I will run rsync as superuser with exactly one file and see what happens before running the backup script as superuser.

Are there any non-user (system) files or user hidden (dot) files I should back up?

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 22 Nov 2019 15:25

This is perfectly logical if your user ID is 1000 and the group ID of user is 1000. On a live ISO that translates to user solydxk with user ID 1000 and group solydxk with group ID 1000.


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 22 Nov 2019 16:13

I don't recall user sam's user ID/group ID. Is 1000 the default for the first user's ID and first user's group ?
If yes, then they are the same.

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 22 Nov 2019 18:27

Yes, usually 1000 is the first ID given to a new user/group.


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 23 Nov 2019 22:57

I modified my backup scripts but the rsync calls because of a double slash for the solydxk in the destination argument whether I wrote it into the BASH script as $USER or as solydxk. I could not figure out where the double slash was coming from. So I ran all my rsync calls one at a time from the BASH shell. That worked okay.

Next for gparted, with which I have minimal experience.
Using gparted from the solydxk 9 Live DVD, I downsized the /dev/sdb3 ext4 partition from 908.51 GB to 896.1 GB.
After that completed in a few minutes, I tried to increase the /dev/sdb2 ext4 partition ( Its label starts with
/media/solydxk/SolydK 10 ), but the operation would not take. Is /dev/sdb2 the correct partition?
What am I doing wrong?

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 24 Nov 2019 11:07

I do not know what steps you took but I tested this with a live SolydK ISO.

I first had to create three partition, then remove the first partition and allocate the free space with the second partition to get a similar setup as yours (starting with partition ID 2 instead of 1).

Screenshot_20191124_112012.png
Then I removed 10G at the start of the last partition to free up space for the root partition.

Screenshot_20191124_115212.png
After that I could allocate that free space to the root partition.

Screenshot_20191124_115843.png
This left a 1MB unallocated space between the two partitions but that does not hinder the stability of the system.


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 24 Nov 2019 19:59

I downsized the home ptn. at /dev/sdb3 by 12 GB, from 908.51 GB to 896.51 GB.
Now gparted shows the image at https://ibb.co/pWzMzjn
(This page showed It was not possible to determine the dimensions of the image.
Please verify that the URL you entered is correct.
when I tried to post the image
here as a png using the insert image button.)

Is this correct ? Or did I do something wrong?

If this is correct, then I will increase the boot ptn. at /dev/sdb2 by 12 GB.

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster

Postby Arjen Balfoort » 25 Nov 2019 10:20

You shrunk sdb3 at the end of the partition but you should have done that at the start of the partition so that you can add the free space to the sdb2 partition.

Add the free space back again to sdb3 as it was and when done, try to free space at the start of sdb3 and add that free space to sdb2.


SolydXK needs you!
Development | Testing | Translations

UncleSam
Posts: 37
Joined: 16 Apr 2016 20:03

Re: KDE Failed in Solydxk 10 buster

Postby UncleSam » 25 Nov 2019 17:54

Arjen,
I followed your advice.

After awhile, I figured out that in gparted you have to unmount/dismount the
partition before you can Resize/Move it. If fact, the numerals in the text
boxes brought up by the Resize/Move button are meaningless until you dismount
the ptn.

I restored 12GB freed space to get sdb3 back to its original size
This step took about 41 minutes.

Then I freed space to the start of sdb3.
Then I added that free 12GB to the sdb2.

I found the Free Space Preceding: and
Free Space Following: text boxes and adjusted the size of
sdb2 upward by 12GB.

These two steps only took a minute or two.

I wasn't sure it would work because when I added the free 12GB to sdb2,
I left zero MB at the end (the Free Space Following textbox).
I rebooted from the hard drive and my user accounts are unchanged so
far. I verified this by opening libre-office and seeing "recent documents"
still set to the ones I had most recently editted. Great!

So I might have a problem if I fill up this sdb2 ptn. more than 12GB.
It might lose data from the hard drive in that case, I am guessing.
Or it just might repeat this problem.

This resizing partitions seems to me a bit like editing sound recordings
on magnetic tape, something else with which I have no experience.

In case you didn't see it, Jessie at distrowatch.com wrote a good review of
this distro. I am also a fan.

Thanks for your advice and for you suggestions, Arjen and ilu. I ap-
preciate your helping me to keep my original boot ptn. unchanged, but
just slightly bigger.

User avatar
Arjen Balfoort
Site Admin
Posts: 9331
Joined: 26 Jan 2013 19:36
Location: Netherlands
Contact:

Re: KDE Failed in Solydxk 10 buster - SOLVED

Postby Arjen Balfoort » 25 Nov 2019 18:33

You're welcome. Enjoy SolydK and visit back if you need help.


SolydXK needs you!
Development | Testing | Translations


Return to “KDE specific (SolydK)”

Who is online

Users browsing this forum: No registered users and 1 guest