** Changed in: gimp (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2055044
Title:
GIMP crash at closure on systems with
Also note that even the system's build of Bubblewrap is not granted the
ability to bypass user namespace restrictions as that would allow the
restrictions to be bypassed by any application. Doing this to your own
build of Bubblewrap will pose the same security issue. If you can avoid
doing things
Unless your app and Bubblewrap can both work without any capabilities in
an unprivileged user namespace, things will probably go south. You
should probably be installing an AppArmor profile for your app that
allows you to use unprivileged user namespaces normally again, as
described in Comment 5
The regression mentioned above appears to have been a glitch in the
s390x autopkgtest infra. I requested a retry.
The test plan succeeded using the GIMP from noble-proposed - I can
export an image as a PNG, then close GIMP and click "Discard" when
prompted to save my changes and it closes
The Tor Browser is actually installable on Ubuntu, and we have
privacy-conscious folks here who are Ubuntu Developers. We just were
absolutely slammed in more ways than we imagined would happen this
cycle and things slipped through the cracks. This is probably one of
them.
You can follow the
** Changed in: gimp (Ubuntu Noble)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2055044
Title:
GIMP crash at closure on systems with GLib
Fix verified on Noble. Will be uploading and submitting to the SRU team
soon.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2055044
Title:
GIMP crash at closure on systems with GLib
Looks like Jeremy Bicha has a new GIMP uploaded to Oracular which will
fix this there. The fix will still need backported to Noble, which I
intend on doing.
** Changed in: gimp (Ubuntu Oracular)
Status: New => Triaged
** Changed in: gimp (Ubuntu Oracular)
Status: Triaged => Fix
0.so.0
No symbol table info available.
#65 0x7f43ecbc5b87 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#66 0x55b13688a515 in app_run ()
No symbol table info available.
#67 0x55b13688041f in main ()
No symbol table info
Public bug reported:
Steps to reproduce:
1. Launch GIMP on Kubuntu 24.04.
2. Create a new image.
3. Draw something in it (a black squiggly line with the default brush is fine)
4. Export the image as a PNG.
5. Close GIMP.
Expected result: GIMP closes normally.
Actual result: Segmentation fault.
We rewrote the update notifier in Qt/C++ and got rid of the aptdaemon
dependency earlier in the Noble cycle, so this is now resolved in Noble.
** Changed in: lubuntu-update-notifier (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
I believe bwrap was ignored intentionally, as the point of the apparmor
change was to prevent arbitrary apps from making unprivileged user
namespaces with capabilities. Allowing Bubblewrap to do so would provide
a loophole. Same reason `unshare` isn't allowed to make unprivileged
namespaces with
Public bug reported:
Lubuntu uses Qt as the primary framework for most of the apps we ship.
However, some functionality we ship in Lubuntu doesn't have a Qt
application that provides that functionality, so we have some GTK3 apps
that we ship as well. Starting in Lubuntu 24.04, we are adding and
User prompting sounds like a good idea. Tt fixes one concern I wanted to
bring up, which is developers who use user namespaces in their code
(possibly indirectly by using QtWebEngine for instance). Those devs
would end up with their software crashing for no apparent reason. A user
prompt or
The reason I was suggesting a single attribute to enable user namespace
creation is because of the myriad of third-party apps that we probably
*aren't* going to catch here that users use out there that require user
namespace privileges. For instance, there are probably at least some
I can't seem to get the xattr solution to work. I'm trying it on a
normal binary and it's failing like so:
# Contents of /etc/apparmor.d/falkon
abi ,
include
profile falkon xattrs=(security.apparmor=falkon) flags=(unconfined) {
userns,
include if exists
}
# setfattr command
How acceptable or possible would a solution be that had one universal
"allowUserNamespaces" attribute in an AppArmor config that could then
simply be set on whatever files one wanted to enable the features on?
That would support all third-party apps that a user deemed worthy
without needing much
Nice! This works with AppImages? If so, I think we have a perfect
solution.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/2046844
Title:
AppArmor user namespace creation
Thanks! I'll be on the hunt for any more that act like this and add them
to the report. I'm also happy to help prep uploads (I'm not an MOTU yet
so I can't upload on my own, but I can prep the packaging).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
This bug also breaks Electron-based AppImages, such as Balena Etcher.
While we specifically don't support these apps, I find it very likely
that Ubuntu has potentially hundreds of thousands of users of these
kinds of apps.
--
You received this bug notification because you are a member of Ubuntu
This is affecting Falkon and qutebrowser as well. Just now me and a
couple of the Lubuntu devs did a deep debugging session and found the
issue.
About four days ago, an upload was made in AppArmor that no longer
allows unprivileged programs to create user namespaces. See
Besides saying that the Bug has been fixed, the issue is still present.
The issue might've been fixed in the past but now it is showing up
again, and according to my logs, I always had it every day since I
installed it more than 6 months ago.
> hostnamectl
Static hostname: aspire-e15
Icon
** Patch added: "0001-Add-HEIF-HEIC-support-by-default-on-desktop.patch"
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1886271/+attachment/5669349/+files/0001-Add-HEIF-HEIC-support-by-default-on-desktop.patch
--
You received this bug notification because you are a member of Ubuntu
@mantas: I made the metapackage changes you mentioned here:
https://git.launchpad.net/~alichtman/ubuntu/+source/ubuntu-
meta/commit/?id=c67add66d28fd38cddfcdd9798339f8040b6589c
I opened a MR here:
https://code.launchpad.net/~alichtman/ubuntu/+source/ubuntu-
meta/+git/ubuntu-meta/+merge/442067.
Latest patch has requested changes. Bug has been submitted to upstream
Debian here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385
** Bug watch added: Debian Bug tracker #1033385
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033385
** Patch added: "glib_crash_bugfix_v5.patch"
Gah, ok, one more try. I failed to update the debian/copyright file last
time. This version has the updated copyright file.
** Patch added: "glib_crash_bugfix.patch"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5657032/+files/glib_crash_bugfix.patch
--
You
After a discussion with dbungert, we're using a different patch instead.
This one is possibly upstream already, which makes it superior to the
original patch I was suggesting since it means less maintenance overhead
in the future.
** Patch added: "glib_crash_bugfix.patch"
New patch, same approach, but with a fallback added if itPrev turns out
to be null.
** Patch added: "glib_crash_bugfix.patch"
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/2011751/+attachment/5656971/+files/glib_crash_bugfix.patch
--
You received this bug notification because you
One worry I am having with my patch now is, what happens if the first
element is the one being modified? Then itPrev is a null pointer. I
*think* from looking at the GLib code that g_list_next will then return
null when it it handed itPrev, which means "it" will be set to null,
which I believe
(One extra bit of info that I realized was left out - according to the
comment on the Arch Linux forums here:
https://bbs.archlinux.org/viewtopic.php?pid=2090270#p2090270 the first
loop iteration succeeds. It's not until the second iteration (after the
list has been modified) that the crash
OK, so I'm not entirely sure testing the one item case is even possible
since the crash happens when switching from a fullscreen window (which
implies that there are at least two windows). However, this is what I
did, and everything was successful (no crashes).
1. Boot a Lubuntu Lunar ISO, and
@dbungert: While the patch that simply copies the list is a possible way
of doing things, a very experienced user on the Arch Linux forums had
concerns about doing things that way, see
https://bbs.archlinux.org/viewtopic.php?pid=2090570#p2090570 "But
creating a copy of the list is inefficient and
I don't have upload access to this package yet (it's not in the Lubuntu
packageset apparently) so I'm uploading the patch here so that it can be
sponsored.
** Patch added: "glib_crash_bugfix.patch"
** Changed in: openbox (Ubuntu)
Assignee: (unassigned) => Aaron Rainbolt (arraybolt3)
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
I believe we have a working patch for the problem. A quick summary of
what it looks like is happening:
Openbox maintains a list of windows organized by stacking order from
highest to lowest. This is a doubly-linked list.
There is a function in Openbox called client_calc_layer that uses a
pointer
Public bug reported:
Note that, in my experience, this bug *only* affect Kubuntu 22.10 and
Ubuntu Studio 22.10, however Ubuntu Studio specifically does not support
VMs, and I assume that fixing the problem in Kubuntu will fix the
problem in Ubuntu Studio too.
Steps to reproduce:
1. Install
I'm not sure if this problem is happening on Linux Mint 21 or Ubuntu
22.04.1. While Linux Mint is based on Ubuntu, it is not the same as
Ubuntu, and may have behaviors (and bugs!) that differ from Ubuntu's.
Could you clarify which Linux distro you're experiencing this problem
on?
--
You received
Sorry for the blurry screenshot.
--
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/1988703
Title:
Ubuntu logo is not shown in the bottom in GDM
To manage notifications about this bug
Public bug reported:
On Ubuntu 22.10 daily builds, the Ubuntu logo in the bottom is not
present. I first found it in a VM and then booted up a live USB and got
the same result.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: gdm logo ubuntu
** Attachment
libraries, about to
create video widget
TotemVideoThumbnailer-Message: 17:38:03.908: setting URI
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 17:38:03.908: Video widget created
TotemVideoThumbnailer-Message: 17:38:03.908: About to open video file
OpenBLAS blas_thread_init: pthr
** Summary changed:
- Video thumbnails fail to genetate
+ Video thumbnails fail to generate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1988100
Title:
Video thumbnails fail to
> Don't be alarmed by that. Those two limits are correct and normal
Fair enough. I only mentioned it because I noted that the -l flag
allowed the process to complete.
Sadly I have nothing in /var/crash. I see a couple of gnome-shell
reports on errors.ubuntu.com but they are from back in March
to
create video widget
TotemVideoThumbnailer-Message: 11:08:44.739: setting URI
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file
(totem-video-thumbnailer:416380
widget
TotemVideoThumbnailer-Message: 11:08:44.739: setting URI
file:///home/aaron/tmp/sample.mp4
TotemVideoThumbnailer-Message: 11:08:44.739: Video widget created
TotemVideoThumbnailer-Message: 11:08:44.739: About to open video file
(totem-video-thumbnailer:416380): GStreamer-WARNING **: 11:08
Changing the package this bug affects to gdm3 as I believe that is the
package that includes the Wayland implementation in Ubuntu.
** Package changed: ubuntu => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
Public bug reported:
Repro:
1. Set dock to auto-hide, tacked to the bottom.
2. Hover mouse at bottom to show the dock.
3. Right click on one icon, intending to perform some task within the context
menu
4. Move mouse to desired task but don't click
5. The dock will autohide and cause
This bug also occurs in Ubuntu 22.04 (Jammy).
** Tags added: jammy
--
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/1973156
Title:
Strange graphical glitch during Ubuntu installation
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm using the same
host system specs as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
While running the test, in
Public bug reported:
Hello,
Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem
crashing.
I have not been able to pin down when it works and when it doesn't, as
playing the same videos seems to work sometimes and not work others.
After it crashes, trying to open it again
Public bug reported:
I am using the Firefox Snap on a fresh install of 22.04 (using defaults,
as far as I know).
Normally, Firefox shows an indicator in the Dock showing that it is
running (the orange dot) and gives the ability to choose between open
windows.
At the moment, I have Firefox
** Attachment added: "Headset back on, output has gone back to the headset but
microphone has not"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png
--
You received this bug notification
Public bug reported:
In Gnome's sound settings, it takes a sensible approach for my Bluetooth
headset speaker:
1) I set it as my preferred audio Output Device
2) I turn the headset off and it disappears, reverting to the built in speakers
3) I turn the headset on again and it switches back to
** Attachment added: "Headset turned off, input and output revert to internal
ones"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png
--
You received this bug notification because you are a
Fixed 2 days ago in updated gdm 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/1969121
Title:
System fallback to gdm login screen when hot-plugging a external
monitor in
Sure thing! The default option when downloading a file is to "Open With"
that is what 3a is about as Software Install is the default "Open With"
option. A coworker thought on this issue is that the file is saved in
/tmp until it is opened and the snap-store can't access outside of the
home
I can confirm that this hasn't been fixed on either 20.04 LTS or 21.04
with the latest updates applied and a reboot into the latest kernel.
Steps to reproduce using GNOME Boxes and the Chrome deb file from
Google:
0. Install GNOME Boxes using apt
1. Setup VM with either OS using the defaults (no
Ah interesting, thanks Daniel. I did not realise Raspberry Pis were
doing Wayland by default.
Yes, it works as expected in xorg, but not in Wayland.
It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my
logs.
--
You received this bug notification because you are a member of
Public bug reported:
In Nautilus File Manager, when trying to rename the bookmark of a
(remote) directory through the context menu, the "rename" option is not
clickable. Instead the click activates the option to drag the entry of
the bookmark to a different position.
ProblemType: Bug
Public bug reported:
Bug Description:
I wanted to rename a directory.
Nautilus crashes with error 'Files not responding'.
Name contains A-Z, a-z, 0-9, Underscore, Hyphen.
Versions:
Ubuntu
Description:Ubuntu 20.10
Release:20.10
Nautilus (Files)
1:3.38.1-1ubuntu1
ProblemType: Bug
Possibly related to this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1530405
That bug focuses on the soft lockup but nouveau has come up as a factor.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Just upgraded to 16.04 LTS and that works as well. To be clear, for both
14.04 and 16.04, the proprietary NVIDIA drivers are available via the
nvidia-304 package, but I'm not using those. The nouveau driver itself
works on 14.04 and 16.04.
FWIW, back when I tried running 18.04/20.04, when
I have been experiencing a similar problem with a GeForce 7300 GT on a
Mac Pro 1,1. I also have visual artifacts in 18.04 and 20.04. With
18.04, there are no artifacts or other problems during installation from
a DVD, but when booting the installed system there are artifacts after
login and
** Attachment added: "Playback on 200% screen"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
I am using Ubuntu Focal Fossa with Wayland and two screens.
Display 1 is a 3840 x 2160 screen at 200% scaling
Display 2 is a 1920x1200 at 100% scaling
Fractional Scaling is on. Display 2 is my Primary Display.
When I play a video on Display 2, everything works as expected.
** Attachment added: "Display Settings screenshot 2"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: "Display Settings screenshot 1"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-54.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
For what it's worth, the only difference between Ubuntu and Pop
regarding Mutter is that we've removed the xrandr patching causing this
issue. We tested the most recent version of the patch in proposed for
Focal at this time, and the issue still occurs there. Given that it's an
experimental
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%
We (System76) were able to replicate the issue on most of our NVIDIA
laptops in NVIDIA mode, with the exception of the addw1. We've therefore
repackaged mutter in Pop without the patch, so it's no longer a problem
for us.
You can find screenshots of the problem in this issue:
Public bug reported:
With the package currently proposed for 20.04, NVIDIA systems are
experiencing very small text in GDM and GNOME Shell. Removing x11-Add-
support-for-fractional-scaling-using-Randr.patch fixes it.
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
The user experience leaves a lot to be desired. At extensions.gnome.org
it shows as an extension which can be disabled and has updates. When I
turn it off, it doesn't turn off, and when I try to update it, it says I
can't update it because it is not turned off. Other extensions don't
work that
Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370
? If so, in the duplicate bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said
"This is a 2020 goal."
** Package changed: evolution (Ubuntu) => firefox (Ubuntu)
** Bug watch added: Mozilla Bugzilla
I wasn't able to recreate it until we added our PPA to get the following
version:
3.28.3-0ubuntu18.04.5pop1~1551986836~18.04~d21ecd7
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Right now I'm working on recreating the issue here. I also installed the
NVIDIA driver from here:
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
and now our build to rule that out as an issue.
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
Hey Daniel,
I've installed Ubuntu 18.04.3 from that link and installed it on the
same Serval WS (serw11). I'm attaching the same version numbers to this
message:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Public bug reported:
This was recreated on a System76 Serval WS (serw11) on Ubuntu 18.04 with
the following versions of packages:
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
Details from address sanitizer:
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: AddressSanitizer:DEADLYSIGNAL
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]:
=
Oct 03 11:46:38 pop-os org.gnome.Calendar[3834]: ==11918==ERROR:
AddressSanitizer:DEADLYSIGNAL
=
==11918==ERROR: AddressSanitizer: SEGV on unknown address 0x0006 (pc
0x7f58b1ab7c7d bp 0x0002 sp 0x7ffd3aad4da0 T0)
==11918==The signal is caused by a READ memory access.
==11918==Hint:
Public bug reported:
Occasionally when launching the calendar from the overview, it segfaults
at startup. This does not seem to happen when launched from the
terminal. Logs from journald:
Oct 03 11:37:50 pop-os gnome-calendar[8992]: gtk_widget_get_scale_factor:
assertion 'GTK_IS_WIDGET
Just made the leap to Linux with Ubuntu 18.04 and am experiencing this
"bug" also.
My error was specifically as @cometdog mentioned with a BMP extension
with a PNG file signature (and data).
I can think of a lot of ways an image would have an incorrect extension.
It would be great if eog could
Can confirm this bug also affects me.
`gnome-shell` is currently consistently the top program in `top` --
~5454092 (Virt) / 2.4g (Res) 15.2% Mem
Other behaviors I've noticed:
- Nautilus is slow at times
- When browsing the filesystem from a web browser (ie. attaching a file, or
any "file
Updating this to state that GNOME has yet to make a decision on how to
approach this, but whatever decision they make will not consist of
sharing an application-specific variable with GDM.
They seem to be hinting that they will create a global variable that
applications can use, but they've yet
** Attachment added: "Screenshot with external monitor connected. Only whole
number scaling available."
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png
--
You received this bug notification
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have enabled the experimental fractional scaling support.
When no external monitor is connected, the fractional scaling options
are displayed as expected. When the
Public bug reported:
Using 19.04 disco with Wayland.
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
If I set the primary display to the built-in display but have the
display settings window open
Public bug reported:
Running 19.04 Disco with Wayland
Version 64ubuntu7
I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor.
I have the laptop screen set to 200% and the external screen set to
100%.
When running the display solely on my built-in monitor, the dock is
correctly
This still occurs in 19.04 with nvidia-driver-418.
--
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/1769857
Title:
Vulkan not working if nvidia-drm.modeset=1 is set and gdm3 is used
Public bug reported:
When the `PrintScrn` key is pressed in GNOME Shell, it takes a
screenshot and writes it to `$HOME/Pictures`, or otherwise falling back
to `$HOME` if that directory is not found. The `gnome-screenshot` tool
does a similar action, but also checks for the existence of the `auto-
@seb128 I guess that means we'll have to keep carrying the patch
ourselves for bionic in our repos.
Personally, I think you should reconsider it if the desktop is part of
your "Long Term Support".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
https://github.com/pop-os/pop/issues/370
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I am seeing this happen here, as well. Though my disk space issue isn't
anywhere near as dire.
** Attachment added: "Screenshot from 2018-08-05 19-37-57.png"
Submitted PR upstream to Nautilus' 3.26 branch:
https://gitlab.gnome.org/GNOME/nautilus/merge_requests/241/diffs
--
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/1774094
Title:
GNOME merged the changes for their 3.26 branch, so it's now up to Ubuntu
to make their move for 18.04
--
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/1774094
Title:
[18.04]
** Summary changed:
- [Patch Included] 3.26.3-0ubuntu4 .desktop extension is duplicated when
renaming a .desktop file
+ [18.04] [3.26.3-0ubuntu4] .desktop extension is duplicated when renaming a
.desktop file
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Patch removed: ".desktop rename patch for Nautilus"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774094/+attachment/5146234/+files/desktop-rename.patch
** Patch added: ".desktop rename patch for Nautilus"
Public bug reported:
When attempting to rename a .desktop file in Ubuntu 18.04, .desktop is
automatically appended. This causes the .desktop extension to get
duplicated, where renaming `app.desktop` to `app2.desktop` will actually
rename it to `app2.desktop.desktop`. The included patch fixes the
Anything that I can do to help get this fix into the Ubuntu package? I
cannot import photos, which is enough of a problem that I'm considering
downgrading to the earlier release -- but happy to help try to fix it
properly.
--
You received this bug notification because you are a member of Ubuntu
Marcus has said in the upstream bug:
"I released 2.5.16 some weeks ago.
the commit fixing this issue for backporting is
472a9461b457b4d08ecf10a93bb7f1efdc2124c0 "
It would be excellent if this could please make its way into Ubuntu.
--
You received this bug notification because you are a member
Would be nice to disable sticky edges and/or the barrier while dragging
a window.
--
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/1726464
Title:
Can't easily move the cursor
** Also affects: gphoto2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.launchpad.net/bugs/1731341
Title:
Fujifilm X-T10 regression on 17.10:
1 - 100 of 649 matches
Mail list logo
