[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[Yousef Saber]

alright thank you for the last additional information

Ubuntu 18.04 runs fine now with unity desktop environment selected as my
main desktop manager

meanwhile I'll wait for the next version of GNOME to run it on my device

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

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

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

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

The bug shows up now even in xfce4. It did not earlier with 17.04. Now all
the managers show up the bug.

Will do the other tests later. It is now 1.30 am and I have to get some
sleep.

Thanks

Peter


On Fri, Aug 17, 2018 at 1:00 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> That log appears to be from XFCE which you said does not exhibit the
> bug.
>
> Please do the 3-monitors test with gnome-shell, and run 'journalctl -f'
> there.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Incomplete
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-ati package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:
> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1787325] Re: Update wayland-protocols to version 1.16

[Simon Quigley]

Unsubscribing ~ubuntu-sponsors because there's nothing to sponsor.

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

Title:
  Update wayland-protocols to version 1.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1787325/+subscriptions

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

[Bug 1744941] Re: gnome-software crashes in as_app_parse_desktop_file

[Simon Quigley]

Unsubscribing sponsors as there's nothing left to sponsor.

Artful is also EOL.

Ping, Iain and Robie.

** Changed in: appstream-glib (Ubuntu Artful)
   Status: Confirmed => Won't Fix

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

Title:
  gnome-software crashes in as_app_parse_desktop_file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1744941/+subscriptions

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

[Bug 1725836] Re: No more than 2 displays work simultaneously

[Daniel van Vugt]

That log appears to be from XFCE which you said does not exhibit the
bug.

Please do the 3-monitors test with gnome-shell, and run 'journalctl -f'
there.

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

Title:
  No more than 2 displays work simultaneously

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

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

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

When I use ubuntu on wayland, the third screen is displayed, but the second
screen is not and there is no keyboard or mouse  input. Have to reboot with
the screen unplugged.

Peter

On Fri, Aug 17, 2018 at 12:29 AM Peter Wallbridge 
wrote:

> Nothing normally
> The following with the third monitor plugged in:
> peterw@simulator:~$ journalctl -f
> -- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769
> 772 800 +hsync +vsync (60.0 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771
> 777 806 -hsync -vsync (48.4 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604
> 625 +hsync +vsync (46.9 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865
> 868 900 +hsync +vsync (67.5 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025
> 1028 1066 +hsync +vsync (64.0 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
> RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080
> 1081 1084 1118 -hsync +vsync (67.1 kHz e)
> Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (EE)
> RADEON(0): failed to set mode: Invalid argument
> Aug 17 00:26:53 simulator xfsettingsd[1902]: Failed to configure CRTC 118.
> Aug 17 00:26:53 simulator kernel: [drm:atombios_crtc_mode_fixup [radeon]]
> *ERROR* unable to allocate a PPLL
> Aug 17 00:26:53 simulator kernel: [drm:drm_crtc_helper_set_config
> [drm_kms_helper]] *ERROR* failed to set mode on [CRTC:41:crtc-1]
> Aug 17 00:28:10 simulator xfce4-terminal[28461]:
> gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed
>
>
>
> On Thu, Aug 16, 2018 at 10:05 PM Daniel van Vugt <
> daniel.van.v...@canonical.com> wrote:
>
>> Going back to your JournalErrors.txt:
>>
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
>> RADEON(0): Page flip failed: Invalid argument
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
>> RADEON(0): present flip failed
>> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
>> RADEON(0): flip queue failed: Invalid argument
>>
>> I would like to verify if those errors correlate with the problem. Can
>> you please run:
>>
>>   journalctl -f
>>
>> and see if those errors only occur when trying to drive 3 monitors?
>>
>> Do the errors go away when only 2 monitors are plugged in?
>>
>> ** Also affects: xserver-xorg-video-ati (Ubuntu)
>>Importance: Undecided
>>Status: New
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1725836
>>
>> Title:
>>   No more than 2 displays work simultaneously
>>
>> Status in Mutter:
>>   Incomplete
>> Status in gnome-shell package in Ubuntu:
>>   Incomplete
>> Status in mutter package in Ubuntu:
>>   Incomplete
>> Status in xorg-server package in Ubuntu:
>>   Incomplete
>> Status in xserver-xorg-video-ati package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   I have three displays that worked fine in 17.04.
>>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>>   All three seem to be properly specified in monitors.xml.
>>   The display setup scree detects all three.
>>   UBUNTU 17.10
>>   AMD PitcairnLSB Version:
>> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>>   ---
>>   ApportVersion: 2.20.7-0ubuntu3
>>   Architecture: amd64
>>   CurrentDesktop: ubuntu:GNOME
>>   DisplayManager: gdm3
>>   DistroRelease: Ubuntu 17.10
>>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
>> (20161012.2)
>>   Package: mutter
>>   PackageArchitecture: amd64
>>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>>   Tags:  artful
>>   Uname: Linux 4.13.0-16-generic x86_64
>>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>>   _MarkForUpload: True
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>>
>

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

Title:
  No more than 2 displays work simultaneously

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

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com

[Bug 1776534] Re: Input devices stop working after logout or switch-user

[Launchpad Bug Tracker]

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

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

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

Title:
  Input devices stop working after logout or switch-user

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

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

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

Nothing normally
The following with the third monitor plugged in:
peterw@simulator:~$ journalctl -f
-- Logs begin at Tue 2018-05-29 18:26:24 EDT. --
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769
772 800 +hsync +vsync (60.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771
777 806 -hsync -vsync (48.4 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604
625 +hsync +vsync (46.9 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865
868 900 +hsync +vsync (67.5 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025
1028 1066 +hsync +vsync (64.0 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (II)
RADEON(0): Modeline "1920x1080"x60.0  172.80  1920 2040 2248 2576  1080
1081 1084 1118 -hsync +vsync (67.1 kHz e)
Aug 17 00:26:53 simulator /usr/lib/gdm3/gdm-x-session[1741]: (EE)
RADEON(0): failed to set mode: Invalid argument
Aug 17 00:26:53 simulator xfsettingsd[1902]: Failed to configure CRTC 118.
Aug 17 00:26:53 simulator kernel: [drm:atombios_crtc_mode_fixup [radeon]]
*ERROR* unable to allocate a PPLL
Aug 17 00:26:53 simulator kernel: [drm:drm_crtc_helper_set_config
[drm_kms_helper]] *ERROR* failed to set mode on [CRTC:41:crtc-1]
Aug 17 00:28:10 simulator xfce4-terminal[28461]:
gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed


On Thu, Aug 16, 2018 at 10:05 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Going back to your JournalErrors.txt:
>
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): Page flip failed: Invalid argument
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE)
> RADEON(0): present flip failed
> Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW)
> RADEON(0): flip queue failed: Invalid argument
>
> I would like to verify if those errors correlate with the problem. Can
> you please run:
>
>   journalctl -f
>
> and see if those errors only occur when trying to drive 3 monitors?
>
> Do the errors go away when only 2 monitors are plugged in?
>
> ** Also affects: xserver-xorg-video-ati (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1725836
>
> Title:
>   No more than 2 displays work simultaneously
>
> Status in Mutter:
>   Incomplete
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> Status in mutter package in Ubuntu:
>   Incomplete
> Status in xorg-server package in Ubuntu:
>   Incomplete
> Status in xserver-xorg-video-ati package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I have three displays that worked fine in 17.04.
>   Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3.
>   All three seem to be properly specified in monitors.xml.
>   The display setup scree detects all three.
>   UBUNTU 17.10
>   AMD PitcairnLSB Version:
> core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
>   ---
>   ApportVersion: 2.20.7-0ubuntu3
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   DisplayManager: gdm3
>   DistroRelease: Ubuntu 17.10
>   InstallationDate: Installed on 2017-02-23 (242 days ago)
>   InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64
> (20161012.2)
>   Package: mutter
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
>   Tags:  artful
>   Uname: Linux 4.13.0-16-generic x86_64
>   UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions
>

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

[Simon Quigley]

Artful is EOL.

** Changed in: gtk+3.0 (Ubuntu Artful)
   Status: Triaged => Won't Fix

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

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

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

[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[Daniel van Vugt]

That version containing the fix has not been released yet :)

https://gitlab.gnome.org/GNOME/mutter/tags

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

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

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

[Bug 1772365] Re: gnome-shell + chrome doing nothing consumes high CPU all the time

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  gnome-shell + chrome doing nothing consumes high CPU all the time

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

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

[Bug 1777115] Re: gnome-shell crashed with stacktrace

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  gnome-shell crashed with stacktrace

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

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

[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)

[Yousef Saber]

can you please give me details on how to update to mutter v3.29.91?

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

Title:
  Login screen never appears on early generation Intel GPUs (Core2 and
  Atom etc)

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

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

[Bug 1783571] Re: Set Yaru as default

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-session/+git/gnome-session/+merge/353283

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

Title:
  Set Yaru as default

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

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

[Bug 1785764] Re: Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated)

[Daniel van Vugt]

On the other hand, maybe we need to treat disabling the default colour
profile as a workaround.

I forgot to mention that in at least one case I noticed similar problems
in web browsers and image viewers even when using a properly custom
calibrated profile for my display.

So a real fix might have to come in the apps themselves, or maybe just
one or two image decoding libraries that are misinterpreting the profile
data (maybe they don't know or expect the whole compositor is applying
the profile already?). To do this someone would need to dig into the
code of an affected app and see how/where it is using the colour profile
data.

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

Title:
  Ubuntu default colour profile distorts colours on some machines (white
  looks green, too dark, or under-saturated)

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr("assertion failed: (icon_info_get_pixbuf_ready (icon_info)

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr() from 
gtk_icon_info_load_icon_finish()
+ gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr("assertion failed: 
(icon_info_get_pixbuf_ready (icon_info))") from gtk_icon_info_load_icon_finish()

** Summary changed:

- gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr("assertion failed: 
(icon_info_get_pixbuf_ready (icon_info))") from gtk_icon_info_load_icon_finish()
+ gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr() from 
gtk_icon_info_load_icon_finish() ["assertion failed: 
(icon_info_get_pixbuf_ready (icon_info))"]

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

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

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

[Bug 1787401] Re: [cosmic] app icons in GNOME Shell top bar are symbolic instead of full-color

[Launchpad Bug Tracker]

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

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

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

Title:
  [cosmic] app icons in GNOME Shell top bar are symbolic instead of
  full-color

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

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

[Bug 1787401] Re: [cosmic] app icons in GNOME Shell top bar are symbolic instead of full-color

[Daniel van Vugt]

Like you, I prefer the monochrome icons but do wonder if it's
intentional...

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

Title:
  [cosmic] app icons in GNOME Shell top bar are symbolic instead of
  full-color

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

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

[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

[Daniel van Vugt]

Tip: You might find removing gnome-shell extensions stops the crashes
from happening :)

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

Title:
  gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

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

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

[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

[Daniel van Vugt]

The terminal window in which you ran ubuntu-bug will tell you the bug
ID. If you've lost that then try looking at
https://errors.ubuntu.com/user/ID where ID is the contents of
/var/lib/whoopsie/whoopsie-id

That all said, your previous_boot.log mentions:

aug 15 23:38:55 poema whoopsie[5963]: [23:38:55] Parsing 
/var/crash/_usr_bin_gnome-shell.1000.crash.
aug 15 23:38:55 poema whoopsie[5963]: [23:38:55] Uploading 
/var/crash/_usr_bin_gnome-shell.1000.crash.
aug 15 23:38:56 poema whoopsie[5963]: [23:38:56] Sent; server replied with: No 
error
aug 15 23:38:56 poema whoopsie[5963]: [23:38:56] Response code: 200
aug 15 23:38:56 poema whoopsie[5963]: [23:38:56] Reported OOPS ID 
9c43cbd2-a0d3-11e8-a8b5-fa163e192766

which I have now tracked down on our servers... It is bug 1787512.

Next, please:

 1. Delete all the files in /var/crash. 
 2. Wait for the problem to happen again and report the gnome-shell crash again 
(hopefully).
 3. Tell us if you get directed to that same bug repeatedly, or if you can't 
tell then attach another 'journalctl -b-1' log.

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

Title:
  gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

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

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

[Bug 1722599] Re: gnome-shell crash on search specific app [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed: (icon_info_get_pixbuf_ready (icon_info))]

[Daniel van Vugt]

It appears this crash stopped happening after 17.10.

However we're getting similar reports in newer releases, now tracking in
bug 1787512 instead.

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

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

Title:
  gnome-shell crash on search specific app
  [gtkicontheme.c:4258:gtk_icon_info_load_icon_finish: assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))]

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

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

[Bug 1787512] [NEW] gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.28.2-0ubuntu0.18.04.1, the problem page at 
https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic kylin-17.10

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish()

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

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

[Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()

[Daniel van Vugt]

Looks like the new form of old bug 1722599.

** Summary changed:

- 
/usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:gtk_icon_info_load_icon_finish
+ gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from 
g_assertion_message() from g_assertion_message_expr() from 
gtk_icon_info_load_icon_finish()

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish()

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

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

[Bug 1787193] Re: copying via Nautilus over the lan is very slow

[Daniel van Vugt]

** Tags added: performance

** Tags added: bionic

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

Title:
  copying via Nautilus over the lan is very slow

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

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

[Bug 1785764] Re: Some applications render too dark when a 4K screen is attached.

[Daniel van Vugt]

Great!

I checked and it was only a year ago that the rest of us noticed the
problem and found a solution (including Matthew Paul Thomas, Robert
Ancell and myself).

If the problem is still occurring in 18.04 then we need to do something
about it. That something is to ensure Ubuntu ships with NO ACTIVE colour
profile, which has been the fix for all of us so far...


** Tags added: bionic

** Summary changed:

- Some applications render too dark when a 4K screen is attached.
+ Ubuntu default colour profile distorts colours on some machines (white looks 
green, too dark, or under-saturated)

** Package changed: ubuntu => colord (Ubuntu)

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

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => 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/1785764

Title:
  Ubuntu default colour profile distorts colours on some machines (white
  looks green, too dark, or under-saturated)

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

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

[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

[Daniel van Vugt]

** Package changed: mutter (Ubuntu) => gtk+3.0 (Ubuntu)

** No longer affects: ubuntu-themes (Ubuntu)

** Summary changed:

- gedit and gnome-calculator transparency/graphics corruption issue
+ gedit and gnome-calculator transparency/graphics corruption issue when 
GTK_IM_MODULE=xim is set

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue when
  GTK_IM_MODULE=xim is set

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+subscriptions

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

[Bug 1725836] Re: No more than 2 displays work simultaneously

[Daniel van Vugt]

Going back to your JournalErrors.txt:

Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
Page flip failed: Invalid argument
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): 
present flip failed
Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): 
flip queue failed: Invalid argument

I would like to verify if those errors correlate with the problem. Can
you please run:

  journalctl -f

and see if those errors only occur when trying to drive 3 monitors?

Do the errors go away when only 2 monitors are plugged in?

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

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1725836] Re: No more than 2 displays work simultaneously

[Daniel van Vugt]

Separately, please also try clicking the cog wheel button on the login
screen and selecting:

  Ubuntu on Wayland

Does that fix it?

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

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

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1725836] Re: No more than 2 displays work simultaneously

[Daniel van Vugt]

GPUs:

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Curacao PRO [Radeon R7 370 / R9 270/370 OEM] (rev 81)
Subsystem: Tul Corporation / PowerColor Curacao PRO [Radeon R7 370 / R9
270/370 OEM]
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 mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1725836

Title:
  No more than 2 displays work simultaneously

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

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

[Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing

[Erick Brunzell]

It seems to me that the most sensible approach would be to just remove
the Computer button from the Places menu. Then you'd just open Home and
select Other Locations. I think that would be more in keeping with the
latest Nautilus redesign.

I'm not at all sure but we may want to do likewise with the Network
button in the Places menu because it's now also accessible via Home ->
Other Locations.

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

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

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

[Bug 1737836] Re: Standard clock applet is oversized in Artful

[Erick Brunzell]

Sorry to take so long getting back to this. Disabling "show weather" and
"show temp" helps reduce that dead space but it must be done after each
boot or reboot because the settings don't "stick".

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

Title:
  Standard clock applet is oversized in Artful

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

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

[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.178ubuntu2.6

---
console-setup (1.178ubuntu2.6) bionic; urgency=medium

  * keyboard-configuration.config: Only treat missing XKBOPTIONS as
empty.

console-setup (1.178ubuntu2.5) bionic; urgency=medium

  * keyboard-configuration.config: While sourcing config files to re-seed
debconf, load missing variables as empty values of same (LP: #1762952)

console-setup (1.178ubuntu2.4) bionic; urgency=medium

  * keyboard-configuration.{config,templates}: There is no good default for
layout toggling, stop pretending there is.  Console users can set one
with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)

 -- Adam Conrad   Wed, 08 Aug 2018 17:32:23 -0600

** Changed in: console-setup (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Alternative shortcut for layout switching Alt+Shift unexpectedly set
  by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions

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

[Bug 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue

[linex83]

I experienced this bug today. Restart didn't help initially. Then I
changed the Input Method from xim to ibus and the problem was gone.
Changing back to xim did not bring the problem back. I'm confused that
it worked. Would be nice if somebody else could try the same.

I did not install any new packages, neither did I re-install any
packages.

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

Title:
  gedit and gnome-calculator transparency/graphics corruption issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+subscriptions

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

[Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

[Jeremy Bicha]

Oh maybe this is just incompatibility with the new glib. There was a new
pygobject release today.

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

Title:
  pygobject fails to build in Ubuntu 18.10

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

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

[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

[Damiön la Bagh]

The name of the crash file is

_usr_bin_gnome-shell.1000.crash

I uploaded it with ubuntu-bug
How do I see the bug number it created?

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

Title:
  gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

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

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

[Bug 1787277] Re: gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

[Damiön la Bagh]

Here is a copy of journalctl -b-1 > Previous_Boot.log


** Attachment added: "Previous Boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1787277/+attachment/5176514/+files/previous_boot.log

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

Title:
  gdm3 freezes then locks out user after upgrade from 16.04 to 18.04

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

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

[Bug 1787474] [NEW] pygobject fails to build in Ubuntu 18.10

[Jeremy Bicha]

Public bug reported:

pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS. 3.29.2-1
does build successfully in Debian unstable.

I confirmed that the problem is reproducible in a local sbuild. I
confirm that the test hang also happens with python 3.7.

By the way, I had to manually cancel the builds since they were still
hanging after 20 hours.

Build log
-
https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

Build log excerpt
-

I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; python2.7 
-m pytest tests
= test session starts ==
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
rootdir: /<>, inifile:
collected 1374 items

tests/test_atoms.py ...  [  0%]
tests/test_cairo.py .[  2%]
tests/test_docstring.py ...x.[  3%]
tests/test_error.py ...  [  4%]
tests/test_everything.py Trace/breakpoint trap (core dumped)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
Scanning for processes to kill in build PACKAGEBUILD-15263898
Build killed with signal TERM after 150 minutes of inactivity

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


** Tags: cosmic ftbfs

** Description changed:

  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.
  
  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS. 3.29.2-1
  does build successfully in Debian unstable.
  
  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.
  
  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.
  
+ Build log
+ -
+ https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898
+ 
  Build log excerpt
  -
- 
  
  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items
  
  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

Title:
  pygobject fails to build in Ubuntu 18.10

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

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

[Bug 1698351] Re: Search in Nautilus Files does not allow sorting of results

[Damiön la Bagh]

Example of search query that Nautilus refuses to sort.

** Attachment added: "Example of where nautilus is not sorting"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+attachment/5176511/+files/Selectie_012.png

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

Title:
  Search in Nautilus Files does not allow sorting of results

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

[Colin Law]

@Darius this bug is about the Software & Updates app, which is the one
that controls sources.list etc.  The bug is that it does not popup the
Authorization dialog.  It seems to be in no way related to your issue.

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

Title:
  After upgrade to ubuntu 17.10 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/+bug/1734095/+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]

[Dariusz Deoniziak]

I have the same problem since 17.10, running currently 18.04.
Reinstalling gnome-software did not help.

gnome-software does not show apt updates at all. I have to update system
using apt from terminal or update-manager

Found similar issue in debian mailinglist, but related only to empty
updates list: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851796

Adding attachment file with gnome-software running with --verbose
command, 9581 is the line where I've typed in other terminal: "sudo apt
update".

** Bug watch added: Debian Bug tracker #851796
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851796

** Attachment added: "verbose_gnome-software"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734095/+attachment/5176480/+files/verbose_gnome-software

-- 
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:
  After upgrade to ubuntu 17.10 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/+bug/1734095/+subscriptions

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

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

Here are three photos that might help.


I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
keyboard will not be active


1  - img_2008.jpg Showing all three terminals plugged in


2. img 2010 showing display screen (All displays appear to be available.


3. img-2011.jpg


As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears


Hope this is of some help


I will have to send the photos seperately


On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
> Peter
>
>
>
> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
> wrote:
>
>> 1... Output of xrandr and lspci
>>
>>  xrandr
>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>> axis) 477mm x 268mm
>>1920x1080 60.00*+  60.0050.0059.94
>>1920x1080i60.0050.0059.94
>>1680x1050 59.88
>>1600x900  60.00
>>1280x1024 75.0260.02
>>1280x960  60.00
>>1280x800  59.91
>>1152x864  75.00
>>1280x720  60.0050.0059.94
>>1024x768  75.0360.00
>>1024x576  59.97
>>832x624   74.55
>>800x600   75.0060.32
>>720x576   50.00
>>720x576i  50.00
>>720x480   60.0059.94
>>720x480i  60.0059.94
>>640x480   75.0060.0059.94
>>720x400   70.08
>> DVI-0 disconnected (normal left inverted right x axis y axis)
>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>> y axis) 477mm x 268mm
>>1920x1080 60.00*+
>>1280x1024 75.0260.02
>>1152x864  75.00
>>1024x768  75.0360.00
>>800x600   75.0060.32
>>640x480   75.0059.94
>>720x400   70.08
>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>
>>
>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>> Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>> Controller
>> Kernel driver in use: hsw_uncore
>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor PCI Express x16 Controller (rev 06)
>> Kernel driver in use: pcieport
>> Kernel modules: shpchp
>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>> Gen Core Processor Integrated Graphics Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>> Processor Integrated Graphics Controller
>> Kernel driver in use: i915
>> Kernel modules: i915
>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor HD Audio Controller (rev 06)
>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>> Audio Controller
>> Kernel driver in use: snd_hda_intel
>> Kernel modules: snd_hda_intel
>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>> Core Processor DRAM Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>> Controller
>> Kernel driver in use: hsw_uncore
>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor PCI Express x16 Controller (rev 06)
>> Kernel driver in use: pcieport
>> Kernel modules: shpchp
>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>> Gen Core Processor Integrated Graphics Controller (rev 06)
>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>> Processor Integrated Graphics Controller
>> Kernel driver in use: i915
>> Kernel modules: i915
>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>> Processor HD Audio Controller (rev 06)
>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>> Audio Controller
>> Kernel driver in use: snd_hda_intel
>> Kernel modules: snd_hda_intel
>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>> Family USB xHCI (rev 05)
>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>> Family USB xHCI
>> Kernel driver in use: xhci_hcd
>> 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
>> Chipset Family MEI Controller #1 (rev 04)
>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>> Family MEI Controller
>> Kernel driver in use: mei_me
>> Kernel modules: 

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
>
> I will have to send the photos seperately
>
>
> On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
> wrote:
>
>> Here are three photos that might help.
>>
>>
>> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
>> keyboard will not be active
>>
>>
>> 1  - img_2008.jpg Showing all three terminals plugged in
>>
>>
>> 2. img 2010 showing display screen (All displays appear to be available.
>>
>>
>> 3. img-2011.jpg
>>
>>
>> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>>
>>
>> Hope this is of some help
>>
>> Peter
>>
>>
>>
>> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
>> wrote:
>>
>>> 1... Output of xrandr and lspci
>>>
>>>  xrandr
>>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>>> axis) 477mm x 268mm
>>>1920x1080 60.00*+  60.0050.0059.94
>>>1920x1080i60.0050.0059.94
>>>1680x1050 59.88
>>>1600x900  60.00
>>>1280x1024 75.0260.02
>>>1280x960  60.00
>>>1280x800  59.91
>>>1152x864  75.00
>>>1280x720  60.0050.0059.94
>>>1024x768  75.0360.00
>>>1024x576  59.97
>>>832x624   74.55
>>>800x600   75.0060.32
>>>720x576   50.00
>>>720x576i  50.00
>>>720x480   60.0059.94
>>>720x480i  60.0059.94
>>>640x480   75.0060.0059.94
>>>720x400   70.08
>>> DVI-0 disconnected (normal left inverted right x axis y axis)
>>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>>> y axis) 477mm x 268mm
>>>1920x1080 60.00*+
>>>1280x1024 75.0260.02
>>>1152x864  75.00
>>>1024x768  75.0360.00
>>>800x600   75.0060.32
>>>640x480   75.0059.94
>>>720x400   70.08
>>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>>
>>>
>>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>>> Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>>> Core Processor DRAM Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>>> Family USB xHCI (rev 05)
>>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>>> Family USB xHCI
>>> Kernel driver in use: xhci_hcd
>>> 00:16.0 Communication controller: Intel Corporation 8 

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

On Thu, Aug 16, 2018 at 11:27 AM Peter Wallbridge 
wrote:

> Here are three photos that might help.
>
>
> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
> keyboard will not be active
>
>
> 1  - img_2008.jpg Showing all three terminals plugged in
>
>
> 2. img 2010 showing display screen (All displays appear to be available.
>
>
> 3. img-2011.jpg
>
>
> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>
>
> Hope this is of some help
>
>
> I will have to send the photos seperately
>
>
> On Thu, Aug 16, 2018 at 11:20 AM Peter Wallbridge 
> wrote:
>
>> Here are three photos that might help.
>>
>>
>> I cannot leave all 3 plgged in. Onl;y 2 will show on the boot, but the
>> keyboard will not be active
>>
>>
>> 1  - img_2008.jpg Showing all three terminals plugged in
>>
>>
>> 2. img 2010 showing display screen (All displays appear to be available.
>>
>>
>> 3. img-2011.jpg
>>
>>
>> As soon as I enable screen 3, screen 1 disappears and screen 2 3 appears
>>
>>
>> Hope this is of some help
>>
>> Peter
>>
>>
>>
>> On Thu, Aug 16, 2018 at 7:07 AM Peter Wallbridge 
>> wrote:
>>
>>> 1... Output of xrandr and lspci
>>>
>>>  xrandr
>>> Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
>>> DisplayPort-0 disconnected (normal left inverted right x axis y axis)
>>> HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
>>> axis) 477mm x 268mm
>>>1920x1080 60.00*+  60.0050.0059.94
>>>1920x1080i60.0050.0059.94
>>>1680x1050 59.88
>>>1600x900  60.00
>>>1280x1024 75.0260.02
>>>1280x960  60.00
>>>1280x800  59.91
>>>1152x864  75.00
>>>1280x720  60.0050.0059.94
>>>1024x768  75.0360.00
>>>1024x576  59.97
>>>832x624   74.55
>>>800x600   75.0060.32
>>>720x576   50.00
>>>720x576i  50.00
>>>720x480   60.0059.94
>>>720x480i  60.0059.94
>>>640x480   75.0060.0059.94
>>>720x400   70.08
>>> DVI-0 disconnected (normal left inverted right x axis y axis)
>>> DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis
>>> y axis) 477mm x 268mm
>>>1920x1080 60.00*+
>>>1280x1024 75.0260.02
>>>1152x864  75.00
>>>1024x768  75.0360.00
>>>800x600   75.0060.32
>>>640x480   75.0059.94
>>>720x400   70.08
>>> VGA-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-1 disconnected (normal left inverted right x axis y axis)
>>> HDMI-1-2 disconnected (normal left inverted right x axis y axis)
>>>
>>>
>>> 00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
>>> Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
>>> Core Processor DRAM Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
>>> Controller
>>> Kernel driver in use: hsw_uncore
>>> 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor PCI Express x16 Controller (rev 06)
>>> Kernel driver in use: pcieport
>>> Kernel modules: shpchp
>>> 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
>>> Gen Core Processor Integrated Graphics Controller (rev 06)
>>> Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
>>> Processor Integrated Graphics Controller
>>> Kernel driver in use: i915
>>> Kernel modules: i915
>>> 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
>>> Processor HD Audio Controller (rev 06)
>>> Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
>>> Audio Controller
>>> Kernel driver in use: snd_hda_intel
>>> Kernel modules: snd_hda_intel
>>> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
>>> Family USB xHCI (rev 05)
>>> Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset
>>> Family USB xHCI
>>> Kernel driver in use: xhci_hcd
>>> 00:16.0 Communication controller: Intel Corporation 8 

[Bug 1787401] Re: [cosmic] app icons in GNOME Shell top bar are symbolic instead of full-color

[Jeremy Bicha]

** Summary changed:

- [cosmic] app icons in GNOME Shell are symbolic instead of full-color
+ [cosmic] app icons in GNOME Shell top bar are symbolic instead of full-color

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

Title:
  [cosmic] app icons in GNOME Shell top bar are symbolic instead of
  full-color

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

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

[Bug 1787418] Re: gimp crashed whilst playing with photo filters

[Chris Guiver]

this is the journalctl-a  (with all lines before last "-- Reboot --"
removed (so as to shrink file)

** Attachment added: "journalctl -a >journalctl-a.2018-06-16.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1787418/+attachment/5176373/+files/journalctl-a.2018-08-16.txt

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

Title:
  gimp crashed whilst playing with photo filters

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

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

[Bug 1785834] Re: Screen randomly turns black minutes after successfully login with GDM

[Eduardo Medina]

OK. I will try to reproduce the error.

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

Title:
  Screen randomly turns black minutes after successfully login with GDM

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

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

[Bug 1780442] Re: Please backport fix for & in attributes

[Mario Limonciello]

Per discussion upstream there is a commit needed for fwupd as well to
make it not abort on the bad data.  So the appstream-glib tasks should
get a verification-done tag and flow through, but we also need to SRU
fwupd with this commit:
https://github.com/hughsie/fwupd/commit/fe1c4de5a4b178cae3e4e9325ea84ff85c4b1be3

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

** Changed in: fwupd (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please backport fix for & in attributes

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

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

[Bug 1787418] [NEW] gimp crashed whilst playing with photo filters

[Chris Guiver]

Public bug reported:

Photo i took with digital camera I resized to 1920x1080 for screen
wallpaper, no issues.

I however wasn't happy with result (as wallpaper), so was playing with
different filters (from top of list down to bottom, undo after each) to
see if it created a better image & crash...

I don't recall which option i was up to, but was ~70% down list of
filters...

Ubuntu 18.10

i haven't retried,  will try it again tomorrow (though unlikely to re-
try same keystrokes). I was trying everything that I felt may help hide
the imperfectly focused photo shortcomings..

I can provide photo original, plus save file I was working from.

No files dated today in /var/crash/

I also have saved `dmesg` & `journalctl -a` so can provide if beneficial
-rw-r--r--   1 rootroot   127K Aug 17 00:16 dmesg_2018-08-16.txt
-rw-r--r--   1 rootroot   288M Aug 17 00:28 journalctl-a.2018-08-16.txt
crash occurred before 1900 (7pm), but I felt I didn't have time to report 
before I left for dinner, so am reporting now hours later (system was slept 
~7pm until I returned home..)

-- pasted BUG Information follows --

GNU Image Manipulation Program version 2.10.2
git-describe: GIMP_2_10_0-292-gbe7f9b433a
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.3.0-19ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-19ubuntu2) 

using GEGL version 0.4.2 (compiled against version 0.4.2)
using GLib version 2.57.2 (compiled against version 2.56.1)
using GdkPixbuf version 2.36.12 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.1 (compiled against version 1.42.1)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)

> fatal error: Aborted

Stack trace:

# Stack traces obtained from PID 2444 - Thread 2444 #

[New LWP 2448]
[New LWP 2449]
[New LWP 2450]
[New LWP 2451]
[New LWP 2452]
[New LWP 2453]
[New LWP 2492]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f36fde8f384 in __libc_read (fd=23, buf=0x7ffcd3afc7d0, nbytes=256) at 
../sysdeps/unix/sysv/linux/read.c:27
  Id   Target Id Frame 
* 1Thread 0x7f36f973ee00 (LWP 2444) "gimp-2.10" 0x7f36fde8f384 in 
__libc_read (fd=23, buf=0x7ffcd3afc7d0, nbytes=256) at 
../sysdeps/unix/sysv/linux/read.c:27
  2Thread 0x7f36f5d75700 (LWP 2448) "gmain" 0x7f36fdba1bf9 in 
__GI___poll (fds=0x563610991f10, nfds=2, timeout=3997) at 
../sysdeps/unix/sysv/linux/poll.c:29
  3Thread 0x7f36f5574700 (LWP 2449) "gdbus" 0x7f36fdba1bf9 in 
__GI___poll (fds=0x563610969e10, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7f36d87b8700 (LWP 2450) "async" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f36d7fb7700 (LWP 2451) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f36d77b6700 (LWP 2452) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f36d6fb5700 (LWP 2453) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f36cfbff700 (LWP 2492) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7f36cfbff700 (LWP 2492)):
#0  0x7f36fdba8839 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7f36fe4cf51f in g_cond_wait () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f36ff2541e9 in  () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3  0x7f36fe4b1105 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f36fde856db in start_thread 

[Bug 1787302] Re: nautilus crashed with SIGSEGV in nautilus_directory_add_file_to_work_queue() from nautilus_file_invalidate_attributes() from g_closure_invoke() from signal_emit_unlocked_R() from g_s

[Brian Murray]

** Also affects: nautilus (Ubuntu Xenial)
   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/1787302

Title:
  nautilus crashed with SIGSEGV in
  nautilus_directory_add_file_to_work_queue() from
  nautilus_file_invalidate_attributes() from g_closure_invoke() from
  signal_emit_unlocked_R() from g_signal_emit_valist()

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

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

[Bug 1787193] Re: copying via Nautilus over the lan is very slow

[Paul White]

** Package changed: ubuntu => nautilus (Ubuntu)

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

Title:
  copying via Nautilus over the lan is very slow

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

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

[Bug 1787401] [NEW] [cosmic] app icons in GNOME Shell are symbolic instead of full-color

[Jeremy Bicha]

Public bug reported:

GNOME Shell uses monochrome symbolic icons in the left side of the top
bar.

The default Ubuntu session in Ubuntu 18.04 LTS overrides that to use
full-color app icons instead.

In 18.10, the Ubuntu session is showing symbolic app icons there instead
of full-color.

Personally, I prefer the symbolic icons there, but I think this is
unintentional.

gnome-shell 3.29.90-1ubuntu2

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


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

Title:
  [cosmic] app icons in GNOME Shell are symbolic instead of full-color

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

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

[Bug 1787193] [NEW] copying via Nautilus over the lan is very slow

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have two laptops running the standard Ubuntu 18.04 LTS (gnome). The one was 
upgraded from 16.04 LTS, the other is a fresh installation. They are connected 
to my network via cifs.
When copying a specific directory on a mounted volume from my server to the 
laptops using the command line, it takes a few seconds to complete.  But using 
the GUI, it takes in both cases almost 30 minutes!
Doing the test with another laptop running 16.04 LTS (Unity) using the GUI 
showed no differences to using the command line. I did not find any possibility 
to speed up the process in 18.04 LTS.

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


** Tags: bot-comment
-- 
copying via Nautilus over the lan is very slow
https://bugs.launchpad.net/bugs/1787193
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to nautilus in Ubuntu.

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

[Bug 1787378] [NEW] Merge with Debian 3.23.2-1

[Andrea Azzarone]

Public bug reported:

Merge with Debian 3.23.2-1

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress


** Tags: upgrade-software-version

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Wishlist => Medium

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

Title:
  Merge with Debian 3.23.2-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787378/+subscriptions

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

Re: [Bug 1725836] Re: No more than 2 displays work simultaneously

[Peter Wallbridge]

1... Output of xrandr and lspci

 xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y
axis) 477mm x 268mm
   1920x1080 60.00*+  60.0050.0059.94
   1920x1080i60.0050.0059.94
   1680x1050 59.88
   1600x900  60.00
   1280x1024 75.0260.02
   1280x960  60.00
   1280x800  59.91
   1152x864  75.00
   1280x720  60.0050.0059.94
   1024x768  75.0360.00
   1024x576  59.97
   832x624   74.55
   800x600   75.0060.32
   720x576   50.00
   720x576i  50.00
   720x480   60.0059.94
   720x480i  60.0059.94
   640x480   75.0060.0059.94
   720x400   70.08
DVI-0 disconnected (normal left inverted right x axis y axis)
DVI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 477mm x 268mm
   1920x1080 60.00*+
   1280x1024 75.0260.02
   1152x864  75.00
   1024x768  75.0360.00
   800x600   75.0060.32
   640x480   75.0059.94
   720x400   70.08
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)


00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM
Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
Controller
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: I00:00.0 Host bridge: Intel Corporation 4th Gen
Core Processor DRAM Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
Controller
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor PCI Express x16 Controller (rev 06)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th
Gen Core Processor Integrated Graphics Controller (rev 06)
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core
Processor Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller (rev 06)
Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD
Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB xHCI
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V
(rev 05)
Subsystem: Gigabyte Technology Co., Ltd Ethernet Connection I217-V
Kernel driver in use: e1000e
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #2 (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB EHCI
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset High
Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #1 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family
PCI Express Root Port #4 (rev d5)
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #1 (rev 05)
Subsystem: Gigabyte Technology Co., Ltd 8 Series/C220 Series Chipset Family
USB EHCI
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation B85 

[Bug 1787362] Re: gnome-shell UI unresponsive

[Daniel van Vugt]

1. Please try removing all extensions you have installed. Gnome Shell
extensions are a major cause of bugs.

2. Do you find that it's only clicking on app windows that is affected?
When the problem happens can you still click on the shell panel/docks?

3. Is the problem confined to only Wayland sessions, or only Xorg
sessions? Does it occur in both?


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

Title:
  gnome-shell UI unresponsive

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1787362] Re: gnome-shell UI unresponsive

[Daniel van Vugt]

** Summary changed:

- gnome-shell crash, UI unresponsive
+ gnome-shell UI unresponsive

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Tags added: no-click

** Tags removed: no-click
** Tags added: noclick

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

Title:
  gnome-shell UI unresponsive

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

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

[Bug 1787362] [NEW] gnome-shell UI unresponsive

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Whilst working normally, I was unable to interact with gnome-shell.  The
clock at the top of the screen continued to increment, and I could ssh
in to the machine, but clicking anywhere on the screen resulted in
nothing.  Changing to another VTY and back again had no effect.

I logged in via ssh, killed gnome-shell and re-ran it using
'DISPLAY=:0.0 gnome-shell' which resolved the problem enough for me to
save work and reboot.

The following appeared in syslog - the crash was possibly around 1001:

Aug 16 10:02:17 angel gnome-shell[2530]: pushModal: invocation of begin_modal 
failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:45 angel gnome-shell[2530]: message repeated 2 times: [ 
g_array_unref: assertion 'array' failed]
Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has 
been already finalized. Impossible to set any property to it.
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has 
been already finalized. Impossible to set any property to it.
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 
0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i   
resource:///org/gnome/shell/ui/userWidget.js:59 (0x7f1d3c555b38 @ 212)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i   
resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 
59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i   
self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 
0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i   
resource:///org/gnome/shell/ui/userWidget.js:60 (0x7f1d3c555b38 @ 274)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i   
resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 
59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i   
self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 
0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i   
resource:///org/gnome/shell/ui/userWidget.js:65 (0x7f1d3c555b38 @ 365)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i   
resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 
59)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i   
self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 
0x55efd9792340 ==
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb4178 i   
resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7f1cc1869ab0 @ 
84)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb40d0 i   
resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71)
Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4010 i   
self-hosted:915 (0x7f1d5c0f12b8 @ 367)
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has 
been already deallocated - impossible to access to it. This might be caused by 
the fact that the object has been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs
Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has 
been already deallocated - impossible to access to it. This might be caused by 
the fact that the object has been destroyed from C code using something such as 
destroy(), 

[Bug 1787124] Re: Update to 3.29.90

[Sebastien Bacher]

Uploaded to Debian

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

Title:
  Update to 3.29.90

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

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

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[ubname]

just to give some feedback, I have a optimus laptop with i7 sandibridge
and nvidia GT550M, there is a led that indicates the nvidia GPU is
always in use also after using the ppa to test, the laptop is indeed
very hot also after I select intel and reboot and the led indicates that
the nvidia GPU is in use despite selecting intel.

thanks!

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

Title:
  SRU: PRIME Power Saving mode draws too much power

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

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

[Bug 1717458] Re: Panel flickers when scrubbing across in-window menus

[Daniel van Vugt]

Confirmed again in 18.10.

** Tags added: bionic cosmic

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

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

Title:
  Panel flickers when scrubbing across in-window menus

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

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

[Bug 1747910] Re: Crashes on DP hotplug (wl_registry@2: error 0: invalid global wl_output (29))

[Daniel van Vugt]

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

** This bug is no longer a duplicate of bug 1746656
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: 
invalid arguments for 
zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"]

** This bug has been marked a duplicate of bug 1745799
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: 
invalid global wl_output (20)\n"]

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

Title:
  Crashes on DP hotplug (wl_registry@2: error 0: invalid global
  wl_output (29))

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

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

[Bug 1787325] [NEW] Update wayland-protocols to version 1.16

[Daniel van Vugt]

Public bug reported:

Update wayland-protocols to version 1.16

The upstream mutter (v3.29.91) code now requires this version.

https://github.com/wayland-project/wayland-protocols/releases/tag/1.16

** Affects: wayland-protocols (Ubuntu)
 Importance: High
 Status: New


** Tags: cosmic upgrade-software-version

** Tags added: cosmic

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

Title:
  Update wayland-protocols to version 1.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland-protocols/+bug/1787325/+subscriptions

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