Jump to content
funtoo forums
  • 0
bourbon

Several problems on KDE-Plasma

Question

Hi All,

I am new on Funtoo world and am trying to make my fresh installation suitable for my daily use, I have been following the installation guide but something is wrong here and I don't know how to resolve, these are the small problems am facing right now:

1 - Icons on the bar don't keep the position, all of them (clock, etc.) are on the left side every time I switch on the computer. I have been trying to cancel the ~/.kde but got nothing.

2 - When I minimize an application in the bar (Konsole, etc.) they simply disappear (when going to open again, is a new one, showing the number, like Konsole (1), Konsole (2), etc. sometime are under the new apps opened, for instance: opening Firefox full screen, when closing it the other app opened before and minimized in the bar is on the desktop there).

3 - I have half KDE in Italian language and half in English language (some programs like Dolphin and LibreOffice, full English). I have been downloading "l10n" and settled the suggested files for Italian language solving nothing and I don't see Italian language in the System Settings (only Firefox is full Italian after installing the appropriate file).

4 - System Settings does'nt keep all the settings. For instance, does'nt keep the user data (profile picture, name, etc.).

I don't know which data/output could be useful for you, if needing some, please ask.

Thank you for reading, ciao

Share this post


Link to post
Share on other sites

41 answers to this question

Recommended Posts

  • 0

Hi, Silvio!

I thought that SystemRescueCD had the driver nvidia, then we'll have to do something else, let's make Funtoo bootable again.

For this you should do a chroot and reinstall the kernel and the necessary drivers with the commands:

# emerge debian-sources
# emerge @module-rebuild

I do not use the UEFI system, but you should follow the steps in the Grub Funtoo installation manual, but this time we will install Grub on a USB drive, so you should connect one and see what device it is with the 'lsblk' command, and at the time of installing Grub you should replace the value of /dev/sda with the pendrive. You should then leave the pendrive connected to the PC and reboot, and choose this device (pen drive) as bootable.

So you do not lose the installation of grub that accesses your other operating systems.

Let's see if that works, because chroot is more for working only in text mode.

Big hug,

Eduardo

Share this post


Link to post
Share on other sites
  • 0

Hi Eduardo :)

For some strange reason the last message of yours is not on the Forum here, I saw it on my mail, this one:
 

Hi, Silvio!

I thought that SystemRescueCD had the driver nvidia, then we'll have to do something else, let's make Funtoo bootable again.

For this you should do a chroot and reinstall the kernel and the necessary drivers with the commands:

# emerge debian-sources # emerge @module-rebuild

I do not use the UEFI system, but you should follow the steps in the Grub Funtoo installation manual, but this time we will install Grub on a USB drive, so you should connect one and see what device it is with the 'lsblk' command, and at the time of installing Grub you should replace the value of /dev/sda with the pendrive. You should then leave the pendrive connected to the PC and reboot, and choose this device (pen drive) as bootable.

So you do not lose the installation of grub that accesses your other operating systems.

Let's see if that works, because chroot is more for working only in text mode.

Big hug,

Eduardo

I did :

# emerge debian-sources

# emerge @module-rebuild

After that, with a bit of embarassement I tell you that am unable to perform the step for usb drive because I don't understand which one it is looking at "lsblk" output (same for "lsusb" command, is like is not there. I don't know if my usb drive is faulty.

Am trying other steps right now but got nothing till now; for instance, after looking at some Gentoo's pages I modified some files, here they are:

/etc/conf.d/xdm

DISPLAYMANAGER="sddm"
#DISPLAYMANAGER="lightdm"
 rc_need="dbus"
/usr/share/sddm/scripts/Xsetup

/bin/sh
# Xsetup - run as root before the login dialog appears

setxkbmap gb,us,it
 nano /etc/portage/make.conf

# Install Italian (Italy) translation (if available)
# L10N="en-US it-IT"
# L10N="en-US it"
L10N="it"

# LINGUAS="en_US it_IT"
LINGUAS="en_US it"


VIDEO_CARDS="nvidia"

USE="nvidia"

USE="dbus"

USE="X"

USE="gif jpeg png tiff xpm"

After that, some output here:

(chroot) sysresccd / # ck-list-sessions
** Message: Failed to connect to the D-Bus daemon: Could not connect: File o directory non esistente

(chroot) sysresccd / # dbus-monitor --system
Failed to open connection to system bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

(chroot) sysresccd / # dbus-monitor --session
Failed to open connection to session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

(chroot) sysresccd / # emerge -auDN @world

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild     U  ] dev-libs/openssl-1.0.2o [1.0.2n]

Would you like to merge these packages? [Yes/No] Yes

(chroot) sysresccd / #  emerge -pv --depclean

>>> No packages selected for removal by depclean
Packages installed:   1227
Packages in world:    71
Packages in system:   79
Required packages:    1227
Number to remove:     0

(chroot) sysresccd / #  emerge -av --update --deep --newuse --changed-use --with-bdeps=y @world

These are the packages that would be merged, in order:

Calculating dependencies... done!

Total: 0 packages, Size of downloads: 0 KiB

Nothing to merge; quitting.

Well, if we get the solution this will be an historical case, I suppose lol

Big hug

Silvio

 

 

Share this post


Link to post
Share on other sites
  • 0

Hi, Silvio!

I believe you did not see my message because she is on page two of the forum. Did you find her now?

In my opinion it would be very important to reinstall grub, for this I'll explain the output lsblk. This is the output of the lsblk command here without the attached pendrive:

NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0 465,8G  0 disk  
├─sda1                8:1    0     2M  0 part  
├─sda2                8:2    0     2G  0 part  
│ └─md1               9:1    0     2G  0 raid1 /boot
└─sda3                8:3    0   463G  0 part  
  └─md2               9:2    0 925,8G  0 raid0 
    ├─swsyho-swap   253:0    0    32G  0 lvm   [SWAP]
    ├─swsyho-system 253:1    0   250G  0 lvm   /
    └─swsyho-home   253:2    0 643,8G  0 lvm   /home
sdb                   8:16   0 465,8G  0 disk  
├─sdb1                8:17   0     2M  0 part  
├─sdb2                8:18   0     2G  0 part  
│ └─md1               9:1    0     2G  0 raid1 /boot
└─sdb3                8:19   0   463G  0 part  
  └─md2               9:2    0 925,8G  0 raid0 
    ├─swsyho-swap   253:0    0    32G  0 lvm   [SWAP]
    ├─swsyho-system 253:1    0   250G  0 lvm   /
    └─swsyho-home   253:2    0 643,8G  0 lvm   /home
sdc                   8:32   0   2,7T  0 disk  
└─sdc1                8:33   0   2,7T  0 part  /hd
sr0                  11:0    1  1024M  0 rom   
sr1                  11:1    1  1024M  0 rom   

And this is the output with the pendrive connected:

NAME                MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0 465,8G  0 disk  
├─sda1                8:1    0     2M  0 part  
├─sda2                8:2    0     2G  0 part  
│ └─md1               9:1    0     2G  0 raid1 /boot
└─sda3                8:3    0   463G  0 part  
  └─md2               9:2    0 925,8G  0 raid0 
    ├─swsyho-swap   253:0    0    32G  0 lvm   [SWAP]
    ├─swsyho-system 253:1    0   250G  0 lvm   /
    └─swsyho-home   253:2    0 643,8G  0 lvm   /home
sdb                   8:16   0 465,8G  0 disk  
├─sdb1                8:17   0     2M  0 part  
├─sdb2                8:18   0     2G  0 part  
│ └─md1               9:1    0     2G  0 raid1 /boot
└─sdb3                8:19   0   463G  0 part  
  └─md2               9:2    0 925,8G  0 raid0 
    ├─swsyho-swap   253:0    0    32G  0 lvm   [SWAP]
    ├─swsyho-system 253:1    0   250G  0 lvm   /
    └─swsyho-home   253:2    0 643,8G  0 lvm   /home
sdc                   8:32   0   2,7T  0 disk  
└─sdc1                8:33   0   2,7T  0 part  /hd
sdh                   8:112  1  14,9G  0 disk  
└─sdh1                8:113  1  14,9G  0 part  
sr0                  11:0    1  1024M  0 rom   
sr1                  11:1    1  1024M  0 rom   

So the pendrive is what is different between one and another, in this case the device /dev/sdh. So in my case I would have to do "grub-install (parameters for the UEFI system) /dev/sdh", can you do this? Then you should choose the boot by the pendrive in bios...

I'm rooting for you and I hope we can get it working again!

Big hug,

Eduardo

Share this post


Link to post
Share on other sites
  • 0

Hi, Eduardo :)

Yes please, I see your message on the forum here now. I see also the last one were you telling me is very important to reinstall Grub.

Before seeing it I have been reinstalling the "original" Grub on the system but situation is still the same.

Do we have to think for something else or still needing to try with Grub on pen drive?

I don't know if important to know but the situation about Grub is this one:

- Installed with Linux Mint which is on /dev/sdb2 (Grub installed on /dev/sda)

- Boot partition for Funtoo is the EFI one on /dev/sda2.

GParted output for you here (/dev/sda = Windows and /dev/sdb = Linux):

C6761nC.png

SxgtzJ2.png

Hoping to help me is fun for you Eduardo, if it is stressing no problem we leave it

Big hug

Silvio

 

Share this post


Link to post
Share on other sites
  • 0

Hi, Silvio!

Yes, we'll have to make Funtoo bootable again and for that we will use a pendrive. After you boot with SystemRescueCD you should connect the pendrive (/dev/sdc) and follow these steps, assuming you only have two disks (/dev/sda and /dev/sdb) on your PC:

# mkdir /mnt/funtoo
# mount /dev/sdb3 /mnt/funtoo
# mount /dev/sda2 /mnt/funtoo/boot/efi
# cd /mnt/funtoo
# mount -t proc none proc
# mount --rbind /sys sys
# mount --rbind /dev dev
# cp /etc/resolv.conf /mnt/funtoo/etc/
# env -i HOME=/root TERM=$TERM /bin/chroot . bash -l
# export PS1="(chroot) $PS1"
(chroot) # ego sync
(chroot) # emerge debian-sources
(chroot) # emerge @module-rebuild
(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
(chroot) # boot-update
(chroot) # exit
# cd /mnt
# umount -lR funtoo
# reboot

After these steps you should start the PC by the pendrive that should not be disconnected. Try this and tell me the result, please.

I'm happy to help and I would love to make everything work again!

Big hug,

Eduardo

Share this post


Link to post
Share on other sites
  • 0
46 minutes ago, bourbon said:

Boot partition for Funtoo is the EFI one on /dev/sda2

Are you sure you have to boot from /dev/sda2? I have an EFI system as well but I don't boot from the EFI partition but from the root partition of my funtoo installation. For you that would probably be /dev/sdb3.

Share this post


Link to post
Share on other sites
  • 0

Hi Jhan,

I can't give you technical explanation, I can tell you my recent experience with UEFI:
- Having Windows 10 on /dev/sda as first installation I reserved /dev/sdb for Linux,
knowing is correct to have both disk "UEFI" they are like that.
Linux Mint has been the first distro going on /dev/sdb, installation process is
very simple and does'nt ask for boot partition.
First time I have been installing Grub on /dev/sdb thinking that is the correct place
but I experienced that Linux Mint not seen by other distros
(needing to create folder in /root and edit /etc/fstab to get access).
So, at second installation I have been
putting Grub on /dev/sda (being the EFI partition over there) and that problem disappeared.
When installing Linux Calculate, the installer asking for /boot partition and
remembering GParted shows /dev/sda2 as EFI /boot partition I have been assigning it.
Calculate Linux (Gentoo based) works perfectly (still needing to set permissions
properly to manage files stored on Linux Mint but that will be simple to fix, just
needing to work on it, I am sure).
At time of Funtoo's installation I have been trying to install it only on "/" partition,
avoiding /usr etc. and thinking is correct to assign /dev/sda2 as /boot partition, I did it.
Grub reconnaissed Funtoo and booting properly, got problem with SDDM login but solved it
creating a new user,thanking Cafaia's hint.
The big problem am experiencing now, as you know, comes out after a wrong command of mine
affecting the "native" kernel.
I don't know if I have been following the right steps installing CLD and Funtoo, I took
action according with what I understood needing to do.

Ciao

Share this post


Link to post
Share on other sites
  • 0

New problem here Eduardo, look:

(chroot) sysresccd / # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
bash: grub-install: comando non trovato

Thinking you forgot something, i have been trying with the command below and comes out another problem
 

(chroot) sysresccd / # emerge grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
!!! '--target=x86_64-efi' is not a valid package atom.
!!! Please check ebuild(5) for full details.
(chroot) sysresccd / #

:)

(comando non trovato = can't find the command)

Edited by bourbon
Adding data

Share this post


Link to post
Share on other sites
  • 0

Hi, Silvio!

The first command is the correct command, the error is because you have not installed in Funtoo the Grub program. Then you will have to do these steps:

# mkdir /mnt/funtoo
# mount /dev/sdb3 /mnt/funtoo
# mount /dev/sda2 /mnt/funtoo/boot/efi
# cd /mnt/funtoo
# mount -t proc none proc
# mount --rbind /sys sys
# mount --rbind /dev dev
# cp /etc/resolv.conf /mnt/funtoo/etc/
# env -i HOME=/root TERM=$TERM /bin/chroot . bash -l
# export PS1="(chroot) $PS1"
(chroot) # ego sync
(chroot) # emerge debian-sources
(chroot) # emerge grub
(chroot) # emerge @module-rebuild
(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
(chroot) # boot-update
(chroot) # exit
# cd /mnt
# umount -lR funtoo
# reboot

I put it more: "emerge grub". I believe that if you follow this you will have a bootable system.

Big hug,

Eduardo

Share this post


Link to post
Share on other sites
  • 0

Ok :) Am starting again with the command

#emerge grub

After that, I will give

(chroot) # emerge @module-rebuild
(chroot) # grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
(chroot) # boot-update
(chroot) # exit
# cd /mnt
# umount -lR funtoo
# reboot

Suppose is correct, I was still in chroot

:)

Share this post


Link to post
Share on other sites
  • 0

My dear Eduardo, better if we laughing here, look:
 

(chroot) sysresccd / #  grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
Installing for x86_64-efi platform.
grub-install: error: /boot doesn't look like an EFI partition.
(chroot) sysresccd / #

I don't know if I have to go to sleep or to try something here lol

Big hug

Silvio

 

Edited by bourbon
Edit skypped

Share this post


Link to post
Share on other sites
  • 0

Hi, dear Silvio!

Well, now who does not know, it's me.

Unfortunately I give up... I suggest you do a new installation of Funtoo, in the face of all this seems to be the most correct thing to do.

Big hug,

Eduardo

Share this post


Link to post
Share on other sites
  • 0
1 hour ago, bourbon said:

My dear Eduardo, better if we laughing here, look:
 


(chroot) sysresccd / #  grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc
Installing for x86_64-efi platform.
grub-install: error: /boot doesn't look like an EFI partition.
(chroot) sysresccd / #

 

I think this error message is correct. If you followed the instructions of cafaia you probably mounted the efi partition /dev/sda like so:

mount /dev/sda2 /mnt/funtoo/boot/efi

That means your grub-install should use the probably look like this:

grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id="Funtoo Linux [GRUB]" --recheck /dev/sdc

as you mounted the efi partition too /boot/efi

Share this post


Link to post
Share on other sites
  • 0

Hi Jhan,

Yes, looking at it now with "fresh mind" I get your point; yesterday I was just following Cafaia's instructions without checking on it, he is very experienced and I am a noob.

Anyway, has been too much, I got annoyed and removed Funtoo. Maybe I will install it again later.

Best regards

Silvio

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×