Public bug reported:
Had trouble starting shotwell.
then
started at CL
Shotwell UI starts but no images load.
Waited.
No joy.
Then shotwell crashed.
Here's the final part:
(shotwell:348418): Gtk-CRITICAL **: 10:21:10.016: gtk_tree_path_compare:
assertion 'a != NULL' failed
(shotwell:348418):
Public bug reported:
Ubuntu Groovy Gorilla Beta
Some applications such as Kdenlive from the traditional (.deb)
repositories are shown as "Proprietary" in their details, despite being
OSS. I haven't seen this on Snaps so far.
System details:
System:
Kernel: 5.8.0-20-generic x86_64 bits: 64 com
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Public bug reported:
The devhelp index for Python 3.8 docs (Ubuntu 20.04) trims method and attribute
names from the index items, leaving only the "(<...> method|attribute)" part.
Effectively that makes most of the items there unsearchable through devehelp
interface.
For instance, the index show
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in: mutter (Ubuntu)
Status: New => In Progress
-
I've proposed a fix for that last issue:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1471
but that doesn't seem to solve this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.
Back on the subject of this bug, it may be related to changes in the fd
numbers of -listen and -displayfd passed to Xwayland in mutter 3.38. If
that's relevant at all then it's probably still a snapd issue.
** Changed in: mutter (Ubuntu)
Status: In Progress => Invalid
** Changed in: mutter
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
--
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/1897224
Title:
On behalf of UB - no objections here +1. Many thanks for doing this.
much appreciated.
--
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/1898541
Title:
[FFe] Update to 3.38.0
@David, @Sean: Since this package is seeded in Ubuntu Budgie and
Xubuntu, do you have any objections?
--
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/1898541
Title:
[FFe] Upd
A bug from more than 4 years ago is blocking this bug reported less than
2 months ago? Wow. Fascinating.
--
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/1892440
Title:
Shell text wit
Daniel,
Detailed ways to reproduce the crash are explained upstream at
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/823#note_866367
The crash was happening easily by using the above script, if it doesn't anymore
than it's a verification.
I also verified this in my setup, but preferred
Release team input on IRC:
https://irclogs.ubuntu.com/2020/10/06/%23ubuntu-desktop.html#t11:39
--
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/1898541
Title:
[FFe] Update to
REGRESSION: With systemd 246.6-1ubuntu1 from Ubuntu 20.10 Beta (Groovy
Gorilla), the issue had reappeared
** Tags added: groovy
--
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
This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1
---
nautilus (1:3.38.1-1ubuntu1) groovy; urgency=medium
* New upstream version
- don't block to restore from trash (lp: #1839380)
* debian/source_nautilus.py:
- updated the apport script to use the multiarch di
This bug was fixed in the package nautilus - 1:3.38.1-1ubuntu1
---
nautilus (1:3.38.1-1ubuntu1) groovy; urgency=medium
* New upstream version
- don't block to restore from trash (lp: #1839380)
* debian/source_nautilus.py:
- updated the apport script to use the multiarch di
** Changed in: libgweather (Ubuntu Focal)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgweather in Ubuntu.
https://bugs.launchpad.net/bugs/1892643
Title:
[SRU] Update libg
untargetting for focal for now since there is no assignee, would still
be nice to SRU but desktop decided to not accepted as a active
nomination for now
** No longer affects: fonts-noto-color-emoji (Ubuntu Focal)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
Daniel, could you add this one to your backlog?
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: plymouth (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Focal)
Importance: Undecided
St
> That is not an upstream fix.
Sorry, my bad. I saw the pull request, but didn't see it hadn't been
merged yet :)
--
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/1898479
Title:
Sh
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Tags removed: rls-ff-incoming
--
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/bug
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Focal Fossa 20.04.1
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in
3.36.3-0ubuntu0.20.04.1
3) What you expected to happen
When selecting a
On 2020-10-06 07:26, Bogdan Vasiliev wrote:
> Done!
>
> I've replaced all cyryllic '%е' with latin one.
>
> https://translations.launchpad.net/ubuntu/focal/+source/shotwell/+pots/shotwell/ru/+translate?batch=10&show=all&search=%25%D0%B5
More precisely you submitted suggestions which will need to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plymouth (Ubuntu Focal)
Status: New => Confirmed
--
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/bu
I filed bug #1888695, is it also a duplicate?
--
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/1872159
Title:
booting with splash hangs when external monitors are connected
To manage n
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to flatpak in Ubuntu.
https://bugs.launchpad.net/bugs/1897988
Title:
GitKraken Flatpak doesn't display Icon in task switcher
To m
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu Focal)
Status: New => Confirmed
--
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/1
Thanks Daniel. I was not aware this switch isn't available upstream.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1894593
Title:
Fractional scaling switch doesn't wo
Bogdan, thank you for the suggestions. I have approved your strings and
tested an updated .mo file in Ubuntu 20.04 (Focal Fossa). Shotwell app
looks better now.
Although, a minor issue with declension of months remains, it does not
block the current fix. Moreover, it at present has no easy solutio
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
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.ne
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
This bug was fixed in the package mutter - 3.36.6-1ubuntu0.20.04.2
---
mutter (3.36.6-1ubuntu0.20.04.2) focal; urgency=medium
* xrandr-scaling: Never try to set invalid screen sizes (again!)
Looks like this change (introduced to fix LP:1889090) got lost while
rebasing previo
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being 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 r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being 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 r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being 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 r
The verification of the Stable Release Update for mutter has completed
successfully and the package is now being 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 r
** Changed in: ubuntu-translations
Status: Triaged => Fix Committed
--
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/1898479
Title:
Shotwell: Russian translation is invalid
Hello Sebastien, or anyone else affected,
Accepted epiphany-browser into focal-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/epiphany-
browser/3.36.4-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
The test case here seems like it was improperly pasted from somewhere,
setting to Incomplete until that's sorted.
** Changed in: gnome-bluetooth (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
FWIW this fixed the issue for me.
--
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/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
on Nvidia)
To
In my experience, the bug occurs when a ThinkPad is in its Ultra Dock
and is run, lid closed, using external display, keyboard, and mouse. Bug
#1888695 refers to a direct connection of an external monitor to the
laptop's own HDMI port. Thus the configuration is not the same. The
cause may be relate
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is
definitely the culprit here. Snaps depend on access to the abstract
namespace socket to function correctly.
Inside the sandboxes, snaps see a private /tmp that is under their
complete control. So there is no /tmp/.X11-unix directory
Looking at the reasoning behind that change, Mutter introduced lazy
initialisation of Xwayland: binding the two sockets, and starting
Xwayland when someone connected to the abstract namespace socket.
Flatpak apps apparently can't speak to the abstract namespace socket, so
would hang forever when st
Groovy is already done. Just add a focal task when ready.
** Tags added: focal groovy
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth i
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream
about this regression.
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454
https://gitlab.gnome.org/GNOME/mutter/-/issues/1454
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1454
Importance: Unknown
Status: Unknown
--
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/1897224
** Summary changed:
- [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X
display
+ Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
display)
** No longer affects: chromium-browser (Ubuntu)
--
You received this bug notification because you are a mem
Please try:
Settings >
Language and Region >
Manage Installed Languages
Now drag your preferred language to the top of the list and click 'Apply
System-Wide'.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3237
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3237
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3237
Importance: Unknown
Status: Unknown
** Also affects: gjs (Ubuntu
For 20.04 and 20.10 using the TearFree option has provided a workaround
solution for me.
Separately Sam (the issue reporter) has confirmed the same solution for
his intel graphics
https://askubuntu.com/questions/1066722/intel-screen-tearing-
ubuntu-18-04
--
You received this bug notification be
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1445
Importance: Unknown
Status: Unknown
--
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/189
Great, but keep in mind that's just a workaround. Using the 'intel'
driver is usually not recommended because it's getting old and buggy in
other ways. It is however your only option if you need 'TearFree'
enabled. See also
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=tearing
--
You received
I should also note that Wayland sessions don't have this bug, and don't
have tearing either.
--
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/1896627
Title:
Windows flicker when being
I install a dell machine (still not disclosed), upgrade everything from
updates channel, and install from focal-proposed
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
gnome-control-center-data all 1:3.36.4-0ubuntu2 [327 kB]
Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/
59 matches
Mail list logo
