Being a more or less "normal" user, I find this behaviour highly
unexpected.
When I decide for auto-login, I do decide that access control to my
computer is carried out by my house door and its locks, I do not want to
be bothered with password prompts after every resume.
--
You received this
** Also affects: gnome-desktop3 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-desktop3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-desktop3 (Ubuntu Cosmic)
Importance: Undecided => Critical
** Changed in:
Public bug reported:
after upgrading to 16.04 from 14.04, I found that all file open dialog
lost the address bar (location entry). The only thing to navigate
between folders is the breadcrumb bar. Every path change requires a
dozen of clicking, while before I could just paste the path and done.
Still happens. Ubuntu 18.10
Confirmed by:
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/57#note_374389
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/57#note_377029
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I had the same issue and the workaround did *not* help; `cdrdao` is 4711
(and just for good measure I changed `wodim` too), but brasero still
hangs. I saw elsewhere that `xfburn` still works - and so it does, but
without cd text information. Does *that* need sudo permission too,
maybe? I have no
** Also affects: gtk+3.0 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gtk+3.0 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: gtk+3.0 (Ubuntu Bionic)
** Also affects: gtk+3.0 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gtk+3.0 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gtk+3.0 (Ubuntu Bionic)
Importance: Undecided => Low
** Changed in: gtk+3.0 (Ubuntu Bionic)
Status:
... sorry, on a bit further experimentation, it worked when I disabled
"burnproof", which I frankly don't understand (what it is *or* why
disabling it would help). I remember having trouble with burnproof in
the distant past and had tried to disable it before I knew to change the
cdrdao
** Changed in: poppler (Ubuntu)
Status: New => In Progress
** Changed in: poppler (Ubuntu)
Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
This bug was fixed in the package hwdata - 0.290-1ubuntu0.18.04.1
---
hwdata (0.290-1ubuntu0.18.04.1) bionic; urgency=medium
* Change PNP vendor name for GSM to LG Electronics (LP: #1755490)
-- Dariusz Gadomski Tue, 27 Nov 2018
09:10:48 +0100
** Changed in: hwdata (Ubuntu
Public bug reported:
Steps to reproduce:
1. Install Ubuntu 18.10
2. Download some deb-file to the desktop - for with help of terminal:
cd ~/Desktop
apt-get download meld
3. Install GDebi package installer with
sudo apt install gdebi
4. Select deb-file on desktop, make right
** Description changed:
after upgrading to 16.04 from 14.04, I found that all file open dialog
lost the address bar (location entry). The only thing to navigate
between folders is the breadcrumb bar. Every path change requires a
dozen of clicking, while before I could just paste the path
This bug was fixed in the package shotwell - 0.30.1-0ubuntu3
---
shotwell (0.30.1-0ubuntu3) cosmic; urgency=medium
* debian/patches/git_notification_segfault.patch:
- direct: Fix crash when dismissing modifications (lp: #1723181)
-- Sebastien Bacher Wed, 07 Nov 2018
The verification of the Stable Release Update for shotwell has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
I'm still experiencing high power consumption with GDM3 on Cosmic with
0.8.10 of nvidia-prime. Can provide logs/hardware info if it's helpful,
just let me know what you need. Nouveau or manually disabling the DGPU
in the BIOS behaves as expected.
--
You received this bug notification because you
is the issue only happening on the desktop view? does it work in
'normal' directories?
** Package changed: nautilus (Ubuntu) => gdebi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Public bug reported:
Steps to reproduce:
1. Install Ubuntu 18.04 LTS
2. Login to default GNOME Shell session
3. Copy some application icon to the desktop - for example with
cp /usr/share/applications/gedit.desktop ~/Desktop/
chown +x ~/Desktop/gedit.desktop # for sure
4. Minimize all
The screenshot is a gtk one, the issue sounds like an upstream one
though
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu)
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
And Ubuntu 18.04 LTS (xenial) is affected too.
** Description changed:
Steps to reproduce:
- 1. Install Ubuntu 18.10
+ 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10
2. Download some deb-file to the desktop - for with help of terminal:
- cd ~/Desktop
- apt-get download meld
+
This happens only on desktop. Which is controlled by `nautilus-desktop`
executable (part of `nautilus` package).
So I think that GDebi is not really affected.
I assume that pkexec-ed applications are not runnable from `nautilus-desktop`.
** Also affects: nautilus (Ubuntu)
Importance:
** Tags added: cosmic disco
** Description changed:
Steps to reproduce:
1. Install Ubuntu 18.04 LTS
2. Login to default GNOME Shell session
3. Copy some application icon to the desktop - for example with
- cp /usr/share/applications/gedit.desktop ~/Desktop/
- chown +x
I'm still experiencing high power consumption with GDM3 on Cosmic with
0.8.10 of nvidia-prime. Can provide logs/hardware info if it's helpful,
just let me know what you need. Nouveau or manually disabling the DGPU
in the BIOS behaves as expected.
--
You received this bug notification because you
Reported to upstream as
https://gitlab.gnome.org/GNOME/nautilus/issues/782 .
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1807761
Title:
Unable to install deb-file stored on
Daniel, I disagree with that. Reading some other reports, it looks like
windows handle those cases by making the 'half' screen larger to match
the minimal width. Under unity7 it was not an issue either. In any case
if gnome-shell refuses to do it, it could at least hint of the reason
** No longer
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
mutter. This problem was most recently seen with package version
3.30.2-1~ubuntu18.10.1, the problem page at
https://errors.ubuntu.com/problem/c9276f65c87660639a259684a4068d333e24feb9
contains
You have been subscribed to a public bug:
(on Ubuntu 18.04.1 LTS, all packages up do date)
For about 5 days now, I've been experiencing random freezes of the X
session.
When this happens, I can still move the mouse pointer and it does change
shape according to what it hovers above. Keystrokes
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
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/1732358
Title:
failed to rescan
To manage
OK, at scale 100% then this would not be a shell bug. Applications
always have the final say in what size their windows are and then shell
can't enforce otherwise unless it wilfully displays the window at the
wrong size. You would notice if the window contents provided by the app
don't fit in that
Thanks. Although gnome-shell, snapd and deja-dup-monitor are the top
users for the previous 60 seconds, it also shows that snapd has used an
accumulated 4m40s which is way above everything else.
Given your uptime is 5h34m then that means snapd has used an average of
over 1% of your CPU for that
Please don't comment on this bug unless the workaround in comment #19
works for you. If it doesn't work for you then you need to log a new bug
of your own.
** Summary changed:
- Ubuntu 18.10 login screen never appears when using the Nvidia driver
+ Ubuntu 18.10 login screen never appears when
I've been testing nvidia-410 in Ubuntu 19.04 recently and can't
reproduce this bug. I get the "Ubuntu on Wayland" login option on my
machine. So I can't confirm this bug myself.
** Summary changed:
- [nvidia] "Ubuntu on Wayland" login option is missing in 19.04
+ [nvidia] "Ubuntu on Wayland"
Assigned to 'nautilus' only. The contents of the desktop window,
including icons, are known to the 'nautilus' process only.
** Summary changed:
- GNOME Shell and GNOME FlashBack sessions does not show desktop file icons on
Desktop
+ Desktop icons are shown using the wrong image
** Changed in:
To really get to the bottom of this we would need to reproduce the
freeze in a development environment.
In the meantime, I have one proposed fix that I think will help to avoid
some Gnome Shell Xorg session freezes:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/216
--
You received this
If the mouse pointer is moving then Xorg is working fine. The rest of
the shell being frozen means it is the 'gnome-shell' process that is
frozen.
** Tags added: bionic
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Summary changed:
- x session freezes randomly
+ Gnome Shell
Please:
1. Run: dmesg > dmesg.txt
and attach the file 'dmesg.txt' here.
2. Run: lspci -k > lspcik.txt
and attach the file 'lspcik.txt' here.
3. Reproduce a freeze, reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the file 'prevboot.txt' here.
** Changed in:
Public bug reported:
bootable ubuntu flash drive not formatted in nautilus
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
** Changed in: nautilus
Status: New => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/593502
Title:
incorrect file contents listed for digital camera
To manage
Assigned to 'nautilus' only. The contents of the desktop window,
including icons, are known to the 'nautilus-desktop' process only.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Summary changed:
- Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
+ Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 even though
WaylandEnable=false is set
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
** Tags removed: nvidia
--
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/1796614
Title:
[nouveau] Ubuntu 18.10 boots to a blank screen with a blinking cursor
To manage notifications
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
** Changed in: oem-priority
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
I am attaching an image of the error.
** Attachment added: "Picture of blank screen after lockup"
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1807265/+attachment/5221095/+files/blank.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop
Sorry, it seems my concerns about EGLStreams are quite different and not
blocking your concerns about EGLDevice. Now restoring the original bug
title.
Since this bug is fixed in Ubuntu 18.10 onward I'm going to mark it as
fixed and we can nominate 18.04 to get the fix later.
** Summary changed:
Public bug reported:
Since upgrading to 18.10, nautilus/gnome/ubuntu doesn't remember trusted
files. The owner is me, the executable bit is set. But every time, it
prompts me with "cancel" or "trust and launch". The problem is, it's not
ever trusting it. Tried the 17.10 stackoverflow answer to
*** This bug is a duplicate of bug 1740792 ***
https://bugs.launchpad.net/bugs/1740792
Agreed!
--
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/1687864
Title:
auto-login
** Tags added: rls-bb-incomin
** Tags removed: rls-bb-incomin
** Tags added: rls-bb-incoming
--
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/1805444
Title:
[nvidia] Fail to launch
Dear Brian
I was wondering when the bugfix will be transfered to updates.
I've marked it as solved. At least I hope so. Please let me know.
Thanks
Ueli
Am Dienstag, November 20, 2018 18:57 CET, Brian Murray
schrieb:
Hello Ueli, or anyone else affected,
Accepted gvfs into bionic-proposed.
As I understand it, we presently have:
mutter in 18.04:
* EGLDevice compiled but not working (this bug)
* EGLStreams not compiled
mutter in 18.10:
* EGLDevice compiled and working
* EGLStreams not compiled
mutter in 19.04:
* EGLDevice compiled and working
* EGLStreams not compiled
** Description changed:
- Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice
- backend due to following missing changes in mutter
- 3.28.3-2~ubuntu18.04.2
+ Wayland sessions don't work with the Nvidia driver in 18.04, even after
+ enabling them via the kernel command line
Works for me, too.
--
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/1587154
Title:
--working-directory does not work anymore
To manage notifications about this bug go to:
GDM3 fails to start, stalled at 'started bpfilter' on my HP laptop
(model hp15-ay016nr) which runs Intel graphics, no nVidia hardware or
drivers. So, this is not strictly an nVidia issue, which began after a
Sat 8 December upgrade.
Booting previous kernels did not fix the problem. Disabling
Thank you.
Attached is the output of top -d60
** Attachment added: "Screenshot from 2018-12-10 17-21-12.png"
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+attachment/5220870/+files/Screenshot%20from%202018-12-10%2017-21-12.png
--
You received this bug notification
Please ignore the previous one, I took that screenshot sooner. Consider
this one.
** Attachment added: "Screenshot from 2018-12-10 17-34-22.png"
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1795342/+attachment/5220876/+files/Screenshot%20from%202018-12-10%2017-34-22.png
--
You
SOLVED (MAYBE)
For me, it's not nVidia, it's not WaylandEnable. It may be the "Started
bpfilter" message, which I earlier thought was nothing. I don't know
beans about this, but I checked, and bpfilter is a recent replacement
for iptables in many Linux distros, and it's handled in the linux
Ok, so it's a nautilus issue if it's only there it doesn't work. What
view mode do you use? Do you try to click on an icon on the bg?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
I forgot to include introductory links to this complicated issue. My
crude understanding is that systemd handles system initialization,
calling bpfilter (replacing iptables) which is handled by the linux
kernel.
https://thenewstack.io/systemd-vs-linux-kernel/
Hi Miguel,
Sorry for the inconvenient, I`m aware of the situation and I`m working
to fix this issue.
Thanks tor report this.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1803059
Confirmed with the example from
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/comments/10
, it's a regression from the poppler security update
** Changed in: poppler (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
Public bug reported:
Impact
==
Some emoji in the emoji chooser show as black & white.
This is because these emoji default to "text presentation" instead of
"emoji presentation".
More information and a screenshot can be found in the pango issue linked
below.
Test Case
=
In an app
@Gregor: that shouldn't be an issue any more, assuming that you are
using the latest updates, and that you are using the nvidia driver from
the ubuntu archive.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
@Krzysztof: The NVIDIA GPU is more powerful, but also more power hungry
than the Intel GPU. This is why you are seeing such a high power
consumption.
If you select the Intel GPU, through prime-select, then you will lose
the HDMI, but power consumption should also go down. If it doesn't, it
is a
Public bug reported:
Impact
==
The variant selector in the emoji chooser was broken and will crash the app if
used.
Test Case
=
In an app like gedit, right click in the text area and select Insert Emoji
Look for one of the "people" emoji.
Right-click on the emoji and select one of
64 matches
Mail list logo
