[Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

2019-04-15 Thread Mohammad Kazemi
** Changed in: gnome-shell (Ubuntu Bionic)
   Status: Triaged => 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/1823175

Title:
  Battery status shows "Estimating..." when fully charged

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

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

[Bug 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

2019-04-15 Thread Patrick
apport information

** Tags added: apport-collected

** Description changed:

  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-04-14 (1 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: mutter 3.32.0+git20190410-1ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_ES.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
+ Tags:  disco
+ Uname: Linux 5.0.0-11-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

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

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

[Bug 1824753] ProcCpuinfoMinimal.txt

2019-04-15 Thread Patrick
apport information

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

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

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

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

[Bug 1810634] Re: Lubuntu lacks an input method for Korean

2019-04-15 Thread Walter Lapchynski
>From 16.04 to 19.04, Lubuntu has shipped the fcitx input method
framework, yet it has not included support for Korean, such as found in
the fcitx-hangul package. In fact, even in 14.04, which used the iBus
input method framework, no Korean support was included.

Further review of the input method packages is necessary, including support of 
other languages. We are tracking this larger effort here:
https://phab.lubuntu.me/T64

** Package changed: fcitx (Ubuntu) => lubuntu-meta (Ubuntu)

** Changed in: lubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: lubuntu-meta (Ubuntu)
   Status: Confirmed => Triaged

** Description changed:

- [Lubuntu 19.04] 
- It is missing Input-Method like fcitx-hangul while installing process.
- After the fresh installation, I can not find input method fcitx-hangul for 
Korean.
- But, There is Input Method Framework Fcitx.
+ From 16.04 to 19.04, Lubuntu has shipped the fcitx input method
+ framework, yet it has not included support for Korean, such as found in
+ the fcitx-hangul package. In fact, even in 14.04, which used the iBus
+ input method framework, no Korean support was included.
  
- I think it is missing while installing Lubuntu 19.04
- I use fcitx-hangul after installing manually
- $ sudo apt install fcitx-hangul
- 
- It should be installed by default.
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 19.04
- Package: fcitx (not installed)
- ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
- Uname: Linux 4.18.0-11-generic x86_64
- ApportVersion: 2.20.10-0ubuntu14
- Architecture: amd64
- CurrentDesktop: LXQt
- Date: Sun Jan  6 10:36:12 2019
- InstallationDate: Installed on 2019-01-05 (0 days ago)
- InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230)
- SourcePackage: fcitx
- UpgradeStatus: No upgrade log present (probably fresh install)
+ Further review of the input method packages is necessary, including support 
of other languages. We are tracking this larger effort here:
+ https://phab.lubuntu.me/T64

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

Title:
  Lubuntu lacks an input method for Korean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1810634/+subscriptions

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

[Bug 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

2019-04-15 Thread Daniel van Vugt
Also, please try downgrading to mutter version 3.32.0-1 by downloading
*.deb from:

  https://launchpad.net/ubuntu/+source/mutter/3.32.0-1/+build/16489975

and then install them with:

  dpkg -i *.deb

Now reboot and tell us if that fixes the problem.

** No longer affects: vlc (Ubuntu)

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

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

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

[Bug 1824753] Re: ubuntu-bug mutter

2019-04-15 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1824753

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Project changed: mutter => mutter (Ubuntu)

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

** Tags added: disco

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

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

** Summary changed:

- ubuntu-bug mutter
+ When I pass the Qt application to the secondary monitor the characters of the 
application increase

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

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

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

[Bug 1824753] [NEW] ubuntu-bug mutter

2019-04-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except the 
Qt applications. I have two monitors and when I pass the Qt application to the 
secondary monitor the characters of the application increase. They happen to 
the traditionally installed Qt applications and to those installed with Flatpak 
and Snap. I leave you a video in which you can see the problem with the VLC 
application.
https://youtu.be/tEZJONsinU4
https://i.imgur.com/R7GubxF.png?fb

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: Incomplete


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

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

[Bug 1623603] Re: display stays on tty1 on timed login

2019-04-15 Thread Daniel van Vugt
At the moment we are only releasing GNOME patches for Ubuntu 18.04 and
later. Plus there have been a couple of years worth of bug fixes.

Are you able to upgrade to Ubuntu 18.04 and try that?

** Tags added: xenial

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

Title:
  display stays on tty1 on timed login

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

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

[Bug 1584388] Re: network manager doesn't parse openvpn argument with IP and port on the same line correctly network-manager-openvpn

2019-04-15 Thread Launchpad Bug Tracker
[Expired for network-manager-openvpn (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  network manager doesn't parse openvpn argument with IP and port on the
  same line correctly network-manager-openvpn

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

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

[Bug 1814169] Re: Mutter upsteam bug: cannot overwrite workspaces layout

2019-04-15 Thread Bug Watch Updater
** Changed in: mutter
   Status: New => Fix Released

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

Title:
  Mutter upsteam bug: cannot overwrite workspaces layout

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

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

[Bug 1806246] Re: Unable to turn off 2 and more openvpn-connections via Network Manager

2019-04-15 Thread Launchpad Bug Tracker
[Expired for network-manager-openvpn (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unable to turn off 2 and more openvpn-connections via Network Manager

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

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

[Bug 1809712] Re: Not responding to input after switch user to auto-login account

2019-04-15 Thread Daniel van Vugt
These look most relevant:

Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
flip queue failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
Page flip failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (EE) modeset(0): 
present flip failed
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
flip queue failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
Page flip failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (EE) modeset(0): 
present flip failed
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
flip queue failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (WW) modeset(0): 
Page flip failed: Permission denied
Jan 19 19:38:47 shehadeh /usr/lib/gdm3/gdm-x-session[1140]: (EE) modeset(0): 
present flip failed

** Summary changed:

- Not responding to input after switch user to auto-login account
+ AutomaticLogin: Not responding to input after switch user to auto-login 
account

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

Title:
  AutomaticLogin: Not responding to input after switch user to auto-
  login account

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

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

[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input

2019-04-15 Thread Daniel van Vugt
Thanks. This appears to be the most interesting part of the log I can
see:

Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to initialize 
accelerated iGPU/dGPU framebuffer sharing: No matching EGL configs
Apr 15 22:22:50 lance-desktop gnome-shell[865]: Failed to apply DRM plane 
transform 0: Permission denied
Apr 15 22:22:51 lance-desktop gnome-shell[865]: WL: error in client 
communication (pid 865)
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE)
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: Fatal server error:
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE) wl_drm@4: 
error 0: authenicate failed
Apr 15 22:22:51 lance-desktop org.gnome.Shell.desktop[865]: (EE)
Apr 15 22:22:51 lance-desktop nm-dispatcher[734]: req:4 'connectivity-change': 
start running ordered scripts...
Apr 15 22:22:51 lance-desktop nm-dispatcher[734]: req:5 'dhcp6-change' 
[enp0s25]: start running ordered scripts...
Apr 15 22:22:51 lance-desktop gnome-shell[865]: X Wayland crashed; exiting
Apr 15 22:22:52 lance-desktop gnome-session[858]: gnome-session-binary[858]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 15 22:22:52 lance-desktop gnome-session-binary[858]: Unrecoverable failure 
in required component org.gnome.Shell.desktop
Apr 15 22:22:52 lance-desktop gnome-session-binary[858]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Apr 15 22:22:52 lance-desktop systemd-logind[529]: Failed to restore VT, 
ignoring: Input/output error

So next please follow these 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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1824588

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input

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

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

[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input

2019-04-15 Thread Erick Brunzell
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and
removed "quiet splash". Now it boots to the gdm3 screen every time. So
maybe something to do with how plymouth hands off the boot process to
gdm3? Or how quickly that hand off is completed?

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

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input

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

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

[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input

2019-04-15 Thread Daniel van Vugt
** Summary changed:

- Ubuntu Disco boots to or logs out to black screen
+ With AutomaticLogin enabled, logging out lands me on a black screen that's 
unresponsive to any keyboard input

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

Title:
  With AutomaticLogin enabled, logging out lands me on a black screen
  that's unresponsive to any keyboard input

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

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

[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen

2019-04-15 Thread Erick Brunzell
This was tricky but I finally got a successful boot (following several
failed boots) using gdm3 by selecting the kernel with "e" from grub and
then removing 'quiet splash'. So I hope this is more helpful.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256203/+files/prevboot.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/1824588

Title:
  Ubuntu Disco boots to or logs out to black screen

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

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

[Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)

2019-04-15 Thread Daniel van Vugt
** No longer affects: mutter (Ubuntu)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145
  (but 4.4.0-143 works)

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

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

[Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)

2019-04-15 Thread You-Sheng Yang
How about 4.4.0-144? Would it help to narrow down the issue a bit more?

https://launchpad.net/ubuntu/+source/linux/4.4.0-144.170

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145
  (but 4.4.0-143 works)

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Daniel van Vugt
It also sounds like this might be the new form of bug 1734095.

** Summary changed:

- undismissable, unclickable authentication dialog left on screen after 
policykit authentication
+ undismissable, unclickable authentication dialog left on screen after 
policykit authentication [gnome-shell[N]: pushModal: invocation of begin_modal 
failed]

** Summary changed:

- undismissable, unclickable authentication dialog left on screen after 
policykit authentication [gnome-shell[N]: pushModal: invocation of begin_modal 
failed]
+ undismissable, unclickable authentication dialog left on screen after 
policykit authentication [pushModal: invocation of begin_modal failed]

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication [pushModal: invocation of begin_modal failed]

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

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

[Bug 1734095] Re: After upgrade to ubuntu 17.10 Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2019-04-15 Thread Daniel van Vugt
** Tags removed: artful
** Tags added: disco

** Summary changed:

- After upgrade to ubuntu 17.10 Software & Updates not showing authorization 
popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]
+ Software & Updates not showing authorization popup [gnome-shell[N]: 
pushModal: invocation of begin_modal failed]

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

** Project changed: gnome-shell => gnome-shell-legacy-bugs

** Changed in: gnome-shell-legacy-bugs
   Importance: High => Unknown

** Changed in: gnome-shell-legacy-bugs
   Status: Confirmed => Unknown

** Changed in: gnome-shell-legacy-bugs
 Remote watch: GNOME Bug Tracker #751335 => bugzilla.gnome.org/ #751335

** Tags removed: disco

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Daniel van Vugt
This sounds particularly relevant:

Apr 15 12:20:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 12:20:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed

which seems to be from gnome-shell/js/ui/main.js

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication [gnome-shell[N]: pushModal: invocation of
  begin_modal failed]

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

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

[Bug 1824855] Re: very long delay to display login prompt if there are a large number of uncleared desktop notifications

2019-04-15 Thread Daniel van Vugt
Steve,

Next time the problem happens please send us the section of the journal
(journalctl -b0) showing that long wake-up period.

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

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

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

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

[Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

2019-04-15 Thread Daniel van Vugt
Thanks. That log shows you are using lightdm and 'slick-greeter', so not
regular Ubuntu.

Are you able to redo those steps using plain Ubuntu? I want to see the
failure happening in a way where lightdm and slick-greeter are not
involved.

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

** Also affects: slick-greeter (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: slick-greeter (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/1824661

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

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

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

[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen

2019-04-15 Thread Daniel van Vugt
Thanks. Unfortunately that log is not helpful because it contains only
one boot done in recovery mode with modesetting disabled:

Apr 15 14:33:53 lance-desktop kernel: Command line:
BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic
root=UUID=ddacea78-cdda-4236-94c3-4c4d9d3dad20 ro recovery nomodeset

Please reproduce the black screen problem once (ensuring that you are
not booting into recovery mode*), then reboot again once, and then run:

   journalctl -b-1 > prevboot.txt

to collect the log of the previous boot which had the problem, and send
us the file 'prevboot.txt'.

* To ensure you are not booting in recovery mode, as soon as the purple
screen appears tap Escape. Then search through the menus and choose a
kernel to boot that is not recovery mode.

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

Title:
  Ubuntu Disco boots to or logs out to black screen

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

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

[Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 4.4.0-143 works)

2019-04-15 Thread Daniel van Vugt
** Summary changed:

- Blank screen after booting 4.4.0-145
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 (but 
4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145
  (but 4.4.0-143 works)

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Steve Langasek
the window did go away when I did a kill -HUP 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/1824874

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

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

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

[Bug 1824886] [NEW] Battery applet does not display battery charge.

2019-04-15 Thread Mike Kapushin
Public bug reported:

Battery applet does not display battery charge. Always shows 100%.

ASUS 1215T-RED008S.
Description:Ubuntu 18.04.2 LTS
Release:18.04
gnome-control-center:
  Установлен: 1:3.28.2-0ubuntu0.18.04.2
  Кандидат:   1:3.28.2-0ubuntu0.18.04.3

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 16 00:48:18 2019
InstallationDate: Installed on 2019-04-10 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Battery applet does not display battery charge.

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Steve Langasek
journalctl output for the period in question, taken from 'journalctl -l
--since today | grep gnome-shell'.

13:19 is my restart of the polkit service.

The actual authentication did not succeed, aptdaemon did not start and
no packages were installed; so I don't know exactly when this window
broke - though I think it was after 13:00, and thus much later than the
polkit messages at the beginning of the log.  (I certainly didn't have a
broken window on my screen for ~2h before filing this bug.)

Apr 15 11:33:29 virgil gnome-shell[4571]: polkitAuthenticationAgent: Received 3 
identities that can be used for authentication. Only considering one.
Apr 15 11:33:29 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 11:33:29 virgil gnome-shell[4571]: polkitAuthenticationAgent: Failed to 
show modal dialog. Dismissing authentication request for action-id 
org.debian.apt.install-or-remove-packages cookie 
2-c14dea1098d77930282650c2c7031008-3-811320afb0a7974406f93ce80f7d4594
Apr 15 11:59:56 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 11:59:56 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 12:20:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 12:20:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 12:22:57 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 12:22:57 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 12:33:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 12:33:28 virgil gnome-shell[4571]: pushModal: invocation of begin_modal 
failed
Apr 15 12:53:18 virgil gnome-shell[4571]: JS WARNING: 
[resource:///org/gnome/gjs/modules/signals.js 128]: Too many arguments to 
method Clutter.Actor.destroy: expected 0, got 1
Apr 15 12:56:06 virgil dbus-daemon[1964]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service' requested by 
':1.317' (uid=1000 pid=4571 comm="/usr/bin/gnome-shell " label="unconfined")
Apr 15 12:56:12 virgil dbus-daemon[4403]: [session uid=1000 pid=4403] 
Activating service name='org.gnome.Nautilus' requested by ':1.26' (uid=1000 
pid=4571 comm="/usr/bin/gnome-shell " label="unconfined")
Apr 15 12:56:12 virgil dbus-daemon[4403]: [session uid=1000 pid=4403] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.26' 
(uid=1000 pid=4571 comm="/usr/bin/gnome-shell " label="unconfined")
Apr 15 12:56:13 virgil gnome-shell[4571]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.80/org/ayatana/NotificationItem/software_update_available
Apr 15 12:56:13 virgil gnome-shell[4571]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Apr 15 12:56:13 virgil gnome-shell[4571]: [AppIndicatorSupport-FATAL] unable to 
update overlay icon
Apr 15 12:56:13 virgil gnome-shell[4571]: Error connecting to Nautilus
Apr 15 12:56:14 virgil gnome-shell[4571]: Couldn’t parse steam.desktop as a 
desktop file, will treat it as a regular file.
Apr 15 13:00:08 virgil gnome-shell[4571]: JS WARNING: 
[resource:///org/gnome/shell/ui/workspacesView.js 639]: reference to undefined 
property 1
Apr 15 13:00:08 virgil gnome-shell[4571]: JS ERROR: TypeError: 
this._workspacesViews[i] is undefined
Apr 15 13:13:40 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 13:13:40 virgil gnome-shell[4571]: remove_mnemonics: assertion 'label != 
NULL' failed
Apr 15 13:19:17 virgil polkitd(authority=local)[22657]: Registered 
Authentication Agent for unix-session:2 (system bus name :1.317 
[/usr/bin/gnome-shell], object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Apr 15 13:20:36 virgil gnome-shell[4571]: Could not delete runtime/persistent 
state file: Error removing file 
/home/vorlon/.local/share/gnome-shell/notifications: No such file or directory
Apr 15 13:23:50 virgil gnome-shell[4571]: Couldn’t parse steam.desktop as a 
desktop file, will treat it as a regular file.

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Sebastien Bacher
** Package changed: policykit-1 (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

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

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

[Bug 1824738] Re: gvfsd-admin crashed with signal 5

2019-04-15 Thread Sebastien Bacher
Right, that seems suboptimal/should be sent upstream on
https://gitlab.gnome.org/GNOME/gvfs/issues

** Information type changed from Private to Public

** Changed in: gvfs (Ubuntu)
   Status: Incomplete => 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/1824738

Title:
  gvfsd-admin crashed with signal 5

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Steve Langasek
Screenshot of the dialog in question.  The text comes from aptdaemon's
policykit policy.

** Attachment added: "lp-1824874-screenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+attachment/5256050/+files/lp-1824874-screenshot.png

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

Title:
  undismissable, unclickable authentication dialog left on screen after
  policykit authentication

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

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

[Bug 1824874] [NEW] undismissable, unclickable authentication dialog left on screen after policykit authentication

2019-04-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

In disco, when policykit prompted me for a password in order for update-
manager to dispatch instructions to aptdaemon to perform package
updates, the password dialog remained on the screen after I clicked
'authenticate'.

The window is not clickable, it appears not to even be a window - mouse
presses are received by the window underneath.  The exception is that
the 'cancel' button is active and receives mouse events - but clicking
it does nothing.

This may be a gnome-shell issue rather than policykit.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: policykit-1 0.105-25
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 13:14:33 2019
InstallationDate: Installed on 2010-09-24 (3125 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: policykit-1
UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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


** Tags: amd64 apport-bug disco rls-dd-incoming
-- 
undismissable, unclickable authentication dialog left on screen after policykit 
authentication
https://bugs.launchpad.net/bugs/1824874
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to gnome-shell in Ubuntu.

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

[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen

2019-04-15 Thread Erick Brunzell
Method used to collect this info:

(1) Fresh installed 20190413.2 choosing not to auto-login.
(2) Rebooted after install and surprisingly gdm3 appeared as it should so I 
booted to desktop and just rebooted.
(3) That reboot failed as had been the previous case - just a black screen, 
totally unresponsive.
(4) Performed a hard reboot with the reset button on the PC, entered recovery 
from grub menu, then installed lightdm, and rebooted.
(5) Collected info as instructed.

So there are a total of 3 boots. The first was successful - no problems.
The second booted to a black screen instead of displaying gdm3 screen.
Third boot was performed using lightdm.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256045/+files/prevboot.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/1824588

Title:
  Ubuntu Disco boots to or logs out to black screen

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

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

[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen

2019-04-15 Thread Erick Brunzell
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium
Dual Core.

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.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/1824588

Title:
  Ubuntu Disco boots to or logs out to black screen

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

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

[Bug 1770502] Re: Brasero hangs when burning cds

2019-04-15 Thread Rob Cannell
Mike's fix worked for me as well - Ubuntu 18.04.

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

Title:
  Brasero hangs when burning cds

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

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

[Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

2019-04-15 Thread Treviño
Nope, glib fix is enough for nautilus.

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

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions

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

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-15 Thread Treviño
Since I see that fix for budgie landed in disco and the SRU package is
in queue, I think we can mark this as verified.

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

Title:
  SRU 3.28 latest git to bionic

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

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

[Bug 1824855] [NEW] very long delay to display login prompt if there are a large number of uncleared desktop notifications

2019-04-15 Thread Steve Langasek
Public bug reported:

When waking my laptop screen up at the lock screen, it takes a very long
time to display the password prompt (definitely longer than 30s,
possibly longer than 1m - I didn't time it).  I notice that while
waiting for the password prompt, the screen is showing a full list of
(obfuscated) desktop notifications.  After logging in, I used the gnome-
shell interface to clear the notifications; then I locked my screen
again, at which point hitting the space bar caused the password prompt
to show up immediately.

So it looks like the time to display the password prompt might scale
linearly with the number of notifications; which is not useful, because
there is a finite number of (obfuscated!) notifications that will be
displayed on the lock screen, and AFAIK you can't interact with them
through the lock screen at all.  So we shouldn't be wasting time
processing (and presumably rendering) notifications that will never be
visible.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 15 09:58:23 2019
InstallationDate: Installed on 2010-09-24 (3125 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
SourcePackage: gdm3
UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  very long delay to display login prompt if there are a large number of
  uncleared desktop notifications

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

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

[Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-15 Thread Tony Pursell
Attached is Xorg log for the boot of 4.4.0-145

** Attachment added: "Xorg log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255955/+files/Xorg.0.log.old

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

Title:
  Blank screen after booting 4.4.0-145

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

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

[Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted

2019-04-15 Thread Colin Watson
** Package changed: gnome-disk-utility (Ubuntu) => parted (Ubuntu)

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

Title:
  Partitions display wrong in gnome -disks - ok in gparted

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

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

[Bug 1821957] Re: Turning off a monitor unlocks the computer

2019-04-15 Thread Eduardo dos Santos Barretto
** Information type changed from Private Security to Public Security

** Changed in: ubuntubudgie
   Status: New => Incomplete

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

Title:
  Turning off a monitor unlocks the computer

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

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

[Bug 1824641] Re: Blank screen after booting 4.4.0-145

2019-04-15 Thread Tony Pursell
Attached is a syslog for the boot of 4.4.0-145 from start up to shut
down in the way described above.

** Attachment added: "Syslog from boot of 4.4.0-145"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145

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

Title:
  Blank screen after booting 4.4.0-145

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

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

[Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

2019-04-15 Thread Eric
Daniel,

As requested, Here is the prevboot.txt file. Please let me know if
there's anything else I can do to assist. Thanks.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824661/+attachment/5255919/+files/prevboot.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/1824661

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

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

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

[Bug 1810316] Re: gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT (object))

2019-04-15 Thread El jinete sin cabeza
** Description changed:

+ The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center. This problem was most recently seen with package version 
1:3.30.0-0ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 
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/.
+ 
+ ---
+ 
  https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143
  
  ---
  
  [Impact]
  gnome-control-center goes crash when I try to work with two USB WiFi cards.
  
  [Test Case]
  I have a wireless card connected and then I connect 'another' wireless card 
and the network module starts to malfunction in the gnome-control-center.
  
  [Potential Regression]
  I think it's not a potential regression.
  
  Original Description
    
  * I was trying to open wifi settings
  * I'm connecting 2 WiFi USB in ubuntu disk
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 09:54:42 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2018-09-27 (97 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: gnome-control-center wifi
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-control-center
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   cc_object_storage_add_object ()
   cc_wifi_panel_static_init_func ()
   cc_panel_loader_fill_model ()
  Title: gnome-control-center crashed with SIGABRT
  UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers 
wireshark
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

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

Title:
  gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
  (object))

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

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

[Bug 1067301] Re: gnome-keyring does not support "ssh-add -c"

2019-04-15 Thread Marius Gedminas
The gnome-bugs link is broken.  Working links:

- https://bugzilla.gnome.org/show_bug.cgi?id=525574 (old bugzilla)
- https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5 (new gitlab)

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #5
   https://gitlab.gnome.org/GNOME/gnome-keyring/issues/5

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

Title:
  gnome-keyring does not support "ssh-add -c"

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

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

[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected

2019-04-15 Thread Bug Watch Updater
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.gnome.org/show_bug.cgi?id=750260.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2015-06-02T03:12:42+00:00 Chris Murphy wrote:

Created attachment 304401
screen shot

control-center-3.16.2-1.fc22.x86_64

There is a question mark icon in the upper right corner that turns out
to be for the wired connection. A ? used in this manner suggests the
system is confused about something, and wants me to know that it's
confused, hoping I can do something about it. So I'd expect there'd be a
notification or a way to get more information about what the confusion
is about.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/0


On 2015-06-02T03:15:42+00:00 Chris Murphy wrote:

Created attachment 304402
journal for this boot

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/1


On 2015-06-02T10:14:57+00:00 Bugzilla-x wrote:

The menu bar is part of gnome-shell. The "?" you're seeing though means
that the connectivity check failed.

[ 3920.153840] f21v.localdomain NetworkManager[826]: 
Connectivity check for uri
'https://fedoraproject.org/static/hotspot.txt' failed with 'Peer failed
to perform TLS handshake'.

It's either a Fedora infrastructure problem, or a NetworkManager one.
Reassigning to NetworkManager.

See bug 750268 for a follow-up on the icon not being self-explanatory
enough.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/2


On 2015-06-03T09:56:08+00:00 Thomas Haller wrote:

This is the same as downstream bug
https://bugzilla.redhat.com/show_bug.cgi?id=1176316

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/3


On 2015-08-31T09:48:34+00:00 Jan Vlug wrote:

I have a similar problem with an unexplained question mark for a wireless 
connection that works fine.
I seem to have this issue when I'm behind a proxy (both for wired and wireless 
network connections).

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/4


On 2015-09-08T10:38:43+00:00 Thomas Haller wrote:

(In reply to Bastien Nocera from comment #2)
> 
> [ 3920.153840] f21v.localdomain NetworkManager[826]:   Connectivity
> check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> 'Peer failed to perform TLS handshake'.

In this case, the connectivity check failed because of the SSL
connection.

It is anyway a bad idea to use https for connectivity checking.

We fixed that upstream in bug 747866 and commit
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2a3a4eb16f9119bf434a28adc94c2684da8fd5e4


Note that this is largely a configuration issue. So, users must rectify their 
configuration, or (if the distribution installed configuration snippets) the 
distribution must fix the configuration file.


For downstream/Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1176316 this 
will be done.


Closing BZ as fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1722256/comments/5


On 2015-09-08T14:34:09+00:00 Bugzilla-x wrote:

(In reply to Thomas Haller from comment #5)
> (In reply to Bastien Nocera from comment #2)
> > 
> > [ 3920.153840] f21v.localdomain NetworkManager[826]:   Connectivity
> > check for uri 'https://fedoraproject.org/static/hotspot.txt' failed with
> > 'Peer failed to perform TLS handshake'.
> 
> In this case, the connectivity check failed because of the SSL connection.
> 
> It is anyway a bad idea to use https for connectivity checking.

Why? It protects the user's privacy, at least a tiny bit.

> We fixed that upstream in bug 747866 and commit
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/
> ?id=2a3a4eb16f9119bf434a28adc94c2684da8fd5e4

If by "fixed" you mean "worked around", then yes.

> Note that this is largely a configuration issue. So, users must rectify
> their configuration, or (if the distribution installed configuration
> snippets) the distribution must fix the configuration file.
> 
> 
> For downstream/Fedora, https://bugzilla.redhat.com/show_bug.cgi?id=1176316
> this will be done.
> 
> 
> 
> Closing BZ as fixed.

This really isn't fixed.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-

[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected

2019-04-15 Thread Daniel van Vugt
** Bug watch added: GNOME Bug Tracker #750260
   https://gitlab.gnome.org/750260

** Project changed: gnome-shell => gnome-shell-legacy-bugs

** Bug watch added: GNOME Bug Tracker #750260
   https://gitlab.gnome.org/750260

** No longer affects: gnome-shell-legacy-bugs

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

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

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

Title:
  Wifi connection status icon shows a "?" question mark when connected

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

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

[Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

2019-04-15 Thread Daniel van Vugt
** Changed in: gnome-bluetooth (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: gnome-bluetooth (Ubuntu Bionic)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

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

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

[Bug 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

2019-04-15 Thread Daniel van Vugt
** Package changed: ubuntu => gdm3 (Ubuntu)

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

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

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

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

[Bug 1824661] [NEW] Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

2019-04-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello. I am having issues consistently with this laptop and the Nvidia
drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu Budgie,
and Ubuntu MATE. This is with both the recommended 418 driver as well as
390. Today I tried installing the latest daily of Ubuntu MATE with the
proprietary driver option on my Dell XPS 15 9570 with Nvidia GP107M
(GeForce GRX 1050 Time Mobile). Boots to blank screen that flashes a
couple times. Can't get to tty. Reboot, editing grub to include
nomodeset. Boots to underscore character in the top left. I can get tty
at least. 418 driver is installed. Looking at logs but nothing seems
obvious. If there's anything I can do to help with this please let me
know. Thanks!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
Uname: Linux 5.0.0-11-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Sat Apr 13 18:27:12 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2019-04-13 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 TERM=cygwin
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.1
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco nvidia ubuntu
-- 
Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank 
screen that flashes a couple times. Can't get to tty.
https://bugs.launchpad.net/bugs/1824661
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 1815550] Re: gnome-shell high memory and CPU usage when desktop icons are constantly created or deleted

2019-04-15 Thread Daniel van Vugt
** Summary changed:

- gnome-shell high memory and CPU usage when desktop icons are constantly 
changing
+ gnome-shell high memory and CPU usage when desktop icons are constantly 
created or deleted

** Summary changed:

- gnome-shell high memory and CPU usage when desktop icons are constantly 
created or deleted
+ gnome-shell high memory and CPU usage when desktop files are constantly 
created or deleted

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

Title:
  gnome-shell high memory and CPU usage when desktop files are
  constantly created or deleted

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

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

[Bug 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)

2019-04-15 Thread Daniel van Vugt
Unfortunately it seems the fix for this bug landed just hours/days
slightly too late to be included in gnome-shell 3.32.0+git20190410

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

Title:
  Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not
  the ubuntu-dock)

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

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

[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

2019-04-15 Thread Sjef Bosman
Yep, no crashes so far with Animation disabled.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

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

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

[Bug 1824235] Re: nautilus package crashes on after power on.

2019-04-15 Thread Sebastien Bacher
See http://wiki.ubuntu.com/DebuggingProgramCrash for some details on the
topic, but it's a program error which leads the application to close in
a specific way

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

Title:
  nautilus package crashes on after power on.

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

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

[Bug 1824497] Re: unable to copy small files with nautilus on cifs mount

2019-04-15 Thread Sebastien Bacher
Thanks!

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

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

Title:
  unable to copy small files with nautilus on cifs mount

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

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

[Bug 1824699] Re: gnome-calendar pango critical

2019-04-15 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

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

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

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

Title:
  gnome-calendar pango critical

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

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

[Bug 1824583] Re: gnome-calendar uses default Adwaita theme when using Yaru-Dark theme

2019-04-15 Thread Sebastien Bacher
** Changed in: gnome-calendar (Ubuntu)
   Importance: Undecided => Low

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

Title:
  gnome-calendar uses default Adwaita theme when using Yaru-Dark theme

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

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

[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected

2019-04-15 Thread Sebastien Bacher
Could those having the issue add their journalctl log after triggering
the bug?

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

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

Title:
  Wifi connection status icon shows a "?" question mark when connected

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

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