Roey's questions

I wanna migrate my Kubuntu 21.04 x64 OS from my current HP laptop to my new one.

It's currently in /dev/sda5 EXT4 partition on a dual-boot machine (w/ Windows 10 21H1 on /dev/sda3 NTFS) using GRUB

AFAIK I have 2 possibilities here:

1. Backup the entire partition using a 3rd party Windows app (e.g Acronis true image backup) create an EXT4 partition with 67GB+ disc space (w/ a linuxswap partition =RAM_SIZE of the new machine) and restore the EXT4 partition to that disc space
2. from rootfs (~/) backup all the apps,settings,configs (essentially all the installations & customizations I've made from the previous 21.04 installation including my user files (/home)) install a fresh Kubuntu 21.04 OS restore/override it with this backup

There are two problems here one for each option:

1. Can Kububtu detect and install the the new hardware on boot from network repos or Kubuntu bootable USB?
2. IDK if it's possible to create this kind of backup and if I can override a fresh one with it

Maybe none of the options above is practical or Maybe there are another options, Any suggestion are welcomed

Thanks

OP on reddit

Hi,

I have a problem with Kubuntu 19.04 in my 13" FHD (1920x1080) laptop screen. The login screen is too small as was the whole Plasma KDE.

I was able to re-scale the screen to 1.5 (150%) and now Plasma KDE looks great but the login screen still remains small (FHD scaled) though when I come back from Suspend mode the login screen do re-scales to 150%.

There is no file called sddm.conf under /etc/, as written in the project's github page, in my OS sddm.conf located under /etc/init.

I have added the lines

[X11]
ServerArguments=-nolisten tcp -dpi 144

At beginning of /etc/init/sddm.conf where 144 represents my base resolution in DPI as written in the X-Server information * 1.5 but still it doesn't fix the login screen resolution scale.

Any suggestions will be gladly welcomed.

TNX

Upon upgrading from Ubuntu 18.04 to Ubuntu 18.10 something happened to Gedit:

1. Its icon disappeared from my favorites (the only one doing so)
2. It doesn't appear anymore on the apps grid
3. Though it's installed I can't launch it from the Software Center

The only way I can launch it is from the terminal and then I get a pixelized icon which I can't add/pin it to my favorites.

I tried:

1. Removing/purging and re-installing (with Software Center and Terminal)
2. Make a soft link of /usr/bin/gedit and pin it but it didn't work
3. In dconf org.gnome.gedit (plugins, state, prefs) I didn't find any value or a key concerning this problem
4. saw this workaround but it doesn't solve the UI problem.

I didn't try snap because I prefer it to stick with PPA (I generally use snap for only for "special" app)

EDIT (17/11/18):

1. My file manager is Nemo 3.9.0 and to prevent collisions I've removed Nautilus which comes default with Ubuntu.
2. I use Communitheme and Suru as the applications and icons appearance themes respectively

Any suggestions will be welcomed

Thanks

I had a dual-boot system with Windows 10 and Ubuntu 18.04.1 and I wanted to try Kubuntu 18.04.1 as well.

So I've edited my partition table, created ~12GB for that cause, installed Kubuntu on it and my partition table looks as follows (I've also created a separate partition for my home folder in Ubuntu)

What followed is that Kubuntu's GRUB override Ubuntu's, it showed all the 3 boot options but from that point on I couldn't restart and boot from Windows to either Linux OSs or from one Linux OS to another without getting this error message

fsck.ext4 Superblock checksum does not match superblock while trying to open /dev/sdaX

As you can see in every reboot I get the (initrmfs) menu and have to manually fix the filesystem using this command e2fsck -pb 32768 /dev/sdaX enter reboot and go to the specific entry (mounted sda) that I fixed previously.

It looks like all 3 ext4 linux partitions Kubuntu, Root(ubuntu), Home(ubuntu) share the same superblock

roey@hpx360-13:~$ sudo fdisk -l|grep Linux|grep -Ev 'swap'
[sudo] password for roey: 
/dev/sda6  360892416 385613823  24721408  11.8G Linux filesystem
/dev/sda7  424935424 483340287  58404864  27.9G Linux filesystem
/dev/sda9  385613824 424935423  39321600  18.8G Linux filesystem
roey@hpx360-13:~$ sudo dumpe2fs /dev/sda6 | grep superblock
dumpe2fs 1.44.1 (24-Mar-2018)
  Primary superblock at 0, Group descriptors at 1-2
  Backup superblock at 32768, Group descriptors at 32769-32770
  Backup superblock at 98304, Group descriptors at 98305-98306
  Backup superblock at 163840, Group descriptors at 163841-163842
  Backup superblock at 229376, Group descriptors at 229377-229378
  Backup superblock at 294912, Group descriptors at 294913-294914
  Backup superblock at 819200, Group descriptors at 819201-819202
  Backup superblock at 884736, Group descriptors at 884737-884738
  Backup superblock at 1605632, Group descriptors at 1605633-1605634
  Backup superblock at 2654208, Group descriptors at 2654209-2654210
roey@hpx360-13:~$ sudo dumpe2fs /dev/sda7 | grep superblock
dumpe2fs 1.44.1 (24-Mar-2018)
  Primary superblock at 0, Group descriptors at 1-2
  Backup superblock at 32768, Group descriptors at 32769-32770
  Backup superblock at 98304, Group descriptors at 98305-98306
  Backup superblock at 163840, Group descriptors at 163841-163842
  Backup superblock at 229376, Group descriptors at 229377-229378
  Backup superblock at 294912, Group descriptors at 294913-294914
  Backup superblock at 819200, Group descriptors at 819201-819202
  Backup superblock at 884736, Group descriptors at 884737-884738
  Backup superblock at 1605632, Group descriptors at 1605633-1605634
  Backup superblock at 2654208, Group descriptors at 2654209-2654210
  Backup superblock at 4096000, Group descriptors at 4096001-4096002
roey@hpx360-13:~$ sudo dumpe2fs /dev/sda9 | grep superblock
dumpe2fs 1.44.1 (24-Mar-2018)
  Primary superblock at 0, Group descriptors at 1-3
  Backup superblock at 32768, Group descriptors at 32769-32771
  Backup superblock at 98304, Group descriptors at 98305-98307
  Backup superblock at 163840, Group descriptors at 163841-163843
  Backup superblock at 229376, Group descriptors at 229377-229379
  Backup superblock at 294912, Group descriptors at 294913-294915
  Backup superblock at 819200, Group descriptors at 819201-819203
  Backup superblock at 884736, Group descriptors at 884737-884739
  Backup superblock at 1605632, Group descriptors at 1605633-1605635
  Backup superblock at 2654208, Group descriptors at 2654209-2654211
  Backup superblock at 4096000, Group descriptors at 4096001-4096003

Which might cause a checksum error but on the other hand there was no problem with a dual-boot.

What is the problem here and how can I fix it ?

Thanks

This problem is going on for several months.

When you try to run a GUI program it suddenly exits the session gets back to the login screen where I get this notification (bubble for several seconds) at the top of screen:

Automatic suspend. Computer will be suspend very soon due to inactivity.

I've disabled automatic suspend in the power settings.

When returning from hibernation and again trying to run a GUI program the exit symptom is a strange string of "@^"s in top left of the brownish pre-login screen , then the PC becomes unresponsive (no tty's whatsoever) and the only way of closing it is hard reset

My machine is an HP Spectre x360 with dual-boot (with Windows 10 using GRUB) I use communitheme on GNOME shell v3.28.2

It doesn't happen immediately or when running a specific program, so I cannot "produce" this error at will. I can run 10 or more programs for an hour or so until it strikes.

Where should I start to debugging this problem ?

Help is much needed here

Thanks

I've installed communtiheme on my Ubuntu 18.04 GNOME Shell v3.28.1.

I cannot enter folders (file opening does work) and the default icons only appear on the desktop but don't exist inside.

Even if I create a folder and it appears on the terminal I cannot enter her via Nautilus (GNOME explorer).

What is the problem here ?

Thanks

I have HP Spectre 13 x360 Laptop I cannot see or control my fan speed

(lm-sensors is installed)

As I can in Windows using a program called SpeedFan.

Here is the it's execution log:

Win9x:NO  64Bit:YES  GiveIO:NO  SpeedFan:YES 
I/O properly initialized
Linked ISA BUS at $0290
Scanning ISA BUS at $0290...
SuperIO Chip=SCH5027D
Found AXNS381E-256GM-B on AdvSMART
INFO : SCSI DISABLED by user or because iaStorA.sys is installed
Found Hewlett-Packard HP Spectre x360 Convertible 13
Found ACPI temperature
Found Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
End of detection
Loaded 0 events

I followed This tutorial and it didn't help When I enter sudo pwmconfig I get this error message/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed My AMI BIOS doesn't show any thermal or sensory info. It's "Fan Always on" is Disabled.

Here is the output of sudo sensors-detect

# sensors-detect revision 6284 (2015-05-31 14:00:33 +0200)
# System: Hewlett-Packard HP Spectre x360 Convertible 13 (laptop)
# Board: Hewlett-Packard 802D
# Kernel: 4.15.0-23-generic x86_64
# Processor: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (6/61/4)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               Yes
Found unknown chip with ID 0x8987
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): y
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): y
Found unknown SMBus adapter 8086:9ca2 at 0000:00:1f.3.
Sorry, no supported PCI bus adapters found.

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): y
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client at address 0x1c can not be probed - unload all client drivers first!

Next adapter: i915 gmbus vga (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpb (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpd (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: DPDDC-A (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: DPDDC-C (i2c-7)
Do you want to scan it? (yes/NO/selectively): y


Now follows a summary of the probes I have just done.
Just press ENTER to continue: 

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Is it a missing ACPI linux driver for this motherboard ?

Does the on-board GPU have thermal info also ?

Thank you

I have 8GB RAM so I crated a SWAP partition of 8GB using this https://help.ubuntu.com/community/SwapFaq manual.

Here is my last hibernation that worked pm-suspend.log

I have a dual-boot machine with Windows.

Thank you

I'm trying to get Ubuntu to enable Wifi automatically on boot currently I get "Airplane mode" on boot and I have to manually turn on the Wireless adapter

I've created /etc/rc.local (which doesn't exist in Ubuntu 17.10)

printf '%s\n' '#!/bin/bash' 'exit 0' | sudo tee -a /etc/rc.local
sudo chmod +x /etc/rc.local
sudo reboot

and add this commands

sudo ifconfig wlo1 up
sudo service network-manager restart

wlo1 is my wireless adapter connection name

When I turn off my wireless connection I automatically get the Airplane mode (which has a dedicated shortcut in my keyboard FN+F12 that doesn't work) and when I run the the command sudo ifconfig wlo1 up I get this error message SIOCSIFFLAGS: Operation not possible due to RF-kill

There is no option to enable/disable the the Airplane switch via a HW setting in my BIOS as suggested Here

Is there a way to automatically turn on my wireless network upon boot ?

Similar question have been previously asked here with no answers

Hi,

I have an HP Spectre x360 13 4003dx with a dual boot (using GRUB) of Ubuntu 17.04 x64 and Windows 10 Pro x64.

On a first boot (after shutdown) either to Windows or Ubuntu the sound works on both of them , but when I restart back to GRUB and boot to a different OS (e.g Windows) the sound doesn't work then boot back to the same initial OS sound doesn't work either. bottom line if you switch OS's with GRUB it shuts down the sound.

Why? Is there a fix?

Many Thanks

Roey

I'm stuck in a login loop Ubuntu 17.04. When I go to tty1 and type chown username:roey .Xauthority taken from Ubuntu gets stuck in a login loop

It says that my user doesn't exist.

What is the problem? How can I log back in to Ubuntu-Gnome?