date:20180415

** Package changed: gjs (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and
  glib 2.56.1-2ubuntu1

Status in glib2.0 package in Ubuntu:
  Won't Fix

Bug description:
  Since Ubuntu updated to gjs 1.52.1-1, our bug tracking systems are
  unable to automatically retrace crashes. This has created a sudden
  wave of crash reports that we can't automatically classify.

  For example, this is what LP: #1748450/LP: #1505409 looks like now:

  #0  raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51
  set = {__val = {0, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 
548, 549, 550, 551, 552}}
  pid = 
  tid = 
  ret = 
  #1  0x558168af3a6b in dump_gjs_stack_on_signal_handler (signo=5) at 
../src/main.c:367
  sa = {__sigaction_handler = {sa_handler = 0x558168af3aa0 
, sa_sigaction = 0x558168af3aa0 
}, sa_mask = {__val = {0 }}, 
sa_flags = 0, sa_restorer = 0x0}
  i = 65
  #2  
  No locals.
  #3  0x7f1d3e2bdc41 in ?? ()
  No symbol table info available.
  #4  0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #5  0x7f1d3e2bec7c in ?? ()
  No symbol table info available.
  #6  0x7f1d3e30a51f in ?? ()
  No symbol table info available.
  #7  0x7f1d3e35fe32 in ?? ()
  No symbol table info available.
  #8  0x in ?? ()
  No symbol table info available.
  #9  0x7f1d3e30a451 in ?? ()
  No symbol table info available.
  #10 0x5581697262f0 in ?? ()
  No symbol table info available.
  #11 0x in ?? ()
  No symbol table info available.
  #12 0x7f1d3e30a464 in ?? ()
  No symbol table info available.
  #13 0x7f1d3e30a2f9 in ?? ()
  No symbol table info available.
  #14 0x in ?? ()
  No symbol table info available.
  #15 0x7f1d3e30a4be in ?? ()
  No symbol table info available.
  #16 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #17 0x in ?? ()
  No symbol table info available.
  #18 0x5581697262f0 in ?? ()
  No symbol table info available.
  #19 0x4cae2c7f65c95f00 in ?? ()
  No symbol table info available.
  #20 0x0006 in ?? ()
  No symbol table info available.
  #21 0x558168af3b45 in default_log_handler (log_domain=0x1 , log_level=6, message=0x5581697262f0 "Connection 
to xwayland lost", data=0x0) at ../src/main.c:310
  now = {tv_sec = 1523717020, tv_usec = 986744}
  #22 0x7f1d3e2bef0d in ?? ()
  No symbol table info available.
  #23 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #24 0x5581697262f0 in ?? ()
  No symbol table info available.
  #25 0x0001 in ?? ()
  No symbol table info available.
  #26 0x558168af3af0 in ?? () at ../src/main.c:337

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1764216/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time

** No longer affects: gnome-shell (Ubuntu Bionic)

** No longer affects: gnome-shell (Ubuntu)

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Confirmed
Status in gjs package in Ubuntu:
  In Progress
Status in gjs source package in Bionic:
  In Progress

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/64

  ---

  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14,

[Desktop-packages] [Bug 1764216] [NEW] [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

You have been subscribed to a public bug:

Since Ubuntu updated to gjs 1.52.1-1, our bug tracking systems are
unable to automatically retrace crashes. This has created a sudden wave
of crash reports that we can't automatically classify.

For example, this is what LP: #1748450/LP: #1505409 looks like now:

#0  raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 
548, 549, 550, 551, 552}}
pid = 
tid = 
ret = 
#1  0x558168af3a6b in dump_gjs_stack_on_signal_handler (signo=5) at 
../src/main.c:367
sa = {__sigaction_handler = {sa_handler = 0x558168af3aa0 
, sa_sigaction = 0x558168af3aa0 
}, sa_mask = {__val = {0 }}, 
sa_flags = 0, sa_restorer = 0x0}
i = 65
#2  
No locals.
#3  0x7f1d3e2bdc41 in ?? ()
No symbol table info available.
#4  0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#5  0x7f1d3e2bec7c in ?? ()
No symbol table info available.
#6  0x7f1d3e30a51f in ?? ()
No symbol table info available.
#7  0x7f1d3e35fe32 in ?? ()
No symbol table info available.
#8  0x in ?? ()
No symbol table info available.
#9  0x7f1d3e30a451 in ?? ()
No symbol table info available.
#10 0x5581697262f0 in ?? ()
No symbol table info available.
#11 0x in ?? ()
No symbol table info available.
#12 0x7f1d3e30a464 in ?? ()
No symbol table info available.
#13 0x7f1d3e30a2f9 in ?? ()
No symbol table info available.
#14 0x in ?? ()
No symbol table info available.
#15 0x7f1d3e30a4be in ?? ()
No symbol table info available.
#16 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#17 0x in ?? ()
No symbol table info available.
#18 0x5581697262f0 in ?? ()
No symbol table info available.
#19 0x4cae2c7f65c95f00 in ?? ()
No symbol table info available.
#20 0x0006 in ?? ()
No symbol table info available.
#21 0x558168af3b45 in default_log_handler (log_domain=0x1 , log_level=6, message=0x5581697262f0 "Connection 
to xwayland lost", data=0x0) at ../src/main.c:310
now = {tv_sec = 1523717020, tv_usec = 986744}
#22 0x7f1d3e2bef0d in ?? ()
No symbol table info available.
#23 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#24 0x5581697262f0 in ?? ()
No symbol table info available.
#25 0x0001 in ?? ()
No symbol table info available.
#26 0x558168af3af0 in ?? () at ../src/main.c:337

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Won't Fix


** Tags: regression-update
-- 
[regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 
2.56.1-2ubuntu1
https://bugs.launchpad.net/bugs/1764216
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to glib2.0 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 1764255] Re: gnome-shell crashed with signal 5

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

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 #1748450, 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/1764255/+attachment/5117508/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Another crash on resume from suspend.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 07:18:04 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1370 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_dbus_connection_send_message_with_reply_sync () at 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (22 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev 
sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764255/+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 1764252] Re: X-KDE-SubstituteUID=true / root can't be used in wayland

** Package changed: wayland (Ubuntu) => kwin (Ubuntu)

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in kwin package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1764252/+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 1764252] Re: X-KDE-SubstituteUID=true / root can't be used in wayland

2018-04-15 Thread trotosa

** Description changed:

  Hello,
  
  kubuntu 18.04 beta 1
  
  I often use :
  
  X-KDE-SubstituteUID=true
  X-KDE-Username=root
  
  in the file ".desktop" for applications who may have root id.
  
  Example, luckybackup, system-config-samba
  
  No bug in a plasma session.
  
  With wayland, using the same desktop, the application asked for passwd
  and then stop.
  
+ I understood that is for security reasons. That's means all the
+ "graphics" applications needing root id are prohibited.
+ 
  Sorry, english is not my native langage.

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in kwin package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1764252/+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 1716900] Re: apt-get: order of the dependencies ends in a diffrent result

2018-04-15 Thread Matthias Klumpp

** Package changed: appstream (Ubuntu) => apt (Ubuntu)

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

Title:
  apt-get: order of the dependencies ends in a diffrent result

Status in apt package in Ubuntu:
  New

Bug description:
  While trying to use the php installation delivered by
  https://launchpad.net/%7Eondrej/+archive/ubuntu/php, we found out,
  that the order within apt-get install change the solved packages.

  Which means if we do:
  apt-get install php-apcu php7.1-cli => installs newest php and 7.1
  apt-get install php7.1-cli php-apcu) => > installs only 7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716900/+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 1764252] [NEW] X-KDE-SubstituteUID=true / root can't be used in wayland

2018-04-15 Thread trotosa

Public bug reported:

Hello,

kubuntu 18.04 beta 1

I often use :

X-KDE-SubstituteUID=true
X-KDE-Username=root

in the file ".desktop" for applications who may have root id.

Example, luckybackup, system-config-samba

No bug in a plasma session.

With wayland, using the same desktop, the application asked for passwd
and then stop.

I understood that is for security reasons. That's means all the
"graphics" applications needing root id are prohibited.

Sorry, english is not my native langage.

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

** Description changed:

  Hello,
  
  kubuntu 18.04 beta 1
  
  I often use :
  
  X-KDE-SubstituteUID=true
  X-KDE-Username=root
  
- in the file ".desktop" for applications who me have root id.
+ in the file ".desktop" for applications who may have root id.
  
  Example, luckybackup, system-config-samba
  
  No bug in a plasma session.
  
- 
- With wayland, using the same desktop, the application asked for passwd and 
then stop.
- 
+ With wayland, using the same desktop, the application asked for passwd
+ and then stop.
  
  Sorry, english is not my native langage.

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1764252/+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 1547135] Re: Support purchasing software

** Changed in: gnome-software (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Support purchasing software

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Committed

Bug description:
  Eventually people will be able to buy software with money.  This means
  that the prices will need to be displayed in the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1547135/+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 1764243] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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 #1759621, 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/1764243/+attachment/5117414/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1759621
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
st_label_set_text() from ffi_call_unix64()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  gnome-shell crashed on login - not sure if this matches an existing
  bug on LP since I don't have enough context in the title to determine
  if the stack trace matches... I guess apport + errors.ubuntu.com
  should figure this out automatically.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 13:30:14 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-09 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
   LANGUAGE=en_AU:en
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SegvAnalysis:
   Segfault happened at: 0x7f3eed984d12 :
mov(%rdi),%rbp
   PC (0x7f3eed984d12) ok
   source "(%rdi)" (0x69) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764243/+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 1112496] Re: python-imaging broken in raring

2018-04-15 Thread Ubuntu Foundations Team Bug Bot

The attachment "simple-image-reducer fix" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  python-imaging broken in raring

Status in Phatch:
  New
Status in comix package in Ubuntu:
  Invalid
Status in gwibber package in Ubuntu:
  Invalid
Status in ocrfeeder package in Ubuntu:
  Invalid
Status in phatch package in Ubuntu:
  Confirmed
Status in python-imaging package in Ubuntu:
  Fix Released
Status in simple-image-reducer package in Ubuntu:
  Fix Released
Status in wsjt package in Ubuntu:
  Invalid
Status in comix source package in Raring:
  Invalid
Status in gwibber source package in Raring:
  Invalid
Status in ocrfeeder source package in Raring:
  Invalid
Status in phatch source package in Raring:
  Won't Fix
Status in python-imaging source package in Raring:
  Fix Released
Status in simple-image-reducer source package in Raring:
  Invalid
Status in wsjt source package in Raring:
  Invalid

Bug description:
  python-imaging in raring doesn't include a PIL.pth to point python at
  the library, so attempts to import modules from the package fail with,
  eg:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  /usr/bin/python: No module named Image

  When the PIL.pth file is manually created, so python can find it, the
  Image module itself still fails to load:

  rachel@rarity:/etc$ python -m Image
  Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
  "__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
  exec code in run_globals
File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 75, in 
  from . import ImageMode
  ValueError: Attempted relative import in non-package

  The ImageMode module that line seems to be trying to import, however,
  seems to import fine by itself:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  ok

  (I've confirmed that ImageMode comes from the same place, as if I
  remove PIL.pth again, the above line just returns the "No module named
  ImageMode" error)

  I've tried reinstalling python-imaging already. I note in any case the
  PIL.pth file is missing on the file list available at
  packages.ubuntu.com for raring.

  This is on Ubuntu Raring as updated from Ubuntu Quantal a few days
  ago:

  rachel@rarity:/etc$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  rachel@rarity:/etc$ apt-cache policy python
  python:
Installed: 2.7.3-10ubuntu5
Candidate: 2.7.3-10ubuntu5
Version table:
   *** 2.7.3-10ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  rachel@rarity:/etc$ apt-cache policy python-imaging
  python-imaging:
Installed: 1.1.7+1.7.8-1ubuntu1
Candidate: 1.1.7+1.7.8-1ubuntu1
Version table:
   *** 1.1.7+1.7.8-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Affects me as it affects building/packaging XBMC post-frodo for
  raring. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/phatch/+bug/1112496/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time

** Changed in: gjs (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: gjs (Ubuntu Bionic)
   Importance: High => Critical

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Confirmed
Status in gjs package in Ubuntu:
  In Progress
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  In Progress
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/64

  ---

  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(12, 0x7fff60efb000, 0)  = -1

[Desktop-packages] [Bug 1749197] Re: file-roller doesn't display .cbz contents

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

** Changed in: file-roller (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  file-roller doesn't display .cbz contents

Status in file-roller package in Ubuntu:
  Expired

Bug description:
  When trying to open .cbz (eComic .zip file) with file-roller, it
  doesn't open the file, just the app.

  .cbz is just a .zip file with it's extension renamed for eComic
  viewers.

  Should open just like any .zip file in file-roller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1749197/+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 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver

** Changed in: mutter
   Status: Unknown => Confirmed

** Changed in: mutter
   Importance: Unknown => Medium

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

Title:
  [bionic][beta][nvidia] gnome-shell high CPU utilization when using
  Nvidia driver

Status in Mutter:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing 60% - 200% CPU utilization after an upgrade from
  ubuntu artful to bionic.

  Pretty much any drawing results in a sluggish behavior due to high CPU
  utilization.

  The same combination of kernel/drivers did not result in the issue on
  17.10 so gnome-shell seems a good candidate to blame.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:53:34 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 
[origin: unknown]
  PackageArchitecture: amd64
  Tags: third-party-packages bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
systemd-journal ubridge
  _MarkForUpload: True

  ➜  ~ dpkg -l | grep -P 'ii.*?nvidia'
  ii  nvidia-390  
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA binary driver - version 390.48
  ii  nvidia-opencl-icd-390   
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.7 
 all  Tools to 
enable NVIDIA's Prime
  ii  nvidia-settings 
396.18-0ubuntu0~gpu17.10.1 amd64
Tool for configuring the NVIDIA graphics driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1764137/+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 1764238] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

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

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 #1759621, 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/1764238/+attachment/5117373/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1759621
   gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from 
st_label_set_text() from ffi_call_unix64()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After  a restart, and when Chrome was loading up, and asking for my
  Password.  No big deal, as it did not even seem to crash - just the
  error.  Perhaps it was related to the slow startup, which was oddly
  after rebooting into windows for a moment the rebooting back into
  Ubuntu.  Both gave hiccups.  And Ubuntu took an extra 10-20 seconds
  going to a black wallpaper and flashed a few times and did the NVidia
  "Dance" but figured it out.  When X loaded it threw the error as
  stated above.

  Just trying to help, Mark

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 20:40:46 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-04-12 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f964affcd3d :
movzbl 0x16(%rax),%edx
   PC (0x7f964affcd3d) ok
   source "0x16(%rax)" (0x93aa) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () at /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   () at /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764238/+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 1763878] Re: [regression] gjs-* and gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

Fixed upstream in:
https://gitlab.gnome.org/GNOME/gjs/commit/8510bede1dd1f8a5fb95a2f594b4d3a68289e5ea

** Changed in: gjs (Ubuntu)
   Status: Confirmed => Triaged

** No longer affects: gnome-shell (Ubuntu)

** Description changed:

- https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3
+ Duplicates: 
https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3
+ A fix: 
https://gitlab.gnome.org/GNOME/gjs/commit/8510bede1dd1f8a5fb95a2f594b4d3a68289e5ea
  
  ---
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:16:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
   b'org.gnome.desktop.interface' b'cursor-size' b'32'
  InstallationDate: Installed on 2018-04-05 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7fe7267807d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fe722d8ad05 
"hash_table->live_entries == 0", file=file@entry=0x7fe722d8ace8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fe722d8ae90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fe722d8ad05 "hash_table->live_entries == 
0", file=0x7fe722d8ace8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fe722d8ae90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Description changed:

- Duplicates: 
https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3
- A fix: 
https://gitlab.gnome.org/GNOME/gjs/commit/8510bede1dd1f8a5fb95a2f594b4d3a68289e5ea
+ Duplicates:
+ https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3
+ https://errors.ubuntu.com/problem/7094d9804b2da7eeaf1803068c126eb376913d49
+ 
+ A fix:
+ 
https://gitlab.gnome.org/GNOME/gjs/commit/8510bede1dd1f8a5fb95a2f594b4d3a68289e5ea
  
  ---
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:16:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
   b'org.gnome.desktop.interface' b'cursor-size' b'32'
  InstallationDate: Installed on 2018-04-05 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7fe7267807d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fe722d8ad05 
"hash_table->live_entries == 0", file=file@entry=0x7fe722d8ace8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fe722d8ae90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fe722d8ad05 "hash_table->live_entries == 
0", file=0x7fe722d8ace8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fe722d8ae90 "_cairo_hash_table_destroy") at assert.c:101

[Desktop-packages] [Bug 1764237] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

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 #1748450, 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/1764237/+attachment/5117358/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Upon loading the Software Updater, the system reported an error.  Did
  not run the update, but instead rebooted.  Following the reboot, I
  again loaded the Software Updater and the error occurred again.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr 15 22:25:49 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-11 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764237/+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 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from

This report:

https://errors.ubuntu.com/problem/7576bbf83cb88a0b3a870e1371dd86416b23c4b3

suggests the wave of unreadable stack traces this week was perhaps due
to an update to glib2.0, because:

/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.0 (deleted)

So they are almost certainly all duplicates of this bug, unreadable due
to the upgrade procedure of glib2.0. The good news is that the wave
should stop after everyone has upgraded.

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

Title:
  gnome-shell crashed with SIGTRAP in _g_log_abort() from
  g_log_default_handler() from default_log_handler(message="Connection
  to xwayland lost") from g_logv() from g_log() from 

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Bionic:
  Triaged

Bug description:
  *** This is a duplicate of bug 1505409, but is being kept separate so
  as to automatically collect duplicate reports since the stacktrace
  signature has changed recently. Any resolution and discussion should
  occur in bug 1505409. ***

  See also:
  https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Feb  8 23:50:23 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-21 (690 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+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 1764232] Re: gnome-shell crashed during login

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

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 #1748450, 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/1764232/+attachment/5117337/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed  during login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  all happening during login after reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Apr 16 14:58:08 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_NZ:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764232/+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 1758107] Re: Firefox: View > Toolbars is Missing "Bookmarks Toolbar"

2018-04-15 Thread Mathew Hodson

** Bug watch removed: Mozilla Bugzilla #1428938
   https://bugzilla.mozilla.org/show_bug.cgi?id=1428938

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

Title:
  Firefox: View > Toolbars is Missing "Bookmarks Toolbar"

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  The "Bookmarks Toolbar" toggler is missing from the View > Toolbars
  menu in Firefox 59 on Ubuntu 16.04.4.

  Video:
  https://youtu.be/Josm0VqtUDQ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 59.0.1+build1-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lonnie 1902 F pulseaudio
   /dev/snd/pcmC0D0p:   lonnie 1902 F...m pulseaudio
   /dev/snd/controlC0:  lonnie 1902 F pulseaudio
  BuildID: 20180316021607
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Thu Mar 22 11:42:51 2018
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-09 (41 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.77.1 dev enp3s0  proto static  metric 100 
   169.254.0.0/16 dev enp3s0  scope link  metric 1000 
   192.168.77.0/24 dev enp3s0  proto kernel  scope link  src 192.168.77.252  
metric 100
  NoProfiles: True
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 7001
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 35.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.25:bd05/31/2010:svnHewlett-Packard:pnHPPaviliondv8NotebookPC:pvr04992224121000104:rvnHewlett-Packard:rn7001:rvr35.35:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv8 Notebook PC
  dmi.product.version: 04992224121000104
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1758107/+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 1763273] Re: kernel panic in Radeon driver while screen blank

While logged in via ssh to the machine with the "hung" Xorg (screen
blank, no way to recover except Alt-SysRq-k), I dumped the output of
Alt-SysRq-t into the syslog -- see attached file. Not sure this is much
use, however. Just trying to be complete while I'm on-site with a hung
machine.

** Attachment added: "syslog with output from Alt-SysRq-t in ssh session"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Bug description:
I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
LTS and 16.04. As we have gradually transitioned them to 16.04, we
have noticed that the machines running 16.04.1 now regularly exhibit
problems restoring from the blank screen which appears after a period
of inactivity.

This only occurs on the machines where we've installed 16.04. All of
the 16.04.1 installations are "fresh", that is, complete re-installs
from scratch, and we install all security and other updates on a
regular basis. This problem has persisted right from the beginning
when we started using 16.04.

Following a period of user inactivity, the screen goes blank; this is,
of course, expected. When the user tries to restore the session by
typing a key or moving the mouse, one of three outcomes occurs.

Sometimes, the session restores normally. Other times, the screen
remains blank regardless of all normal keyboard input, until a magic
SysRq sequence is performed. After Alt-SysRq-k, either the virtual
console resets to a login screen (as expected after this SysRq
sequence), or we get a kernel panic text screen (see attached screen
photo) and can only restore via a hard power-cycle reboot.

I will continue to try to capture a better trace output from one of
these conditions, perhaps from /var/log/kern.log or by installing
linux-crashdump (although these old machines may not have enough
memory for the stock package). But in the meantime, I'm attaching a
photo of the kernel panic we see, which suggests a problem may reside
in the Radeon driver ... which would seem possible, given the general
blank-screen no-resume problem on these systems.

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

Confirmed also with LANGUAGE=it_IT.UTF-8 (bug 1764071)

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760201/+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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

Ahmet, are you using multiple monitors?

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760201/+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 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "rom.vga.bin"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Desktop-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "gdb-Xorg.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.txt

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Desktop-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

Further debugging today while I'm on-site with the kiosks.  The system
froze, as usual, after normal idle screen blanking.  I was able to login
via ssh and retrieve some details.

First, it appears that the basic screen blanking problem is somehow
related to the Radeon driver.  I will attach the Xorg.0.log file and a
gdb backtrace on the running but non-responsive Xorg process.  No
keyboard or mouse activity will un-blank the screen.

Here's the output from lspci | grep VGA:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 
[Radeon X1300/X1550 Series]

I'll also attach the PCI ROM dump from the /sys/devices rom file for
this device.

This suggests that when we use Alt-SysRq-k to restore the system,
sometimes we trigger *another* bug in the driver which results in the
overall system crash.  See the attached apr1.full.kern.log file for what
details I could recover from the crash on April 1st; that corresponds to
the screen photo I took that day (the radeon_kernel_panic1.jpg
attachment).

The Xorg "hang" bug which precedes this appears similar, but not
identical, to what is documented in #1664979:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979

I will continue to try to study the live Xorg process to see if I can
determine where its hung, but I may not have time this evening.  Let me
know if there are specific further debugging steps I can take to examine
either the Xorg hang or the subsequent crash which (sometimes) follows
on attempting to recover with Alt-SysRq-k.  (And note that I'll copy in
the files apport-bug generated from #1764211 later tonight, using my
"cdarroch" personal account, and then I'll try to close that extra bug
report.)

Thanks very much,
Chris.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1764137] Re: [bionic][beta][nvidia] gnome-shell high cpu utilization

See also bug 1716434.

** Tags added: nvidia performance

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

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

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=781835
   Importance: Unknown
   Status: Unknown

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

** Summary changed:

- [bionic][beta][nvidia] gnome-shell high cpu utilization
+ [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia 
driver

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

Title:
  [bionic][beta][nvidia] gnome-shell high CPU utilization when using
  Nvidia driver

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

Bug description:
  I am experiencing 60% - 200% CPU utilization after an upgrade from
  ubuntu artful to bionic.

  Pretty much any drawing results in a sluggish behavior due to high CPU
  utilization.

  The same combination of kernel/drivers did not result in the issue on
  17.10 so gnome-shell seems a good candidate to blame.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:53:34 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 
[origin: unknown]
  PackageArchitecture: amd64
  Tags: third-party-packages bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
systemd-journal ubridge
  _MarkForUpload: True

  ➜  ~ dpkg -l | grep -P 'ii.*?nvidia'
  ii  nvidia-390  
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA binary driver - version 390.48
  ii  nvidia-opencl-icd-390   
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.7 
 all  Tools to 
enable NVIDIA's Prime
  ii  nvidia-settings 
396.18-0ubuntu0~gpu17.10.1 amd64
Tool for configuring the NVIDIA graphics driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1764137/+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 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "Xorg.0.log"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Desktop-packages] [Bug 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

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

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

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760201/+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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

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

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

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

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760201/+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 1760201] Re: ubuntu 18.04 GDM - missing icons and letters on login screen

** Summary changed:

- ubuntu 18.04 GDM - missing icons and letters in Turkish system language
+ ubuntu 18.04 GDM - missing icons and letters on login 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/1760201

Title:
  ubuntu 18.04 GDM - missing icons and letters on login screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots
  --- 
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-03-24 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
  Package: gnome-shell
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Tags:  bionic
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1760201/+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 1764049] Re: [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card

** Summary changed:

- [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
+ [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card

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

Title:
  [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Audio is very glitchy through speakers while using any application.
  Have tried a lot of different things, and configured my audio, but
  still can not get audio to not skip. I'm using Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   chuck  1786 F...m pulseaudio
   /dev/snd/controlC0:  chuck  1786 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 22:31:49 2018
  InstallationDate: Installed on 2018-03-12 (33 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.36
  dmi.board.asset.tag: 8CC7460L0N
  dmi.board.name: 81BB
  dmi.board.vendor: HP
  dmi.board.version: 
  dmi.chassis.asset.tag: 8CC7460L0N
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.36:bd07/20/2017:svnHP:pn20-c013w:pvr:rvnHP:rn81BB:rvr:cvnHP:ct13:cvr:
  dmi.product.family: 103C_53316J HP Desktop
  dmi.product.name: 20-c013w
  dmi.sys.vendor: HP
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-04-04T21:49:05.382211
  mtime.conffile..etc.pulse.default.pa: 2018-04-14T20:03:46.503451

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1764049/+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 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

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

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763940/+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 1763975] Re: DP1.2 daisy-chain flickering

2018-04-15 Thread Stuart

@update. Started occurring even when bypassing the Avocent.

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

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  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'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763975/+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 1762545] Re: No dashed line to indicate that more content is scrollable

** Also affects: ubuntu-themes
   Importance: Undecided
   Status: New

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

Title:
  No dashed line to indicate that more content is scrollable

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ambiance does not show a dashed line to indicate that more content is
  scrollable. I have been using another theme than Ambiance for some
  time and I find the dashed line very helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 22:25:00 2018
  InstallationDate: Installed on 2017-10-02 (189 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1762545/+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 1721428] Re: Artful (17.10) Session logout after screen turned off

This bug is closed due to no response from the original reporter, so
please don't add further comments.

Everyone else should:

1. If using a release older than 18.04 then apply the workaround from
bug 994921 first.

2. Run: ubuntu-bug /var/crash/YOURFILE.crash

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

Title:
  Artful (17.10) Session logout after screen turned off

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Whenever I turn off my screen, the computer (a desktop PC) logs me out
  of my session.

  Here is a discussion thread with users of similar issue:
  
https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1672297] Re: gnome-shell uses lots of memory, and grows over time

@cement_head: The desktop team agrees. We'll be releasing *something*
for this bug this week. Only 3 days to final freeze...

@Amr: Those are probably better left as separate bugs to this one.

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

Title:
  gnome-shell uses lots of memory, and grows over time

Status in GNOME Shell:
  Confirmed
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Triaged
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  Upstream:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/64

  ---

  gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
  almost 2 GiB.

  user  3039  1.8 16.1 4302340 1968476 tty2  Sl+  Mar09 120:17
  /usr/bin/gnome-shell

  strace output is voluminous; here is a representative sample:

  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\231\n\10\0\n\0 
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0 
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
  poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
  recvmsg(5, {msg_name(0)=NULL, 
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32
  recvmsg(5, 0x7fff60efac90, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
  writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0 
(Timeout)
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  open("/proc/self/stat", O_RDONLY)   = 36
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  fcntl(36, F_GETFL)  = 0x8000 (flags O_RDONLY|O_LARGEFILE)
  fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
  read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
  read(36, "", 3072)  = 0
  close(36)   = 0
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, 0x7fff60efb000, 0)  = -1 EAGAIN (Resource temporarily 
unavailable)
  poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN}, 
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26, 
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40, 
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) = 
1 ([{fd=4, revents=POLLIN}])
  read(4, "\1\0\0\0\0\0\0\0", 16) = 8
  recvmsg(5, 0x7fff60efb040, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(5, 0x7fff60efb020, 0)   = -1 EAGAIN (Resource temporarily 
unavailable)
  recvmsg(12, {msg_name(0)=NULL, 
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
 4096}], msg_controllen=0, msg_flags=0}, 0) = 32

[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

if you have any ongoing issues then open a new bug.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1579142] Re: Evince windows cannot be resized after upgrade to Xenial

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

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

Title:
  Evince windows cannot be resized after upgrade to Xenial

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Since upgrade to Xenial, windows of evince cannot be resized on my
  machine. Windows can be maximized and restored, but windows cannot be
  resized with the mouse to arbitrary width and height. Works fine for
  windows of other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evince 3.18.2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-58.64~14.04.1-generic 3.19.8-ckt16
  Uname: Linux 3.19.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  6 18:27:55 2016
  InstallationDate: Installed on 2015-11-05 (183 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1579142/+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 1740618] Re: Remove gksu from Ubuntu

** Description changed:

  Debian has removed gksu. I recommend that we remove gksu and libgksu for
  Ubuntu 18.04 LTS also.
  
  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.
  
  It is recommended that users use the gvfs admin backend available in
  Ubuntu 17.10 and 18.04 LTS. You can do this with the admin:// prefix.
  For instance, instead of running gksu gedit or gksu nautilus to edit say
  /etc/default/grub, navigate to admin:///etc/default/ and open the grub
  file.
  
  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.
  
  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
- * cinnamon  (for gksu)
- * lxde-core (for gksu)
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)
  * zenmap(for gksu)
  
  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)
  
  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
+ * libui-dialog-perl: no other rdepends but macchanger-gtk. This is the 
security bug that got macchanger-gtk removed from Testing. Debian bug 496448
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu
  
  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201
  
  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

** Also affects: libui-dialog-perl (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove gksu from Ubuntu

Status in edubuntu-netboot package in Ubuntu:
  New
Status in gksu package in Ubuntu:
  New
Status in libgksu package in Ubuntu:
  New
Status in libui-dialog-perl package in Ubuntu:
  New
Status in macchanger-gtk package in Ubuntu:
  New
Status in network-config package in Ubuntu:
  Fix Released
Status in sbackup package in Ubuntu:
  Fix Released
Status in umit package in Ubuntu:
  New

Bug description:
  Debian has removed gksu. I recommend that we remove gksu and libgksu
  for Ubuntu 18.04 LTS also.

  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.

  It is recommended that users use the gvfs admin backend available in
  Ubuntu 17.10 and 18.04 LTS. You can do this with the admin:// prefix.
  For instance, instead of running gksu gedit or gksu nautilus to edit
  say /etc/default/grub, navigate to admin:///etc/default/ and open the
  grub file.

  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.

  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)
  * zenmap(for gksu)

  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)

  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
  * libui-dialog-perl: no other rdepends but macchanger-gtk. This is the 
security bug that got macchanger-gtk removed from Testing. Debian bug 496448
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu

  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201

  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-netboot/+bug/1740618/+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 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

Closing this bug, but it continues in bug 1759621.

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

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

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64()

Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1714989/+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 1763878] Re: [regression] gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

Assigning this bug to gjs, because it seems related and is the only
package that changed recently:

#4  0xb791e7bb in __assert_fail_base (fmt=0xb7a7a848 "%s%s%s:%u: %s%sAssertion 
`%s' failed.\n%n", assertion=0xb588c015 "hash_table->live_entries == 0", 
file=0xb588bff8 "../../../../src/cairo-hash.c", line=217, function=0xb588c198 
<__PRETTY_FUNCTION__.12348> "_cairo_hash_table_destroy") at assert.c:92
str = 0x143bf00 ""
total = 4096
#5  0xb791e819 in __GI___assert_fail (assertion=0xb588c015 
"hash_table->live_entries == 0", file=0xb588bff8 
"../../../../src/cairo-hash.c", line=217, function=0xb588c198 
<__PRETTY_FUNCTION__.12348> "_cairo_hash_table_destroy") at assert.c:101
No locals.
#6  0xb57cf573 in _cairo_hash_table_destroy (hash_table=0x13b0980) at 
../../../../src/cairo-hash.c:217
__PRETTY_FUNCTION__ = "_cairo_hash_table_destroy"
#7  0xb580a096 in _cairo_scaled_font_map_destroy () at 
../../../../src/cairo-scaled-font.c:441
font_map = 0x1418880
scaled_font = 0x10ee8c0
__PRETTY_FUNCTION__ = "_cairo_scaled_font_map_destroy"
#8  0xb57c6018 in cairo_debug_reset_static_data () at 
../../../../src/cairo-debug.c:67
No locals.
#9  0xb7b7b2a9 in shutdown () at gjs/engine.cpp:227
No locals.
#10 GjsInit::~GjsInit (this=0xb7bf95b4, __in_chrg=) at 
gjs/engine.cpp:268
No locals.

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

** Summary changed:

- [regression] gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.
+ [regression] gjs-* and gnome-shell-* assert failure: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.

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

Title:
  [regression] gjs-* and gnome-shell-* assert failure: ../../../../src
  /cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
  `hash_table->live_entries == 0' failed.

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3

  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:16:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
   b'org.gnome.desktop.interface' b'cursor-size' b'32'
  InstallationDate: Installed on 2018-04-05 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7fe7267807d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fe722d8ad05 
"hash_table->live_entries == 0", file=file@entry=0x7fe722d8ace8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fe722d8ae90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fe722d8ad05 "hash_table->live_entries == 
0", file=0x7fe722d8ace8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fe722d8ae90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1763878/+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 1763878] Re: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_entri

Tracking in:
https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3

** Description changed:

- Booting Error
+ https://errors.ubuntu.com/problem/8fa67805fb56d4a092138487045210c260c3
+ 
+ ---
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.2-041602-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:16:32 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
-  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
-  b'org.gnome.shell' b'favorite-apps' redacted by apport
-  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
-  b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
-  b'org.gnome.desktop.interface' b'cursor-size' b'32'
+  b'org.gnome.shell' b'app-picker-view' b'uint32 1'
+  b'org.gnome.shell' b'favorite-apps' redacted by apport
+  b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+  b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25'
+  b'org.gnome.desktop.interface' b'cursor-size' b'32'
  InstallationDate: Installed on 2018-04-05 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  ProcEnviron:
-  XDG_RUNTIME_DIR=
-  SHELL=/bin/bash
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  LANG=en_IN
+  XDG_RUNTIME_DIR=
+  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  LANG=en_IN
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
-  __assert_fail_base (fmt=0x7fe7267807d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fe722d8ad05 
"hash_table->live_entries == 0", file=file@entry=0x7fe722d8ace8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fe722d8ae90 "_cairo_hash_table_destroy") at 
assert.c:92
-  __GI___assert_fail (assertion=0x7fe722d8ad05 "hash_table->live_entries == 
0", file=0x7fe722d8ace8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fe722d8ae90 "_cairo_hash_table_destroy") at assert.c:101
-  ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
-  ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
-  cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
+  __assert_fail_base (fmt=0x7fe7267807d8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fe722d8ad05 
"hash_table->live_entries == 0", file=file@entry=0x7fe722d8ace8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7fe722d8ae90 "_cairo_hash_table_destroy") at 
assert.c:92
+  __GI___assert_fail (assertion=0x7fe722d8ad05 "hash_table->live_entries == 
0", file=0x7fe722d8ace8 "../../../../src/cairo-hash.c", line=217, 
function=0x7fe722d8ae90 "_cairo_hash_table_destroy") at assert.c:101
+  ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
+  ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
+  cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Information type changed from Private to Public

** Summary changed:

- gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion 
`hash_table->live_entries == 0' failed.
+ gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

** Summary changed:

- gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.
+ [regression] gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

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

** Changed in: gjs (Ubuntu)
   Importance: Undecided => High

** Tags added: regression-update

** Tags added: regression

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

Title:
  [regression] gjs-* and gnome-shell-* assert failure: ../../../../src
  /cairo-hash.c:217: _cairo_hash_table_destroy: Assertion
  `hash_table->live_entries == 0' failed.

Status in gjs package in Ubuntu:

[Desktop-packages] [Bug 1764102] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live

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

** This bug is no longer a duplicate of private bug 1763909
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Zusicherung »hash_table->live_entries == 0« nicht erfüllt.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash happened after install of Shell Extension Topicons from
  Repository.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung 
»hash_table->live_entries == 0« nicht erfüllt.
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Apr 15 13:03:18 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2016-11-14 (516 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcCmdline: gnome-shell-extension-prefs openweather-extens...@jenslody.de
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f257921b195 , assertion=assertion@entry=0x7f258c116d05 
"hash_table->live_entries == 0", file=file@entry=0x7f258c116ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f258c116e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f258c116d05 "hash_table->live_entries == 
0", file=0x7f258c116ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f258c116e90 "_cairo_hash_table_destroy") at assert.c:101
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht 
erfüllt.
  UpgradeStatus: Upgraded to bionic on 2018-04-05 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764102/+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 1764192] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live

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

** This bug is no longer a duplicate of private bug 1763909
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Zusicherung »hash_table->live_entries == 0« nicht erfüllt.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  just happened

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung 
»hash_table->live_entries == 0« nicht erfüllt.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 23:30:38 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 
'ga...@base-art.net', 'cpuf...@nodefourtytwo.net', 
'openweather-extens...@jenslody.de', 'cpupo...@mko-sl.de', 
'Short_Memo@kusabashira', 'toggle-touch...@martin.kopta.eu']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs
  ProcEnviron:
   LANG=de_DE.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f2a9c0ba195 , assertion=assertion@entry=0x7f2aa6475d05 
"hash_table->live_entries == 0", file=file@entry=0x7f2aa6475ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f2aa6475e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f2aa6475d05 "hash_table->live_entries == 
0", file=0x7f2aa6475ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f2aa6475e90 "_cairo_hash_table_destroy") at assert.c:101
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht 
erfüllt.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764192/+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 1764177] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración `hash_table->l

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

** This bug is no longer a duplicate of private bug 1763971
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La
  declaración `hash_table->live_entries == 0' no se cumple.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't really know what is wrong, but when I lock my screen the dock
  appears edge to edge in the bottom of the screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración 
`hash_table->live_entries == 0' no se cumple.
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:59:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f858c260075 , 
assertion=assertion@entry=0x7f859ce20d05 "hash_table->live_entries == 0", 
file=file@entry=0x7f859ce20ce8 "../../../../src/cairo-hash.c", 
line=line@entry=217, function=function@entry=0x7f859ce20e90 
"_cairo_hash_table_destroy") at assert.c:92
   __GI___assert_fail (assertion=0x7f859ce20d05 "hash_table->live_entries == 
0", file=0x7f859ce20ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f859ce20e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: La declaración `hash_table->live_entries == 0' no se 
cumple.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764177/+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 1764095] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live

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

** This bug is no longer a duplicate of private bug 1763909
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Zusicherung »hash_table->live_entries == 0« nicht erfüllt.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Opened prefs of dash-to-panel

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung 
»hash_table->live_entries == 0« nicht erfüllt.
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Apr 15 12:18:21 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['dash-to-pa...@jderose9.github.com']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: gnome-shell-extension-prefs dash-to-pa...@jderose9.github.com
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f0c9c43e195 , assertion=assertion@entry=0x7f0ca6982d05 
"hash_table->live_entries == 0", file=file@entry=0x7f0ca6982ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f0ca6982e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f0ca6982d05 "hash_table->live_entries == 
0", file=0x7f0ca6982ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f0ca6982e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht 
erfüllt.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764095/+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 1764160] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración `hash_table->l

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

** This bug is no longer a duplicate of private bug 1763971
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La
  declaración `hash_table->live_entries == 0' no se cumple.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash when editing preferences gnome-shell

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración 
`hash_table->live_entries == 0' no se cumple.
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 19:51:11 2018
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2018-04-03 (12 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180402)
  ProcCmdline: gnome-shell-extension-prefs mediapla...@patapon.info
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f5106629075 , 
assertion=assertion@entry=0x7f512f74bd05 "hash_table->live_entries == 0", 
file=file@entry=0x7f512f74bce8 "../../../../src/cairo-hash.c", 
line=line@entry=217, function=function@entry=0x7f512f74be90 
"_cairo_hash_table_destroy") at assert.c:92
   __GI___assert_fail (assertion=0x7f512f74bd05 "hash_table->live_entries == 
0", file=0x7f512f74bce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f512f74be90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: La declaración `hash_table->live_entries == 0' no se 
cumple.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764160/+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 1764010] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live

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

** This bug is no longer a duplicate of private bug 1763909
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Zusicherung »hash_table->live_entries == 0« nicht erfüllt.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Crash happened after changing settings of Gnome Shell Extension
  Topicons Plus.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung 
»hash_table->live_entries == 0« nicht erfüllt.
  CurrentDesktop: GNOME
  Date: Sat Apr 14 23:36:30 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2017-11-13 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  ProcCmdline: gnome-shell-extension-prefs topic...@phocean.net
  ProcEnviron:
   LANGUAGE=de_DE:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f45a0919195 , assertion=assertion@entry=0x7f45b170bd05 
"hash_table->live_entries == 0", file=file@entry=0x7f45b170bce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f45b170be90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f45b170bd05 "hash_table->live_entries == 
0", file=0x7f45b170bce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f45b170be90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht 
erfüllt.
  UpgradeStatus: Upgraded to bionic on 2018-04-12 (2 days ago)
  UserGroups: adm libvirtd lxd sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764010/+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 1764195] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное утверждение «hash

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

** This bug is no longer a duplicate of private bug 1764019
** This bug has been marked a duplicate of bug 1763878
   gnome-shell-* assert failure: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Assertion `hash_table->live_entries == 0' failed.

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Проверочное утверждение «hash_table->live_entries == 0» не выполнено.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  сбой при установке расширений gnome-sheel

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное 
утверждение «hash_table->live_entries == 0» не выполнено.
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 01:43:37 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['dash-to-pa...@jderose9.github.com', 'mediapla...@patapon.info', 
'openweather-extens...@jenslody.de', 'topic...@phocean.net']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell-extension-prefs 
extension:///dash-to-pa...@jderose9.github.com
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f5778091622 , assertion=assertion@entry=0x7f5782807d05 
"hash_table->live_entries == 0", file=file@entry=0x7f5782807ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f5782807e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f5782807d05 "hash_table->live_entries == 
0", file=0x7f5782807ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f5782807e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Проверочное утверждение «hash_table->live_entries == 
0» не выполнено.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764195/+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 1764213] Re: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: ../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 ‘hash_table->live_entries == 0’

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

** This bug is no longer a duplicate of private bug 1764058
** This bug has been marked a duplicate of private bug 1763878

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

Title:
  gnome-shell-portal-helper assert failure: gnome-shell-portal-helper:
  ../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设
  ‘hash_table->live_entries == 0’ 失败。

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i dont`t konw how it happend,i only see the layout.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 
‘hash_table->live_entries == 0’ 失败。
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 09:09:15 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-14 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f87181c676b , assertion=assertion@entry=0x7f872c316d05 
"hash_table->live_entries == 0", file=file@entry=0x7f872c316ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f872c316e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f872c316d05 "hash_table->live_entries == 
0", file=0x7f872c316ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f872c316e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 
‘hash_table->live_entries == 0’ 失败。
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764213/+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 1764218] Re: /usr/lib/gnome-shell/gnome-shell-portal-helper:gnome-shell-portal-helper: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->live_

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

** This bug has been marked a duplicate of private bug 1763878

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

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-helper:gnome-shell-portal-
  helper: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Assertion `hash_table->live_entries == 0' failed.

Status in gnome-shell package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764218/+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 1764218] [NEW] /usr/lib/gnome-shell/gnome-shell-portal-helper:gnome-shell-portal-helper: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Assertion `hash_table->liv

2018-04-15 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: bionic

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

Title:
  /usr/lib/gnome-shell/gnome-shell-portal-helper:gnome-shell-portal-
  helper: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Assertion `hash_table->live_entries == 0' failed.

Status in gnome-shell package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764218/+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 1762794] Re: Can't complete purchases in GNOME Software

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

I set up a new account and that worked, so it looks like a legacy
account issue.

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

Title:
  Can't complete purchases in GNOME Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  (Using the PPA with the purchasing stuff in)

  With the release of a paid snap in the store I tried to buy it with
  GNOME Software starting on a fresh machine.  Here's what happened:

  * I search for and found the kiosc snap
  * Clicking on the details showed that it was priced at 9.99 USD
  * I click on the snap and was asked if I was sure I wanted to buy
  * I was asked to login to the store
  * I didnt have any credit card information and so Firefox opened and took me 
to the page to add a credit card, which I did, and then closed firefox.
  * I switched back to G-S and clicked on the 9.99 button again
  * I received an email from the store confirming my purchase
  * However - the snap was not installed. Click the button more times didn't 
result in more purchases, nor did it install the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762794/+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 1762794] Re: Can't complete purchases in GNOME Software

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

I reproduced and fixed the issue, so I'll mark this as a duplicate of
the main purchasing bug.

** This bug has been marked a duplicate of bug 1547135
   Support purchasing software

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

Title:
  Can't complete purchases in GNOME Software

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  (Using the PPA with the purchasing stuff in)

  With the release of a paid snap in the store I tried to buy it with
  GNOME Software starting on a fresh machine.  Here's what happened:

  * I search for and found the kiosc snap
  * Clicking on the details showed that it was priced at 9.99 USD
  * I click on the snap and was asked if I was sure I wanted to buy
  * I was asked to login to the store
  * I didnt have any credit card information and so Firefox opened and took me 
to the page to add a credit card, which I did, and then closed firefox.
  * I switched back to G-S and clicked on the 9.99 button again
  * I received an email from the store confirming my purchase
  * However - the snap was not installed. Click the button more times didn't 
result in more purchases, nor did it install the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1762794/+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 1760795] Re: gnome-software leaks file descriptors

Was released in snapd-glib 1.39-0ubuntu1

** Changed in: snapd-glib (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  gnome-software leaks file descriptors

Status in gnome-software package in Ubuntu:
  Invalid
Status in snapd-glib package in Ubuntu:
  Fix Released
Status in gnome-software source package in Bionic:
  Invalid
Status in snapd-glib source package in Bionic:
  Fix Released

Bug description:
  To verify the bug:
  1) killall gnome-software
  2) lsof -p $(pidof gnome-software) | wc -l
  3) Use gnome-software for a while (search for snaps, etc.)
  4) Again: lsof -p $(pidof gnome-software) | wc -l

  As you can seen the list of open files grows overtime.

  This (https://paste.ubuntu.com/p/rF5tHn5BwG/) also shows the problem,
  just compile it, get the pid and check with lsof the number of open
  files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1760795/+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 1764213] Re: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: ../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 ‘hash_table->live_entries == 0’

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

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 #1764058, 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/1764213/+attachment/5117259/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1764058

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

Title:
  gnome-shell-portal-helper assert failure: gnome-shell-portal-helper:
  ../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设
  ‘hash_table->live_entries == 0’ 失败。

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  i dont`t konw how it happend,i only see the layout.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 
‘hash_table->live_entries == 0’ 失败。
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 09:09:15 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-14 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f87181c676b , assertion=assertion@entry=0x7f872c316d05 
"hash_table->live_entries == 0", file=file@entry=0x7f872c316ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f872c316e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f872c316d05 "hash_table->live_entries == 
0", file=0x7f872c316ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f872c316e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-portal-helper assert failure: gnome-shell-portal-helper: 
../../../../src/cairo-hash.c:217：_cairo_hash_table_destroy: 假设 
‘hash_table->live_entries == 0’ 失败。
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (1 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764213/+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 1763892] Re: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

Thanks for the bug report. It's been a known issue for a while:
https://bugzilla.gnome.org/show_bug.cgi?id=781296

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

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=781296
   Importance: Unknown
   Status: Unknown

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

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

Title:
  144Hz/120Hz monitor but Wayland sessions seem to cap rendering at
  60FPS

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz.  On XOrg it  runs higher and feels much smoother.  I have
  confirmed the monitor is running at 144Hz during the Wayland session,
  and that is also the setting in the Settings control panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  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.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1763892/+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 1763273] Re: kernel panic in Radeon driver while screen blank

Further details from apport-bug are in #1764211; I'll copy them into
this account using my "cdarroch" personal Launchpad account in a few
hours, when I get home.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763273/+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 1764211] Re: apport bug details for #1763273 (radeon crash while screen blank)

When I get home I'll copy these attachments and data into the original
bug report under my personal Launchpad account.

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

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
  InstallationDate: Installed on 2017-07-24 (265 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JKT30AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
  dmi.product.name: 8811BJ8
  dmi.product.version: ThinkCentre M55
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 15 17:45:51 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764211/+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 1764211] [NEW] apport bug details for #1763273 (radeon crash while screen blank)

Public bug reported:

Unfortunately, I had to create a second bug report because apport-
collect will not accept a different set of Launchpad user credentials
from those I used to create the original bug report (#1763273).  My
apologies, but I had to use a different Launchpad account to run apport-
bug, so this is the result.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Apr 15 18:28:07 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
InstallationDate: Installed on 2017-07-24 (265 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT30AUS
dmi.board.name: LENOVO
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
dmi.product.name: 8811BJ8
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Apr 15 17:45:51 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

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

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest:

[Desktop-packages] [Bug 1252909] Re: Nautilus takes no notice of my selection in File --> Properties

** Changed in: nautilus (Ubuntu)
   Status: Invalid => Won't Fix

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

Title:
  Nautilus takes no notice of my selection in File --> Properties

Status in nautilus package in Ubuntu:
  Won't Fix

Bug description:
  1. Select directory.
  2. Go to File --> Properties.
  3. Nautilus shows properties of the wrong thing.

  Nautilus doesn't appear to have any idea what it's doing.

  Cut and Copy are also not an option so I've had to revert to the
  command line!

  Screenshots attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Wed Nov 20 01:03:12 2013
  GsettingsChanges:
   org.gnome.nautilus.window-state geometry '800x550+437+144'
   org.gnome.nautilus.window-state maximized true
   org.gnome.nautilus.window-state sidebar-width 235
   org.gnome.nautilus.window-state start-with-status-bar true
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1252909/+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 1763273] Re: kernel panic in Radeon driver while screen blank

** Attachment added: "Full kern.log from April 1 crash"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

[Desktop-packages] [Bug 1720552] Re: appstreamcli crashed with SIGSEGV in gvs_tuple_needed_size()

2018-04-15 Thread Matthias Klumpp

** Changed in: appstream (Ubuntu)
 Assignee: Matthias Klumpp (ximion) => (unassigned)

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

Title:
  appstreamcli crashed with SIGSEGV in gvs_tuple_needed_size()

Status in appstream package in Ubuntu:
  New

Bug description:
  Crashed, reset my screen but kept all documents open I had

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: appstream 0.11.3-1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  Date: Sat Sep 30 16:27:55 2017
  ExecutablePath: /usr/bin/appstreamcli
  InstallationDate: Installed on 2017-07-25 (67 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release i386 (20170412)
  ProcCmdline: appstreamcli refresh-cache
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xb7e0e0ba : 
pushl  (%eax)
   PC (0xb7e0e0ba) ok
   source "(%eax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "(%esp)" (0xbfaca794) ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: appstream
  StacktraceTop:
   g_variant_serialiser_needed_size () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_variant_serialiser_needed_size () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: appstreamcli crashed with SIGSEGV in g_variant_serialiser_needed_size()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1720552/+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 1740618] Re: Remove gksu from Ubuntu

** Description changed:

- The Debian GNOME team is aiming to remove gksu before the Debian 10
- "Buster" release in 2019.
+ Debian has removed gksu. I recommend that we remove gksu and libgksu for
+ Ubuntu 18.04 LTS also.
  
- Please remove these packages to help Ubuntu follow:
+ It has recommended that developers use PolicyKit to only use elevated
+ privileges for the specific actions where it is needed.
  
- * aptoncd: Removed from Debian Testing in January 2017 (a year ago), removal 
also requested at LP: #1739800
- * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
- * network-config: Removed from Debian Testing in September 2017
- 
- * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
- * sbackup: never in Debian, appears unmaintained upstream since 2014, removal 
also requested at LP: #1739800
- * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
+ It is recommended that users use the gvfs admin backend available in
+ Ubuntu 17.10 and 18.04 LTS. Instead of running gksu gedit or gksu
+ nautilus to edit say /etc/default/grub, navigate to
+ admin:///etc/default/ and open the grub file.
  
  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
- support gksu.
+ support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
+ as default but it is expected that Wayland will once again be the
+ default in 18.10.
  
- IMO, mythtv is the blocker for removing gksu from Ubuntu LP: #1740620
- (mythtv  does not exist in Debian)
+ $ reverse-depends src:gksu
+ Reverse-Recommends
+ ==
+ * cinnamon  (for gksu)
+ * lxde-core (for gksu)
+ * macchanger-gtk(for gksu)
+ * wicd-gtk  (for gksu)
+ * zenmap(for gksu)
+ 
+ Reverse-Depends
+ ===
+ * edubuntu-netboot  (for gksu)
+ * peony-gksu(for gksu)
+ * umit  (for gksu)
+ 
+ List of packages to remove and commentary
+ -
+ * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
+ * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
+ * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
+ * gksu
+ * libgksu
+ 
+ Blocker bug
+ ---
+ peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201
+ 
+ References
+ --
+ https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
+ https://bugs.debian.org/892768

** Also affects: macchanger-gtk (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  Debian has removed gksu. I recommend that we remove gksu and libgksu for
  Ubuntu 18.04 LTS also.
  
  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.
  
  It is recommended that users use the gvfs admin backend available in
- Ubuntu 17.10 and 18.04 LTS. Instead of running gksu gedit or gksu
- nautilus to edit say /etc/default/grub, navigate to
- admin:///etc/default/ and open the grub file.
+ Ubuntu 17.10 and 18.04 LTS. You can do this with the admin:// prefix.
+ For instance, instead of running gksu gedit or gksu nautilus to edit say
+ /etc/default/grub, navigate to admin:///etc/default/ and open the grub
+ file.
  
  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.
  
  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
  * cinnamon  (for gksu)
  * lxde-core (for gksu)
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)
  * zenmap(for gksu)
  
  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)
  
  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu
  
  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201
  
  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

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

Title:
  Remove gksu from Ubuntu

Status in edubuntu-netboot package in

[Desktop-packages] [Bug 1740618] Re: Remove gksu from Ubuntu

** Summary changed:

- Remove unmaintained gksu reverse dependencies
+ Remove gksu from Ubuntu

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

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

** No longer affects: macchanger-gtk (Ubuntu)

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

Title:
  Remove gksu from Ubuntu

Status in edubuntu-netboot package in Ubuntu:
  New
Status in gksu package in Ubuntu:
  New
Status in libgksu package in Ubuntu:
  New
Status in macchanger-gtk package in Ubuntu:
  New
Status in network-config package in Ubuntu:
  Fix Released
Status in sbackup package in Ubuntu:
  Fix Released
Status in umit package in Ubuntu:
  New

Bug description:
  Debian has removed gksu. I recommend that we remove gksu and libgksu
  for Ubuntu 18.04 LTS also.

  It has recommended that developers use PolicyKit to only use elevated
  privileges for the specific actions where it is needed.

  It is recommended that users use the gvfs admin backend available in
  Ubuntu 17.10 and 18.04 LTS. Instead of running gksu gedit or gksu
  nautilus to edit say /etc/default/grub, navigate to
  admin:///etc/default/ and open the grub file.

  Ubuntu 17.10's default session (a themed GNOME on Wayland) does not
  support gksu. Ubuntu 18.04 switched back to using X instead of Wayland
  as default but it is expected that Wayland will once again be the
  default in 18.10.

  $ reverse-depends src:gksu
  Reverse-Recommends
  ==
  * cinnamon  (for gksu)
  * lxde-core (for gksu)
  * macchanger-gtk(for gksu)
  * wicd-gtk  (for gksu)
  * zenmap(for gksu)

  Reverse-Depends
  ===
  * edubuntu-netboot  (for gksu)
  * peony-gksu(for gksu)
  * umit  (for gksu)

  List of packages to remove and commentary
  -
  * macchanger-gtk: Removed from Debian Testing in January 2017 for a security 
bug
  * edubuntu-netboot: never in Debian. Edubuntu is "on hold" since 2016.
  * umit: never in Debian, appears unmaintained upstream since at least 2014 
(maybe 2012?)
  * gksu
  * libgksu

  Blocker bug
  ---
  peony-gksu (source peony-extensions) was accepted into Ubuntu in April 2018. 
See LP: #1764201

  References
  --
  https://jeremy.bicha.net/2018/03/21/gksu-is-dead/
  https://bugs.debian.org/892768

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edubuntu-netboot/+bug/1740618/+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 938514] Re: gedit segfaults in gtk_tree_model_get_valist()

** Changed in: gtk
   Status: Incomplete => Expired

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

Title:
  gedit segfaults in gtk_tree_model_get_valist()

Status in GTK+:
  Expired
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Whilst the file open dialog was open, in another window i changed the
  filename of a file that was highlighted - gedit then crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: gedit 3.3.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
  Uname: Linux 3.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Wed Feb 22 09:22:17 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gedit
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: gedit
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f05b5535885 :
mov0x30(%rax),%rdx
   PC (0x7f05b5535885) ok
   source "0x30(%rax)" (0x0030) not located in a known VMA region (needed 
readable region)!
   destination "%rdx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gedit
  StacktraceTop:
   gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_entry_completion_compute_prefix () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   gtk_entry_completion_insert_prefix () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: gedit crashed with SIGSEGV in gtk_tree_model_get_valist()
  UpgradeStatus: Upgraded to precise on 2012-02-20 (1 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/938514/+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 1112496] Re: python-imaging broken in raring

2018-04-15 Thread ipatrol

** Patch added: "PIL/Pillow fix"
   
https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1112496/+attachment/5117196/+files/simple-image-reducer.diff

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

Title:
  python-imaging broken in raring

Status in Phatch:
  New
Status in comix package in Ubuntu:
  Invalid
Status in gwibber package in Ubuntu:
  Invalid
Status in ocrfeeder package in Ubuntu:
  Invalid
Status in phatch package in Ubuntu:
  Confirmed
Status in python-imaging package in Ubuntu:
  Fix Released
Status in simple-image-reducer package in Ubuntu:
  Fix Released
Status in wsjt package in Ubuntu:
  Invalid
Status in comix source package in Raring:
  Invalid
Status in gwibber source package in Raring:
  Invalid
Status in ocrfeeder source package in Raring:
  Invalid
Status in phatch source package in Raring:
  Won't Fix
Status in python-imaging source package in Raring:
  Fix Released
Status in simple-image-reducer source package in Raring:
  Invalid
Status in wsjt source package in Raring:
  Invalid

Bug description:
  python-imaging in raring doesn't include a PIL.pth to point python at
  the library, so attempts to import modules from the package fail with,
  eg:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  /usr/bin/python: No module named Image

  When the PIL.pth file is manually created, so python can find it, the
  Image module itself still fails to load:

  rachel@rarity:/etc$ python -m Image
  Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
  "__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
  exec code in run_globals
File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 75, in 
  from . import ImageMode
  ValueError: Attempted relative import in non-package

  The ImageMode module that line seems to be trying to import, however,
  seems to import fine by itself:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  ok

  (I've confirmed that ImageMode comes from the same place, as if I
  remove PIL.pth again, the above line just returns the "No module named
  ImageMode" error)

  I've tried reinstalling python-imaging already. I note in any case the
  PIL.pth file is missing on the file list available at
  packages.ubuntu.com for raring.

  This is on Ubuntu Raring as updated from Ubuntu Quantal a few days
  ago:

  rachel@rarity:/etc$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  rachel@rarity:/etc$ apt-cache policy python
  python:
Installed: 2.7.3-10ubuntu5
Candidate: 2.7.3-10ubuntu5
Version table:
   *** 2.7.3-10ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  rachel@rarity:/etc$ apt-cache policy python-imaging
  python-imaging:
Installed: 1.1.7+1.7.8-1ubuntu1
Candidate: 1.1.7+1.7.8-1ubuntu1
Version table:
   *** 1.1.7+1.7.8-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Affects me as it affects building/packaging XBMC post-frodo for
  raring. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/phatch/+bug/1112496/+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 1112496] Re: python-imaging broken in raring

2018-04-15 Thread ipatrol

Problem still exists in current repository version

** Changed in: simple-image-reducer (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: simple-image-reducer (Ubuntu)
 Assignee: (unassigned) => ipatrol (ipatrol6010)

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

Title:
  python-imaging broken in raring

Status in Phatch:
  New
Status in comix package in Ubuntu:
  Invalid
Status in gwibber package in Ubuntu:
  Invalid
Status in ocrfeeder package in Ubuntu:
  Invalid
Status in phatch package in Ubuntu:
  Confirmed
Status in python-imaging package in Ubuntu:
  Fix Released
Status in simple-image-reducer package in Ubuntu:
  Fix Released
Status in wsjt package in Ubuntu:
  Invalid
Status in comix source package in Raring:
  Invalid
Status in gwibber source package in Raring:
  Invalid
Status in ocrfeeder source package in Raring:
  Invalid
Status in phatch source package in Raring:
  Won't Fix
Status in python-imaging source package in Raring:
  Fix Released
Status in simple-image-reducer source package in Raring:
  Invalid
Status in wsjt source package in Raring:
  Invalid

Bug description:
  python-imaging in raring doesn't include a PIL.pth to point python at
  the library, so attempts to import modules from the package fail with,
  eg:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  /usr/bin/python: No module named Image

  When the PIL.pth file is manually created, so python can find it, the
  Image module itself still fails to load:

  rachel@rarity:/etc$ python -m Image
  Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main
  "__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
  exec code in run_globals
File "/usr/lib/python2.7/dist-packages/PIL/Image.py", line 75, in 
  from . import ImageMode
  ValueError: Attempted relative import in non-package

  The ImageMode module that line seems to be trying to import, however,
  seems to import fine by itself:

  rachel@rarity:/etc$ python -m ImageMode && echo ok
  ok

  (I've confirmed that ImageMode comes from the same place, as if I
  remove PIL.pth again, the above line just returns the "No module named
  ImageMode" error)

  I've tried reinstalling python-imaging already. I note in any case the
  PIL.pth file is missing on the file list available at
  packages.ubuntu.com for raring.

  This is on Ubuntu Raring as updated from Ubuntu Quantal a few days
  ago:

  rachel@rarity:/etc$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  rachel@rarity:/etc$ apt-cache policy python
  python:
Installed: 2.7.3-10ubuntu5
Candidate: 2.7.3-10ubuntu5
Version table:
   *** 2.7.3-10ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  rachel@rarity:/etc$ apt-cache policy python-imaging
  python-imaging:
Installed: 1.1.7+1.7.8-1ubuntu1
Candidate: 1.1.7+1.7.8-1ubuntu1
Version table:
   *** 1.1.7+1.7.8-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Affects me as it affects building/packaging XBMC post-frodo for
  raring. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/phatch/+bug/1112496/+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 1725928] Re: package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb'

** Changed in: sane-backends (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages
  with differing files  '/lib/udev/hwdb.d/20-sane.hwdb'

Status in sane-backends package in Ubuntu:
  Fix Released
Status in sane-backends package in Debian:
  Fix Released

Bug description:
  
  From #3 comment below, to get a workaround, try:

  sudo apt-get -o Dpkg::Options::="--force-overwrite" install
  --reinstall libsane1:i386 (or your real package name)

  ***
  Has been fixed with:

  sane-backends (1.0.27-1~experimental3ubuntu2) bionic; urgency=medium

* debian/rules: Drop timestamps from conflicting multiarch:same files
  hwdb.d/20-sane.hwdb and rules.d/60-libsane1.rules (closes: #880391)

   -- Adam Conrad  Sat, 03 Feb 2018 14:26:39 -0700
  ***

  apport error this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 22 09:37:46 2017
  DuplicateSignature:
   package:libsane1:1.0.27-1~experimental2ubuntu1
   Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-edJWJn/5-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb 
(--unpack):
    trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is 
different from other instances of package libsane1:i386
  ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  InstallationDate: Installed on 2016-10-08 (378 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
  UpgradeStatus: Upgraded to artful on 2017-10-20 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1725928/+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 1764202] [NEW] chromium-browser not drawing change when tab change after resume

2018-04-15 Thread Michinari Nukazawa

Public bug reported:

# reploduce
chromium open multi tab.
suspend and resume ubuntu.
chromium tab change.

# issue
Drawing of the contents of the tab is not updated even when tab switching is 
done. (Even in this state, the Chromium Web page title display switches 
normally.)

# workaround
After waiting for a while after switching the tab, the tab switch will operate 
normally.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 65.0.3325.181-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 16 09:14:10 2018
DetectedPlugins:
 
InstallationDate: Installed on 2018-03-04 (42 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ja_JP.UTF-8
 SHELL=/bin/bash
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  chromium-browser not drawing change when tab change after resume

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  # reploduce
  chromium open multi tab.
  suspend and resume ubuntu.
  chromium tab change.

  # issue
  Drawing of the contents of the tab is not updated even when tab switching is 
done. (Even in this state, the Chromium Web page title display switches 
normally.)

  # workaround
  After waiting for a while after switching the tab, the tab switch will 
operate normally.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 65.0.3325.181-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 09:14:10 2018
  DetectedPlugins:
   
  InstallationDate: Installed on 2018-03-04 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium-browser: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1764202/+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 1732530] Re: Dejadup is not working b/c duplicity is not installed

I'm marking as wontfix for ubuntu-meta for the same reason mentioned in
comment 5 here.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Dejadup is not working b/c duplicity is not installed

Status in ubuntu-mate:
  Invalid
Status in deja-dup package in Ubuntu:
  Won't Fix
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in ubuntukylin-meta package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 17.10

  Dejadup is not working b/c duplicity is not installed. After a manual
  install, Deja-Dup works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1732530/+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 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

I'm not sure why it seems to show for you in 16.04 but not for me, but
I'm going to propose we change the icon anyway.

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

** Also affects: gnome-software (Ubuntu Bionic)
   Importance: Medium
 Assignee: Robert Ancell (robert-ancell)
   Status: Confirmed

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

** Changed in: gnome-software (Ubuntu Artful)
   Status: New => Won't Fix

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

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

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

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

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Changed in: gnome-software (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Committed

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+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 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

** Branch linked: lp:~ubuntu-desktop/gnome-software/ubuntu

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Fix Committed
Status in gnome-software source package in Xenial:
  Fix Committed
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Committed

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+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 1681269] Re: Launcher Type=link, can not be opened with other application

2018-04-15 Thread Rob Peters

[Desktop Entry]
Encoding=UTF-8
Name=Calendar
Type=Link
URL=https://calendar.google.com/calendar/render?tab=mc#main_7
Icon=/home/rob/user1/Graphics/calendar.png

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

Title:
  Launcher Type=link, can not be opened with other application

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  If you right click on a desktop launcher and select an application to
  launch it e.g. Text Editor, some launchers do not populate the
  application. For example:

  [Desktop Entry]
  Encoding=UTF-8
  Name=Calendar
  Type=Link
  URL=https://calendar.google.com/calendar/render?tab=mc#main_7
  Icon=/home/rob/user1/Graphics/calendar.png

  This happens in both budgie and gnome shell on 17.04. If you change
  the file name from calendar.desktop to calendar.txt it works
  correctly.

  Secondly, if you look at the permissions for this type of launcher,
  you get the message "The permissions of "ServiceLogin" could not be
  determined."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  9 13:21:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'965x550+0+32'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
  InstallationDate: Installed on 2017-02-08 (60 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170208)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1681269/+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 1681269] Re: Launcher Type=link, can not be opened with other application

2018-04-15 Thread Rob Peters

OK, I had to go back and think about this for a moment  since I am no
longer on 17.04.  I have tested this issue on both Ubuntu as well as
Ubuntu Bodgie, both on 18.04 and the same thing is happening with
Nautilus as the default.

To duplicate the issue, take the desktop file below, save it to the desktop as 
calendar.desktop.
Then, right click on the file.  You should be able to open it with gedit.  
However, if it loads, gedit is empty or contains the last buffer from the 
previous file edited.  You can't set permissions on the desktop file with a 
right click e.g. set it executable.

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

Title:
  Launcher Type=link, can not be opened with other application

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  If you right click on a desktop launcher and select an application to
  launch it e.g. Text Editor, some launchers do not populate the
  application. For example:

  [Desktop Entry]
  Encoding=UTF-8
  Name=Calendar
  Type=Link
  URL=https://calendar.google.com/calendar/render?tab=mc#main_7
  Icon=/home/rob/user1/Graphics/calendar.png

  This happens in both budgie and gnome shell on 17.04. If you change
  the file name from calendar.desktop to calendar.txt it works
  correctly.

  Secondly, if you look at the permissions for this type of launcher,
  you get the message "The permissions of "ServiceLogin" could not be
  determined."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  9 13:21:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'965x550+0+32'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
  InstallationDate: Installed on 2017-02-08 (60 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170208)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1681269/+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 1764195] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное утверждение «hash

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

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 #1764019, 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/1764195/+attachment/5117128/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1764019

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Проверочное утверждение «hash_table->live_entries == 0» не выполнено.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  сбой при установке расширений gnome-sheel

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Проверочное 
утверждение «hash_table->live_entries == 0» не выполнено.
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 16 01:43:37 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['dash-to-pa...@jderose9.github.com', 'mediapla...@patapon.info', 
'openweather-extens...@jenslody.de', 'topic...@phocean.net']"
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  ProcCmdline: /usr/bin/gnome-shell-extension-prefs 
extension:///dash-to-pa...@jderose9.github.com
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f5778091622 , assertion=assertion@entry=0x7f5782807d05 
"hash_table->live_entries == 0", file=file@entry=0x7f5782807ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f5782807e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f5782807d05 "hash_table->live_entries == 
0", file=0x7f5782807ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f5782807e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Проверочное утверждение «hash_table->live_entries == 
0» не выполнено.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764195/+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 1763736] Re: communitheme snap not present in gnome software on bionic, but it is on 16.04

The short answer is the snap package doesn't have an icon set in the
store. Set that and it will show.

The longer answer is in 16.04 we use the "package-x-generic" icon, but
that doesn't seem to work anymore, I think due to GNOME Software having
changed the way it uses themes.

The generic icon support was dropped by upstream in the 18.04 version,
so we need to distro patch it back in.

I'll also look at using the new icon the store uses:
https://assets.ubuntu.com/v1/6fbb3483-snapcraft-default-snap-icon.svg

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

Title:
  communitheme snap not present in gnome software on bionic, but it is
  on 16.04

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 18.04, communitheme is not present in the logitheque. We can't find 
it in the available applications.
  snap search can find it

  on the other side, we can notice its presence in the logitheque of
  ubuntu 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1763736/+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 558841] Re: bluetooth "devices" menu item not working in bluetooth indicator

** Changed in: gtk
   Status: Incomplete => Expired

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

Title:
  bluetooth "devices" menu item not working in bluetooth indicator

Status in GTK+:
  Expired
Status in Application Indicators:
  Fix Released
Status in Application Indicators 0.1 series:
  Fix Released
Status in Application Indicators 0.2 series:
  Fix Released
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Lucid:
  Won't Fix
Status in gtk+2.0 source package in Lucid:
  Fix Released

Bug description:
  Binary package hint: gnome-bluetooth

  when clicking on bluetooth icon, i'm presented with a menu that has
  "devices" grayed out. as of lucid alpha3, this was working fine and
  would present me with a list of my bluetooth devices. however, this
  looks to be a regression introduced by the update I did on april 8th.

  if i click on preferences, i can browse, connect and disconnect
  devices just fine and they work; however, "devices" in the bluetooth
  indicator menu is still grayed out.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-bluetooth 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  Architecture: i386
  Date: Thu Apr  8 18:54:31 2010
  ExecutablePath: /usr/bin/bluetooth-applet
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/558841/+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 1764137] Re: [bionic][beta][nvidia] gnome-shell high cpu utilization

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

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

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

Title:
  [bionic][beta][nvidia] gnome-shell high cpu utilization

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  I am experiencing 60% - 200% CPU utilization after an upgrade from
  ubuntu artful to bionic.

  Pretty much any drawing results in a sluggish behavior due to high CPU
  utilization.

  The same combination of kernel/drivers did not result in the issue on
  17.10 so gnome-shell seems a good candidate to blame.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  Uname: Linux 4.16.0-041600-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:53:34 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  ---
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-02-27 (412 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 
[origin: unknown]
  PackageArchitecture: amd64
  Tags: third-party-packages bionic
  Uname: Linux 4.16.0-041600-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo 
systemd-journal ubridge
  _MarkForUpload: True

  ➜  ~ dpkg -l | grep -P 'ii.*?nvidia'
  ii  nvidia-390  
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA binary driver - version 390.48
  ii  nvidia-opencl-icd-390   
390.48-0ubuntu0~gpu17.10.2 amd64
NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.7 
 all  Tools to 
enable NVIDIA's Prime
  ii  nvidia-settings 
396.18-0ubuntu0~gpu17.10.1 amd64
Tool for configuring the NVIDIA graphics driver

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764137/+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 1764192] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung »hash_table->live

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

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 #1763909, 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/1764192/+attachment/5117106/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1763909

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy:
  Zusicherung »hash_table->live_entries == 0« nicht erfüllt.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  just happened

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: Zusicherung 
»hash_table->live_entries == 0« nicht erfüllt.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 23:30:38 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 
'ga...@base-art.net', 'cpuf...@nodefourtytwo.net', 
'openweather-extens...@jenslody.de', 'cpupo...@mko-sl.de', 
'Short_Memo@kusabashira', 'toggle-touch...@martin.kopta.eu']"
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs
  ProcEnviron:
   LANG=de_DE.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f2a9c0ba195 , assertion=assertion@entry=0x7f2aa6475d05 
"hash_table->live_entries == 0", file=file@entry=0x7f2aa6475ce8 
"../../../../src/cairo-hash.c", line=line@entry=217, 
function=function@entry=0x7f2aa6475e90 "_cairo_hash_table_destroy") at 
assert.c:92
   __GI___assert_fail (assertion=0x7f2aa6475d05 "hash_table->live_entries == 
0", file=0x7f2aa6475ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f2aa6475e90 "_cairo_hash_table_destroy") at assert.c:101
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: Zusicherung »hash_table->live_entries == 0« nicht 
erfüllt.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764192/+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 1314556] Re: Unable to mount Android MTP device

2018-04-15 Thread Albert Dean

need help this is what im getting as im running ubuntu 14.04 "Unable to open 
~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 16
Attempting to connect device
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
Unable to open raw device 0 
  

can someone give me some advice that can put me in the right direction and im 
also not the greatest 
while just learning linux and really likeing it.

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

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
 Found 1 device(s):
 Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+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 1764191] Re: shares-admin crashes when adding shares

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

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 #1731256, 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/1764191/+attachment/5117088/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1731256

** 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-system-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1764191

Title:
  shares-admin crashes when adding shares

Status in gnome-system-tools package in Ubuntu:
  New

Bug description:
  shares-admin crashes when I click on the "Add" button to add a share.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-tools 3.0.0-6ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Apr 15 22:35:22 2018
  ExecutablePath: /usr/bin/shares-admin
  InstallationDate: Installed on 2018-04-07 (8 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: shares-admin
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f41513cded0 :   
movzbl 0x14(%r8),%ecx
   PC (0x7f41513cded0) ok
   source "0x14(%r8)" (0x3f800bb4) not located in a known VMA region (needed 
readable region)!
   destination "%ecx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-system-tools
  StacktraceTop:
   g_type_check_instance_cast () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   share_settings_dialog_run_for_iter ()
   share_settings_dialog_run ()
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: shares-admin crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1764191/+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 1682436] Re: Location Options button gets stuck

I've reproduced the bug with Files 3.26 and the Files 3.28 Nightly
Flatpak on Ubuntu 17.10. I've filed the bug upstream:
https://gitlab.gnome.org/GNOME/nautilus/issues/367

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

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

Title:
  Location Options button gets stuck

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.04 with GNOME shell and Nautilus 3.14.3. I was able
  to reproduce this bug in a fresh 16.04 VM.

  After clicking the Location Options toggle (the hamburger menu) once,
  the button does not deactivate on subsequent clicks. See the attached
  image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1682436/+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 1764182] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

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 #1748450, 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/1764182/+attachment/5117015/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Happened on 1st logon after update 15/04/2018

  Ubuntu 18.04 beta.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr 15 10:42:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-03-19 (27 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180317)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764182/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-15 Thread Biswajit biswas

All things as mentioned above are garbage

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1764179] Re: gnome-shell crashed with signal 5

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

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 #1748450, 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/1764179/+attachment/5116994/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  For info...

  Pb with right buttom on mouse pad don't be recognize ... Right buttom put the 
same Action like left buttom. Since last update from 17.10 to 18.04. Works well 
with a standard mouse.
  My pc : ASUS GL753VD   core I7  7700  8GB Ram  NVidia GEForce 1050

  I use too ... A conky weather and Walch

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr 15 00:13:11 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-02-16 (422 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-04-12 (3 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764179/+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 1764178] Re: gnome-shell crashed with signal 5

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

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 #1748450, 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/1764178/+attachment/5116983/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  It crashed when i dragged a folder window.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr 15 12:18:03 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-11-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0
   _XIOError () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6
   () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764178/+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 1752053] Re: nvidia-390 fails to boot graphical display

2018-04-15 Thread chadotter

I upgraded to Bionic using a GeForce 950 and got a blank screen when
lightdm should have been visible. The only way I have been able to get
it working has been to delete /etc/X11/xorg.conf which was being used
before since my card was overclocked. If nvidia-xconfig is used later
and creates xorg.conf again the display breaks again until xorg.conf is
removed.

The actual text in xorg.conf was the same as what was working previously
with artful and nvidia-384.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1764177] Re: gnome-shell-extension-prefs assert failure: gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración `hash_table->l

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

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 #1763971, 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/1764177/+attachment/5116972/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1763971

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

Title:
  gnome-shell-extension-prefs assert failure: gnome-shell-extension-
  prefs: ../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La
  declaración `hash_table->live_entries == 0' no se cumple.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I don't really know what is wrong, but when I lock my screen the dock
  appears edge to edge in the bottom of the screen.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AssertionMessage: gnome-shell-extension-prefs: 
../../../../src/cairo-hash.c:217: _cairo_hash_table_destroy: La declaración 
`hash_table->live_entries == 0' no se cumple.
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 15 16:59:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell-extension-prefs
  InstallationDate: Installed on 2018-04-15 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  ProcCmdline: gnome-shell-extension-prefs dash-to-d...@micxgx.gmail.com
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   __assert_fail_base (fmt=0x7f858c260075 , 
assertion=assertion@entry=0x7f859ce20d05 "hash_table->live_entries == 0", 
file=file@entry=0x7f859ce20ce8 "../../../../src/cairo-hash.c", 
line=line@entry=217, function=function@entry=0x7f859ce20e90 
"_cairo_hash_table_destroy") at assert.c:92
   __GI___assert_fail (assertion=0x7f859ce20d05 "hash_table->live_entries == 
0", file=0x7f859ce20ce8 "../../../../src/cairo-hash.c", line=217, 
function=0x7f859ce20e90 "_cairo_hash_table_destroy") at assert.c:101
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
   cairo_debug_reset_static_data () from /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: gnome-shell-extension-prefs assert failure: 
gnome-shell-extension-prefs: ../../../../src/cairo-hash.c:217: 
_cairo_hash_table_destroy: La declaración `hash_table->live_entries == 0' no se 
cumple.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764177/+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 1657016] Re: Desktop icons zoom automatically if folder icons are zoomed

DimkaS that sounds like a separate issue, if you can find the issue on
Ubuntu 17.10 or 18.04 as well please could you report that as a bug with
`ubuntu-bug nautilus`? Thanks :)

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

Title:
  Desktop icons zoom automatically if folder icons are zoomed

Status in nautilus package in Ubuntu:
  New

Bug description:
  This is new to Ubuntu 16.10 (I have not experienced this earlier
  including in 16.04).

  I have set nautilus to show desktop icons (network, home)

  I open the home folder (it could be any file folder) and zoom in so
  that the icon size increases. Then I do show desktop and the desktop
  icons have zoomed as well!!

  THen I go to the home folder and zoom out. Desktop icons zoom out as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 17 12:41:25 2017
  InstallationDate: Installed on 2017-01-16 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1657016/+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 1657016] Re: Desktop icons zoom automatically if folder icons are zoomed

>From Files 3.28 onwards (3.28 is the latest upstream version and 3.30
will presumably be used in Ubuntu 18.10), desktop icons are handled by a
GNOME extension and not by Files. I have thus filed this bug against the
GNOME Extension, it is up to Ubuntu developers, not upstream, to fix the
bug (if they feel the behavior is not intended) in Files 3.26 and
earlier on earlier Ubuntu releases. They may want to wait first to see
what how GNOME treats the issue with the Extension, though :)

https://gitlab.gnome.org/csoriano/org.gnome.desktop-icons/issues/5

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

Title:
  Desktop icons zoom automatically if folder icons are zoomed

Status in nautilus package in Ubuntu:
  New

Bug description:
  This is new to Ubuntu 16.10 (I have not experienced this earlier
  including in 16.04).

  I have set nautilus to show desktop icons (network, home)

  I open the home folder (it could be any file folder) and zoom in so
  that the icon size increases. Then I do show desktop and the desktop
  icons have zoomed as well!!

  THen I go to the home folder and zoom out. Desktop icons zoom out as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 17 12:41:25 2017
  InstallationDate: Installed on 2017-01-16 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1657016/+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 1764176] Re: gnome-shell crashed with signal 5 in g_log_default_handler()

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

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 #1748450, 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/1764176/+attachment/5116959/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1748450
   gnome-shell crashed with SIGTRAP in _g_log_abort() from 
g_log_default_handler() from default_log_handler(message="Connection to 
xwayland lost") from g_logv() from g_log() from 

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

Title:
  gnome-shell crashed with signal 5 in g_log_default_handler()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm not aware of anything special done

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr 15 16:21:42 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2018-01-28 (77 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=sk_SK
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sk_SK.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764176/+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 1755986] Re: WiFi icon / settings gone from user menu

2018-04-15 Thread Dylan Borg

I get empty space isntead of them.

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

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+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 1681269] Re: Launcher Type=link, can not be opened with other application

Hi Rob can you clarify what's happening here? When I do this (Files 3.26
on Ubuntu 17.10) it opens the webpage in Text Editor (rather than the
launcher), is that the bug you're reporting and can you reproduce it on
Ubuntu 17.10 or 18.04? :) Marking Incomplete for now (please change to
New if you're able to reproduce on 14.04, 16.04, 17.10 or 18.04 and can
clarify the process of reproducing the bug here!) :)

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

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

Title:
  Launcher Type=link, can not be opened with other application

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  If you right click on a desktop launcher and select an application to
  launch it e.g. Text Editor, some launchers do not populate the
  application. For example:

  [Desktop Entry]
  Encoding=UTF-8
  Name=Calendar
  Type=Link
  URL=https://calendar.google.com/calendar/render?tab=mc#main_7
  Icon=/home/rob/user1/Graphics/calendar.png

  This happens in both budgie and gnome shell on 17.04. If you change
  the file name from calendar.desktop to calendar.txt it works
  correctly.

  Secondly, if you look at the permissions for this type of launcher,
  you get the message "The permissions of "ServiceLogin" could not be
  determined."

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: nautilus 1:3.20.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  9 13:21:05 2017
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'show-delete-permanently' b'true'
   b'org.gnome.nautilus.preferences' b'show-create-link' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'965x550+0+32'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'true'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'true'
  InstallationDate: Installed on 2017-02-08 (60 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Alpha amd64 (20170208)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1681269/+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 1755986] Re: WiFi icon / settings gone from user menu

2018-04-15 Thread Dylan Borg

I have two bonded NICS, on 17.10 the menu used to show both NICs each
with a connection name. In 18.04 the labels and respective icons are
gone.

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

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+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 1755986] Re: WiFi icon / settings gone from user menu

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

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

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

Title:
  WiFi icon / settings gone from user menu

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Recently, in the GNOME session, the WiFi icon vanished, and all that I
  get is the icon for connected network, which is odd. My other machine
  does not even seem to get that icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.27.92-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 15 06:59:07 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-03-14 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755986/+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 1513063] Re: trouble setting file association

Pretty sure this is fixed on Files 3.26 on Ubuntu 17.10. If you can
reproduce the bug on a supported Ubuntu release (14.04, 16.04, or 17.10)
or the development release (18.04) then, if the former, please post
asking for the bug to be marked as affecting the relevant series (e.g.
Xenial (for 16.04)) or, if the latter, please change the bug's status to
'New' and report upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues (though it's a problem
that I'm unable to reproduce it).

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

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

Title:
  trouble setting file association

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I want to set gedit as the default application for xml files. I alt-click an 
xml file, open properties, go to "Open With" tab. Chrome is the default for 
xml, I select "gedit" and press "Set as default". When I do, the selection goes 
back to Chrome and the file association remains with Chrome. 
  I tested this on Ubuntu 14.10 and 15.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: nautilus 1:3.14.2-0ubuntu9
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov  4 13:39:32 2015
  EcryptfsInUse: Yes
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-10-02 (32 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1513063/+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 1658484] Re: When I drag and drop a file, the animation doesn't look properly

PI can't reproduce this bug on Files 3.26 on Ubuntu 17.10. If you can
reproduce the bug on a supported Ubuntu release (14.04, 16.04, or 17.10)
or the development release (18.04) then, if the former, please post
asking for the bug to be marked as affecting the relevant series (e.g.
Xenial (for 16.04)) or, if the latter, please change the bug's status to
'New' and report upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues (though it's a problem
that I'm unable to reproduce it).

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

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

Title:
  When I drag and drop a file, the animation doesn't look properly

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  I have attached a screenshot that describe the problem :)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: evince 3.22.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 22 15:17:20 2017
  InstallationDate: Installed on 2017-01-08 (13 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: evince
  UpgradeStatus: Upgraded to zesty on 2017-01-21 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1658484/+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 1764174] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()