@ daisy
You subscribed me to this bug report, but I'm no longer involved in
Ubuntu's development.
So I'm unsubscribing.
--
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/1812359
Title:
Output of echo $XDG_SESSION_TYPE is x11
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
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/1812359
Title:
Login
[Expired for gnome-keyring (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: gnome-keyring (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
h
[Expired for gnome-system-monitor (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system
[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Expired
--
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/b
GNOME Software doesn't have a field to show this, so this needs some
thought as to how it fits into the upstream design.
** Changed in: gnome-software (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I tried this on my 19.04 machine and Chromium is showing as being
confined (both when not installed and installed).
There are two things that must be true for G-S to consider a snap to be
confined:
1. The snap must be confined:
$ curl --unix-socket /run/snapd.socket
http://localhost/v2/find?nam
If installed, also check the installed snap metadata:
$ curl --unix-socket /run/snapd.socket http://localhost/v2/snaps/chromium|jq
.result.confinement
"strict"
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
+1, Ubuntu 18.04.1. Just the bluetooth so far for me.
Running on Dell XPS 13 9380
3840 X 2160 @ 200%
Bumping it to 300% it looks normal (of course everything else on the
screen is far too large to be workable)
** Attachment added: "stretched_bluetooth"
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
Ubuntu 18.04, all gnome extensions get turned off after waking up from sleep
Noticed since: past 1-2 week
Workaround: Alt+F2 followed by 'r' - Turns on the extensions which I had on
earlier
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
I wasn't having any problems with Ubuntu 18.04 but ever since I upgraded
to Ubuntu 18.10 gnome-shell seems to crash two out of every three times
the screensaver starts.
I used ubuntu-bug on a /var/crash file but I have no idea what happened
to it: it showed me the info in a window and I said go ah
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-de
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-de
Not sure if related: Not only the current layout indicator change after
a lock but the whole indicator area. Screenshots of before/after:
https://i.imgur.com/OazRcHL.png
#workaround: Restart Gnome Shell: Alt+F2 r
--
You received this bug notification because you are a member of Ubuntu
Desktop Bu
** Description changed:
When right clicking on a PGP key and clicking properties, it works fine
the first time, and opens the properties menu correctly. When closing
that properties menu, and then clicking properties again, it does not
properly open the menu, only showing a white propertie
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 12.10 (quantal) reached end-of-life on May 16, 2014.
Do you still see a problem related to th
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 12.04 (precise) reached end-of-life on April 28, 2017.
Do you still see a problem related to
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 12.04 (precise) reached end-of-life on April 28, 2017.
Do you still see a problem related to
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 13.10 (saucy) reached end-of-life on July 17, 2014.
Do you still see a problem related to the
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 12.04 (precise) reached end-of-life on April 28, 2017.
Do you still see a problem related to
Public bug reported:
When right clicking on a PGP key and clicking properties, it works fine
the first time, and opens the properties menu correctly. When closing
that properties menu, and then clicking properties again, it does not
properly open the menu, only showing a white properties screen. W
As per bug description bug was fixed (on 2013-12-11)
so marking "Fix Released" to close as backporting fix
to an earlier release is no longer relevant.
** Changed in: epiphany-browser (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ub
** Description changed:
Estou querendo uma alternativa do firefox, já que eu não consigo
reproduzir vídeos flash player, e nunca concertam o bug, então re-solvir
instalar o epiphany tudo legal, tudo o máximo ate que então para de
responder.
+
+ Google translation:
+ I'm looking for a fire
Upstream reports closed "RESOLVED FIXED" on 2010-10-16
Not reproducible here using Ubuntu 18.04 so closing as fixed
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Incomplete
** Changed in: epiphany-browser (Ubuntu)
Status: Incomplete => Fix Released
--
You received th
Upstream report showing "RESOLVED FIXED" on 2012-01-01
Filed against obsolete GNOME 2 package
No comments here for over 8 years so closing as fixed
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ub
** Tags removed: artful
** Tags added: cosmic disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1721955
Title:
Human, Human-Clearlooks and other themes have incorrect gray windo
Sorry for the belated response.
Here's a test kernel:
https://people.canonical.com/~khfeng/lp1745032-new-fix/
Will request an SRU soon.
--
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.laun
Public bug reported:
Steps to reproduce:
$ sudo apt-get install appstream
$ sudo appstreamcli refresh-cache --force --verbose
AppStream cache update completed successfully.
# (it works good, because shared-mime-info is installed by default in Ubuntu)
$ sudo apt-get remove shared-mime-info
$ sudo
** Description changed:
6 year old HP laptop with A6 processor. Loaded Xubuntu 18.10 then MATE
18.10. I saved a login password but it did not show in the keyring when
I looked. I did not check any other parts of Seahorse since I don't plan
to use encryption. Reloaded MATE 18.04 and it work
The error seems to have been fixed.
Can't reproduce it anymore.
:)
Gabor Toth
+45 21 63 49 83 (tel:+4521634983)
+36 70 323 9832 (tel:+36%2070%20323%209832)
gabor...@gmail.com (https://link.getmailspring.com/link/1548601665
.local-
26c7f5c0-1889-v1.5.5-b7939...@getmailspring.com/0?redirect=mail
I was seeing this same warning. The only overlap of extensions with the
list above and my list (I only use 3 extensions) is 'system-
moni...@paradoxxx.zero.gmail.com'.
I realized I had installed that extension from source rather than
through the extensions website since it needed to be built from
So far, I have not experienced the problem again. Thank you for your
help!
--
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/1813139
Title:
Screen unlocked after resume, black fli
I have an update although. I enabled password promt on login, but the
problem remains. I have two gnome extensions installed. On previous
checks it doesn't happened that (if the password was enabled, then
everything was fine). Now, either with password either without,
sometimes (about 50%) returnin
Tested various images using Ubuntu 18.04.
No issues noted so closing as fixed.
** Changed in: hundredpapercuts
Status: Incomplete => Fix Released
** Changed in: ubuntu-gnome
Status: Incomplete => Fix Released
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Rele
Bug did not expire due to bugwatch
Upstream issue is a duplicate of #724929 which
was closed "RESOLVED FIXED" on 2014-02-22
No reply from reporter so closing as fixed
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you
I think I have a similar problem. It started on 24-JAN-2019 I think.
When I return to my PC after a while I hit Escape to get rid of the
shield as normal (I don't have a password lock) and return to my desktop
but with all my previous running applications missing. The left hand bar
is present and
After having a 2nd look I think the feature isn't this major yet => If
someone can decide upon this ticket's priority it perhaps can be set to
"low".
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shotwell in Ubuntu.
https://bugs.laun
Closing as per comment #6
** Changed in: hundredpapercuts
Status: Confirmed => Invalid
--
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/1584240
Title:
Duplicate Nautilus in
Bug did not expire due to bug watch
No reply to comment #4 or #6 so closing
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://
Bug did not expire due assignment
No comments for over 9 years
Bug filed against obsolete GNOME 2 package
Seems to be a vte bug so closing
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop
For anyone else affected by the missing keyboard layout indicator issue, I
believe this is the bug report you should follow:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscrib
I can confirm the issue on Ubuntu 18.10 (Cosmic) as well. I experienced
that beside locking the screen, seeing the elevated prompt dialog (when
the screen is dimmed) also makes the keyboard layout indicator
disappear. Will be gnome-shell - version 3.30.2-2ubuntu1 available for
cosmic too?
** Attac
Public bug reported:
Shotwell now comes with a faces detection tool in my opinion is a major feature.
In order to enable it after the
meson build
a
cd build&&meson configure -Dface-detection=true&&cd..
has to be executed during the build of the package. Currently this step
is missing.
43 matches
Mail list logo
