[Bug 1832946] Re: Gnome Shell performance decreases as the number of running apps increases

2019-06-16 Thread Daniel van Vugt
Note that not all performance improvements will ever make it into Ubuntu
18.04.

If you want higher performance right now then please use Ubuntu 19.04
instead. And Ubuntu 19.10 will be even faster (_after_ it gets mutter
3.33.3 or later).

Do you find that Ubuntu 19.04 has this same bug?

** Summary changed:

- Gnome Shell works the worst after I will  launch some apps
+ Gnome Shell performance decreases as the number of running apps increases

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

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

Title:
  Gnome Shell performance decreases as the number of running apps
  increases

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

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

Re: [Bug 1832946] Re: Gnome Shell works the worst after I will launch some apps

2019-06-16 Thread Artyom Pozharov
May be you can't see this sad picture. After I launch a few huge apps
animation will freeze, button press response is very slow. I can say that
Unity shell on this PC is more performance and doesn't have such problems.

пн, 17 июн. 2019 г., 5:30 Daniel van Vugt
:

> It sounds like you're trying to describe general frame skipping and
> performance degradation as more apps are opened. Can you please put the
> problem into words so we can be sure what the problem is you are
> reporting?
>
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> ** Tags added: performance
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1832946
>
> Title:
>   Gnome Shell works the worst after I will  launch some apps
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   You should watch my video: https://photos.app.goo.gl/1TY6YWcw1UZEwKfNA
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gnome-shell 3.28.4-0ubuntu18.04.1
>   ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
>   Uname: Linux 4.18.0-21-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Jun 15 18:50:37 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'command-history' redacted by apport
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>   InstallationDate: Installed on 2019-06-14 (1 days ago)
>   InstallationMedia:
>
>   ProcEnviron:
>LANGUAGE=ru_UA:ru
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ru_UA.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832946/+subscriptions
>

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

Title:
  Gnome Shell works the worst after I will  launch some apps

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

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

[Bug 1832988] Re: Intel 8260 Bluetooth not working

2019-06-16 Thread Kai-Heng Feng
Please test this kernel:
https://people.canonical.com/~khfeng/lp1832988/

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

Title:
  Intel 8260 Bluetooth not working

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

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

[Bug 1825066] Re: gsd-xsettings have tons of error in syslog

2019-06-16 Thread Launchpad Bug Tracker
[Expired for gnome-settings-daemon (Ubuntu) because there has been no
activity for 60 days.]

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

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

Title:
  gsd-xsettings have tons of error in syslog

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

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

[Bug 1825006] Re: snapp apps not showing in software center

2019-06-16 Thread Launchpad Bug Tracker
[Expired for gnome-software (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  snapp apps not showing in software center

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Eric Desrochers
** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Eric Desrochers (slashd)

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

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

[Bug 1806697] Re: Status of interface connections not properly updated in the UI

2019-06-16 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-software - 3.30.6-2ubuntu8

---
gnome-software (3.30.6-2ubuntu8) eoan; urgency=medium

  * debian/patches/0014-Add-a-basic-permissions-system.patch:
- Fix interface connections not showing correct state (LP: #1806697)

 -- Robert Ancell   Mon, 17 Jun 2019
14:55:38 +1200

** Changed in: gnome-software (Ubuntu Eoan)
   Status: Triaged => Fix Released

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

Title:
  Status of interface connections not properly updated in the UI

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

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

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
The attached RfKill.txt seems to suggest that Bluetooth is only turned
off in software. So maybe this is just a gnome-shell GUI bug, or gnome-
bluetooth.

To confirm this, please try turning it on by running this command in a
terminal:

  rfkill unblock 0


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

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

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

** Changed in: gnome-bluetooth (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/1832988

Title:
  Intel 8260 Bluetooth not working

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

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

[Bug 1832988] Re: Bluetooth not working

2019-06-16 Thread Daniel van Vugt
If the above command doesn't work then I would next focus on a possible
kernel problem in:

[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)

** Summary changed:

- Bluetooth not working
+ Intel 8260 Bluetooth not working

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

Title:
  Intel 8260 Bluetooth not working

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it

2019-06-16 Thread Daniel van Vugt
Pat,

Re comment #19, your crash (hang) reports there seem to show the gnome-
shell process behaving normally (in poll) and not stuck at all. That
doesn't tell us much but it would support the theory in comment #31.

** Summary changed:

- Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or 
using WaylandEnable=false) fixes it

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 (or using WaylandEnable=false) fixes it

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes it

2019-06-16 Thread Daniel van Vugt
Interesting one of the commits mentioned above:

  37efe80ce85f drm/vmwgfx: use monotonic event timestamps
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5&id=37efe80ce85f)

is related to what I changed in the latest update to mutter:

  https://gitlab.gnome.org/GNOME/mutter/commit/e9e4b2b72

The latest update to mutter requires monotonic event timestamps in the
kernel driver in order to work properly. It should kind of work without
them, but that fallback is untested...

So if that is the problem then you might find reverting to the previous
mutter version also works around the issue(?). You can download the
debs:

https://launchpad.net/ubuntu/+source/mutter/3.28.3+git20190124-0ubuntu18.04.2/+build/16644915

and then try installing them together:

  dpkg -i *.deb



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

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

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

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

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

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

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

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

2019-06-16 Thread Daniel van Vugt
Indeed there was a kernel update to 18.04 around the same time as the
mutter update which I thought was causing this bug.

** No longer affects: mutter (Ubuntu)

** No longer affects: mutter (Ubuntu Bionic)

** No longer affects: mutter (Ubuntu Eoan)

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

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

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

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

** Summary changed:

- Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it
+ Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 fixes 
it

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

Title:
  Login screen never appears on vmwgfx but installing kernel >=
  v4.17-rc1 fixes it

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

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

[Bug 1832959] Re: Wrong cursor size after screensaver

2019-06-16 Thread Daniel van Vugt
** Tags added: cursor hidpi

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Wrong cursor size after screensaver
+ [hidpi] Cursor is too small after screensaver

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

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

Title:
  [hidpi] Cursor is too small after screensaver

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

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

[Bug 1832946] Re: Gnome Shell works the worst after I will launch some apps

2019-06-16 Thread Daniel van Vugt
It sounds like you're trying to describe general frame skipping and
performance degradation as more apps are opened. Can you please put the
problem into words so we can be sure what the problem is you are
reporting?


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

** Tags added: performance

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

Title:
  Gnome Shell works the worst after I will  launch some apps

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

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

[Bug 1832943] Re: When Firefox is appeared and I open gno-menu, I will see shade of Firefox at background

2019-06-16 Thread Daniel van Vugt
Can you please reword that? I don't understand (and can't see in the
video) what the problem is here.

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

Title:
  When Firefox is appeared and I open gno-menu, I will see shade of
  Firefox at background

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

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

[Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-16 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1800196 ***
https://bugs.launchpad.net/bugs/1800196

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


** This bug has been marked a duplicate of bug 1800196
   spice-vdagent[1345]: Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0

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

Title:
  Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

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

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

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Tags added: regression-update

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

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

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

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
It appears this crash is in:

  /home/gjm/.local/share/gnome-
shell/extensions/wsmat...@martin.zurowietz.de

which is not part of Ubuntu, so we can't handle it here. Sorry.

I suggest you uninstall that extension to avoid the crash.

** Summary changed:

- Gnome-shell crashes frequently
+ Gnome-shell crashes frequently in 
gnome-shell/extensions/wsmat...@martin.zurowietz.de

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

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

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

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

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

[Bug 1832856] Re: Gnome-shell crashes frequently

2019-06-16 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

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

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

Title:
  Gnome-shell crashes frequently in gnome-
  shell/extensions/wsmat...@martin.zurowietz.de

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

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

[Bug 1832812] Re: Locking and unlocking the screen is slow and stuttery

2019-06-16 Thread Daniel van Vugt
Thanks. Since gnome-shell provides all the graphics (even the lock
screen), this bug is now assigned to gnome-shell only.

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

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

** No longer affects: gdm3 (Ubuntu)

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

Title:
  Locking and unlocking the screen is slow and stuttery

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

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

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread 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/1832869

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

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

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

[Bug 1827450] Re: Some context menu entries are unavailable in list view if folder has many items for nautilus 1:3.26.4-0~ubuntu18.04.4

2019-06-16 Thread widon1104
I find a good way to solve this problem in ubuntu18.04: use dde file
manager create by deepin

sudo add-apt-repository ppa:leaeasy/dde
sudo apt install dde dde-file-manager

I think dde-file-manager is better than nautilus.

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

Title:
  Some context menu entries are unavailable in list view if folder has
  many items for nautilus 1:3.26.4-0~ubuntu18.04.4

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

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

[Bug 1832869] Re: gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → ffi_call()

2019-06-16 Thread Daniel van Vugt
** Summary changed:

- gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows 
meta_workspace_list_windows
+ gnome-shell crashed with SIGSEGV in g_hash_table_iter_next → 
meta_display_list_windows → meta_workspace_list_windows → ffi_call_SYSV → 
ffi_call()

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

Title:
  gnome-shell crashed with SIGSEGV in g_hash_table_iter_next →
  meta_display_list_windows → meta_workspace_list_windows →
  ffi_call_SYSV → ffi_call()

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

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

[Bug 1753884] Re: session logout after suspend

2019-06-16 Thread Daniel van Vugt
Unfortunately we can't backport a fix which we don't know the location
of. And I don't see any links to a patch here. Also, we generally don't
support/patch gnome-shell on Ubuntu releases older than 18.04.

Anyway, this bug is closed and we can't be sure you are experiencing the
exact same issue. So please open a new bug.

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

Title:
   session logout after suspend

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

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

[Bug 1722886] Re: Include logs, monitors.xml and org.gnome.desktop.* settings in the apport-retrace data

2019-06-16 Thread Daniel van Vugt
I'm not sure monitors.xml is any more useful than the xrandr output we
already get... unless xrandr output is missing from crash bugs?

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

Title:
  Include logs, monitors.xml and org.gnome.desktop.* settings in the
  apport-retrace data

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

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

[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

2019-06-16 Thread Gregory Orange
Regarding #17 and the bug (issue) report at Seahorse Gitlab, the latest
comment is that Seahorse 3.20.0 which is the latest available on Ubuntu
18.04, is "an ancient version". Can 18.04 receive a newer version such
that upstream can be brought into the issue if it persists with that?

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

Title:
  Seahorse unable to import pkcs12 certificates

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

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

[Bug 1833011] [NEW] rotating a 70MB TGA image

2019-06-16 Thread Kunst Uber Alles
Public bug reported:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--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 --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 8.2.0 (Ubuntu 8.2.0-13ubuntu1) 

using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.60.0 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 9937 - Thread 9938 #

[New LWP 9938]
[New LWP 9939]
[New LWP 9940]
[New LWP 9941]
[New LWP 9942]
[New LWP 9943]
[New LWP 9952]
[New LWP 9953]
[New LWP 9954]
[New LWP 9965]
[New LWP 9966]
[New LWP 13433]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
  Id   Target Id  Frame 
* 1Thread 0x7fbe41884e00 (LWP 9937) "gimp-2.10"   __lll_lock_wait () at 
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
  2Thread 0x7fbe410a7700 (LWP 9938) "worker"  __libc_read (nbytes=256, 
buf=0x7fbe410a5c10, fd=17) at ../sysdeps/unix/sysv/linux/read.c:26
  3Thread 0x7fbe408a6700 (LWP 9939) "worker"  __lll_lock_wait () at 
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
  4Thread 0x7fbe3bfff700 (LWP 9940) "worker"  __lll_lock_wait () at 
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
  5Thread 0x7fbe3a0d7700 (LWP 9941) "gmain"   0x7fbe4356f729 in 
__GI___poll (fds=0x561c660482e0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7fbe398d6700 (LWP 9942) "gdbus"   0x7fbe4356f729 in 
__GI___poll (fds=0x561c6603b2e0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7fbe1e431700 (LWP 9943) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7fbe1dc30700 (LWP 9952) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fbe1d42f700 (LWP 9953) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7fbe17fff700 (LWP 9954) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7fbdfe498700 (LWP 9965) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7fbdfd897700 (LWP 9966) "dashboard"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7fbe1cc2e700 (LWP 13433) "paint"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 13 (Thread 0x7fbe1cc2e700 (LWP 13433)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7fbe438599ff in g_cond_wait () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x561c64164cdd in ?? ()
No symbol table info available.
#3  0x7fbe4383793d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7fbe43654182 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140454503048960, 
8043367585879587281, 140720685929390, 140720685929391, 140720685929536, 
140454503045376, -8006289967426930223, -8006468856880924207}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0,

[Bug 1822380] Re: Thunar right-click menu not expanded

2019-06-16 Thread Theo Linkspfeifer
A workaround is not a proper fix. Would it not make more sense to revert
the GTK commit which broke the menu behavior?

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Thunar right-click menu not expanded

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

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