Twinkle crashes with PCM error message #321
Comments
|
I use same configuration (pipewire), and have similar "silent" crashes. |
|
@urbanware-org Thank you very much for taking the time to provide so many details; this was quite helpful and very much appreciated! I think I know where the (ALSA) bug is located, but just to make sure, could you provide us with a backtrace? We have instructions on how to generate one on our Wiki; Fedora also has its own information on the subject. In addition:
Thanks in advance! |
fbriere
added
bug
external
|
For the record, here's where I think the bug is located (with another copy in
After some experimentation, it appears that the value assigned to |
|
@cyberbeat Do you get the same "failed assertion" message? If so, would you be able to generate a backtrace as I have explained in my previous comment? Thanks! |
@fbriere You're welcome, I'm always glad to help!
I'm currently not in office having a few days off, but I will be back at work on October, 16th and can create a backtrace then. |
Yes: Language name: "de" unluckily, I cannot find a core dump (although started from shell with |
|
Finally a backtrace: Using Btw most times I have this crash at the end of calls, and I often don't recognize that twinkle does not run anymore... |
Drat! I did not expect PipeWire to show up this early in the stack... Could you please generate another backtrace after installing the |
|
@urbanware-org Like in my reply to @cyberbeat above, I also suggest you install the |
fbriere
added
audio
and removed
external
|
I also recognized this, and wait for the next crash (if there is any, after my pipewire update to pipewire 0.3.80) |
|
Here is some more debuginfo: |
@fbriere All right, I have installed the additional packages this morning. Unfortunately, I can't provide a backtrace so far as Twinkle did not crash, yet. |
|
I hope the next time, I can also deliver debuginfo for pipewire-spa calls. |
|
So, Twinkle crashed once today and I can finally provide the backtrace. |
|
Now with all debug-info-packages (also pipewire libspa-support), using pipewire 0.3.82, libasound 1.2.6.1 @fbriere Could you estimate, if this is an alsa bug, or pipewire bug? |
Thanks! I have opened an issue on the PipeWire tracker. |
|
Should be fixed in the released |
|
Yes, I already use 0.3.84, and did not have any crash until now. Many thanks @fbriere ! |
|
I assume that the problem might also be solved for me as well then. However, I cannot verify this (yet) as I no longer receive updates for Fedora 37 after the release of version 39 and don't have the latter running so far. From this point of view, the issue could be closed, I guess, unless you explicitly want to wait for my confirmation. |
fbriere
added
the
external
Weird, your backtrace contains function names, but lacks argument values and line numbers. First time I've seen something like this. (scratches head) Still, it matches the one from @cyberbeat, and therefore was caused by the same PipeWire bug (now fixed). Now, may I assume this was with an outgoing call? (It's okay if you don't remember after all this time. 😄) From your initial description, it seems that incoming calls would cause Twinkle to crash when attempting to play the ringtone, which does not involve PipeWire at all according to your configuration. Would it be possible for you to post a backtrace of Twinkle crashing on an incoming call? (The lack of argument values and line numbers shouldn't pose too much of a problem here, since I have a good idea of where the bug is actually located, and am merely looking for confirmation.) |
Glad to hear it, and you're welcome! |
Honestly, I do not remember. 😄
Sure, I can see what I can get. Within the last days it crashed a couple of times, so I am confident it will do again. |
Interestingly, I meanwhile can get the PipeWire update to version 0.3.84 for Fedora 37, even though, its EOL is imminent.
Anyway, Twinkle did not crash again so far. The in-house upgrade to Fedora 39 at work is scheduled for in two days now. Maybe I can get some backtraces before that. |
The upgrade was performed last week and the systems are running on Fedora 39 with PipeWire version 0.3.85 now. Everything works as expected so far. Before, Twinkle also did not crash anymore (still with PipeWire 0.3.83), so I unfortunately can't provide any further backtrace. |
Still the case, not a single crash. For my part, this issue could be closed. |
|
I still have the crashes on Kubuntu 24.04 with KDE-Plasma-Version: 5.27.11 and pipewire 1.0.5. The version number of pipewire does not seem to match with the version numbers above. Maybe it is also interesting for others to explain the version number difference here. But the main reason for the crashes could be, that Ubuntu still uses twinkle 1.10.2. Here ( https://bugs.launchpad.net/ubuntu/+source/twinkle/+bug/1981347 ) is a request for the upgrade. Maybe others are also interested in voting for this upgrade in ubuntu. |
|
@zukunft I think you're stumbling upon an unrelated bug, because this one was fixed by newer Pipewire. So it's worth creating a separate report. (on an unrelated note, when you report to whatever upstream project, it is expected that you have tested with either the latest supported release or ideally with the master branch. 1.10.2 you mention is neither of that. Ubuntu is well known for distributing ancient software, but that means that every report on such software can only go to Ubuntu's launchpad, unless you manually compile and test newer version, thus confirming the problem persists in upstream). |
|
Yes, possible, that the bug is unrelated, but as you say, I guess, first this ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054566 ) should be solved. |
Not necessarily, building a project from sources is not difficult. Twinkly has instructions for building from source code here. So you just The cmake command will be giving you errors about missing dependencies, you have to google them and install. Actually, to save you time the project has a list here, so you can just go to packages.ubuntu.com and search by keyword. Most often it will likely be the name from that paragraph with Afterwards I'd recommend against running |
|
@zukunft …that said, to save you time: I looked at the list of PRs and many have been unanswered for 2 years. Last commit to the project has been an year ago too. So it looks like the project is dead. |
|
It seems, that we have some activities here ... #324 . I will have a more detailed look at the project and maybe we can fix some more issues. |
|
I have build and installed version Twinkle 1.10.3, 18 Februar 2022 now and I cannot crash the program any more. From my point of view, this confirms, that upgrading debian to twinkle 1.10.3 would solve the crash problem the all debian/ubuntu user. |
As you're using Kubuntu, note that Ubuntu and Debian repositories are completely unrelated. Canonical are weird regarding updates. Sometimes they avoid upgrading even the app's minor version, but then they locally apply every patch from that minor version, thus basically getting same code as in the newer version, barring the point release difference. You can report the crash downstream (to launchpad) with the note that upgrading resolves the problem, hoping that the package maintainer will find which commit fixed the bug (or at least ask you to). Though in my vast experience of interacting with Ubuntu launchpad, their reports usually get zero feedback, even highly upvoted ones. It seems to be something Ubuntu-specific, on Fedora and Arch maintainers are much more responsive. |
Please file a separate issue for this clearly separate issue. Thanks. |
I'm using Twinkle on Fedora 37 and Twinkle 1.10.3 with PipeWire as follows:
Actually this works fine, however, once in a while, Twinkle crashes "silently". The tray icon suddenly disappears without any error message. After that happened a couple of times, I ran Twinkle on a shell to see what happens when it crashes again. Every time it crashes, it does with this error message:
This occurs in the following two situations:
This happens at irregular intervals. Sometimes it doesn't happen at all in one day, sometimes several times. So, I'm unable to manually reproduce it in any way.
If I'm not mistaken, the error message comes from ALSA libraries. If relevant, this is the list of the installed ALSA packages:
While I'm on the phone, I don't have any problems at all.
The text was updated successfully, but these errors were encountered: