digiwizkid's questions

I have connected my LG full HD monitor via VGA with ThinkPad L460 and I am not able to change its resolution any greater than 1024*768

xrandr
Screen 0: minimum 16 x 16, current 2390 x 1511, maximum 32767 x 32767
XWAYLAND0 connected 1366x768+0+743 (normal left inverted right x axis y axis) 310mm x 170mm
   1366x768      59.98*+
XWAYLAND1 connected 1024x768+1366+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1024x768      59.92*+

Graphics: Mesa Intel® HD Graphics 520 (SKL GT2)

OS: Ubuntu 20.04.3 LTS

How to resolve this issue?

After connecting my Bluetooth headset with the A2DP profile, it works fine most of the time.

But I have noticed a persistent issue when I use youtube/ facebook-

For the first few videos, the audio works fine, suddenly the audio stops working, but the headset is still connected, audio works only after disconnecting and reconnecting.

I am using Ubuntu 20.04.1 LTS with PulseAudio 13.99.1

After a couple of force shutdowns of Ubuntu 20.04, I am getting busybox prompt on boot from my 256GB M.2 SATA SSD(sdb). Booted from another HDD(sda) and Disks is showing the following error when trying to repair the SSD-

Error while repairing filesystem

Error repairing filesystem on /dev/sdb5: Process reported exit code 12: e2fsck 1.45.5 (07-Jan-2020)

e2fsck: unable to set superblock flags on /dev/sdb5 (udisks-error-quark, 0)

There are two petitions on this SSD namely, Root(sdb1) and Home(sdb5).

I am able to mount Root and browse but, not able to mount home.

Steps I followed so far-

# sudo fsck -f /dev/sdb

fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Found a dos partition table in /dev/sdb

Tried replacing alternate superblocks with e2fsck -b 32768 <device>

None of these worked.

Made a (partial)backup of Root with Backups, I have not tried to format and restore yet.

Is it possible to repair this SSD? What is the exact issue?

Edit:

~ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT

<removed snaps and loops>

sda      8:0    0 465.8G  0 disk
├─sda1   8:1    0 114.5G  0 part /
├─sda2   8:2    0     1K  0 part
├─sda5   8:5    0   124G  0 part /home
└─sda6   8:6    0 227.3G  0 part /run/timeshift/backup
sdb      8:16   0 238.5G  0 disk
├─sdb1   8:17   0  93.3G  0 part
├─sdb2   8:18   0     1K  0 part
└─sdb5   8:21   0 145.2G  0 part

~ sudo fdisk -l /dev/sdb
Disk /dev/sdb: 238.49 GiB, 256060514304 bytes, 500118192 sectors
Disk model: OSC M.2 256GB
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: 0x9c55915b

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sdb1            2048 195710975 195708928  93.3G 83 Linux
/dev/sdb2       195710976 500117503 304406528 145.2G  5 Extended
/dev/sdb5       195715072 500117503 304402432 145.2G 83 Linux

Edit 1:

~ sudo fsck -f /dev/sdb1
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sdb1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on /dev/sdb1


/dev/sdb1: ********** WARNING: Filesystem still has errors **********

➜  ~ sudo fsck -f /dev/sdb5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext4: Input/output error while trying to open /dev/sdb5

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

Thanks

I am not able to use my Bluetooth headset Mic as a mic input in my Ubuntu 20.04 LTS installation. I can use it as an Output device with profiles - High Fidelity Playback (A2DP Sink) and Headset Head Unit(HSP/ HFP) but in the Input section, only the Internal microphone - Built-in audio is showing.

In google meet in sound settings, it is appearing as Monitor of Infinity Glide 501, but the sound is not getting recorded.

Model: JBL Infinity Glide 501

Note it works flawlessly with mobile devices. What could be the reason? How to resolve this issue?

In my freshly installed Ubuntu 20.04 LTS, Ubuntu Software is not loading properly.

It is loading only Editor's Picks but nothing else. Installed tab is empty and search is not working as well. My internet connection is perfectly working and I am not using any firewall.

Everything was working fine till yesterday, now it is stuck on the POST screen while I am powering on or, restart.

It is working only if I press ESC or Enter button, which takes me to diagnostics screen and the rest of the startup works as expected. I am not getting any error or, any beep sound.

Model: Lenovo Thinkpad L460

OS: Ubuntu 16.04 LTS (Single boot only)

Thanks

Edit: Any multiple keypresses starting it normally. Enter key taking me to bios options, f12 to the boot selection menu.

While changing a directory ownership, accidentally I did

sudo chown subhadip / instead of sudo chown MyApp

After realizing my mistake, tried to fixed few permissions i.e., sudo etc. by sudo chown -R root / stopped operation as its wrong.

Now I am getting “The system is running in low-graphics mode” error, which I believe because of wrong permissions only.

I am able to login in console mode.

Please guide me.