Public bug reported:
Additional information (may be helpful for diagnosis)
In the days before that problem, I was struggling with the Nvidia
drivers, installing the driver myself (NVIDIA-Linux-x86_64-550.135)
every time there was a kernel update in Ubuntu. However, before this
problem (the networ
I got this error for the first time today. I found that an HP DeskJet
2800 printer had been installed, but I don't know how or by whom. I
have ever used this machine to print anything. I can remove this printer
from the list, but it keeps coming back. cups-browsed is a notoriously
insecure piece o
Public bug reported:
In Ubuntu 24.10, if you have the removable drives option present to be
shown in the dock, navigating to that folder will break the indicator
that a Files window is open. This includes both the little dot that
indicates the number of windows, as well as when Files is the active
Heya! I still have the machine setup with this issue. I've since
upgraded to 24.04, so if there's a PPA or some other thing I can test,
I'll happily do so. :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
land uses 40% CPU.
FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
other one from busy-looping as well.
If I switch back to the affected VT, it appears to function fine, but
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shel
Public bug reported:
- I have a laptop that I connected two additional monitors to. 1, via USB C,
and the 2nd via HDMI output.
- At some point, the USB C connected monitor froze. The monitor was still
responsive and working normally, but the image on it did not change according
to input / move
Public bug reported:
Here is the issue log:
Oct 25 09:11:36 am-ThinkPad-X1-Carbon-Gen-9 kernel: Bluetooth: hci0: Device
booted in 14662 usecs
Oct 25 09:11:36 am-ThinkPad-X1-Carbon-Gen-9 kernel: Bluetooth: hci0: Malformed
MSFT vendor event: 0x02
Oct 25 09:11:36 am-ThinkPad-X1-Carbon-Gen-9 system
Just installed a brand new 24.04 on a new laptop. All seems OK apart
from when I try to open preferences of Gedit. After a few seconds get
the wait or force quit message. If I don't force quit asap then it
causes whole system to hang. And I couldn't ALT+Fn to a terminal screen
to see what is happen
Malheureusement. This is the result of my email contacts being stolen.ย As far
as I know I have recovered control of the email and deleted the filters placed
by the scammer.Thank you for your message.
Alan
On Wednesday 28 August 2024 at 03:20:25 BST, Thibault D
<588...@bugs.launchpad.
I just rebuilt and installed fresh packages on Noble using the supplied
patch above and all good now!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to remmina in Ubuntu.
https://bugs.launchpad.net/bugs/2062177
Title:
Remmina crashes aft
I managed to unbreak my system (in case anyone stumbles here looking for
help) after reporting bug 2063219
Julian suggested installing libglib2.0-0t64_2.80.0-6ubuntu1_amd64.deb
manually downloaded from the archive with dpkg, which I did.
Then checked the debs in /var/cache/apt/archives/*.deb were
Public bug reported:
Problem:
When maximising/minimising/restoring a window by clicking on the item in
the launcher, sometimes (often) the animation - which makes the window
shrink and 'fly' to or from the dock, will fly in the wrong direction.
Steps to reproduce:
* Have multiple monitors (I th
Why do we have to file a new bug for this. The task for mantic says it's
fix released, but it clearly isn't.
alan@ziggy:~$ grep -r Meta.Rectangle /usr/share/gnome-shell/extensions/
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js:
const rect = new Meta
alan@ziggy:~$ sudo journalctl -b0 | grep Meta.Rectangle | wc -l
1836
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2034664
Title:
Meta.Rectangle is
Public bug reported:
Crashes on my ThinkPad Z13 running up-to-date Ubuntu 23.10.
$ sudo switcherooctl --list
Traceback (most recent call last):
File "/usr/bin/switcherooctl", line 187, in
launch(args, gpu)
File "/usr/bin/switcherooctl", line 66, in launch
os.execvp(args[0], args)
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shell 42.9-0ubuntu2
xwayland 2:22.1.1-1ubuntu0.7
$ ps -aux | grep 'alan .*gnome-shell$'
alan9248 26.1 3.4 5492888 269136 ? Rsl 19:54 30:26
/usr/bin/gnome-shell
$ sudo s
alan@nuc:~$ switcherooctl list
Device: 0
Name:Advanced Micro Devices, Inc. [AMDยฎ/ATI] Polaris 22 XT [Radeon RX
Vega M GH]
Default: yes
Environment: DRI_PRIME=pci-_01_00_0
Device: 1
Name:NVIDIA Corporation TU102 [GeForce RTX 2080 Ti Rev. A]
Default: no
I see this on both 23.04 and 23.10, around 10% of the time emacs
launches from a shell, and with emacs -Q too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2011244
Title:
emacs
The PC I reproduced the black screen bug on is running Ubuntu 22.04,
however.
--
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/1838963
Title:
Firefox window initially appears black when
The upstream bug for the black window is here - it's how I was notified
about Firefox switching to wayland:
https://bugzilla.mozilla.org/show_bug.cgi?id=1788205
Reading the end of the comments, there's a resolution - not inside
Firefox - apparently available as an update in Ubuntu 23.04.
** Bug
It still reproduces in a small number of tries - on a 10 year old
Celeron. The packages have been updated recently, and I updated them
again before testing.
I recently saw that Firefox are enabling Wayland for their next release.
So that should bypass this bug with XWayland:
https://bugzilla.moz
to either gnome-shell or XWayland stops the
other one from busy-looping as well.
If I switch back to the affected VT, it appears to function fine, but
it is still using 100% + 40% CPU.
Version numbers:
Ubuntu 22.04.3 LTS
gnome-shell 42.9-0ubuntu2
xwayland 2:22.1.1-1ubuntu0.7
grep 'alan .*gnome-shell$'
alan9248 26.1 3.4 5492888 269136 ? Rsl 19:54 30:26
/usr/bin/gnome-shell
$ sudo strace -p 9248 2>&1|head
strace: Process 9248 attached
epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}],
32, 0) = 1
recv
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2662
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2662
Importance: Unknown
Status: U
Public bug reported:
My system has multiple GPUs:
00:02.0 Display controller: Intel Corporation HD Graphics 630 (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Polaris 22 XT [Radeon RX Vega M GH] (rev c0)
40:00.0 VGA compatible controller: NVIDIA Corporation GP
** Attachment added: "Screenshot from 2023-05-16 17-26-13.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019886/+attachment/5673370/+files/Screenshot%20from%202023-05-16%2017-26-13.png
--
You received this bug notification because you are a member of Desktop
Package
Public bug reported:
I would like to see the printer ink levels of my printer.
If I visit the gnome settings printer panel, I see lots of cyan, and a small
amount of magenta, and a small amount of yellow. An unknown about of black is
shown, perhaps in between magenta and yellow, or perhaps the
Sorry, attached wrong screenshot!
** Attachment added: "Screenshot from 2023-05-16 17-26-13.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2019885/+attachment/5673365/+files/Screenshot%20from%202023-05-16%2017-26-13.png
--
You received this bug notification because
Public bug reported:
See screenshot.
I'd like to know the ink level in my laser printer.
I can see the ink level in the gnome control center. However the colours look
like they're not centred vertically.
The ink levels are inside a losenge but don't fit perfectly vertically.
There's a gap belo
Public bug reported:
This scanner has previously worked on other computers running Ubuntu.
However, it doesn't work on 23.04.
The scanner is on, and shows up in the front screen in simple-scan
When I press the scan button a dialog appears titled "Failed to scan" "Unable
to connect to scanner".
Kdenlive.
alan@ziggy:~$ pactl stat
Currently in use: 7865827 blocks containing 2.1 GiB bytes total.
Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total.
Sample cache size: 275.2 KiB
alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail
207.7 MiB + 419.6 MiB = 627.2 MiB
The network-manager package in Bionic and Focal install as symlink to
NetworkManager.service correctly:
https://packages.ubuntu.com/search?searchon=contents&keywords=network-
manager.service&mode=exactfilename&suite=bionic&arch=any
https://packages.ubuntu.com/search?searchon=contents&keywords=net
Public bug reported:
I can save a libre doc to my desktop for example. I do see in my Ubuntu
"files and or Dics" app both the USB external drive and the additional
SSD added post purchase, but libre does not see those memory places when
I attempt a "save as". Libre only sees that which would be ca
(In reply to Robert Mader [:rmader] from comment #42)
> Hm, this pretty much sounds like Gnome-Shell bug around Xwayland-on-demand to
> me - so maybe a better place for that would be
> https://gitlab.gnome.org/GNOME/mutter/-/issues (or a Ubuntu bug, in case they
> ship some custom patches).
...
Something similar happened on Fedora. So I've reported to GNOME.
"Timing/race condition with Xwayland-on-demand breaks firefox & confuses gedit
etc"
Link: https://gitlab.gnome.org/GNOME/mutter/-/issues/2472
--
You received this bug notification because you are a member of Desktop
Packages, whic
(In reply to Robert Mader [:rmader] from comment #32)
> Oh, that's really interesting...so does launching with
> `MOZ_GTK_TITLEBAR_DECORATION=system` also solve the issue?
It does about the same as XDG_CURRENT_DESKTOP="". Instead of remaining
black, basically nothing gets drawn. The inside of the
It feels like the problem is to do with socket-activated Xwayland.
I can suppress the issue where firefox remains black, by editing my
.desktop file to run "xlsclients" first. I.e.:
Exec=/bin/bash -c "xlsclients; MOZ_ENABLE_WAYLAND=0
/home/alan/firefox-104.0.2/firefox/firefox&q
Created attachment 9298517
Screenshot from 2022-10-13 20-59-46.png
1. If I launch gedit with GDK_BACKEND=x11, as the first app after
logging in, it appears usable. However the window is incorrectly drawn
with a square window border. See screenshot.
If I then launch firefox, using the snap for
Nice tool. It seemed like nightlies default to Wayland, so I had to test
with MOZ_ENABLE_WAYLAND=0.
Bisecting the *temporary* black window gave:
9:33.09 INFO: Last good revision: d1eb6fe5a1fa5457425c5a33f212516a5eeaa381
9:33.09 INFO: First bad revision: 498e0e6f9b19107c8c17525a3d01a659f89002e8
Created attachment 9298516
Screenshot of firefox with MOZ_GTK_TITLEBAR_DECORATION=system
> To double-check, can you confirm that
MOZ_GTK_TITLEBAR_DECORATION=system works
No, I say MOZ_GTK_TITLEBAR_DECORATION=system fails. Just slightly
differently. Instead of a black window, only a border (drop s
Weird!
I can run xterm. Including immediately after login, which is how I've
been reproducing this Firefox issue.
I can change my hacked-up .desktop file to run "WAYLAND_DISPLAY=''
libreoffice" instead, and the libreoffice window seems fine.
I can run glxgears, xeyes, and xvidtune ok :-). (Didn
Yes to all of the above.
I disabled the Firefox snap. I used this download from mozilla.org, and
I still had the black window issue.
And forcing Wayland seems to fix that completely.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firef
Something similar happened on Fedora. So I've reported to GNOME.
"Timing/race condition with Xwayland-on-demand breaks firefox & confuses gedit
etc"
Link: https://gitlab.gnome.org/GNOME/mutter/-/issues/2472
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2472
https://gitlab.gnome
Public bug reported:
not sure
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: firefox 104.0+build3-0ubuntu0.20.04.1
Uname: Linux 4.9.312-125 aarch64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: arm64
AudioDevicesInUse:
USERPID ACCESS COMMAND
Created attachment 9295261
about:support json from running MOZ_ENABLE_WAYLAND=1
./firefox-104.0.2/firefox/firefox
--
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/1987976
Title:
firefo
Created attachment 9295260
about:support json from running ./firefox-104.0.2/firefox/firefox
--
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/1987976
Title:
firefox black window
Status
> It seems not to happen if instead of the "firefox" launcher binary, I
run "firefox-bin" directly. What's the difference?
Nevermind. I think it can happen with either. It's just a bit random
whether it happens or not.
--
You received this bug notification because you are a member of Desktop
Pac
Sorry, I can't deal with the randomness. Let's simplify -
$ sudo snap disable firefox
firefox disabled
$ cat ~/.local/share/applications/firefox2.desktop
[Desktop Entry]
Version=1.0
Name=Firefox Web Browser 2
Exec=/bin/bash -c "/home/alan/firefox-104.0.2/firefox/firefox&qu
I have the same black window problem. Can I help?
I can reproduce it with upstream "firefox" unpacked from
firefox-104.0.2.tar.bz2 ! (As well as by using the snap)
It seems *not* to happen if instead of the "firefox" launcher binary, I
run "firefox-bin" directly. What's the difference?
It happen
Public bug reported:
Running KDE 5.24.4 on Ubuntu Jammy. On a few occasions, I've been able
to trigger a complete desktop crash by pressing and holding the volume
keys on my laptop.
Steps to reproduce:
1) Have something play audio - typically youtube in a browser
2) Hold down Fn+F3 or Fn+F2 to in
failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
Aug 22 16:01:16 alan-GL63-9SD pulseaudio[1669]: D-Bus name
org.pulsea
This is happening on a default Jammy GNOME install. No extra extensions.
This starts when the machine reaches high uptime usually 2 weeks+
journalctl is full of:
Aug 18 11:28:09 veloci gnome-shell[2558]: Key repeat discarded, Wayland
compositor doesn't seem to be processing events fast enough!
I have had a similar issue with Sea Monkey losing access to all my
stored passwords etc. The upgrade was from 20.04 to 22.04. Hopefully my
Timeshift backup will let me get things back
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefo
Just tested the above image with eog 3.36.3-0ubuntu1 (Focal) and it
crashed (Virtual Machine with 2 CPU cores and 4GB RAM). Tested with eog
42.0-1 (Jammy) and it worked.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eog in Ubuntu.
https
This is also affecting Virsh (KVM/QEMU) based virtual machines. Just
tested with The latest Focal update (gnome-settings-daemon
3.36.1-0ubuntu1.1) and the machine was turned off without any
notifications.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and was not
able to reproduce this issue. Should be fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1576252
Title:
L
Just tested with Focal's Nautilus 1:3.36.3-0ubuntu1.20.04.1 and this
does not happen.
Followed the same scenario and renamed 2 out of 4 sample files:
1) Using Nautilus itself.
2) Closed Nautilus and renamed the files in terminal.
In both cases Nautilus automatically regenerated the thumbnails.
I just tested this with Bionic and it seems to be fixed. Previewed files
~/.cache/.fr- no longer exist after closing file-roller.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/14442
I have exactly the same issue! REALLY ANNOYING!!
How can I retrieve all my tabs, bookmarks, passwords,.
from my previous installation. This cock-up alone has made me regret the update
to 22.04. I was using 20.04, and wish I still was :-(
--
You received this bug notification because you ar
It looks like the issue is resolved because it's no longer in the new
version (98).
Let me know if you still want apport-collect output.
-Original Message-
From: Olivier Tilloy <1956...@bugs.launchpad.net>
Reply-To: Bug 1956348 <1956...@bugs.launchpad.net>
To: al...@gmx.com
Subject: [Bug
Public bug reported:
I recently upgraded from 18.04.6LTS to 20.04.3LTS (both 64-bit).
>From the very first time I launched chromium (after the upgrade) it started
>using 100% CPU.
I'm running this on a VM which only has 1 CPU allocated (and 2GB RAM with 2GB
SWAP) but I've been running 18.04 (and
Public bug reported:
If you click the "Trash" icon in the dock, the Trash entry in Files
opens, but a Files icon also spawns in the dock, and it appears as if
both the Trash and Files icons associate with the same Trash window in
Files. This seems to correct itself after 15-30 seconds or whenever
Public bug reported:
The newly translated strings in GTK does not seem to be imported from
Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is
fully translated in Damned Lies.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this b
** Changed in: miral
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1420334
Title:
[enhancement] Missing client API for relative surface mo
gtk-mir is no longer a thing
** No longer affects: unity8 (Ubuntu)
** No longer affects: qtmir (Ubuntu)
** No longer affects: mir (Ubuntu)
** No longer affects: gtk+3.0 (Ubuntu)
** No longer affects: miral
** No longer affects: mir
** Changed in: canonical-devices-system-image
Status:
Same problem occurs for me with nvidia-driver-470. The graphical effect
/ issue is a bit different, yet. See attached pic... My Ubuntu 20.04 is
as up-to-date as possible.
The last suggested solution is working for me (restarting gnome-shell),
but this is still annoying... I've just read this :
htt
Public bug reported:
ThinkPad X1C9 running Kubuntu.
I'm using an external nVidia GPU in an enclosure, attached via thunderbolt.
I have applied updates over the last few weeks, and rebooted today.
Got a black screen. Turns out an update back in mid June (22nd) removed the
Option
"AllowExternalGp
Public bug reported:
change [printer] driver selected. then 'select printer from data base'
clicked. freezes on 'searching for drivers'. choice to 'force quit' or
'wait' appears but 'searching for drivers ' message freezes over the
'force quit/wait' message.
ProblemType: Bug
DistroRelease: Ubuntu
Sebastien
I have downloaded and installed gnome-system-monitor/40.0-2
This now works
Running on Xubuntu 21.04
Thank You
Best wishes
Alan
On Wed, 07 Apr 2021 13:05:29 -
Sebastien Bacher <1922...@bugs.launchpad.net> wrote:
> It sounds like the !GNOME issue that was fixed in
&
Here's a tarball of the wallpapers and the mascot in SVG format:
https://people.canonical.com/~alan/Hirsute_Hippo_Wallpapers.zip
https://people.canonical.com/~alan/Hirsute_Hippo_Mascot.zip
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
** Attachment added: "Screenshot from 2021-03-05 19-24-08.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1917939/+attachment/5473781/+files/Screenshot%20from%202021-03-05%2019-24-08.png
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
Under wayland on 21.04 windows keep maximising underneath the dock. So I
can see icons "through" the dock, when I shouldn't. In the attached
screenshot you can see Telegram showing through the dock.
If I switch to the application in question, unmaximise and re-maximise,
it go
Public bug reported:
I installed 'unity desktop before upgrading Libreoffice and it all went
pear shaped. I tried it twice, thinking it may very well be my error.
But it appears to be an equal opportunity error.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libreoffice-gnome (not inst
Public bug reported:
I got the "Oh no!" screen.
The likely trigger was when I was playing a game and took a screenshot -
where the environment is likely hard to reproduce because the game I'm
playing that triggered the scenario isn't out yet. It can be built tho.
1) git clone https://github.com/
+dfsg-0ubuntu5
Uname: Linux 5.6.0-050600-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: alan 47711 F pulseaudio
/dev/snd/controlC0: alan 47711 F pulseaudio
/dev/snd
-050600-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: alan 47711 F pulseaudio
/dev/snd/controlC0: alan 47711 F pulseaudio
/dev/snd/pcmC0D1p: alan 47711 F...m pulseaudio
/dev
*** This bug is a duplicate of bug 199 ***
https://bugs.launchpad.net/bugs/199
It does indeed! Thanks.
Looks like upstream marked the linked bug from there as a dupe of
https://gitlab.gnome.org/GNOME/mutter/-/issues/1389 which is the 'real' bug
marked as fixed in https://gitlab.gnome
Public bug reported:
Summary:
Snapping a window to one side of the screen will often snap to the side
of the wrong monitor.
Steps to reproduce:
1. Have two monitors arranged side by side
2. Open a new application window such as nautilus or a terminal
3a. Grab the right half of the title bar of
I added a workaround to the askubuntu post.
https://askubuntu.com/a/1266706/612
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1732482
Title:
[snap] doesn't properly save des
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1838152
Title:
gnome-shell freezes on notification arrival (fixed upstream)
Status in GNOME Shell:
Public bug reported:
Summary of current state:
Back in 19.10 we migrated the deb of chromium to a snap. Users who
installed the deb, got snapd and the snap of chromium. Users who already
had the deb of chromium, and upgraded, got snapd and the snap.
The goal of making the snap was (largely) to r
Public bug reported:
I just installed chromium on my 20.04 machine. I've not used chromium on
this system before. It installed but I get this warning:
snap "chromium" has bad plugs or slots: system-packages-doc
$ snap install chromium
2020-07-16T11:52:42+01:00 INFO snap "chromium" has bad plugs
I've actually found if you keep toggling the switch it will eventually
work. Sometimes it only takes a couple or other times I've clicked it
30 times.
Before I discovered this I was removing and re-adding my devices to get
them to reconnect.
--
You received this bug notification because you are
Running 20.04. Seems to me this bug appears only after I run
Transmission Bit Torrent Client. My log files have shown that my kernel
has been changed and after that I may lose wifi and lan connectivity. I
have performed a fresh install of 20.04 numerous times to eliminate the
problem and have ru
Nethertheless, I tried to report the bug to Gnome here :
https://gitlab.gnome.org/GNOME/mutter/-/issues/1263
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1263
https://gitlab.gnome.org/GNOME/mutter/-/issues/1263
--
You received this bug notification because you are a member of D
I appreciate some considerable time has passed since this bug was reported.
Does it still occur with newer versions of the font viewer?
Was there (if you recall) a particular font file which triggered this?
** Changed in: gnome-font-viewer (Ubuntu)
Status: New => Incomplete
--
You receive
update/upgrade.
As of today you'll get linux-image-5.4.0-29-generic
Reboot
Expected outcome
Boot to newer linux-image-5.4.0-29-generic kernel
Actual outcome
Booted to older stock kernel - 5.4.0-21-generic
Data:
alan@mcp:~$ uname -a
Linux mcp 5.4.0-21-generic #25-Ubuntu SMP Sat Mar 28 13:
Public bug reported:
Just after fresh installation of Ubuntu 20.04 64 bits in UEFI mode, I'm
not able to install chromium-browser. I need to kill the process snap
install chromoum-browser?
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser (not installed)
ProcVersionSignat
Public bug reported:
After letting my laptop go to sleep, the WiFi does not reconnect anymore
to an hidden access point. I must go to the WiFi settings window, then
go to the menu where hidden networks are... hidden, and force Network
Manager to connect to the hidden AP. Note that I don't have any
Note that the video does not show exactly what I'm experiencing. The
right edge of the Firefox window is at a little bit more at right of the
"middle" of the secondary screen (say +500 pixels on the 900 pixels).
And then I move right the mouse to the right edge of the secondary
screen, the left sid
Additionally, I just realized that if I move the mouse to the right side
of my secondary screen (which is at the riht side of my primary screen),
the "whole screen moves", like if I had a virtual screen which
resolution exceed the native 2560x1440 of my main screen. Difficult to
explain, so please
Done : https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874217
Thanks for answering that fast !
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/186957
See the screen capture attached for the demonstration of the bug.
** Attachment added: "Capture dโรฉcran du 2020-04-19 23-16-25.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874217/+attachment/5357862/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202020-04-19%2023-16-25.png
--
Public bug reported:
I will provide below a screen capture. I think this bug is related to
this one : https://bugs.launchpad.net/dash-to-dock/+bug/1869571
I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted.
I use dual screen : the main screen is on the left side (32"), the
secondary
I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5,
but still got "my" problem. Should I fill a separate bug report ? And
sorry for the pollution-by-comments :-(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-sh
Argh. Just forgotten : the problem of window extending out from its
natural place disappear if I revert the orientation of secondary screen
from ยซ portrait turned right ยป to ยซ landscape ยป.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to g
Re-argh : my Ubuntu 20.04 is fully up to date.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1869571
Title:
Vertical dual monitor setup with main monitor on
Hi, I decided to add information here rather than creating a new bug
report. I'm in dual screen too, main screen at left (32"), secondary
screen (19") at right and in portrait mode (rotated right). The window
are improperly growed : they extend from full main screen to half the
"witdh" of the seco
Confirmed I'm no longer seeing the tiny-icons thing, but still seeing
the pager issue, fully up to date.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1869737
Title:
App icons sh
I just ninja'ed the docking.js file as per the change in comment #23 and
that fixes both the issue in this bug, and the issue where the icons are
all small (as shown here https://www.youtube.com/watch?v=2mZZtClVOSg)
Screenshots attached.
** Attachment added: "Screenshot from 2020-04-20 15-21-15.p
1 - 100 of 1092 matches
Mail list logo