date:20190611

** Description changed:

- I believe this is a regression for  
- #1740869  is not responding window is constantly showing when 
debugging a program 
+ I believe this is a regression for bug 1740869:
+  is not responding window is constantly showing when debugging a 
program
  
  I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
  this window shows up and I can't get it to stop asking me to close the
  program.
  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 19.04
  Release:  19.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  gnome-shell:
-   Installed: 3.32.1-1ubuntu1~19.04.1
-   Candidate: 3.32.1-1ubuntu1~19.04.1
-   Version table:
-  *** 3.32.1-1ubuntu1~19.04.1 500
- 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  3.32.0+git20190410-1ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
+   Installed: 3.32.1-1ubuntu1~19.04.1
+   Candidate: 3.32.1-1ubuntu1~19.04.1
+   Version table:
+  *** 3.32.1-1ubuntu1~19.04.1 500
+ 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  3.32.0+git20190410-1ubuntu1 500
+ 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  
  3) What you expected to happen
  When I hit a breakpoint in gdb, the program should stop.
  
  4) What happened instead
  The program stops and ubuntu asks me if i want to kill the program.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
  Uname: Linux 5.0.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 11 22:03:44 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-08 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  "Program" is not responding when debugging in gdb

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

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

[Bug 1740869] Re: is not responding window is constantly showing when debugging a program

Now tracking in bug 1832426 :(

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

Title:
   is not responding window is constantly showing when
  debugging a program

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

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

[Bug 1832426] [NEW] "Program" is not responding when debugging in gdb

2019-06-11 Thread Eric Shaw

Public bug reported:

I believe this is a regression for    
#1740869  is not responding window is constantly showing when 
debugging a program 

I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
this window shows up and I can't get it to stop asking me to close the
program.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
Description:Ubuntu 19.04
Release:19.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
gnome-shell:
  Installed: 3.32.1-1ubuntu1~19.04.1
  Candidate: 3.32.1-1ubuntu1~19.04.1
  Version table:
 *** 3.32.1-1ubuntu1~19.04.1 500
500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 3.32.0+git20190410-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages

3) What you expected to happen
When I hit a breakpoint in gdb, the program should stop.

4) What happened instead
The program stops and ubuntu asks me if i want to kill the program.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 11 22:03:44 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-06-08 (4 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

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

Title:
  "Program" is not responding when debugging in gdb

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

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

David, see bug 1832138.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Also affects: mutter (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gdm3 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: mutter (Ubuntu Eoan)
   Importance: Undecided
 Assignee: Daniel van Vugt (vanvugt)
   Status: Confirmed

** Also affects: gdm3 (Ubuntu Eoan)
   Importance: Undecided
   Status: Confirmed

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

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

** No longer affects: gdm3 (Ubuntu)

** No longer affects: gdm3 (Ubuntu Bionic)

** No longer affects: gdm3 (Ubuntu Eoan)

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

** Changed in: mutter (Ubuntu Bionic)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

** Changed in: mutter (Ubuntu Eoan)
 Assignee: Daniel van Vugt (vanvugt) => (unassigned)

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

Thanks. I see now that you filed this bug from a Unity session, and I
can reproduce the problem on Unity. The problem is that AFAIK gnome-
control-center is not designed to work with Unity; unity-control-center
is there for reasons.

Why are you using gnome-control-center on Unity?

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

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

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

[Bug 1831356] Re: Settings crashes when I click "Devices"(Enheter in norwegian) tap

2019-06-11 Thread Lars Bahner

bahner@venus:~$ gnome-control-center

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunset data, using 16,00

(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunrise data, using 8,00

(gnome-control-center:14031): GLib-GObject-CRITICAL **: 00:05:00.230: 
g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Minnesegmentsfeil (kjerne lagret i fil)
bahner@venus:~$ 

That's a segfault. This happens, when I click Devices, and everytime I
start gnome-control-center after that (without getting the time to do
anything).

Cheers.

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

Title:
  Settings crashes when I click "Devices"(Enheter in norwegian) tap

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

** Description changed:

+ [Impact]
+
+ If you
+
+ * start your computer with a bootable USB stick or DVD with the
+ 18.04.2 desktop ISO
+
+ * wait until Ubiquity's welcome screen shows up (only possible on
+ systems with legacy BIOS; bug #1766047)
+
+ * select a language which requires an input method for typing
+
+ * click the "Try Ubuntu" button
+
+ no IBus method is made easily available via the input source indicator
+ in the session you enter. If you for instance select zh_CN as language
+ and "Try Ubuntu", you would expect to enter a session with the
+ "Intelligent Pinyin" method included among the available input sources.
+
+ The proposed fix should ensure that an IBus method is always available
+ in "live sessions" in languages which are prepared for it.
+
+ [Test Case]
+
+ 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is
+not included among your available input sources.
+
+ 2. Generate the Chinese locale:
+
+sudo locale-gen zh_CN.UTF-8
+
+ 3. Add to ~/.profile this line:
+
+export LC_CTYPE=zh_CN.UTF-8
+
+ 4. Remove the gnome-settings-daemon stamp file:
+
+rm ~/.local/share/gnome-settings-daemon/input-sources-converted
+
+ 5. Log out and log in again.
+
+ => Find that the "Intelligent Pinyin" method was not added (since the
+ sources already in the list prevented it from being added).
+
+ 6. Install gnome-settings-daemon from bionic-proposed.
+
+ 7. Repeat step 4 and 5.
+
+ => Find that the "Intelligent Pinyin" method was added.
+
+ [Regression Potential]
+
+ The proposed upload includes a small change which specifically addresses
+ the issue as described above. I find that the risk for adverse side
+ effects is low.
+
+ [Original description]
+
Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't
input Chinese character. From Settings -> Regions and Languages, selected
Intelligent Pinyin, also could not input Chinese.

---

18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择
智能拼音，也无法输入中文。

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

Title:
Default IBus input method ignored in live session

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

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

[Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

** Changed in: evolution-data-server (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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

[Bug 1832374] Re: Media keys stop working due to missing service file

Thank you for your bug report, could you also send it upstream on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues ?

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Media keys stop working due to missing service file

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal unlinked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657

** Merge proposal unlinked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368409

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

Title:
  Default IBus input method ignored in live session

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368678

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

Title:
  Default IBus input method ignored in live session

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

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

[Bug 1778361] Re: The Processes tab only displays the current user's processes

2019-06-11 Thread Ken VanDine

This was definitely fixed in revision 70.  The specific fix was actually
building it based on core18/bionic with a newer version of GTK.  This is
a new bug that I'll look into.

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

Title:
  The Processes tab only displays the current user's processes

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-11 Thread Bill Coleman

CONFIRMED: Same situation running 18.04.2 on VMWare 12.5.9. After
uncommenting the WaylandEnable=false line and rebooting, then I see the
login prompt as expected and I can then log in and use the system
normally again.

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832374] [NEW] Media keys stop working due to missing service file

2019-06-11 Thread Bruce Pieterse

Public bug reported:

Over the last two releases I've noticed that if you have an audio player
such as Clementine running, pause the audio playback and watch a video
via VLC or SMPlayer and then close the video player and try to use the
media keys again, the following is logged to journald:

gsd-media-keys[2607]: Error calling method
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.mpris.MediaPlayer2.smplayer was not provided by any .service files.

>From what I can see is that a service file is created for the media keys
for SMPlayer, when SMPlayer is closed that service file is removed and
then media keys are still bound to that service.

I get the above output for previous track, stop, play, pause and next
track media keys.

I do get the following output if neither is SMPlayer or Clementine is
running or if Clementine is running and playing audio and SMPlayer is
open, but no video is loaded:

org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym ffb5 with keysym ffb5 (keycode 54).
org.gnome.Shell.desktop[2480]: Window manager warning: Overwriting existing 
binding of keysym 31 with keysym 31 (keycode a-e,12,f,10,11) <-- I collapsed 
the range into a comma separated list

If you re-open SMPlayer and load a video, the media keys work and the
GDBus error doesn't occur but the above "Overwriting ..." messages still
get logged. Closing SMPlayer again does not restore media keys so that
Clementine can handle them. I had SMPlayer running ~17 hours ago.

Doing a shell reload doesn't seem to fix this either.

I can't really tell if this is an SMPlay/VLC/Video Player issue or
actually an issue in GSD, so filing here until someone can reassign to
the relevant project.

I hit this a while ago, while trying to get some debugging information
for a Clementine bug: https://github.com/clementine-
player/Clementine/issues/6320

If you need any other information let me know.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jun 11 17:36:07 2019
InstallationDate: Installed on 2019-02-01 (129 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181202)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to disco on 2019-04-09 (63 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  Media keys stop working due to missing service file

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

Ok, noted Sebastien. I do plan to SRU it myself, so I re-added a bionic
task and assigned it to me.

** Also affects: gnome-settings-daemon (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: gnome-settings-daemon (Ubuntu Bionic)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  Default IBus input method ignored in live session

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

** Merge proposal linked:
   
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657

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

Title:
  Default IBus input method ignored in live session

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

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

2019-06-11 Thread David Wolff

I posted too soon.  It turns out that in my case the error was a red-herring.  
I loaded a backed up VM without the latest Ubuntu updates and I am able to log 
in fine even though the syslog still contains the error:
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: 
GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process 
org.gnome.ScreenSaver exited with status 1

This clearly isn't the root cause of my missing login screen.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

@Gunnar, we discussed it in the meeting and decided it was not important
to rls track, that doesn't mean it can't be fixed/SRUed though (also in
the futur, please don't do direct nomination without assignement, either
you plan to fix it yourself and then you can assign the bug to you or
use rls-nn-incoming tagging)

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

Title:
  Default IBus input method ignored in live session

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

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

[Bug 1786344] Re: Default IBus input method ignored in live session

** No longer affects: gnome-settings-daemon (Ubuntu Bionic)

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

Title:
  Default IBus input method ignored in live session

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

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

Re: [Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."

2019-06-11 Thread Brian Murray

On Tue, Jun 11, 2019 at 02:07:14AM -, Daniel van Vugt wrote:
> What model machine are you seeing this bug on?

A Lenovo T450s, while it has a fingerprint reader I've no interest in
using it.

--
Brian Murray

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

Title:
  Unlocking the screen takes a long time after "Starting Fingerprint
  Authentication Daemon..."

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

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

[Bug 1828124] Re: org.gnome.evolution.dataserver.Source completely unveils account credentials in plain text while using dbus-monitor

2019-06-11 Thread Bug Watch Updater

** Changed in: evolution-data-server
   Status: New => Fix Released

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

Title:
  org.gnome.evolution.dataserver.Source completely unveils account
  credentials in plain text while using dbus-monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1828124/+subscriptions

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

[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr

2019-06-11 Thread David Wolff

Same issue after an update this morning on Ubuntu 18.04.  Running Ubuntu
in a VMWare Workstation.  My login screen never appears after startup.

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

Title:
  CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
  calling StartServiceByName for org.gnome.ScreenSaver:
  GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process
  org.gnome.ScreenSaver exited with status 1

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

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

[Bug 1832038] Re: nautilus do not anymore start

Thank you for your bug report report. Could you add your "journalctl -b
0 "log to the bug after getting the issue?

** Changed in: nautilus (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  nautilus do not anymore start

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

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

Re: [Bug 1832317] Re: A quick type in the Gnome 3 search sticks

2019-06-11 Thread Artyom Pozharov

Anyone doesn't notice this bug, that I had opened. Please check it. It's
critical error: https://bugs.launchpad.net/bugs/1831374

вт, 11 июн. 2019 г., 13:10 Bug Watch Updater
<1832...@bugs.launchpad.net>:

> ** Changed in: gnome-shell
>Status: Unknown => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832317
>
> Title:
>   A quick type in the Gnome 3 search sticks
>
> Status in GNOME Shell:
>   New
> Status in gnome-shell package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
>   ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
>   Uname: Linux 5.0.0-16-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jun 11 11:10:33 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.shell' b'command-history' redacted by apport
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2019-06-06 (4 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1832317/+subscriptions
>

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

Title:
  A quick type in the Gnome 3 search sticks

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

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

[Bug 1832330] Re: gnome archive manager: "show the files" -> "Close and show the files"

Thank you for your bug report, that has been reported upstream before
but they didn't comment on it

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  gnome archive manager: "show the files" -> "Close and show the files"

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

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

[Bug 1814125] Re: [nvidia] gnome-shell eats 100% cpu when seconds display is on and screen is locked

** Tags added: fixed-in-3.33.3 fixed-upstream

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

Title:
  [nvidia] gnome-shell eats 100% cpu when seconds display is on and
  screen is locked

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

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

[Bug 1797734] Re: slow calculator startup

2019-06-11 Thread Valentin Crone

Hello,
Try to remove the snap package:

snap remove gnome-calculator

And install the deb package:

apt-get install gnome-calculator


I have experimented this on Ubuntu 18.04 and 19.04 and it seem to be really 
faster.
I have experienced many speed problems with snap apps. And some was really 
laggy.

For example, with discord on snap, on one of my laptop: crashes, and mic 
problems.
For the other laptop: Really laggy, 5 to 10s between the time I type something, 
and the time it appear on the screen, on a laptop with 2 SSD.
I have the time to start firefox 3 times on the same period, and discord in 
firefox doesn't present any of theses problems.

After this, I remove the snap version, and install the official deb
version (from the discord website), and no problems. Fluid and not full
of bugs.

Same problem for Atom (atom.io), buggy and laggy with snap.
I don't understand why snap is slow like this for certain apps, and I don't 
understand exactly how snap works, but I suspect him to be the cause of many 
slow apps on recent versions of Ubuntu.

On my laptop, for gnome-calculator, the time to open:
- Snap: 2 to 10s
- Deb: 0.1 to 1s

I can't say it's definitely snap, but I suppose you can look at this.

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

Title:
  slow calculator startup

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

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

[Bug 1832330] [NEW] gnome archive manager: "show the files" -> "Close and show the files"

2019-06-11 Thread simon

Public bug reported:

this is about the application Archive manager (I do not like generic
names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04

If I open an archive and extract the contents, I get a window with two
options: close and show the files. I always want to press both buttons
at the same time as I am finished with the archive and want to continue
with the extracted files. there is no need to keep the archive manager
window open.

Hence my request for a change of the button "show the files" to a "close
and show the files"

uname -a: Linux compaq 4.15.0-51-generic #55-Ubuntu SMP Wed May 15
14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

ubuntu 18.04.2 LTS, Gnome 3.28.2

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  gnome archive manager: "show the files" -> "Close and show the files"

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

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

[Bug 1832317] Re: A quick type in the Gnome 3 search sticks

2019-06-11 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => 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/1832317

Title:
  A quick type in the Gnome 3 search sticks

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

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

[Bug 1615389] Re: Searching for files and folders in AO takes much longer than previously

This bug is nearly 3 years old. Can you say if you think GNOME 3.32 in
Ubuntu 19.04 performs adequately now?

** Changed in: ubuntu-gnome
   Status: New => Incomplete

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

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

** Tags added: performance

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

Title:
  Searching for files and folders in AO takes much longer than
  previously

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

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

[Bug 1832317] Re: A quick type in the Gnome 3 search sticks

Yes, it is a bug. Thanks for reporting it.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1246
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1246

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1246
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

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

Title:
  A quick type in the Gnome 3 search sticks

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

If I had to guess then I would guess the most likely cause is the
changes I made in the latest update:

https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.1

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Seems like a bionic updates regression. Duplicate bug 1832320 confirms
the same date.

** Tags added: regression-update

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

Re: [Bug 1832317] Re: A quick type in the Gnome 3 search sticks

2019-06-11 Thread Artyom Pozharov

I don't understand you in "and unsurprising if it's during an operation
that requires
gnome-shell to perform disk IO like searching". What does it mean? Do such
freezes look like norm? I believe it's a problem and we should solve it. I
want to add, that I will not see such problems if I print a random text in
the search line. Problem will appear only if I enter a part of name of
Ubuntu package, file or folder.

вт, 11 июн. 2019 г. в 12:00, Daniel van Vugt :

> In your video it looks like you are typing "ubuntu" and gnome-shell is
> too slow to display much of the typing. So this is a performance
> problem, and unsurprising if it's during an operation that requires
> gnome-shell to perform disk IO like searching.
>
>
> ** Tags added: performance
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832317
>
> Title:
>   A quick type in the Gnome 3 search sticks
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
>   ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
>   Uname: Linux 5.0.0-16-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jun 11 11:10:33 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.shell' b'command-history' redacted by apport
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2019-06-06 (4 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832317/+subscriptions
>

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

Title:
  A quick type in the Gnome 3 search sticks

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832317] Re: A quick type in the Gnome 3 search sticks