Sync Updates for Week 22, 2024

snowee

TraceyC
Thanks.

Can I check what is the command to unmount the boot partition?

silke

snowee There's no need to unmount! This is because the system might expect it to be mounted for various reasons.

penny-farthing

silke
silke

Thank you for your explanations.

catfishsushi

I am seeing this, but not sure what it means.
any ideas or possible advise?

Staudey

catfishsushi Sounds like your EFI partition is too small.

Harvey

Cherry-picked plasma-workspace 6.0.5.1 (Thanks @Justin)

presianbg

I've skipped Week 21 updated and just installed Week 22 updates, so far everything works flawlessly... except spotify-qt:

[1]    5300 segmentation fault (core dumped)  spotify-qt

Am I the only one having this issue ?

Harvey

presianbg Am I the only one having this issue ?

I can not reproduce so possibly.

Staudey

presianbg Unfortunately I also can't reproduce this (on Budgie). Is there anything else printed to the terminal? Do you perhaps see additional information in journalctl (e.g. by running sudo journalctl -f and then launching spotify-qt in parallel)

brent

presianbg it's a silly question but did you reboot after you did the updates?

presianbg

Staudey

Process 20503 (spotify-qt) of user 1000 dumped core.

Stack trace of thread 20503:
#0  0x00007fd7bf94ca38 _ZN7QObject11deleteLaterEv (libQt6Core.so.6 + 0x34ca38)
#1  0x000055affefaac57 n/a (spotify-qt + 0x15ec57)
#2  0x000055affefa9a77 n/a (spotify-qt + 0x15da77)
#3  0x000055affefa8b00 n/a (spotify-qt + 0x15cb00)
#4  0x00007fd7bf04030e n/a (libc.so.6 + 0x2a30e)
#5  0x00007fd7bf0403c9 __libc_start_main (libc.so.6 + 0x2a3c9)
#6  0x000055affeefac55 n/a (spotify-qt + 0xaec55)

Stack trace of thread 20506:
#0  0x00007fd7bf12444d syscall (libc.so.6 + 0x10e44d)
#1  0x00007fd7bf57436c g_cond_wait (libglib-2.0.so.0 + 0xba36c)
#2  0x00007fd7bf4dc72c n/a (libglib-2.0.so.0 + 0x2272c)
#3  0x00007fd7bf545507 n/a (libglib-2.0.so.0 + 0x8b507)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20505:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7be550773 n/a (libxcb.so.1 + 0xc773)
#2  0x00007fd7be5531eb xcb_wait_for_event (libxcb.so.1 + 0xf1eb)
#3  0x00007fd7bb3c594f n/a (libQt6XcbQpa.so.6 + 0x6594f)
#4  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20511:
#0  0x00007fd7bf51548a n/a (libglib-2.0.so.0 + 0x5b48a)
#1  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#2  0x00007fd7bfbebca2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5ebca2)
#3  0x00007fd7bf9021ba _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3021ba)
#4  0x00007fd7bfa160d6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x4160d6)
#5  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#6  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#7  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20512:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7b83a03a6 n/a (libdconfsettings.so + 0xb3a6)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20507:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7bf515d42 n/a (libglib-2.0.so.0 + 0x5bd42)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20508:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515fd7 g_main_loop_run (libglib-2.0.so.0 + 0x5bfd7)
#3  0x00007fd7bbc82f10 n/a (libgio-2.0.so.0 + 0x121f10)
#4  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#5  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#6  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20513:
#0  0x00007fd7bf12913b __socket (libc.so.6 + 0x11313b)
#1  0x00007fd7bf13afa5 n/a (libc.so.6 + 0x124fa5)
#2  0x00007fd7bf1555e6 getaddrinfo (libc.so.6 + 0x13f5e6)
#3  0x00007fd7c0712846 n/a (libQt6Network.so.6 + 0xdc846)
#4  0x00007fd7c07bd1d8 n/a (libQt6Network.so.6 + 0x1871d8)
#5  0x00007fd7c071377c n/a (libQt6Network.so.6 + 0xdd77c)
#6  0x00007fd7bfac6d52 n/a (libQt6Core.so.6 + 0x4c6d52)
#7  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#8  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#9  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20510:
#0  0x00007fd7bf12444d syscall (libc.so.6 + 0x10e44d)
#1  0x00007fd7bf57436c g_cond_wait (libglib-2.0.so.0 + 0xba36c)
#2  0x00007fd7bf4dc72c n/a (libglib-2.0.so.0 + 0x2272c)
#3  0x00007fd7bf4dcbe9 g_async_queue_pop (libglib-2.0.so.0 + 0x22be9)
#4  0x00007fd7bb22aa75 n/a (libpangoft2-1.0.so.0 + 0xda75)
#5  0x00007fd7bf544d18 n/a (libglib-2.0.so.0 + 0x8ad18)
#6  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#7  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)

Stack trace of thread 20504:
#0  0x00007fd7bf11997f __poll (libc.so.6 + 0x10397f)
#1  0x00007fd7bf5155c7 n/a (libglib-2.0.so.0 + 0x5b5c7)
#2  0x00007fd7bf515cf1 g_main_context_iteration (libglib-2.0.so.0 + 0x5bcf1)
#3  0x00007fd7bfbebca2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x5ebca2)
#4  0x00007fd7bf9021ba _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3021ba)
#5  0x00007fd7bfa160d6 _ZN7QThread4execEv (libQt6Core.so.6 + 0x4160d6)
#6  0x00007fd7c10cb92a n/a (libQt6DBus.so.6 + 0x4e92a)
#7  0x00007fd7bfabf3cf n/a (libQt6Core.so.6 + 0x4bf3cf)
#8  0x00007fd7bf0af27e n/a (libc.so.6 + 0x9927e)
#9  0x00007fd7bf126c9c n/a (libc.so.6 + 0x110c9c)
ELF object binary architecture: AMD x86-64

TraceyC

presianbg

Please open an issue on our bug tracker for this. By opening an issue, it will allow our developers to look into it and keep track of progress. Thanks.

dassuan

Since week 22 update all three versions of the firefly iota wallet (firefly-iota-desktop-2.0.10.AppImage; firefly-shimmer-desktop-2.1.15; firefly-canary-desktop-3.0.1.AppImage) crash on start. The apps work normal in Windows Virtual Machine. I think the AppImages are Electron based . Budgie Desktop. Any ideas?

presianbg

TraceyC I will do for sure if I can't fix it by myself in next few days.
The reason I asked was if anybody else is having the same defect, if not... I believe it's something with my setup.

davidjharder

presianbg I bumped spotify-qt and there were some ABI changes with qt6.

presianbg

davidjharder honestly... I'm not sure what you mean 🙂

WetGeek

I have to admit that I haven't carefully read all 43 posts that are here, but has there been any Bluetooth trouble mentioned so far? Here's why I ask ...

Today I received my new Arteck multi-device mouse from Amazon. It's a near duplicate of the Logitech Triathlon mouse that I've used for years, except that it has multiple DPI settings, it's rechargeable via USB-C, and costs about 1/3 what I paid for the Triathlon.

My problem is, I can't make it connect with my Plasma laptop (on which I've used the Triathlon mouse for years) as Device 1. It pairs and is trusted, but cannot connect. It connects and works fine as Device 2 with my Windows 10 media machine that controls my TV, and likewise as Device 3 setting with my Samsung smartphone. It just won't connect with my Solus laptop.

After trying to make that work for a while, I decided to give up for now and just go back to the Triathlon mouse until I can figure this issue out. It took me 4 tries to get that mouse - the one I've used for years - connected. Of course, I had the laptop "forget" the mouse in between attempts. And I rebooted once. The fourth try was successful.

The laptop is a DELL Latitude, all Intel inside, and has never given me a problem like this before. Any ideas?

Axios

WetGeek Sorry you are having constant bluetooth issues.

brent

WetGeek The laptop is a DELL Latitude, all Intel inside, and has never given me a problem like this before. Any ideas?

you have all 4 solus de's. maybe two Plasma machines? you have sparky somewhere. maybe ultramarine still?
maybe start with where bluetooth works and where does bluetooth not work and ascertain differences. I know you have done this but my suggestion is just taking it all to the lowest common denominator I hope.

I mean if you have success pairing with some OS's and not others that still is huge as far as variables: hardware, software, dongles, compatibilities, compatibility of the peripherals with the OS, compatibility of the peripherals with the software and hardware now I am thinking needle/haystack. make problem smaller..

ReillyBrogan

WetGeek Have you considered the possibility that your constant bluetooth problems are symptoms that your environment has a lot of 2.4Ghz wireless interference?

BuzzPCSOS

WetGeek Do other Bluetooth devices work with your Plasma laptop? This sounds like the same issue that I had when I got a new Bluetooth Mouse. The Bluetooth on my laptop was just too old to connect to my new device. A little research will quickly reveal if your mouse should connect to the laptop.
Edit: From what I can see it was BLE (Bluetooth Low Energy) technology that my old Dell Latitude could not deal with along with a requirement for Bluetooth 4.0 or above, when my machine only sported 3.0.
I could not find an easy way to interrogate Bluetooth version on Linux so ended up running my VirtualBox Windows install and using a neat little tool by Sordum to tell me the version that was installed.

WetGeek

ReillyBrogan your environment has a lot of 2.4Ghz wireless interference?

No, that never occurred to me. The reason I started using the multi-device mouse and keyboard years ago is so that I wouldn't need other 2.4 GHz single-device peripherals and their dongles. And, as I mentioned, the Bluetooth versions've worked for years. And the keyboard is still working fine today (that's what I'm using right now.) It's something to think about, though.

Is there a way to clean the Bluetooth system to make sure that there's no stray config file somewhere that's causing my problems? Just going to Settings and telling the laptop to "forget" that device, and then reconnecting it, isn't helping. In the past I would have expected that to work. By the way, bluedevilglobalrc has re-appeared in my .config, after having been removed recently. It gets replaced automatically, apparently. I was under the impression it's an artifact of an ancient problem. Maybe a regression?

The only 2.4 GHz device in use now is the mouse I'm using because I can't get either of the Bluetooth mouses to connect now. And both the old Logitech mouse and the new Arteck mouse still gladly connect and work with the media computer across the room and the smartphone next to the laptop. Just not the Plasma laptop.

Axios

WetGeek I would disable the WiFi on the laptop and try it

Just for info 2.4g WiFi can cause Bluetooth issues rare but can usually with connecting

« Previous Page Next Page »