[Bug 1586835] Re: ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

2018-06-14 Thread Bruce Smith
I have a very similar experience on Ubuntu MATE 18.04.

/run/user/1000/keyring/ssh is opened by gnome-keyring-daemon
/run/user/1000/keyring/.ssh is opened by /usr/bin/ssh-agent
$SSH_AUTH_SOCK points to /run/user/1000/keyring/ssh

When I try to open an SSH session to another machine it hangs just after
"SSH2_MSG_NEWKEYS received"

Changing $SSH_AUTH_SOCK to point to /run/user/1000/keyring/.ssh allows
the SSH to complete

-- 
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/1586835

Title:
  ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1586835/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1762168] Re: package libmutter-1-0:amd64 (not installed) failed to install/upgrade: no package named 'libmutter-1-0:amd64' is installed, cannot configure

2018-06-14 Thread Launchpad Bug Tracker
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mutter (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1762168

Title:
  package libmutter-1-0:amd64 (not installed) failed to install/upgrade:
  no package named 'libmutter-1-0:amd64' is installed, cannot configure

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1762168/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1681269] Re: Launcher Type=link, can not be opened with other application

2018-06-14 Thread Launchpad Bug Tracker
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1681269

Title:
  Launcher Type=link, can not be opened with other application

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1681269/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Daniel van Vugt
It sounds like you mean you just can't click on things.

There is a whole family of those bugs to check out here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick
https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=noclick

** Tags added: noclick

** Also affects: mutter (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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Stephen Allen
Yes it does accept focus but doesn't activate. Did a Cold Boot up this
afternoon and the problem doesn't occur - seems only to happen on warm
reboots. I'll look at the other bug in the am my time. Bedtime now.

On Thu, Jun 14, 2018 at 10:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Also, this sounds contradictory:
>
> "GDM3 accepts focus but won't accept any input either from keyboard or
> mouse."
>
> You can't set focus without using a keyboard or mouse. So can you
> clarify what that means?
>
> ** Changed in: gdm3 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1776901
>
> Title:
>   Startup or Reboot GDM3 Keyboard/Mouse Not Working
>
> Status in gdm3 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I don't reboot often due to running LTS. However over the past month
>   or so, on subsequent reboots after upgrades, GDM3 accepts focus but
>   won't accept any input either from keyboard or mouse.
>
>   The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to
>   a console, which won't give me a login prompt until I hit the 'return'
>   key. Then I can go back to the GDM3 session and login normally.
>
>   I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current
>   updates applied.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gdm3 3.28.2-0ubuntu1.2
>   ProcVersionSignature: Ubuntu
> 4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
>   Uname: Linux 4.15.0-20201805060708-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   Date: Thu Jun 14 08:44:36 2018
>   InstallationDate: Installed on 2018-01-19 (146 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   SourcePackage: gdm3
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions
>
-- 

This email is printed from 100% recycled electrons.

-- 
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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776916] Re: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files\n"]

2018-06-14 Thread Daniel van Vugt
jibel, it sounds like you might have a file descriptor leak, which is
something I don't ever recall seeing in gnome-shell before.

If you can reproduce the issue in future then please try eliminating
extensions:

b'org.gnome.shell' b'enabled-extensions' b"['alternate-tab@gnome-shell-
extensions.gcampax.github.com', 'bettervol...@tudmotu.com', 'dash-to-
d...@micxgx.gmail.com', 'mediapla...@patapon.info',
'nohotcor...@azuri.free.fr', 'sound-output-device-choo...@kgshank.net',
'topic...@phocean.net', 'system-moni...@paradoxxx.zero.gmail.com',
'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']"

** Summary changed:

- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files\n"]

** Summary changed:

- gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files\n"]
+ gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open 
files]

-- 
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/1776916

Title:
  gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many
  open files]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776916/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776916] Re: gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many open files]

2018-06-14 Thread Daniel van Vugt
Or just keep an eye on the list of descriptors in:

/proc/PIDOFGNOMESHELL/fd/

and see if it grows with any duplicates.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

-- 
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/1776916

Title:
  gnome-shell crashed with SIGSEGV [Creating pipes for GWakeup: Too many
  open files]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776916/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Daniel van Vugt
Also, this sounds contradictory:

"GDM3 accepts focus but won't accept any input either from keyboard or
mouse."

You can't set focus without using a keyboard or mouse. So can you
clarify what that means?

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

-- 
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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776901] Re: Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Daniel van Vugt
Stephen,

Would you say this is the same as bug 1776534?

-- 
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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776534] Re: Input devices stop working after logout or switch-user

2018-06-14 Thread Daniel van Vugt
** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => 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/1776534

Title:
  Input devices stop working after logout or switch-user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776534/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777018] Re: gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

2018-06-14 Thread Apport retracing service
*** This bug is a duplicate of bug 1664613 ***
https://bugs.launchpad.net/bugs/1664613

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 #1664613, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152784/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152786/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152789/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152790/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152791/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152792/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1777018/+attachment/5152793/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1664613

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1777018

Title:
  gnome-terminal-server crashed with SIGSEGV in gdk_display_get_event()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1777018/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777013] [NEW] /usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

2018-06-14 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
nautilus.  This problem was most recently seen with package version 
1:3.18.4.is.3.14.3-0ubuntu6, the problem page at 
https://errors.ubuntu.com/problem/0e3038b0c9af56d760909f8c27a8d125eb09d8dc 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kylin-14.10 kylin-15.04 raring saucy trusty utopic vivid wily xenial

-- 
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/1777013

Title:
  
/usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1777013/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1777013] Re: /usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

2018-06-14 Thread Brian Murray
This are still occurring quite regularly on an LTS release, Ubuntu
16.04, of Ubuntu.

-- 
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/1777013

Title:
  
/usr/bin/nautilus:11:g_type_check_instance:g_signal_connect_data:set_pending_icon_to_reveal:end_renaming_mode:nautilus_canvas_container_clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1777013/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

2018-06-14 Thread Gunnar Hjalmarsson
Installed im-config 0.34-1ubuntu1.2 from bionic-proposed, rebooted, and
started a Wayland session. Could input Japanese and Chinese characters
in LO Writer using ibus-mozc respective ibus-libpinyin without LO Writer
crashing, so this version fixes the regression reported in comment #17.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-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/1761554

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered

2018-06-14 Thread Brian Murray
Hello Jeremy, or anyone else affected,

Accepted im-config into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/im-
config/0.34-1ubuntu1.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: im-config (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-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/1761554

Title:
  [bionic] Extended characters in GNOME screen keyboard don't get
  entered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776978] [NEW] Update to calendar invitations cannot be processes

2018-06-14 Thread Jürgen Kübler
Public bug reported:

I am using a caldav calendar on a synology NAS and observed issues with 
calendar invitations I previously received. When I open one of these events I 
get the warning 'Event cannot be fully edited, because you are not the 
organizer' which I can live with. However, I cannot process any update I 
receive to these invitation.
The calendar entry is identified. Message: 
  Found the appointment in the calendar “myCal”
When I click on 'Accept' I get the message:
  Unable to send item to calendar “mycal”. Cannot receive calendar objects: 
Failed to put data: HTTP error code 412 (Precondition Failed): Existing 
resource matches "If-None-Match" header - not accepted.[if-none-match]
and the event remains unchanged.

Updates are both possible with Thunderbird on the same machine and on my
iPhone

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: evolution 3.28.1-2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 14 21:59:26 2018
InstallationDate: Installed on 2018-05-02 (42 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: evolution (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1776978

Title:
  Update to calendar invitations cannot be processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1776978/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774810] Re: Nautilus shows wrong trash icon if not emptied before unplugging external drive

2018-06-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nautilus (Ubuntu)
   Status: New => Confirmed

-- 
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/1774810

Title:
  Nautilus shows wrong trash icon if not emptied before unplugging
  external drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774810/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 49579] Re: screen doesn't lock when some menu is open

2018-06-14 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579

Title:
  screen doesn't lock when some menu is open

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1755536] Re: gnome-control-center is not open ubuntu 18.04

2018-06-14 Thread Loren Pearson
Thanks Abhishek AN (darkabhi) . That fixed it for me.

-- 
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.launchpad.net/bugs/1755536

Title:
   gnome-control-center is not open ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1755536/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 49579]

2018-06-14 Thread Ajax-a
*** This bug has been marked as a duplicate of bug 4286 ***

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/49579

Title:
  screen doesn't lock when some menu is open

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1775798] Re: Inappropriately uses Snapcraft icon when snap is missing an icon

2018-06-14 Thread Adolfo Jayme
** Changed in: gnome-software (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

-- 
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/1775798

Title:
  Inappropriately uses Snapcraft icon when snap is missing an icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1775798/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776534] Re: Input devices stop working after logout or switch-user

2018-06-14 Thread Ananth P
My /var/crash has 3 crashes currently, none of them at the time of the
problem:

* update manager
* puredata
* apport-gtk

errors.ubuntu.com has a longer list, includes nautilus, audacity,
xwayland, gvfs-backends. (gdm3 is not in the list).

I brought the system to the same frozen state again (happens everytime I
log out), logged in through ssh, didn't see any change in /var/crash.
None shows up at journalctl either (attachment to original post). Could
it be possible that it's not really a crash but some invalid state?

Let me know if I can get some additional log/info through ssh when the
machine is in problem state.

-- 
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/1776534

Title:
  Input devices stop working after logout or switch-user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776534/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1740869] Re: is not respoding window is constantly showing when debugging a program in Eclipse

2018-06-14 Thread Phil Wolff
It appears that the dialog is system-wide modal. Is that really
necessary? If so, it should also appear on top of *every* window stack
in the system, not just the stack containing the offender.

-- 
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/1740869

Title:
   is not respoding window is constantly showing when
  debugging a program in Eclipse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1740869/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1570227] Re: Open Recent Items show as always empty in Gedit

2018-06-14 Thread jimmack
I'm using Linux Mint 18.1 (based on Ubuntu 16.04).
I was experiencing the same problem with gedit and I noticed that GIMP was also 
not populating the document history.  A search for this issue with GIMP found a 
post that explained that under Preferences -> System Settings -> Privacy, there 
is an option to "Remember recently accessed files" (defaulting to "Off").  I've 
enabled that and now I'm getting my history lists again, although on gedit, 
it's only through the Open \/ menu.
Personally, I'd prefer it if the File menu was fixed, but if we're going to 
have to use the new open drop-down, then the "Open Recent" option needs to be 
removed to avoid further confusion.

-- 
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/1570227

Title:
  Open Recent Items show as always empty in Gedit

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1570227/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776916] Re: gnome-shell crashed with SIGSEGV

2018-06-14 Thread Jean-Baptiste Lallement
** Information type changed from Private 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/1776916

Title:
  gnome-shell crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1776916/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1572762] Re: File-roller shows home folder in each zip

2018-06-14 Thread Merlijn Sebrechts
** Changed in: file-roller (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1572762

Title:
  File-roller shows home folder in each zip

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/1572762/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 26662] Re: using the filename to get the mimetype is not always correct

2018-06-14 Thread Merlijn Sebrechts
Marked as fix released because the original issue is fixed.

** Changed in: file-roller (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: file-roller (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 the bug report.
https://bugs.launchpad.net/bugs/26662

Title:
  using the filename to get the mimetype is not always correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/26662/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 26662] Re: using the filename to get the mimetype is not always correct

2018-06-14 Thread Merlijn Sebrechts
I created a new issue for this: https://gitlab.gnome.org/GNOME/file-
roller/issues/2

Although I'm not sure this issue and the new issue are related.

-- 
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/26662

Title:
  using the filename to get the mimetype is not always correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/26662/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776901] [NEW] Startup or Reboot GDM3 Keyboard/Mouse Not Working

2018-06-14 Thread Stephen Allen
Public bug reported:

I don't reboot often due to running LTS. However over the past month or
so, on subsequent reboots after upgrades, GDM3 accepts focus but won't
accept any input either from keyboard or mouse.

The work-a-round that works for me is to 'Ctl+Alt+F(number) to get to a
console, which won't give me a login prompt until I hit the 'return'
key. Then I can go back to the GDM3 session and login normally.

I'm reporting this from Vanilla Gnome Ubuntu 18.04, all current updates
applied.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 
4.15.0-20201805060708.0+mediatree+hauppauge-generic 4.15.17
Uname: Linux 4.15.0-20201805060708-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Jun 14 08:44:36 2018
InstallationDate: Installed on 2018-01-19 (146 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic gnome3-ppa third-party-packages

-- 
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/1776901

Title:
  Startup or Reboot GDM3 Keyboard/Mouse Not Working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776901/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1743736] Re: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")

2018-06-14 Thread Alexander
I can confirm it as well. Occurred after upgrade to 18.04 (X and
Wayland), worked fine with 16.04 (on Gnome). Unfortunately this is a
core feature to my workflow, is there a workaround?

-- 
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/1743736

Title:
  In overview, windows from all workspaces are shown for the second
  display (when using "Workspaces span displays")

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1743736/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 970686] Re: Activities search does not complete recent documents anymore

2018-06-14 Thread Stu
Confirming.

-- 
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/970686

Title:
  Activities search does not complete recent documents anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/970686/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1701047] Re: Renaming of conf file fails

2018-06-14 Thread Łukasz Zemczak
Hello Gunnar, or anyone else affected,

Accepted fonts-guru-extra into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fonts-guru-
extra/2.0-4ubuntu0.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: fonts-guru-extra (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-guru-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1701047

Title:
  Renaming of conf file fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-beng-extra/+bug/1701047/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776863] Re: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread Apport retracing service
*** This bug is a duplicate of bug 1776862 ***
https://bugs.launchpad.net/bugs/1776862

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 #1776862, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1776862
   package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 
package post-installation script subprocess returned error exit status 127

-- 
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/1776863

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776863/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776862] Re: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
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/1776862

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776862/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776862] Re: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread golomb
no more comment

-- 
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/1776862

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776862/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776862] [NEW] package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread golomb
Public bug reported:

no more comment

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun 14 10:37:54 2018
ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
InstallationDate: Installed on 2018-05-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gdm3
Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 
package post-installation script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.gdm3.custom.conf: [modified]
mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
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/1776862

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776862/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776863] [NEW] package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 127

2018-06-14 Thread golomb
*** This bug is a duplicate of bug 1776862 ***
https://bugs.launchpad.net/bugs/1776862

Public bug reported:

no more info

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Jun 14 10:37:54 2018
ErrorMessage: installed gdm3 package post-installation script subprocess 
returned error exit status 127
InstallationDate: Installed on 2018-05-29 (16 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gdm3
Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 
package post-installation script subprocess returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2018-05-29T07:41:49.115219

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
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/1776863

Title:
  package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed
  gdm3 package post-installation script subprocess returned error exit
  status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1776863/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package desktop-file-utils -
0.23-1ubuntu3.17.10.1

---
desktop-file-utils (0.23-1ubuntu3.17.10.1) artful; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:30:25
-0700

** Changed in: desktop-file-utils (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: desktop-file-utils (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package desktop-file-utils -
0.23-1ubuntu3.18.04.1

---
desktop-file-utils (0.23-1ubuntu3.18.04.1) bionic; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:30:25
-0700

** Changed in: desktop-file-utils (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1769954] Update Released

2018-06-14 Thread Łukasz Zemczak
The verification of the Stable Release Update for desktop-file-utils has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1769954] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package desktop-file-utils - 0.22-1ubuntu5.2

---
desktop-file-utils (0.22-1ubuntu5.2) xenial; urgency=medium

  * Use noawait trigger (LP: #1769954)

 -- Julian Andres Klode   Tue, 05 Jun 2018 11:43:53
-0700

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1769954

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1769954/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs