Hi, this issue is reproduced on my 17.04 system with lightdm display
manager.
--
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/1652618
Title:
Impossible to unlock the screen when
Public bug reported:
Hello!
This record is for bug evidence in ubuntu 17.04 nautilus 3.20.4
Please check this bug.
Bug occur when renaming folder in korean after creating folder!
May be unicode bug...
https://youtu.be/G_FcGdn20eE
My computer using ubuntu 17.04
i5-6200u
ram 4gb
cybertr...@nate.
On Latest 17.04, killall nautilus and restarting nautilus doesn't help.
Maybe I am not doing the right thing in detail.
So for a couple of years now, every time I present something at a
conference, I panic because I'm not going to be able to write my PDF
file on a USB key in order to share it -- t
*** This bug is a duplicate of bug 1722024 ***
https://bugs.launchpad.net/bugs/1722024
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1722024, so is being marked as such.
How long until this fix is pushed downstream to Ubuntu and GNOME
Software? The issue is present in Ubuntu 17.10 64-bit Beta 2 Artful
Aardvark.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launc
*** This bug is a duplicate of bug 1702473 ***
https://bugs.launchpad.net/bugs/1702473
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1702473, so is being marked as such.
*** This bug is a duplicate of bug 1721064 ***
https://bugs.launchpad.net/bugs/1721064
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1721064, so is being marked as such.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https:/
*** This bug is a duplicate of bug 1701289 ***
https://bugs.launchpad.net/bugs/1701289
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1701289, so is being marked as such.
** Branch linked: lp:~gunnarhj/gnome-session/lp1722002
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1722002
Title:
Ignore the "region" gsettings value
To manage notificati
** Changed in: gtk
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1712011
Title:
Unable to close Printer properties
To manage notification
I tried also: sudo su -c 'echo 10 >
/sys/class/backlight/acpi_video0/brightness'.
Pressing the Fn keys brings up the OSD brightness control, which
reflects the value of the /sys/class/backlight/acpi_video0/brightness
file (and viceversa), but the actual screen brightness does not change.
--
You
** Changed in: evolution
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/139393
Title:
evolution filters must be specific for mailboxes
To manage notifications a
Interestingly the .djvu file of the same images from the torrent works
smoothly and without incident. the PDF claims to be a PDF/A of some
variety, so I'd have assumed it was less complicated a dataset than
most!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
@brinstar, yes I did the sudo update-grub part, and tried
acpi_brightness=[native|vendor] which for me makes the Fn hot keys not
working (when you press them, no brightness icon appears).
Last update brought in NVidia drivers 384.90, but no joy, the problem is
still present.
--
You received this
Public bug reported:
The PDF from https://archive.org/details/kamikiukulelemet00newy
displayed fine under zesty, but under artful it shows up as lots of
blank white pages. This is the same under other PDF viewers, so I
suspect the real bug is in one of the shared libraries used by all of
them.
P
Public bug reported:
Demonstration: https://www.youtube.com/watch?v=gIUq196KnVg
The lock screen cover can't be dismissed with a double-click or double-
tap. The only methods to dismiss it is by pressing a keyboard key or
dragging the mouse up while holding click, the latter of which is
unintuitiv
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-power-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://b
Public bug reported:
Video demonstration: https://www.youtube.com/watch?v=Sbn-02k_n9E
The "Launch" button in Ubuntu/GNOME Software does not always work.
Launching the same program from the GNOME interface or the Terminal
works fine.
Tested on Ubuntu 17.10 64-bit Beta2 Artful Aardvark.
** Affect
Public bug reported:
https://i.redd.it/ellp7c7yggqz.png
Some free (gratis) packages require logging in with a Snap Store account
in Ubuntu/GNOME Software.
This is, quite frankly, ridiculous. I should not need an account to
install any software. Neither should anyone else. These packages are
avai
Public bug reported:
The /usr/bin/gnome-session wrapper sets some LC_* variables based on the
"region" gsettings value. Since we rely on ~/.pam_environment for those
variables, setting them from /usr/bin/gnome-session is redundant, and
may occasionally cause unexpected behavior.
** Affects: gnome
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display".
---
After debugging that a little bit more I can see that the bug is not
triggered if I do not change scaling from 10
Public bug reported:
Attached screenshots for "before applying" and after.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm n
** Attachment added: "After"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+attachment/4964664/+files/after.png
--
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/
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-she
Public bug reported:
Using default login on 17.10 Beta, which I believe is Wayland, when
Universal Access > Zoom is selected the mouse cursor disappears. The
mouse continues to function, but no cursor is visible.
It is ok when used with X login.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Packa
After trying to install it gives me:
Running Steam on ubuntu 16.04 64-bit
STEAM_RUNTIME is enabled automatically
Installing breakpad exception handler for appid(steam)/version(0)
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver:
I read up on this one on the link provided. If Ctrl q is not allocated,
it should be easy to close the current version. Surely you have a linux
build. It is very standard to have ctrl Q not ctrl W
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
I read up on this one on the link provided. If Ctrl q is not allocated,
it should be easy to close the current version. Surely you have a linux
build. It is very standard to have ctrl Q not ctrl W
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
Seems to have gone away with recent upgrades. I can't tell exactly which
as I was attempting to use wayland under amd and even under nvidia-387
(which worked fine except for a couple of random system freezes during
closing windows). Back on nvidia/xorg because of that (although not
exhaustively tes
*** This bug is a duplicate of bug 1556601 ***
https://bugs.launchpad.net/bugs/1556601
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1556601, so is being marked as such.
*** This bug is a duplicate of bug 1701843 ***
https://bugs.launchpad.net/bugs/1701843
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1701843, so is being marked as such.
https://bugzilla.gnome.org/show_bug.cgi?id=788630
** Bug watch added: GNOME Bug Tracker #788630
https://bugzilla.gnome.org/show_bug.cgi?id=788630
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https
33 matches
Mail list logo
