[Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2018-05-27 Thread Apport retracing service
** Tags added: cosmic

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

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

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

[Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using Firefox

2018-05-27 Thread Daniel van Vugt
Oooh... that makes sense now, thanks.

The problem you are seeing is with mutter/gnome-shell being inefficient
at frequently-updating software rendered windows. This is a known
problem, but until now we only knew of Eclipse triggering it (bug
1756508), and the older pre-Quantum versions of Firefox (bug 1696305).

What you are seeing is a known performance problem, but you have
discovered a great test case for it in the Resources tab. So thanks.

As I suspected, this is not a problem with the new Firefox at all (which
is hardware rendered). It's a problem with gnome-system-monitor, or any
frequently-redrawing software rendered (e.g. Gnome) app.

I only have two more questions: What is your display resolution, and are
you using Wayland or Xorg? Both of these can be answered by running
'xrandr' and sending us the output.

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell.

2018-05-27 Thread Daniel van Vugt
What specific app do you find triggers gnome-shell's high CPU usage?

** Tags added: performance

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

Title:
  High CPU usage by gnome-shell.

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

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

[Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using Firefox

2018-05-27 Thread Daniel van Vugt
Nevermind, it's obvious you're using Xorg sessions.

At what resolution though? Please just run 'xrandr' and send us the
output.

** Summary changed:

- High CPU usage in gnome-shell & Xorg when using Firefox
+ High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's 
Resources tab

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

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

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

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

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

[Bug 1773541] Re: Entering wrong password once on login causes startup to hang on purple screen

2018-05-27 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1766137 ***
https://bugs.launchpad.net/bugs/1766137

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1766137, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1766137
   [regression] Password accepted but login fails (blank purple screen and 
mouse pointer only)

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

Title:
  Entering wrong password once on login causes startup to hang on purple
  screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773541/+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)

2018-05-27 Thread Daniel van Vugt
Does anyone feel like logging a new bug for the regression in
3.28.0-0ubuntu1.1/3.28.0-0ubuntu2 ?

It's a real bug now, since 3.28.0-0ubuntu2 was released in cosmic.

** Description changed:

  [ Description ]
  
  Due to a refcounting bug, a GDBusConnection was getting disposed when it
- was still required. The symptom of this was that you couldn't log in if
- you'd got your password wrong.
+ was still required. The symptom of this was that you couldn't log in on
+ the second attempt if you'd got your password wrong on the first
+ attempt.
  
  [ Test case ]
  
  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password
  
  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.
  
  [ Fix ]
  
  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-
  
  The GdmClient has a shared GDBusConnection for its operations. The first
  time  someone calls for it, it is created and stored in the object's
  private structure. Subsequent calls return *a new reference* to this
  same object. It turned out that the asynchronous method to get the
  connection was accidentally unreferencing its object before giving it to
  the caller if it was returning an already-existing connection.
  
  For this to work properly, we need to nullify the pointer we stored when
  the connection goes away, so we know when to make a new one. There were
  some cases where we didn't add the weak references required to do that.
  Those are also fixed.
  
  [ Regression potential ]
  
  Now we share connections more than we did before. We also more carefully
  track when to clear our object. If we got this wrong, we might end up
  leaking the connection or dropping it in even more cases.
  
  [ Original report ]
  
- 
- WORKAROUND: After typing an incorrect password, click Cancel, then click your 
name, then enter your password again.
+ WORKAROUND: After typing an incorrect password, click Cancel, then click
+ your name, then enter your password again.
  
  ---
  
  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable menu
  in the top right. If I enter it correctly the first time, there is no
  problem.
  
  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.
  
  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  [ Description ]
  
  Due to a refcounting bug, a GDBusConnection was getting disposed when it
  was still required. The symptom of this was that you couldn't log in on
  the second attempt if you'd got your password wrong on the first
- attempt.
+ attempt. All you'd see is a blank purple screen and mouse pointer only.
  
  [ Test case ]
  
  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password
  
  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.
  
  [ Fix ]
  
  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-
  
  The GdmClient has a shared GDBusConnection for its operations. The first
  time  someone calls for it, it is created and stored in the object's
  private structure. Subsequent calls return *a new reference* to this
  same object. It turned out that the asynchronous method to get the
  connection was accidentally unreferencing its object before giving it to
  the caller if it was returning an already-existing connection.
  
  For this to work properly, we need to nullify the pointer we stored when
  the connection goes away, so we know when to make a new one. There were
  some cases where we didn't add the weak references required to do that.
  Those are also fixed.
  
  [ Regression potential ]
  
  Now we share connections more than we did before. We also more carefully

[Bug 1773528] Re: High CPU usage by gnome-shell.

2018-05-27 Thread Hayk Baghdasaryan
I've noticed that playing videos on youtube affects it the most. The bigger is 
resolution the higher is CPU usage. But it's 
also high while using WebStorm or VmWare.

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

Title:
  High CPU usage by gnome-shell.

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell.

2018-05-27 Thread Daniel van Vugt
When "playing videos on youtube", what browser (and version) are you
using?

Remember to focus on the CPU usage of the gnome-shell process only.

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

Title:
  High CPU usage by gnome-shell.

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell.

2018-05-27 Thread Hayk Baghdasaryan
Google Chrome Version 66.0.3359.181 (Official Build) (64-bit). 
By [CPU usage] in my previous letter I refer to CPU usage of gnome-shell.

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

Title:
  High CPU usage by gnome-shell.

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Daniel van Vugt
Thanks.

Can you please also run 'lspci -k' and send us the output?

** Summary changed:

- High CPU usage by gnome-shell. 
+ High CPU usage by gnome-shell when using Google Chrome

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 421239]

2018-05-27 Thread eddie latham
http://original.moxieyogafitness.com
Edward Latham

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

Title:
  updates failed http://:8080/:invalid host name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/421239/+subscriptions

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Hayk Baghdasaryan
Sure. Here is it.


00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 
08)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Host Bridge/DRAM Registers
Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07)
Subsystem: Lenovo Skylake GT2 [HD Graphics 520]
Kernel driver in use: i915
Kernel modules: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
Subsystem: Lenovo Sunrise Point-LP Thermal subsystem
Kernel driver in use: intel_pch_thermal
Kernel modules: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
Subsystem: Lenovo Sunrise Point-LP CSME HECI
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller 
[AHCI mode] (rev 21)
Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
Subsystem: Lenovo Sunrise Point-LP LPC Controller
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
Subsystem: Lenovo Sunrise Point-LP PMC
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
Subsystem: Lenovo Sunrise Point-LP SMBus
Kernel modules: i2c_i801
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
Kernel driver in use: r8169
Kernel modules: r8169
02:00.0 Network controller: Intel Corporation Dual Band Wireless-AC 3165 Plus 
Bluetooth (rev 99)
Subsystem: Intel Corporation Dual Band Wireless-AC 3165 Plus Bluetooth
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT 
[Radeon HD 8670A/8670M/8690M / R5 M330 / M430] (rev 83)
Subsystem: Lenovo Radeon R5 M330
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Daniel van Vugt
Do you find any significant difference in performance between Xorg and
Wayland sessions?

Is this bug the same?

** Tags added: radeon

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Hayk Baghdasaryan
I mean the performance is mostly the same.

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Hayk Baghdasaryan
Not actually. But mouse pointer moves are not smooth in Wayland session.
So I guess that counts.

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 1773634] [NEW] Nutilus can't delete folders on samba share

2018-05-27 Thread Vonschutter
Public bug reported:

When deleting folders (only) on a samba share, the folders re appear
after view/refresh. They were never deleted even though initially the
folders seemed to be. Same share, same credentials, are able to delete
the folders successfully from windows and older versions of Ubuntu.

Bug is resolved upstream it seems: 
https://bugzilla.gnome.org/show_bug.cgi?id=792147

Please implement.

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

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

Title:
  Nutilus can't delete folders on samba share

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

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

[Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

2018-05-27 Thread Yuri
Resolution: 1920 X 1080 (16:9), with a refresh rate of 60,00 Hz, I use
an HDMI connection:

yuri@DS47:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 509mm x 286mm
   1920x1080 60.00*+  50.0059.94  
   1920x1080i60.0050.0050.0059.94  
   1600x1200 60.00  
   1680x1050 59.88  
   1400x1050 59.95  
   1280x1024 75.0260.02  
   1440x900  74.9859.90  
   1280x960  60.00  
   1360x768  60.02  
   1152x864  75.00  
   1280x720  60.0050.0059.94  
   1024x768  75.0370.0760.00  
   832x624   74.55  
   800x600   72.1975.0060.3256.25  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   720x480i  60.0059.94  
   640x480   75.0072.8166.6760.0059.94  
   720x400   70.08  
DP-2 disconnected (normal left inverted right x axis y axis)

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

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

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

[Bug 1765261] Re: [regression] Ubuntu 18.04 login screen rejects a valid password on first attempt. Usually works on the second attempt

2018-05-27 Thread Kabeer Vohra
Can also confirm bug, when logging in from a reboot, it works fine but
when I show text after locking and unlocking (using windows key + L to
lock) and I show text, it seems that the first 3 letters of my password
are lowercase even though I was holding shift. I can also confirm that
backspacing them all (using ctrl + backspace) and retyping the password
without attempting to log in with the incorrect password works fine.

I am using Gnome 3 on Ubuntu 18.04

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

Title:
  [regression] Ubuntu 18.04 login screen rejects a valid password on
  first attempt. Usually works on the second attempt

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

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

[Bug 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Metta Crawler
gdm version 3.28.0-0ubuntu1

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

Title:
  No caps lock indicator on login screen

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

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

[Bug 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Metta Crawler
18.04 GDM login screen now displays an exclamation mark as a caps lock 
indicator.
The older GDM used a different icon but this is sufficient for me.
It is my opinion that this issue has been resolved.

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

Title:
  No caps lock indicator on login screen

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

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

[Bug 1772913] Re: Android phone doesn't appear in shotwell

2018-05-27 Thread Jens Georg
For some reason the device is not tagged with ID_GPHOTO2 anymore on
18.04 when in PTP mode.

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

Title:
  Android phone doesn't appear in shotwell

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

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

[Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

2018-05-27 Thread Bump
It should be installed somehow.

When I installed ubuntu I was running the discrete graphics card so
nvidia proprietary drivers installed automatically. Then I wanted to
switch to nouveau and that package is missing.

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

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

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

[Bug 1773651] [NEW] xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

2018-05-27 Thread Bump
Public bug reported:

When I switch from nvidia to nouveau from software-properties-gtk and
reboot, with the nouveau driver already running, I experience graphic
glitches on gnome apps. This is due to "xserver-xorg-video-nouveau"
missing.

See bugs here:

https://bugs.freedesktop.org/show_bug.cgi?id=106657
https://gitlab.gnome.org/GNOME/nautilus/issues/426

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

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

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: nautilus (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: xserver-xorg-video-nouveau (Ubuntu)
   Importance: Undecided
   Status: New

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

** Summary changed:

- xserver-xorg-video-nouveau is required to display properly gnome graphics 
with nouveau driver
+ xserver-xorg-video-nouveau is required with nouveau driver to display 
properly gnome apps

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

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

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

[Bug 1773665] [NEW] gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

2018-05-27 Thread Hans Deragon
Public bug reported:

Whenever as root in a terminal, I start 'gvim', the whole windows system
crashes and the user find himself on the gdm login screen.  Windowing
session has been lost.

It only occurs with gvim. I tried xterm, terminator and gthumb as root
and these graphical application do not cause the crash.

Ubuntu 18.04 Bionic Beaver, all packages up to date as of 2018-05-27
11:26:45 EDT.

Following is the trace found under /var/log/syslog:

May 27 10:43:45 demloka gnome-shell[21426]: g_array_unref: assertion 'array' 
failed
May 27 10:43:45 demloka gnome-shell[21426]: message repeated 2 times: [ 
g_array_unref: assertion 'array' failed]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Xorg: 
../../../../glamor/glamor_largepixmap.c:1449: 
glamor_composite_largepixmap_region: Assertion `0' failed.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Backtrace:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 0: 
/usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5619d46e58ad]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 1: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x1bc649) [0x5619d46e9649]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 2: 
/lib/x86_64-linux-gnu/libpthread.so.0 (0x7f4c99632000+0x12890) [0x7f4c99644890]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 3: 
/lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7f4c9927fe97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 4: 
/lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7f4c99281801]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 5: 
/lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x3039a) [0x7f4c9927139a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 6: 
/lib/x86_64-linux-gnu/libc.so.6 (0x7f4c99241000+0x30412) [0x7f4c99271412]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x21e21) [0x7f4c95ee4e21]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 8: 
/usr/lib/xorg/modules/libglamoregl.so (0x7f4c95ec3000+0x16362) [0x7f4c95ed9362]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 9: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x13d896) [0x5619d466a896]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 10: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x13312c) [0x5619d466012c]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 11: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x52e98) [0x5619d457fe98]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 12: 
/usr/lib/xorg/Xorg (0x5619d452d000+0x56ee0) [0x5619d4583ee0]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 13: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7f4c99262b97]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) 14: 
/usr/lib/xorg/Xorg (_start+0x2a) [0x5619d456db8a]
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Fatal server error:
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Caught signal 
6 (Aborted). Server aborting
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: Please consult the 
The X.Org Foundation support
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: #011 at 
http://wiki.x.org
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]:  for help.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Please also 
check the log file at "/home/hans/.local/share/xorg/Xorg.0.log" for additional 
information.
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE)
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (II) AIGLX: 
Suspending AIGLX clients for VT switch
May 27 10:43:49 demloka /usr/lib/gdm3/gdm-x-session[21293]: (EE) Server 
terminated with error (1). Closing log file.
May 27 10:43:49 demloka update-notifier[22815]: update-notifier: Fatal IO error 
11 (Resource temporarily unavailable) on X server :0.

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

Title:
  gdm-x-session crash:  glamor_composite_largepixmap_region: Assertion
  `0' failed.

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

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

[Bug 1773665] Re: gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

2018-05-27 Thread Hans Deragon
** Tags added: crash gdm3

** Attachment added: "Full syslog at the point the crash occured."
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773665/+attachment/5145227/+files/syslog.crash-gdm-x-session-glamor_composite_largepixmap_region-launchpad-bug%231773665.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/1773665

Title:
  gdm-x-session crash:  glamor_composite_largepixmap_region: Assertion
  `0' failed.

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

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

[Bug 901147] Re: No timeout in gedit when connection is lost

2018-05-27 Thread Bug Watch Updater
** Changed in: gedit
   Status: Confirmed => Won't Fix

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

Title:
  No timeout in gedit when connection is lost

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

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

[Bug 1187981] Re: symbol conflicts in libtimezonemap1

2018-05-27 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Incomplete => Confirmed

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

Title:
  symbol conflicts in libtimezonemap1

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

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

[Bug 113338] Re: Cannot close a tab in Gedit by middle clicking the tab bar

2018-05-27 Thread Bug Watch Updater
** Changed in: gedit
   Status: Confirmed => New

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

Title:
  Cannot close a tab in Gedit by middle clicking the tab bar

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

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

[Bug 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell
** Also 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/1773597

Title:
  USB flash drive won't mount

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

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

[Bug 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell
Tried ...

 apt-get install --reinstall nautilus
 
No change. Still cannot mount USB flash drives.

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

Title:
  USB flash drive won't mount

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

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

[Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

2018-05-27 Thread Daniel van Vugt
Thanks. That explains a lot. I think gnome-shell is presently too slow
to be able to handle 1080p on a Celeron 847. But we are working on a
bunch of different optimizations that should help in future.

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

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

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

[Bug 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Daniel van Vugt
Upstreams:
https://gitlab.gnome.org/GNOME/gdm/issues/326
https://bugzilla.gnome.org/show_bug.cgi?id=762881

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

** Bug watch added: GNOME Bug Tracker #762881
   https://bugzilla.gnome.org/show_bug.cgi?id=762881

** Also affects: gnome-shell via
   https://bugzilla.gnome.org/show_bug.cgi?id=762881
   Importance: Unknown
   Status: Unknown

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

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

** Changed in: unity-greeter (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No caps lock indicator on login screen

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

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

[Bug 1773528] Re: High CPU usage by gnome-shell when using Google Chrome

2018-05-27 Thread Daniel van Vugt
Yes, I am aware of the mouse pointer being less efficient in Wayland
sessions. That's covered by bug 1690719.

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

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

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

Title:
  High CPU usage by gnome-shell when using Google Chrome

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

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

[Bug 1773665] Re: gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

2018-05-27 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your bug report is missing crash details. In
order to debug a crash we will need a crash report. To create one,
please follow these steps:

1. If you are not running a future development release of Ubuntu then apply the 
workaround from bug 994921.
2. If you are running the Ubuntu Stable Release you might need to enable apport 
in /etc/default/apport.
3. If the crash is in Xorg then uncomment this option from 
/etc/gdm3/custom.conf:
   # Additionally lets the X server dump core if it crashes
   #Enable=true
4. Reboot.
5. Reproduce the crash.
6. Look in /var/crash for crash files and when found, run:
   ubuntu-bug /var/crash/YOURFILE.crash
7. Add a comment here telling us the ID of the new bug that was created in step 
6.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments, and doing so is also a
security risk for yourself.

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

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

Title:
  gdm-x-session crash:  glamor_composite_largepixmap_region: Assertion
  `0' failed.

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

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

[Bug 1773651] Re: xserver-xorg-video-nouveau is required with nouveau driver to display properly gnome apps

2018-05-27 Thread Daniel van Vugt
Does the problem occur only in Xorg sessions or Wayland too?

Please run 'apport-collect 1773651' to help us get more information
about the machine.

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

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

** Changed in: software-properties (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Incomplete

** Tags added: nouveau

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

Title:
  xserver-xorg-video-nouveau is required with nouveau driver to display
  properly gnome apps

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

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

[Bug 1773665] Re: gdm-x-session crash: glamor_composite_largepixmap_region: Assertion `0' failed.

2018-05-27 Thread Daniel van Vugt
Alternatively, just look up previous crash reports from your system
here:

  https://errors.ubuntu.com/user/ID
  where ID is the contents of /var/lib/whoopsie/whoopsie-id

If you find relevant crashes there then please send us links to them.

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

Title:
  gdm-x-session crash:  glamor_composite_largepixmap_region: Assertion
  `0' failed.

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

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

[Bug 1773597] Re: USB flash drive won't mount

2018-05-27 Thread Roy Kimbrell
After a reboot, inserted encrypted USB flash drive (32G Lexar). Waited
about 15 minutes and the request for the password was displayed. I
entered the password, but nothing happened. Waited five minutes - then
rebooted with the drive still inserted. It was not recognized (by
Nautilus) upon completion of the reboot. Removed and inserted and it was
eventually recognized, but no window asking for a password showed until
I opened the "file cabinet" and clicked on the drive listed on the left.
A request for password then appeared. I entered the password and was
able to open the drive. However after about ten minutes, I could not
open any files - a lock icon appeared on the file icon. Removed the USB
flash drive and rebooted.

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

Title:
  USB flash drive won't mount

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1773597/+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)

2018-05-27 Thread Sum Sim
When are you gonna fix this bug? It says "Fix committed", but the bug is
still exist. I can't login to my Xubuntu like a month already!

-- 
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 1716159] Re: gdm greeter does not allow non-US characters (like euro character €) when typing password

2018-05-27 Thread Launchpad Bug Tracker
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  gdm greeter does not allow non-US characters (like euro character €)
  when typing password

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

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

[Bug 1734887] Re: No caps lock indicator on login screen

2018-05-27 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => Confirmed

** Changed in: gnome-shell
   Importance: Unknown => Medium

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

Title:
  No caps lock indicator on login screen

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

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

[Bug 1773620] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

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

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

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

Title:
  package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
  triggers looping, abandoned

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

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