[Desktop-packages] [Bug 1734820] [NEW] package chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386 failed to install/upgrade: nem másolhatók a kibontott adatok ehhez: „./usr/lib/chromium-bro

[Tibor Muli]

Public bug reported:

hiba

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Tue Nov 28 08:20:09 2017
ErrorMessage: nem másolhatók a kibontott adatok ehhez: 
„./usr/lib/chromium-browser/libffmpeg.so” ide: 
„/usr/lib/chromium-browser/libffmpeg.so.dpkg-new”: váratlan fájl vagy folyam vég
InstallationDate: Installed on 2017-11-18 (10 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: chromium-browser
Title: package chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386 
failed to install/upgrade: nem másolhatók a kibontott adatok ehhez: 
„./usr/lib/chromium-browser/libffmpeg.so” ide: 
„/usr/lib/chromium-browser/libffmpeg.so.dpkg-new”: váratlan fájl vagy folyam vég
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386
  failed to install/upgrade: nem másolhatók a kibontott adatok ehhez:
  „./usr/lib/chromium-browser/libffmpeg.so” ide: „/usr/lib/chromium-
  browser/libffmpeg.so.dpkg-new”: váratlan fájl vagy folyam vég

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  hiba

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Tue Nov 28 08:20:09 2017
  ErrorMessage: nem másolhatók a kibontott adatok ehhez: 
„./usr/lib/chromium-browser/libffmpeg.so” ide: 
„/usr/lib/chromium-browser/libffmpeg.so.dpkg-new”: váratlan fájl vagy folyam vég
  InstallationDate: Installed on 2017-11-18 (10 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: chromium-browser
  Title: package chromium-codecs-ffmpeg-extra 62.0.3202.89-0ubuntu0.17.10.1386 
failed to install/upgrade: nem másolhatók a kibontott adatok ehhez: 
„./usr/lib/chromium-browser/libffmpeg.so” ide: 
„/usr/lib/chromium-browser/libffmpeg.so.dpkg-new”: váratlan fájl vagy folyam vég
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1734820/+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 1716639] Re: gnome-screensaver issue when using Wayland

[ggalli]

Same issue on Ubuntu 17.10 on a Lenovo B50 10.

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

Title:
  gnome-screensaver issue when using Wayland

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  When using a Wayland session instead of X11 from the standard lightdm-
  gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+
  initialisation, causing the gnome-session-binary to exit and
  subsequently a greeter loop where a user is unable to log in.

  The following is an excerpt from the syslog:

  ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service 
name='org.gnome.ScreenSaver'
  Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init 
server: Could not connect: Connection refused
  Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+
  S

  Running an identical session without Wayland produces the expected
  behaviour: a user can log into his desktop session and start working
  as usual.

  Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share
  /gnome-session/sessions/gnome.session doesn't have any effect. I'm
  suspecting foul play between the screensaver proxy and the screensaver
  binary itself, but don't have the bandwidth to analyse the source at
  the moment.

  More than happy to provide more information as required - just let me
  know.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: gnome-screensaver 3.6.1-7ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 12 11:29:30 2017
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2017-08-31 (11 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1716639/+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 1174162] Re: chrome-browser makes gnome-keyring-daemon use 100% cpu

[William Crandell]

What worked for me was `gnome-keyring-daemon-old`

though

`google-chrome --password-store:basic` may work according to:

https://andreafortuna.org/chrome/how-to-prevent-the-huge-cpu-usage-of-
gnome-keyring-daemon-when-starting-google-chrome/

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

Title:
  chrome-browser makes gnome-keyring-daemon use 100% cpu

Status in Chromium Browser:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 13.04, when starting the chromium browser, the
  gnome-keyring-daemon runs at full CPU load and the chromium-browser
  has no access to the stored passwords.

  The issue seems to be known
  (https://code.google.com/p/chromium/issues/detail?id=98601). I'm
  personally a bit surprised that Ubuntu 13.04 was released with such a
  serious problem.

  The frequently proposed workaround (e.g.
  https://plus.google.com/110130355317073712944/posts/PckhFj5HUn4)
  doesn't work because (a) there is no .gnome2/keyrings any more and (b)
  it's rather inresponsible to store your passwords unencryted.

  I found that killing gnome-keyring-server several times eventually gives you 
a working system.
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mnl   18759 F pulseaudio
  CRDA:
   country DE:
(2400 - 2483 @ 40), (N/A, 20)
(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
(5470 - 5725 @ 40), (N/A, 26), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=86292e17-edd2-4a1b-8e1b-5208a1731140
  InstallationDate: Installed on 2010-11-10 (900 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  MachineType: Hewlett-Packard HP Compaq 6730b (GB990EA#ABD)
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=cff10fb4-08a2-459b-be12-80698b20d2d3 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic i686
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare voice 
wireshark
  WifiSyslog: Apr 29 07:28:34 lipp-nb wpa_supplicant[1803]: wlan0: WPA: Group 
rekeying completed with c0:25:06:24:93:e1 [GTK=CCMP]
  dmi.bios.date: 12/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDD Ver. F.20
  dmi.board.name: 30DD
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 96.23
  dmi.chassis.asset.tag: CNU9326SJY
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDDVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPCompaq6730b(GB990EA#ABD):pvrF.20:rvnHewlett-Packard:rn30DD:rvrKBCVersion96.23:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6730b (GB990EA#ABD)
  dmi.product.version: F.20
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1174162/+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 1433032] Re: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins

[William Crandell]

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

My best solution is to use `gnome-keyring-daemon-old`

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

Title:
  Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU
  thread for 5 at least mins

Status in gnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  This is Ubuntu 14.04 LTS x64.

  I removed good amount of remembered passwords but there are no
  noticable changes.

  Chrome is v 40.0.2214.10 beta (64-bit)

  ---

  Regards & respect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1433032/+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 1717737] Re: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status

[Launchpad Bug Tracker]

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

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

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

Title:
  package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade:
  package libgraphite2-3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in graphite2 package in Ubuntu:
  Expired

Bug description:
  tried to install gcc

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgraphite2-3:amd64 1.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   libgraphite2-3: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Sep 16 19:44:19 2017
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
  DpkgHistoryLog:
   Start-Date: 2017-09-16  19:44:19
   Commandline: apt-get install gcc
   Requested-By: kev (1000)
  DpkgTerminalLog:
   dpkg: error processing package libgraphite2-3:amd64 (--configure):
package libgraphite2-3:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration  
cannot configure (current status 'half-installed')
  InstallationDate: Installed on 2017-07-03 (75 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: graphite2
  Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: 
package libgraphite2-3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1717737/+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 1632027] Re: New Document feature missing from Nautilus 3.20+

[Shuhao]

This seems to affect 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/1632027

Title:
  New Document feature missing from Nautilus 3.20+

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu has a patch ( 16_unity_new_documents.patch ) to enable a 'New
  Document' function in the right-click context menu. This patch was not
  ported to Nautilus 3.20 so this Ubuntu-specific feature is missing in
  Ubuntu 16.10.

  https://bazaar.launchpad.net/~ubuntu-
  desktop/nautilus/ubuntu/view/head:/debian/patches/16_unity_new_documents.patch

  While this patch being disabled is noted in the debian/changelog,
  here's a formal bug to document the issue and maybe give it a bit more
  visibility so that it will be fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: nautilus 1:3.20.3-1ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 10 12:54:50 2016
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'open-folder-on-dnd-hover' b'false'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'171'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1106x542+436+438'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small'"
  InstallationDate: Installed on 2016-08-11 (59 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha amd64 (20160811)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus: gnome-terminal 3.20.2-1ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1632027/+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 1726516] Re: no progress bar while copying files

[Shuhao]

I filed an upstream issue:
https://gitlab.gnome.org/GNOME/nautilus/issues/142

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

Title:
  no progress bar while copying files

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  while copying files, it does not show progress or any copy dialogue at
  all. also there is no option to create new file while right clicking

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 23 23:08:22 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726516/+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 1734802] [NEW] Can't type the numbers 1-5 into the search bar when trying to filter emails.

[Michael Neuling]

Public bug reported:

I can't type the numbers 1-5 into the search bar when trying to filter
emails.

Fix is upstream in evolution in this commit

commit 0b6a4a707279d63c389bff691da4519d51f468a6
Author: Milan Crha 
Date:   Wed Oct 4 18:49:06 2017 +0200

Label shortcuts prevent typing numbers

Since change for bug 787002 typing numbers into for example search
entry was not possible, due to the shortcuts for labels "consuming"
the key presses. The fix is to allow labels only if the message
list is focused, when also the context menu contains the Labels.

This had been reported downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=1498484


Please backport to Artful

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

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

Title:
  Can't type the numbers 1-5 into the search bar when trying to filter
  emails.

Status in evolution package in Ubuntu:
  New

Bug description:
  I can't type the numbers 1-5 into the search bar when trying to filter
  emails.

  Fix is upstream in evolution in this commit

  commit 0b6a4a707279d63c389bff691da4519d51f468a6
  Author: Milan Crha 
  Date:   Wed Oct 4 18:49:06 2017 +0200

  Label shortcuts prevent typing numbers
  
  Since change for bug 787002 typing numbers into for example search
  entry was not possible, due to the shortcuts for labels "consuming"
  the key presses. The fix is to allow labels only if the message
  list is focused, when also the context menu contains the Labels.
  
  This had been reported downstream:
  https://bugzilla.redhat.com/show_bug.cgi?id=1498484

  
  Please backport to Artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1734802/+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 1734750] Re: Fail to shutdown system properly

[Kai-Heng Feng]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Fail to shutdown system properly

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK 
(standard hardware - no modifications).
  When I try to reboot or shutdown I see messages like:
  [ *** ] A stop job is running for Network Manager (/)
  OR
  [ *** ] A stop job is running for WPA supplicant (/)
  (Messages appears periodically, replacing each other), and later this
  INFO task kworker/ blocked for more than 120 seconds
  is added to the line
  Where  could be different, for example: u8:2:169 or 0:1:33
  If I wait about 6 or so minutes I finally can see:
  Reached target Shutdown
  But the laptop is still on and I have have to hold power button a few seconds 
to halt it.

  I've tried:
  - Update BIOS to the latest version
  - Update Intel microcode
  - Uncheck "Use Intel Microcode" from Device Manager
  - Install all updates

  But the problem is persistent and I run into it each time I want to 
shutdown/reboot my laptop. It even can be reproduced from live usb stick 
(reboot after install). However, during regular work everything is fine.
  Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases 
on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more 
shutdowns).

  Before I created bug https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1733203 but it turned out to be two different
  bugs and there are attached photos of logs on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Nov 27 13:40:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-27 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  802-11-wireless  
1511807923  Mon 27 Nov 2017 01:38:43 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  9794efad-4922-3754-bb66-2a49594348d1  802-3-ethernet   
1511807906  Mon 27 Nov 2017 01:38:26 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734750/+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 1734794] Re: Install of ubuntu-desktop login loop

[Nick Mayer]

** Package changed: xorg (Ubuntu) => ubuntu-meta (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/1734794

Title:
  Install of ubuntu-desktop login loop

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Tested on clean VM. To repro install ubuntu-17.10 server edition

  > sudo apt update
  > sudo apt upgrade
  > sudo apt install ubuntu-desktop --no-install-recommends
  > sudo reboot
  # Reboots to graphical login screen. After entering username password returns 
to graphical login for both Ubuntu and Ubuntu on Xorg
  # Switch to tty2
  > sudo apt install gsettings-ubuntu-schemas
  # Switch to tty1
  # Login now works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Mon Nov 27 19:50:24 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-11-28 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  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 N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1734794/+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 1734794] [NEW] Install of ubuntu-desktop login loop

[Nick Mayer]

Public bug reported:

Tested on clean VM. To repro install ubuntu-17.10 server edition

> sudo apt update
> sudo apt upgrade
> sudo apt install ubuntu-desktop --no-install-recommends
> sudo reboot
# Reboots to graphical login screen. After entering username password returns 
to graphical login for both Ubuntu and Ubuntu on Xorg
# Switch to tty2
> sudo apt install gsettings-ubuntu-schemas
# Switch to tty1
# Login now works

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Mon Nov 27 19:50:24 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2017-11-28 (0 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2017
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
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 N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug artful crash 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/1734794

Title:
  Install of ubuntu-desktop login loop

Status in xorg package in Ubuntu:
  New

Bug description:
  Tested on clean VM. To repro install ubuntu-17.10 server edition

  > sudo apt update
  > sudo apt upgrade
  > sudo apt install ubuntu-desktop --no-install-recommends
  > sudo reboot
  # Reboots to graphical login screen. After entering username password returns 
to graphical login for both Ubuntu and Ubuntu on Xorg
  # Switch to tty2
  > sudo apt install gsettings-ubuntu-schemas
  # Switch to tty1
  # Login now works

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  Date: Mon Nov 27 19:50:24 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-11-28 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3fb3b989-6bd0-43f4-a49e-04af4ecac2f2 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

Just sent a new merge request.
https://code.launchpad.net/~hui.wang/pulseaudio/+git/pulseaudio/+merge/334346

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

Adding gjs here as it's the one that should avoid such hard crashes.

In order to avoid them I've prepared a pull request for upstream
 https://gitlab.gnome.org/GNOME/gjs/merge_requests/22

And that works quite well in such cases, let's see what upstream thinks.

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[Bug Watch Updater]

** Changed in: emacs25 (Debian)
   Status: Unknown => New

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

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New
Status in emacs25 package in Debian:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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 1734791] [NEW] gnome-keyring doesn't start gnome-keyring-ssh services

[Tessa]

Public bug reported:

Looking at the gnome-keyring packages in 17.10, I see the following
files, which should be auto-starting the gnome-keyring ssh agent
service:

/usr/lib/systemd/user/gnome-keyring-ssh.service
/usr/lib/systemd/user/graphical-session-pre.target.wants/gnome-keyring-ssh.service

As well, I seem to have a file in ~/.config/autostart/gnome-keyring-
ssh.desktop which should also start gnome-keyring-daemon with the
--components=ssh option.

However, in my actual GNOME session on Wayland, gnome-keyring-daemon is
running with the following options:

"/usr/bin/gnome-keyring-daemon --daemonize --login"

and there are no SSH-AGENT related env vars set, and common ssh commands
like ssh-add do not work.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-keyring 3.20.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 27 16:56:40 2017
InstallationDate: Installed on 2016-07-08 (507 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to artful on 2017-10-19 (39 days ago)

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


** Tags: amd64 apport-bug artful third-party-packages wayland-session

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

Title:
  gnome-keyring doesn't start gnome-keyring-ssh services

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Looking at the gnome-keyring packages in 17.10, I see the following
  files, which should be auto-starting the gnome-keyring ssh agent
  service:

  /usr/lib/systemd/user/gnome-keyring-ssh.service
  
/usr/lib/systemd/user/graphical-session-pre.target.wants/gnome-keyring-ssh.service

  As well, I seem to have a file in ~/.config/autostart/gnome-keyring-
  ssh.desktop which should also start gnome-keyring-daemon with the
  --components=ssh option.

  However, in my actual GNOME session on Wayland, gnome-keyring-daemon
  is running with the following options:

  "/usr/bin/gnome-keyring-daemon --daemonize --login"

  and there are no SSH-AGENT related env vars set, and common ssh
  commands like ssh-add do not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-keyring 3.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 27 16:56:40 2017
  InstallationDate: Installed on 2016-07-08 (507 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to artful on 2017-10-19 (39 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1734791/+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 1734577] Re: Only returns snap packages in current 18.04 image installs

[Doug McMahon]

After several restarts seems to clear up.

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

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

Title:
  Only returns snap packages in current 18.04 image installs

Status in gnome-software package in Ubuntu:
  Invalid

Bug description:
  Daily image of 18.04 (11/26
  Fresh install, sources updated 

  When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors 
picks is shown
  Searching for apps only returns snap version or nothing if no snap available

  Test case:
  Fresh install of current 18.04 image
  Boot up, log in, update sources
  Open Ubuntu Software, notice main screen
  Search for an app, ex. in screens below

  What happens:
  Only snap versions are found (if they exist

  To fix (user side):
  Remove the gnome-software snap plugin package
  re-open Software, all is as expected.
  Re-install the snap plugin, all remains as expected..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+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 332309] Re: Support QuickTime VR files with interactive elements

[Bug Watch Updater]

** Changed in: gst-plugins-good
   Status: Confirmed => Won't Fix

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

Title:
  Support QuickTime VR files with interactive elements

Status in gst-plugins-good:
  Won't Fix
Status in gst-plugins-good0.10 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem-mozilla

  totem-mozilla | 2.24.3-0ubuntu1
  ubuntu 8.10

  Totem Browser Plugin plays VR as a series of photos
  http://www.apple.com/quicktime/technologies/qtvr/gallery/times_square.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/332309/+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 1685591] Re: Gnome Calendar does not show details of "Other X events" in Week view

[Bug Watch Updater]

** Changed in: gnome-calendar
   Status: Confirmed => Expired

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

Title:
  Gnome Calendar does not show details of "Other X events" in Week view

Status in GNOME Calendar:
  Expired
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  If there are too many events to show in one day / week tile, Calendar
  will display "Other X events", where X is the number of events that
  are not displayed explicitly. In Month view, clicking on "Other X
  events" will show the details of these events. I'd expect the same
  behaviour in Week view. Instead, nothing happens in Week view if I
  click on "Other X events".

  Ubuntu 17.04
  gnome-calendar 3.24.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1685591/+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 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[themusicgod1]

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

** Also affects: emacs25 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882957
   Importance: Unknown
   Status: Unknown

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

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New
Status in emacs25 package in Debian:
  Unknown

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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 1734071] Re: idk

[Emily Ratliff]

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1734069
   idk

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734071/+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 1734072] Re: idk

[Emily Ratliff]

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1734069
   idk

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734072/+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 1734073] Re: idk

[Emily Ratliff]

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1734069
   idk

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734073/+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 1734074] Re: idk

[Emily Ratliff]

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1734069
   idk

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734074/+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 1734785] [NEW] /usr/bin/nm-applet:11:applet_schedule_update_icon:weak_refs_notify:g_object_unref:g_ptr_array_foreach:ptr_array_free

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful trusty xenial yakkety zesty

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

Title:
  /usr/bin/nm-
  
applet:11:applet_schedule_update_icon:weak_refs_notify:g_object_unref:g_ptr_array_foreach:ptr_array_free

Status in network-manager-applet package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1734785/+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 1734069] Re: idk

[Emily Ratliff]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it, because your description
didn't include enough information. You may find it helpful to read 'How
to report bugs effectively'
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1.
the specific steps or actions you took that caused you to encounter the
problem, 2. the behavior you expected, and 3. the behavior you actually
encountered (in as much detail as possible). Thanks!

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

** Information type changed from Private Security to Public

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

Title:
  idk

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734069/+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 1734070] Re: idk

[Emily Ratliff]

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

** Information type changed from Private Security to Public

** This bug has been marked a duplicate of bug 1734069
   idk

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

Title:
  idk

Status in xorg package in Ubuntu:
  New

Bug description:
  idk

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic i686
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: i386
  CompositorRunning: None
  Date: Thu Nov 23 01:59:44 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:3a02]
  InstallationDate: Installed on 2017-10-30 (24 days ago)
  InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 
(20171017.1)
  MachineType: LENOVO 4186
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=04d3d2bc-6477-407b-bb6a-316c379aa151 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 15CN31WW(V2.04)
  dmi.board.name: KIWB1
  dmi.board.vendor: LENOVO
  dmi.board.version: REFERENCE
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnLENOVO:bvr15CN31WW(V2.04):bd09/21/2009:svnLENOVO:pn4186:pvrLenovoIdeaPadY550:rvnLENOVO:rnKIWB1:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Lenovo
  dmi.product.name: 4186
  dmi.product.version: Lenovo IdeaPad Y550
  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
  xserver.bootTime: Thu Nov 23 01:49:56 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734070/+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 590369] Re: wrong keyboard language at keyboard indicator at screen lock login

[Dimitar Garkov]

** Also affects: unity-greeter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  wrong keyboard language at keyboard indicator at screen lock login

Status in ubiquity package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  New

Bug description:
  On a Ubuntu Lucid setup with two keyboard languages (Deu, USA) 
  and the current language (at time of screen lock) being German (Deu)
  Language when attempting to login incorrectly indicates USA. 
  Keyboard actually in place is Deu, and this is proven when using a password 
which has the letter 'Z' or 'Y' in it (as these letters are in different 
positions in USA or Deu)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/590369/+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 1734762] [NEW] Evolution crashes often

[Raffi Khatchadourian]

Public bug reported:

Started crashing when I upgraded to Ubuntu 17.10. See
https://bugzilla.gnome.org/show_bug.cgi?id=790806 for more info.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: evolution-indicator 0.2.20-0ubuntu31
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 27 15:18:08 2017
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
SourcePackage: evolution-indicator
UpgradeStatus: Upgraded to artful on 2017-11-07 (20 days ago)

** Affects: evolution-indicator (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Evolution crashes often

Status in evolution-indicator package in Ubuntu:
  New

Bug description:
  Started crashing when I upgraded to Ubuntu 17.10. See
  https://bugzilla.gnome.org/show_bug.cgi?id=790806 for more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: evolution-indicator 0.2.20-0ubuntu31
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 15:18:08 2017
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, user)
  SourcePackage: evolution-indicator
  UpgradeStatus: Upgraded to artful on 2017-11-07 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1734762/+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 1734727] Re: Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

[Hans Joachim Desserud]

** Tags added: artful

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

Title:
  Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  BEHAVIOR
  When I left-click or right-click on the HP menu in the top right of the 
Ubuntu 17.10 top bar, the menu doesn't appear.

  STEPS TO REPRODUCE
  (1) open a terminal
  (2) type "sudo apt install hplip-gui"
  (3) open HP toolbox
  (4) Restart PC
  (4) After restart, try to left or right-click the hp icon in the appindicator 
menu at the top-right.

  EXPECTED BEHAVIOR
  For the menu to appear when you left or right-click it (probably left-click)

  BUG DISCOVERED USING
  HPLIP Software vertion 3.17.7
  Ubuntu 17.10 x64
  GNOME Shell 3.26.1
  Linux kernel 4.13.0-17-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1734727/+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 508618] Re: Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

[era]

Do you mean this is a new way to repro?  Which replaces the old? (For
all versions, or just the latest one you tried?)

If we are to finally report this upstream, can you provide a brief use
case to assess the priority of this?  If it's just an academic
curiosity, I don't really see the point; but even in that case, it would
make more sense for it to sit in the Emacs bug tracker where the people
who can do something about it at least have a chance to stumble into it.
Here, it's not doing anyone any good.

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

Title:
  Setting max-specpdl-size of 34295 allows segfaults with 'simple' elisp

Status in emacs23 package in Ubuntu:
  New
Status in emacs24 package in Ubuntu:
  New
Status in emacs25 package in Ubuntu:
  New

Bug description:
  Binary package hint: emacs23

  Setting max-specpdl-size higher than 34295, and then running the following 
code results in a segfault of emacs.  I am 
  running a system of mostly 9.04 with some packages (such as this one) 
upgraded. I know it's kind of pushing emacs to the limit, but still;  this 
seems like an arbitrary limit on emacs' otherwise diety-like functionality.  
What should happen is emacs should continue to fail to execute with 
"file-truename: Variable binding depth exceeds max-specpdl-size"  as it does 
below 34295., or at the very least when setting max-specpdl-size higher than 
34295 it should warn you that you are making some kind of error if this is not 
acceptable.

  example code:

  (defun por (pcurrent pb numberleft)
 (if (= numberleft 0)
   pcurrent
   (por (- (+ pcurrent pb) (* pcurrent pb)) pb (- numberleft 1

  (por 0 0.01 1)

  (setq max-lisp-eval-depth 100)  ; this may be necessary, but doesn't 
appear to be the problem
  (setq max-specpdl-size 34295)  ; setting this lower results in 
predictable, expected behaviour - emacs refuses to run the result, citing 
max-specpdl-size not high enough.   Setting this higher (like...34296), results 
in a segfault of emacs

  emacs23:
Installé : 23.1+1-4ubuntu3
Candidat : 23.1+1-4ubuntu3
   Table de version :
   *** 23.1+1-4ubuntu3 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  Package: emacs23 23.1+1-4ubuntu3
  ProcEnviron:
   PATH=(custom, user)
   LANG=fr_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: emacs23
  Uname: Linux 2.6.28-16-generic x86_64
  UnreportableReason: Ceci n'est pas un authentique paquet Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/508618/+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 1696415] Re: NetworkManager does not update IPv4 address lifetime even though DHCP lease was successfully renewed

[Ray Link]

Sorry for the delay - I was away for a week.  I have deployed the
packages from -proposed and will  confirm after keeping an eye on DHCP
lease renewals for a while.

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

Title:
  NetworkManager does not update IPv4 address lifetime even though DHCP
  lease was successfully renewed

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed

Bug description:
  SRU REQUEST:

  Debdiff (nm-dhcp-helper.debdiff) attached.

  Fixed in current Ubuntu zesty and newer: Bionic uses NM 1.8.x. This
  bug was fixed upstream in 1.4.

  [Impact]

   * nm-dhcp-helper sometimes fails to notify NetworkManager of a DHCP
     lease renewal due to a DBus race condition.

   * Upstream NetworkManager 1.4 fixes the race condition by changing
     nm-dhcp-helper's DBus notification from signal "Event" to method
     "Notify".

   * Original bug submitter backported NM 1.4's nm-dhcp-helper notification fix 
to NM 1.2. This SRU request applies that backported patch to Xenial's
     NM 1.2.x.

  [Test Case]

   * Not reliably reproducible. Out of hundreds of machines, only a
     dozen or so fail to notify NetworkManager of a DHCP lease
     renewal about 30-50% of the time. (i.e. It's always the same
     handful of machines that fail.)

   * All such machines with the patched packages have been fine for weeks,
     over many dozens of lease renewals.

  [Regression Potential]

  * The patch changes both nm-dhcp-helper and NetworkManager itself. As
  soon as the new packages are unpacked, the new nm-dhcp-helper will be
  used on DHCP lease renewals, with the new Notify mechanism. Since the
  running, old NetworkManager is still expecting Event notifications,
  the patched nm-dhcp-helper has fallback capability to Event.

  * Once NetworkManager is restarted and is running the patched version,
  it will have the new Notify support.

  [Other Info]

   * Upstream bug w/ patch:
  https://bugzilla.gnome.org/show_bug.cgi?id=784636

   * RHEL bug with links to the 1.4 commits from which the patch was
     derived: https://bugzilla.redhat.com/show_bug.cgi?id=1373276

   * NOTE:  The final comment on the upstream GNOME bug claims that the
  fix is incomplete.  However, it is possible that the running
  NetworkManager was not restarted (see Regression Potential notes
  above), which is why nm-dhcp-helper is falling back to Event.  The
  remainder of the log messages in that final comment are from a custom
  wrapper the submitter was running around nm-dhcp-helper.  I have
  deployed the exact same patch (without said wrapper) to real-world
  systems and tested extensively, and see nothing but successful DHCP
  lease renewal notifications using D-Bus Notify, not D-Bus Event.


  
  I've found an issue on some of our Xenial office machines, causing 
NetworkManager to drop its IP address lease in some cases when it shouldn't. 
I'm not sure if the actual bug is in NetworkManager or perhaps dbus or 
dhclient, but I'll do my best to help to figure out where it is.

  What appears to happen:
  * NetworkManager is informed of a new IPv4 lease.
  * During the lease, dhclient keeps it fresh by renewing it using DHCPREQUESTs 
regularly.
  * In spite of this, NetworkManager drops the IP address from the interface 
when the last reported lease time expires.

  This happens on various machines, once every few days. We are using a
  failover DHCP configuration using two machines (192.168.0.3 'bonaire'
  and 192.168.0.4 'curacao').

  The machine where I've done the debugging is called 'pampus'
  (192.168.0.166). As you can see in the logs, at 01:21:06
  NetworkManager reports a new lease with lease time 7200.

  jun 07 01:21:06 pampus dhclient[1532]: DHCPREQUEST of 192.168.0.166 on eth0 
to 192.168.0.4 port 67 (xid=0x3295b440)
  jun 07 01:21:06 pampus dhclient[1532]: DHCPACK of 192.168.0.166 from 
192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
address 192.168.0.166
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   plen 
24 (255.255.255.0)
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
gateway 192.168.0.5
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
server identifier 192.168.0.4
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
lease time 7200
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.3'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
nameserver '192.168.0.4'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9530]   
domain name 'office.screenpointmed.com'
  jun 07 01:21:06 pampus NetworkManager[1161]:   [1496791266.9531] dhcp4 
(eth0): state changed bound -> bound

  After 

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64()

[Treviño]

André, this is something we discussed a bit upstream (see comments
starting from https://bugzilla.gnome.org/show_bug.cgi?id=788931#c61).

So as said it would be better not to make it crash, the shell too...
However it's something gjs should probably handle better, but I'm not
sure how this is something that could be wanted or not upstream. I'm
looking how to manage that, though.

It's even true that those extensions should not play with objects that
might have been destroyed on their async functions, then they need to be
fixed too.

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1734759] [NEW] Meta-P will change user's display configuration to mirror without prompting, losing existing configuration

[Dan Watkins]

Public bug reported:

I just accidentally hit Meta-P and was extremely confused by the result.
As I only tapped it, I didn't see the on-screen menu, and my displays
were suddenly configured completely differently (both resolution _and_
orientation).

Furthermore, when I used Meta-P to switch back to "Join Displays", my
previous configuration was lost.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 27 14:40:52 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-23 (34 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful wayland-session

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

Title:
  Meta-P will change user's display configuration to mirror without
  prompting, losing existing configuration

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I just accidentally hit Meta-P and was extremely confused by the
  result.  As I only tapped it, I didn't see the on-screen menu, and my
  displays were suddenly configured completely differently (both
  resolution _and_ orientation).

  Furthermore, when I used Meta-P to switch back to "Join Displays", my
  previous configuration was lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 14:40:52 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-23 (34 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734759/+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 1734750] Re: Fail to shutdown system properly

[Surfer]

I decided to update system again after bug report and... it gone.
Sorry for disturbing. Seems this issue can be closed.

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

Title:
  Fail to shutdown system properly

Status in network-manager package in Ubuntu:
  New

Bug description:
  I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK 
(standard hardware - no modifications).
  When I try to reboot or shutdown I see messages like:
  [ *** ] A stop job is running for Network Manager (/)
  OR
  [ *** ] A stop job is running for WPA supplicant (/)
  (Messages appears periodically, replacing each other), and later this
  INFO task kworker/ blocked for more than 120 seconds
  is added to the line
  Where  could be different, for example: u8:2:169 or 0:1:33
  If I wait about 6 or so minutes I finally can see:
  Reached target Shutdown
  But the laptop is still on and I have have to hold power button a few seconds 
to halt it.

  I've tried:
  - Update BIOS to the latest version
  - Update Intel microcode
  - Uncheck "Use Intel Microcode" from Device Manager
  - Install all updates

  But the problem is persistent and I run into it each time I want to 
shutdown/reboot my laptop. It even can be reproduced from live usb stick 
(reboot after install). However, during regular work everything is fine.
  Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases 
on shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more 
shutdowns).

  Before I created bug https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1733203 but it turned out to be two different
  bugs and there are attached photos of logs on shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Mon Nov 27 13:40:10 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-27 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  802-11-wireless  
1511807923  Mon 27 Nov 2017 01:38:43 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  9794efad-4922-3754-bb66-2a49594348d1  802-3-ethernet   
1511807906  Mon 27 Nov 2017 01:38:26 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

[Apport retracing service]

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

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 #1732878, 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/1734755/+attachment/5015359/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1732878
   gnome-shell crashed with signal 5 in g_log_default_handler()

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

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

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running gnome-shell and open apport.

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  Uname: Linux 4.14.2-041402-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Mon Nov 27 15:24:36 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-13 (45 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_CL.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: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734755/+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 1709781] Re: Screenshots do not work in Wayland session

[yolen]

No screenshots go to my clipboard either. Saving to files is just fine

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

Title:
  Screenshots do not work in Wayland session

Status in Gnome Screenshot:
  New
Status in gnome-screenshot package in Ubuntu:
  Incomplete

Bug description:
  With the current 17.10 builds, it's not possible to take screenshots
  when using the Wayland session.

  Expected result: Screenshot of actual screen/application/rectangle taken and 
either copied to clipboard or saved to file
  Actual result: No Image, just a black image

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screenshot/+bug/1709781/+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 1734750] [NEW] Fail to shutdown system properly

[Surfer]

Public bug reported:

I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK 
(standard hardware - no modifications).
When I try to reboot or shutdown I see messages like:
[ *** ] A stop job is running for Network Manager (/)
OR
[ *** ] A stop job is running for WPA supplicant (/)
(Messages appears periodically, replacing each other), and later this
INFO task kworker/ blocked for more than 120 seconds
is added to the line
Where  could be different, for example: u8:2:169 or 0:1:33
If I wait about 6 or so minutes I finally can see:
Reached target Shutdown
But the laptop is still on and I have have to hold power button a few seconds 
to halt it.

I've tried:
- Update BIOS to the latest version
- Update Intel microcode
- Uncheck "Use Intel Microcode" from Device Manager
- Install all updates

But the problem is persistent and I run into it each time I want to 
shutdown/reboot my laptop. It even can be reproduced from live usb stick 
(reboot after install). However, during regular work everything is fine.
Before I used Ubuntu Mate 17.04 and such problem appears in some rare cases on 
shutdown/reboot (hard to say exactly, roughly 1 of 10 or even more shutdowns).

Before I created bug https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1733203 but it turned out to be two different bugs and
there are attached photos of logs on shutdown.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Mon Nov 27 13:40:10 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-11-27 (0 days ago)
InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20171018)
IpRoute:
 default via 192.168.1.1 dev wlp2s0 proto static metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
 MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  802-11-wireless  
1511807923  Mon 27 Nov 2017 01:38:43 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
 Wired connection 1  9794efad-4922-3754-bb66-2a49594348d1  802-3-ethernet   
1511807906  Mon 27 Nov 2017 01:38:26 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
MNANSHFF2df64dd7-961d-47cd-acce-5fc9aec6ce8d  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1734750

Title:
  Fail to shutdown system properly

Status in network-manager package in Ubuntu:
  New

Bug description:
  I use Ubuntu Mate 17.10 installed from scratch on Lenovo ideapad 700-15ISK 
(standard hardware - no modifications).
  When I try to reboot or shutdown I see messages like:
  [ *** ] A stop job is running for Network Manager (/)
  OR
  [ *** ] A stop job is running for WPA supplicant (/)
  (Messages appears periodically, replacing each other), and later this
  INFO task kworker/ blocked for more than 120 seconds
  is added to the line
  Where  could be different, for example: u8:2:169 or 0:1:33
  If I wait about 6 or so minutes I finally can 

[Desktop-packages] [Bug 1734745] [NEW] NM assumes avahi ip addres and default gw for disconnected device

[Ben Aceler]

Public bug reported:

I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The ethernet
device is not connected at all. The WiFi is connected to WiFi network.

The problem is, the connection drops itself after a while. I did some
research and find out, the NM creates a new connection for the ethernet
device, assuming Avahi IP for that connection, actually making this
device a default route in a routing table. Thus, all outgoing packets
are going through a non-connected ethernet device instead of gateway in
WiFi network.

See commands output for details.

If I delete that default route manually, re-run dhclient to get a new
route or disconnect enp9s0 using NM, the internet start working again.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "commands_output"
   
https://bugs.launchpad.net/bugs/1734745/+attachment/5015325/+files/commands_output

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

Title:
  NM assumes avahi ip addres and default gw for disconnected device

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have an Ubuntu 17.10 box with WiFi and Ethernet devices. The
  ethernet device is not connected at all. The WiFi is connected to WiFi
  network.

  The problem is, the connection drops itself after a while. I did some
  research and find out, the NM creates a new connection for the
  ethernet device, assuming Avahi IP for that connection, actually
  making this device a default route in a routing table. Thus, all
  outgoing packets are going through a non-connected ethernet device
  instead of gateway in WiFi network.

  See commands output for details.

  If I delete that default route manually, re-run dhclient to get a new
  route or disconnect enp9s0 using NM, the internet start working again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734745/+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 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

[Andreas Hasenack]

Or nvidia

** Also affects: nvidia-graphics-drivers (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

Status in glib2.0 package in Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  This is a bug report about errors during the upgrade process. I don't
  know whether or not my samba installation was working immediately
  before the upgrade; the windows box that was intended to be a client
  died and has not been replaced. Don't believe my answers to the forced
  questions.

  ***

  My ubuntu system locks up regularly. Bugs I've reported about this get
  closed for inattention, after being ignored, and queries about how to
  do basic debugging get the same treatment, so I just power cycle
  whenever it happens again.

  This time the lock up happened while the GUI upgrade-everything-to-
  latest tool was running.

  When I power cycled the box to recover, the system was unusable -
  flashing "system problem detected" popups, none staying stable long
  enough to respond.

  ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to
  "sudo dpkg --configure -a"

  That command reported numerous errors - I don't know which of them are
  "normal" for this system, but hidden by the GUI, and which are new.

  But it got the system semi-usable from the GUI, so now I'm clicking on
  "yes, report it" for the many pop-ups, of which this is one.

  FWIW, samba is one of the ones "dpkg --reconfigure -a" complained
  about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Nov 12 11:07:42 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2012-04-26 (2026 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  NmbdLog:
   
  OtherFailedConnect: Yes
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+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 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

[Andreas Hasenack]

I added an nvidia task to the bug so its maintainer can take a look to
see if it's related or not.

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]

Status in glib2.0 package in Ubuntu:
  New
Status in nvidia-graphics-drivers package in Ubuntu:
  New

Bug description:
  This is a bug report about errors during the upgrade process. I don't
  know whether or not my samba installation was working immediately
  before the upgrade; the windows box that was intended to be a client
  died and has not been replaced. Don't believe my answers to the forced
  questions.

  ***

  My ubuntu system locks up regularly. Bugs I've reported about this get
  closed for inattention, after being ignored, and queries about how to
  do basic debugging get the same treatment, so I just power cycle
  whenever it happens again.

  This time the lock up happened while the GUI upgrade-everything-to-
  latest tool was running.

  When I power cycled the box to recover, the system was unusable -
  flashing "system problem detected" popups, none staying stable long
  enough to respond.

  ssh + "sudo apt-get update" + "sudo apt-get upgrade" pointed me to
  "sudo dpkg --configure -a"

  That command reported numerous errors - I don't know which of them are
  "normal" for this system, but hidden by the GUI, and which are new.

  But it got the system semi-usable from the GUI, so now I'm clicking on
  "yes, report it" for the many pop-ups, of which this is one.

  FWIW, samba is one of the ones "dpkg --reconfigure -a" complained
  about.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: samba 2:4.3.11+dfsg-0ubuntu0.16.04.10
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Nov 12 11:07:42 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2012-04-26 (2026 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  NmbdLog:
   
  OtherFailedConnect: Yes
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SambaServerRegression: Yes
  SmbConfIncluded: Yes
  SmbLog:
   
  SourcePackage: samba
  Title: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-03-31 (226 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+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 1734294] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul White]

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

** This bug has been marked a duplicate of bug 1514474
   package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  I didnt see a bug for the 6.04 tex-common, so im submitting this. I did an in 
place upgrade from ubuntu 14.04 to 16.04.
I just rebooted for the second time after the upgrade, so im not sure if 
its going to 'fix itself' after a few more reboots or not. Each time im 
rebooting various things seem to be getting better (first reboot had all kinds 
of problems, updater didnt work, no wifi access, gui broken but still there). 
After this 2nd update, the updater says im 'up to date', the wifi is working, 
and the gui is closer to normal. Will report back if problems persist. Feel 
free to ask for more details, or log files. Im assuming you can contact me from 
inside launchpad without me having to post my email addy.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  Date: Fri Nov 24 02:02:40 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  02:02:28
   Requested-By: jonny2 (1000)
   Install: fonts-droid-fallback:i386 (1:6.0.1r16-1, automatic)
   Upgrade: renpy-thequestion:i386 (6.15.7-1ubuntu1, 6.99.8+dfsg-2), renpy:i386 
(6.15.7-1ubuntu1, 6.99.8+dfsg-2)
   Remove: fonts-droid:i386 (1:4.3-3ubuntu1.2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-09-09 (1902 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-11-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1734294/+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 1734727] Re: Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

[Till Kamppeter]

** Also affects: hplip
   Importance: Undecided
   Status: New

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

Title:
  Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  New

Bug description:
  BEHAVIOR
  When I left-click or right-click on the HP menu in the top right of the 
Ubuntu 17.10 top bar, the menu doesn't appear.

  STEPS TO REPRODUCE
  (1) open a terminal
  (2) type "sudo apt install hplip-gui"
  (3) open HP toolbox
  (4) Restart PC
  (4) After restart, try to left or right-click the hp icon in the appindicator 
menu at the top-right.

  EXPECTED BEHAVIOR
  For the menu to appear when you left or right-click it (probably left-click)

  BUG DISCOVERED USING
  HPLIP Software vertion 3.17.7
  Ubuntu 17.10 x64
  GNOME Shell 3.26.1
  Linux kernel 4.13.0-17-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1734727/+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 1734735] [NEW] [xenial] nm-openvpn continuously retries with bad password after receiving AUTH_FAIL locking out my account

[Ryan Stark]

Public bug reported:

I have nm-openvpn configured via the network manager gui on Xenial with
a saved password. My organization has a password expiration policy of X
days. If I forgot to update the saved password for nm-openvpn and try to
VPN in, nm-openvpn tries the connection, fails without notice in the UI
and retries until I stop it. This ultimately causes my account to get
locked out for too many invalid auth attempts.

sanitized/censored from syslog:
Nov 27 09:11:06 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971] 
started
Nov 27 09:11:06 carbon nm-openvpn[4971]: OpenVPN 2.3.10 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Jun 22 2017
Nov 27 09:11:07 carbon nm-openvpn[4971]: library versions: OpenSSL 1.0.2g  1 
Mar 2016, LZO 2.08
Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: file 
'/home/myusername/Downloads/certs/ta.key' is group or others accessible
Nov 27 09:11:07 carbon nm-openvpn[4971]: Control Channel Authentication: using 
'/home/myusername/Downloads/certs/ta.key' as a OpenVPN static key file
Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: chroot will be delayed because 
of --client, --pull, or --up-delay
Nov 27 09:11:07 carbon nm-openvpn[4971]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link local: [undef]
Nov 27 09:11:07 carbon nm-openvpn[4971]: UDPv4 link remote: 
[AF_INET]10.0.28.166:1195
Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
Nov 27 09:11:07 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
Nov 27 09:11:07 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer Connection 
Initiated with [AF_INET]10.0.28.166:1195
Nov 27 09:11:10 carbon nm-openvpn[4971]: AUTH: Received control message: 
AUTH_FAILED
Nov 27 09:11:10 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, 
process restarting
Nov 27 09:11:10 carbon NetworkManager[1173]: (nm-openvpn-service:4894): 
nm-openvpn-WARNING **: Password verification failed
Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
Nov 27 09:11:12 carbon nm-openvpn[4971]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link local: [undef]
Nov 27 09:11:12 carbon nm-openvpn[4971]: UDPv4 link remote: 
[AF_INET]10.0.28.166:1195
Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
Nov 27 09:11:12 carbon nm-openvpn[4971]: WARNING: this cipher's block size is 
less than 128 bit (64 bit).  Consider using a --cipher with a larger block size.
Nov 27 09:11:12 carbon nm-openvpn[4971]: [VPNGate.example.com] Peer Connection 
Initiated with [AF_INET]10.0.28.166:1195
Nov 27 09:11:15 carbon nm-openvpn[4971]: AUTH: Received control message: 
AUTH_FAILED
Nov 27 09:11:15 carbon nm-openvpn[4971]: SIGUSR1[soft,auth-failure] received, 
process restarting
...
...
[eventually I caught on to what was happening and stopped it]
...
...
Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971]: 
send SIGTERM
Nov 27 09:12:00 carbon nm-openvpn[4971]: event_wait : Interrupted system call 
(code=4)
Nov 27 09:12:00 carbon nm-openvpn[4971]: SIGTERM[hard,] received, process 
exiting
Nov 27 09:12:00 carbon NetworkManager[1173]: nm-openvpn-Message: openvpn[4971] 
exited with success


(and yes, I know I should fix the cipher and key file permissions)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [xenial] nm-openvpn continuously retries with bad password after
  receiving AUTH_FAIL locking out my account

Status in network-manager-openvpn package in Ubuntu:
  New

Bug description:
  I have nm-openvpn configured via the network manager gui on Xenial
  with a saved password. My organization has a password expiration
  policy of X days. If I forgot to update the saved password for nm-
  openvpn and try to VPN in, nm-openvpn tries the connection, fails
  without notice in the UI and retries until I stop it. This ultimately
  causes my account to get locked out for too 

[Desktop-packages] [Bug 1431753] Fw (1): us:

[Zewbie]

..

http://binaturalperu.com/bqgjlv.php?8j309jo






__

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

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Fix Released
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Fix Released

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+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 1734727] [NEW] Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

[Jesse]

Public bug reported:

BEHAVIOR
When I left-click or right-click on the HP menu in the top right of the Ubuntu 
17.10 top bar, the menu doesn't appear.

STEPS TO REPRODUCE
(1) open a terminal
(2) type "sudo apt install hplip-gui"
(3) open HP toolbox
(4) Restart PC
(4) After restart, try to left or right-click the hp icon in the appindicator 
menu at the top-right.

EXPECTED BEHAVIOR
For the menu to appear when you left or right-click it (probably left-click)

BUG DISCOVERED USING
HPLIP Software vertion 3.17.7
Ubuntu 17.10 x64
GNOME Shell 3.26.1
Linux kernel 4.13.0-17-generic

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

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

Title:
  Menu doesn't show up in Ubuntu gnome-shell appindicator when clicked

Status in hplip package in Ubuntu:
  New

Bug description:
  BEHAVIOR
  When I left-click or right-click on the HP menu in the top right of the 
Ubuntu 17.10 top bar, the menu doesn't appear.

  STEPS TO REPRODUCE
  (1) open a terminal
  (2) type "sudo apt install hplip-gui"
  (3) open HP toolbox
  (4) Restart PC
  (4) After restart, try to left or right-click the hp icon in the appindicator 
menu at the top-right.

  EXPECTED BEHAVIOR
  For the menu to appear when you left or right-click it (probably left-click)

  BUG DISCOVERED USING
  HPLIP Software vertion 3.17.7
  Ubuntu 17.10 x64
  GNOME Shell 3.26.1
  Linux kernel 4.13.0-17-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1734727/+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 1162288] Re: rhythmbox crashed with SIGSEGV

[Bug Watch Updater]

** Changed in: rhythmbox
   Status: Expired => Fix Released

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

Title:
  rhythmbox crashed with SIGSEGV

Status in Rhythmbox:
  Fix Released
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Drag and drop the album art on itself makes Rhythmbox crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: rhythmbox 2.98-0ubuntu3
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sat Mar 30 12:48:27 2013
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2013-03-29 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130328)
  MarkForUpload: True
  ProcCmdline: rhythmbox
  SegvAnalysis:
   Segfault happened at: 0x7fd310e607cb:mov(%rax),%rdi
   PC (0x7fd310e607cb) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/librhythmbox-core.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: rhythmbox crashed with SIGSEGV
  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/rhythmbox/+bug/1162288/+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 1728072] Re: [SRU] libreoffice 5.4.2 for artful

[Łukasz Zemczak]

Olivier, could you take a look at the mentioned bug by the bot? I would
like to make sure this does not introduce any regression.

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

Title:
  [SRU] libreoffice 5.4.2 for artful

Status in libreoffice package in Ubuntu:
  Fix Committed
Status in libreoffice-l10n package in Ubuntu:
  Fix Committed
Status in libreoffice source package in Artful:
  Fix Committed
Status in libreoffice-l10n source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * LibreOffice 5.4.2 is the second bugfix release of the fresh 5.4 line, 
after 5.4.1 (currently in 17.10).
 For a list of fixed bugs compared to 5.4.1 see the list of bugs fixed in 
RC1 and RC2:
   https://wiki.documentfoundation.org/Releases/5.4.2/RC1#List_of_fixed_bugs
   https://wiki.documentfoundation.org/Releases/5.4.2/RC2#List_of_fixed_bugs

   * Given the nature of the project, the complexity of the codebase and
  the high level of quality assurance upstream, it is preferable to SRU
  a minor release rather than cherry-pick selected bug fixes.

   * Libreoffice 5.4.2 (RC2, which is effectively the final release) has
  been available for users to test since 2017-10-04 in the official
  "LibreOffice Pre-Releases" PPA
  (https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-
  prereleases/+packages).

  
  [Test Case]

   * No specific test case, bugs fixed upstream hopefully come with
  unit/regression tests, and the release itself is extensively exercised
  upstream (both in an automated manner and manually) by a community of
  testers. The release went through 2 release candidates.

   * The libreoffice packages include autopkgtests, those should be run
  and verified to pass.

   * General smoke testing of all the applications in the office suite
  should be carried out.

  
  [Regression Potential] 

   * A new release with more than 100 bug fixes always carries the
  potential for introducing regressions, even though it's a bugfix-only
  release, meaning that no new features were added, and no existing
  features were removed.

   * A combination of autopkgtests and careful smoke testing as
  described above should provide reasonable confidence that no
  regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1728072/+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 1716359] Update Released

[Brian Murray]

The verification of the Stable Release Update for unity-control-center
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Invalid
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+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 1716359] Re: Unplugging headset with audio panel open mutes internal mic

[Launchpad Bug Tracker]

This bug was fixed in the package unity-control-center -
15.04.0+16.04.20170214-0ubuntu2

---
unity-control-center (15.04.0+16.04.20170214-0ubuntu2) xenial; urgency=medium

  [ Andrea Azzarone ]
  * sound: Discard selection-changed events that are not triggered
by the user (lp: #1716359)

 -- Sebastien Bacher   Tue, 31 Oct 2017 16:50:03
+0100

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: Incomplete => Fix Released

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

Title:
  Unplugging headset with audio panel open mutes internal mic

Status in OEM Priority Project:
  Fix Committed
Status in unity-control-center package in Ubuntu:
  Invalid
Status in unity-control-center source package in Xenial:
  Fix Released

Bug description:
  
  Impact
  ==
  This is required by OEM team.

  Test Case
  =
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

  Make sure the internal mic is not muted.

  Regression Potential
  ===
  - Make sure that plugging/unplugging headphones does the correct thing.
  - Make sure that manually selecting an headphone actually switch mic.
  - Please also check that output sound works too.

  Original Bug Report
  ===
  This bug was reported by our OEM team, I'm opening this public bug.

  The internal microphone is muted after he headset is unplugged when the 
System Settings is running.
  We can not reproduce this bug when closed the System Settings window before 
unplugged the headset.

  Reproduce steps:
  1. Open System Settings -> Sound -> select the input tab
  2. Plug headset and select Headset on Unknown Audio Device dialog.
  3. Check external mic is working
  4. Adjust the internal microphone volume.(Just change the volume value.)
  5. Adjust headset input volume around 100% in Input tab from Sound settings
  6. Unplug headset
  7. Check internet mic status

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1716359/+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 1734720] [NEW] /usr/lib/gvfs/gvfsd-smb-browse:6:talloc_abort:talloc_abort_magic:talloc_chunk_from_ptr:__talloc_with_prefix:__talloc

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful trusty wily xenial yakkety zesty

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

Title:
  /usr/lib/gvfs/gvfsd-smb-
  
browse:6:talloc_abort:talloc_abort_magic:talloc_chunk_from_ptr:__talloc_with_prefix:__talloc

Status in gvfs package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1734720/+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 1365926] Re: The “Enable this account” item in the new account settings page doesn’t work.

[Anthony Wong]

** Changed in: ubuntukylin
 Assignee: Anthony Wong (anthonywong) => (unassigned)

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

Title:
  The “Enable this account” item in the new account settings page
  doesn’t work.

Status in Ubuntu Kylin:
  Confirmed
Status in unity-control-center package in Ubuntu:
  New

Bug description:
  The “Enable this account” item in the new account settings page
  doesn’t work.

  Steps:
  1. Enter into System settings-->User Accounts
  2. Click Unlock in this page
  3. Add a new account
  4. Enter into the new account setting page, click the drop list at the right 
of "Password" item
  5. Chose Enable this account from Action list
  -->Failed. This item doesn't work

  Configuration:
  PC: Dell Vostro
  OS: Ubuntu Kylin 14.10 x32 Daily 20140905

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1365926/+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 1734716] [NEW] /usr/bin/nm-applet:11:nma_icon_check_and_load:foo_set_icon:applet_update_icon:g_main_dispatch:g_main_context_dispatch

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: xenial yakkety zesty

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

Title:
  /usr/bin/nm-
  
applet:11:nma_icon_check_and_load:foo_set_icon:applet_update_icon:g_main_dispatch:g_main_context_dispatch

Status in network-manager-applet package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1734716/+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 1732454] Re: Reply to message composer window opens behind main evolution window

[Launchpad Bug Tracker]

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

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

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

Title:
  Reply to message composer window opens behind main evolution window

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  In evolution, open a message which opens a 'message reader' window.

  In that window press the 'Reply' button - this opens a new 'message
  composer' window in which to type the reply

  In 17.10 running under gnome-shell, the composer window is opened, but
  it also seems that the main Evolution window is also brought to the
  front ... leaving the newly opened composer window behind in the
  window stack.

  Running 17.10 with the old unity does not have this problem

  So I guess this bug may be a problem with gnome-shell rather than
  evolution - something is making it ping the main application window to
  the front.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+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 1733970] Re: Google search suggestions do not work due to erroneous URL

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 57.0+build4-0ubuntu0.14.04.5

---
firefox (57.0+build4-0ubuntu0.14.04.5) trusty-security; urgency=medium

  * Fix LP: #1733970 - Search suggestions are broken after refreshing the
Google searchplugin
  * Fix a missing token in the user agent string
- update debian/patches/ubuntu-ua-string-changes.patch
- update debian/patches/support-coinstallable-trunk-build.patch
- update debian/build/rules.mk
- update debian/config/mozconfig.in

 -- Chris Coulson   Thu, 23 Nov 2017
17:02:23 +

** Changed in: firefox (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Google search suggestions do not work due to erroneous URL

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Release: Ubuntu 17.04
  Package: firefox 57.0+build4-0ubuntu0.17.10.5

  Google search suggestions (i.e. completion of search terms in the
  address bar) will not work in this release.

  Investigation shows that the problem lies in e.g.
  /usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml

  Search suggestions are configured to use this URL:
  https://www.google.com/complete/search?client=ubuntu={searchTerms}

  However testing shows that this URL always fails with a 400 error, but if you 
replace the "ubuntu" in the URL with "firefox" (as the vanilla Firefox release 
has it) then it does work.
  Compare the responses for these URLs:
  https://www.google.com/complete/search?client=ubuntu=test
  https://www.google.com/complete/search?client=firefox=test

  So if I change "ubuntu" to "firefox" in google.xml, and then start
  Firefox with a new profile, Google search suggestions start workng
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733970/+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 1733970] Re: Google search suggestions do not work due to erroneous URL

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 57.0+build4-0ubuntu0.17.10.6

---
firefox (57.0+build4-0ubuntu0.17.10.6) artful-security; urgency=medium

  * Fix LP: #1733970 - Search suggestions are broken after refreshing the
Google searchplugin
  * Fix a missing token in the user agent string
- update debian/patches/ubuntu-ua-string-changes.patch
- update debian/patches/support-coinstallable-trunk-build.patch
- update debian/build/rules.mk
- update debian/config/mozconfig.in

 -- Chris Coulson   Thu, 23 Nov 2017
13:18:24 +

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

Title:
  Google search suggestions do not work due to erroneous URL

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Release: Ubuntu 17.04
  Package: firefox 57.0+build4-0ubuntu0.17.10.5

  Google search suggestions (i.e. completion of search terms in the
  address bar) will not work in this release.

  Investigation shows that the problem lies in e.g.
  /usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml

  Search suggestions are configured to use this URL:
  https://www.google.com/complete/search?client=ubuntu={searchTerms}

  However testing shows that this URL always fails with a 400 error, but if you 
replace the "ubuntu" in the URL with "firefox" (as the vanilla Firefox release 
has it) then it does work.
  Compare the responses for these URLs:
  https://www.google.com/complete/search?client=ubuntu=test
  https://www.google.com/complete/search?client=firefox=test

  So if I change "ubuntu" to "firefox" in google.xml, and then start
  Firefox with a new profile, Google search suggestions start workng
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733970/+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 1732454] Re: Reply to message composer window opens behind main evolution window

[bastubis]

Same issue, Ubuntu 17.10 with upstream vanilla GNOME shell and Evo
3.26.1-1 - when opened from the message window, the composer window is
opening behind the main suite window. You have to spread the windows to
find it.

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

Title:
  Reply to message composer window opens behind main evolution window

Status in evolution package in Ubuntu:
  Confirmed

Bug description:
  In evolution, open a message which opens a 'message reader' window.

  In that window press the 'Reply' button - this opens a new 'message
  composer' window in which to type the reply

  In 17.10 running under gnome-shell, the composer window is opened, but
  it also seems that the main Evolution window is also brought to the
  front ... leaving the newly opened composer window behind in the
  window stack.

  Running 17.10 with the old unity does not have this problem

  So I guess this bug may be a problem with gnome-shell rather than
  evolution - something is making it ping the main application window to
  the front.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1732454/+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 1733970] Re: Google search suggestions do not work due to erroneous URL

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 57.0+build4-0ubuntu0.17.04.6

---
firefox (57.0+build4-0ubuntu0.17.04.6) zesty-security; urgency=medium

  * Fix LP: #1733970 - Search suggestions are broken after refreshing the
Google searchplugin
  * Fix a missing token in the user agent string
- update debian/patches/ubuntu-ua-string-changes.patch
- update debian/patches/support-coinstallable-trunk-build.patch
- update debian/build/rules.mk
- update debian/config/mozconfig.in

 -- Chris Coulson   Thu, 23 Nov 2017
16:47:12 +

** Changed in: firefox (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: firefox (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Google search suggestions do not work due to erroneous URL

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Release: Ubuntu 17.04
  Package: firefox 57.0+build4-0ubuntu0.17.10.5

  Google search suggestions (i.e. completion of search terms in the
  address bar) will not work in this release.

  Investigation shows that the problem lies in e.g.
  /usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml

  Search suggestions are configured to use this URL:
  https://www.google.com/complete/search?client=ubuntu={searchTerms}

  However testing shows that this URL always fails with a 400 error, but if you 
replace the "ubuntu" in the URL with "firefox" (as the vanilla Firefox release 
has it) then it does work.
  Compare the responses for these URLs:
  https://www.google.com/complete/search?client=ubuntu=test
  https://www.google.com/complete/search?client=firefox=test

  So if I change "ubuntu" to "firefox" in google.xml, and then start
  Firefox with a new profile, Google search suggestions start workng
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733970/+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 1721248] Re: Totem could not get a screenshot of the video

[corrado venturini]

Done some more test installing Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20171126)
on various partitions of same disk on my PC:
Problem does NOT occur with live session
Problem does NOT occur with an installation in us-english - installation default
problem DOES occur with an installation in italian - language italian locale 
italian
problem DOES occur with an installation in english-italian - language english 
locale italian
problem DOES occur with the above installation also changing locale to english:
corrado@corrado-p8-bb-1126:~$ inxi -S
System:Host: corrado-p8-bb-1126 Kernel: 4.13.0-16-generic x86_64 bits: 64
   Desktop: Gnome 3.26.2
   Distro: Ubuntu Bionic Beaver (development branch)
corrado@corrado-p8-bb-1126:~$ locale
LANG=en_US.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
corrado@corrado-p8-bb-1126:~$

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

Title:
  Totem could not get a screenshot of the video

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  I try to get a screenshot from my video and totem shows a message
  saying it could not get a screenshot of the video and suggesting to
  open a bug. See attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.25.90.1-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 14:54:16 2017
  InstallationDate: Installed on 2017-09-29 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+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 1733970] Re: Google search suggestions do not work due to erroneous URL

[Prahlad Yeri]

The quantum release was otherwise great, except for this little glitch.
There is a similar bug raised on Mozilla support forum
(https://support.mozilla.org/en-US/questions/1188416), and I wasn't
surprised that the issue lied at the Canonical end. It looks like you
have messed up the location of the Google search bar plugin, while that
of other plugins are intact, as one comment in that thread mentions:

> The main thing I notice is that the Google search plugin is located in
a folder under [distribution] while the others are in the compressed
program file omni.ja:

"_name":"Google","_shortName":"google",
"_loadPath":"[distribution]/searchplugins/locale/en-US/google.xml"

"_name":"Yahoo","_shortName":"yahoo",
"_loadPath":"jar:[app]/omni.ja!browser/yahoo.xml"

"_name":"Bing","_shortName":"bing",
"_loadPath":"jar:[app]/omni.ja!browser/bing.xml"


Can you confirm when will this update available on Xenial?

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

Title:
  Google search suggestions do not work due to erroneous URL

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Release: Ubuntu 17.04
  Package: firefox 57.0+build4-0ubuntu0.17.10.5

  Google search suggestions (i.e. completion of search terms in the
  address bar) will not work in this release.

  Investigation shows that the problem lies in e.g.
  /usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml

  Search suggestions are configured to use this URL:
  https://www.google.com/complete/search?client=ubuntu={searchTerms}

  However testing shows that this URL always fails with a 400 error, but if you 
replace the "ubuntu" in the URL with "firefox" (as the vanilla Firefox release 
has it) then it does work.
  Compare the responses for these URLs:
  https://www.google.com/complete/search?client=ubuntu=test
  https://www.google.com/complete/search?client=firefox=test

  So if I change "ubuntu" to "firefox" in google.xml, and then start
  Firefox with a new profile, Google search suggestions start workng
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733970/+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 1734666] Re: gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()

[Apport retracing service]

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

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 #1712961, 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/1734666/+attachment/5015217/+files/CoreDump.gz

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

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

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

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

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

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

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

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

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

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

Bug description:
  Trying to access the audio settings panel triggers this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-control-center 1:3.18.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Nov 27 14:15:13 2017
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2017-07-25 (125 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: gnome-control-center --overview
  SegvAnalysis:
   Segfault happened at: 0x7fe2ddf1d924 <__GI_strtoul_l_internal+68>:   
movsbq (%r14),%rax
   PC (0x7fe2ddf1d924) ok
   source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   __GI_strtoul_l_internal (nptr=0x0, endptr=0x7ffcf5eb89a8, base=10, 
group=, loc=0x7fe2de2a4b60 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:293
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
  Title: gnome-control-center crashed with SIGSEGV in 
__GI_strtoul_l_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1734666/+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 1734669] [NEW] Long texts in windows overlap with icon on the left

[Robert Orzanna]

Public bug reported:

The attached screenshot should make clear what I mean.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.26.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 27 12:39:02 2017
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' 
b"['appindicatorsupp...@rgcjonas.gmail.com', 'ubuntu-d...@ubuntu.com', 
'updateindica...@aegirxx.googlemail.com', 'dejadup-launcher@stefano.facchini', 
'active-notifications-indicator@nls1729', 'xcaffe...@asegner.gmail.com', 
'gnome-shell-screens...@ttll.de', 'clipboard-indica...@tudmotu.com', 
'caffe...@patapon.info', 'updates-dia...@rtcm.fedorapeople.org', 
'drop-down-termi...@gs-extensions.zzrough.org', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 'tinkerer@joebodo', 
'apt-update-indica...@franglais125.gmail.com', 'topic...@phocean.net']"
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Terminal.desktop', 'google-chrome.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2017-11-12 (14 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic wayland-session

** Attachment added: "glitch.png"
   https://bugs.launchpad.net/bugs/1734669/+attachment/5015240/+files/glitch.png

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

Title:
  Long texts in windows overlap with icon on the left

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The attached screenshot should make clear what I mean.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.8-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 27 12:39:02 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' 
b"['appindicatorsupp...@rgcjonas.gmail.com', 'ubuntu-d...@ubuntu.com', 
'updateindica...@aegirxx.googlemail.com', 'dejadup-launcher@stefano.facchini', 
'active-notifications-indicator@nls1729', 'xcaffe...@asegner.gmail.com', 
'gnome-shell-screens...@ttll.de', 'clipboard-indica...@tudmotu.com', 
'caffe...@patapon.info', 'updates-dia...@rtcm.fedorapeople.org', 
'drop-down-termi...@gs-extensions.zzrough.org', 
'drive-m...@gnome-shell-extensions.gcampax.github.com', 'tinkerer@joebodo', 
'apt-update-indica...@franglais125.gmail.com', 'topic...@phocean.net']"
   b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 
'org.gnome.Terminal.desktop', 'google-chrome.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2017-11-12 (14 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (2017)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1734669/+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 1718336] Re: Firefox requires PulseAudio for working sound again

[Adolfo Jayme]

** Changed in: firefox (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Firefox requires PulseAudio for working sound again

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 17.10 dev with Firefox 55.0.2+build1-0ubuntu4 and
  Firefox requires PulseAudio for working sound again. This is a
  regression of
  https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1671273 and
  there is a report at https://bugs.launchpad.net/ubuntu/+source
  /lubuntu-meta/+bug/1710993 but it seems to be Lubuntu-specific.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1718336/+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 1730433] Re: Keyboard not working at login screen

[David]

How do I attach the syslog? I would like to help. This bug is annoying!

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

Title:
  Keyboard not working at login screen

Status in unity-greeter package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 17.10 in use, keyboard (USB Corsair Strafe) often not working
  on login screen, especially after cold boot.

  I've checked other bug reports, but none show this as being fixed and
  it's affecting the latest Ubuntu at the time of writing this (version
  17.10). All latest updates installed.

  The keyboard is plugged in properly and when Ubuntu does recognise it
  after unplugging and reconnecting, the keyboard works fine (which
  rules out any hardware fault). Latest BIOS installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1730433/+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 1734649] [NEW] package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-l

[joubuntu]

Public bug reported:

I have this informations. What I can do about that??

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglib2.0-dev 2.48.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Sun Nov 26 15:06:32 2017
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
InstallationDate: Installed on 2017-11-23 (3 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: glib2.0
Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/x86_64-linux-
  gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-
  new': odottamaton tiedoston loppu tai jono

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have this informations. What I can do about that??

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Sun Nov 26 15:06:32 2017
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
  InstallationDate: Installed on 2017-11-23 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1734649/+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 1734649] Re: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to '/usr/lib/x86_64-lin

[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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1734649

Title:
  package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/x86_64-linux-
  gnu/libglib-2.0.a' to '/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-
  new': odottamaton tiedoston loppu tai jono

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  I have this informations. What I can do about that??

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglib2.0-dev 2.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Sun Nov 26 15:06:32 2017
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
  InstallationDate: Installed on 2017-11-23 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: glib2.0
  Title: package libglib2.0-dev 2.48.2-0ubuntu1 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libglib-2.0.a' to 
'/usr/lib/x86_64-linux-gnu/libglib-2.0.a.dpkg-new': odottamaton tiedoston loppu 
tai jono
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1734649/+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 854333] Re: ibus GUI not loading, unable to use input

[chenyalin]

sudo apt-get install gnome-icon-theme

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

Title:
  ibus GUI not loading, unable to use input

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Fix Released

Bug description:
  I'm using oneiric since alpha3, and despite all the updates and
  bugfixes, ibus is just not working under ubuntu, nor kubuntu.

  kernel: 3.0.0-11 (also previous versions)
  ibus: 1.3.99.20110419-1ubuntu3 (also ibus-gtk, ibus-gtk3, ibus-qt4, 
ibus-pinyin packages are installed and up-to-date, with all dependencies)
  kubuntu 11.10 

  The problem is that even though ibus-daemon starts up at login, but it
  doesn't do anything, the icon doesn't appear in the notificaion area,
  and I can't seem to switch to a different method with the hotkey
  either. When I try running ibus-daemon from the command line, i get
  the answer that it's already running for this session. Also there is
  no way under language support to install chinese language pack, only
  the translations, all the other options are greyed out (input methods,
  etc) since oneiric.

  There isn't any error messages whatsoever, it just doesn't work, and
  also the same with scim and uim too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/854333/+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 854333] Re: ibus GUI not loading, unable to use input

[chenyalin]

sudo apt-get install gnome-icon-theme

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

Title:
  ibus GUI not loading, unable to use input

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Fix Released

Bug description:
  I'm using oneiric since alpha3, and despite all the updates and
  bugfixes, ibus is just not working under ubuntu, nor kubuntu.

  kernel: 3.0.0-11 (also previous versions)
  ibus: 1.3.99.20110419-1ubuntu3 (also ibus-gtk, ibus-gtk3, ibus-qt4, 
ibus-pinyin packages are installed and up-to-date, with all dependencies)
  kubuntu 11.10 

  The problem is that even though ibus-daemon starts up at login, but it
  doesn't do anything, the icon doesn't appear in the notificaion area,
  and I can't seem to switch to a different method with the hotkey
  either. When I try running ibus-daemon from the command line, i get
  the answer that it's already running for this session. Also there is
  no way under language support to install chinese language pack, only
  the translations, all the other options are greyed out (input methods,
  etc) since oneiric.

  There isn't any error messages whatsoever, it just doesn't work, and
  also the same with scim and uim too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/854333/+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 1728547] Re: SRU: Add support for keeping the dGPU on in power saving mode

[Alex Tu]

verified on FIR5K-PILOT-C1 for zesty , it works as well.

** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1728547/+attachment/5015093/+files/gpu-manager.log

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

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

Title:
  SRU: Add support for keeping the dGPU on in power saving mode

Status in HWE Next:
  New
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Xenial:
  Fix Committed
Status in ubuntu-drivers-common source package in Zesty:
  Fix Committed
Status in ubuntu-drivers-common source package in Artful:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Some systems don't play well when the dGPU is disabled. It should still be 
possible to use the Intel iGPU without disabling the dGPU.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common"

  2) Make sure the nvidia packages are installed, and enable power saving mode:
  sudo prime-select intel

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Install the mesa-utils package:
  sudo apt install mesa-utils

  5) Check the output of the following command (which should mention Intel):
  glxinfo | grep OpenGL

  
  [Regression Potential]
  Low, as the feature is disabled by default. This is only for hardware 
specific workarounds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1728547/+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 1716633] Re: Installed, popular and featured snaps are loaded in parallel threads can crash

[Jean-Baptiste Lallement]

SRU Verification

>From errors.u.c [1] new crashes specific to version 3.26.1-0ubuntu2.17.10.1 
>all but one failed to retrace and could not be bucketed. Hence it is not 
>possible to take a decision based on these new crash reports. The crashes that 
>failed to retrace are:
https://errors.ubuntu.com/problem/169c8b88552a2231004318e45da0c61d14238d17
https://errors.ubuntu.com/problem/897b37ad31b25c3c042535a5f2fcb051a38c5e2a
https://errors.ubuntu.com/problem/e6a6f59139de19a51e1d9b6a546c4222cf0a8d5d
https://errors.ubuntu.com/problem/34980d512593c1800342e6bf5cb60ac988be5902
https://errors.ubuntu.com/problem/a3d20a0452b8d20985a14a66046b66dd94549055

The following crash report is new with the version in artful-proposed and has 
been reported as bug 1734630
https://errors.ubuntu.com/problem/627675f12f5f22a3d6b6ee73271c007681d1d0db

@Robert, could you have a look and tell if it has been introduced by the
new code in this SRU and could you give your opinion on the crashes that
failed to retrace?


Thanks.

[1] https://errors.ubuntu.com/?release=Ubuntu%2017.10=gnome-
software=week=3.26.1-0ubuntu2.17.10.1

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

Title:
  Installed, popular and featured snaps are loaded in parallel threads
  can crash

Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Triaged
Status in gnome-software source package in Zesty:
  Triaged
Status in gnome-software source package in Artful:
  Fix Committed
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  GNOME Software has a cache that can be accessed by multiple threads. This can 
cause GNOME Software to crash. This seems to have been caused by adding support 
for featured snaps (bug 1663097) as the popular, featured and installed snaps 
are all requested on different threads.

  [Test Case]
  Since this is a random crash there's not a good test case. Could be checked 
by looking at errors.ubuntu.com crash reports or repeated restarts of GNOME 
Software to see if it crashes on startup.

  [Regression Potential]
  Solution is to add a lock around this cache. Some risk of breaking related 
code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1716633/+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 1733970] Re: Google search suggestions do not work due to erroneous URL

[pavel]

Is there a way to restore Google search suggestions working with
existing Firefox profile?

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

Title:
  Google search suggestions do not work due to erroneous URL

Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Release: Ubuntu 17.04
  Package: firefox 57.0+build4-0ubuntu0.17.10.5

  Google search suggestions (i.e. completion of search terms in the
  address bar) will not work in this release.

  Investigation shows that the problem lies in e.g.
  /usr/lib/firefox/distribution/searchplugins/locale/en-GB/google.xml

  Search suggestions are configured to use this URL:
  https://www.google.com/complete/search?client=ubuntu={searchTerms}

  However testing shows that this URL always fails with a 400 error, but if you 
replace the "ubuntu" in the URL with "firefox" (as the vanilla Firefox release 
has it) then it does work.
  Compare the responses for these URLs:
  https://www.google.com/complete/search?client=ubuntu=test
  https://www.google.com/complete/search?client=firefox=test

  So if I change "ubuntu" to "firefox" in google.xml, and then start
  Firefox with a new profile, Google search suggestions start workng
  again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733970/+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 1734627] [NEW] /usr/bin/gnome-software:11:g_wakeup_signal:g_main_loop_quit:do_call:call_vanished_handler:call_vanished_handler

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful zesty

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

Title:
  /usr/bin/gnome-
  
software:11:g_wakeup_signal:g_main_loop_quit:do_call:call_vanished_handler:call_vanished_handler

Status in gnome-software package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734627/+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 1734628] [NEW] /usr/bin/gnome-software:11:__strlen_ia32:_IO_vfprintf_internal:__GI___vasprintf_chk:vasprintf:g_vasprintf

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful yakkety

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

Title:
  /usr/bin/gnome-
  
software:11:__strlen_ia32:_IO_vfprintf_internal:__GI___vasprintf_chk:vasprintf:g_vasprintf

Status in gnome-software package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734628/+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 1734630] [NEW] /usr/bin/gnome-software:7:_int_malloc:__libc_calloc:g_malloc0:g_hash_table_new_full:g_variant_dict_init

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful

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

Title:
  /usr/bin/gnome-
  
software:7:_int_malloc:__libc_calloc:g_malloc0:g_hash_table_new_full:g_variant_dict_init

Status in gnome-software package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734630/+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 1734629] [NEW] /usr/bin/gnome-software:*** Error in `/usr/bin/gnome-software': corrupted double-linked list: ADDR ***

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful xenial yakkety zesty

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

Title:
  /usr/bin/gnome-software:*** Error in `/usr/bin/gnome-software':
  corrupted double-linked list: ADDR ***

Status in gnome-software package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734629/+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