I am seeing similar interactivity issues on fully updated 22.04 on a Dell
Precision laptop with Nvidia + X11 that started a day or so ago. Most
noticeable in the terminal with lag/stuttering and seemingly lost keyboard
inputs, but also affecting other apps with stuttering keyboard inputs and
Public bug reported:
The display settings are stuck at 2560x1440 x 93Hz
xrandr says:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 2560 x 1440, current 2560 x 1440, maximum 2560 x 1440
default connected primary 2560x1440+0+0 0mm x 0mm
2560x1440 93.00*
ubuntu-
> bug' and the name of the package affected. You can learn more about this
> functionality at https://wiki.ubuntu.com/ReportingBugs.
>
I'll try to remember to do that in future :)
BW,
Ian
--
-- ACCU - Professionalism in programming - http://www.accu.org
-- My writing - https://sites.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2012135/+attachment/5655331/+files/ProcEnviron.txt
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2012135/+attachment/5655330/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
Nautilus does not resize window when WIN+left or right arrow pressed.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.25
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop:
Public bug reported:
Nautilus does not resize window when WIN+left or right arrow pressed.
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in
.. and the PPA means I am now running the 510 drivers successfully.
Thanks again, Martin.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1960621
Title:
MATE Desktop session
It turns out that I may have misunderstood - the same thing happens for
me when telling MATE Tweak that I want to use Compiz rather than Marco
as my window manager.
The switch to Compiz certainly happens (I am reminded of why I stopped
using it..) and it is sticky between reboots.
So either it's
Thank you, Martin.
I do indeed have Marco with the 'adaptive compositor' (it's the default,
I think...)
It's been ages since I used Compiz, but... :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
Public bug reported:
On Impish 21.10, gnome-shell freezes up when trying to login,
specifically after I have typed in my password and hit enter. I have
seen this both when logging in after the display shuts itself off after
whatever the automatic timeout is, and also after manually locking the
Also I'm not sure I agree with jdstrand's apparmor profile which
includes:
/run/snapd.socket rw,
which I don't think we want to grant to any PDF file opened with evince?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in
Public bug reported:
At seemingly random intervals throughout the day gnome-shell becomes
very active, the CPU gets very busy and the fans kick in because of the
large load.
I attached health-check to the busy process for 60 seconds and got the
following utilization stats:
sudo health-check -p
** Attachment added: "ASCII log of health-check analysis"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943434/+attachment/5524939/+files/health-check-report.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This has occurred at 3 fresh installs of 21.10 on this laptop
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1939938
Title:
dialog asking for restart appears on close of
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
Public bug reported:
following last update to rhythmbox dialog box now appears at every
closure of rhythmbox from top bar
Ubuntu 21.10 image from 13/08
lenovo thinkpad T430
250gb ssd 16gb ram
** Affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
--
You received
I have the same sort of issue... Ubuntu 20.04 (Ubuntu Studio spin).
>From Xorg.0.log
[ 13886.780] (EE) client bug: timer event4 debounce short: scheduled expiry is
in the past (-9ms), your system is too slow
[ 13926.080] (EE) client bug: timer event4 debounce: scheduled expiry is in the
past
Public bug reported:
Automatic upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-0 2.48.2-0ubuntu4.8
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474126/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474125/+files/lspci.txt
** Attachment removed: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1912246/+attachment/5474124/+files/prevboot.txt
--
You received
Here's lspci
--
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/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
Here's lspci
--
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/1912246
Title:
[nvidia] gnome-shell freezes randomly
To manage notifications about this bug go to:
Okay, so this time when it happened at Sun Mar 7 02:44 AM UTC 2021,
here are the logs. I did not find any crash files in /var/crash, and
there were no results for my whoopsie-id either.
The journalctl output is attached
** Attachment added: "prevboot.txt"
Here's lspci
** Attachment added: "lspci -kv"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1912246/+attachment/5471916/+files/lspci.txt
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell-extension-ubuntu-dock
Hey so sorry I missed that you wanted me to run those commands before,
but it happened again this morning and here are the requested logs and
lspci output. Note that I stripped out all the messages from snapd since
I have debug mode enabled and it's extremely noisy, but if you think
snapd could be
So I disabled both ubuntu-dock and the desktop icons extensions and
still see the freezes, here's a log of gnome-shell:
https://pastebin.ubuntu.com/p/CXCfTVtkMJ/
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Public bug reported:
The symptoms here for me are exactly the same as described in
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1912246 where after starting up my Groovy system with X11 and
proprietary NVIDIA drivers the desktop session just hangs for a
Unfortunately, I seem to be on that version of gnome-shell-extension-
desktop-icons and still experience the freeze when I enable the desktop
icons extension. Here's the dpkg output and gnome-shell logs:
https://pastebin.ubuntu.com/p/yqDTV5KBmC/
** Changed in: gnome-shell-extension-desktop-icons
So indeed after enabling _only_ the Desktop Icon extension I experienced
a freeze. Here are the logs: https://pastebin.ubuntu.com/p/XwJS7N4tF5/
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop
So after a full day of usage yesterday I did not see the freeze/crash at
all, so it does indeed appear to be caused by one of the extensions
bundled with Ubuntu. Should I try just enabling them one-by-one using
the Extensions app?
I can't remember what all Extensions are enabled by default, but I
Well for the short bit that I've been using the system after disabling
all the extensions through the Extensions app, I have not experienced
any freeze. I will report back after the end of the day if I see any
more freezes though.
Interestingly, after disabling all Extensions, I have no more dock
Hi Daniel, I disabled all of these extensions, and then rebooted the
machine and still a minute or two after logging in again experienced the
freeze. Here are the logs from gnome-shell:
https://pastebin.ubuntu.com/p/YKtMQ2qy4g/
Note, I only disabled the extensions located in ~/.local/share/gnome-
Public bug reported:
I recently upgrading from Focal to Groovy, and use proprietary NVIDIA
drivers with X11 with otherwise standard GNOME, but some extensions
installed. I see frequently errors relating to the dash-to-dock
extension which I'm not sure are related, but I also see that gnome-
shell
Public bug reported:
The gdm3 package comes with a session launcher script /etc/gdm3/Xsession which
starts
everything up. In that script it unconditionally executes $HOME/.profile (if
it exists).
But this is not necessarily the correct shell startup file.
If your shell is bash and you have a
Is there any other way that I'm not thinking of to fix this?
** Changed in: gnome-bluetooth (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/gnome-bluetooth/+question/693642
--
You received this bug notification because you are a
Public bug reported:
Whether going into the settings and enabling the bluetooth or using
rfkill to unblock it, the bluetooth remains disabled. I've added myself
to the bluetooth group and this did work until the next restart. After
blocking it the indicator icon shows up, but upon unblocking
Public bug reported:
I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3
install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run
sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in
Public bug reported:
With Ubuntu 20.04, GDM 3.34.1 (bundled with Focal), and the proprietary
NVIDIA drivers, I am unable to use Wayland to login, and can only use
XOrg. Debugging this a little, I found that wayland support is wholesale
disabled when proprietary NVIDIA drivers are used by this
Thanks folks, this works for me now as well.
--
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/1825593
Title:
Display scale not remembered when X11 Fractional Scaling is enabled
To
Daniel, it sounds then like you are saying this is a duplicate of
1873403?
--
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/1869042
Title:
[nvidia] fractional monitor scaling fails
(the issues here originally were that the screens go black and that I
couldn't set the main monitor after changing scaling, for which I filed
1873266, as per your request)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Summary changed:
- [nvidia] cannot change main monitor after setting scaling for monitors
+ [nvidia] with x11 fractional scaling enabled, cannot change main monitor
after setting scaling for monitors
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Okay, so now looking back at this bug, I see that when I have Focal with
X11 and the 440 nvidia drivers enabled, I can set scaling to integer
multiples without problems, but enabling fractional scaling and then
using a fractional scaling results in the black screen problem mentioned
in this bug as
Daniel, I just turned off fractional scaling and I no longer have this
problem, so for me at least with nvidia drivers and focal, I don't see
this bug and instead see 1825593 as you mentioned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Also, if I disable Fractional Scaling, it now works to use/apply these
settings in any order
--
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/1873266
Title:
[nvidia] cannot change
Yes, 'Fractional Scaling' is enabled, sorry I should have specified. I
am unable to actually use fractional scaling however due to
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification
Hi Daniel, I tried your instructions and there is no difference between
~/.config/monitors.xml and monitors-before.xml. Both files specify the
desired configuration, but upon logging in the monitors are in the wrong
configuration.
Let me know if there's anything else I can try to help debug this
Hi Daniel,
> Since your setup only uses gnome-shell in the host and not the guest
it
Host is KDE Plasma, guest is GNOME => I have problems with clipboard
when I close virt-manager or shutdown the guest => no problems
So if I remove GNOME from the equation, then it's OK.
--
You received this
Hi Daniel,
Thank you for coming back to me so fast.
I don't think it's related to either of those bugs you mentioned. This
is happening only when I'm running virtual machines and have "virt-
manager" opened.
Is it a bug in gnome-shell? It's difficult to say. I'm not experiencing
the issue with
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1873266/+attachment/5356137/+files/ProcCpuinfoMinimal.txt
** Changed in: mutter (Ubuntu)
Status: Incomplete => Opinion
** Changed in: mutter (Ubuntu)
Status: Opinion => New
--
apport information
** Tags added: apport-collected focal package-from-proposed
** Description changed:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first
a couple of years ago.
Thank you all great people in Canonical for Ubuntu.
Ian
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
Uname: Linux 5.4.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture
Daniel, I filed that issue as
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873266
--
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/1869042
Title:
[nvidia] all monitor
Public bug reported:
After booting with nvidia drivers, if I change which monitor is the main
one first, then change the scaling from 100% to 200%, it works. But
doing this in the inverse direction, by first setting the scaling and
then changing the main monitor, it fails and the screens go
I should point out that the behavior in comment #9 happens when I am
using the nvidia 440 drivers.
I still cannot use fractional scaling with the nvidia drivers
successfully under any ordering, but I can at least use 200% scaling if
I set it first, then set the main monitor it works.
--
You
Just to clarify, I still see this bug with Focal and X11 and nvidia
drivers
--
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/1292398
Title:
Second screen position isn't saved
It is still unfortunately happening to me, but I also have a new
permutation of this, my machine also happens to suffer from
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1292398, so when I
boot up my machine the incorrect monitor layout is present, and I find
that if I first set the main
Is this perhaps a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869750 ?
--
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/1869042
Title:
[nvidia] all monitor
Actually after testing this out, I was able to use fractional scaling
with X11 again by using the nouveau driver instead of the proprietary
nvidia driver, which on my machine is at nvidia-440. This is a
sufficient work-around for me, it's unfortunate I can't use the
proprietary nvidia driver with
FWIW, if I switch to using the noveau driver and then login via Wayland,
I can enable fractional scaling through Settings and that is successful,
but unfortunately then all the text in some apps becomes rather blurry.
--
You received this bug notification because you are a member of Ubuntu
Oddly enough I was able to get 200% scaling to work randomly by not
quite lining up all the monitors and offsetting them from each other in
the settings window.
Is there anything I could try manually to unbreak the situation or is
there a debian package I could downgrade to in order to get
Attaching monitors.xml since it doesn't seem that apport picked it up
** Attachment added: "~/.config/monitors.xml from my system"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml
--
You received this bug notification because you are a
Public bug reported:
After an upgrade with focal-proposed this morning, I am unable to set
any scaling for any of my monitors without the monitor turning blank for
15 seconds and reverting to 100% scaling.
I am using X11 with gnome and proprietary nvidia drivers on Focal. I
have 3 monitors
Just to be clear, the messages:
```
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
```
are normal and harmless.
--
You received this bug notification because you are a member of Ubuntu
Desktop
Public bug reported:
Installing from Ubuntu Software store
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: gimp-data (not installed)
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date:
Originally assigned to wrong package, sorry - I thought I had selected
the right one, but hadn't pressed enough buttons!
** Package changed: nvidia-graphics-drivers-435 (Ubuntu) => gimp
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks for your prompt response Sebastien.
Sorry i thought i had remembered there being a default notification
sound in older versions of Ubuntu/gnome and thought this was a
regression. My mistake.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
If it's any bit of helpful information, I occasionally have this issue
(on 18.04) and it is fixed by a proper shutdown and boot. It seems to
happen for me when one of the servers that I sshfs to crashes/becomes
unavailable (or something else server side) and the issue persists past
the time in
Public bug reported:
gsd-housekeeping is opening /etc/fstab every 60 seconds and because it
is being opened without the O_NOATIME flag the access time updates are
causing regular meta data flushes. On an idle laptop this can cause the
HDD to spin up, flush write and spin down every 60 seconds.
Public bug reported:
I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gsd-color opens
/usr/share/zoneinfo/Europe/London on my machine at regular intervals.
This causes the access time (atime) to be updated causing a
Oh, actually, it was doing 10 accesses in 300 seconds, so it's polling
every 30 seconds, higher than I first thought.
** Summary changed:
- gnome-calendar opens /usr/share/zoneinfo/* every 60 seconds
+ gnome-calendar opens /usr/share/zoneinfo/* every 30 seconds
** Changed in: gnome-calendar
Public bug reported:
I've been trying to figure out why my HDD keeps on flushing metadata out
every minute on an idle laptop and discovered that gnome-calendar opens
/usr/share/zoneinfo/Europe/London on my machine every minute. This
causes the access time (atime) to be updated causing a metadata
Looking good on 18.04.1 LTS Desktop. I have installed the patch from
comment #23 and the network icon now appears consistently on both the
status bar and the status menu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
This affects a new snap we uploaded with license metadata to the store
around December 2018. We uploaded the snap and used the snap store
description editor to choose "Other Open Source" software and it shows
up as "Proprietary" in gnome-software.
--
You received this bug notification because
According to https://gitlab.gnome.org/GNOME/gnome-shell/issues/140 this
is fixed in Gnome Shell 3.30.1 & 3.28.4. Any chance of getting 3.28.4
(or the fix) in 18.04 LTS desktop?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Uncommenting this line worked for me. This bug occurred after a fresh
install of 18.10.
--
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/1798790
Title:
Ubuntu login screen never
Public bug reported:
/usr/lib/tmpfiles.d/00rsyslog.conf (in the rsyslog package) includes
these lines:
# Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
# the syslog group, so that rsyslog can run as user.
# See tmpfiles.d(5) for details.
# Type PathMode UID GID
I am experiencing this on Ubuntu 18.04 with evince 3.28.2-1. A possible
regression?
--
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/1579142
Title:
Evince windows cannot be
I deem that it should be removed, it is too much of a maintenance
overhead and has way too many issues to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1758163
Title:
Public bug reported:
I was running the new stress-ng softlockup stressor and observed that
systemd-journald gets killed with an abort and this corrupts the systemd
journal.
How to reproduce:
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make clean; make
sudo ./stress-ng
Public bug reported:
Ubuntu GNOME 17.04 with GNOME 3.24.
gnome-control-center:
Installed: 1:3.24.1-0ubuntu1
Candidate: 1:3.24.1-0ubuntu1
What actually happened:
When I open settings, I find that my perfectly innocuous Region & Language
settings have been kidnapped by a stranger named Lan
I think this is a systemd/udevd kinda bug isn't it?
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I've instrumented a kernel so I can clearly see when processes start and
exit, this allows me to see when exactly the kernel has handed off
control to userspace. The time the kernel actually takes to initialize
compared to the time systemd-analyze reports are different.
$
This affects me, the search does not work, which is a real pain for
large documents of thousands of pages; not being able to search makes
the tool unusable for large docs.
** Changed in: evince (Ubuntu)
Status: Expired => Confirmed
** Changed in: evince (Ubuntu)
Importance: Low =>
Public bug reported:
Several errors reported during installation, all seemd related to
amd-64.
However on reboot, everything seems to be working, but the system has
aksed for several erros reports, all of which have been completed. This
post is therefore responding to system requests and has
This has been reported in a couple other places, like
https://bugzilla.redhat.com/show_bug.cgi?id=1303300. It seems that many
people encounter it (and this is the case for me) when on a network with
one of those horrible DNS-hijacking landing pages that are all too
common among USA ISPs.
** Bug
A few discoveries in 15.10:
1. This bug doesn't affect non-URL type files.
2. (URL files only) Comment four doesn't work for me. Nautilus just crashes and
all my files disappear until I log out and log back in.
3. (URL files only) If I repeat comment four with a file instead of a
directory, it
The upstream bug mentioned by Michael in comment #6 was fixed in
libsmbclient 4.1.18 and 4.2.1.
--
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/1401917
Title:
GVFS Samba mounts time
Public bug reported:
Eye of GNOME doesn't display an error if the currently-viewed image is
deleted. For example, if you open an image in EoG, close it, delete the
image, then attempt to open the image from recent, you will receive an
error stating No images found in
Public bug reported:
When trying to open a video file from Ubuntu 14.04.3 Daily Image
(2015-07-29), it will not open. If totem is manually run from the
terminal, this error occurs:
totem: error while loading shared libraries: libwayland-egl.so.1: cannot
open shared object file: No such file or
Public bug reported:
I noticed that systemd on my idle Wily desktop is creating very short
lived threads at 1Hz. While these aren't doing much, it still consumes
power doing wakeups to create these periodic threads.
Showing thread creation with forkstat:
$ sudo forkstat
Time Event PID
Recommend closing this bug, I can't reproduce it now.
--
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/962825
Title:
Menubar still shows when off by default
To manage
Public bug reported:
For reasons I cannot fathom, my development server goes into deep
suspend after ~3 minutes after startup with systemd, however, if I boot
with upstart it does not. This happens everytime I boot with systemd,
the machine just goes into a deep suspend without me requesting
Public bug reported:
I believe this is a change in shutdown tied somehow to systemd, but I am
guessing.
How to reproduce the bug:
sudo shutdown -h now
[ wait a couple of minutes, don't enter in one's password ]
authentication times out and one is left with non-echo on one's tty.
This has to be
I'm guessing this is a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/897188
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1308648
Title:
Getting this same behavior on 14.04 LTS. I'm sad to see that this has
been reported for so long and doesn't have any activity. Is there any
further information I can provide to help with troubleshooting?
Of note: after a suspend, not only will my accounts fail to update
automatically, but if I
In reference to Milton's comments (and thanks for the follow-ups) - my
problems (listed in #11) are *not* related to a post-suspend loss of
wifi. My problems happen consistently on a fresh boot.
Frankly my E6420 can be 'wobbly' after suspend (it has been since 10.10)
so I rarely suspend (it can
I'm seeing this on 14.04 (Linux mint 17), 64 bit. I can't help but
remember that I've seen this bug over the years.
Two scenarios:
1) Edit|Preferences, Resources tab, Update interval is shown as 0.00, you can
adjust it, Close, then if you go back it'll be marked as 0.00 (although the
update
Public bug reported:
Steps to reproduce:
1. Under notebook's DC mode, prepare the big file in internal HDD.
2. Plug-in the USB flash storage (DOK/SD card) and translate the file from the
Internal HDD to it.
3. Plug-in the AC during file transferring, found file transfer speed become
slowly or
1 - 100 of 651 matches
Mail list logo
