[opencl]

F29 included bugs such as:

-Cron jobs don't run

-Package manager creates multi-gigabyte log files

-Package manager crashes on systems upgraded from previous releases

-GNOME crashes when switching to a virtual terminal and back

-Default bluetooth config doesn't work for some devices

-Ethernet runs at 10mbps instead of 1gbps

https://fedoraproject.org/wiki/Common_F29_bugs

[passthejoe]

I think the Fedora community is pretty responsive when it comes to fixing bugs that are under their control, and the developers dogfood the desktop enough that they care about these things.

Also, Fedora gets new kernels all the time, and that often takes care of problems that sometimes persist in more "stable" distributions.

I have one mid-level issue per release, I figure, and it is usually patched within a couple of weeks.

I did have a bad experience upgrading from F27-29, so I've only been on F29 for maybe a month or so, and it has been smooth so far. I will probably wait a few weeks to a month to upgrade to F30 to increase my chances of a trouble-free transition.

[pizza234]

> -Default bluetooth config doesn't work for some devices

Bluetooth (Bluez) is a trainwreck on any distro; even the version shipped with Ubuntu 18.04 (LTS!) is broken.

[opencl]

This is true, F29 just happened to ship with an extra-broken default config.

Though I have yet to see any BT implementation that isn't at least a little bit broken. Nobody actually conforms to the spec so you have to attempt to make your noncomforance work with the widest possible variety of other vendors' nonconformance and you'll always find device combinations that just don't work together.

[dullgiulio]

Not my experience. Or, if anything, bluetooth on Ubuntu works much better than on my Windows laptop (Lenovo).

[pizza234]

Certainly YMMV applies, however, it's important to distinguish the nature of the two cases.

Broken BT support in a Windows context generally means poor drivers for a given device - at least the Windows 10, which is almost 4 years old, has a stable BT stack. Therefore, BT problems are of particular (per-device) nature.

In Ubuntu, the problem is systemic, due to (even ignoring how terrible the BT protocol is) both Bluez's (alleged) terrible engineering practices, and Ubuntu's utter carelessness of the area. In this terms, BT problems are of universal nature.

For example, the 18.04 Pulseaudio/BT configuration is broken by default - see https://askubuntu.com/a/1050172.

This is not an exception; the Pulseaudio/BT configuration has been broken in a way or another since... forever. Very evidently, the Ubuntu devs prefer to ship a broken-but-up-to-date BT stack, than a working-but-old one.

For a more historical perspective of the Ubuntu/Bluez trainwreck, see http://www.bennybottema.com/2010/08/08/how-ubuntus-broken-bl.... Summary: "Bluez is a bunch of cowboy coders is why".

[phkahler]

Lot of dnf issues on that list. I find using dnf more reliable than using the gui software installer. That program is really buggy.

[soulofmischief]

I have had my own share of bugs, all virt-related, but I have experienced none of the bugs you've described across more than a dozen systems.

dnf could definitely work on keeping its generated garbage down to a more reasonable size, though.