It's not always easy to check that the pasted text it's the correct one,
then this is a data corruption bug. That is why I think this is a
critical bug.
Worse, the most affected users of this bug (non-technical ones) are very
unlikely to ever report it. For example, I am a programmer and I only
How can I help to fix this bug?
I can easely reproduce it easely on three differnt computers (one new
install, and two upgraded from 19.10).
The only workaround that I have found is to install xubuntu-desktop or
lubuntu-desktop. I cannot use "Ubuntu Wayland" because libreoffice
becomes sluggish
You are right, the bug is fixed upstream. I have manually downloaded
gvfs-bin_1.34.1-1ubuntu1_amd64.deb and checked the file: it includes the
fix.
However it is not fixed on my computer. And I do not know why.
Unfortunately I have not found the package in /var/cache/apt/archives,
then I am not
** Description changed:
The script /usr/bin/gvfs-info uses two bash features:
1. "==" is used for string comparison instead of "="
2. "$@:2" is used instead of "shift" and then "$@" to expand all but the
first argument.
+
+ You can see the errors by running "gvfs-info --help".
I
Public bug reported:
The script /usr/bin/gvfs-info uses two bash features:
1. "==" is used for string comparison instead of "="
2. "$@:2" is used instead of "shift" and then "$@" to expand all but the first
argument.
I have found this bug using xdg-open to open a PDF file from the command
I haven't seen anymore this bug for months. So I think it was fixed by
some updates.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1003316
Title:
Cannot close Firefox inspector
@chemnic, have you checked comment #132? What happens if you wait 5
seconds before reopening LibreOffice, as stated at bug #1075263?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
apport-collect does not work for me because I am not the bug's reporter.
However, I have tried to find a reliable way to reproduce this bug. I
have found it to be very easy to reproduce on two computers, but it is
not that easy to understand when it happens.
I have come to the conclusion that it
Thanks for the tips Christopher.
After much searching, I have finally found the bug that I am seeing: Bug
#1064962
However I think this bug is a duplicate of bug #1064962.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in
Johan, you should post the output of the script, not the script.
Raymond, you can find the output alsa-info.sh on my computer at
http://www.alsa-project.org/db/?f=578ac23a785c41eae14c32f15fb39ccb1da3a663
Thanks for any help.
--
You received this bug notification because you are a member of
As suggested at http://askubuntu.com/a/206554/11223 doing:
rm -r ~/.pulse ~/.pulse-cookie
pkill pulse
makes the problem disappear, but only until I change the sound volume
through the panel indicator.
--
You received this bug notification because you are a member of Desktop
Packages,
Looks like e duplicate of Bug #1063965
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1067434
Title:
Sound output device keeps changing when using headphones
Status in
Looks like a duplicate of bug #1067434
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1063965
Title:
Choppy sound in 12.10
Status in “alsa-driver” package in Ubuntu:
Confirmed
Going to (translated from my language) System properties Sound
Output, and clicking on a output device, I see that the device Analog
headphones appears and disappears continuosly at a fast rate.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
Started the inspector via context menu Inspect Element (Q).
Clicking on the X (Close Inspector) button does nothing.
Reloading the page, the inspector is still here.
Forcing reload, same effect.
Switching to other tabs on the same window, all tabs show the inspector.
Opening
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1003316
Title:
Cannot close Firefox inspector
Status in “firefox” package in Ubuntu:
New
Bug description:
Started the inspector
16 matches
Mail list logo
