Public bug reported:
I own YubiKey 5 Nano.
In Ubuntu 23.10 I had configured a login to Gnome using YubiKey so that
when I started OS with YubiKey inserted, clicked on my username in login
screen, I was offered to touch YubiKey and when I did it, then a login
succeeded ✓.
But when I upgraded to
Just hit a similar issue with "fonts-wine 8.0.1~repack-3ubuntu2" in
Ubuntu 23.10.
Text on the web page https://www.virtualdub.org/altirra.html is rendered
by the font Tahoma and it looks ugly, see
https://i.imgur.com/KXC5DYq.png
I uninstalled the package "fonts-wine". Now the font Verdana is
Public bug reported:
I upgraded from Ubuntu 23.04 to 23.10 and when I open Settings => About,
I can see "Unknown" disk capacity: https://i.imgur.com/KM97Ytm.png
This is what "df" shows (it look correctly):
$ df
Filesystem 1K-blocks Used
Can't reproduce it anymore in Ubuntu 23.04 (was able to reproduce it
last time on 2023-05-26). Was it fixed?
When I run VSCode (snap), maximize window, close VSCode and run again, window
is maximized ✔
When I run VSCode, resize window, close VSCode and run again, window is resized
✔
I also
It would be great if anyone could add an explanation why such regression
behavior started in 23.04.
Is it a bug or by design? Maybe it's possible to change the behavior in dconf
editor?
For me it's a show stopper for upgrade of Ubuntu on other machines I have.
--
You received this bug
It's a regression in 23.04 because it started after upgrade Ubuntu 22.10 =>
23.04.
I have the issue with VSCode and Skype. The issue worsened UX of the
applications I need to work maximized with as I still need to maximize them
manually.
--
You received this bug notification because you are a
I would expect that Firefox should show the dialog "What to do with file?"
again if OS is not able to open the file regardless the option "Do this
automatically from now" is ticked.
I guess Firefox nor OS cannot handle KML file itself. However the state "New
tab is open again and again
Just had the same issue with Totem 42.0 in Ubuntu 22.04. Removing of
".config/totem" helped me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1966787
Title:
Totem crashes on launch |
** Attachment added: "Screenshot from 2022-06-05 11-04-35.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1977679/+attachment/5594931/+files/Screenshot%20from%202022-06-05%2011-04-35.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
Found when trying open a KML export file from Google Timeline.
It can be reproduced even with an empty KML file.
Steps:
* Create an empty file "test.kml" (run "$ touch test.kml")
* Open the application "Files"
* Right click on the test.kml and open it with Firefox
* Open
The issue persists in 22.04. Not sure if it should be fixed in upstream:
https://gitlab.gnome.org/GNOME/gtksourceview/-/issues/121.
However at least gedit behavior in Ubuntu 22.04 is better than in 21.10 (maybe
fixed in new Gnome Shell 42.0).
Let's say you have a JSON file, not prettified, 1.9
I can confirm that moving of mouse cursor over the time in time widget fixes
the issue (temporarily, because it usually occurs in a few minutes again).
Also if I press "PrtScr" to save screenshot, the issue is fixed itself.
Tested with Ubuntu 21.10, Gnome 40.4.0, Wayland.
--
You received this
Finally I upgraded my Ubuntu 20.10 to "groovy-proposed" and the issue seems to
be fixed.
More likely this bug is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1901922 .
--
You received this bug notification because you are a member of Desktop
Packages, which is
A workaround exists:
* Add "options snd-hda-intel index=1" into /etc/modprobe.d/alsa-base.conf
* Restart OS
* When login screen appears, sound works ✔️. Actually the device "Speaker -
HD-Audio Generic" is used instead of "Speaker - Family 17h HD Audio
Controller", but sound
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428556/+files/PulseList.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428553/+files/PaInfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428555/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428552/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428554/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428550/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1901901/+attachment/5428551/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Public bug reported:
My output sound device "Lenovo Family 17h" worked well in Ubuntu 20.04.
But when I upgraded to Ubuntu 20.10, I cannot hear any sound. The sound card is
not detected, "System => Sound => Output Device" shows only "Dummy Output".
I'm able to reproduce it even with live Ubuntu
I forgot to mention that I'm running:
* Ubuntu 20.04.1
* xserver-xorg-input-libinput 0.29.0-1
* libinput-bin 1.15.5-1
* libinput10:amd64 1.15.5-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
I have the same problem with touchpad in laptop "Lenovo Yoga Slim 7 14 with
Ryzen 4700u".
My Ubuntu 20.04 setting is "Tweaks => Keyboard & Mouse => Mouse Click Emulation
=> Area".
With this setting: Three finger tap works as a middle click and two finger tap
works as a right click which is
** Attachment added: "xinput --list"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5403560/+files/xinput_list.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: "xinput --list-props 12"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5403561/+files/xinput_list_props_12.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I fixed the issue by installation of proprietary AMDGPU drivers (https
://amdgpu-install.readthedocs.io/en/latest/install-installing.html
#installing-the-all-open-variant, current version is 1:19.1.0-1109583)
--
You received this bug notification because you are a member of Desktop
Packages,
I have similar problem with AMD graphics Renoir (Is it the same problem as this
issue #1870736 ?). I can scale display from 100% to 200%, but scaling to 125%
or 150% fails (see log below).
At least I'm able to scale text to 1.25.
syslog:
---
Aug 15 18:36:47 yoga gnome-shell[9538]:
Related issue is bug 1733890.
I'm seeing the bug in X (haven't tried Wayland).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1506847
Title:
gnome-screenshot doesn't put the
I can see this behavior in Ubuntu 19.10 (gnome-screenshot 3.33.90):
* If you press PrintScreen or Shift+PrintScreen then screenshot is saved as a
file to the folder Pictures instead of showing gnome-screenshot dialog (see
also bug 927952). The same behavior occurs if you run "gnome-screenshot"
I can confirm the fix helped.
I verified it according to the steps in this bug (bug 1845302) and also
according to the steps in bug 1850046 (its gnome-shell's part).
BTW when I run "killall -CONT firefox" (see the original description in
this issue), the app is closed. I guess it's correct
I've just verified a fix of the gnome-shell part of this issue in bug
1845302.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1850046
Title:
gedit freezes when opening PHP file with
As for the issue with non responsive gnome shell (bug 1845302), I hope
the fix in Mutter will be delivered to Ubuntu 19.10 (where it's broken
from my point of view). And then I'm able to test it.
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1850046 ***
https://bugs.launchpad.net/bugs/1850046
** Summary changed:
- Gnome is not responsive when opening long line file in gedit
+ Gnome stops responding if gedit is not responding
--
You received this bug notification because you are a member of
Jaromir Obr (jaromir-obr) wrote:
> An annoying thing on this bug is that it may lead to non-responsive Gnome
> desktop and then you
> have to perform system restart to get Ubuntu desktop working again, see
> #1850046.
> I guess it may be caused by an issue in OS, not only
*** This bug is a duplicate of bug 505765 ***
https://bugs.launchpad.net/bugs/505765
I don't agree it is a duplicate of the bug #505765.
Bug #505765 is an old bug in gedit happening in any distro whereas this bug
#1850073 is a regression in recently released Ubuntu 19.10 (Gnome) and should
Public bug reported:
It seems to be a regression in Ubuntu 19.10.
It works well with Ubuntu 19.04.
I compared the behavior in both distros on the same HW.
Steps to reproduce:
* Download
https://github.com/vrana/adminer/releases/download/v4.7.4/adminer-4.7.4.php
(485 kB)
* Try to open the file
An annoying thing on this bug is that it may lead to non-responsive Gnome
desktop and then you have to perform system restart to get Ubuntu desktop
working again, see #1850046.
I guess it may be caused by an issue in OS, not only in gedit.
--
You received this bug notification because you are
Public bug reported:
Steps:
* Download
https://github.com/vrana/adminer/releases/download/v4.7.4/adminer-4.7.4.php
(485 kB)
* Open it in gedit
Expected result:
* It takes a few seconds. E.g. in Visual Studio Code editor it takes max 10 sec
Actual result:
* File isn't open even in a few
It's not a bug and man page ping6(8) mentions it:
---
-I interface
For IPv6, when doing ping to
a link-local scope address, link specification (by the '%'-nota‐
tion in destination, or by this option) is required.
---
However the error message "connect: Invalid argument"
Public bug reported:
Similar to #1270791
Steps I did:
# Install Ubuntu desktop from live image (fresh installation)
# Set WiFi connection and enter password - it's saved well. I'm using a hidden
network with WPA2-PSK encryption
# Reboot
Expected result:
As the password was saved, no
It should be fixed in gedit 3.10, see
https://bugzilla.gnome.org/show_bug.cgi?id=584803#c7
This version is a part of Ubuntu 14.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/360591
Do you have an experience with the downgrade of xserver on Ubuntu 12.10
(64-bit), is it usable ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1058040
Title:
fglrx-installer
madbiologist, Christopher:
Thank you for your help, the issue with compiz is tracked as bug #1046497
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1032672
Title:
In reply to deuce:
I agree.
I tried using the OSS driver radeon in Unity, but compiz takes 100% of CPU
when using it.
So I was forced to start using Xubuntu which is uncomfortable for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
45 matches
Mail list logo
