gitlab closed the issue as not belonging there
--
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/1798828
Title:
gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
reported upstream at https://gitlab.com/gitlab-
org/gitlab/-/issues/233169
** Bug watch added: gitlab.com/gitlab-org/gitlab/-/issues #233169
https://gitlab.com/gitlab-org/gitlab/-/issues/233169
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
after reboot the Trash icon shows empty
--
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/1798828
Title:
gvfsd-trash fills up memory (uses about 1 GB) if Trash contains
thousands of
copied from Bug 1798828
--
Ubuntu LTS 16.04.6
118K files in trash
gvfs-trash consumes both CPUs and 100% of available memory
"empty trash" goes into prepare phase, but nothing appears to happen,
presumably because of the large number of files, so I closed the window
by clicking the
rm -rf
Ubuntu LTS 16.04.6
118K files in trash
gvfs-trash consumes both CPUs and 100% of available memory
"empty trash" goes into prepare phase, but nothing appears to happen,
presumably because of the large number of files, so I closed the window
by clicking the
rm -rf ~/.local/share/Trash/*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
It seems the bug that actually describes the "cannot rotate monitor to
portrait mode" issue is 1874567, and a fix is in hand. Apologies for the
noise here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
The workaround for me was to disable vt_handoff in /etc/grub.d/10_linux*
(i.e. set vt_handoff=0 in both places near the top of the file).
That resolved the issue completely.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Joe - I'm glad to hear that it is working and that Debian has also
updated their code. I'm glad that it helped others!
--
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/1876286
For anyone interested in a workaround:
It looks like if you import both the public and private key manually
into ~/.ssh (may also need to sudo systemctl restart gdm) and then run
seahorse again, they should show up.
--
You received this bug notification because you are a member of Ubuntu
Issue did return for me. You can always take a picture of the screen
with your phone if screenshot does not capture the cursor. I did take a
picture of it happening in 19.10 as well (attached)
** Attachment added: "IMG_6554.jpg"
@Syver Stensholt,
I don't think it's possible to screenshot it. The screenshot does not
capture the cursor even though it's there when the screenshot is taken.
When I notice the 2nd fixed mouse cursor icon, if I reboot the machine,
it goes away. But then at some point the 2nd fixed mouse cursor
Daniel,
As requested, I enabled Wayland and logged in with 'Ubuntu on Wayland'.
The second monitor is now working.
Thank you. I am very impressed with the quick turn around and support.
Jim Battis
On 7/30/20 10:11 PM, Daniel van Vugt wrote:
> Thanks. It looks like Xorg is the cause of this
Thanks, it looks like it has already been reported upstream.
I have added a remote bug watch.
https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
** Bug watch added: gitlab.gnome.org/GNOME/seahorse/-/issues #205
https://gitlab.gnome.org/GNOME/seahorse/-/issues/205
** Also affects: seahorse
IMO we shouldn't split the bug unless there's evidence of an unrelated
cause in cases where there's no overlap.
I'm not convinced that blaming it on Nvidia isn't justified. The xrandr
CLI tool cannot directly fix a broken monitor layout; usually it turns
off one monitor and spits out an error. In
Another video capturing user troubles:
https://www.youtube.com/watch?v=s_VDmBIG6os
--
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/1874217
Title:
[nvidia] Dual monitor setup with
Either the bug title should be renamed to something more generic or a
new bug should be created. As far as I can tell, many users have this
problem but don't necessarily have the screen overlap issue. At least,
overlap is not mentioned in [the reddit
I'm also having this issue, even with the latest Ubuntu 20.04. I tried
taking a screenshot of it with Spectacle, but when it asked me to draw
rectangular region both my screens blacked out and came back every
second. This removed the extra cursor too, which is weird and might
suggest the two
Still unable to import .p12 and .cer certificates on Ubuntu 20.04.1 LTS
/ GNOME 3.36.3 / Seahorse 3.36.
--
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/1771880
Title:
I am getting this error while installing hostapd, lighttpd and isc-dhcp-
server on Kali Linux. How can I fix this error and install these
packages?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
** Attachment added: "gnome-shell's text is not scaled"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889777/+attachment/5397417/+files/Screenshot%20from%202020-07-31%2015-33-17.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
I have set the text scaling factor to 1.25 using gnome-tweaks. However,
every time I log in, gnome-shell text is not scaled. Other apps (GTK,
electron, firefox) are scaling correctly.
I am using Ubuntu 20.04.1 with gnome-shell version
3.36.4-1ubuntu1~20.04.1.
ProblemType:
The issue is super small text in all GDM and GNOME Shell elements when
the display is being driven by NVIDIA graphics. The problem is caused by
the patch in the title. If you switch to Intel graphics, the text is
back to normal. If you switch to NVIDIA, the text shrinks down to what
looks like 50%
To maintain a respectful atmosphere, please follow the code of conduct -
http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are
handled by humans, the majority of whom are volunteers, so please bear
this in mind. Venting frustration in a bug report isn't fine.
The bug is triaged with
This is really amazing. I still have the same problem.
And yes, it is NOT triaged.
I have Ubuntu 18.04.4 LTS. LibreOffice is version 6.0.7.3.
I would expect some things just work in 21tg century. But obviously, I
am wrong.
Maybe the problem is, that Ubuntu developers does not use encryption
Sorry but there is no recording on how and when the key was change,
could be that you used some configuration interface that includes a such
option. Anyway closing since it's not really a bug in the software
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks, it's probably better if you could report it directly to the
software writers on
https://gitlab.gnome.org/GNOME/seahorse/-/issues
** Changed in: seahorse (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I've done more research and this may be related to xorg from what I've
been reading. This has also been an issue since ubuntu 17. So many
people have this problem and it's not been fixed 3 ubuntu versions down;
google search xorg media key lag. In summary short spike of cpu usage
when
28 matches
Mail list logo
