[Desktop-packages] [Bug 1694004] Re: [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

2018-03-30 Thread Simon Quigley
Unsubscribing the Ubuntu Sponsors Team; there's nothing to sponsor.

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

Title:
  [RFE] Add pidgin-otr to Pidgin Addons in GNOME Software

Status in pidgin-otr:
  Confirmed
Status in pidgin package in Ubuntu:
  New
Status in pidgin-otr package in Ubuntu:
  New

Bug description:
  Please consider adding the pidgin-otr plugin to Pidgin Addons in GNOME
  Software. It would make installing this plugin a lot easier for end-
  users. Currently, there is only a SIPE plugin in the list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pidgin-otr/+bug/1694004/+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-03-30 Thread siddesh kadam
i have tried the above link for Ubuntu 16.04 not working with nvidia
drivers (390) i have del 5558 and 920m graphics . (same flickering
screen ) , reverted back to nouveau drivers .

-- 
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 1745786] Re: package libreoffice-calc 1:4.2.8-0ubuntu5.2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

2018-03-30 Thread Launchpad Bug Tracker
[Expired for libreoffice (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  package libreoffice-calc 1:4.2.8-0ubuntu5.2 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  Date: Sat Jan 27 23:56:37 2018
  DuplicateSignature: package:libreoffice-calc:1:4.2.8-0ubuntu5.2:subprocess 
new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2018-01-21 (6 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.0.1ubuntu2.17
  SourcePackage: libreoffice
  Title: package libreoffice-calc 1:4.2.8-0ubuntu5.2 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2018-01-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1745786/+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 1745738] Re: deja-dup crashed with SIGSEGV in settings_backend_path_changed → g_settings_backend_invoke_closure → g_main_dispatch → g_main_context_dispatch → g_main_context_ite

2018-03-30 Thread Launchpad Bug Tracker
[Expired for deja-dup (Ubuntu) because there has been no activity for 60
days.]

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  deja-dup crashed with SIGSEGV in settings_backend_path_changed →
  g_settings_backend_invoke_closure → g_main_dispatch →
  g_main_context_dispatch → g_main_context_iterate

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  .

  https://errors.ubuntu.com/problem/d5ebdea594886fbf49caa5e9a29cc0d2c07ea816

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-0ubuntu2
  Uname: Linux 4.15.0-041500rc7-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 27 09:32:42 2018
  ExecutablePath: /usr/bin/deja-dup
  InstallationDate: Installed on 2017-11-08 (80 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/deja-dup --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f11ab3ae0ef:mov0x18(%rax),%rdi
   PC (0x7f11ab3ae0ef) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: deja-dup crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2017-11-20 (68 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  mtime.conffile..etc.xdg.autostart.org.gnome.DejaDup.Monitor.desktop: 
2017-11-13T08:07:54.070663

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1745738/+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 1760206] Re: Firefox cant install extensions from extensions.gnome.org

2018-03-30 Thread dino99
Steps to follow when a problem comes up:
- search a similar issue on the net; maybe you can fix it yourself.
- glance for help on ubuntuforums
- search and/or ask on askubuntu
- if its really a bug, then report it via the required script. Otherwise ask 
yourself if you are doing things the right way.


http://www.ubuntubuzz.com/2017/10/install-gnome-shell-extensions-on-ubuntu-artful.html

https://askubuntu.com/questions/5121/how-do-i-report-a-bug

Note: extensions are better installed via the ubuntu archive now, for
compatibility and avoid conflict/race with a different path. So run:
sudo rm -rf ~/.local/share/gnome-shell/extensions

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

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

Title:
  Firefox cant install extensions from extensions.gnome.org

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04 (Updated 30.03.18)
  Firefox 59.0.1
  I cant install gnome-shell extensions via firefox from extensions.gnome.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760206/+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 1759669] Re: Switch background uses gradients in backdrop mode

2018-03-30 Thread Adolfo Jayme
Fixed with ubuntu-themes 16.10+18.04.20180328-0ubuntu1

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switch background uses gradients in backdrop mode

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  On non focused windows elements should have no gradients or colors, switch 
still uses it:
  https://i.imgur.com/uLQMLZu.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1759669/+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 1760251] Re: unity-gnome-shell-migration.17.10.py crashed with signal 5

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1754623 ***
https://bugs.launchpad.net/bugs/1754623

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 #1754623, 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/1760251/+attachment/5096642/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-session in Ubuntu.
https://bugs.launchpad.net/bugs/1760251

Title:
  unity-gnome-shell-migration.17.10.py crashed with signal 5

Status in gnome-session package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  gnome-session:
Installed: 3.28.0-0ubuntu2
Candidate: 3.28.0-0ubuntu2
Version table:
   *** 3.28.0-0ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  Login takes a long time and eventually this script reports failure.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 21:17:28 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ExecutablePath: 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py
  InstallationDate: Installed on 2018-03-09 (21 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  InterpreterPath: /usr/bin/python3.6
  ProcCmdline: /usr/bin/python3 
/usr/share/session-migration/scripts/unity-gnome-shell-migration.17.10.py
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: gnome-session
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: unity-gnome-shell-migration.17.10.py crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-19 (11 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760251/+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 1724977] Re: two mouse cursors visible at the same time on rotated screen

2018-03-30 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Confirmed => Fix Released

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

Title:
  two mouse cursors visible at the same time on rotated screen

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in wayland package in Fedora:
  Unknown

Bug description:
  When my 2nd Asus (Ancor) display is in portrait mode and is set to be
  to the left of my centered landscape display in extended mode, moving
  the mouse to roughly the left 20% of my landscape display will show a
  mouse cursor on my landcape display AND portrait display at the same
  time.  Oddly moving a window into this area only shows on the
  landscape display.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 13:43:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203]
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230 Tablet
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  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/gnome-shell/+bug/1724977/+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 1760246] [NEW] nautilus does not obey display order after keyboard-find

2018-03-30 Thread Humphrey van Polanen Petel
Public bug reported:

When nautilus displays icons, the display is sorted horizontally.
However, when finding files by typing on the keyboard, to move the focus
 needs to be pressed rather then .

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 31 11:25:45 2018
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true'
 b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+1325+24'"
 b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 
'none']"
 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 2017-12-13 (107 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  nautilus does not obey display order after keyboard-find

Status in nautilus package in Ubuntu:
  New

Bug description:
  When nautilus displays icons, the display is sorted horizontally.
  However, when finding files by typing on the keyboard, to move the
  focus  needs to be pressed rather then .

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 31 11:25:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1235x472+1325+24'"
   b'org.gnome.nautilus.icon-view' b'captions' b"['date_modified', 'where', 
'none']"
   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 2017-12-13 (107 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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/1760246/+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 1759921] Re: printing system doesn't work

2018-03-30 Thread Carlos Rodriguez
I've installed Debian 9.4.0 with Gnome desktop and CUPS print server to
test, and it works OK, so the problem is in Ubuntu.

Thank again.

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

Title:
  printing system doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  My printer, Lexmark Optra E310, is configured automatically by the
  system and it worked perfectly in Linux until now. The Printer is OK,
  it works perfectly in Windows, but now in Linux everytime I try to
  print something, whatever it is, it prints the next messages on paper:

  ERROR:
  configurationerror
  OFFENDING COMMAND:
  setpagedevice
  STACK:
  --nostringval--
  false
  842
  595
  0
  0
  842
  595
  --nostringval--
  5

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4ubuntu0.4
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Mar 29 19:38:02 2018
  Lpstat: device for Lexmark-Optra-E310: 
usb://Lexmark/Optra%20E310?serial=5163293
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Papersize: a4
  PpdFiles: Lexmark-Optra-E310: Lexmark Optra E310 Foomatic/Postscript 
(recommended)
  ProcEnviron:
   LANGUAGE=es_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=6a60c9b5-8fd9-472c-95f2-6fb8dcdd7e1d ro splash quiet vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: N68-GS3 UCC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd09/19/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-GS3UCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1759921/+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 1042069] Re: Jumpy Mouse Cursor using Thinkpad X230 Touchpad

2018-03-30 Thread Tony Mobily
Well I just wanted to confirm that I switched back to Xorg and
unfortunately the hack to 50-synaptics.conf no longer works -- the mouse
is still jumpy

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

Title:
  Jumpy Mouse Cursor using Thinkpad X230 Touchpad

Status in xserver-xorg-input-synaptics package in Ubuntu:
  Expired

Bug description:
  Really annoying bug!

  Trackpoint moves the mouse cursor smootly,
  when using the touchpad i have a jumpy cursor. (vertically it moves fine, 
horizontally it moves always 4 pixels at once).

  Please see the following demonstration video:
  http://www.youtube.com/watch?v=XUVRKFUsAmc

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
  Uname: Linux 3.5.0-11-generic x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Date: Mon Aug 27 08:08:27 2012
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120824)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1042069/+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 1760240] [NEW] Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

2018-03-30 Thread Kirk Wolff
Public bug reported:

In all repositories there is a buffer-overrun in the function
gtk_rc_add_default_file(), where if the dynamic array
gtk_rc_default_files has exactly max_default_files entries, a NULL will
be written past the allocated memory.  The resize function does not
resize the null terminated array in this case, and address sanitizer
(and valgrind) detects a memory access violation in any code leading to
this function.

The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
{{{
  for (n = 0; n < max_default_files; n++) 
{
  if (gtk_rc_default_files[n] == NULL)
break;
}

  if (n == max_default_files)
{
  max_default_files += 10;
  gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
}
  
  gtk_rc_default_files[n++] = g_strdup (filename);
  gtk_rc_default_files[n] = NULL;
}}}

Proposed modified implementation is as follows:
{{{
  for (n = 0; n < (max_default_files-1); n++) 
{
  if (gtk_rc_default_files[n] == NULL)
break;
}

  if (n >= (max_default_files-1))
{
  max_default_files += 10;
  gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
}
  
  gtk_rc_default_files[n++] = g_strdup (filename);
  gtk_rc_default_files[n] = NULL;
}}}

This implementation should be changed in all branches:

https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Write past end of buffer in gtk/gtkrc.c gtk_rc_add_default_file

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  In all repositories there is a buffer-overrun in the function
  gtk_rc_add_default_file(), where if the dynamic array
  gtk_rc_default_files has exactly max_default_files entries, a NULL
  will be written past the allocated memory.  The resize function does
  not resize the null terminated array in this case, and address
  sanitizer (and valgrind) detects a memory access violation in any code
  leading to this function.

  The following code is in error ( from 
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596
 )
  {{{
for (n = 0; n < max_default_files; n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n == max_default_files)
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  Proposed modified implementation is as follows:
  {{{
for (n = 0; n < (max_default_files-1); n++) 
  {
if (gtk_rc_default_files[n] == NULL)
break;
  }

if (n >= (max_default_files-1))
  {
max_default_files += 10;
gtk_rc_default_files = g_renew (gchar*, gtk_rc_default_files, 
max_default_files);
  }

gtk_rc_default_files[n++] = g_strdup (filename);
gtk_rc_default_files[n] = NULL;
  }}}

  This implementation should be changed in all branches:

  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-updates/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/gtk+2.0/trusty-proposed/view/head:/gtk/gtkrc.c#L569
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise/view/head:/gtk/gtkrc.c#L590
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-updates/view/head:/gtk/gtkrc.c#L596
  
https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/gtk+2.0/precise-proposed/view/head:/gtk/gtkrc.c#L596

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

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

[Desktop-packages] [Bug 1760234] Re: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which

2018-03-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libfontconfig1-dev
  /fontconfig-devel.pdf.gz', which is different from other instances of
  package libfontconfig1-dev:i386

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was installing dependencies to compile wine git.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 23:51:17 2018
  DuplicateSignature:
   package:libfontconfig1-dev:2.12.6-0ubuntu1
   Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1760234/+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 1760233] This bug is a duplicate

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1751460 ***
https://bugs.launchpad.net/bugs/1751460

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 #1751460, 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.

** This bug has been marked a duplicate of bug 1751460
   [regression] deja-dup-monitor crashed with SIGSEGV in 
Gigacage::::operator()

** 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 deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1760233

Title:
  deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()

Status in deja-dup package in Ubuntu:
  New

Bug description:
  the back up crashed when it was automatically updating the Ubuntu
  software for my computer.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: deja-dup 37.1-2fakesync1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 18:45:28 2018
  ExecutablePath: /usr/lib/deja-dup/deja-dup-monitor
  InstallationDate: Installed on 2018-03-17 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
  ProcCmdline: /usr/lib/deja-dup/deja-dup-monitor
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f7c7e1190a8:movl   $0x0,(%rax)
   PC (0x7f7c7e1190a8) ok
   source "$0x0" ok
   destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: deja-dup
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   __pthread_once_slow (once_control=0x7f7c7e38002c, 
init_routine=0x7f7c753fb490 <__once_proxy>) at pthread_once.c:116
   Gigacage::ensureGigacage() () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::Heap::Heap(bmalloc::HeapKind, 
std::lock_guard&) () from 
/usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
   bmalloc::PerProcess::getSlowCase() () 
from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18
  Title: deja-dup-monitor crashed with SIGSEGV in __pthread_once_slow()
  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/deja-dup/+bug/1760233/+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 1760234] [NEW] package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', whi

2018-03-30 Thread TuroLate
Public bug reported:

I was installing dependencies to compile wine git.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
Architecture: amd64
Date: Fri Mar 30 23:51:17 2018
DuplicateSignature:
 package:libfontconfig1-dev:2.12.6-0ubuntu1
 Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~beta1
SourcePackage: fontconfig
Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libfontconfig1-dev
  /fontconfig-devel.pdf.gz', which is different from other instances of
  package libfontconfig1-dev:i386

Status in fontconfig package in Ubuntu:
  New

Bug description:
  I was installing dependencies to compile wine git.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfontconfig1-dev 2.12.6-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-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 23:51:17 2018
  DuplicateSignature:
   package:libfontconfig1-dev:2.12.6-0ubuntu1
   Unpacking libfontconfig1-dev:i386 (2.12.6-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MaYTZY/067-libfontconfig1-dev_2.12.6-0ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180330)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: fontconfig
  Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz', which is different 
from other instances of package libfontconfig1-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1760234/+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 1760231] ThreadStacktrace.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760231/+attachment/5096552/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760231/+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 1760231] Stacktrace.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760231/+attachment/5096550/+files/Stacktrace.txt

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760231/+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 1760231] StacktraceSource.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1760231/+attachment/5096551/+files/StacktraceSource.txt

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760231/+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 1760231] gnome-software crashed with signal 5 in g_main_context_new()

2018-03-30 Thread Apport retracing service
StacktraceTop:
 g_wakeup_new () at ../../../../glib/gwakeup.c:161
 g_main_context_new () at ../../../../glib/gmain.c:656
 start_sync (data=, data=) at 
snapd-client-sync.c:24
 snapd_client_get_interfaces_sync (client=client@entry=0x55c32bfd3580, 
plugs=plugs@entry=0x7fe8231667b0, slots=slots@entry=0x7fe8231667b8, 
cancellable=cancellable@entry=0x55c32a8f7e80, error=error@entry=0x7fe823166878) 
at snapd-client-sync.c:454
 gs_plugin_refine_app (plugin=plugin@entry=0x55c32a6cf910, 
app=app@entry=0x7fe81c112750, flags=flags@entry=2097184, 
cancellable=cancellable@entry=0x55c32a8f7e80, error=error@entry=0x7fe823166878) 
at ../plugins/snap/gs-plugin-snap.c:994

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760231/+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 1760230] Re: gnome-calendar crashed with SIGSEGV in gtk_image_clear()

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1754202 ***
https://bugs.launchpad.net/bugs/1754202

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 #1754202, 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/1760230/+attachment/5096525/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754202
   gnome-calendar crashed with SIGSEGV in gtk_image_reset()

** Tags removed: need-amd64-retrace

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  crashed on log out with weather

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Fri Mar 30 16:37:42 2018
  ExecutablePath: /usr/bin/gnome-calendar
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe7941d2667 :mov
0x28(%rdi),%rbp
   PC (0x7fe7941d2667) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () 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: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (10 days ago)
  UserGroups: sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1760230/+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 1760231] [NEW] gnome-software crashed with signal 5 in g_main_context_new()

2018-03-30 Thread Mantas Kriaučiūnas
Public bug reported:

Just installed latest bionic from cdimage.ubuntu.com/daily-live and
after installation installed aptitude and lots of other software with
aptitude from ppa:baltix-members ;)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-software 3.28.0-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 31 00:40:16 2018
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-limba   N/A
 gnome-software-plugin-snap3.28.0-0ubuntu7
ProcCmdline: /usr/bin/gnome-software --gapplication-service
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-software
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
 gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
Title: gnome-software crashed with signal 5 in g_main_context_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


** Tags: amd64 apport-crash bionic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Just installed latest bionic from cdimage.ubuntu.com/daily-live and
  after installation installed aptitude and lots of other software with
  aptitude from ppa:baltix-members ;)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 31 00:40:16 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-03-30 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180330)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_get_interfaces_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   gs_plugin_refine_app () from 
/usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1760231/+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 1760230] [NEW] gnome-calendar crashed with SIGSEGV in gtk_image_clear()

2018-03-30 Thread Jerry D,Hodge
Public bug reported:

crashed on log out with weather

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.28.0-1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Fri Mar 30 16:37:42 2018
ExecutablePath: /usr/bin/gnome-calendar
ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe7941d2667 :  mov
0x28(%rdi),%rbp
 PC (0x7fe7941d2667) ok
 source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-calendar
StacktraceTop:
 gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ()
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () 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: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
UpgradeStatus: Upgraded to bionic on 2018-03-20 (10 days ago)
UserGroups: sudo

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


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  crashed on log out with weather

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Fri Mar 30 16:37:42 2018
  ExecutablePath: /usr/bin/gnome-calendar
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fe7941d2667 :mov
0x28(%rdi),%rbp
   PC (0x7fe7941d2667) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () 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: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-03-20 (10 days ago)
  UserGroups: sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1760230/+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 1547127] Re: Guest account option - feature request

2018-03-30 Thread Gunnar Hjalmarsson
Latest(?) news about the topic:

https://community.ubuntu.com/t/brain-dump-on-guest-session-progress/3717

Bug #1742912 may be considered related.

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

Title:
  Guest account option - feature request

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1760203] Re: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1754924 ***
https://bugs.launchpad.net/bugs/1754924

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 #1754924, 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/1760203/+attachment/5096436/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754924
   gnome-control-center crashed with SIGSEGV in actualize_printers_list()

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

Title:
  gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

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

Bug description:
  Trying to set up samba printer (needed more software)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 16:11:27 2018
  ExecutablePath: /usr/bin/gnome-control-center
  ProcCmdline: gnome-control-center --overview
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x558a07f17311:mov0x90(%rbp),%rsi
   PC (0x558a07f17311) ok
   source "0x90(%rbp)" (0x0090) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
  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-control-center/+bug/1760203/+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-03-30 Thread Lysenko Denis
You may try this ppa https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa just updated driver from this rep on 18.04
and succesfully booted.

-- 
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 1661590] Re: GNOME Software only supports running one application from a snap

2018-03-30 Thread Simos Xenitellis 
** Tags removed: verification-done
** Tags added: verification-done-xenial

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
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 Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1754202 ***
https://bugs.launchpad.net/bugs/1754202

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 #1754202, 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/1760208/+attachment/5096457/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1754202
   gnome-calendar crashed with SIGSEGV in gtk_image_reset()

** 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-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1760208

Title:
  gnome-calendar crashed with SIGSEGV in gtk_image_clear()

Status in gnome-calendar package in Ubuntu:
  New

Bug description:
  Opened calendar by mistake. Tried to close it. This happened

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.28.0-1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 21:17:37 2018
  ExecutablePath: /usr/bin/gnome-calendar
  InstallationDate: Installed on 2017-09-27 (184 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-calendar --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7fcb129d1667 :mov
0x28(%rdi),%rbp
   PC (0x7fcb129d1667) ok
   source "0x28(%rdi)" (0x0028) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-calendar
  StacktraceTop:
   gtk_image_clear () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ()
   g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   () 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: gnome-calendar crashed with SIGSEGV in gtk_image_clear()
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (19 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-calendar/+bug/1760208/+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 1759043] Re: gdm3 disable-user-list does not work bionic

2018-03-30 Thread Gunnar Hjalmarsson
Thanks for the heads up, Jeremy. I think so too when looking at the
code; no reason to bother upstream.

** Summary changed:

- gdm3 disable-user-list does not work bionic
+ Consider simpler version of login-userlist-disable.page on Ubuntu

** Changed in: gnome-user-docs (Ubuntu)
   Importance: Undecided => Wishlist

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

** Also affects: ubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-docs (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-docs (Ubuntu)
   Status: New => Triaged

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

Title:
  Consider simpler version of login-userlist-disable.page on Ubuntu

Status in gnome-user-docs package in Ubuntu:
  Triaged
Status in ubuntu-docs package in Ubuntu:
  Triaged

Bug description:
  This how-to does not work on artful and bionic:
  
https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en

  GDM will always show the users list - even those logged remotely.
  There were a similar key for lightdm/unity that did work good.
  Version in use: gdm3 3.27.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1759043/+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 1760206] [NEW] Firefox cant install extensions from extensions.gnome.org

2018-03-30 Thread Ahmet Aksoy
Public bug reported:

Ubuntu 18.04 (Updated 30.03.18)
Firefox 59.0.1
I cant install gnome-shell extensions via firefox from extensions.gnome.org

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


** Tags: artful bionic

** Attachment added: "Screenshot from 2018-03-30 23-15-28.png"
   
https://bugs.launchpad.net/bugs/1760206/+attachment/5096456/+files/Screenshot%20from%202018-03-30%2023-15-28.png

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

Title:
  Firefox cant install extensions from extensions.gnome.org

Status in firefox package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 (Updated 30.03.18)
  Firefox 59.0.1
  I cant install gnome-shell extensions via firefox from extensions.gnome.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760206/+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 1197395] Re: /run/user/$ID/pulse owned by root and not by the user

2018-03-30 Thread Ccurtis0
With the caveat that I haven't followed the entire thread, I had a
similar problem today on an older 14.04 release: the owner of
/run/user/$id/pulse would "spontaneously" become root. Comment #34 says
this is easily reproducible when running pkexec/synaptic. I believe I
can explain - broadly - what is happening by describing what I can
confirm.

First, here is one way to reproduce the problem:
*) PulseAudio (v4 in this case) starts as a normal user.
*) As root (via sudo su -), run 'aplay --list-devices'
*) /run/user/$id/pulse is now owned by root.

Tracing 'aplay' I can see that it is dlopen()ing a bunch of pulseaudio
support libraries. *Somehow* they (the pulseaudio support libraries, I
presume) determine that pusleaudio is running. They extract a cookie
from /root/.config/cookie and try to connect to the server via
/run/user/$id/pulse/native socket.

At this point, I don't know what the code is trying to do, but what it
_does_ do is this:

mkdir("/run/user/1000/pulse", 0700) = -1 EEXIST (File exists)
open("/run/user/1000/pulse", O_RDONLY|O_NOCTTY|O_NOFOLLOW|O_CLOEXEC) = 5
fchown(5, 0, 0) = 0
fchmod(5, 0700) = 0
[...]
getuid()= 0
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 5
connect(5, {sa_family=AF_LOCAL, sun_path="/run/user/1000/pulse/native"}, 110) = 
-1 ENOENT (No such file or directory)
[...]

If my supposition is true that this is in the pulseaudio libraries, any
application running as root (like synaptic) is going to disable the
sound server when it tries to play audio through pulseaudio.

I scanned the pulseaudio changelogs and didn't see anything mentioning
this, but I can also confirm that Ubuntu 17.10 with pulseaudio version
10 and aplay version 1.1.3 does not do this. The older aplay version was
1.0.27.2.

In Ubuntu 17.10 pulseaudio is being run by 'gdm' but the same aplay
strace shows that it now looks for the socket in /var/run/pulse/native
instead of any particular UID in /run. It's unclear to me if the problem
is solved (in pulseaudio, if the culprit) or just band-aided by changing
the configuration (perhaps of ALSA integration with pulseaudio).

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

Title:
  /run/user/$ID/pulse owned by root and not by the user

Status in elementary OS:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Saucy:
  Invalid
Status in systemd source package in Saucy:
  Fix Released
Status in systemd package in Fedora:
  Won't Fix

Bug description:
  I'm experiencing this problem with Ubuntu Saucy. Some times, when I start a 
media player (I use Musique), it freezes, as it finds that it cannot write into 
/run/user/$ID/pulse.
  If I change the owner of that directory to me, the media player starts as 
usual and is able to play music.
  I've never had this problem with previous versions of Ubuntu.
  Someone says that running PulseAudio with the -D argument changes the owner 
of that directory, but I didn't try.

  This is before manually changing the owner of that directory:
  $ musique
  Failed to create secure directory (/run/user/1000/pulse): Permission denied+

  ... # it doesn't crash, it keeps waiting

  If needed:
  (dmesg attached)
  lspci:
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 
(rev 03)
  00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller 

[Desktop-packages] [Bug 1759043] Re: gdm3 disable-user-list does not work bionic

2018-03-30 Thread Fábio Lima
Yeah, I may have made a mistake. I've made many tryes before. And It only 
worked when I've undone all the procedures.
I guess editing greeter.dconf-defaults is much better too. It's safier and 
easier to make automated config across many installations.

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

Title:
  gdm3 disable-user-list does not work bionic

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  This how-to does not work on artful and bionic:
  
https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en

  GDM will always show the users list - even those logged remotely.
  There were a similar key for lightdm/unity that did work good.
  Version in use: gdm3 3.27.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1759043/+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] [NEW] ubuntu 18.04 GDM - missing icons and letters

2018-03-30 Thread Ahmet Aksoy
Public bug reported:

Ubuntu 18.04(Updated 30.03.2018)
System Language: Turkish
Please check screenshots

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

** Attachment added: "Screenshot 1"
   
https://bugs.launchpad.net/bugs/1760201/+attachment/5096434/+files/DSC_0552.JPG

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

Title:
  ubuntu 18.04 GDM - missing icons and letters

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04(Updated 30.03.2018)
  System Language: Turkish
  Please check screenshots

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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

2018-03-30 Thread Jeremy Bicha
** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: vte2.91 (Ubuntu)
   Importance: Undecided => High

** Changed in: vte2.91 (Ubuntu)
   Status: New => Confirmed

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1752299] Re: [RFE] Show snaps in "Recent Releases"

2018-03-30 Thread AsciiWolf
Same issue with applications listed in the categories. Snap packages are
not listed there.

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

Title:
  [RFE] Show snaps in "Recent Releases"

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Currently, there are no snap packages shown in the "Recent Releases"
  section in GNOME Software. Consider fixing this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1752299/+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 1759043] Re: gdm3 disable-user-list does not work bionic

2018-03-30 Thread Jeremy Bicha
Gunnar, I think /etc/gdm3/greeter.dconf-defaults might be unique to
Debian and Ubuntu.

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

Title:
  gdm3 disable-user-list does not work bionic

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  This how-to does not work on artful and bionic:
  
https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en

  GDM will always show the users list - even those logged remotely.
  There were a similar key for lightdm/unity that did work good.
  Version in use: gdm3 3.27.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1759043/+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 1760192] [NEW] Update gnome-screenshot to version 3.26

2018-03-30 Thread Ahmet Aksoy
Public bug reported:

bionic and artful still have gnome-screenshot 3.25. Please update to
3.26

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


** Tags: artful bionic

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

Title:
  Update gnome-screenshot to version 3.26

Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  bionic and artful still have gnome-screenshot 3.25. Please update to
  3.26

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1760192/+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 1643901] Re: flxdec security update tracking bug

2018-03-30 Thread Amr Ibrahim
** Changed in: gst-plugins-good1.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  flxdec security update tracking bug

Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good0.10 source package in Precise:
  Fix Released
Status in gst-plugins-good0.10 source package in Trusty:
  Fix Released
Status in gst-plugins-good1.0 source package in Trusty:
  Fix Released
Status in gst-plugins-good0.10 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Xenial:
  Fix Released
Status in gst-plugins-good1.0 source package in Yakkety:
  Fix Released
Status in gst-plugins-good1.0 source package in Zesty:
  Confirmed

Bug description:
  This bug is to track the security update to fix the flxdec out-of-
  bounds write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1643901/+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 1760190] [NEW] Useless icon themes

2018-03-30 Thread Ahmet Aksoy
Public bug reported:

Humanity-Dark
LoginIcons
Ubuntu-mono-dark
Ubuntu-mono-light
Hicolor

if i switch icons from these icons nothing happening.
I think these icons are no longer used in ubuntu.

And DMZ-Black, DMZ-White listing in icons

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1760190/+attachment/5096429/+files/Screenshot%20from%202018-03-30%2022-22-06.png

** Tags added: bionic

** Tags added: artful

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

Title:
  Useless icon themes

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Humanity-Dark
  LoginIcons
  Ubuntu-mono-dark
  Ubuntu-mono-light
  Hicolor

  if i switch icons from these icons nothing happening.
  I think these icons are no longer used in ubuntu.

  And DMZ-Black, DMZ-White listing in icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1760190/+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 1303531] Re: Fix for misplaced tooltips (upper-left corner) - upstream pending patch

2018-03-30 Thread Bug Watch Updater
** Changed in: gtk
   Status: Confirmed => Invalid

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

Title:
  Fix for misplaced tooltips (upper-left corner) - upstream pending
  patch

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

Bug description:
  Hi,

  Any chance this:

  https://bugzilla.gnome.org/show_bug.cgi?id=698730#c4

  could make it in?

  Current Gtk+3.0 has had a bug since Saucy where gtk tooltips will
  briefly appear in the upper left corner before repositioning to their
  proper location.

  I will do the legwork if necessary (as a quilt patch)

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1303531/+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 1759043] Re: gdm3 disable-user-list does not work bionic

2018-03-30 Thread Gunnar Hjalmarsson
Thank you, Fábio!

My guess is that you made some typo the first time, which speaks for the
documented way being error prone. So with this information, I'm thinking
of asking the GNOME help developers to consider to replace it with
showing how to edit /etc/gdm3/greeter.dconf-defaults. The latter way is
apparently easier and, probably, safer.

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

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

Title:
  gdm3 disable-user-list does not work bionic

Status in gnome-user-docs package in Ubuntu:
  New

Bug description:
  This how-to does not work on artful and bionic:
  
https://help.gnome.org/admin/system-admin-guide/stable/login-userlist-disable.html.en

  GDM will always show the users list - even those logged remotely.
  There were a similar key for lightdm/unity that did work good.
  Version in use: gdm3 3.27.92-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1759043/+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 1661590] Reminder of SRU verification policy change

2018-03-30 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to verify this stable release fix.  We
have noticed that you have used the verification-done tag for marking
the bug as verified and would like to point out that due to a recent
change in SRU bug verification policy fixes now have to be marked with
per-release tags (i.e. verification-done-$RELEASE).  Please remove the
verification-done tag and add one for the release you have tested the
package in.  Thank you!

https://wiki.ubuntu.com/StableReleaseUpdates#Verification

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
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 Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1661590/+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 1760187] [NEW] the sound is broken

2018-03-30 Thread Oscar
Public bug reported:

--2018-03-30 14:22:36--  http://www.alsa-project.org/alsa-info.sh
Resolviendo www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
Conectando con www.alsa-project.org (www.alsa-project.org)[77.48.224.243]:80... 
conectado.
Petición HTTP enviada, esperando respuesta... 302 Found
Ubicación: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [siguiente]
--2018-03-30 14:22:39--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
Resolviendo git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
Conectando con git.alsa-project.org (git.alsa-project.org)[77.48.224.243]:80... 
conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: no especificado [application/x-sh]
Grabando a: “alsa-info.sh”

alsa-info.sh[   <=>  ]  28,03K  33,9KB/sin
0,8s

2018-03-30 14:22:41 (33,9 KB/s) - “alsa-info.sh” guardado [28707]

chmod: cambiando los permisos de './alsa-info.sh': Operación no
permitida

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  the sound is broken

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  --2018-03-30 14:22:36--  http://www.alsa-project.org/alsa-info.sh
  Resolviendo www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
  Conectando con www.alsa-project.org 
(www.alsa-project.org)[77.48.224.243]:80... conectado.
  Petición HTTP enviada, esperando respuesta... 302 Found
  Ubicación: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [siguiente]
  --2018-03-30 14:22:39--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
  Resolviendo git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
  Conectando con git.alsa-project.org 
(git.alsa-project.org)[77.48.224.243]:80... conectado.
  Petición HTTP enviada, esperando respuesta... 200 OK
  Longitud: no especificado [application/x-sh]
  Grabando a: “alsa-info.sh”

  alsa-info.sh[   <=>  ]  28,03K  33,9KB/sin
  0,8s

  2018-03-30 14:22:41 (33,9 KB/s) - “alsa-info.sh” guardado [28707]

  chmod: cambiando los permisos de './alsa-info.sh': Operación no
  permitida

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1760187/+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 1760184] [NEW] rename command pops up dialog box

2018-03-30 Thread peterzay
Public bug reported:

rename command pops up a dialog box instead of allowing inline editing.

See attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.2-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 15:02:46 2018
ExecutablePath: /usr/bin/nautilus-desktop
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'890x542+989+135'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
InstallationDate: Installed on 2018-03-10 (19 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "rename command pops up a dialog box"
   
https://bugs.launchpad.net/bugs/1760184/+attachment/5096410/+files/Screenshot%20from%202018-03-30%2015-01-17.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/1760184

Title:
  rename command pops up dialog box

Status in nautilus package in Ubuntu:
  New

Bug description:
  rename command pops up a dialog box instead of allowing inline
  editing.

  See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.2-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 15:02:46 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x542+989+135'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'standard'"
  InstallationDate: Installed on 2018-03-10 (19 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1760184/+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 1164016] Re: restore type-ahead find

2018-03-30 Thread Henrik Holmboe
Perhaps a legit workaround: https://askubuntu.com/questions/980855/make-
nemo-produce-desktop-icons-gnome-3-26-1-on-ubuntu-17-10

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find

2018-03-30 Thread teo1978
> Anyway I did, like yesterday, and it got closed
> (can't find it right now [...])

Here:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find

2018-03-30 Thread teo1978
"not so well developed/maintained"? You mean worse than Nautilus??

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1693474] Re: Switches in Ambiance CSD headerbar are disproportionately big

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Switches in Ambiance CSD headerbar are disproportionately big

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  Look at the screenshot, is it expected for the switch in the top right
  corner to be so large?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20170518-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu May 25 12:36:16 2017
  InstallationDate: Installed on 2017-04-28 (26 days ago)
  InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 
(20170426)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+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 1759481] Re: Horizontal single-child disabled scale isn't properly themed

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Horizontal single-child disabled scale isn't properly themed

Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The last scale selector should be disabled in gtk3-widget-factory (cfr
  with Adwaita), but it's not:

  https://imgur.com/jLMa0Rd.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1759481/+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 1693609] Re: The "Minimize", " Maximize" and "Close" buttons are too small to click

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-themes -
16.10+18.04.20180328-0ubuntu1

---
ubuntu-themes (16.10+18.04.20180328-0ubuntu1) bionic; urgency=medium

  * Ambiance, Radiance: use static bg imgs for window buttons and add
padding (LP: #1693609)
  * Ambiance, Radiance: don't use any background image (gradient) when
in backdrop
  * Ambiance, Radiance: add more specific selectors for scale states
(LP: #1759481)
  * Ambiance, Radiance: set top and bottom margins for switch and
separators in headerbar (LP: #1693474)

 -- Marco Trevisan (Treviño)   Wed, 28 Mar 2018 06:27:32
+

** Changed in: ubuntu-themes (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  The "Minimize", " Maximize" and "Close" buttons are too small to click

Status in Ubuntu UX:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Fix Released

Bug description:
  The window control buttons ( _  X ) in Ambiance are noticeably
  smaller than other icon buttons in the headerbar of a "native" GNOME3
  app.

  I think this is both a visual issue and an accessibility issue since
  it is harder to click the window control buttons than the other
  buttons. Please compare with Adwaita which has a much larger click
  area for the window control buttons.

  Commentary
  --
  Remember that one of the major strengths of GNOME 3 is that it is usable on a 
touch-enabled laptop.

  And while there are many people that complain about Adwaita, I believe
  many more actually like the proportions and padding of the default
  GNOME theme!

  ubuntu-themes  16.10+17.10.20170518-0ubuntu1
  Ubuntu 17.10 Alpha

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1693609/+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 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-session - 3.28.0-0ubuntu2

---
gnome-session (3.28.0-0ubuntu2) bionic; urgency=medium

  * Add new communitheme session to the ubuntu session package. This
session only appears if the communitheme snap is installed. (LP: #1760049)
- debian/patches/50_ubuntu_sessions.patch, debian/ubuntu-session.install:
  generate and install session file.
- add Recommends on gtk adwaita and pixbuf theme engine.
- debian/rules: enable communitheme to override the default ubuntu-dock
  stylesheet from the snap.
- debian/rules: workaround for Xorg to pick up communitheme cursor theme
  from the snap.
  * Refresh debian/patches/revert_remove_gnome_session_properties.patch

 -- Didier Roche   Fri, 30 Mar 2018 11:03:17 +0200

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760049/+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 1741119] Re: Software App crashed while in the background - was installing MATE Desktop via terminal

2018-03-30 Thread Jean-Baptiste Lallement
** Information type changed from Private to Public

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

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

Title:
  Software App crashed while in the background - was installing MATE
  Desktop via terminal

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Software App crashed while in the background - was installing MATE
  Desktop via terminal

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.26.3-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  3 22:48:45 2018
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-01-02 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171209)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.26.3-2ubuntu1
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  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-software/+bug/1741119/+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 1758918] Re: Ubuntu-Budgie: unable to read filedescriptor flags for

2018-03-30 Thread Jeremy Bicha
Let's handle the gdebi issue in LP: #1756238

That only leaves your vte.sh issue.

Khurshid, it would help us handle this bug if you could start with a
clean install and then try to reproduce this bug. Then reply here with a
list of the steps you took to reproduce the bug. (Upgrading from 17.10
could be one of the steps if needed.)

** Summary changed:

- Ubuntu-Budgie: unable to read filedescriptor flags for https://bugs.launchpad.net/bugs/1758918

Title:
  Ubuntu-Budgie: could not found /etc/profile.d/vte.sh

Status in budgie-desktop package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Incomplete

Bug description:
  After upgrading libvte to latest release, When installing deb with
  gdebi, it shows following error:

  unable to read filedescriptor flags for https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+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 1760144] Re: Wrong size of icon, if launcher put on desktop

2018-03-30 Thread nmaxx
I noticed the same problem in Ubuntu MATE 18.04 beta 1, updated to the current 
state as of 2018-03-30.
The FF desktop icon is enormous. The huge icon also appears in the combo box of 
"Preferred Applications" for setting the default browser.
On my regular 16.04 installation it looks fine, though.

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

Title:
  Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  as off Firefox 59, if a launcher is put on desktop, its icon size is
  too large.

  The culprit may be a missing icons folder ?

  Testing on a liveUSB of Ubuntu 16.04.1 here I get :
  https://postimg.org/image/6t98217zt/
  left window is the liveUSB, right window is my actual 16.04 installation.

  Right after upgrading FF to newer version, I get :
  https://postimg.org/image/cu6wz42bt/
  left window is still the liveUSB.
  « icons » folder disappeared while upgrading FF
  and then instantly icon get much larger on desktop.

  It's not unity related : see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
  ://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
  static-desktop-icon/16205/3 or https://forum.ubuntu-
  fr.org/viewtopic.php?id=2023636

  The workarounds provided by those topics are not reliable fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+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 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-settings - 18.04

---
ubuntu-settings (18.04) bionic; urgency=medium

  * Add gsettings override for communitheme session (LP: #1760049)

 -- Didier Roche   Fri, 30 Mar 2018 17:29:10 +0200

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760049/+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 1760144] Re: Wrong size of icon, if launcher put on desktop

2018-03-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  as off Firefox 59, if a launcher is put on desktop, its icon size is
  too large.

  The culprit may be a missing icons folder ?

  Testing on a liveUSB of Ubuntu 16.04.1 here I get :
  https://postimg.org/image/6t98217zt/
  left window is the liveUSB, right window is my actual 16.04 installation.

  Right after upgrading FF to newer version, I get :
  https://postimg.org/image/cu6wz42bt/
  left window is still the liveUSB.
  « icons » folder disappeared while upgrading FF
  and then instantly icon get much larger on desktop.

  It's not unity related : see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
  ://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
  static-desktop-icon/16205/3 or https://forum.ubuntu-
  fr.org/viewtopic.php?id=2023636

  The workarounds provided by those topics are not reliable fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+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 1547127] Re: Guest account option - feature request

2018-03-30 Thread Mantas Kriaučiūnas
** Also affects: gdm3 (Baltix)
   Importance: Undecided
   Status: New

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

Title:
  Guest account option - feature request

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1760005] Re: Dialog 'add custom shortcut dialog' is unusable with keyboard only

2018-03-30 Thread Andrea Azzarone
Merged upstream. Will likely be fixed once gnome 3.28.1 is released.

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

Title:
  Dialog 'add custom shortcut dialog' is unusable with keyboard only

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end
  of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if
  used from keyboard.

  Current field order is: 'Name' -> 'Command' -> 'Cancel' button.
  Tab key switches focus only between these 3 fields. Arrow keys switch focus 
only between input fields.

  Expected field order:  'Name' -> 'Command' -> 'Set Shortcut...' ->
  'Add' button (if enabled) -> 'Cancel' button.

  =
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  =
  gnome-control-center:
Installed: 1:3.28.0-0ubuntu6
Candidate: 1:3.28.0-0ubuntu6
Version table:
   *** 1:3.28.0-0ubuntu6 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1: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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 10:03:23 2018
  InstallationDate: Installed on 2018-03-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760005/+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 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper

2018-03-30 Thread carlix
*** This bug is a duplicate of bug 1672297 ***
https://bugs.launchpad.net/bugs/1672297

** This bug has been marked a duplicate of bug 1672297
   gnome-shell uses lots of memory, and grows over time

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

Title:
  Gnome-Shell don't free ram when I change a wallpaper

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Sorry for my bad english, here is the link to see the error by
  yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+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 1547127] Re: Guest account option - feature request

2018-03-30 Thread Mantas Kriaučiūnas
** Tags added: artful bionic

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

Title:
  Guest account option - feature request

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gdm3 package in Baltix:
  New

Bug description:
  Though I didn't have it enabled for security reasons when I was using
  Unity, I think that some may find it useful to have a 'guest account'
  option, though I think that it should be off by default and be
  reasonably easy to configure in the gnome-control-center.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1547127/+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 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

2018-03-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760049/+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 1760049] Re: [UIFe] Optional (hidden by default) communitheme snap session

2018-03-30 Thread Launchpad Bug Tracker
** Branch linked: lp:~ubuntu-desktop/+junk/ubuntu-settings

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

Title:
  [UIFe] Optional (hidden by default) communitheme snap session

Status in gnome-session package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  This session isn't displayed and available in GDM by default.

  If the communitheme snap is installed, 2 new session options appears,
  selecting the corresponding theme (for GNOME Shell, sound, GTK2&3,
  cursor). All session/theme assets will be in the snap. We only expose
  here default gsettings settings, session files and extension override.

  There are 2 new strings for GDM:
  * Ubuntu with communitheme snap
  * Ubuntu with communitheme snap on Wayland

  
  This is to give the community a chance to get an easy glimpse of our next 
default theme, backed by the community.
  This doesn't impact any default UI has nothing will appear before you install 
the snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1760049/+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 1719462] Re: [Translation] "Left" and "Right" must be translated differently in different contexts

2018-03-30 Thread Gunnar Hjalmarsson
** Changed in: ubuntu-translations
   Status: Triaged => Fix Released

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

Title:
  [Translation] "Left" and "Right" must be translated differently in
  different contexts

Status in Ubuntu Translations:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released

Bug description:
  In 17.10 artful in GNOME Control Center, there are two places where
  words "Left" and "Right" are encountered: the Mouse settings and the
  Dock settings. Both of the words have only one item to translate in
  Rosetta with indication that they are located in two different places
  in the sources:

  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:4 
../panels/ubuntu/cc-ubuntu-panel.c:417"
  "Located in ../panels/mouse/gnome-mouse-properties.ui.h:5 
../panels/ubuntu/cc-ubuntu-panel.c:419"

  When translating in Russian, the words "Left" and "Right" must be translated 
differently in these two places. One translation for both contexts leads to 
inconsistent and ridiculous result.
  I can guess that this is also valid for some other languages, not only 
Russian.

  Please make two independent translations in Rosetta for "Left" and
  "Right" in these two different contexts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1719462/+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 1760144] [NEW] Wrong size of icon, if launcher put on desktop

2018-03-30 Thread Coeur Noir
Public bug reported:

Hi,

as off Firefox 59, if a launcher is put on desktop, its icon size is too
large.

The culprit may be a missing icons folder ?

Testing on a liveUSB of Ubuntu 16.04.1 here I get :
https://postimg.org/image/6t98217zt/
left window is the liveUSB, right window is my actual 16.04 installation.

Right after upgrading FF to newer version, I get :
https://postimg.org/image/cu6wz42bt/
left window is still the liveUSB.
« icons » folder disappeared while upgrading FF
and then instantly icon get much larger on desktop.

It's not unity related : see
https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https://ubuntu-
mate.community/t/firefox-v59-has-a-ridiculously-large-static-desktop-
icon/16205/3 or https://forum.ubuntu-fr.org/viewtopic.php?id=2023636

The workarounds provided by those topics are not reliable fixes.

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

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

Title:
  Wrong size of icon, if launcher put on desktop

Status in firefox package in Ubuntu:
  New

Bug description:
  Hi,

  as off Firefox 59, if a launcher is put on desktop, its icon size is
  too large.

  The culprit may be a missing icons folder ?

  Testing on a liveUSB of Ubuntu 16.04.1 here I get :
  https://postimg.org/image/6t98217zt/
  left window is the liveUSB, right window is my actual 16.04 installation.

  Right after upgrading FF to newer version, I get :
  https://postimg.org/image/cu6wz42bt/
  left window is still the liveUSB.
  « icons » folder disappeared while upgrading FF
  and then instantly icon get much larger on desktop.

  It's not unity related : see
  https://bugzilla.mozilla.org/show_bug.cgi?id=1446262 or https
  ://ubuntu-mate.community/t/firefox-v59-has-a-ridiculously-large-
  static-desktop-icon/16205/3 or https://forum.ubuntu-
  fr.org/viewtopic.php?id=2023636

  The workarounds provided by those topics are not reliable fixes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760144/+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 1760137] Re: libreoffice writer does not launch

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1726145 ***
https://bugs.launchpad.net/bugs/1726145

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 #1726145, 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/1760137/+attachment/5096174/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  libreoffice writer does not launch

Status in libreoffice package in Ubuntu:
  New

Bug description:
  It is only the writer function that does not launch (goes through the
  motions but crashes before displaying the window) all other functions
  (draw, impress etc) launch properly

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 30 15:46:54 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-03-12 (18 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha i386 
(20180311)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0xa7e46c15:movb   $0x0,(%eax)
   PC (0xa7e46c15) ok
   source "$0x0" ok
   destination "(%eax)" (0xbf7fcfe0) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   JNI_CreateJavaVM () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
  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/libreoffice/+bug/1760137/+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 1661590] Re: GNOME Software only supports running one application from a snap

2018-03-30 Thread Simos Xenitellis 
Hi!

On Ubuntu 16.04 (xenial) I enabled the `xenial-proposed` repository and
upgrade `gnome-software`.

$ apt policy gnome-software
gnome-software:
  Installed: 3.20.5-0ubuntu0.16.04.10
  Candidate: 3.20.5-0ubuntu0.16.04.10
  Version table:
 *** 3.20.5-0ubuntu0.16.04.10 400
400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 3.20.5-0ubuntu0.16.04.8 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

I launched `gnome-software` and located the `libreoffice` snap package.
I clicked on the Launch button.

WHAT HAPPENED: LibreOffice Base was launched (the wizard for Base to open a 
database).
When I do 'snap info libreoffice', libreoffice.base is the first in the list.

WHAT SHOULD HAPPEN: 
It should launch `libreoffice` instead.


** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  In Progress
Status in gnome-software package in Ubuntu:
  Fix Released
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 Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1661590/+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 1760129] [NEW] Tiny mouse cursor on hidpi screens after logging in

2018-03-30 Thread David Cesarino de Sousa
Public bug reported:

=== System comments

Lenovo Yoga 910 with 13.9" UHD screen.
Bionic Beta 1. 
Using 200% scaling.

=== Problem description

Mouse cursor size alternates between tiny size and normal size depending
on where I hover the cursor, tiny on top and left bars, normal on
desktop and everywhere else.

Of course I expected size to stay normal wherever I positioned the
cursor.

=== How to fix the problem

1. Wait for some time or event to pass (have no idea how much/which); AND
2. Click the mouse.

=== Other comments

Must meet both conditions 1 and 2 above in order to fix the issue. That
is, cursor size behavior is restored only immediatelly after clicking,
but also only after the click has happened after event 1 (and I have no
idea what that may be) has passed.

I have noticed this before on 17.10 as well when I briefly tested it
last year, but since 1) there are other bug reports dealing with it; and
2) I only use LTS releases anyway, I never got time to test and report
it.

This happens on a fresh install of Bionic beta 1. Also today with all
updated applied.

=== Required stuff (not sure if it is xorg, if not just ask me and I'll
post what you need)

david@buzz:~$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

david@buzz:~$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu5
  Candidate: 1:7.7+19ubuntu5
  Version table:
 *** 1:7.7+19ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 11:10:19 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.8, 4.15.0-12-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:3801]
InstallationDate: Installed on 2018-03-15 (15 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 003: ID 138a:0094 Validity Sensors, Inc. 
 Bus 001 Device 002: ID 5986:2104 Acer, Inc 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80VF
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=0bf3fe9c-33ec-4653-b53e-adc64d7b62a0 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JCN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Agera
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 910-13IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr2JCN39WW:bd05/31/2017:svnLENOVO:pn80VF:pvrLenovoYOGA910-13IKB:rvnLENOVO:rnAgera:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA910-13IKB:
dmi.product.family: IDEAPAD
dmi.product.name: 80VF
dmi.product.version: Lenovo YOGA 910-13IKB
dmi.sys.vendor: LENOVO
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

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


** Tags: amd64 apport-bug bionic reproducible ubuntu

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

Title:
  Tiny mouse cursor on hidpi screens after logging in

Status in xorg package in Ubuntu:
  New

Bug description:
  === System comments

  Lenovo Yoga 910 with 13.9" UHD screen.
  Bionic Beta 1. 
  Using 200% scaling.

  === Problem description

  Mouse cursor size alternates between tiny size and normal size
  depending on where I hover the cursor, tiny on top and left bars,
  normal on desktop and everywhere else.

  Of course I expected size to stay normal wherever I positioned the
  cursor.

  === How to fix the problem

  1. Wait for some time or event to pass (have no idea how much/which); AND
  2. 

[Desktop-packages] [Bug 1760123] Re: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1758651 ***
https://bugs.launchpad.net/bugs/1758651

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 #1758651, 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/1760123/+attachment/5096071/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1760123

Title:
  Xwayland crashed with signal 7 in mieqProcessDeviceEvent()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  This is happening regularly, and often results in crashing gnome-
  session too.  I _am not_ running Wayland!

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 30 10:11:06 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 4.15.0-12-generic, x86_64: installed
   acpi-call, 1.1.0, 4.15.0-13-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c]
  InstallationDate: Installed on 2018-03-12 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114)
  MachineType: LENOVO 20ARA0S100
  ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=1
  Signal: 7
  SourcePackage: xorg-server
  StacktraceTop:
   mieqProcessDeviceEvent ()
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55f2643e5aa0, argc=12, argv=0x7ffc3477f3b8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffc3477f3a8) at ../csu/libc-start.c:310
  Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440s
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO
  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
  

Re: [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() f

2018-03-30 Thread Martin D. Weinberg
I continue to see this problem on a daily basis, often after a resume
from suspend, I am not running Wayland, and this crashes my
gnome-session half the time, so something there is some confusion/bug
somewhere.  This morning's crash resulted in message from xorg-server so
I let apport file a bug against that package too (#1760123).


On 03/30/2018 06:38 AM, Amr Ibrahim wrote:
> There is a mix of duplicates with and without Wayland. Mine was without
> Wayland.
>

-- 
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039

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

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 1760115] Stacktrace.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760115/+attachment/5096055/+files/Stacktrace.txt

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

Title:
  gnome-system-monitor crashed with SIGABRT

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

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1760115] gnome-system-monitor crashed with SIGABRT

2018-03-30 Thread Apport retracing service
StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
 __cxxabiv1::__terminate(void (*)()) () at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
 std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:57
 __cxxabiv1::__cxa_throw (obj=obj@entry=0x55de6d05fa30, tinfo=0x55de6c398dd0 
, tinfo@entry=0x7fb91a6ed760 , dest=dest@entry=0x7fb91a4bd060 
) at 
../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:95
 Glib::RegexError::throw_func (gobject=0x55de6d05d010) at regex.cc:318

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

Title:
  gnome-system-monitor crashed with SIGABRT

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

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1760115] ThreadStacktrace.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760115/+attachment/5096057/+files/ThreadStacktrace.txt

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

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

** Tags removed: need-amd64-retrace

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

Title:
  gnome-system-monitor crashed with SIGABRT

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

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1760115] StacktraceSource.txt

2018-03-30 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1760115/+attachment/5096056/+files/StacktraceSource.txt

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

Title:
  gnome-system-monitor crashed with SIGABRT

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

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1760117] [NEW] software-properties-gtk installs canonical-livepatch from edge

2018-03-30 Thread Andrea Azzarone
Public bug reported:

software-properties installs canonical-livepatch from edge. Switch to
stable before release.

** Affects: software-properties (Ubuntu)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: In Progress

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

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

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

** Package changed: gnome-software (Ubuntu) => software-properties
(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/1760117

Title:
  software-properties-gtk installs canonical-livepatch from edge

Status in software-properties package in Ubuntu:
  In Progress

Bug description:
  software-properties installs canonical-livepatch from edge. Switch to
  stable before release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1760117/+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 1760113] [NEW] System does not display video after waking up from sleep

2018-03-30 Thread Daniel
Public bug reported:

Hello,

I'm using the latest daily development snapshot iso of Ubuntu Bionic
Beaver.

My issue is that after issuing a sleep command with systemctl suspend
-i, the system cannot doesn't display any video or seems to work at all
when waking it up. It does detect the keypress of my keyboards, because
the fans will start spinning up and the HDD LED will flicker, confirming
that it did wake up, but I can't do anything with it. All I could do was
to shut off the computer entirely with my hardware button.

As this was my first bug report I'm willing to provide any more
debugging information, I just don't know how. I'm using a desktop
computer and I'm certain the motherboard supports this sleep state and
it worked fine in previous versions of several linux distros. I blamed
the error to xorg in particular because it seems to be waking up, it
just won't start up my screens.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-13ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 15:47:01 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GM206 [GeForce GTX 950] [1458:36c5]
InstallationDate: Installed on 2018-03-30 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=cf158901-6c71-4345-89dd-371337d8426a ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88TD-V EVO/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88TD-VEVO/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
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.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

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


** Tags: amd64 apport-bug bionic regression reproducible ubuntu

** Description changed:

  Hello,
  
  I'm using the latest daily development snapshot iso of Ubuntu Bionic
  Beaver.
  
  My issue is that after issuing a sleep command with systemctl suspend
  -i, the system cannot doesn't display any video or seems to work at all
  when waking it up. It does detect the keypress of my keyboards, because
  the fans will start spinning up and the HDD LED will flicker, confirming
  that it did wake up, but I can't do anything with it. All I could do was
  to shut off the computer entirely with my hardware button.
  
  As this was my first bug report I'm willing to provide any more
 

[Desktop-packages] [Bug 1760114] [NEW] Misleading Error Message when changing uppercase/lowercase on a FAT/NTFS partition.

2018-03-30 Thread darksiderobot
Public bug reported:

If there is a file/folder on a FAT/NTFS partition e.g. with the name
"aBcde", you cannot rename it to "abCde", but you can rename it to
something else and then to "abCde". This bug not only appears when using
the command line, but also when using nautilus.


How to reproduce: Execute these commands on a FAT/NTFS partition:
$ ls
$ mkdir aBcde
$ ls
aBcde
$ mv aBcde abCde
mv: cannot move 'aBcde' to a subdirectory of itself, 'abCde/aBcde'
$ ls
aBcde
$ mv aBcde test
$ mv test abCde
$ ls
abCde

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 30 15:32:24 2018
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2017-07-28 (245 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 LANGUAGE=de_DE
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SourcePackage: nautilus
UpgradeStatus: Upgraded to artful on 2017-10-19 (161 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  Misleading Error Message when changing uppercase/lowercase on a
  FAT/NTFS partition.

Status in nautilus package in Ubuntu:
  New

Bug description:
  If there is a file/folder on a FAT/NTFS partition e.g. with the name
  "aBcde", you cannot rename it to "abCde", but you can rename it to
  something else and then to "abCde". This bug not only appears when
  using the command line, but also when using nautilus.


  How to reproduce: Execute these commands on a FAT/NTFS partition:
  $ ls
  $ mkdir aBcde
  $ ls
  aBcde
  $ mv aBcde abCde
  mv: cannot move 'aBcde' to a subdirectory of itself, 'abCde/aBcde'
  $ ls
  aBcde
  $ mv aBcde test
  $ mv test abCde
  $ ls
  abCde

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 15:32:24 2018
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2017-07-28 (245 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to artful on 2017-10-19 (161 days ago)

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

2018-03-30 Thread Apport retracing service
*** This bug is a duplicate of bug 1741119 ***
https://bugs.launchpad.net/bugs/1741119

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 #1741119, 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/1760109/+attachment/5095985/+files/CoreDump.gz

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

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

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

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

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

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

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

** 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-software in Ubuntu.
https://bugs.launchpad.net/bugs/1760109

Title:
  gnome-software crashed with signal 5 in g_main_context_new()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Happens constantly while installations from terminal are under way.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.0-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 15:13:59 2018
  ExecutablePath: /usr/bin/gnome-software
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.28.0-0ubuntu7
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.0-0ubuntu7
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  Signal: 5
  SourcePackage: gnome-software
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   snapd_client_find_section_sync () from 
/usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/gs-plugins-11/libgs_plugin_snap.so
  Title: gnome-software crashed with signal 5 in g_main_context_new()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1760109/+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 1760115] [NEW] gnome-system-monitor crashed with SIGABRT

2018-03-30 Thread nabin
Public bug reported:

Ubuntu 18.04 beta

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-system-monitor 3.28.0-1
Uname: Linux 4.15.12-041512-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 30 19:44:31 2018
ExecutablePath: /usr/bin/gnome-system-monitor
ProcCmdline: gnome-system-monitor
Signal: 6
SourcePackage: gnome-system-monitor
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
Title: gnome-system-monitor crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

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


** Tags: amd64 apport-crash bionic need-amd64-retrace third-party-packages

** Information type changed from Private to Public

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

Title:
  gnome-system-monitor crashed with SIGABRT

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

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1649428] Re: Cannot open file from https location (URL)

2018-03-30 Thread Paulo Marcel Coelho Aragão
I'm running Xubuntu 17.10 with gimp 2.8.20 and I still can't open https
URLs with gimp. According to this upstream bug report:

https://bugzilla.gnome.org/show_bug.cgi?id=782319

gimp 2.8 should be able to open https URLs as long as glib-networking is
installed, here I quote that bug report:

> If it is installed while not working, it probably means it is not found at 
> runtime for a reason
> which pertains to how the system is set up.

I have glib-networking 2.54.0-1 installed but I still can't open https
URLs, so there's something wrong with the build and/or packaging.

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

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

Title:
  Cannot open file from https location (URL)

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  If I try, I get this GIMP message:

Opening 'https://[...]' failed:

Could not load 'https://[...]': Failed to open file 'https://[...]':
  open() failed: No such file or directory

  Most of the time, I can manually edit the URL to read http://[...] and
  I can open the document as expected.

  The bug is a security vulnerability because it forces users to use
  unsecure communication.

  $ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  $ apt-cache policy gimp
  gimp:
Installed: 2.8.16-1ubuntu1.1
Candidate: 2.8.16-1ubuntu1.1
Version table:
   *** 2.8.16-1ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.8.16-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1649428/+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 1689356] Re: UI scale being reset to 1 everytime when display sleeps for a while

2018-03-30 Thread Park Ju Hyung
Awesome, thanks for the confirmation :)

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

Title:
  UI scale being reset to 1 everytime when display sleeps for a while

Status in compiz package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.04,
  the HiDPI setting(Scale for menu and title bars)
  is being reset to 1 everytime when display sleeps for a while,
  making everything looks small.

  If the display sleeps and I resume it instantly, it's fine,
  but if the display slept for long, the HiDPI setting gets reset to 1.

  My guess is that if a display is plugged in(detected), the old DPI
  setting is not restored.

  This issue is not present on previous Ubuntu versions
  and the same issue persists even after a fresh install.

  *-*
  This bug is now present also in 16.04 since a recent update, experiencing 
this in Xenial since 23 Feb 2018 at least. We could trace the cause of the bug 
in the recent backports/bugfix updates to Xenial.
  *-*

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  Uname: Linux 4.10.14-zen+ x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Tue May  9 02:08:25 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 375.66, 4.10.14-zen+, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1080] [1043:85aa]
   Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] 
[1002:6658] (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Bonaire XTX [Radeon R7 260X/360] 
[1458:227b]
  InstallationDate: Installed on 2017-05-06 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.14-zen+ 
root=UUID=e1130f0b-d82f-4976-989f-c8b18f0965eb ro intel_iommu=on 
vfio_iommu_type1.allow_unsafe_interrupts=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3402
  dmi.board.asset.tag: Default string
  dmi.board.name: X99-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3402:bd08/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  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.14-0ubuntu1
  xserver.bootTime: Tue May  9 00:26:57 2017
  

[Desktop-packages] [Bug 1759758] Re: gsd-locate-pointer crashed with signal 5 in _XEventsQueued()

2018-03-30 Thread DigitalFiz
This has been a recurring problem since 2010? Can we just have someone
look at it a tiny little bit please?

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

Title:
  gsd-locate-pointer crashed with signal 5 in _XEventsQueued()

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  -

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-settings-daemon 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 14:18:10 2018
  ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-locate-pointer
  InstallationDate: Installed on 2018-03-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-locate-pointer
  Signal: 5
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gsd-locate-pointer crashed with signal 5 in _XEventsQueued()
  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-settings-daemon/+bug/1759758/+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 1164016] Re: restore type-ahead find

2018-03-30 Thread Serge
Unfortunately this is really a deal-breaker for me and forces me to drop
Nautilus and experiment with other, perhaps not so well
developed/maintained, GUI file managers. What a pity.

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

Title:
  restore type-ahead find

Status in Nautilus:
  Expired
Status in nautilus package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  GNOME removed type-ahead find in Nautilus 3.6, not without
  controversy:

  https://mail.gnome.org/archives/nautilus-
  list/2012-August/msg2.html

  Now when you type in a Nautilus window, Nautilus immediately performs
  a search in the current directory and all its subdirectories.  I
  personally find this annoying.  If I want to search, I'll click the
  search icon.  Often I'm looking at a long directory listing and simply
  want to jump to a certain point in it, and type-ahead find works great
  for that.

  Would Ubuntu consider patching type-ahead find back in?

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-03-30 Thread Jarno Suni
Brian, I tested the update-manager version you told. It is true that
update-manager removes the unused packages, but step 3. (unattended-
upgrades) does not remove the unused kernels.

I add failed tag as this bug is originally about unattended-upgrades.

** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

 sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]
   
  The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1758247] Re: gnome-control-center is not open ubuntu 18.04

2018-03-30 Thread Andrea Azzarone
*** This bug is a duplicate of bug 1755536 ***
https://bugs.launchpad.net/bugs/1755536

** This bug has been marked a duplicate of bug 1755536
gnome-control-center is not open ubuntu 18.04

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

Title:
  gnome-control-center is not open ubuntu 18.04

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

Bug description:
  it is not openning and stuck

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu3
  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: ubuntu:GNOME
  Date: Fri Mar 23 13:13:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-03-04 (384 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1758247/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

2018-03-30 Thread Jarno Suni
Testing is painfully slow because connection to e.g.
archive.canonical.com is very slow.

Downgrading in step 2 does not work without --allow-downgrades

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in update-manager source package in Xenial:
  Fix Committed
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.

  [Test Case]

   1. Install kernel packages to be removed, mark them auto-installed
  and run apt's kernel hook script to make apt consider them
  autoremovable:

sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
sudo /etc/kernel/postinst.d/apt-auto-removal

   2. Also downgrade a package to be upgraded:

 sudo apt-get install -y ca-certificates=20160104ubuntu1

   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.

sudo update-manager

   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.

   3. (unattended-upgrades) Run unattended-upgrades manually and observe
  the removal of the autoremovable kernel packages:

sudo unattended-upgrade -v

  [Regression Potential]

   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.

  [Other Info]
   
  The unattended-upgrades fix is uploaded with many other fixes and those may 
cause regressions in other areas in unattended-upgrades.

  [Original bug text]

  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+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 1760005] Re: Dialog 'add custom shortcut dialog' is unusable with keyboard only

2018-03-30 Thread Andrea Azzarone
Fix proposed upstream: https://gitlab.gnome.org/GNOME/gnome-control-
center/merge_requests/20

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

Title:
  Dialog 'add custom shortcut dialog' is unusable with keyboard only

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end
  of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if
  used from keyboard.

  Current field order is: 'Name' -> 'Command' -> 'Cancel' button.
  Tab key switches focus only between these 3 fields. Arrow keys switch focus 
only between input fields.

  Expected field order:  'Name' -> 'Command' -> 'Set Shortcut...' ->
  'Add' button (if enabled) -> 'Cancel' button.

  =
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  =
  gnome-control-center:
Installed: 1:3.28.0-0ubuntu6
Candidate: 1:3.28.0-0ubuntu6
Version table:
   *** 1:3.28.0-0ubuntu6 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1: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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 10:03:23 2018
  InstallationDate: Installed on 2018-03-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760005/+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 1760088] [NEW] Can't click Apply using display panel, with 2 screen

2018-03-30 Thread Jean-Francois Bourdeau
Public bug reported:

Just reinstalled my Main production PC on 18.04 ( I like to live
dangerously)… Though that if it was my production computer, I would be
more useful to you ( reporting bugs)

If I use the display tool to change resolution with 2 screen :

if I change the 1st screen display, I can’t hit Apply
I need to click the 2nd display to click apply…

Most people will normally change the resolutation to be the same on both
display, but in case some people want different screen resolution, it
could be normal ( if simple to code) that if we change one of the
display resolution only, that we don’t have to click the 2nd display to
CLICK APPLY

I don’t care if fixed or not but reporting it… As I want to make your
project better that Winwos and Mac OS LOL

JF
18.04 is a lot faster on my i7 computer, 8 gig with SSD hard drive…

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.0-0ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Fri Mar 30 08:23:26 2018
InstallationDate: Installed on 2018-03-29 (0 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180324)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Can't click Apply using display panel, with 2 screen

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

Bug description:
  Just reinstalled my Main production PC on 18.04 ( I like to live
  dangerously)… Though that if it was my production computer, I would be
  more useful to you ( reporting bugs)

  If I use the display tool to change resolution with 2 screen :

  if I change the 1st screen display, I can’t hit Apply
  I need to click the 2nd display to click apply…

  Most people will normally change the resolutation to be the same on
  both display, but in case some people want different screen
  resolution, it could be normal ( if simple to code) that if we change
  one of the display resolution only, that we don’t have to click the
  2nd display to CLICK APPLY

  I don’t care if fixed or not but reporting it… As I want to make your
  project better that Winwos and Mac OS LOL

  JF
  18.04 is a lot faster on my i7 computer, 8 gig with SSD hard drive…

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.0-0ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Mar 30 08:23:26 2018
  InstallationDate: Installed on 2018-03-29 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180324)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2018-03-30 Thread Apport retracing service
*** 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/1760081/+attachment/5095839/+files/CoreDump.gz

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

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

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

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

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

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1760081/+attachment/5095848/+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/1760081

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Dunno, if this bug is related to occasional GUI crash (most of I/O
  stops working, including cursor, sound, screen is frozen).

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-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-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Mar 30 00:59:27 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-09-01 (209 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/false
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to bionic on 2018-03-12 (18 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760081/+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-03-30 Thread siddesh kadam
same problem i got black flickering screen on del 5558 , i have 920m
please suggest me which stable graphics driver can i use right now i am
unable to use tensorflow because of this , right now it is working on
nouveau drivers which has got set automatically by the sysytem , m
running linux ubuntu 64 bit .

** Attachment added: "this is the problem plaese twkl me which stable version , 
that i can install right now"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053/+attachment/5095870/+files/alternate_drivers

-- 
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 1727653] Re: error: can't start new thread

2018-03-30 Thread Kenneth Loafman
>From the permissions error message it looks like you tried to run that
as yourself.  Try going into root and running the commands again.

** Changed in: duplicity
Milestone: None => 0.7.18

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

Title:
  error: can't start new thread

Status in Duplicity:
  In Progress
Status in deja-dup package in Ubuntu:
  Triaged
Status in duplicity package in Ubuntu:
  In Progress

Bug description:
  $ uname -a
  Linux mbpr13b 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

  duplicity gets started daily via deja-dup automatically.

  Every now and then (approx. every third time) I get the following
  error:

  --

  Failed with an unknown error.

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1468, in do_backup
  restore(col_stats)
File "/usr/bin/duplicity", line 731, in restore
  restore_get_patched_rop_iter(col_stats)):
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 560, in 
Write_ROPaths
  for ropath in rop_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 523, in 
integrate_patch_iters
  for patch_seq in collated:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 389, in 
yield_tuples
  setrorps(overflow, elems)
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 378, in 
setrorps
  elems[i] = iter_list[i].next()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 107, in 
filter_path_iter
  for path in path_iter:
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 121, in 
difftar2path_iter
  tarinfo_list = [tar_iter.next()]
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 339, in 
next
  self.set_tarfile()
File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 333, in 
set_tarfile
  self.current_fp = self.fileobj_iter.next()
File "/usr/bin/duplicity", line 768, in get_fileobj_iter
  manifest.volume_info_dict[vol_num])
File "/usr/bin/duplicity", line 811, in restore_get_enc_fileobj
  fileobj = tdp.filtered_open_with_delete("rb")
File "/usr/lib/python2.7/dist-packages/duplicity/dup_temp.py", line 119, in 
filtered_open_with_delete
  fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
File "/usr/lib/python2.7/dist-packages/duplicity/path.py", line 778, in 
filtered_open
  return gpg.GPGFile(False, self, gpg_profile)
File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 202, in 
__init__
  'logger': self.logger_fp})
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
374, in run
  create_fhs, attach_fhs)
File "/usr/lib/python2.7/dist-packages/duplicity/gpginterface.py", line 
420, in _attach_fork_exec
  process.thread.start()
File "/usr/lib/python2.7/threading.py", line 736, in start
  _start_new_thread(self.__bootstrap, ())
  error: can't start new thread

  --

  Restarting deja-dup manually fixes the problem and the next few days,
  automatic backup will run correctly until (see above).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:49:45 2017
  InstallationDate: Installed on 2017-10-20 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+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 1760062] Re: gnome-shell crashed with SIGSEGV

2018-03-30 Thread Jean-Baptiste Lallement
** Information type changed from Private to Public

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

Title:
  gnome-shell crashed with SIGSEGV

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  crahed when I open the notifications.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-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-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 11:46:57 2018
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1521124756
  InstallationDate: Installed on 2014-07-15 (1354 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/j-lallement
  SegvAnalysis: Skipped: missing required field "Disassembly"
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_cancellable_make_pollfd () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_socket_condition_timed_wait () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_input_stream_read () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-24 (5 days ago)
  UserGroups: adm autopilot 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/1760062/+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 1760039] Re: Theme lookup should respect XDG_DATA_DIRS

2018-03-30 Thread Launchpad Bug Tracker
This bug was fixed in the package gnome-shell - 3.28.0-0ubuntu2

---
gnome-shell (3.28.0-0ubuntu2) bionic; urgency=medium

  * debian/patches/ubuntu_theme_lookup_xdg.patch:
- theme lookup should respect XDG_DATA_DIRS (LP: #1760039)

 -- Didier Roche   Fri, 30 Mar 2018 10:21:27 +0200

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

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

Title:
  Theme lookup should respect XDG_DATA_DIRS

Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  mods, extensions and others GNOME Shell assets lookup into each dir,
  relative to XDG_DATA_DIRS. However, this isn't the case for themes
  (which can be referened by a mod in a different XDG_DATA_DIR),
  harcoding the global.datadir.

  The fix is to have the theme finding pattern following the same logic
  than others.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760039/+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 1723758] Re: Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)

2018-03-30 Thread Metta Crawler
I haven't seen this issue in a long time.

I'm still using the same graphics card but in another motherboard.

Gigabyte AX370-Gaming 5 BIOS F22, AMD Ryzen 5 2400G, Linux
4.15.0-13-generic, Ubuntu 18.04

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

Title:
  Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up
  (hangs)

Status in Nouveau Xorg driver:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  This is an intermittent issue. Rumored to be fixed in Ubuntu 17.04
  according to comments in bug 1645375

  Oct 15 11:36:26 lakshmi kernel: nouveau :01:00.0: timeout at
  /build/linux-
  
Pcn0xK/linux-4.4.0/drivers/gpu/drm/nouveau/nvkm/engine/fifo/chang84.c:111/g84_fifo_chan_engine_fini()!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-video-nouveau 1:1.0.12-1build2
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  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 Oct 15 12:27:28 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   iscsitarget, 1.4.20.3+svn502, 4.4.0-96-generic, x86_64: installed
   iscsitarget, 1.4.20.3+svn502, 4.4.0-97-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 210] 
[1462:2011]
  InstallationDate: Installed on 2016-01-13 (641 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic 
root=/dev/mapper/vg0-lv0 ro
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.6
  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: Thu Oct 12 15:08:58 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 8
   inputMicrosoft Comfort Curve Keyboard 2000 KEYBOARD, id 9
   inputMicrosoft Comfort Optical Mouse 1000 MOUSE, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.6
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1723758/+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 1760078] [NEW] Double login required from suspend

2018-03-30 Thread Kev Bowring
Public bug reported:

Following a suspend.

Get unlock screen - which then gets me a desktop.

Returned to unlock screen to enter password a second time.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-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: XFCE
Date: Fri Mar 30 12:09:46 2018
InstallationDate: Installed on 2018-03-08 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Double login required from suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Following a suspend.

  Get unlock screen - which then gets me a desktop.

  Returned to unlock screen to enter password a second time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-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: XFCE
  Date: Fri Mar 30 12:09:46 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760078/+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 1760005] Re: Dialog 'add custom shortcut dialog' is unusable with keyboard only

2018-03-30 Thread Andrea Azzarone
** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => In Progress

** Changed in: gnome-control-center (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  Dialog 'add custom shortcut dialog' is unusable with keyboard only

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end
  of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if
  used from keyboard.

  Current field order is: 'Name' -> 'Command' -> 'Cancel' button.
  Tab key switches focus only between these 3 fields. Arrow keys switch focus 
only between input fields.

  Expected field order:  'Name' -> 'Command' -> 'Set Shortcut...' ->
  'Add' button (if enabled) -> 'Cancel' button.

  =
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  =
  gnome-control-center:
Installed: 1:3.28.0-0ubuntu6
Candidate: 1:3.28.0-0ubuntu6
Version table:
   *** 1:3.28.0-0ubuntu6 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1: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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 10:03:23 2018
  InstallationDate: Installed on 2018-03-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760005/+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 1760071] Re: package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-03-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  Following the instructions at 
http://ubuntuforums.org/showthread.php?t=2143157=12650610#post12650610 , I 
tried to disable speech-dispatcher as follows:
  sudo vi /etc/default/speech-dispatcher
  terminal refused to accept change from RUN=yes to RUN=no.
  TRIED TO CHANGE 'YES' TO 'NO' -would not accept the command so tried to close 
terminal. Reports:
  “There is still a process running in this terminal. Closing the terminal will 
kill it.”
  opted to close
   On rebooting get a message:
  E325: ATTENTION
  Found a swap file by the name "/etc/default/.speech-dispatcher.swp"
owned by: root   dated: Fri Mar 30 10:16:12 2018
   file name: /etc/default/speech-dispatcher
modified: YES
   user name: root   host name: nicnoks-desktop
  process ID: 4222
  While opening file "/etc/default/speech-dispatcher"
   dated: Fri Mar 23 11:21:51 2018
  (1) Another program may be editing the same file.  If this is the case,
  be careful not to end up with two different instances of the same
  file when making changes.  Quit, or continue with caution.
  (2) An edit session for this file crashed.
  If this is the case, use ":recover" or "vim -r 
/etc/default/speech-dispatcher"
  to recover the changes (see ":help recovery").
  If you did this already, delete the swap file 
"/etc/default/.speech-dispatcher.swp"
  to avoid this message.
  "/etc/default/speech-dispatcher"" 4 lines, 133 characters
  Press ENTER or type command to continue"
  tried to close terminal:
  “There is still a process running in this terminal. Closing the terminal will 
kill it.”
  went to "/etc/default/.speech-dispatcher.swp" [12.3kb binary] but it refuses 
to be deleted, cut or renamed
  I don't want Speech-Despatcher anyway – so remove through Synaptic
  changelog kept - summary =
  gnome-orca will be removed
  libgnome-speech7 will be removed
  libspeechd2 will be removed
  python3-speechd will be removed
  speech-dispatcher will be removed
  speech-dispatcher-audio-plugins will be removed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: speech-dispatcher 0.8-5ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-143-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Fri Mar 30 11:43:31 2018
  DuplicateSignature: package:speech-dispatcher:0.8-5ubuntu1:subprocess 
installed post-removal script returned error exit status 1
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.8
   apt  1.0.1ubuntu2.17
  SourcePackage: speech-dispatcher
  Title: package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-08-13 (1324 days ago)
  modified.conffile..etc.default.speech.dispatcher:
   # Defaults for the speech-dispatcher initscript, from speech-dispatcher
   
   # Set to yes to start system wide Speech Dispatcher
   RUN=yes
  mtime.conffile..etc.default.speech.dispatcher: 2018-03-23T11:21:51.735065

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1760071/+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 1758677] Re: Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

2018-03-30 Thread Stephen Allen
Thanks. Thursday's March 29/18 updates seemed to have fixed it! Thank-
you.

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

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

Title:
  Vanilla Gnome-Session & Ubuntu-Session Lengthy Time to Logout

Status in gnome-session package in Ubuntu:
  Fix Released

Bug description:
  When manually logging out, it often takes over 30 seconds to give me logout 
dialogue. 
  Been happening for the past week.

  Additionally When I complete the logout - Mouse or keyboard input isn't 
registered forcing a hard reboot.
  Happens in both vanilla-gnome-session and ubuntu-session.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-session 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 
4.13.0-36201803011620.0+mediatree+hauppauge-generic 4.13.13
  Uname: Linux 4.13.0-36201803011620-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 25 10:32:33 2018
  InstallationDate: Installed on 2018-01-19 (65 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1758677/+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 1760073] [NEW] No network from suspend resume

2018-03-30 Thread Kev Bowring
Public bug reported:

Following a resume from suspend - no network available on machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-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: XFCE
Date: Fri Mar 30 11:53:22 2018
InstallationDate: Installed on 2018-03-08 (21 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  No network from suspend resume

Status in lightdm package in Ubuntu:
  New

Bug description:
  Following a resume from suspend - no network available on machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.25.2-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: XFCE
  Date: Fri Mar 30 11:53:22 2018
  InstallationDate: Installed on 2018-03-08 (21 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1760073/+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 1760071] [NEW] package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-03-30 Thread Nic Knox
Public bug reported:

Following the instructions at 
http://ubuntuforums.org/showthread.php?t=2143157=12650610#post12650610 , I 
tried to disable speech-dispatcher as follows:
sudo vi /etc/default/speech-dispatcher
terminal refused to accept change from RUN=yes to RUN=no.
TRIED TO CHANGE 'YES' TO 'NO' -would not accept the command so tried to close 
terminal. Reports:
“There is still a process running in this terminal. Closing the terminal will 
kill it.”
opted to close
 On rebooting get a message:
E325: ATTENTION
Found a swap file by the name "/etc/default/.speech-dispatcher.swp"
  owned by: root   dated: Fri Mar 30 10:16:12 2018
 file name: /etc/default/speech-dispatcher
  modified: YES
 user name: root   host name: nicnoks-desktop
process ID: 4222
While opening file "/etc/default/speech-dispatcher"
 dated: Fri Mar 23 11:21:51 2018
(1) Another program may be editing the same file.  If this is the case,
be careful not to end up with two different instances of the same
file when making changes.  Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r 
/etc/default/speech-dispatcher"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file 
"/etc/default/.speech-dispatcher.swp"
to avoid this message.
"/etc/default/speech-dispatcher"" 4 lines, 133 characters
Press ENTER or type command to continue"
tried to close terminal:
“There is still a process running in this terminal. Closing the terminal will 
kill it.”
went to "/etc/default/.speech-dispatcher.swp" [12.3kb binary] but it refuses to 
be deleted, cut or renamed
I don't want Speech-Despatcher anyway – so remove through Synaptic
changelog kept - summary =
gnome-orca will be removed
libgnome-speech7 will be removed
libspeechd2 will be removed
python3-speechd will be removed
speech-dispatcher will be removed
speech-dispatcher-audio-plugins will be removed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: speech-dispatcher 0.8-5ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39
Uname: Linux 3.13.0-143-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Fri Mar 30 11:43:31 2018
DuplicateSignature: package:speech-dispatcher:0.8-5ubuntu1:subprocess installed 
post-removal script returned error exit status 1
ErrorMessage: subprocess installed post-removal script returned error exit 
status 1
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.8
 apt  1.0.1ubuntu2.17
SourcePackage: speech-dispatcher
Title: package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-08-13 (1324 days ago)
modified.conffile..etc.default.speech.dispatcher:
 # Defaults for the speech-dispatcher initscript, from speech-dispatcher
 
 # Set to yes to start system wide Speech Dispatcher
 RUN=yes
mtime.conffile..etc.default.speech.dispatcher: 2018-03-23T11:21:51.735065

** Affects: speech-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

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

Title:
  package speech-dispatcher 0.8-5ubuntu1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 1

Status in speech-dispatcher package in Ubuntu:
  New

Bug description:
  Following the instructions at 
http://ubuntuforums.org/showthread.php?t=2143157=12650610#post12650610 , I 
tried to disable speech-dispatcher as follows:
  sudo vi /etc/default/speech-dispatcher
  terminal refused to accept change from RUN=yes to RUN=no.
  TRIED TO CHANGE 'YES' TO 'NO' -would not accept the command so tried to close 
terminal. Reports:
  “There is still a process running in this terminal. Closing the terminal will 
kill it.”
  opted to close
   On rebooting get a message:
  E325: ATTENTION
  Found a swap file by the name "/etc/default/.speech-dispatcher.swp"
owned by: root   dated: Fri Mar 30 10:16:12 2018
   file name: /etc/default/speech-dispatcher
modified: YES
   user name: root   host name: nicnoks-desktop
  process ID: 4222
  While opening file "/etc/default/speech-dispatcher"
   dated: Fri Mar 23 11:21:51 2018
  (1) Another program may be editing the same file.  If this is the case,
  be careful not to end up with two different instances of the same
  file when making changes.  Quit, or continue with caution.
  (2) An edit session for this file crashed.
  If this is the case, use ":recover" or "vim -r 
/etc/default/speech-dispatcher"
  to recover the changes (see ":help recovery").
  If you did this already, delete the swap file 
"/etc/default/.speech-dispatcher.swp"
 

[Desktop-packages] [Bug 1760005] Re: Dialog 'add custom shortcut dialog' is unusable with keyboard only

2018-03-30 Thread Andrea Azzarone
** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Dialog 'add custom shortcut dialog' is unusable with keyboard only

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

Bug description:
  'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end
  of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if
  used from keyboard.

  Current field order is: 'Name' -> 'Command' -> 'Cancel' button.
  Tab key switches focus only between these 3 fields. Arrow keys switch focus 
only between input fields.

  Expected field order:  'Name' -> 'Command' -> 'Set Shortcut...' ->
  'Add' button (if enabled) -> 'Cancel' button.

  =
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  =
  gnome-control-center:
Installed: 1:3.28.0-0ubuntu6
Candidate: 1:3.28.0-0ubuntu6
Version table:
   *** 1:3.28.0-0ubuntu6 500
  500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1: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-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 30 10:03:23 2018
  InstallationDate: Installed on 2018-03-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760005/+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

2018-03-30 Thread Amr Ibrahim
There is a mix of duplicates with and without Wayland. Mine was without
Wayland.

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

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


  1   2   >