To make it clear: you are using the GNOME Flashback (Metacity) session,
not the default GNOME session, right?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1863391
Title:
GNOME f
Public bug reported:
Problem reported at boot but does not seem to collect data and send, just does
nothing.
Still able to use laptop.
This file exists in /var/crash
-rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash
The time of this file must have been at last shut
[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.
https:/
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
When scaling the desktop to e.g. 150%, fullscreen video does seem to
trigger constant changes of the scaling factor: the system switches
every 0.5s from 150% to 100% to 200% or things like those.
The problem does not occur, when there is another windows present (e.g.
a "alway
Adam: I am using Ubuntu 19.10, LibreOffice 6.3.4.2, and a default session (X11).
Actually, copy/paste worked really better on the 1st of February and during the
days after. I thought it was fixed! Today, the issue is exactly the same as
before.
--
You received this bug notification because you
Public bug reported:
1) Ubuntu 19.10
2) 3.34.1
3) No seg fault.
4) Seg fault occurred when checking nautilus version.
** Affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "gnome_version_seg_fault.png"
https://bugs.launchpad.net/bugs/1863376/+atta
Public bug reported:
1) Ubuntu 19.10
2) Version 3.34.0
3) If I type the following in the terminal, the gedit version should be
displayed: gedit -v
4) The gedit version was not displayed. The uppercase -V argument should be
changed to a -v lower case argument.
** Affects: gedit (Ubuntu)
Imp
Looks like this was updated already :)
https://bugs.launchpad.net/ubuntu/+source/flatpak/1.6.2-1
** Changed in: flatpak (Ubuntu)
Status: New => Fix Released
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1863254
Title:
Update flatpak to 1.6.2 in Focal
To manage notifications about this bug go to:
https:
Public bug reported:
unknown error encountered
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdg-desktop-portal (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
I am still seeing thins on a fresh Eoan install ..
https://bugs.launchpad.net/bugs/1857892
--
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/1734095
Title:
Software & Updates not
Public bug reported:
Please, update the flatpak package in Ubuntu 20.04 to a recently
released version 1.6.2.
"Due to a combination of some behaviour in flatpak and recent versions of
ostree we at some point lost the use of deltas for the initial install case,
instead always falling back to a f
You have been subscribed to a public bug by AsciiWolf (asciiwolf):
Please, update the flatpak package in Ubuntu 20.04 to a recently
released version 1.6.2.
"Due to a combination of some behaviour in flatpak and recent versions of
ostree we at some
point lost the use of deltas for the initial ins
I was able to solve the problem, by switching GPU-driver.
"Software & Updates" -> "Additional Drivers" - I switched from:
"Using X.Org X server - Nouveau display driver" to the NVIDIA-435.
Perhaps this is only specific to my setup, by powering monitors from GPU
as well as motherboard. Hope it help
Hi, I'm seeing this error as well.
The last frame shown while logging in freezes on the second monitor and
only the cursor updates.
I have enabled iGPU Multi-Monitor for my ASUS motherboard, which enabled
me to connect one monitor through the motherboard and one through my GPU
- the one connected
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1863244
When reporting bugs in the future please use apport by using 'ubuntu-
bu
I ask you to analyze the content and then delete it.
It was the only way to send crash data to the totem
** Attachment added: "Crash"
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+attachment/5328158/+files/usr_bin_totem.1000.crash.txt
--
You received this bug notification be
I ask you to analyze the content and then delete it.
It was the only way to send crash data to the totem
--
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/1863184
Title:
Application do
Public bug reported:
```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Further information. After updating the packages the error returned
(nvidia is still uninstalled).
$ gnome-control-center --verbose
**
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
assertion failed: (G_IS_OBJECT (object))
Bail out!
cc-object-storage:ERRO
These error on the icons it happened because of re\installation of GIMP then
should be solved. In detail I had installed GIMP 2.04, I installed GIMP 2.10
over GIMP 2.04 and later I uninstalled GIMP 2.04. Then the problem has been
solved uninstalling both and reinstalling GIMP 2.10.
Thank You.
-
22 matches
Mail list logo
