Im using Ubuntu 22.04 LTS Intel cpu I7 9th gen NVIDIA gpu but i disabled it My problem is that the Picture in Picture mode isnt sticky if i press anything it vanishes fro… (read more)
Im using Ubuntu 22.04 LTS Intel cpu I7 9th gen NVIDIA gpu but i disabled it My problem is that the Picture in Picture mode isnt sticky if i press anything it vanishes from view.
I woke up this morning to my home directory having been remounted as read-only (it has its own dedicated hard drive at /dev/sdd1). I ran e2fsck and things looked good, so… (read more)
I woke up this morning to my home directory having been remounted as read-only (it has its own dedicated hard drive at /dev/sdd1). I ran e2fsck and things looked good, so I restarted and things were fine again.
However, whenever I open Firefox, it hangs for about 1 full minute before it goes haywire and renders the entire system essentially unusable since being able to access my home directory is vital. The following is visible in dmesg:
[ 2710.362946] Aborting journal on device sdd1-8. [ 2710.363000] EXT4-fs warning (device sdd1): ext4_end_bio:343: I/O error 5 writing to inode 10520593 starting block 44134769) [ 2710.363008] Buffer I/O error on device sdd1, logical block 44134513 [ 2710.363041] EXT4-fs error (device sdd1): ext4_journal_check_start:84: comm glean.dispatche: Detected aborted journal [ 2710.363048] EXT4-fs warning (device sdd1): ext4_dx_find_entry:1795: inode #9718667: lblock 2: comm Renderer: error -5 reading directory block [ 2710.363076] EXT4-fs warning (device sdd1): htree_dirblock_to_tree:1082: inode #9701223: lblock 1: comm Cache2 I/O: error -5 reading directory block [ 2710.800016] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm BgIOThr~ool #12: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.812447] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm Backgro~Pool #1: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.884557] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9976467: comm Backgro~Pool #1: No space for directory leaf checksum. Please run e2fsck -D. [ 2710.980923] EXT4-fs (sdd1): Remounting filesystem read-only [ 2711.049635] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D. [ 2711.152739] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D. [ 2711.152757] EXT4-fs warning (device sdd1): ext4_dirblock_csum_verify:405: inode #9701223: comm Cache2 I/O: No space for directory leaf checksum. Please run e2fsck -D.
All other programs that I use daily do not cause this issue. No clue what to do here. LibreWolf works fine - that's what I'm using now that Firefox breaks everything and basically forces me to restart if I want to use my computer normally.
This pops up every few hours. Sometimes it pops up invisible but steals focus from the main window. How can this be disabled? I tried all methods that have been mentione… (read more)
This pops up every few hours. Sometimes it pops up invisible but steals focus from the main window. How can this be disabled?
I tried all methods that have been mentioned everywhere on the Internet, including policy.json, Group Policy on Windows, etc. Nothing disables this nagging yet.
Versions: Firefox: 127.0 (64-bit) Linux: Ubuntu 22.04.4 LTS Description: After some time, and (under unknown conditions), the input delay will shoot way up. Like 20-30 s… (read more)
Versions: Firefox: 127.0 (64-bit) Linux: Ubuntu 22.04.4 LTS
Description: After some time, and (under unknown conditions), the input delay will shoot way up. Like 20-30 seconds.
Strangely enough, this only applies to keyboard inputs. I can change my tab with my mouse, I can click on things, no issues there. But any keyboard interaction is hugely delayed.
This does not fix itself until I close my browser and restart it. Closing the browser is always broken here too, if I close the browser with the [X] exit button, I then need to kill the process because it just hangs. It blanks out the contents of each tab like it's preparing to close them, but it just doesn't ever complete the task without a manual kill.
CPU usage and memory usage are relatively low; significantly below my system's limits.
I've already tried this suggested fix, to no avail.
The frequency of this is only about once a week at most, usually once a month, so it's not a huge issue, but I'm just worried about this occurring during a critical meeting or something later. Having this impending restart needed is kind of worrying for critical usage times.
Hello I am using firefox 126.0.1 (64-bit) version of firefox on a linux system (kernel 6.6). Firefox is closing the main window abruptly (or crashing). Wanted to get i… (read more)
Hello
I am using firefox 126.0.1 (64-bit) version of firefox on a linux system (kernel 6.6). Firefox is closing the main window abruptly (or crashing).
Wanted to get information on the crash, but when I navigated to the about:crashes page, it return a page with title "invalid URL" and the page says "Hmm. That address doesn’t look right."
Is there a way to get to the crash data/information?
Kind Regards Riza
