Some further information: As I'm intending to switch to MATE for
preference anyway, I went ahead and installed the ubuntu-mate-desktop
package and set gdm3 to default in the process (I believe it is already
default for Bionic?); now on boot I see the MATE loading screen, am
taken to the Gnome
Public bug reported:
On my fresh install of Ubuntu 18 (minimal install last night) the
control center will not open; it shows a loading notification on the top
panel briefly, then does nothing. I have attempted to restore
functionality by re-installing to no avail. The system does not
recognise
I'm getting a similar crash. Here's the backtrace:
#0 0x775ee129 in gtk_tree_model_get_valist () at /usr/lib/libgtk-3.so.0
#1 0x775ee450 in gtk_tree_model_get () at /usr/lib/libgtk-3.so.0
#2 0x77d4b1ca in () at /usr/lib/eog/libeog.so
#3 0x77d4f76a in () at
** Description changed:
Experienced complete system lockup and hang on two different machines
when trying to boot a VirtualBox VM running Fedora 29 live (no virtual
disk) when Firefox is open with a few (~5-10) inactive tabs.
System 1:
4GB RAM host
1536MB guest, no virtual disk
Thanks
--
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/1809567
Title:
Password Information visible after logging out/visiting virtual
terminal
To manage notifications about this
+1 for gnome-shell 3.28.3-0ubuntu0.18.04.4 bionic-proposed - fixed for
me
--
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/1765304
Title:
Ubuntu 18.04's ibus package breaks
** Information type changed from Public Security to Public
--
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/1723857
Title:
onscreen keyboard appears whenever i touch touchscreen
apport information
** Tags added: apport-collected bionic wayland-session
** Description changed:
Running Ubuntu 18.04, GDM3 & Gnome
Problem: Password information visible on a virtual terminal
Steps to produce:
1. During a regular session (either Gnome or i3 in my case) either log
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1809567/+attachment/5226470/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
https://bugs.launchpad.net/bugs/1809567/+attachment/5226471/+files/modified.conffile..etc.gdm3.custom.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
apport information
** Attachment added: "modified.conffile..etc.pam.d.gdm-password.txt"
https://bugs.launchpad.net/bugs/1809567/+attachment/5226472/+files/modified.conffile..etc.pam.d.gdm-password.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I can confirm the problem on my system:
gvfsd-metadata[PID]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE
(device)' failed
(hundrets of entries ...)
As a temporary workaround I killed (only) the gvfsd-metadata process (will
auto-respawan, unless changed in systemd) and erased the
Public bug reported:
On the top panel, the date/time info are displayed as:
四 1月3 09:38
It should be displayed as:
星期四 1月3日 09:38
If I switch off the date part, it is correct:
星期四 09:38
Is it because of the width limitation of date/time widget, or something
wrong with i18n?
** Affects:
Hello Gaussian, if you're still seeing this can you please run:
apport-collect 1809567
to attach some package information and logs to this bug?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
It works for me using XFCE but I agree it doesn't work on KDE or Gnome.
--
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/1767654
Title:
[Intel Braswell] Cursor gets stuck on
THe bug is stll here in 2019, on 18.04.1!
I had loads of files in .local/share/Trash/expunged.
Removing them, they vanished, (rapidly), but the disc space occupied has
not been released. 256GB on this machine, and it has run out of space.
Backups of home/user are taking up 192GB.
--
You
XFCE 18.04, nautilus was working fine. Started to see this behaviour
recently. Possibly due to adding nautilus-extension-gnome-terminal.
Commenting out the line:
x-scheme-handler/file=exo-file-manager.desktop
in
/usr/share/xubuntu/applications/defaults.list (provided by Xubuntu)
Worked
I have this message each time i try to write a review for a snap package
--
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/1808880
Title:
Got unknown content type text/html
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
Do we work on the same problem? My nfs share is exported by an external file
server (i.e. a synology disc station) and imported by Ubuntu 18.04.
Thus, the line in my /etc/fstab on my Ubuntu system reads
xxx.yyy.zzz:/volume1/homes/peter /media/peter/MyStorage nfs defaults,intr 0 0
This links the
I have this message from Ubuntu Software trying to write a review on a
snap application. After which my report appear with reporter name
'unknown'
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
** Changed in: nautilus (Ubuntu)
Status: Invalid => Incomplete
--
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/1800043
Title:
nautilus cannot write on nfs file share
To
I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS,
used nfs-kernel-server: 1:1.3.4-2.1ubuntu5 and nfs-common:
1:1.3.4-2.1ubuntu5 nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not
reproduce the problem. Ensure the system is properly patched.
** Changed in: nautilus (Ubuntu)
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
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/1800043
Title:
nautilus cannot write on nfs file share
To manage
I exported a nfs share (rw,sync,no_subtree_check) on Ubuntu 18.04.1 LTS
Release: 18.04
nautilus: 1:3.26.4-0~ubuntu18.04.2 and could not reproduce the problem.
Nautilus works OK.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- Nautilus (list view) - selection is done by a whole line instead of a file
name which causing problem to get the right mouse click menu of the current
folder
+ Nautilus (list view) - selection is done by a whole line instead of by a file
name which causing problem to get
** Summary changed:
- Nautilus (list view) - it is not always possible to get the right mouse click
menu of the current folder
+ Nautilus (list view) - selection is done by a whole line instead of a file
name which causing problem to get the right mouse click menu of the current
folder
--
** Summary changed:
- In the nautilus list view is not always possible to get the right mouse click
menu of the current folder
+ Nautilus (list view) - it is not always possible to get the right mouse click
menu of the current folder
--
You received this bug notification because you are a
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Presumably you resolved this issue a long time ago and we can now close
this report?
** Changed in: gedit (Ubuntu)
Status:
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Presumably your problem was resolved a long time ago and we can now
close this report?
** Changed in: gedit (Ubuntu)
Status:
Further to reporter's comment #2 (also tested in Ubuntu 18.04) I'm
marking this as "Fix Released" to close.
** Changed in: gedit (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit
Fixied in Bionic, Artful is EOL.
** Changed in: totem (Ubuntu)
Status: Confirmed => Fix Released
--
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/1710858
Title:
totem crashed
I do not, honestly it’s been so long that I’d forgotten about this. I do
believe this was resolved with the update to 16.04 however, and has not
persisted since.
> On Jan 2, 2019, at 3:51 AM, Paul White <1497...@bugs.launchpad.net> wrote:
>
> We are sorry that we do not always have the capacity
** Summary changed:
- Not always possible in the nautilus list view to get the right mouse click
menu of the current folder
+ In the nautilus list view is not always possible to get the right mouse click
menu of the current folder
--
You received this bug notification because you are a member
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.
Do you still see a problem related to the one that you reported in a
currently supported version of
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.04 (raring) reached end-of-life on January 27, 2014.
Do you still see a problem related
** Tags removed: maverick
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/685541
Title:
saving new file to selected directory in file browser
To manage
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
** Tags added: bionic
--
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/692432
Title:
reload in nautilus temporarily blanks file list
To manage notifications about this bug go 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.04 (raring) reached end-of-life on January 27, 2014.
Do you still see a problem related
There is only a fix released for disco. When can we expect a fix for
Cosmic and Bionic?
--
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/1769383
Title:
Ubuntu dock/launcher is
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 13.04 (raring) reached end-of-life on January 27, 2014.
Do you still see a problem related
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner.
Presumably your issue was resolved a long time ago and this bug report
can now be closed?
Thank you for helping make Ubuntu better.
Paul White
[Ubuntu Bug Squad]
** Description changed:
Mon
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.
Do you still see a problem related to the one that you reported in a
currently supported version of
Upstream issue was closed "RESOLVED OBSOLETE" on 2011-04-04 due
to recent changes involving gio. Confirmed password not shown
when using Ubuntu 18.04 so marking "Fix Released" to close.
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
Upstream bug is showing a duplicate of #330644
which was closed "RESOLVED FIXED" on 2011-02-25
Marking "Fix Released" to close
** Changed in: nautilus (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Further to comment #21 and no further comments for nearly
three years I'm closing this by marking "Fix Released".
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
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 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 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 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 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 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 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 14.10 (utopic) reached end-of-life on July 23, 2015.
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 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 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 15.10 (wily) reached end-of-life on July 28, 2016.
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 15.10 (wily) reached end-of-life on July 28, 2016.
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 13.10 (saucy) reached end-of-life on July 17, 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 15.10 (wily) reached end-of-life on July 28, 2016.
Do you still see a problem related to the
Forgot to mention, I have a dual-monitor setup, which I've read may not
be supported.
That doesn't explain #1 and #2 though, or why include this rudimentary
feature at all, when there is much more powerful and easy-to-use
software[1] that could be bundled, with a UI that lets the user select a
66 matches
Mail list logo
