[Bug 1701047] Re: Renaming of conf file fails

2018-06-15 Thread Steve Langasek
Hello Gunnar, or anyone else affected,

Accepted fonts-beng-extra into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fonts-beng-
extra/1.0-6ubuntu0.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-beng-extra (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-orya-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 1701047] Re: Renaming of conf file fails

2018-06-15 Thread Steve Langasek
Fix confirmed with the bionic-proposed version of fonts-guru-extra.

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

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-orya-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 1701047] Please test proposed package

2018-06-15 Thread Steve Langasek
Hello Gunnar, or anyone else affected,

Accepted fonts-deva-extra into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fonts-deva-
extra/3.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-gujr-extra (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-orya-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 1701047] Please test proposed package

2018-06-15 Thread Steve Langasek
Hello Gunnar, or anyone else affected,

Accepted fonts-gujr-extra into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fonts-gujr-
extra/1.0-6ubuntu0.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-orya-extra (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-orya-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 1701047] Please test proposed package

2018-06-15 Thread Steve Langasek
Hello Gunnar, or anyone else affected,

Accepted fonts-orya-extra into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/fonts-orya-
extra/2.0-5ubuntu0.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!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-orya-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 1777212] [NEW] package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

2018-06-15 Thread Thibaut
Public bug reported:

failde to update from 16.04 LTS to 17.10

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gnome-menus 3.13.3-6ubuntu3.1
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sat Jun 16 12:15:39 2018
Dependencies:
 
ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
InstallationDate: Installed on 2017-08-27 (293 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: gnome-menus
Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: bloqué 
en boucle sur le traitement des actions différées (« triggers »), abandon
UpgradeStatus: Upgraded to xenial on 2018-06-16 (0 days ago)

** Affects: gnome-menus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  bloqué en boucle sur le traitement des actions différées (« triggers
  »), abandon

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

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

[Bug 1443794] Re: Folders with large names cause icons to disappear

2018-06-15 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/1443794

Title:
  Folders with large names cause icons to disappear

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

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

[Bug 329610] Re: clicking Eject disk button in nautilus twice in a row ejects disk and displays error message

2018-06-15 Thread Bug Watch Updater
** Changed in: nautilus
   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/329610

Title:
  clicking Eject disk button in nautilus twice in a row ejects disk and
  displays error message

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

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

[Bug 1763837] Re: Update apport hook

2018-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package yelp - 3.28.1-1ubuntu2

---
yelp (3.28.1-1ubuntu2) cosmic; urgency=medium

  * debian/source_yelp.py:
- Use URL to a page with more generic info about seeking support
  (LP: #1763837). Thanks to Gunnar Hjalmarsson for the patch!

 -- Brian Murray   Fri, 15 Jun 2018 14:30:47 -0700

** Changed in: yelp (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Update apport hook

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

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

[Bug 1768176] Re: Unable to suspend computer

2018-06-15 Thread David LaPointe
I'd like to confirm the above observation. With GNOME the user has to
hold down ALT to get the suspend option to appear on shutdown menu (IMHO
this is really poor design). When the ALT key releases it wakes the
computer before it has even really shut down. It is very timing
sensitive. You have to release the ALT key the instant you click the
button for the computer to actually suspend.

It's a simple fix: just make suspend option appear all the time in a
separate button. Why would you want to hide capability from users?

Now, I've seen the computer be unable to suspend for other reasons
(maybe 20% of the time). It seems to be something to do with a process
that refuses to cooperate.

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

Title:
  Unable to suspend computer

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

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

[Bug 1763837] Re: Update apport hook

2018-06-15 Thread Brian Murray
Thanks for working on this, I've gone ahead and sponsored it.

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

Title:
  Update apport hook

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

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

[Bug 1768786] Re: Desktop is displayed when resuming from suspend

2018-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/348099

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

Title:
  Desktop is displayed when resuming from suspend

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

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

[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt (if starting with Shift key). Usually works on the second attempt

2018-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/348099

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt (if starting with Shift key). Usually works on the
  second attempt

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

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

[Bug 927544] Re: Log nautilus file operations with Zeitgeist

2018-06-15 Thread Bug Watch Updater
** Changed in: nautilus
   Status: New => Confirmed

** Changed in: nautilus
   Importance: Medium => Wishlist

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

Title:
  Log nautilus file operations with Zeitgeist

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

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

[Bug 1775145] Re: Please merge gnome-shell 3.28.2 from Debian

2018-06-15 Thread Treviño
** Changed in: gnome-shell (Ubuntu Cosmic)
 Assignee: Olivier Tilloy (osomon) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Please merge gnome-shell 3.28.2 from Debian

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

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

[Bug 1777147] Re: boot without a screen attached and I cannot remote in

2018-06-15 Thread Noel Grandin
In fact, even if I boot __with__ a screen, if I later unplug that
monitor, weird stuff starts happening to my  session (dragging windows
leave behinds "trails", clicking on menus and stuff stops responding,
etc)

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

Title:
  boot without a screen attached and I cannot remote in

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

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

[Bug 1777147] Re: boot without a screen attached and I cannot remote in

2018-06-15 Thread Noel Grandin
And by "my session" I mean my remotely logged in via screen sharing
session

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

Title:
  boot without a screen attached and I cannot remote in

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

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

[Bug 1777147] [NEW] boot without a screen attached and I cannot remote in

2018-06-15 Thread Noel Grandin
Public bug reported:

This is in Ubuntu 18 Desktop,

This used to work fine in Ubuntu16.

If I boot without a screen attached, I can attach via screen sharing, but the 
left hand bar is missing and nothing on the top menu bar is responsive.
Attaching a screen after that does not help, something is badly wedged, 
requires a reboot.

This is an Intel CPU with Intel graphics, nothing special, running a
freshly installed copy  of Ubuntu18.

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  boot without a screen attached and I cannot remote in

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

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

[Bug 1777138] [NEW] disabling ipv6 in network control panel does not disable ipv6

2018-06-15 Thread Noel Grandin
Public bug reported:

If I select "disable" on the IPV6, I can see that it is still acquiring
an IPV6 address, and that apt is still attempting to use IPV6, even
though I have disabled.

I had to edit sysctl.conf to turn it off

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  disabling ipv6 in network control panel does not disable ipv6

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

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

[Bug 1759699] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()

2018-06-15 Thread vasilisc
gnome-calendar:
  Installed: 3.28.2-1
  Candidate: 3.28.2-1
  Version table:
 *** 3.28.2-1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1759699/+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-15 Thread Stephen Allen
I can click, just no response to that action. I'll close this if you think
it's already represented.

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

> 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 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
> Status in mutter package in Ubuntu:
>   New
>
> 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.


** Changed in: mutter (Ubuntu)
   Status: New => Invalid

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

-- 
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/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 1777115] [NEW] gnome-shell crashed with stacktrace

2018-06-15 Thread Ernst Sjöstrand
Public bug reported:

Gnome-shell looked like it crashed, I got the traditional blinking of the 
window manager etc.
However I still have
 4580 ernsjo20   0 5822836 2,164g 109184 S   1,7  6,9 309:41.18 gnome-shell 


in top, so it looks like it didn't really crash (high memory usage and long 
running time).

gnome-shell 3.28.1-0ubuntu2

jun 15 11:15:00 edesk evolution-alarm[2240]: GtkDialog mapped without a 
transient parent. This is discouraged.
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: Object St.BoxLayout (0x560373857b10), 
has been already deallocated - impossible to access to it. This might be caused 
by the fact that the object has been destroye
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: == Stack trace for context 
0x5603268604b0 ==
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #0 0x560326d19e48 i   
resource:///org/gnome/shell/ui/popupMenu.js:717 (0x7fed9ae262b8 @ 22)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #1 0x7ffef656d740 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #2 0x7ffef656ded0 b   
resource:///org/gnome/shell/ui/popupMenu.js:735 (0x7fed9ae26560 @ 23)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #3 0x7ffef656df30 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #4 0x560326d19dc0 i   
/home/ernsjo/.local/share/gnome-shell/extensions/sensory-percept...@harlemsquirrel.github.io/extension.js:100
 (0x7fed6a59f6f8 @ 4
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #5 0x7ffef656eb30 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #6 0x7ffef656f2d0 b   
self-hosted:915 (0x7fedc40f12b8 @ 367)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #7 0x7ffef656f3c0 b   
resource:///org/gnome/gjs/modules/signals.js:128 (0x7fedc40d3230 @ 386)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #8 0x560326d19d38 i   
resource:///org/gnome/shell/ui/panelMenu.js:194 (0x7fed9ae7a230 @ 94)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #9 0x7ffef6570030 I   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #10 0x560326d19cc0 i   
/home/ernsjo/.local/share/gnome-shell/extensions/sensory-percept...@harlemsquirrel.github.io/extension.js:276
 (0x7fed6a59fe68 @ 
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #11 0x560326d19c00 i   
resource:///org/gnome/shell/ui/extensionSystem.js:82 (0x7fed9ae5a120 @ 431)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #12 0x560326d19b78 i   
resource:///org/gnome/shell/ui/extensionSystem.js:184 (0x7fed9ae5a340 @ 18)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #13 0x560326d19ac0 i   
resource:///org/gnome/shell/ui/extensionSystem.js:199 (0x7fed9ae5a3c8 @ 81)
jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #14 0x560326d19a20 i   
resource:///org/gnome/shell/ui/extensionSystem.js:299 (0x7fed9ae5a808 @ 76)
jun 15 11:15:00 edesk gnome-software[5173]: State change on 
user/*/*/shell-extension/sensory-perception_HarlemSquirrel.github.io/* from 
installed to available is not OK
jun 15 11:15:00 edesk gnome-software[5173]: State change on 
user/*/*/shell-extension/sensory-perception_HarlemSquirrel.github.io/* from 
available to installed is not OK
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed
jun 15 11:15:00 edesk gnome-software[5173]: State change on 
user/*/*/shell-extension/mediaplayer_patapon.info/* from installed to available 
is not OK
jun 15 11:15:00 edesk gnome-software[5173]: State change on 
user/*/*/shell-extension/mediaplayer_patapon.info/* from available to installed 
is not OK
jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 
'handler_id > 0' failed

[Bug 1777099] [NEW] [backport] DRM devices opened by logind stay referenced indefinitely by PID 1

2018-06-15 Thread Alex Tu
Public bug reported:

refer to https://github.com/systemd/systemd/issues/6908

we need that solution to make NVIDIA dGPU switching works.

impacted issue:
https://bugs.launchpad.net/somerville/+bug/1774326

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: ihv-nvidia

** Bug watch added: github.com/systemd/systemd/issues #6908
   https://github.com/systemd/systemd/issues/6908

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/6908
   Importance: Unknown
   Status: Unknown

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: ihv-nvidia

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

Title:
  [backport] DRM devices opened by logind stay referenced indefinitely
  by PID 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1777099/+subscriptions

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

[Bug 525119]

2018-06-15 Thread qweqwe
http://interest.kawata.me

John

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/525119

Title:
  folders in evolution dont appear , it seams i can subscribe to folders
  so i can't see any email

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

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

[Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

2018-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1754949 ***
https://bugs.launchpad.net/bugs/1754949

Thanks.

Your new crash report is a known issue (bug 1754949):
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665

So this is now a duplicate of bug 1754949.

** This bug has been marked a duplicate of bug 1754949
   gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from 
meta_renderer_native_finish_frame()

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

Title:
  Segfault in libmutter-2.so after suspend/resume using wayland. Core
  files are always truncated and invalid while the default shell is zsh.

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

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

[Bug 1772638] Re: Segfault in libmutter-2.so after suspend/resume using wayland. Core files are always truncated and invalid while the default shell is zsh.

2018-06-15 Thread Thorsten
Hi, i reinstalled my system and tried to reproduced the bug and switch
from xorg to wayland session. I think that this time i was able to sent
a complete crash report:

https://errors.ubuntu.com/oops/415ba0dc-7077-11e8-997a-fa163e192766

I don't know whether the new system install or the updates to apport/gdm
or something else fixed the crash reporting or whether it was just luck.

But i hope this helps to identify the issue.

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

Title:
  Segfault in libmutter-2.so after suspend/resume using wayland. Core
  files are always truncated and invalid while the default shell is zsh.

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

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

[Bug 1749007] Re: Snap mounts should be hidden from System Monitor

2018-06-15 Thread Sebastien Bacher
** 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-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1749007

Title:
  Snap mounts should be hidden from System Monitor

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

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

[Bug 1773382] Re: /usr/bin/gnome-control-center:11:remove_all_custom_widgets:set_active_panel_from_id:launch_panel_activated:g_closure_invoke:signal_emit_unlocked_R

2018-06-15 Thread Sebastien Bacher
There are no report of the SRU version, assuming the fix is working

** 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-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1773382

Title:
  /usr/bin/gnome-control-
  
center:11:remove_all_custom_widgets:set_active_panel_from_id:launch_panel_activated:g_closure_invoke:signal_emit_unlocked_R

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

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