Public bug reported:
That's part of fixing bug #1732780 and making files listed in the
desktop overview for the LTS (which is currently not working and a
regression over Unity or upstream GNOME).
The proposed change uses "locate" as a backend (same as unity was doing), the
corresponding patch
Yes, this is present in 17.10.
** Tags added: artful
** Changed in: appmenu-qt (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug was fixed in the package nautilus - 1:3.26.2-0ubuntu1
---
nautilus (1:3.26.2-0ubuntu1) bionic; urgency=medium
* New upstream version
* debian/patches/git_fat_chars.patch:
- list ‘\’ and ‘|’ as non valid on fat filesystems
*
This bug was fixed in the package gnome-software - 3.27.90-1ubuntu1
---
gnome-software (3.27.90-1ubuntu1) bionic; urgency=medium
* Merge with Debian, remaining changes:
+ debian/patches/*.patch: Various Ubuntu changes from ubuntu-master
branch - see patch headers for more
** Changed in: webkit-open-source
Status: Unknown => Won't Fix
** Changed in: webkit-open-source
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
** Changed in: gnome-shell (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Confirmed
** Changed in: mutter (Ubuntu)
See also bug 1728342
** Package changed: linux (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
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/1752680
Title:
Night light does not work in
mate-terminal and terminator have the same problem. The checkboxes for
'allow bold text' can be clicked but they do nothing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
Thanks @vanvugt for keeping me organized; I have moved my issue
(https://bugs.launchpad.net/gnome-shell/+bug/1721428/comments/74) here:
https://lists.debian.org/debian-user/2018/03/msg00021.html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
/org/gnome/terminal/legacy/profiles//allow-bold is set to false in
dconf, but the terminal continues to display boldface, rendering some
fixed-width fonts barely readable.
$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
$
Oops. I wasn't testing the new packages yet. I guess we're waiting on:
gst-plugins-base1.0 (1.13.1-1) experimental; urgency=medium
** Changed in: gst-plugins-base1.0 (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Thanks Laney. It was in the back of my mind -- I knew upstream had done
a fix identical to mine, but they just moved it. I had not stopped to go
looking for it...
I can verify everything seems to be working with the latest bionic
updates.
** Also affects: gst-plugins-base1.0 (Ubuntu)
I would like to find out if this is a problem in libinput.
Can you please try installing Unity (package 'unity-session')? Then log
in to Unity and tell us if the problem also occurs there?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: libinput (Ubuntu)
Please also look in /var/crash for any crash files.
If you find some then:
1. Apply the workaround described in bug 994921.
2. Run: ubuntu-bug /var/crash/YOURFILE.crash
3. Tell us here the ID of the newly created bug(s).
--
You received this bug notification because you are a member of
** Tags added: noclick
** Summary changed:
- Regression: left mouse button stops working
+ Left mouse button gets stuck down (in software), usually after suspend/resume
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libinput (Ubuntu)
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 1752431
When reporting bugs in the future please use apport by using 'ubuntu-
You have been subscribed to a public bug:
When I select "gnome" on login, the session fails to start. If I select
gnome/xorg all is well.
Description:Ubuntu 17.10
Release:17.10
wayland-protocols:
Installed: 1.10-1
Candidate: 1.10-1
Version table:
*** 1.10-1 500
500
dino99, please don't recommend that users use Ubuntu 18.04 now. It's not
even officially in beta yet.
Also, there's no reason to recommend that users use the minimal install
option for this bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
I appreciate the reminder, but Ubuntu Bionic is still under development
and has not been officially released. Does it make sense to recommend
installing pre-release software right now? Perhaps it's better to
suggest installing it when it's actually released.
--
You received this bug notification
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
** Changed in: libpam-ldap (Ubuntu)
Status: Invalid => Incomplete
** Changed in: libpam-ldap (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to accountsservice in Ubuntu.
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still
Public bug reported:
Raised this upstream:
https://github.com/systemd/systemd/issues/8328
In short, in systemd 237 as it ships with Bionic, if a unit has a drop-
in present but has been masked, systemctl is-enabled and systemctl list-
unit-files report incorrect state, showing the units as
Sorry, I made a mistake: the original report and the subsequent comment
apply to xorg session, not wayland. But the bug also occurs with the
wayland session, the only difference being that under wayland, switching
VTs does not make the issue disappear, only logging out and back in
does.
--
You
After some more testing I can add the following:
- The bug is consistently triggered by a suspend/resume cycle (sudo pm-suspend)
- An easier workaround instead of logging out and back in is to switch to a
different VT and switch back.
- Right after resuming, the computer behaves as if the left
And I was wondering why 2 years ago 0,5 Gigabytes of RAM was plentiful
for 32bit and now 4 Gigabytes on 64 bit is too little. Let's hope the
window preview problem gets resolved soon.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Sometimes the left mouse button stops working. The right button, the
movements, and the keyboard all still work normally. The laptop's touch
screen also still works. The left mouse button doesn't work anywhere,
neither in the application nor in the shell widgets.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
*** This bug is a duplicate of bug 1724699 ***
https://bugs.launchpad.net/bugs/1724699
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1724699, so is being marked as such.
*** This bug is a duplicate of bug 1752645 ***
https://bugs.launchpad.net/bugs/1752645
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1752645, so is being marked as such.
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
This bug was fixed in the package unattended-upgrades - 1.0ubuntu1
---
unattended-upgrades (1.0ubuntu1) bionic; urgency=medium
* Merge from Debian unstable
- Remaining changes:
- unattended-upgrades: Do not automatically upgrade the development
release of Ubuntu
** Also affects: glib2.0 (Ubuntu Bionic)
Importance: Medium
Status: New
** Also affects: ubiquity (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu Bionic)
Status: New => Triaged
** Changed in: ubiquity (Ubuntu Bionic)
Importance:
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
Confirming this is being delayed through feature-freeze because of the
sheer volume of other transitions and can be applied when sensible.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
Those reports are from "Kali 2016.2" users, not Ubuntu
** Changed in: gnome-keyring (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-keyring (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: gnome-software (Ubuntu Xenial)
Assignee: (unassigned) => Robert Ancell (robert-ancell)
--
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/1739759
Title:
Daniel - with 1.13 -gl has moved from -bad to -base. I think that
b769f022619db7b46851986494621492342eaafb is the same as your fix, so I
have dropped your patch. Please let me know if that's wrong somehow.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1748450, so is being marked as such.
** Description changed:
- mutter/gnome-shell transition bug
+ Feature Freeze Exception
+
+ The Ubuntu Desktop Team would like to update mutter and gnome-shell to
3.27.92.
- mutter's soname is being bumped (this will probably happen for every
- major new GNOME Shell
Public bug reported:
The Ubuntu Desktop Team would like to update evolution-data-server,
evolution, and evolution-ews to 3.27.91 in preparation for evolution
3.28 (expected release March 12).
Evolution bumped its sonames so we'll need a transition.
Trackers
=
** Summary changed:
-
/usr/bin/gnome-software:11:g_type_check_instance_is_fundamentally_a:g_object_unref:gs_app_dispose:g_object_unref:g_list_foreach
+ gnome-software (11) g_type_check_instance_is_fundamentally_a → g_object_unref
→ gs_app_dispose → g_object_unref → g_list_foreach
--
You
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Invalid
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: nautilus (Ubuntu)
Status: Confirmed => Invalid
--
You
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: gconf (Ubuntu)
Status: Confirmed => Invalid
--
You
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: tracker (Ubuntu)
Status: Confirmed => Invalid
--
You
This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'
http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option
** Changed in: tracker (Ubuntu)
Status: New => Invalid
--
You
*** This bug is a duplicate of bug 1675150 ***
https://bugs.launchpad.net/bugs/1675150
** This bug is no longer a duplicate of bug 1664007
package gnome-keyring 3.20.0-2ubuntu4 failed to install/upgrade: intentando
sobreescribir `/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so',
*** This bug is a duplicate of bug 1675150 ***
https://bugs.launchpad.net/bugs/1675150
** This bug has been marked a duplicate of bug 1675150
package gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: trying to
overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so',
*** This bug is a duplicate of bug 1675150 ***
https://bugs.launchpad.net/bugs/1675150
** This bug has been marked a duplicate of bug 1675150
package gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: trying to
overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so',
*** This bug is a duplicate of bug 1675150 ***
https://bugs.launchpad.net/bugs/1675150
** This bug is no longer a duplicate of bug 1664007
package gnome-keyring 3.20.0-2ubuntu4 failed to install/upgrade: intentando
sobreescribir `/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so',
*** This bug is a duplicate of bug 1675150 ***
https://bugs.launchpad.net/bugs/1675150
** This bug has been marked a duplicate of bug 1675150
package gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: trying to
overwrite '/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so',
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
zenity. This problem was most recently seen with package version 3.27.90-1,
the problem page at
https://errors.ubuntu.com/problem/2b11576fed59ad23c640bc85a266cc82ec30a689
contains more details,
*** This bug is a duplicate of bug 1752533 ***
https://bugs.launchpad.net/bugs/1752533
** This bug has been marked a duplicate of bug 1752533
zenity (6) g_assertion_message → g_assertion_message_error →
ensure_surface_for_gicon → gtk_icon_helper_load_surface →
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zenity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zenity in Ubuntu.
** Summary changed:
-
/usr/bin/zenity:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface
+ zenity (6) g_assertion_message → g_assertion_message_error →
ensure_surface_for_gicon → gtk_icon_helper_load_surface →
** Changed in: zenity (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1752533
Title:
zenity (6) g_assertion_message →
Interesting, I had a display plugged into my laptop and indeed the
external HDMI display had night light enabled by the primary display did
not.
The primary display was running 4K resolution with HiDPi scaling at
200%. I'll try to remember to open a new issue when I return from
holiday.
--
You
*** This bug is a duplicate of bug 1725160 ***
https://bugs.launchpad.net/bugs/1725160
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1725160, so is being marked as such.
76 matches
Mail list logo
