This just happened to me also, after a fresh install of 23.10 daily. It
happened during an install script, and it happened in particular while
my install script was installing packages via `sudo apt-get install`.
Unfortunately, I cannot reproduce.
--
You received this bug notification because
Also, forgive me as I'm a n00b with using Launchpad. I was not sure how
to add the tag "verification-failed-lunar". Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2013216
I was able easily to install version 44.1 as well:
$ sudo apt-get install mutter/lunar-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '44.1-0ubuntu1' (Ubuntu:23.04/lunar-proposed [amd64]) for
'mutter'
Selected version
Super, thank you for the information, Jeremy.
-SW
On Tue, May 23, 2023 at 3:55 PM Jeremy Bícha <2013...@bugs.launchpad.net>
wrote:
> Scott, the mutter 44.1 update for Ubuntu 23.04 needs to be manually
> approved by a member of the Ubuntu SRU team before it will be built as a
> -
Is there any news or ETA for the new mutter 44.1-1ubuntu1 package?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2013216
Title:
Single click on title bar does not transfer focus
Is there any specific date that Gnome 44.1 will be released for Lunar?
Also, FYI only, I've noticed that Firefox (snap, version 112.0.2-1, rev
2605) doesn't seem to suffer the same issue as other application
windows. I wonder why that is?
--
You received this bug notification because you are a
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
I am observing the same issue on 22.04. I cannot drag and drop from
nautilus into chrome or slack.
If I switch to an xorg session I can drag and drop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967812
Title:
ubuntu 22.04 beta crash regarding gnome-shell and several
In case it helps, I noticed that in Ubuntu 21.04, my
~/.config/GIMP/2.10/pluginrc contained
(menu-path "/File/Create/Acquire/XSane/Device dialog...")
within the (proc-def "xsane" ...) s-expression. No menu-path appears in
my Ubuntu 21.10 ~/.config/GIMP/2.10/pluginrc.
--
You received this bug
This is still a bug in Ubuntu 21.04 and 21.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
This issue was fixed in https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/994 which avoids changing `xkb-options` unless
the Alternate Characters dialog is opened. (That was originally part of
MR 910, but was split off so it could be merged without being blocked on
design
this worked for me to set all profiles as I wanted in 20.04
$ val='@ms
Happens to me (headset recognized but no sound) XPS 13 9380
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1866194
Title:
External audio device shows up in the sound
i got an email about released. I also notice on here that a fix has been
released. I don't see it as an update via software updates. How to I get
the fix.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
The power button in gdm3 will not power off or reboot the system.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset
I can confirm that I am still having this issue on 3.34 as well
(Manjaro).
This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day. Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation
Public bug reported:
Image: 19.10 beta –
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
Device: Dell Precision 5540 (201904-26937)
1. Install Ubuntu 19.10.
2. Check 'Encrypt the new Ubuntu Installation for security' and 'Use LVM with
the new Ubuntu Installation'
3.
I believe I made a mistake in the steps taken above.
I believe I rebooted my computer once after the `journalctl --vacuum-
time=1s`
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
# journalctl rotate
# journalctl --vacuum-time=1s
journalctl -b-1 --no-pager > prevboot.txt
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+attachment/5264569/+files/prevboot.txt
--
You received this bug notification because you
WORKAROUND on how to use keyboard Ctrl+Shift+/Alf+Shift+ shortcuts with
Ctrl+Shift as layout switch.
Order of keys pressed for layout switching is important. So
['Shift_L'] implies Control pressed first and Shift pressed
second. Inverse order won't work. You have to use ['Control_L']
for inverse
** Changed in: gvfs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1815395
Title:
GVFS-SMB write problems to SMB2 shares
To manage
cause the problem to
recur.
I suppose this is why I wanted to see if anyone could replicate this. I
would bet now that they couldn't but I doubt I'll ever know what the
actual issue was, now.
Anyway, I'm closing this bug. Sorry for the false alarm. :)
Thanks,
Scott
--
You received thi
Sorry, spoke too soon. I'm not sure which status to change this to. It
was never confirmed by anyone else, but the traces definitely showed
something bad happening. Any suggestions what I should set the status
to in order to properly file it away?
--
You received this bug notification because
Will do. I wanted to post here before cross-posting it in case the
issue was something to do with the Ubuntu implementation of GVFS and not
GVFS itself. I was also kind of hoping someone could do my tests to
confirm this is actually a bug and not some craziness that only affects
me but I suppose
Public bug reported:
Summary:
I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus)
that manifests when writing to SMB2 shares. It occurs inconsistently
(but enough to be annoying) in everyday use, but it can be replicated
consistently with a simple echo command redirected to
The solution until this is solved is to use something other than gnome
shell as far as I know. Mint Cinnamon and Elementary are both popular
alternatives.
On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:
> I am facing the same issue in Ubuntu 18.10. The super key randomly
Same very high CPU on Ubuntu 19.04 just
after I installed, launched and logged into gmail
using browser chrome Version 73.0.3679.0 (Official Build) dev (64-bit)
After 5 mins
/usr/bin/gnome-keyring-daemon --daemonize --login
no longer used high CPU
--
You received this bug notification
For my reference later.
The 'dconf read' with ':list' syntax has changed, so the comments above don't
work in 18.04.
Updated, this worked for me:
$ dconf list /org/gnome/terminal/legacy/profiles:/
:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/
$ dconf write
Public bug reported:
In xenial the file
/usr/lib/x86_64-linux-gnu/librsvg-2.a
was still there but in bionic onwards it's missing. I cannot statically
link with librsvg-2 without it. Please add it back in.
** Affects: librsvg (Ubuntu)
Importance: Undecided
Status: New
--
*** This bug is a duplicate of bug 1735071 ***
https://bugs.launchpad.net/bugs/1735071
** This bug is no longer a duplicate of bug 1801912
ctrl-f doesn't open the search box
** This bug has been marked a duplicate of bug 1735071
Ctrl + F search disengages immediately after CTRL + F
*** This bug is a duplicate of bug 1735071 ***
https://bugs.launchpad.net/bugs/1735071
** This bug has been marked a duplicate of bug 1735071
Ctrl + F search disengages immediately after CTRL + F pressed
--
You received this bug notification because you are a member of Ubuntu
Desktop
** This bug is no longer a duplicate of bug 1801912
ctrl-f doesn't open the search box
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1735071
Title:
Ctrl + F search
Well, I think I found out what was happening.
In gnome-tweaks I had somehow gotten 'Workspaces' -> 'Display Handling'
set to 'Workspaces on primary display only'.
So what happened was that there was only a single workspace on the
"second" head and thus no need for "always on visible workspace".
Yes I have a password ... wrt #1803527 I removed all gnome extensions no
help.
UPDATE - this issue only happens when using nvidia drivers installed
using Software & Updates -> Additional Drivers -> nvidia 390 , with
nouveau its OK
** Description changed:
This is not a problem using only
** Description changed:
This is not a problem using only built in laptop screen however when I
attach an external monitor and choose
Setting->Display->Single Display
then choose the external monitor to be the only active screen -> then
when I suspend upon resume the external
Public bug reported:
This is not a problem using only built in laptop screen however when I
attach an external monitor and choose
Setting->Display->Single Display
then choose the external monitor to be the only active screen -> then
when I suspend upon resume the external monitor lights up
I just now realized that this issue only occurs when the window is on my
"second" monitor.
If move the window to the primary display then the window menu has
Minimize, Maximize, Move, Resize, Always on Top, Always on Visible
Workspace, Move Workspace Down, Move to Monitor Right, Close
But on
Don't get too excited..
https://gitlab.gnome.org/GNOME/nautilus/issues/703
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1706097
Title:
gvfsd-mtp crashed with SIGSEGV
To manage
Well, after an upgrade and reboot (including mutter 3.30.1-1), 'alt
space' now works to bring up the m enu.
However, there is no 'Always on visible workspace' option.
So I will close this bug as 'fix released' and I have opened bug
1797120.
** Changed in: mutter (Ubuntu)
Status: New =>
Public bug reported:
I filed bug 1795410 a few weeks ago complaining that the 'alt space'
didn't bring up the window menu. That is now fixed (seemingly likely
with mutter 3.3.0-6).
However, the window menu that does come up does not have an entry for
'Always on visible workspace' as it used to.
As a work around, I just configured some short cut (super w) to 'Toggle
window on all workspaces or one' in the gnome-control-center and that
seems to function.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I ran sudo apt-get autoclean, and other command line clean up tools and
tried again.
I was able to upgrade then. Not sure why just running some cleaning
programs worked but did and now I have 18.10 running.
Thank you
You can marked this solved.
Scott Stehno
On 09/25/2018 08:46 AM, Colin
I'm finding the same symptoms from gnome-shell, relatively high cpu use by
gnome-shell with all extenstions deisabled (if I turn on extensions the cpu
usages is ridiculous high, in the range of 20-50%).
I checked strace as above and am finding the same high number of errors from
the recvmsg
Copy and Paste is not working for me on a freshly installed copy of 18.04.1
using Wayland.
Is this regression from 3 years ago still not resolved?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
** Description changed:
9-8-018
-
- I suspect this is a gdm3 bug as a similar bug was reported earlier with blank
purple screen. This is running a fully updated fresh install september-8-018
+ I suspect this is a gdm3 bug as a similar bug was reported earlier with
+ blank purple screen.
Public bug reported:
9-8-018
I suspect this is a gdm3 bug as a similar bug was reported earlier with blank
purple screen. This is running a fully updated fresh install september-8-018
some switch user operations function. Others result in a successful
appearance, but the machine is
gdm3 info. for above comment
matt@Wallace:~$ apt list gdm3
Listing... Done
gdm3/bionic-updates,bionic-security,now 3.28.2-0ubuntu1.4 amd64 [installed]
N: There is 1 additional version. Please use the '-a' switch to see it
matt@Wallace:~$ apt list gdm3 -a
Listing... Done
9-8-018 fresh install with updates .. some user switches work, some
don't logout is also crashing with irresponsive black screen. When the
user switch fails, the description is slightly different from above. If
the mouse pointer comes in at lower right, the user switch works. If it
comes in upper
This also affects 18.04 (updated to July 5, 2018)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724921
Title:
VLANs get incorrectly listed under Bluetooth
To
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Great news! Glad to hear it! I was surprised to see this issue still
around.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1650395
Title:
Large grey border around
Well, on Arch the issue, (as I said before) doesn't seem to be present.
However can't you just check yourself? It should be quite easy to
reproduce if it's still a bug. If it is, then as it says "Fix released"
for the upstream bug, then surely you can fix it downstream as well. And
if not, then we
@Robie, I run Arch now, so it would be best if someone else tested this,
otherwise if nobody is around other than me to test it then I will
happily do so in my QEMU VM. Just let me know if nobody gets back to you
about this in a while.
--
You received this bug notification because you are a
The upstream bug reports have been moved to:
https://gitlab.gnome.org/GNOME/gnome-calendar/issues/160,
https://gitlab.gnome.org/GNOME/gnome-tweaks/issues/75
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
** Bug watch added: GNOME Bug Tracker #761461
https://bugzilla.gnome.org/show_bug.cgi?id=761461
** Changed in: gnome-control-center
Importance: Wishlist => Unknown
** Changed in: gnome-control-center
Status: Invalid => Unknown
** Changed in: gnome-control-center
Remote watch:
The official upstream GNOME bug has been moved to here:
https://gitlab.gnome.org/GNOME/gdm/issues/342
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using
The official upstream GNOME bug has been moved to here:
https://gitlab.gnome.org/GNOME/gdm/issues/342
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1652282
Title:
Xwayland not using
** Changed in: gnome-terminal (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1770494
Title:
Does not display VT-100 control
This appears fixed in Ubuntu 18.04. I just checked in a virtualbox VM.
This can be closed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1770494
Title:
Does not display
** Description changed:
- I'm writing a shell script that draws in color to any VT-100 terminal.
+ I'm writing a shell script that draws in color to any VT-100 terminal.
The terminal in Ubuntu consistently and randomly drops out of graphics
mode producing huge glitches. This does not occur
I did the -proposed version if seems to me all is good (but I'm new to
this - so take it with a grain of salt).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541
Title:
All the excape codes were stripped from the description, please use the
attached screen-capture.txt file.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1770494
Title:
Does
Public bug reported:
I'm writing a shell script that draws in color to any VT-100 terminal.
The terminal in Ubuntu consistently and randomly drops out of graphics
mode producing huge glitches. This does not occur in Xterm or Gnome
terminal on CentOS.
Appearance:
The image from the file
Public bug reported:
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
apt-cache policy nautilus
nautilus:
Installed: 1:3.26.3-0ubuntu4
Candidate: 1:3.26.3-0ubuntu4
Version table:
*** 1:3.26.3-0ubuntu4 500
500
This is what I have for
$ lsof | awk '{ print $1 }' | uniq -c | sort -rn | head
17808 dropbox
6042 dropbox
3504 JS\x20Hel
3024 JS\x20Hel
2628 DNS\x20Re
2456 JS\x20Hel
2056 JS\x20Hel
1856 JS\x20Hel
1752 mozStorag
1600 JS\x20Hel
--
You received this bug notification
** Also affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1751797
Title:
dns resolution only works for
** No longer affects: maas
** No longer affects: nplan (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Changed in: cloud-init
Status: New => Confirmed
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Assignee: (unassigned) => Ryan Harper
** Bug watch added: github.com/systemd/systemd/issues #4762
https://github.com/systemd/systemd/issues/4762
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4762
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Bug watch added: github.com/systemd/systemd/issues #8328
https://github.com/systemd/systemd/issues/8328
** Also affects: systemd via
https://github.com/systemd/systemd/issues/8328
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Summary changed:
- transient boot fail with overlayroot
+ transient boot fail with overlayroot [open-iscsi dep8 tests]
** Attachment added: "bionic failure log 2.0.874-5ubuntu2
qemu/1:2.11+dfsg-1ubuntu2"
Public bug reported:
After reboot, dns was broken.
I've attached systemd-resolve --status output.
In order to file the bug I just modified /etc/resolv.conf to put the dns
server in directly.
Other information, it seems like it just will only look for dns under my
search domains from the dhcp
Public bug reported:
Description
===
What I expect to happen
---
When I move the cursor to one of the displays in the display control
panel and press down the left button I should be able to move the
display.
What actually happens
-
Now I have
Public bug reported:
Description
===
What I expect to happen
---
That the changes I've made in the display arrangement is the same after
starting the computer as before shutting it down or rebooting.
What actually happens
-
Both the display
Public bug reported:
Description
===
What I expect to happen
---
After changing the display arrangement the button *Apply* should be
available for me to press and apply the changes I've made.
What actually happens
-
After finishing the display
** Description changed:
1. $ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
2. $ apt-cache policy linux-image-`uname -r`
linux-image-4.13.0-16-generic:
- Installed: 4.13.0-16.19
- Candidate: 4.13.0-16.19
- Version table:
- *** 4.13.0-16.19 500
- 500
I just ran into this today:
Setting up avahi-utils (0.7-3.1ubuntu1) ...
dpkg: cycle found while processing triggers:
chain of packages whose triggers are or may be responsible:
gnome-menus -> ufw
packages' pending triggers which are or may be unresolvable:
gnome-menus:
Filed upstream as: https://bugzilla.gnome.org/show_bug.cgi?id=793049
Added above as bug watch (as described in comment #4's link).
[Sorry about comment #5 - my page only showed the text in the comment-entry box,
not yet as a confirmed comment - if someone can delete the duplicate comment,
my
** Bug watch added: GNOME Bug Tracker #793049
https://bugzilla.gnome.org/show_bug.cgi?id=793049
** Also affects: eog via
https://bugzilla.gnome.org/show_bug.cgi?id=793049
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
If you look at the right edge of the image, opposite to the "C", the
rest of the "C" as it fades out can be seen - but the dark area is to
the left, not the right.
This appears to indicate that the columns of pixels that are transferred
are brought over in reversed order (mirrored).
(If the
If you look at the right edge of the image, opposite to the "C", the
rest of the "C" as it fades out can be seen - but the dark area is to
the left, not the right.
This appears to indicate that the columns of pixels that are transferred
are brought over in reversed order (mirrored).
(If the
** Attachment added: "After roate"
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1746146/+attachment/5045292/+files/eog_rotate%26save_error2.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to eog in Ubuntu.
about 7 pixels wide))
----
scott@scott-Asus-M2N68-AM-PLUS:~$ uname -a
Linux scott-Asus-M2N68-AM-PLUS 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25
09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-Asus-M2N68-AM-PLUS:~$ lsb_release -dsc
I no longer use Ubuntu, I'm on Arch so I don't know for sure. But it's
not happening over here with GNOME 3.26.3 so I assume that the issue has
probably gone.
** Changed in: ubuntu-gnome
Status: New => Invalid
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete =>
** Description changed:
I much prefer GNOME Software to the Ubuntu Software Center, however I
believe that there is one thing lacking in GS which is present in USC,
the installation and uninstallation history. That is, the history of all
packaged which have been installed and uninstalled,
** Description changed:
Some religious as well as regional calendars (e.g.: the Japanese
calendar) start the week with Sunday as opposed to Monday. I think that
there should be an option in the gnome-tweak-tool to make it so that the
weeks are displayed as starting on Sunday in the
I hadn't noticed this bug in a while. And then suddenly yesterday (on
Arch Linux) it appeared!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/;
qemu-system-x86_64 -enable-kvm -m 768 \
-net
Well, I do not have 'Sticky keys' enabled now, and I doubt I ever did.
It really felt to me that the lock screen and "everything else" seemed to keep
independent state for shift (or caps lock possibly), and I happened to get them
out of sync.
I'm fine for this bug to expire, but figure I'd at
Public bug reported:
I received this error message on logging into cinnamon. This error
message popped up with out me doing anything other than logging in. I
do not know if it is related, but before logging in with cinnamon I
logged in with openbox which was having problems itself.
This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of
on Ubuntu 17.04 am seeing high CPU upon launching Chrome 63.0.3239.70-1
however after about 60 seconds it finishes and CPU usage returns to normal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
Public bug reported:
I press Ctrl + F to open up the search bar to search but I find that
immediately after I press Ctrl + F, the bar closes and resets to its
original state. I can visibly see the bar show up as well as it closing
immediately. I have tested this functionality in the
Public bug reported:
I accidentally opened a 7.8 MB text file with gedit and closed it. From
what I could tell, it looked like it exited fine but evidently it
didn't.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gedit 3.22.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic
zesty does not show this problem. neither does xenial. I reflected that
in the status.
** Changed in: cloud-init (Ubuntu Artful)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: cloud-init (Ubuntu Artful)
Importance:
$ wget http://cloud-images.ubuntu.com/artful/20171122/artful-server-
cloudimg-amd64.img
## set up dns locally for 'qemu-host' to the default ip for user networking.
$ grep qemu-host /etc/hosts
10.0.2.2 qemu-host
$ cat data/user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
Public bug reported:
After right clicking for the context menu on the Show Applications
button the context menu option "Dash to Dock Settings" doesn't open up
the dock settings in gnome-control-center but the shell extensions menu
instead.
1.
Description:Ubuntu Bionic Beaver (development
This isn't a new bug, but it has been fixed in the past. I'm not sure
whether to make a new bug or just link to it so it inevitably gets
reopened. I'll post the link to the bug here:
https://bugzilla.gnome.org/show_bug.cgi?id=746798
** Bug watch added: GNOME Bug Tracker #746798
Just to clarify, the Dock item in the gnome-control-center was
populated.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1734196
Title:
gnome-control-center: Ubuntu
1 - 100 of 2659 matches
Mail list logo
