[Bug 1580605] Re: gnome-shell crashes often

[Oyedotun Sodiq]

REINSTALL GNOME SHELL

sudo apt install gnome-session

THE RESULT OF ABOVE WILL INSTALL LATEST GNOME ON UR DESKTOP

UPDATE AND UPGRADE

sudo apt-get update

sudo apt-get upgrade

CHECK GNOME VERSION

gnome-shell --version

RESULT SHOULD BE GNOME Shell 3.26.2

RESTART UR SYSTEM

FURTHER OPTION, NOT NECCESSARY THO, U CUD INTEGRATE UR FAVORITE BROWSER
WTH GNOME TO WORK BETTER,FASTER AND EFFICIENTLY: SEE HELP LINK BELOW

https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation

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

Title:
  gnome-shell crashes often

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

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

[Bug 1771739] [NEW] Dell Latitude E6400 - Hotkeys for Volume Up, Down, Mute does nothing

[Oa Hyltén-Cavallius]

Public bug reported:

The hotkeys for Volume Up, Volume Down and Mute does not work on my Dell
Latitude E6400 running Ubuntu Budgie 18.04 LTS (Gnome version 3.28.1).
They worked fine in Ubuntu 17.10 that I was running before, but haven't
worked since I installed Budgie.

If I go into keyboard settings and configure keyboard shortcuts they are
detected when pressed, and register as "Audio raise volume", "Audio
lower volume" and "Audio mute", but even though correctly configured as
keyboard shortcuts they don't seem to work when pressed.

I have updated both the OS and all of the applications to the newest
available versions, but the problem persists.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Thu May 17 07:19:56 2018
InstallationDate: Installed on 2018-05-13 (3 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-settings-daemon (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 gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1771739

Title:
  Dell Latitude E6400 - Hotkeys for Volume Up, Down, Mute does nothing

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

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

[Bug 1771734] [NEW] gedit abnormally use high CPU

[Chia-Hao Hsu]

Public bug reported:

Gedit trigger an ubuntu high cpu consumption when the mouse is not in
the windows of gedit.

 gnome-shell ate up 50 % of cpu, while Xorg consumed 20 % of cpu, gedit
consumed 30 % of cpu. CPU is not able to cool down, when gedit is opened
and the location of mouse is in other applications instead of gedit. If
the situation goes on, system will hang.

  When Gedit is turned off in time, everything goes back to normal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu May 17 12:58:37 2018
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2018-04-29 (17 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  gedit abnormally use high CPU

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

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

[Bug 1771661] Re: [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[Daniel van Vugt]

Thanks. It looks like you have a hybrid system with both Nvidia/Intel
GPUs.

In case the freezes are caused by something crashing, please also:

1. Look in /var/crash for crash files and if found run:
   ubuntu-bug /var/crash/YOURFILE.crash
and tell us the ID of any new bug created.

2. Check for older crashes send from your system by looking at
https://errors.ubuntu.com/user/ID where ID is the contents of
/var/lib/whoopsie/whoopsie-id. If you find any links to crashes that you
think are relevant then please share them here.

3. Attach output from 'journalctl -b' from right after a failure has
occurred.

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

Re: [Bug 1771661] Re: After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[jim ruxton]

Thanks ,

See below for requested info.

Results of "apport-collect 1771661" was sent via launchpad

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f76e7b72-a204-4096-ac1d-8857a3afacb0 ro quiet splash vt.handoff=1

Result of  "lspci -k"
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers (rev 05)
     Subsystem: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
     Kernel driver in use: pcieport
     Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
     Subsystem: Lenovo Device 38e1
     Kernel driver in use: i915
     Kernel modules: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI 
Controller (rev 31)
     Subsystem: Lenovo Sunrise Point-H USB 3.0 xHCI Controller
     Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H 
Thermal subsystem (rev 31)
     Subsystem: Lenovo Sunrise Point-H Thermal subsystem
     Kernel driver in use: intel_pch_thermal
     Kernel modules: intel_pch_thermal
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-H 
Serial IO I2C Controller #0 (rev 31)
     Subsystem: Lenovo Sunrise Point-H Serial IO I2C Controller
     Kernel driver in use: intel-lpss
     Kernel modules: intel_lpss_pci
00:15.2 Signal processing controller: Intel Corporation Device a162 (rev 31)
     Subsystem: Lenovo Device 381e
     Kernel driver in use: intel-lpss
     Kernel modules: intel_lpss_pci
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME 
HECI #1 (rev 31)
     Subsystem: Lenovo Sunrise Point-H CSME HECI
     Kernel driver in use: mei_me
     Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA 
Controller [AHCI mode] (rev 31)
     Kernel driver in use: ahci
     Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root 
Port #3 (rev f1)
     Kernel driver in use: pcieport
     Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root 
Port #4 (rev f1)
     Kernel driver in use: pcieport
     Kernel modules: shpchp
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root 
Port #5 (rev f1)
     Kernel driver in use: pcieport
     Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root 
Port #9 (rev f1)
     Kernel driver in use: pcieport
     Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller 
(rev 31)
     Subsystem: Lenovo Sunrise Point-H LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
     Subsystem: Lenovo Sunrise Point-H PMC
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
     Subsystem: Lenovo CM238 HD Audio Controller
     Kernel driver in use: snd_hda_intel
     Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
     Subsystem: Lenovo Sunrise Point-H SMBus
     Kernel modules: i2c_i801
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce 
GTX 1060 Mobile] (rev a1)
     Subsystem: Lenovo GP106M [GeForce GTX 1060 Mobile]
     Kernel driver in use: nvidia
     Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
     Subsystem: Lenovo QCA6174 802.11ac Wireless Network Adapter
     Kernel driver in use: ath10k_pci
     Kernel modules: ath10k_pci
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
     Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
     Kernel driver in use: r8169
     Kernel modules: r8169
3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe 
SSD Controller SM961/PM961
     Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
     Kernel driver in use: nvme
     Kernel modules: nvme



On 2018-05-16 10:15 PM, Daniel van Vugt wrote:
> It sounds like you might have two different bugs, if the purple screen
> is bug 1766137.
>
> Please:
>
> 1. Run this command to attach more information: apport-collect 1771661
>
> 2. Run 'lspci -k' and attach its output here.
>
> 3. Copy /proc/cmdline and attach it here.
>
>
> ** Tags added: bionic nvidia
>
> ** Changed in: gdm3 (Ubuntu)
> Status: New => Incomplete
>
> ** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
> Status: New => Incomplete
>
> ** Summary changed:
>
> -  After updating to 18.04 only Wayland works. Cannot get Xorg to work on 
> Gnome
> + [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to 
> 

[Bug 1771661] ProcEnviron.txt

[jim ruxton]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1771661/+attachment/5140602/+files/ProcEnviron.txt

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

[Bug 1771661] Re: [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[jim ruxton]

apport information

** Tags added: apport-collected wayland-session

** Description changed:

- I recently updated to Ubuntu 18.04. After updating I can only log into
- Gnome if I select Gnome or Ubuntu with Wayland at my login screen.
- Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg and
- reinstalling my video driver (nvidia-390) . If I select Ubuntu with Xorg
- at login I get a purple screen and frozen mouse. If I set etting
- |WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to the
- login screen. The system freezes.
+ I recently updated to Ubuntu 18.04. After updating I can only log into Gnome 
if I select Gnome or Ubuntu with Wayland at my login screen. Nothing I can do 
will allow me tuse Xorg. I tried reinstalling Xorg and reinstalling my video 
driver (nvidia-390) . If I select Ubuntu with Xorg at login I get a purple 
screen and frozen mouse. If I set etting |WaylandEnable=false| in 
|/etc/gdm/custom.conf| I cannot get to the login screen. The system freezes.
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2017-09-16 (242 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: nvidia-graphics-drivers-390
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
+ Tags:  bionic wayland-session
+ Uname: Linux 4.15.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo video
+ _MarkForUpload: True
+ mtime.conffile..etc.gdm3.custom.conf: 2018-05-13T00:31:45.698321

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1771661/+attachment/5140600/+files/Dependencies.txt

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

[Bug 1771661] modified.conffile..etc.gdm3.custom.conf.txt

[jim ruxton]

apport information

** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
   
https://bugs.launchpad.net/bugs/1771661/+attachment/5140603/+files/modified.conffile..etc.gdm3.custom.conf.txt

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

[Bug 1771661] ProcCpuinfoMinimal.txt

[jim ruxton]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1771661/+attachment/5140601/+files/ProcCpuinfoMinimal.txt

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

[Bug 1771661] Re: After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[Daniel van Vugt]

It sounds like you might have two different bugs, if the purple screen
is bug 1766137.

Please:

1. Run this command to attach more information: apport-collect 1771661

2. Run 'lspci -k' and attach its output here.

3. Copy /proc/cmdline and attach it here.


** Tags added: bionic nvidia

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

** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Incomplete

** Summary changed:

-  After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome
+ [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg to work 
on Gnome

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

Title:
  [nvidia] After updating to 18.04 only Wayland works. Cannot get Xorg
  to work on Gnome

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

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

[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

[Daniel van Vugt]

If you are using Wayland then ignore step 3 :)

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

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

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

[Bug 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state

[Daniel van Vugt]

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/282
+ 
+ ---
+ 
  Toggling Super+D hides or un-hides all windows so you can access icons
  on the desktop.
  
  But this breaks if a new window appears while the windows are hidden:
  They become PERMANENTLY hidden, i.e. Super+D does not restore them.
  They seem to be "minimized" -- you have to individually un-minimize each
  window to get your session back.
  
  This is very annoying, and is common: The only reason for using Super+D
  is to see something on the desktop; probably you then need to do
  something with it, i.e. click it.  If that action opens a new window,
  which is almost certain, you're hosed.
  
  STEPS TO REPRODUCE:
  
  1. Open a bunch of windows and artfully arrange them.
  2. Type Super+D (they all become hidden)
  3. Double-click the "Trash" desktop icon and wait for a file browser to open.
  
  RESULTS: Once the file-viewer opens, Super+D will not restore the
  previously-hidden windows.  Instead, it seems to forget about them and
  instead hide the new window (and un-hide it if pressed a second time
  --before yet another window is opened, of course).
  
- EXPECTED RESULTS: 
-The state should be well-defined: Either normal or windows-hidden.  
-Once in the windows-hidden state, Super-D should un-hide the hidden 
windows e
-ven if new windows have been created in the interim.
+ EXPECTED RESULTS:
+    The state should be well-defined: Either normal or windows-hidden.
+    Once in the windows-hidden state, Super-D should un-hide the hidden 
windows e
+    ven if new windows have been created in the interim.
  
  SUGGESTED FIX:
  1. (preferred): On the first Super+D, hide all windows and remember their 
IDs.  On the next Super+D, un-hide just those windows, if they still exist, and 
do nothing at all with any other windows which might be present (i.e. new 
ones).   Then return to the initial state, where Super+D hides all visible 
windows.
  
  2. (if the above is too hard to implement): If a new window appears
  while in the "hiding" state, make the new window immediately become
  hidden also; only on the second Super+D would the new window become
  visible along with the old ones.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 16:40:22 2018
  DisplayManager: gdm3
  GsettingsChanges:
-  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 
'rece...@leonardo.bartoli.gmail.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'workspaces-to-d...@passingthru67.gmail.com']"
-  b'org.gnome.shell' b'favorite-apps' redacted by apport
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 
'rece...@leonardo.bartoli.gmail.com', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 
'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 
'systemmoni...@gnome-shell-extensions.gcampax.github.com', 
'workspaces-to-d...@passingthru67.gmail.com']"
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-05 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1)
  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/1771466

Title:
  Super+D wrongly  leaves windows minimized if a new window appears
  while in "hiding" state

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

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

[Bug 1771308] Re: Adding the user to a new group doesn't take effect on logout and back in

[Daniel van Vugt]

By "running process" I mean any process.

But you're right; I misread "doesn't take effect on logout" as "doesn't
take effect until logout".

One should indeed reasonably expect group changes to apply after the
next login.

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

Title:
  Adding the user to a new group doesn't take effect on logout and back
  in

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

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

[Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

[Daniel van Vugt]

*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

Thanks for pointing that out. The error you mention is actually right
before bug 1543192 happens to you:

May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) 
Screen(s) found, but none have a usable configuration.
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: Fatal server 
error:
May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE) no 
screens found(EE)

So still bug 1543192. Maybe worth commenting on that one about the
above.

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

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

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

Re: [Bug 1771394] Re: gvfsd-mtp hoovers up all memory

[Bill Miller]

Thanks, I'll give it a try, although I use adb on the host, maybe I can 
disable it, if that's what's causing the issue.

On 05/16/2018 07:57 PM, Steve Childs wrote:
> I just experienced this too. If you don't need them, remove the adb
> files from ubuntu, if you're passing the USB device onto the guest OS,
> you don't need them anyway.
>
> FYI, I followed an install guide online, so just reversed the install
> line, e.g.
>
> sudo apt-get remove android-tools-adb android-tools-fastboot
>
> Sorry if its teaching you to suck eggs, I've just included it for others
> if they stumble over the same issue.
>

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

Title:
  gvfsd-mtp hoovers up all memory

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

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

[Bug 1771394] Re: gvfsd-mtp hoovers up all memory

[Steve Childs]

I just experienced this too. If you don't need them, remove the adb
files from ubuntu, if you're passing the USB device onto the guest OS,
you don't need them anyway.

FYI, I followed an install guide online, so just reversed the install
line, e.g.

sudo apt-get remove android-tools-adb android-tools-fastboot

Sorry if its teaching you to suck eggs, I've just included it for others
if they stumble over the same issue.

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

Title:
  gvfsd-mtp hoovers up all memory

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[Bug Watch Updater]

** Changed in: gdm
   Status: In Progress => Fix Released

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1768541] Update Released

[Brian Murray]

The verification of the Stable Release Update for gnome-keyring 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 gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[aeronutt]

FYI, I (temporarily?) switched to SDDM, so far so good (although a bit
cumbersome as delivered). It also allows Wayland sessions.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1768541] Re: package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-keyring -
3.28.0.2-1ubuntu1.18.04.1

---
gnome-keyring (3.28.0.2-1ubuntu1.18.04.1) bionic; urgency=medium

  * debian/control{,.in}: Make the transitional packages be Arch any and MA
same, so upgrades work properly. (LP: #1768541)
  * Update Vcs-* for bionic.

 -- Iain Lane   Wed, 09 May 2018 20:19:29 +0100

** Changed in: gnome-keyring (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 gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1768541

Title:
  package libp11-kit-gnome-keyring 3.20.1-1ubuntu1 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

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

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

[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:17.10.14

---
update-manager (1:17.10.14) artful; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 19:57:57 +0100

** Changed in: update-manager (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

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

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

[Bug 1624644] Update Released

[Brian Murray]

The verification of the Stable Release Update for update-manager 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 gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

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

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

[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Launchpad Bug Tracker]

This bug was fixed in the package update-manager - 1:16.04.13

---
update-manager (1:16.04.13) xenial; urgency=medium

  * Offer removal of unused autoremovable kernel packages
(LP: #1624644, #1675079)
  * Support package removals in install backends and really remove packages
(LP: #1624644, #1675079)
  * Keep PEP 8 checks happy
  * Place .keep files in empty directories to keep them when converting the
repo to git (LP: #1758963)

 -- Balint Reczey   Sun, 25 Mar 2018 20:10:49 +0100

** Changed in: update-manager (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 gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1624644

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

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

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

[Bug 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Brian Murray]

Verified update-manager for artful.

** Attachment added: "bug-1624644-verification.png"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+attachment/5140527/+files/bug-1624644-verification.png

** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

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

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

[Bug 1740804] Re: Remove old vte package from Ubuntu

[Jeremy Bicha]

** No longer affects: genius (Ubuntu)

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

Title:
  Remove old vte package from Ubuntu

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

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

[Bug 1771682] Re: No way to logout from Snap Store.

[Andrea Azzarone]

MP here: https://gitlab.gnome.org/GNOME/gnome-software/merge_requests/46

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

Title:
  No way to logout from Snap Store.

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

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

[Bug 1771685] [NEW] Show Desktop and trashbin icon on the Dock

[HouseSessions]

Public bug reported:

Hi,

Would it be possible to add check boxes (on the "Dock" settings screen?)
to show the icons for "Show Desktop" and "Trash Bin" on the Dock?

These options were present in Unity were as really useful (helped in
productivity).

Thanks,
br, Koen.

** Affects: adwaita-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Show Desktop and trashbin icon on the Dock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1771685/+subscriptions

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

[Bug 1771682] [NEW] No way to logout from Snap Store.

[Andrea Azzarone]

Public bug reported:

Gnome-software has not GUI way to logout from snap store. Implement the
proposed solution: https://github.com/CanonicalLtd/desktop-
design/issues/62#issuecomment-385643142

** Affects: gnome-software (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

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

** Changed in: gnome-software (Ubuntu)
   Status: New => In Progress

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Description changed:

- Gnome-software has not GUI way to logout from snap store.
+ Gnome-software has not GUI way to logout from snap store. Implement the
+ proposed solution: https://github.com/CanonicalLtd/desktop-
+ design/issues/62#issuecomment-385643142

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

Title:
  No way to logout from Snap Store.

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[HouseSessions]

Hi,

Being new around here, seen the high impact on a lot of users, is there
anyway or chance that Canonical can set prio with GNOME or deliver the
fix themselves to upstream?

thanks,
Koen.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1760708] Re: Download Adobe Flash Player (apt-url). gnome-software crashed with signal 5 in g_main_context_new()

[Marius Groenewald]

*** This bug is a duplicate of bug 1760795 ***
https://bugs.launchpad.net/bugs/1760795

I have downloaded the .tar.gz file from Adobe Flash Player website,
instead of using the APL option, which do not work. I extracted the file
and followed the instructions in the readme.txt file, and my Flash
Player is working!

Installation instructions
-

Installing using the plugin tar.gz:
o Download and Unpack the plugin tar.gz file. (I downloaded and extracted 
within my Downloads folder).  
o Open a terminal window and run: sudo nautilus.
o Copy the following file and folder under the extracted folder.
  + libflashplayer.so
  + /usr
o Paste the file and folder under the following location: 
/usr/lib/firefox/browser/plugins/
o Open Firefox and your Flash Player should work.

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

Title:
  Download Adobe Flash Player (apt-url). gnome-software crashed with
  signal 5 in g_main_context_new()

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

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

[Bug 1771661] [NEW] After updating to 18.04 only Wayland works. Cannot get Xorg to work on Gnome

[jim ruxton]

Public bug reported:

I recently updated to Ubuntu 18.04. After updating I can only log into
Gnome if I select Gnome or Ubuntu with Wayland at my login screen.
Nothing I can do will allow me tuse Xorg. I tried reinstalling Xorg and
reinstalling my video driver (nvidia-390) . If I select Ubuntu with Xorg
at login I get a purple screen and frozen mouse. If I set etting
|WaylandEnable=false| in |/etc/gdm/custom.conf| I cannot get to the
login screen. The system freezes.

** Affects: gdm3 (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/1771661

Title:
   After updating to 18.04 only Wayland works. Cannot get Xorg to work
  on Gnome

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

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

[Bug 1771650] [NEW] openvpn startup script isn't working in ubuntu 18.04

[Fanar Webb]

Public bug reported:

Its very simple.

1- Install ubuntu 18.04.
2- Install Openvpn using apt.
3- Put your configuration at path /etc/openvpn, for example : 
/etc/openvpn/myconfig.conf.
4- start openvpn service! It won't start automatically.

Note : my config have a security weakness, but it still valid and works
perfect if I start it manually. For example : openvpn
/etc/openvpn/myconfig.conf - it works !


Thank you

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  openvpn startup script isn't working in ubuntu 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1771650/+subscriptions

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

[Bug 1767264] Re: Window manager refresh rate is different from monitor refresh rate

[Rachel]

** This bug is no longer a duplicate of bug 1763892
   144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

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

Title:
  Window manager refresh rate is different from monitor refresh rate

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

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

[Bug 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state

[jimav]

Upstream bug is
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/282

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

Title:
  Super+D wrongly  leaves windows minimized if a new window appears
  while in "hiding" state

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

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

[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

[aeronutt]

Same problem here. I can no longer log into 18.04. First password entry
fails, then on second entry, I get purple screen with working mouse
pointer. But hangs there. This has been an intermittent problem for me
over the past few weeks, but today seems to be 100%.

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

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

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

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

[Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt

[fossfreedom]

** Changed in: gnome-menus (Ubuntu)
   Status: In Progress => New

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

Title:
  Applications menu does not get populated with recently installed apps
  using apt

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

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

[Bug 1771603] [NEW] Does not honour UID_MAX

[Marc Deslauriers]

Public bug reported:

accountsservice doesn't honour the UID_MAX settings in /etc/login.defs,
resulting in system users being displayed at the login screen and in the
users control panel.

See attached screenshot to see that the "libvirt-qemu" user is being
displayed when it shouldn't.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: accountsservice 0.6.45-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 16 11:03:09 2018
InstallationDate: Installed on 2017-12-12 (155 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: accountsservice
UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screenshot of issue"
   
https://bugs.launchpad.net/bugs/1771603/+attachment/5140372/+files/Screenshot%20from%202018-05-16%2011-05-30.png

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

Title:
  Does not honour UID_MAX

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

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

[Bug 1771308] Re: Adding the user to a new group doesn't take effect on logout and back in

[Sebastien Bacher]

Daniel, what do you mean by "running process"? The steps involve login
out and back in, so starting a new session, group changes should be
active on a new login no?

** Package changed: linux (Ubuntu) => gdm3 (Ubuntu)

** 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/1771308

Title:
  Adding the user to a new group doesn't take effect on logout and back
  in

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

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

[Bug 1771308] [NEW] Adding the user to a new group doesn't take effect on logout and back in

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps to reproduce:

Log in to a GNOME session
Use adduser to add yourself to an existing group
Log out and back in
Open a terminal, run "groups" and notice that your user isn't in the new group.
Reboot and log in, and you user is now in the group.

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

-- 
Adding the user to a new group doesn't take effect on logout and back in
https://bugs.launchpad.net/bugs/1771308
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gdm3 in Ubuntu.

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

[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

Some gdb debugging is

#1  0x7f3abc9a1bc8 in st_label_set_text (label=0x555b3f768d10, 
text=0x555b5369d360 "...")
at ../../gnome-shell/src/st/st-label.c:331
331   ctext = CLUTTER_TEXT (priv->label);
(gdb) list
326 
327   g_return_if_fail (ST_IS_LABEL (label));
328   g_return_if_fail (text != NULL);
329 
330   priv = label->priv;
331   ctext = CLUTTER_TEXT (priv->label);
332 
333   if (clutter_text_get_editable (ctext) ||
334   g_strcmp0 (clutter_text_get_text (ctext), text) != 0)
335 {
(gdb) print label
$1 = (StLabel *) 0x555b3f768d10
(gdb) print *label
$2 = {parent_instance = {parent_instance = {parent_instance = {g_type_instance 
= {g_class = 0x555b3e5ea510}, 
ref_count = 1, qdata = 0x555b3f759800}, flags = 0, private_flags = 0, 
priv = 0x555b3f7689f0}}, 
  priv = 0x555b3f7688b0}
(gdb) print *label->priv
$3 = {label = 0x555b3f712210, text_shadow_pipeline = 0x0, shadow_width = -1, 
shadow_height = -1}
(gdb) print *label->priv->labe
There is no member named labe.
(gdb) print *label->priv->label
$4 = {parent_instance = {g_type_instance = {g_class = 0x7f3abdf80be0
 }, ref_count = 
1102656128, qdata = 0x30}, flags = 113, 
  private_flags = 0, priv = 0x68733b6572616873}

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

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

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

[Bug 1759621] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

I got it finally with some proper JS stacktrace, in my case it was an
extension triggering it:

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.730: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:132
 (0x7f1e0fa86808 @ 342)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.730:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.730:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:157
 (0x7f1e0fa86808 @ 585)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.731:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.731:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Gjs-CRITICAL **: 12:22:44.731: Object St.BoxLayout 
(0x55950fcf1230), has been already deallocated - impossible to access to it. 
This might be caused by the fact that the object has been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs
== Stack trace for context 0x55950f5194c0 ==
#0 0x7fffe152eed0 I   resource:///org/gnome/shell/ui/environment.js:41 
(0x7f1e5c586d58 @ 20)
#1 0x7fffe152efc0 b   resource:///org/gnome/shell/ui/popupMenu.js:642 
(0x7f1e5c224de0 @ 61)
#2 0x7fffe152f060 I   resource:///org/gnome/gjs/modules/_legacy.js:82 
(0x7f1e5c5b5e68 @ 71)
#3 0x55950f8dd540 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/extension.js:171
 (0x7f1e0fa86808 @ 778)
#4 0x55950f8dd480 i   
/home/marco/.local/share/gnome-shell/extensions/clipboard-indica...@tudmotu.com/utils.js:121
 (0x7f1e0fab9340 @ 458)

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): Clutter-CRITICAL **: 12:22:44.732:
clutter_layout_manager_get_child_meta: assertion
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed

(gnome-shell:6754): GLib-GObject-CRITICAL **: 12:22:44.732:
g_object_set: assertion 'G_IS_OBJECT (object)' failed

(gnome-shell:6754): 

[Bug 1770238] Re: [nvidia] Logging in results in a black screen for many minutes after which the login screen reappears and I am able to login fine.

[Jonathan]

*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192

I cannot view my own error reports, it just tells me I don't have
permission and am not part of the correct group. I filled out the form
to request access so we shall see.

I'm not sure if my original error is a duplicate of bug #154192. There
doesn't appear to be a crash involved. gdm-x-session just seems to shut
itself down because it couldn't find monitors.  Even though it works
after a system reload.

 May 9 11:04:06 jcormier-MS-7A93 /usr/lib/gdm3/gdm-x-session[2581]: (EE)
Screen(s) found, but none have a usable configuration.

It definitely does seem I am being hit by a miriad of bugs.  Its getting
pretty frustrating to keep using it. And its also hard to tell the
difference between them.

Issues as far as I can tell:
* First login fails due to no usable monitors, if wayland is disabled. 
(Workaround, don't disable wayland)
* gnome-calculator and possibly other snap apps lock up the computer when 
opened if wayland is disabled. (Workaround, don't disable wayland)
* System locks up and reboots. (Unknown cause, no errors appear in logs as they 
don't get flushed to disk.)
* Gnome locks up and I am returned to login screen (Unknown cause but seems to 
generate a variety of different crash reports)

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

Title:
  [nvidia] Logging in results in a black screen for many minutes after
  which the login screen reappears and I am able to login fine.

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

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

[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

[Jeremy Bicha]

Just installing hexchat would mean adding a "transitional" package in
the hexchat source.

One way to have a suggestion about hexchat would be having command-not-
found handle it. To get an idea of how that works, if you uninstall
hexchat and run hexchat in a terminal, you'll get this output on Ubuntu
18.04 LTS:

$ hexchat

Command 'hexchat' not found, but can be installed with:

sudo snap install hexchat
sudo apt  install hexchat

See 'snap info hexchat' for additional versions.

===
So I suggest filing a separate bug against hexchat or command-not-found for 
your suggestion.

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

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

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

[Bug 1771278] Re: search in gnome is not working

[Jeremy Bicha]

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

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

Title:
  search in gnome is not working

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Ubuntu Foundations Team Bug Bot]

The attachment "AMD64 .deb included, with .patch file" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Penn Mackintosh]

I have a patch, taken from SO.

Patch is attached for package xorg-server.
After building with it, you need to install xserver-xorg-core-*.deb package 
generated.
I have attached the .deb too.

** Attachment added: "AMD64 .deb included"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1244090/+attachment/5140329/+files/patches.zip

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Penn Mackintosh]

I have confirmed that the above patch works by applying it and running
xev. I then pressed META+SPACE and the keyboard layout changed without
any output from xev.

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

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

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

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

[Bug 1713034] Re: gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]

[Bug Watch Updater]

** Changed in: glib
   Status: Confirmed => 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/1713034

Title:
  gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion
  failed: (wd >= 0)"]

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

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

[Bug 1768734] Re: Restoring edge tiled windows on Wayland shrinks them

[mtvoid]

I've found a recent bug report for this issue on the GitLab site for mutter:
https://gitlab.gnome.org/GNOME/mutter/issues/140

This also requires me to correct my initial bug report. The issue is
unrelated to client-side decorated windows, but affects all native
Wayland windows, while XWayland windows are unaffected.

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

Title:
  Restoring edge tiled windows on Wayland shrinks them

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

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

[Bug 1758163] Re: Please remove xchat-gnome from Ubuntu (again)

[Kieran Bingham]

I find my way here after losing xchat-gnome on the bionic upgrade:

Ok - so I just tried out hexchat - and that seems to be pretty good
alternative / update.

Is there a way to get apt to suggest / recommend hexchat instead of
failing to install xchat-gnome?

"""
# sudo apt-get install xchat-gnome
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package xchat-gnome is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'xchat-gnome' has no installation candidate
"""

It would be useful for that to print the alternatives - or just install
hexchat as a replacement :D

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

Title:
  Please remove xchat-gnome from Ubuntu (again)

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

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

[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)

[mtvoid]

** Project changed: gtk => mutter

** Summary changed:

- Restoring edge tiled windows with client-side decorations shrinks them 
(Wayland)
+ Restoring edge tiled windows on Wayland shrinks them

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

Title:
  Restoring edge tiled windows on Wayland shrinks them

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

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

[Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & gnome-shell fail to start?

[Jean-Baptiste Lallement]

I cannot reproduce this issue anymore with a fresh installation of
xenial upgraded to bionic. I'm wondering if the fontconfig fix that
delayed the boot was causing this issue (bug 1749546)

Setting to incomplete.

** 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/1765724

Title:
  Xenial -> Bionic - System fails to boot after upgrade - gnome-
  screensaver & gnome-shell fail to start?

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

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

[Bug 1771278] Re: search in gnome is not working

[Matej]

Thank you Daniel.

You are right the vscode extension was the problem. After removing it
everything is back to normal.

I don't even remember installing it?!


Thank you for you fast response.

The problem is resolved.

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

Title:
  search in gnome is not working

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

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

[Bug 1722353] Re: Screen blanking and/or screen lock crashes gnome-shell user session on wayland - Ubuntu 17.10 beta

[Penn Mackintosh]

*** This bug is a duplicate of bug 1717170 ***
https://bugs.launchpad.net/bugs/1717170

** Tags added: bionic

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

Title:
  Screen blanking and/or screen lock crashes gnome-shell user session on
  wayland - Ubuntu 17.10 beta

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

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

[Bug 484521] Re: Nautilus causes memory leak in Xorg?

[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 a bug assignee.
https://bugs.launchpad.net/bugs/484521

Title:
  Nautilus causes memory leak in Xorg?

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

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

[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

[Zihang Ye]

Thank you for replying, Daniel. I'll try that out. However, since I
can't reproduce it, you might have to wait for a long time before my
next reply.

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

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

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

[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

[Zihang Ye]

Hi Daniel, after read through your suggestion, I found some problem. I'm 
actually using Wayland, so that shouldn't be a Xorg crash, right?
And in the /etc/gdm3/custom.conf, I saw this:
# Uncomment the line below to force the login screen to use Xorg
# WaylandEnabled=false
So does that mean during my usage of my system, I've never activated the Xorg 
server? I don't know much about how things work.

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

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

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

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

[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby

[Daniel van Vugt]

It gives you several steps that must be followed first to *fix* the
problem with not being able to upload it via ubuntu-bug. Please follow
all steps.

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

Title:
  Temporary screen freeze when coming back from screen standby

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

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

[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby

[Alberto Donato]

That link mentions how to create a crash file, but I do have one, I just
can't upload it via ubuntu-bug

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

Title:
  Temporary screen freeze when coming back from screen standby

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

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

[Bug 196785]

[TerryG]

http://bridge.aidrock.com
Terry Galati

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

Title:
  'sh' syntax highlighting actually for bash, and uses syntax invalid
  for Bourne shell

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

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Penn Mackintosh]

No, the problem is in the grabbing code:
https://github.com/GNOME/gnome-shell/blob/2997e4950ba31747b5e3260c306456b0de413421/js/misc/keyboardManager.js#L37
https://github.com/GNOME/mutter/blob/49f029571cc425a878e520310a8db616fa5c4b70/src/core/keybindings.c#L1803
This grabs the keyboard.
>From https://www.x.org/wiki/Development/Documentation/GrabProcessing :
'There can only be one grab on a device ...'
See the xev output below, of me pressing META+SPACE to change layout:

FocusOut event, serial 34, synthetic NO, window 0x321,
mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 34, synthetic NO, window 0x321,
mode NotifyUngrab, detail NotifyNonlinear

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys:  70  0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

FocusOut event, serial 34, synthetic NO, window 0x321,
mode NotifyGrab, detail NotifyNonlinear

FocusIn event, serial 34, synthetic NO, window 0x321,
mode NotifyUngrab, detail NotifyNonlinear

KeymapNotify event, serial 34, synthetic NO, window 0x0,
keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0

The issue is that it is losing grab, as the FocusOut event shows the
mode is notifyGrab. Or at least that is my interpretation. I don't know
why the grab and ungrab events are the wrong way round.

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Penn Mackintosh (penn-mackintosh)

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

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

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

[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled

[Daniel van Vugt]

Just to clarify, we aim to fix this bug with
https://gitlab.gnome.org/GNOME/mutter/merge_requests/52 or similar. So
please track that page.

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

Title:
  Top bar and shell dialogs are not displayed properly when zoom is
  enabled

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

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

[Bug 1763892] Re: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

[Daniel van Vugt]

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

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  144Hz/120Hz monitor but Wayland sessions seem to cap rendering at
  60FPS

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

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

[Bug 1767693] Re: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz

[Daniel van Vugt]

*** This bug is a duplicate of bug 1763892 ***
https://bugs.launchpad.net/bugs/1763892

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=781296
   Importance: Unknown
   Status: Unknown

** This bug has been marked a duplicate of bug 1763892
   144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

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

Title:
  18.04 GNOME displays at 60fps even if the monitor is set to 144hz

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

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

[Bug 1767264] Re: Window manager refresh rate is different from monitor refresh rate

[Daniel van Vugt]

*** This bug is a duplicate of bug 1763892 ***
https://bugs.launchpad.net/bugs/1763892

** This bug has been marked a duplicate of bug 1763892
   144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

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

Title:
  Window manager refresh rate is different from monitor refresh rate

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

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

[Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present

[Daniel van Vugt]

Please report the bug upstream: 
https://gitlab.gnome.org/GNOME/gnome-shell/issues
and let us know the URL of the new bug you create.

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

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

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

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

Title:
  Position of left-tiled windows not restored correctly when another
  left-tiled window present

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

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

[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)

[Daniel van Vugt]

... and tell us the URL of the new bug.

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

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

Title:
  Restoring edge tiled windows with client-side decorations shrinks them
  (Wayland)

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

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

[Bug 1768734] Re: Restoring edge tiled windows with client-side decorations shrinks them (Wayland)

[Daniel van Vugt]

Please report this bug the the mutter developers here:
https://gitlab.gnome.org/GNOME/mutter/issues

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

Title:
  Restoring edge tiled windows with client-side decorations shrinks them
  (Wayland)

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

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

[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby

[Daniel van Vugt]

In that case please follow the standard instructions :)

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Temporary screen freeze when coming back from screen standby

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

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

[Bug 1769981] Re: Temporary screen freeze when coming back from screen standby

[Alberto Donato]

Yes I have a Xwayland crash file in /var/crash with the same timestamp.

I tried running ubuntu-bug on it, but after I confirm the popup message,
it just exits without any error and it doesn't pop up a launchpad
window.

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

Title:
  Temporary screen freeze when coming back from screen standby

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

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

[Bug 1771273] Re: Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

[Daniel van Vugt]

** Tags added: 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/1771273

Title:
  Gnome-shell crashes when wake up after updated to 3.28.1-0ubuntu2

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

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

[Bug 1770875] Re: gnome-shell crashed with signal 5 in g_main_context_new()

[Daniel van Vugt]

It appears this crash stopped occurring after Ubuntu 17.10. See:

https://errors.ubuntu.com/problem/685b1f09a620aa3b892715d4eb6e43895ca64b76

** Description changed:

+ https://errors.ubuntu.com/problem/685b1f09a620aa3b892715d4eb6e43895ca64b76
+ 
  apt-cache policy gnome-shell
  gnome-shell:
-   Installed: 3.18.5-0ubuntu0.3
-   Candidate: 3.18.5-0ubuntu0.3
+   Installed: 3.18.5-0ubuntu0.3
+   Candidate: 3.18.5-0ubuntu0.3
  
  lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04
  
  Gnome Shell crashed this morning while I was un-installing Gnome-Shell
  extensions to try and figure out why I was seeing this in my syslog:
  
  May 12 10:47:58 localhost gnome-session[3343]: (gnome-shell:3393): 
Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 
'CLUTTER_IS_LAYOUT_MANAGER (manager)' failed
  May 12 10:47:58 localhost gnome-session[3343]: (gnome-shell:3393): 
GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed
  May 12 10:47:58 localhost gnome-session[3343]: (gnome-shell:3393): 
GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)'
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sat May 12 11:18:28 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (1296 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
-  PATH=(custom, user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
-  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
-  g_dbus_connection_send_message_with_reply_sync () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
-  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  g_dbus_connection_send_message_with_reply_sync () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
+  ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo

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

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

Title:
  gnome-shell crashed with signal 5 in g_main_context_new()

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

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

[Bug 1771512] [NEW] /usr/bin/gnome-shell:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_with_unix_fd_list_

[errors.ubuntu.com bug bridge]

*** This bug is a duplicate of bug 1770875 ***
https://bugs.launchpad.net/bugs/1770875

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.26.1-0ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/685b1f09a620aa3b892715d4eb6e43895ca64b76 
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: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful saucy trusty xenial yakkety zesty

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

Title:
  /usr/bin/gnome-
  
shell:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_with_unix_fd_list_sync

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

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

[Bug 1771278] Re: search in gnome is not working

[Daniel van Vugt]

It appears you are using an exentsion:
https://extensions.gnome.org/extension/1207/vscode-search-provider/

Please try removing that extension from your system and see if the bug
persists.

** 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/1771278

Title:
  search in gnome is not working

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

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

[Bug 1771512] Re: /usr/bin/gnome-shell:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_with_unix_fd_list_sy

[Daniel van Vugt]

*** This bug is a duplicate of bug 1770875 ***
https://bugs.launchpad.net/bugs/1770875

** This bug has been marked a duplicate of bug 1770875
   gnome-shell crashed with signal 5 in g_main_context_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/1771512

Title:
  /usr/bin/gnome-
  
shell:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_with_unix_fd_list_sync

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

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

[Bug 1770875] Re: gnome-shell crashed with signal 5 in g_main_context_new()

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell crashed with signal 5 in g_main_context_new()

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

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

[Bug 1770875] Re: gnome-shell crashed with signal 5 in g_main_context_new()

[Daniel van Vugt]

** 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/1770875

Title:
  gnome-shell crashed with signal 5 in g_main_context_new()

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

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

[Bug 1771511] [NEW] Desktop lockdown vanished

[Stefan]

Public bug reported:

In 14.04 and 16.04, as desktop lockdown ("kiosk mode") we disabled the gsetting 
"org.gnome.desktop.background show-desktop-icons". 
Nautilus then disabled the context menu when a user right clicks on the 
background and didn't show any icons, but still showed the wallpaper - nice!
I tested this with nautilus 1:3.18.4.is.3.14.3-0ubuntu6 and earlier.

In 18.04 (tested version 1:3.26.3-0ubuntu4), this flag is not honored,
any more. After source code inspection, I saw, the nautilus-desktop is
always started in mode "--forced" which ignores this flag, completely.

Then I tried to remove the option "--forced" from nautilus-
classic.desktop, but nautilus-desktop didn't start, the whole session
didn't start (I think this is lp bug #1633826).

What can I do to get the desktop locking, again? Thanks for your help.

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

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

Title:
  Desktop lockdown vanished

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

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

[Bug 1663839] Re: gnome-session-binary[1676]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

[Frits Jalvingh]

18.04 has this quite often too, most of the times about 1 to 2 minutes
after the first login.

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

Title:
  gnome-session-binary[1676]: Unrecoverable failure in required
  component org.gnome.SettingsDaemon.Color.desktop

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

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

[Bug 830348] Re: desktop contents briefly visible on resume from suspend before lock dialog

[Lorant Nemeth]

*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300

I still experience this with stock Ubuntu 18.04 (fresh install, with
default wm, screensaver settings...) with latest upgrades.

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

Title:
  desktop contents briefly visible on resume from suspend before lock
  dialog

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

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

[Bug 1764643] Re: Logout after console use freezes GUI

[Daniel van Vugt]

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

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

Title:
  Logout after console use freezes GUI

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

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