date:20200115

** Tags added: fixed-in-3.35.4 fixed-upstream

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

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

2020-01-15 Thread karlsebal

I compiled 3.30.1.1 and yet: The same error message—“No compatible
importer found”

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto

Perfect, thanks. It's now conclusive that extensions are not the
problem.

Given the stack trace mentions Wayland subsurfaces I guess you're just
the first to hit this crash.

Next please try avoiding MOZ_ENABLE_WAYLAND=1

Also note that upstream the mutter maintainer has been rewriting the
Wayland subsurfaces code recently. This might mean it's a recent
regression in 3.34.3, or it might mean this issue has already been fixed
in 3.35 (which you can't try yet, sorry).


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

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

** Tags added: wayland

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1009
   https://gitlab.gnome.org/GNOME/mutter/issues/1009

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/1009
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

This does still mean it's a bug in mutter/gnome-shell somewhere, but
probably not one we can realistically reproduce and fix any time soon.
Hopefully the bug stays away with a fresh monitors.xml, or with none at
all.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1859173] Re: [viafb] Display issue

2020-01-15 Thread Alessandro Tiezzi

Il Gio 16 Gen 2020, 02:50 Daniel van Vugt 
ha scritto:

> Sorry. Please run:
>
>   sudo apt install mesa-utils
>   glxinfo > glxinfo.txt
>
> and then attach the resulting file 'glxinfo.txt' here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1859173
>
> Title:
>   [viafb] Display issue
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   i comandi e la barra superiore sbordano, non riesco a visualizzarli
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu12
>   ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
>   Uname: Linux 5.0.0-38-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu27.3
>   Architecture: amd64
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Jan 10 13:12:16 2020
>   DistUpgraded: 2020-01-10 07:57:08,409 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione
> del processo figlio «./xorg_fix_proprietary.py» non riuscita (File o
> directory non esistente) (8))
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   GraphicsCard:
>VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro]
> [1106:3108] (rev 01) (prog-if 00 [VGA controller])
>  Subsystem: ASUSTeK Computer Inc. K8M800/K8N800/K8N800A [S3 UniChrome
> Pro] [1043:8129]
>   InstallationDate: Installed on 2020-01-08 (2 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
> (20181017.3)
>   MachineType: System manufacturer System Product Name
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic
> root=UUID=943bdf0d-bfd4-4e4d-b427-5c0ac904be90 ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to disco on 2020-01-10 (0 days ago)
>   dmi.bios.date: 09/12/2005
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 0203
>   dmi.board.name: K8V-MX
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.chassis.asset.tag: Asset-1234567890
>   dmi.chassis.type: 6
>   dmi.chassis.vendor: Chassis Manufacture
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr0203:bd09/12/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnK8V-MX:rvr:cvnChassisManufacture:ct6:cvrChassisVersion:
>   dmi.product.name: System Product Name
>   dmi.product.version: System Version
>   dmi.sys.vendor: System manufacturer
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20180925-2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859173/+subscriptions
>


** Attachment added: "20200116_080617.jpg"
   
https://bugs.launchpad.net/bugs/1859173/+attachment/5320760/+files/20200116_080617.jpg

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

Title:
  [viafb] Display issue

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i comandi e la barra superiore sbordano, non riesco a visualizzarli

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 10 13:12:16 2020
  DistUpgraded: 2020-01-10 07:57:08,409 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
«./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] [1106:3108] 
(rev 01) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] 
[1043:8129]
  InstallationDate: Installed on 2020-01-08 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vml

[Desktop-packages] [Bug 1859924] Re: gnome-shell crashed with SIGSEGV

2020-01-15 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1859259, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320744/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320746/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320750/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320751/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320752/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320754/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1859924/+attachment/5320755/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1859259
   gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from 
meta_wayland_actor_surface_real_sync_actor_state() from 
meta_wayland_subsurface_sync_actor_state()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Dupe of 1859259.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 16 01:37:04 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1578333288
  InstallationDate: Installed on 2020-01-05 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/asif
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fd52af981db:mov(%rdi,%rax,1),%rax
   PC (0x7fd52af981db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Thanks for working on this Daniel.  Your supposition is likely an the
right track.  Before I started on this consulting assignment (the
beginning of this year) I was using two external monitors, one on my
desk at home, and one at school.  They were different.  I also was using
some projectors in classrooms that were different yet.  It really
behaves like some part of the system thinks the screen is smaller than
it is. Last year I was using 1920x1080, because I could put smaller text
on the external monitor.  Now I have just this laptop, and so I changed
the resolution to 1600x900.  I think that is about when I started
noticing this.  I moved the monitors.xml, and rebooted.  It hasn't
reappeared, and it sometimes took a little time before I noticed it, so
I'm not ready to say that fixed it.  I'll let you know if it didn't and
supply you with the xrandr output then too.

Again, thanks for looking at this.  It was kind of annoying, though I
could expand and contract the window, and that one would be good for a
while.

Rob

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859926] [NEW] fonts-noto-color-emoji not making pretty emojis in google chrome

2020-01-15 Thread gork skoal

Public bug reported:

Google-Chrome and emoji's is being a weird headache. Something's causing it not 
to find the right font to make emoji's:
"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

** Affects: fonts-noto-color-emoji (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu.
https://bugs.launchpad.net/bugs/1859926

Title:
  fonts-noto-color-emoji not making pretty emojis in google chrome

Status in fonts-noto-color-emoji package in Ubuntu:
  New

Bug description:
  Google-Chrome and emoji's is being a weird headache. Something's causing it 
not to find the right font to make emoji's:
  
"[13743:1:0115/225907.016533:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1859926/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto

Please see bug 1859924.

GsettingsChanges.txt doesn't show any enabled extensions.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto

Also rebooting my machine after resetting the key so extensions should
not be enabled after this for sure.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto

This crash just happened: 1859911

I still see those errant extensions inside of GsettingsChanges.txt, but
they don't appear in the GNOME Tweak UI, nor do I see them in
/home/asif/.local/share/gnome-shell/extensions

I have no idea where they are on disk, and I would be happy to remove
them from disk if I knew where they were.

I also don't see them installed via apt.

I went ahead and reset the key via dconf-editor since it seems like
those are stale entries, so new crashes shouldn't have that set and
confound the situation.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Also, if the problem continues then please try to write down the steps
required to reproduce it.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859911] Re: gnome-shell crashed with SIGSEGV

2020-01-15 Thread Apport retracing service

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1859259, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320705/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320707/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320711/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320712/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320713/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320715/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1859911/+attachment/5320716/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1859259
   gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from 
meta_wayland_actor_surface_real_sync_actor_state() from 
meta_wayland_subsurface_sync_actor_state()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Same as crash 1859259.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 16 00:43:39 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1578333288
  InstallationDate: Installed on 2020-01-05 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/asif
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fadbec8e1db:mov(%rdi,%rax,1),%rax
   PC (0x7fadbec8e1db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Thanks.

The only strange graphics-related issue I can see is that this system
has 22 (twenty two) known monitor layouts stored mentioning dozens of
different monitors. It's a mess and could easily cause this bug. Please
try moving the file ~/.config/monitors.xml to a different directory and
restart the system. You might then need to reconfigure the monitor
layout in Settings.

If the problem reoccurs then next please run:

  xrandr > xrandr.txt

and then attach the file 'xrandr.txt' here.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()

The GSettingsChanges.txt in this bug and bug 1859890 both say you had at
the time of the crashes:

b'org.gnome.shell' b'enabled-extensions' b"['user-theme@gnome-shell-
extensions.gcampax.github.com', 'impatie...@gfxmonk.net',
'no...@maestroschan.fr', 'bingwallpa...@ineffable-gmail.com',
'dayni...@maze-n.github.com']"

I'm not sure how effective disable-user-extensions is as we have found
in other bug reports that buggy extensions can just ignore the disable
setting. Extensions need to be uninstalled to be sure.

It is also possible you have disabled extensions successfully and the
latest crash dump (bug 1859890) was just sitting on disk from before
that time. Hence removing extensions may have successfully stopped the
crash from occurring. Let's give it time and see if any more occur.

Also worth noting you are the only person reporting this crash right
now, which suggests it's caused by something uncommon.



** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from 
meta_wayland_actor_surface_real_sync_actor_state()
+ gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from 
meta_wayland_actor_surface_real_sync_actor_state() from 
meta_wayland_subsurface_sync_actor_state()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_acto

The uncommon thing might be subsurfaces:

  meta_wayland_subsurface_sync_actor_state

which would be triggered by MOZ_ENABLE_WAYLAND=1. So maybe extensions
are not involved. We should wait and get a clean crash report from your
system while no extensions are installed, to be completely sure.

I still can't find any other reports of this crash from other people in
Ubuntu or upstream :/

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state() from
  meta_wayland_subsurface_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()

Daniel,

The first line in GsettingsChanges.txt says:

b'org.gnome.shell' b'disable-user-extensions' b'true'

I globally disabled extensions via GNOME Tweak -- does this switch not
work?

I just now also removed everything inside of /home/asif/.local/share
/gnome-shell/extensions -- there was only one extension there (but it
should have been disabled anyway).

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320681/+files/lspcik.txt

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320677/+files/journal.txt

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Here are the files:

** Attachment added: "here"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320676/+files/here

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320682/+files/dmesg.txt

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Please also run these commands on the machine:

  dmesg > dmesg.txt
  lspci -k > lspcik.txt
  journalctl -b0 > journal.txt

and then attach all three resulting files to this bug, as well as the
resulting file from comment #5.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1843157] Re: SUPER+D does not maximize minimized opened windows with SUPER+D after right-click on desktop

2020-01-15 Thread Launchpad Bug Tracker

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

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

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

Title:
  SUPER+D does not maximize minimized opened windows with SUPER+D after
  right-click on desktop

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  If I do SUPER+D the desktop will be shown minimizing all opened
  windows.

  It I right-click on desktop, then I can't reuse SUPER+D to maximize
  those windows.

  In the previous Ubuntu versions it worked fine.

  If I don't right-click on desktop SUPER+D works.

  I'm using Ubuntu 18.04, just installed.

  lsb_release -rd:
  Description: Ubuntu 18.04.3 LTS
  Release: 18.04

  apt-cache policy nemo:
  nemo:
Installato: 3.6.5-1
Candidato: 3.6.5-1
Tabella versione:
   *** 3.6.5-1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.4-0~ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 08:17:33 2019
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x545+428+170'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2019-09-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1838604] Re: cannot close nautilus windows

2020-01-15 Thread Launchpad Bug Tracker

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

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

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

Title:
  cannot close nautilus windows

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.04
  Release:  19.04

  apt-cache policy nautilus
  nautilus:
Installed: 1:3.32.1-0ubuntu0.19.04.0
Candidate: 1:3.32.1-0ubuntu0.19.04.0
Version table:
   *** 1:3.32.1-0ubuntu0.19.04.0 500
  500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.32.0-0ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  Right click quit 2 windows = windows remain open

  click on close individual window = window remains open

  WORSE, none of the contents in the folders are available. Mouse clicks
  do NOT respond in any of the open Nautilus windows.

  I can open other windows but if directory Z is not responding then I
  cannot open another instance of directory Z!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.32.1-0ubuntu0.19.04.0
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug  1 08:30:38 2019
  InstallationDate: Installed on 2015-08-23 (1438 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-04-24 (98 days ago)
  usr_lib_nautilus: dropbox 2019.02.14

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859899] [NEW] Please add a ZFS gui

2020-01-15 Thread Hveem

Public bug reported:

Right now the only way is with CLI. I do know the CLI methods but simple 
operations that I'd like to be able to see visually, like the RAID array or the 
allocated drives with ZFS, pools, datasets etc would all be nicely placed in a 
GUI that would double as an input to modify them.
There are GUI's that exist on Ubuntu for non-ZFS volumes, but since Ubuntu is 
moving towards ZFS as a standard it only makes sense that a GUI would be 
created for such tasks. It's nice to see things like your currently configured 
cron jobs, like scrubs and disk usage etc..

A GUI for ZFS would be a tremendous advance in terms of expediency,
utility, and ease of use.

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


** Tags: wishlist

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

Title:
  Please add a ZFS gui

Status in gnome-disk-utility package in Ubuntu:
  New

Bug description:
  Right now the only way is with CLI. I do know the CLI methods but simple 
operations that I'd like to be able to see visually, like the RAID array or the 
allocated drives with ZFS, pools, datasets etc would all be nicely placed in a 
GUI that would double as an input to modify them.
  There are GUI's that exist on Ubuntu for non-ZFS volumes, but since Ubuntu is 
moving towards ZFS as a standard it only makes sense that a GUI would be 
created for such tasks. It's nice to see things like your currently configured 
cron jobs, like scrubs and disk usage etc..

  A GUI for ZFS would be a tremendous advance in terms of expediency,
  utility, and ease of use.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1730072] Re: Gnome Night Light doesn't work

2020-01-15 Thread Rocco Muscaritolo

I too see tons of messages in systemd.

xrandr -q works fine from the terminal. however, I just caught these
access denied messages as well. Looks like the root cause.

Sender: xdg-desktop-por
Message: Failed to get application states:
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not
allowed

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

Title:
Gnome Night Light doesn't work

Status in gnome-control-center package in Ubuntu:
Invalid

Bug description:
I have a similar issue as this bug
https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/1676131. But I am reopening according to what it is said
in the last post of the above bug ticket.

Gnome Night Light doesn't work on my system: Asus UX301L Notebook
using Ubuntu 17.10 with the latest updates.

It used to work and suddenly stopped working but I can't remember at
what period exactly. I think it was before the official release...

If you need more information, tell me.

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

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

If that doesn't work then please run:

  apport-cli -p gnome-shell -f --save=here

and attach the file 'here' to this bug.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

2020-01-15 Thread Bug Watch Updater

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  The bluetooth gets started automatically whenever a network is
  selected after turning on the wifi.

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Whenever the WiFi feature is turned off after usage,the system
  automatically goes to Airplane mode.If the user turns on the WiFi
  again by selecting the option Select Network in WiFi menu bar then a
  dialog box is displayed with the option of TURN OFF THE AIRPLANE
  MODE.After clicking the option, the Bluetooth automatically gets TURN
  ON without users willing(Even though not required).Or if continue with
  turning on the WiFi ,another dialog box appears with the option of
  TURN ON WiFi. After clicking this option ,the system will search for
  WiFi networks. Once the desired network is selected the WiFi starts
  working. After this if the user check the Bluetooth, it gets started
  automatically with use.This may lead to quick battery drainage.

  In short, the Bluetooth gets automatically started even if not
  required after turning the airplane mode OFF. Please solve this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 00:49:11 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-07 (526 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Vostro 3578
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Please run:

  apport-collect 1859774

as we need more information about the affected system.

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2113
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/2113

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

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

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

Title:
  The bluetooth gets started automatically whenever a network is
  selected after turning on the wifi.

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Whenever the WiFi feature is turned off after usage,the system
  automatically goes to Airplane mode.If the user turns on the WiFi
  again by selecting the option Select Network in WiFi menu bar then a
  dialog box is displayed with the option of TURN OFF THE AIRPLANE
  MODE.After clicking the option, the Bluetooth automatically gets TURN
  ON without users willing(Even though not required).Or if continue with
  turning on the WiFi ,another dialog box appears with the option of
  TURN ON WiFi. After clicking this option ,the system will search for
  WiFi networks. Once the desired network is selected the WiFi starts
  working. After this if the user check the Bluetooth, it gets started
  automatically with use.This may lead to quick battery drainage.

  In short, the Bluetooth gets automatically started even if not
  required after turning the airplane mode OFF. Please solve this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 00:49:11 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-07 (526 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Vostro 3578
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859867] Re: The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

Confirmed. I think the problem is that "airplane mode" doesn't really
exist. It's just the state in which all radios (reported by 'rfkill')
are set to soft blocked.

Yeah, gnome-shell ideally should be doing better here. Inverting
airplane mode is a mistake. It should only be enabling wifi.

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

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

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

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

Title:
  The bluetooth gets started automatically whenever a network is
  selected after turning on the wifi.

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Whenever the WiFi feature is turned off after usage,the system
  automatically goes to Airplane mode.If the user turns on the WiFi
  again by selecting the option Select Network in WiFi menu bar then a
  dialog box is displayed with the option of TURN OFF THE AIRPLANE
  MODE.After clicking the option, the Bluetooth automatically gets TURN
  ON without users willing(Even though not required).Or if continue with
  turning on the WiFi ,another dialog box appears with the option of
  TURN ON WiFi. After clicking this option ,the system will search for
  WiFi networks. Once the desired network is selected the WiFi starts
  working. After this if the user check the Bluetooth, it gets started
  automatically with use.This may lead to quick battery drainage.

  In short, the Bluetooth gets automatically started even if not
  required after turning the airplane mode OFF. Please solve this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
  Uname: Linux 4.15.0-74-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 16 00:49:11 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-08-07 (526 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. Vostro 3578
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 01Y7V4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3578
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859810] Re: [Inspiron 3268] audio esta mudo

Please run this command, again :)

apport-collect 1859810


** Summary changed:

- som
+ [Inspiron 3268] audio esta mudo

** Package changed: xorg (Ubuntu) => pulseaudio (Ubuntu)

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

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

Title:
  [Inspiron 3268] audio esta mudo

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  o audio esta mudo

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jan 15 08:28:41 2020
  DistUpgraded: 2020-01-14 10:48:30,743 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falha ao executar processo filho 
“./xorg_fix_proprietary.py” (Arquivo ou diretório inexistente) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0764]
  InstallationDate: Installed on 2020-01-11 (4 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Inspiron 3268
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=fd473502-2a31-400b-b303-9f46a74c2132 ro locale=pt_BR quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2020-01-14 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 07F37C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd01/25/2018:svnDellInc.:pnInspiron3268:pvr:rvnDellInc.:rn07F37C:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3268
  dmi.product.sku: 0764
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Jan 13 20:38:33 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8758 
   vendor AOC
  xserver.version: 2:1.18.4-0ubuntu0.8

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()

Asif,

Please try again. Bug 1859890 says you had the extensions enabled when
that crash happened:

b'org.gnome.shell' b'enabled-extensions' b"['user-theme@gnome-shell-
extensions.gcampax.github.com', 'impatie...@gfxmonk.net',
'no...@maestroschan.fr', 'bingwallpa...@ineffable-gmail.com',
'dayni...@maze-n.github.com']"

Assuming you have disabled the extensions then the crash in bug 1859890
might be from before or after you disabled them. So that's kind of good
-- there is no evidence of the crash happening WITHOUT the extensions.
Please uninstall them and keep them uninstalled. Then let us know about
any future crashes.

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

Title:
  gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
  from meta_wayland_actor_surface_real_sync_actor_state()

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2

  ---

  This has begun happening in the last few days; I was unable to create
  a bug for the last crash because I had some outdated packages
  installed.

  This crash occurred as I started Firefox Nightly on my machine with a
  fairly large session being restored.

  GNOME logged me out as the windows were being spawned by session
  restored.

  My Firefox is being started in pure Wayland mode --
  MOZ_ENABLE_WAYLAND=1

  I am using "Basic" compositing (not WebRender) in this session.

  Happy to provide any other details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jan 10 20:22:13 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2020-01-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax
   PC (0x7fa5318821db) ok
   source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA 
region (needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859774] Re: Full screen window becomes "small" in the upper left of the screen...

Here is another photo.

** Attachment added: "Another photo of the problem..."
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859774/+attachment/5320654/+files/gnome-shell-bug1.png

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

Title:
  Full screen window becomes "small" in the upper left of the screen...

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  This happens with a number of different programs, so I suspect it is a
  window manager bug.  The best way to describe it is with a screen
  shot.  The only responsive part of the screen is the small window in
  the upper left.  You can hit the little maximize box and it goes back
  to full screen okay, but after a while it comes back to this.  It can
  be annoying, because sometimes you can't quickly see what happened to
  the title bar.  I'm using Ubuntu 19.10.  This has been happening for
  about a week.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859867] [NEW] The bluetooth gets started automatically whenever a network is selected after turning on the wifi.

2020-01-15 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Whenever the WiFi feature is turned off after usage,the system
automatically goes to Airplane mode.If the user turns on the WiFi again
by selecting the option Select Network in WiFi menu bar then a dialog
box is displayed with the option of TURN OFF THE AIRPLANE MODE.After
clicking the option, the Bluetooth automatically gets TURN ON without
users willing(Even though not required).Or if continue with turning on
the WiFi ,another dialog box appears with the option of TURN ON WiFi.
After clicking this option ,the system will search for WiFi networks.
Once the desired network is selected the WiFi starts working. After this
if the user check the Bluetooth, it gets started automatically with
use.This may lead to quick battery drainage.

In short, the Bluetooth gets automatically started even if not required
after turning the airplane mode OFF. Please solve this bug.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
Uname: Linux 4.15.0-74-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 16 00:49:11 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-08-07 (526 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: Dell Inc. Vostro 3578
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
root=UUID=cae6b0e3-ea25-4b38-9cf5-0f431e2d7c9c ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 01Y7V4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd07/04/2019:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 3578
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: DC:A2:66:4C:A1:A4  ACL MTU: 1024:8  SCO MTU: 50:8
UP RUNNING PSCAN 
RX bytes:1320 acl:0 sco:0 events:80 errors:0
TX bytes:1142 acl:0 sco:0 commands:80 errors:0

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


** Tags: amd64 apport-bug bionic
-- 
The bluetooth gets started automatically whenever a network is selected after 
turning on the wifi.
https://bugs.launchpad.net/bugs/1859867
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-shell in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859782] Re: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display

Same issue in Chromium if you visit vsynctester.com


** Summary changed:

- Xwayland apps like glxgears report 58 FPS on a 60Hz display
+ Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1859782

Title:
  Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz
  display

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Xwayland apps like glxgears report 58 FPS on a 60Hz display. This does
  not happen in a native Xorg login.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xwayland 2:1.20.6-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Wed Jan 15 18:18:00 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 630 [17aa:3102]
  InstallationDate: Installed on 2019-12-02 (44 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191201)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
   Bus 001 Device 003: ID 045e:0823 Microsoft Corp. Microsoft® Classic 
IntelliMouse®
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=37e661a7-90ed-4c1c-b0f0-b564dbd4a532 ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060530
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1859782/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859173] Re: [viafb] Display issue

Sorry. Please run:

  sudo apt install mesa-utils
  glxinfo > glxinfo.txt

and then attach the resulting file 'glxinfo.txt' here.

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

Title:
  [viafb] Display issue

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  i comandi e la barra superiore sbordano, non riesco a visualizzarli

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 10 13:12:16 2020
  DistUpgraded: 2020-01-10 07:57:08,409 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio 
«./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8))
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] [1106:3108] 
(rev 01) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] 
[1043:8129]
  InstallationDate: Installed on 2020-01-08 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=943bdf0d-bfd4-4e4d-b427-5c0ac904be90 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2020-01-10 (0 days ago)
  dmi.bios.date: 09/12/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0203
  dmi.board.name: K8V-MX
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 6
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0203:bd09/12/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnK8V-MX:rvr:cvnChassisManufacture:ct6:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859320] Re: Multiple sign-in options in menu of Ubuntu Software

2020-01-15 Thread Robert Ancell

I need to confirm that but it was my understanding that if you have done
a snap login from the command line these should still show.

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

Title:
  Multiple sign-in options in menu of Ubuntu Software

Status in gnome-software package in Ubuntu:
  In Progress

Bug description:
  Why does Ubuntu Software have (effectively) two sign in / sign out
  options for the same thing?

  Steps to reproduce

  * Install 20.04 (or indeed 19.10, not tested on previous releases)
  * Launch Ubuntu Software

  Expected behaviour

  * Option to sign in to Snap Store should exist
  * Option to sign in to Ubuntu One should not exist

  Actual behaviour

  * Options for signing into Ubuntu One and Snap Store are present

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.30.6-2ubuntu11
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 12 10:29:11 2020
  InstallationDate: Installed on 2020-01-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu11
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()