The system was updated from Ubuntu 20.04 to 21.10, but it’s still not
working out of the box without the script `a2dp.py`.
I am not able to work more on the issue, as I do not have the
environment, but maybe Canonical and Google should work more closely
together on the QA side.
--
You received t
Yes, thank you for assigning the right component.
Personally, for desktops, I would always recommend the latest release. I
think a lot of users do not know the difference, and just click the
green button.
> We also have the latest BlueZ in Ubuntu already.
Do you mean 21.10, which has 5.60-0ubunt
I understand, that bugs are probably fixed in newer versions.
https://ubuntu.com/#download still offers Ubuntu 20.04 for desktops, and
even highlighted green. So what functionality can users expect?
Anyway, I just wanted to report it, and, as it is not my device, I am
also unable to debug more.
** Attachment added: "a2dp.py fixing the problem"
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+attachment/5550575/+files/a2dp-0.6.2.py
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ub
This is not my system, so I cannot debug a lot.
Linux kernel 5.4.x is used, and Linux logs hci related messages, and
bluetoothd also segfaults. (Ubuntu noticed the crash, and should have
uploaded the resulting dumps.)
What fixed it was using `a2dp.py`:
```
$ curl
"https://gist.githubusercontent
Public bug reported:
On ppc64le and Ubuntu 20.10 with *evolution-data-server* 3.38.1-1, the
logs contain, when starting an Xfce session over X2Go.
[98982.444956] systemd-xdg-autostart-generator[297820]: Exec binary
'/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No
Public bug reported:
See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss-nis
and suchlike) [1]. Logging in takes a long time.
May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: RPC:
Unable to send; errno = Operation not permitted
May 30 13:26:50 ubunt
Also please look at Thomas’ comment. The patch is just for some follow
up comments in this report. The original reporter of this issue
(LP:780117) has a different issue with growisofs. Though closing this
report might be wise and people still experiencing problems with Brasero
should submit new rep
Just a small nit pick. In the SRU message it says that part of the
offending commit are reverted. Actually nothing is reverted and the
change just completed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bu
The way to solve this error, is that people provide the necessary log
files from Brasero and to improve the things Thomas Schmitt and George
Danchev have found out to be incorrect [1].
[1] http://bugs.debian.org/617409
--
You received this bug notification because you are a member of Ubuntu
Desk
Looking at `git log` [2] or `NEWS` [2] I am pretty sure nothing changed.
[1] http://git.gnome.org/browse/brasero/log/?h=gnome-3-6
[2] http://git.gnome.org/browse/brasero/tree/NEWS
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to braser
Perriman, thank you for following up on my question.
I think the only way is to save the log, when Brasero asks you to after
a burn process. You can also look into `/tmp/` for the log.
Are you sure, you are seeing the exact same error as the reporter of
this bug does? That means progress bar stop
Parriman, thank you for testing.
Unfortunately without any log files, the developers have a hard time
fixing the error. Do you have log files from failed and successful
burns? It would be great if you could attach those.
--
You received this bug notification because you are a member of Ubuntu
De
Dear Andrea, thank you for testing the patch.
Could you please provide more information. Especially the version of
Brasero, maybe find out if libburn is really disabled and what is used
now. Additionally the versions of the components Brasero depends on and
the any log files from Brasero.
It is s
A similar bug report is on Debian [1], but it is not known yet if all
talk about the same cause the original reporter was seeing.
Anyway the libburnia developers stepped up and cooked up some patches
for you to try please to gather some more information what goes wrong.
So please apply Georges pa
15 matches
Mail list logo
