Is there a way to predict when the next release will be out? I read somewhere that it has to do with number of bugs remaining in the testing branch . Could someone please explain how this works and when the next release will happen based on what variables?

I've downloaded and installed Elementary OS in my laptop, but something weird is happening with me. I made an USB Flash Drive installation, using UNetbootin. I was able to test it (like a Live-CD) and everything went just fine. So I decided to install it. When I installed it, these bugs started to happen: - The mouse pointer takes ~30 seconds to appear (i'm still able to click things), and when it does, all I see is an "X" on my screen. Perhaps this is the standard mouse pointer, right? - When I try to close or maximize a window, the top bar with these options just doesn't exists. I'm able to drag the window across the screen, but when I double-click (hoping the window will maximize), the system stops working for a while, and then the window crashes. - I've tested Elementary OS before installing. When I click something in the Plank, a small animation starts playing. This doesn't happen in the installed version. There are other things happening, but these are the "main bugs" I can remember now. I tried to do these: - I tried reinstalling the system. Still the same. - I tried to update the system. 100mb of updates, and the bugs didn't go away. - A friend of mine asked me to type "sudo apt-get update" and "sudo-apt get upgrade" in the terminal. Still the same. Since I've always been a Windows user, I don't know why this is happening and neither I know how can I fix this. My laptop config is: Dell Inspiron 14R (5420), Core i7 3612QM 2.10GHz, 8GB RAM, nVidia 630GT 1GB and 1TB storage. Any thoughts?

When I'm turning my Debian Stretch (9) off, chances are that I see something like: So a have a few questions: 1) It seems like a bug that's not been solved yet (it's been around for a few years). By "bug" I mean Linux should turn off faster than Windows; if it doesn't, there's a bug. 2) Since this bug seems hard to isolate and solve, maybe a "Esc to cancel" would solve a big part of the problem. 3) I have programming experience, but not with Linux Kernel and such. Am I advised to try to include "Esc to cancel" myself? If so, which file should I change? May I compile only this file, or something more? EDIT Contents of /etc/gdm3/daemon.conf # GDM configuration storage # # See /usr/share/gdm/gdm.schemas for a list of available options. [daemon] # Uncoment the line below to force the login screen to use Xorg #WaylandEnable=false # Enabling automatic login # AutomaticLoginEnable = true # AutomaticLogin = user1 # Enabling timed login # TimedLoginEnable = true # TimedLogin = user1 # TimedLoginDelay = 10 [security] [xdmcp] [chooser] [debug] # Uncomment the line below to turn on debugging # More verbose logs # Additionally lets the X server dump core if it crashes #Enable=true

## Soft Lockup dmesg reports in my laptop, since quite some time now, NMI watchdog: BUG: soft lockup *every time* I try to use updatedb or firefox. Samples of what is reported posted at https://github.com/zfsonlinux/zfs/issues/4536#issuecomment-280894134 . **Related questions** are - https://unix.stackexchange.com/q/303062/13011 - https://unix.stackexchange.com/q/216959/13011 - https://unix.stackexchange.com/q/282316/13011 I have also read/commented at - https://github.com/zfsonlinux/zfs/issues/4536 ## Question How can I detect whether it's a hardware issue or, as I think, confirm it's an issue related to the kernel/software? --- ## Details ### Linux Distribution Funtoo-Linux , a rolling distribution ### Kernels I have (at least) observed the "BUG" while using the following kernel(s) versions: pf - 4.11_p4-pf - 4.8_p8 - 4.5_p4 ck - 4.12.7-ck debian - lts-4.9.30 - 4.8.x - 4.7.8 ### Configuration I use a custom configuration to compile the kernel. It's mostly the same configuration I use(d) for long time, when there was no "soft lockup" problem or whatsoever related to a "watchdog". I can copy-paste or link the configuration file. However, two important settings I have found else to be "required" CONFIG_KALLSYMS=y CONFIG_PREEMPT_NONE=y ### ZFS I observed the "BUG" while using ZoL versions - 0.6.5.11 - 0.6.5.10 - 0.6.5.9 - 0.6.5.8 - 0.6.5.3

I'm using the following system: - OS: Linux Mint 22.1 - Kernel: Linux 6.8.0-59-generic. - CPU: Ryzen 5 1600 - GPU: GT430C - Motherboard: B450M-A II - PSU: Corsair RM850 - BIOS 3002 - Microcode 0x08001138 From time to time, the PC beeps once and reboots. With BIOS 4609 and 4410, the PC could hang or reboot anywhere between 30 and 170 minutes. I'm using mdadm to create a RAID 6 and Samba to use the PC as NAS. The next time after it hung, I found this in the journal.

watchdog: BUG: soft lockup - CPU#2 stuck for 100s! [kcompactd0:100]
kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 3855s! [gdbus:2699]

I would appreciate any info about this. Thanks. I read this [thread](https://forums.debian.net/viewtopic.php?t=148561) and seems like the first Ryzen generation/family has some issues, at least at that time. I wonder if this was solved in the current kernel?

While [pondering whether IEEE 1003.1-2017 forbids race-condition safe ln -f](https://unix.stackexchange.com/questions/794236/idiomatic-way-of-generating-a-unique-filename/794239#comment1526091_794239) , it occurred to me: Even if this is really an unfortunate definition (which GNU coreutils' ln thankfully ignores), I would have no way to say "hey, dear standardizers, next iteration, maybe don't specify this broken thing, and instead demand this safe thing, or at least don't prohibit safe implementation". How does the evolution of the POSIX / IEEE 1003.1 standard actually happen? How can the interested public participate, if at all?

In Ubuntu 24.10 systemd-resolved often goes comatose and stops resolving everything. The following messages are logged:

Apr 21 12:50:27 localhost systemd-resolved: [🡕] DNSSEC validation failed for question optimizationguide-pa.googleapis.com IN DS: failed-auxiliary
Apr 21 12:50:27 localhost systemd-resolved: [🡕] DNSSEC validation failed for question optimizationguide-pa.googleapis.com IN SOA: failed-auxiliary
Apr 21 12:50:27 localhost systemd-resolved: [🡕] DNSSEC validation failed for question optimizationguide-pa.googleapis.com IN A: failed-auxiliary
Apr 21 12:50:27 localhost systemd-resolved: [🡕] DNSSEC validation failed for question optimizationguide-pa.googleapis.com IN AAAA: failed-auxiliary

The bug is known however still not fixed in this version of Ubuntu: https://github.com/systemd/systemd/issues/34896

I recently installed Debian on a fresh system with a new SSD, but it has stopped being usable. Now, I can only reach the login screen, which is 50% white. The screen flickers to fully white when I move the mouse, and upon login, the screen goes completely black (no signal to the monitor). I can access the terminal but have no other control. I am using an old Radeon card, an RX 460, but also have an Nvidia GTX 970 installed.

Until today, when I closed any LibreOffice application (e.g. Writer, Calc, Draw, Impress, etc.) in Linux Mint, the expected happened: LibreOffice would close. Now, suddenly, when I close any LibreOffice application, the LibreOffice file picker (AKA the LibreOffice loader/launcher) is displayed. LibreOffice did not have any recent updates. What caused this, and how do I fix this?

I am using archlinux and after last update, when i have an heavy python script running via cli and some opened page in firefox, I get the GUI frozen and I have to reboot the system.
I don't know how/where to start this is the output of jourtanctl -b -1, last line show the error kernel: wlp6s0: AP 98:da:c4:b7:0d:78 changed bandwidth, new used config is 2412.000 MHz, width 2 (2422.000/0 MHz) systemd: drkonqi-coredump-pickup.service: Service reached runtime time limit. Stopping. systemd: drkonqi-coredump-pickup.service: Failed with result 'timeout'. systemd: drkonqi-coredump-pickup.service: Consumed 39ms CPU time, 138.9M memory peak. kscreenlocker_greet: qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile plasmashell: file:///usr/share/plasma/plasmoids/org.kde.plasma.keyboardindicator/contents/ui/main.qml:61:13: Unable to assign [undefined] to bool rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. rtkit-daemon: Supervising 9 threads of 6 processes of 1 users. kernel: i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out kernel: i915 0000:00:02.0: [drm] kwin_wayland context reset due to GPU hang kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:859ffffb, in kwin_wayland kernel: sched: RT throttling activated kwin_wayland: kwin_wayland_drm: Pageflip timed out! This is a kernel bug

A month ago, a regression happened in Debian 12 [that caused dead keys not to work for a while](https://unix.stackexchange.com/questions/776059/cant-type-%c3%aa-e-on-my-french-keyboard-anymore-dead-keys-and-ctrl-shift-u-a) . It was a [bug](https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1970288.html) and they corrected it. Things came back mostly to normal now, except for ` + A that doesn't type __À__ anymore. Today, it produces:

`A

(if you have a VM with a previous Debian 12 version before May, or a Debian 11, you can check that it was working once: you got the À) I would like to warn the Debian team that the resolution of the bug #1070745 isn't finished. Because I'm not sure they are aware of this. But I don't know the steps to follow to add such an entry to this issue. Just send an e-mail? To which destination, with what title and what formalism? Can you give me clues to do my report correctly?

How to change the software package an issue is filed under in the Debian bug tracker? The help page has these instructions: > In case you need to write a message to the bug and also manipulate the bug's metadata, the commands can also be included in the mail to nnn@bugs.debian.org. Do this by starting the mail with the commands prefixed by Control: . Another common way is to send a copy of the mail to control@bugs.debian.org and start the mail with commands terminated by thanks. and then under Commands available: >reassign bugnumber package [ version ] I tried: * Control: reassign -1 kde-plasma-desktop [5:142] at the start of mail reply to the bug report with control at bugs.debian.org in the CC (I think I should have used nnn@ here; all below went to the same control email) * Control: reassign 1019438 kde-plasma-desktop [ 5:142 ] * Control: reassign 1019438 src:kde-plasma-desktop [ 5:142 ] (thanks in the line below) * Control: reassign 1019438 kde-plasma-desktop (thanks in the line below) * reassign 1019438 kde-plasma-desktop [ 5:142 ] (thanks in the line below) I could not find a full example anywhere so I'm asking here.

Create a directory ~/test with abcdefghijklmnopqrstuvwxyz and zyxwvutsrqponmlkjihgfedcba files in it. ls ~/test will list them using multi-column layout:

abcdefghijklmnopqrstuvwxyz	zyxwvutsrqponmlkjihgfedcba

Each filename is 26 characters long. But if you use Cyrillic letters, the maximum length of a filename for ls to use multi-column layout is limited to 17 characters. If any of your filenames is longer, the single-column layout will be used. Is it documented somewhere? Or is it just a bug?

abcdefghijklmnopqrstuvwxyz		абвгдеёжзийклмноп

abcdefghijklmnopqrstuvwxyz
абвгдеёжзийклмнопр

After an update/ upgrade on Debian 12 (weekly update), there is NO WiFi, files are not opening, unable to shutdown or sleep, and freezes when using **sudo**. The bug is fixed with a new release of kernel. But, I am NOT able to install the new kernel. 1. I downloaded the new kernel file to a flash drive using another laptop 2. Copied it to the freezing laptop 3. But on hitting the command:

$ sudo apt install ./linux-image-6.1.0-16-amd64_6.1.67-1_amd64.deb

terminal freezes without prompting for password. **EDIT**: Tried to edit $ nano /etc/default/grub # GRUB_DEFAULT=0 GRUB_DEFAULT="1>2" But it could not be saved since I did NOT use '**sudo**'. But, when I use *sudo* $ sudo nano /etc/default/grub It freezes without prompting for password (may be because of Network Manager issue) Any help?

I have a TP-Link UB500 Bluetooth 5 adapter which I use with a wireless keyboard and mouse on my Linux Mint machine. This adapter uses an RTL8761 chip. After a recent update Linux mint version update I found that the connection to both the mouse and keyboard would drop frequently, typically every few minutes. I managed to resolve the issue by installing the previous version of the firmware from https://cdn.kernel.org/pub/linux/kernel/firmware/ . I would like to report this issue but where can I do this?

GNU bash, version 3.2.48 has this bug; already version 3.2.57 does not. Make a file with 8000 identical lines (say each line says 1). Run split -a3 -p "1" on it (-p is a BSD split option which makes it split on the given pattern. For a file with just one 1 per line, you can do the same thing with a standard split by running split -a3 -b 1). And execute find . -name xaaa -exec echo {} + And after the expected output, you get find: fts_read: Invalid argument output to cerr. The same error occurs when xaaa is replaced by any set of files, and echo by any other command I've tried. The length of the filename doesn't matter. The directory of the files also doesn't matter. After some creating files elsewhere, the error is gone. However, when xaaa is replaced by xaa* (or any other wildcard that includes multiple files, at least one of which is near the beginning of the directory listing), then the error occurs again. At that point, no single file causes the error to appear. Replacing + with ; does avoid the error, but is not acceptable for my script. This problem has been occurring intermittently in other situations in my script, but by reducing it I was able to come up with a simple way of replicating it. I want the script to stop if an error occurs, but this just makes it stop very often. Any idea how to get around this? (e.g. retrieve an error code and ignore just this specific error). Mac OS version 10.8.5. Darwin Kernel Version 12.5.0.

I've been having this issue lately where whenever I hit Caps Lock or Print Screen, it works normally but also acts like I hit the lower brightness key. This only happens with these keys specifically, none of the rest of them are bugged like this. I'm not sure where to start with troubleshooting this. Is there a way I can remap these inputs to just be capslock and just be printscreen as normal instead of being this weird inconvenient macro? I should also note that this only happens on this laptop's built-in keyboard. When using a USB keyboard, neither key has this problem. I am running debian-stable 12 (bookworm) with the KDE Plasma desktop environment on an ASUS ProArt Studiobook laptop.

Red Hat Enterprise Linux 9 is no longer listed as a product under bugzilla at https://bugzilla.redhat.com/enter_bug.cgi?classification=Red%20Hat There are no onward links indicating the issuer tracker has moved, or where it has moved to. Google comes up with nothing. Anyone know where bugs are reported in Red Hat Enterprise Linux 9 in September 2023?

I had audio crackling in 2 different software at least (Chrome & Spotify) so I guessed it was system level issue. I searched and found a solution that worked for me and wanted to share it. Edit : Issue was on ubuntu 21.10 on latitude 5511

Login Failed.When I turn on my laptop I login to openSUSE Tumbleweed with same username and password, my screen shows message "login failed" I do't know how to fix it when i log in as root it work and can login to my desktop but My main User cannot.I'am newbie in linux can anyone help me please?I use desktop environment KDE Plasma.