As I said on [this][1] probable upstream issue this bug seems to be
reduced just to have by default 'ask' or 'launch' as the default value
for key `executable-text-activation` (on
org.gnome.nautilus.preferences), or I'm missing something?
[1]:
journal.txt
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259189/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
dmesg.txt
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259187/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
edids.txt
** Attachment added: "edids.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259188/+files/edids.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
lspci.txt
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1826316/+attachment/5259190/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
about xrandr.txt... this happens with wayland session (the bug is tagged
properly i think)
honestly, i didnt try the xorg session... so the file is empty
root@r7:/home/mspehar# xrandr --verbose > xrandr.txt
No protocol specified
Can't open display :0
--
You received this bug notification
Please also:
5. Run: xrandr > xrandr.txt
and send us the file 'xrandr.txt'.
--
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/1826316
Title:
two monitor setup - resolution not
Please also:
5. Run: xrandr --verbose > xrandr.txt
and send us the file 'xrandr.txt'.
--
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/1826316
Title:
two monitor setup -
Please:
1. Run: lspci -k > lspcik.txt
and send us the file 'lspcik.txt'.
2. Run: strings -f /sys/class/drm/*/edid > edids.txt
and send us the file 'edids.txt'.
3. Run: dmesg > dmesg.txt
and send us the file 'dmesg.txt'.
4. Run: journalctl -b0 > journal.txt
and send us the file
The log messages you mention seem to be describing symptoms of the
problem but not the cause.
In order to find the cause of the problem, first please try uninstalling
the 'gsconnect' extension and then reboot. Then tell us if the problem
still happens.
Please also run these commands and send us
I am using 18.10 and I have not yet experienced this issue.
For me, in 18.04, something that consistently triggered this bug was
whenever I accidentally touched the touch-screen on my laptop while
adjusting it.
In 19.04, I am able to interact with the touch-screen using my fingers,
and this
** Changed in: gnome-shell
Status: Unknown => Fix Released
** Changed in: mutter
Status: Unknown => Fix Released
--
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/1826176
*** This bug is a duplicate of bug 1550779 ***
https://bugs.launchpad.net/bugs/1550779
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1550779, so it is being marked as such. Please
** Changed in: mutter
Status: Unknown => Fix Released
--
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/1826182
Title:
[DisplayLink][fixed upstream] GNOME libmutter crash on
Thanks Pekka.
Since I know you're the upstream developer of the fix there's no need
for us to ask any further questions.
** Tags added: fixed-in-3.32.1 fixed-upstream
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Status: New => Triaged
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
Great!
That makes this a duplicate of bug 1798790.
** This bug has been marked a duplicate of bug 1798790
Ubuntu login screen never appears when using the Nvidia driver (and setting
Thanks.
I wonder if this comes under the "send info to canonical" option chosen
on first login. Maybe if you choose "No" then that also means crash
reports don't get sent...? :(
We'll need to find out how to flip that option to test it.
--
You received this bug notification because you are a
@Sebastien Bacher
verdre responded:
This is caused by x11 not sending a device-changed event if no
interaction happened with the OSK before using the physical keyboard.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1185
--
You received this bug notification because you are a member of
Just in case, please try uninstalling your extensions:
b'org.gnome.shell' b'enabled-extensions' b"['workspace-
g...@mathematical.coffee.gmail.com', 'nohotcor...@azuri.free.fr',
'gnomeGlobalAppMenu@lestcape', 'static_workspa...@rmy.pobox.com', 'user-
Also verified in February in comment #9.
--
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/1779615
Title:
Shell text and some icons have sharp edges during zoom
To manage
I was using 3.28.3+git20190124-0ubuntu18.04.2
--
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/1779615
Title:
Shell text and some icons have sharp edges during zoom
To manage
This bug is closed because:
(a) The original reporter can't reproduce it any more; and
(b) The developer can't reproduce it any more.
If there are any remaining issues then please open a new bug by running:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a
I believe that I managed to fix this on my machine. I'd suggest to
anyone having this issue to check for and uninstall any workspace-
related extensions in gnome-tweaks. Read on for more detail.
This problem appeared for me after updating to 19.04 from 18.10. Like
everyone else, I could click on
Also worth mentioning that the issue was present when running under both
Wayland and XOrg.
--
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/1181666
Title:
gnome-shell randomly
** Also affects: mutter (Ubuntu Eoan)
Importance: Medium
Status: Invalid
** Also affects: gnome-shell (Ubuntu Eoan)
Importance: Medium
Status: Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407
** This bug has been marked a duplicate of bug 1809407
[nvidia] Corrupted wallpaper after resuming from suspend
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
One of IHV parnter get this issues too during stressapp + iperf testing.
LP#1823615
--
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/1752091
Title:
gvfsd-metadata[1703]:
I believe that I found a "solution", I don't know what caused it. After
suffering with the problem for 2 weeks I discovered that emptying the
trash the terminal way solved it. It seems Nautilus was having issues
with something in the rubbish bin via the below command.
rm -rf
** Changed in: ipython
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1602900
Title:
libzmq3 crashes when 'getifaddrs()' is unavailable
To
WaylandEnable=false workaround also works for 19.04
Nvidia 340 and 390 drivers still having issues with 19.04 but does not
seem to be the cause of the gdm problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Public bug reported:
```
GNU Image Manipulation Program version 2.10.10
git-describe: 5e662c37d7cc472266989f259c4ae579d66a6617
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
I've inferred that the reporting process itself possibly interferes with the
misbehaviour. After submitting this report (before the terminal session was
closed, however) (began through a terminal session and not the Alt-F2 launcher,
using ubuntu-bug [PID of nautilus]) the reported behaviour is
Public bug reported:
Immediately after upgrading from 18.10 to 19.04, my computer froze about
30-40 secs after I logged in.
I finally tracked this down to the tracker-extract process. This process
starts within about half a minute after logging in. When it starts, it's
a matter of seconds until
Public bug reported:
I've recently upgraded from 18.10 to 19.04.
When I right-click on any folder the context menu has extra padding on the
bottom edge, below the 'properties' item. Performing the same action on files
doesn't produce the problem.
Strangely, while reporting this bug the noted
Public bug reported:
Ubuntu 19.04 / Nautilus 3.32.0 stable (?)
Mounting a disk (which does not show on the desktop may I add here as
well) and asking for disk properties gives a black circle.
Expected behaviour: different colours for used and unused parts, maybe
gray for the unusable meta data.
** Changed in: gnome-shell-extension-desktop-icons
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1826081
Title:
Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded.
Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value !=
NULL' failed
Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating
service name='org.gnome.Logs' requested by ':1.15' (uid=1000
It just happened now...
When this happened, I had right clicked on a misspelled work in a
Firefox text area. I didn't get a popup context menu; I thought it was
just Firefox acting up.
So, I switched to my open Gedit window, to cut the correctly spelled
word from my text document, and the
Public bug reported:
It is not possible to play embedded videos in the presentation mode.
This affects PDF slides created with the beamer/multimedia latex
package. Initially, no controls are shown on the slide with the video.
In the normal mode, video controls appear when the video is clicked
Public bug reported:
Full-day events jump a date back if edited and saved, even when no
information about date or time is changed. Tested in local and Google
calendars, happens in both.
To reproduce:
1. Create a full-day event (say on May 5)
2. Click on the event to open event editor
3. Keep the
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
An upload of gnome-software to xenial-proposed has been rejected from
the upload queue for the following reason: "Since this upload includes
the same change for 'new media API' as others, I would feel much safer
if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) -
since it seems
Hello Robert, or anyone else affected,
Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Robert, or anyone else affected,
Accepted gnome-software into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Robert, or anyone else affected,
Accepted gnome-software into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Robert, or anyone else affected,
Accepted gnome-software into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Robert, or anyone else affected,
Accepted gnome-software into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.30.6-2ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
*** This bug is a duplicate of bug 1760399 ***
https://bugs.launchpad.net/bugs/1760399
** This bug is no longer a duplicate of bug 1761554
[bionic] Extended characters in GNOME screen keyboard don't get entered
** This bug has been marked a duplicate of bug 1760399
New On-screen
*** This bug is a duplicate of bug 1760399 ***
https://bugs.launchpad.net/bugs/1760399
My understanding is that this bug has been taken care of through the
fixes of bug #1760399 and bug #1816808. Marking it a duplicate of the
former.
** This bug has been marked a duplicate of bug 1760399
Same problem here. Nvidia GeForce 920MX, latest driver installed.
--
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/1822179
Title:
Resuming from sleep breaks desktop and lock
Public bug reported:
Version: 3.28.3
I managed to format my system drive to NTFS by accident, the UI did
nothing to prevent it or even warn me.
Last week I was formatting a thumb drive to NTFS. I forgot to select it
and my system NVME was selected. I noticed it after I created the NTFS
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016
Is this still an issue for anyone in a later Ubuntu release?
** Changed in: hundredpapercuts
Status: Confirmed => Incomplete
** Changed in: totem (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: totem
Status:
Upstream report is a duplicate of #551365
which was closed "RESOLVED NOTABUG" on 2008-09-09
In new interface the order of buttons does not change when
running Totem full screen so marking this as being fixed.
** Changed in: totem (Ubuntu)
Status: Triaged => Fix Released
--
You received
Upstream report showing "RESOLVED FIXED" on 2011-08-30
New interface has these controls if appropriate plugin enabled
** Changed in: totem (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
** Changed in: totem (Ubuntu)
Status: Triaged => Fix Released
--
You
No, fix is not released:
gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 - package from bionic-
proposed.
We are still waiting for it in bionic-updates.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Upstream report closed "RESOLVED FIXED" on 2012-04-18
Tested ok with iPhone and Ubuntu 18.04 so closing
** Changed in: totem (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
go to settings > search. then look for a setting icon on bottom right of
the box and click it. Go to other and select those folders where you
want the Star to work
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
This bug was fixed in the package mutter -
3.28.3+git20190124-0ubuntu18.04.2
---
mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium
* control: Add Breaks on budgie-desktop verions broken by this upload.
budgie-desktop needs a fix in
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
The verification of the Stable Release Update for gnome-shell 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
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
The verification of the Stable Release Update for mutter 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 a
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
Please always report what package version has been used during
verification! But yeah, this time accepting verification even without
this info as I trust you have used -proposed as required.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The verification of the Stable Release Update for mutter 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 a
This bug was fixed in the package gnome-shell -
3.28.3+git20190124-0ubuntu18.04.1
---
gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium
* New git snapshot release up to commit 24cdcc56d (LP: #1811900)
- Don't fill journal with osdWindow errors (LP:
The verification of the Stable Release Update for gnome-shell 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
Thanks, could you reprort it upstream on
https://gitlab.gnome.org/GNOME/nautilus/issues/?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)
** Changed in: gstreamer-vaapi (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
84 matches
Mail list logo
