Can this please be backported to 18.04, give it's 10 year LTS status
--
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/1637988
Title:
gvfsd-nfs not present in gvfs-backends, why?
To
Just installed Ubuntu 18.04 LTS on HP EliteBook 8470p. Got the same
error on fresh boot. It probebly was because of ubuntu now uses screen
rotation gyro(?) and started to rotate screen. Anyway, to steps to fix.
1. CTRL+ALT+F2 to get into console.
2. Login
3. Do
Sorry for the delay in getting back to you Svilen. May be an upstream
report is long overdue? See comment #3.
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Confirmed fixed in Pop_OS 18.10 using the test case provided.
--
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/1763892
Title:
144Hz/120Hz monitor but mutter seems to cap rendering at
** Changed in: mutter
Status: In Progress => Fix Released
--
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/1687246
Title:
GNOME Shell should support fractional
** Changed in: gnome-settings-daemon
Status: Unknown => Won't Fix
** Changed in: gnome-settings-daemon
Importance: Unknown => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Problem remains in 18:10, Wayland, Gnome 3.30.1, 64-bit,
4.18.0-15-generic
--
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/1704765
Title:
can't drag file from desktop to folder
Public bug reported:
When you configure your window title bar buttons to be on the left
instead of the right in the tweaks app, the close window button is cut
off in the Disks app. I don't see this behavior in other apps. See
attached screenshot for illustration of what I mean.
ProblemType: Bug
** Bug watch added: GNOME Bug Tracker #699642
https://bugzilla.gnome.org/show_bug.cgi?id=699642
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=699642
Importance: Unknown
Status: Unknown
** Description changed:
Expected:
Be able to
I had similar issues where the upgrade from 16.04 to 18.04 resulted in blank
screen,
The key to finding the problems was reviewing the errors in the file
/var/log/syslog
gnome-session[2851]: X Error of failed request: BadValue (integer parameter
out of range for operation)
Upstream issue showing "RESOLVED FIXED" on 2012-04-28
No further comments for almost 7 years so I'm closing this as fixed
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried:
- Booting 18.04.2 from a usb disk
- The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of
other bugs)
- The 18.04 default Ubuntu Xorg session
all of them seem to be showing reasonable <1% gnome-shell CPU usage
Hello guys
Perfect!
Many thanks to all involved for the prompt resolution of the problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1817128
Title:
gnome-keyring not
Attached.
** Attachment added: "dump.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812527/+attachment/5242850/+files/dump.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
Upstream bug closed "RESOLVED FIXED" on 2011-03-11
Further to comment #27, closing as fixed
** Changed in: epiphany-browser (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Upstream issue was closed "RESOLVED FIXED" on 0112-02-23
With no further comments here for almost 8 years I'm closing this as being fixed
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Upstream bug was closed "RESOLVED FIXED" on 2012-10-29
Closing as fixed as no further activity here or upstream for over 6 years
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Upstream issue showing "RESOLVED FIXED" on 2010-12-15
With no comments here for over 9 years I'm treating this as being fixed.
** Changed in: epiphany-browser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thanks for replying Erik.
As issue was not confirmed by another user will use "Invalid" to close.
** Changed in: epiphany-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Unable to reproduce. Please close.
--
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/1206981
Title:
Text form field not redrawn upon HOME/END keypress with some CSS
styles
Can anyone affected post a the result of
journalctl /usr/bin/gnome-shell -b
Or otherwise follow what explaind here to have a full javascript dump
too.
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details
*** This bug is a duplicate of bug 1812683 ***
https://bugs.launchpad.net/bugs/1812683
This is funny, yes. "LANG=C rhythmbox" works. Deactivated the alternative
toolbar then, and it worked again.
Thanks, this is a dupe.
** This bug has been marked a duplicate of bug 1812683
rhythmbox
This bug was fixed in the package gnome-keyring - 3.31.91-1ubuntu1
---
gnome-keyring (3.31.91-1ubuntu1) disco; urgency=medium
* Sync with Debian. Remaining changes:
- debian/user/*, debian/gnome-keyring.links, debian/gnome-keyring.install:
+ Install units to start
Thanks for your reply. Closing as "Invalid" as issue never confirmed by
another user.
** Changed in: epiphany-browser (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in
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 11.10 (oneiric) reached end-of-life on May 9, 2013.
Do you still see a problem related to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at 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.
Your problem may
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
Hi,I think that you can close it. I do not even remember the bug.Thank you,César
"Never increase, beyond what is necessary, the number of entities required to
explain anything" --- William of Ockham (1285-1349) "Para qué repetir los
errores antiguos habiendo tantos errores nuevos que cometer?"
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 15.04 (vivid) reached end-of-life on February 4, 2016.
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 11.04 (natty) reached end-of-life on October 28, 2012.
Do you still see a problem related to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at 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.
Your problem may
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.10 (quantal) reached end-of-life on May 16, 2014.
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 10.04 (lucid) reached end-of-life on May 9, 2013.
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 11.10 (oneiric) reached end-of-life on May 9, 2013.
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 8.04 (hardy) reached end-of-life on May 12, 2011.
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
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 11.10 (oneiric) reached end-of-life on May 9, 2013.
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 8.04 (hardy) reached end-of-life on May 12, 2011 and
Ubuntu 9.10 (karmic) reached end-of-life
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 11.04 (natty) reached end-of-life on October 28, 2012.
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 11.04 (natty) reached end-of-life on October 28, 2012.
Do you still see a problem related to
I deleted all printers and waited for CUPS / driverless to find them again.
Here a few CLI outputs (which are small enough so I dare to spost them inline )
$ ls -1 /etc/cups/ppd/
Kyocera_ECOSYS_P6026cdn.ppd
Kyocera-ECOSYS-P6026cdn.ppd
Kyocera_ECOSYS_P6026cdn.ppd.O
Kyocera-ECOSYS-P6026cdn.ppd.O
$
Thank you for your bug report. Could you type 'backtrace' in gdb to get
more information on the issue?
Also could you try to start with another locale or to disable the
alternative toolbar plugin? The issue sounds similar to bug #1812683
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided
Thank you for your bug report, as indicated by the error message (which
could probably be a bit nicer/user friendly) the packaging system seems
currently locked by another proceess. Did you have any other packaging
tools in use at the time? Did that resolve itself after some time?
** Changed in:
Public bug reported:
I hope this is no dupe.
Since I opened a flac file per doubleclick on my desktop with Rhythmbox, it
crashes everytime right after the start, even when started without parameters.
I just started a gdb session and ran rhythmbox, maybe this in fo helps a bit.
Please tell me
Second file. The printer is added automatically twice. Maybe this is
because the printer has a print server, which exports the printer again
and announces it to the network? KM15881D.local is the network name of
the printer.
** Attachment added: "autogenerated 2. ppd file"
This file is named .0 because I have the printer installed with a custom
ppd file (from kyocera) manually - with the same name, so I think cups
adds the .0 automatically.
** Attachment added: "IPP PPD file"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-calendar (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
** Changed in: seahorse (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/231502
Title:
Passphrase dialog
Hi everyone,
I'm not exactly sure how but this is now fixed, I did an update and it works.
Thanks to everyone who worked on this fix.
My question is, can updates that break accessibility be stopped until they are
accessible for all?
This issue should not have happened and I wonder how we can stop
Bug did not expire due to bug watch
No reply to comment #6 or to upstream request
Closing as invalid as issue not confirmed
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Bug did not expire due to bug watch
No reply to comment #6 or to upstream request
Closing as invalid as issue not confirmed
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
53 matches
Mail list logo
