Re: [Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

[Steve Langasek]

On Sun, Oct 22, 2017 at 12:04:01AM -, Julian Andres Klode wrote:
> Because let's face it: If A suggests B, B provides or modifies
> functionality for A, so removing B might just break your use case of A.

That is absolutely not apt's responsibility to handle, when the admin has
never indicated to the package manager that they want to keep B; and is
nothing when weighed against the asymmetry that causes package cruft to be
kept around on every user's systems after upgrade.

A user who discovers after autoremovals that she wants B installed can
install B from the archive.  But a user who just wants no-longer-needed
packages to be autoremoved has no reasonable way to get this - because
that's what 'autoremove' is supposed to imply already, but it doesn't
actually deliver unless you track down this non-obvious apt setting and
tweak your config.

If 'apt install A=1; apt install A=2; apt autoremove --purge' gives
different results than 'apt install A=2; apt autoremove --purge', then that
is a bug.  Sometimes it's a bug in a package.  In this case, it's a bug in
the package manager.

The current behavior is not a sensible default.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  New

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1724955] Re: unable to drag monitors in Display Arrangement

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724955

Title:
  unable to drag monitors in Display Arrangement

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am unable to drag the displays in the Display Arrangement section.
  I have a dual monitor setup and they are in the reverse order.

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

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

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

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+subscriptions

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

[Touch-packages] [Bug 1721839] Re: Services asked for by UDEV do not get triggered

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1721839

Title:
  Services asked for by UDEV do not get triggered

Status in systemd:
  New
Status in Release Notes for Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The packages system-config-printer-udev and ippusbxd are installed,
  having the following UDEV rule files:

  /lib/udev/rules.d/70-printers.rules

  --
  # Low-level USB device add trigger
  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", 
TAG+="systemd", PROGRAM="/bin/systemd-escape 
--template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c"
  # Low-level USB device remove trigger
  ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", 
ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p"
  --

  /lib/udev/rules.d/55-ippusbxd.rules

  --
  # ippusbxd udev rules file

  ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" 
ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", 
PROGRAM="/bin/systemd-escape --template=ippusbxd@.service 
$env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c"
  --

  If I turn on an appropriate printer (USB, supporting IPP-over-USB,
  here the HP DeskJet 2540) I get in the output of "udevadm monitor
  --environment"

  --
  UDEV  [17527.514150] add  /devices/pci:00/:00:14.0/usb2/2-2 (usb)
  ACTION=add
  BUSNUM=002
  DEVNAME=/dev/bus/usb/002/033
  DEVNUM=033
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2
  DEVTYPE=usb_device
  DRIVER=usb
  ID_BUS=usb
  ID_MODEL=Deskjet_2540_series
  ID_MODEL_ENC=Deskjet\x202540\x20series
  ID_MODEL_ID=c211
  ID_REVISION=0100
  ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK
  ID_SERIAL_SHORT=BR54BFB02C05XK
  ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401:
  ID_VENDOR=HP
  ID_VENDOR_ENC=HP
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  ID_VENDOR_ID=03f0
  MAJOR=189
  MINOR=160
  PRODUCT=3f0/c211/100
  SEQNUM=9891
  SUBSYSTEM=usb
  SYSTEMD_WANTS=ippusbxd@002:033.service 
udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service 
printer.target
  TAGS=:udev-configure-printer:systemd:
  TYPE=0/0/0
  USEC_INITIALIZED=17527513940

  UDEV  [17527.517724] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb)
  .MM_USBIFNUM=00
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/204/0
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00
  PRODUCT=3f0/c211/100
  SEQNUM=9892
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527517478

  UDEV  [17527.522565] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb)
  .MM_USBIFNUM=02
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2
  DEVTYPE=usb_interface
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=255/4/1
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02
  PRODUCT=3f0/c211/100
  SEQNUM=9895
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527522332

  UDEV  [17527.523761] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb)
  .MM_USBIFNUM=01
  ACTION=add
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1
  DEVTYPE=usb_interface
  DRIVER=usblp
  ID_VENDOR_FROM_DATABASE=Hewlett-Packard
  INTERFACE=7/1/2
  MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01
  PRODUCT=3f0/c211/100
  SEQNUM=9893
  SUBSYSTEM=usb
  TYPE=0/0/0
  USEC_INITIALIZED=17527523500

  UDEV  [17527.527275] add  
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc)
  .MM_USBIFNUM=01
  ACTION=add
  DEVNAME=/dev/usb/lp1
  DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1
  MAJOR=180
  MINOR=1
  SEQNUM=9894
  SUBSYSTEM=usbmisc
  USEC_INITIALIZED=17527527175
  --

  Here one can see that the UDEV rules files are correct, leading to the
  correct systemd services being requested

  SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer
  @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target

  but neither the service ippusbxd@002:033.service nor the service udev-
  configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service
  get started (note that I have put the .service file for ippusbxd in
  place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service
  /lib/systemd/system/").

  I can start each of these services manually though:

  sudo systemctl start 'udev-configure-printer@-devices-
  pci:00-:00:14.0-usb2-2\x2d2.service'

  sudo systemctl start ippusbxd@002:033.service

  In each 

[Touch-packages] [Bug 1718931] Re: No VPN autoconnect

[Nicholas Stommel]

Literally just toggling that one option "Store password for all users"
in the VPN settings fixes the problem entirely. Use "sudo service
network-manager restart" and it connects flawlessly the first time. To
avoid the error loop on bootup specifically, just uncheck the box "Make
available to other users" on the primary connection.

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

Title:
  No VPN autoconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   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.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions

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

[Touch-packages] [Bug 1697769] Re: tracker doesn't automatically start when installed until after log out and log in

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1697769

Title:
  tracker doesn't automatically start when installed until after log out
  and log in

Status in Release Notes for Ubuntu:
  Fix Released
Status in tracker package in Ubuntu:
  Confirmed
Status in tracker package in Debian:
  New

Bug description:
  One problem with Ubuntu not enabling tracker by default is that
  several apps depend on tracker for basic functionality.

  A user installs gnome-photos, opens the app and sees none of the
  pictures from her ~/Pictures/ directory. She needs to log out and then
  log back in for the tracker services to start running and her app to
  work.

  tracker uses systemd user services now.

  Workaround
  --
  Log out and log back in after installing tracker

  Affected GNOME apps
  ---
  Books
  Documents
  Games
  Music
  Photos

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1697769/+subscriptions

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

[Touch-packages] [Bug 1718931] Re: No VPN autoconnect

[Nicholas Stommel]

Yeah, I keep getting the "vpn-connection[...]: Failed to request VPN
secrets #3: No agents were available for this request." error message in
my syslog. I found, however, that THIS worked for me: All you have to do
is go Dash->VPN->VPN
Settings->connection_name_here->Identity->Password->"Store for all
users" and bingo problem solved. If nm-connection-editor says that you
can't save the connection (the save box is grayed out), then...just
forget the network and set up the connection again (worked for me at
least). Once you have checked said auto-connect box with nm-connection-
editor and ensured that the VPN password is set to "Store for all
users," both the primary connection AND the VPN will start successfully
at the same time. See my post at https://askubuntu.com/questions/967408
/how-to-automatically-connect-to-vpn-in-ubuntu-17-10/967415#967415

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

Title:
  No VPN autoconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   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.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions

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

[Touch-packages] [Bug 1685542] Re: xserver libinput and synaptics conflict on mouse/touchpad settings

[Mathew Hodson]

** Tags removed: gnome-17.10
** Tags added: packaging

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1685542

Title:
  xserver libinput and synaptics conflict on mouse/touchpad settings

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  xserver-xorg-input-all was installed. As a result, both xserver-xorg-
  input synaptics and xserver-xorg-input-libinput got installed.

  This breaks usage for both natural scrolling *and* moving the primary
  button of the mouse/touchpad to the right (a.k.a. typing while being
  left-handed).

  Purging xserver-xorg-input-synaptics resolves it, with both natural
  scrolling and left-handedness now working.

  This bug only affects Gnome; KDE and Unity work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-input-all (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Apr 22 14:44:44 2017
  DistUpgraded: 2016-12-02 17:02:11,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:0655]
  InstallationDate: Installed on 2016-02-08 (439 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  MachineType: System76, Inc. Gazelle Professional
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro text
  SourcePackage: xorg
  UpgradeStatus: Upgraded to zesty on 2016-12-02 (140 days ago)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.05RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp9
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: gazp9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.05RS76:bd08/15/2013:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp9:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp9:cvnSystem76,Inc.:ct9:cvrgazp9:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp9
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 22 14:35:09 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

[Mathew Hodson]

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1686081

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  Confirmed
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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

[Touch-packages] [Bug 635149] ✈OMG it's true

[orowitz]

Hey,

I've just found something really interesting and OMG ... it s
amazing, just take a look
http://www.cyclingburma.com/rglosaiw/goren/rise.php?UE82MzUxNDlAYnVncy5sYXVuY2hwYWQubmV0


Best regards, mauro gardenal


From: Bug 635149 [mailto:635...@bugs.launchpad.net]
Sent: Saturday, October 21, 2017 8:28 PM
To: mauro.garde...@libero.it
Subject: You too!

My now 4 year old did this at around 2. We never really figured out the
exact  cause  but we  suspect it was either  reflux or food related.
There  was a particular brand  of milk (Goldenrod) that we would pick up
from the local  convenient store sometimes  and it  seemed to coincide
with that. He  doesn't have any reflux issues or food  allergies now. He
kind of just stopped doing  it at around 3 year old.  The only  thing
is anything Flaming  Hot flavored like chips or cheetoes will make him
throw up every time, usually in the  night. We haven't  encountered any
other foods that do this to him.


Sent from Mail for Windows 10

** Attachment added: "F2B46F9E13C722F4.jpg"
   
https://bugs.launchpad.net/bugs/635149/+attachment/4983828/+files/F2B46F9E13C722F4.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to diffutils in Ubuntu.
https://bugs.launchpad.net/bugs/635149

Title:
  package diff 2.8.1-13 failed to install/upgrade:during upgrade from
  9.10 to 10.04

Status in diffutils package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: diffutils

  during upgrade from 9.10 to 10.04 on a fresh install (maybe no good
  hardware?, old laptop?)

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: diff 2.8.1-13
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  Uname: Linux 2.6.31-14-generic i686
  Architecture: i386
  Date: Fri Sep 10 18:31:50 2010
  ErrorMessage:
   ErrorMessage: package diff is not ready for configuration  cannot configure 
(current status `half-installed')
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  SourcePackage: diffutils
  Title: package diff 2.8.1-13 failed to install/upgrade:

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

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

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

[Mathew Hodson]

** Tags added: regression-release

** Tags removed: regression

** Tags removed: release-blocker

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

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

[Touch-packages] [Bug 1725878] [NEW] HP Probook 4515s

[Pertti Ahvonen]

Public bug reported:

System update and boot file size problems :(

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
Uname: Linux 3.13.0-129-generic i686
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Oct 22 04:17:00 2017
DistUpgraded: 2017-07-09 14:18:03,311 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:3077]
InstallationDate: Installed on 2017-03-06 (229 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: Hewlett-Packard HP ProBook 4515s
ProcEnviron:
 LANGUAGE=fi
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 nopat 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2017-07-09 (104 days ago)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GPI Ver. F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3077
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 25.0C
dmi.chassis.asset.tag: CNU9320V0W
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPIVer.F.06:bd06/17/2009:svnHewlett-Packard:pnHPProBook4515s:pvrF.06:rvnHewlett-Packard:rn3077:rvrKBCVersion25.0C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4515s
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Oct 21 23:05:19 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.9
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725878

Title:
  HP Probook 4515s

Status in xorg package in Ubuntu:
  New

Bug description:
  System update and boot file size problems :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Oct 22 04:17:00 2017
  DistUpgraded: 2017-07-09 14:18:03,311 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780M [Mobility Radeon HD 3200] 
[1002:9612] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3077]
  InstallationDate: Installed on 2017-03-06 (229 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4515s
  ProcEnviron:
   LANGUAGE=fi
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 nopat 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2017-07-09 (104 days ago)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPI Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3077
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 25.0C
  dmi.chassis.asset.tag: 

[Touch-packages] [Bug 1718931] Re: No VPN autoconnect

[J. Snow]

** Also affects: network-manager
   Importance: Undecided
   Status: New

** No longer affects: network-manager

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

Title:
  No VPN autoconnect

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   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.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1718931/+subscriptions

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

[PJSingh5000]

Same experience as in #2...

Just added Google account in Online Accounts in Control Center, and
Control Center crashed. Despite the crash, the Google account was added
successfully and seems to be working.

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[Bug Watch Updater]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1720519

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1725863] [NEW] Logitech G930 Fails in 17.10 (But not in 17.04)

[Luis Alvarado]

Public bug reported:

Every so many seconds / minutes the Wireless headset Logitech G930
simply drops connection. It always reconnects but when doing a
recording, a meeting, listening to music or a movie it simply drops the
connection for 1 to 3 second. This happens several times an hour. If it
helps, it was not happening in 17.04 (Never happened in more than 200+
hours of using the headset).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  cyrex  1288 F pulseaudio
 /dev/snd/controlC2:  cyrex  1288 F pulseaudio
 /dev/snd/controlC0:  cyrex  1288 F pulseaudio
Date: Sat Oct 21 17:55:42 2017
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO ALPHA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1725863

Title:
  Logitech G930 Fails in 17.10 (But not in 17.04)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Every so many seconds / minutes the Wireless headset Logitech G930
  simply drops connection. It always reconnects but when doing a
  recording, a meeting, listening to music or a movie it simply drops
  the connection for 1 to 3 second. This happens several times an hour.
  If it helps, it was not happening in 17.04 (Never happened in more
  than 200+ hours of using the headset).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cyrex  1288 F pulseaudio
   /dev/snd/controlC2:  cyrex  1288 F pulseaudio
   /dev/snd/controlC0:  cyrex  1288 F pulseaudio
  Date: Sat Oct 21 17:55:42 2017
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO ALPHA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

[Julian Andres Klode]

I package A suggests package B and you install B because C depends on
it, and now you remove C a year later, removing B might or might not be
a good idea. I think it's better to be on the safe side here and not
remove stuff the user might have come to rely on in autoremove.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  New

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default

[Julian Andres Klode]

Because let's face it: If A suggests B, B provides or modifies
functionality for A, so removing B might just break your use case of A.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  New

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725865] [NEW] Network shows Cable Unplugged

[Luis Alvarado]

Public bug reported:

This was working perfectly on 17.04, but after installing 17.10 from
scratch, the wired network is not detected. It simply shows as Cable
Unplugged when in fact there is the same cable still connected directly
to the router. This same computer has Windows 10 and it detects the
network correctly. I also tested Fedora and it detected the network
correctly (The wired one). I am currently using only the Wireless
connection because of this.

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: Sat Oct 21 17:59:31 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
IpRoute:
 default via 192.168.1.1 dev wlp9s0 proto static metric 600 
 169.254.0.0/16 dev wlp9s0 scope link metric 1000 
 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
 enp0s31f6  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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1725865

Title:
  Network shows Cable Unplugged

Status in network-manager package in Ubuntu:
  New

Bug description:
  This was working perfectly on 17.04, but after installing 17.10 from
  scratch, the wired network is not detected. It simply shows as Cable
  Unplugged when in fact there is the same cable still connected
  directly to the router. This same computer has Windows 10 and it
  detects the network correctly. I also tested Fedora and it detected
  the network correctly (The wired one). I am currently using only the
  Wireless connection because of this.

  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: Sat Oct 21 17:59:31 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-10-19 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp9s0 proto static metric 600 
   169.254.0.0/16 dev wlp9s0 scope link metric 1000 
   192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.2 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   wlp9s0 wifi  connected/org/freedesktop/NetworkManager/Devices/3  
Linux   ecb8e125-48ff-4994-94c8-bdf3731334ce  
/org/freedesktop/NetworkManager/ActiveConnection/13 
   enp0s31f6  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  

[Touch-packages] [Bug 1725861] [NEW] APT::AutoRemove::SuggestsImportant "false" should be the default

[Steve Langasek]

Public bug reported:

After an upgrade to 17.10, I took a look at how much cruft I had
accumulated on my system, and started marking various packages 'auto'
which I know I don't care about keeping installed.

apt autoremove didn't remove nearly as much stuff as I expected, and as
I dug down into some of them I found that a number of them were being
kept because other packages on the system have Suggests: referencing
them.

This is asymmetric and wrong.  If Suggested packages are not
automatically installed by default, then a Suggests should also not
prevent a package from being automatically removed.

After a web search led me to 'https://askubuntu.com/questions/351085
/how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my apt
config; apt autoremove now wants to remove 365MiB of packages from my
system.  That is a LOT of cruft that has accumulated over the years of
upgrades, none of which I have ever asked to be installed and all of
which were universe or no-longer-available packages.

** Affects: apt (Ubuntu)
 Importance: High
 Status: New


** Tags: rls-bb-incoming

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

** Tags added: rls-bb-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1725861

Title:
  APT::AutoRemove::SuggestsImportant "false" should be the default

Status in apt package in Ubuntu:
  New

Bug description:
  After an upgrade to 17.10, I took a look at how much cruft I had
  accumulated on my system, and started marking various packages 'auto'
  which I know I don't care about keeping installed.

  apt autoremove didn't remove nearly as much stuff as I expected, and
  as I dug down into some of them I found that a number of them were
  being kept because other packages on the system have Suggests:
  referencing them.

  This is asymmetric and wrong.  If Suggested packages are not
  automatically installed by default, then a Suggests should also not
  prevent a package from being automatically removed.

  After a web search led me to 'https://askubuntu.com/questions/351085
  /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
  packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
  apt config; apt autoremove now wants to remove 365MiB of packages from
  my system.  That is a LOT of cruft that has accumulated over the years
  of upgrades, none of which I have ever asked to be installed and all
  of which were universe or no-longer-available packages.

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

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

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Steve Langasek]

Preparando para desempaquetar .../013-resolvconf_1.79ubuntu4_all.deb ...
Desempaquetando resolvconf (1.79ubuntu4) sobre (1.79ubuntu1) ...

This shows an upgrade from 16.10 to 17.04, not an upgrade from 17.04 to
17.10.  Do you have a later log file available?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

[Julian Andres Klode]

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

@Jonathan Kamens (jik) The problem with msttcorefonts/accepted-
mscorefonts-eula is a different one, you could open a bug for
msttcorefonts for that. Silently not doing it seems to be the right
thing, though. If you want to install it non-interactive, you could
preseed the debconf value somehow.

** This bug has been marked a duplicate of bug 1651923
   apt https method decodes redirect locations and sends them to the 
destination undecoded.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1655431

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

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

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

[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

[Julian Andres Klode]

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

This problem has been fixed a while ago, seems we forgot to close it.
Obviously Sourceforge is having issues again, causing problems for
LinuxRussia (kobylyanets).

** Changed in: apt (Ubuntu)
 Assignee: LinuxRussia (kobylyanets) => (unassigned)

** Changed in: apt (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1655431

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

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

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

[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

[Julian Andres Klode]

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

Let's mark this as a duplicate again, so we actually have stuff correct
again.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1655431

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

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

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

[Touch-packages] [Bug 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

[Treviño]

** Project changed: gnome-control-center => gtk

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

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  /usr/bin/gnome-control-
  
center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render

Status in GTK+:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-control-center.  This problem was most recently seen with package version 
1:3.26.0-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a 
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/gtk/+bug/1720400/+subscriptions

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

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Artur Schmitt]

** Attachment added: "upgrade logs"
   
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+attachment/4983661/+files/20171019-2226.zip

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Touch-packages] [Bug 1655431] Re: apt-helper / update-notifier / ttf-mscorefonts-installer download failure (regression)

[LinuxRussia]

:~$ sudo apt install ttf-mscorefonts-installer --reinstall
Чтение списков пакетов… Готово
Построение дерева зависимостей   
Чтение информации о состоянии… Готово
Обновлено 0 пакетов, установлено 0 новых пакетов, переустановлено 1 пакетов, 
для удаления отмечено 0 пакетов, и 0 пакетов не обновлено.
Необходимо скачать 0 B/27,6 kB архивов.
После данной операции, объём занятого дискового пространства возрастёт на 0 B.
Предварительная настройка пакетов ...
(Чтение базы данных … на данный момент установлено 185726 файлов и каталогов.)
Подготовка к распаковке …/ttf-mscorefonts-installer_3.6ubuntu2_all.deb …
mscorefonts-eula license has already been accepted
Распаковывается ttf-mscorefonts-installer (3.6ubuntu2) на замену (3.6ubuntu2) …
Обрабатываются триггеры для update-notifier-common (3.186) …
ttf-mscorefonts-installer: processing...
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/andale32.exe
Ошк:1 http://downloads.sourceforge.net/corefonts/andale32.exe
  Redirection from https to 
'http://downloads.sourceforge.net/mirrorproblem?failedmirror=vorboss.dl.sourceforge.net'
 is forbidden
E: Не удалось получить https://vorboss.dl.sourceforge.net/project/corefonts/the 
fonts/final/andale32.exe  Redirection from https to 
'http://downloads.sourceforge.net/mirrorproblem?failedmirror=vorboss.dl.sourceforge.net'
 is forbidden
E: Ошибка при скачивании
Настраивается пакет ttf-mscorefonts-installer (3.6ubuntu2) …
Обрабатываются триггеры для fontconfig (2.11.94-0ubuntu2) …


** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => LinuxRussia (kobylyanets)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1655431

Title:
  apt-helper / update-notifier / ttf-mscorefonts-installer download
  failure (regression)

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  * OS release: Ubuntu 16.04.1 LTS
  * Package version: 3.168.3

  For the past few days (maybe even weeks for other users), update-
  notifier has been very repeatedly failing to handle the downloads for
  ttf-mscorefonts-installer. Previously it was working fine on the same
  system.

  This seems to affect a lot of desktop users, but the issue is usually
  misdiagnosed on forums because it is attributed to ttf-mscorefonts-
  installer and not to update-notifier-common.

  The issue is made particularly irritating because the update-notifier
  cron job tries and fails and notifies users daily of this failure.

  The issue can be reproduced by having ttf-mscorefonts-installer
  installed, and running:

  sudo dpkg-reconfigure update-notifier-common

  The error messages seem to be random but actually appear to be
  consistent for a given download source:

  * freefr.dl.sourceforge.net: 404  Not Found
  * kent.dl.sourceforge.net: Protocol "http" not supported or disabled in 
libcurl
  * netassist.dl.sourceforge.net: The HTTP server sent an invalid Content-Range 
header Bad header data [IP: 62.205.134.42 80]
  * netcologne.dl.sourceforge.net: The HTTP server sent an invalid 
Content-Range header
  * netix.dl.sourceforge.net: 404  Not Found
  * vorboss.dl.sourceforge.net: 404  Not Found

  In all above cases, the reported failing URL can be downloaded just
  fine using wget.

  Some other mirrors appear to work (unfortunately, mirror names are
  only printed in case of errors). However, since ttf-mscorefonts-
  installer triggers 11 downloads in a row, chances of randomly getting
  11 working mirrors are very low.

  I am tagging this as regression-update because the issue started
  happening when upgrading from 3.168.2 to 3.168.3 last Friday. It is of
  course entirely possible the root cause is in another package, but
  this would also likely be a regression-update, since I am very careful
  about system-wide changes on this machine.

  The previous update from 3.168.1 to 3.168.2 on November 4th went just
  fine. ttf-mscorefonts-installer has been installed (just fine) on
  September 26th, and not upgraded since then.

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

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

[Touch-packages] [Bug 1725847] [NEW] libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99

[Andrew Paxie]

Public bug reported:

Test program compiled on Artful Aardvark Ubuntu 17.10.

$ which g++-4.8
/usr/bin/g++-4.8

$ /usr/bin/g++-4.8 --version
g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ /usr/bin/g++-4.8 -std=c++11 -x c++ - <
#include 
int main()
{
  std::cout << std::to_string(0) << '\n';
  return 0;
}
EOF 

Expected result

compile without errors, output 0

Actual result

: In function ‘int main()’:
:5:16: error: ‘to_string’ is not a member of ‘std’

Supposed cause

_GLIBCXX_USE_C99 is not set in 
/usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h
in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6)

Further information

Test program compiles and runs on Zesty Zapus with package
libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4).

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1725847

Title:
  libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without
  _GLIBCXX_USE_C99

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  Test program compiled on Artful Aardvark Ubuntu 17.10.

  $ which g++-4.8
  /usr/bin/g++-4.8

  $ /usr/bin/g++-4.8 --version
  g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5
  Copyright (C) 2015 Free Software Foundation, Inc.
  This is free software; see the source for copying conditions.  There is NO
  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

  $ /usr/bin/g++-4.8 -std=c++11 -x c++ - <
  #include 
  int main()
  {
std::cout << std::to_string(0) << '\n';
return 0;
  }
  EOF 

  Expected result

  compile without errors, output 0

  Actual result

  : In function ‘int main()’:
  :5:16: error: ‘to_string’ is not a member of ‘std’

  Supposed cause

  _GLIBCXX_USE_C99 is not set in 
  /usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h
  in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6)

  Further information

  Test program compiles and runs on Zesty Zapus with package
  libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1725847/+subscriptions

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

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Steve Langasek]

Please attach your upgrade logs from /var/log/dist-upgrade to help us
try to see what has happened on your system.

Both before and after the upgrade, /etc/resolv.conf should be a symlink
to /run/resolvconf/resolv.conf.  If something has replaced that with a
file, we would need to figure out what that is.  It probably wasn't
resolvconf itself.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Bug Watch Updater]

** Changed in: gnubash
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1725333

Title:
  do-release-upgrade broke WSL

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful

[Dimitri John Ledkov]

When you boot livecd and connect with network-manager to your wifi, what
is the output of:

$ systemd-resolve --status

$ sudo NetworkManager --print-config

Does your wifi provide DNS nameservers?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725680

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  New

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

Re: [Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Dimitri John Ledkov]

On 21 October 2017 at 21:51, Steve Langasek
 wrote:
> On Sat, Oct 21, 2017 at 08:54:03AM -, diabloneo wrote:
>> No, I wasn't using resolvconf.
>
> Ok, is there any particular reason for that?  The resolvconf package is part
> of ubuntu-minimal in Ubuntu 17.04.  Removal of ubuntu-minimal leaves you
> with an unsupported configuration.

If you want to switch to the new default configuration you can do this:

$ sudo ln -fs ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

And reboot. both ifupdown and network-manager, in 17.10 feed
nameservers to resolved and this is what default configuration should
look like.

Otherwise you need to specify nameserver in either /etc/resolv.conf
direct, or by supplying them to network-manager and asking it to
manage the /etc/resolv.conf.

-- 
Regards,

Dimitri.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1725840] [NEW] resolvconf not correctly configured after update from 17.04 to 17.10

[Artur Schmitt]

Public bug reported:

After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
lookup on my wireless network connection did not work any more.

As it seems, the file /etc/resolv.conf was static and contained wrong
data assigned by the NetworkManager. When I changed the file content
manually to

  nameserver 127.0.0.53

DNS lookup worked fine. After reboot, however, I had to repeat this
operation since NetworkManager seems to have replaced the file content.

Finally, I found a solution. Running

sudo dpkg-reconfigure resolvconf

the file /etc/resolv.conf was replaced by the link

/etc/resolv.conf -> ../run/resolvconf/resolv.conf

Now, the wireless network seems to work properly.

Hence, there must be some kind of bug during the update process from
Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly.

Best regards,

Artur

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: resolvconf 1.79ubuntu8
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 23:17:38 2017
InstallationDate: Installed on 2013-10-18 (1463 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1725840

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  New

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

Re: [Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

On Sat, Oct 21, 2017 at 08:54:03AM -, diabloneo wrote:
> No, I wasn't using resolvconf.

Ok, is there any particular reason for that?  The resolvconf package is part
of ubuntu-minimal in Ubuntu 17.04.  Removal of ubuntu-minimal leaves you
with an unsupported configuration.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[Gastón Fournier]

** Changed in: xmxmind
 Assignee: (unassigned) => Gastón Fournier (gastonfournier)

** No longer affects: xmxmind

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  
  That installation is a default Ubuntu , no Mate installed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725784] Re: Gdebi doesn't show in "open with" menu in Nautilus

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1725784

Title:
  Gdebi doesn't show in "open with" menu in Nautilus

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When right-clicking on a .deb file in nautilus and choosing "Open With
  Other Application", Gdebi doesn't show up in the list. Same with right
  click/properties/open with.

  Using Ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdebi 0.9.5.7+nmu1ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:43:47 2017
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723641] Re: pulseaudio assert failure: pulseaudio: mixer.c :929 : snd_mixer_elem_get_callback_private: l'assertion « mixer » a échoué.

[Launchpad Bug Tracker]

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1723641

Title:
  pulseaudio assert failure: pulseaudio: mixer.c :929 :
  snd_mixer_elem_get_callback_private:  l'assertion « mixer » a échoué.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Happens at each start of the graphical (xorg apparently not wayland
  because of nvidia despite KMS at boot).

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c :929 : 
snd_mixer_elem_get_callback_private:  l'assertion « mixer » a échoué.
  CrashCounter: 1
  Date: Tue Oct 10 08:33:43 2017
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2017-06-18 (118 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7fefdaa1f188 "mixer", 
file=file@entry=0x7fefdaa1f419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7fefdaa1f6a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7fefdaa1f188 "mixer", file=0x7fefdaa1f419 
"mixer.c", line=929, function=0x7fefdaa1f6a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c :929 : 
snd_mixer_elem_get_callback_private:  l'assertion « mixer » a échoué.
  UpgradeStatus: Upgraded to artful on 2017-09-03 (41 days ago)
  UserGroups:
   
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0902
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0902:bd09/08/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1724933

Title:
  I can't adjust display brightness

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I
  can't adjust display brightness. when I press F2|F3 keys icon
  brightness appears, the controller moves but the brightness doesn't
  change.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 22:14:51 2017
  DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:3388]
   Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M 
XT] [1002:6740] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2017-06-18 (123 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3388
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124471610100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1724711] Re: rsyslog fails to start (Lubuntu 17.10)

[Dima]

Today rsyslog started fine. I don't know what the problem was.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1724711

Title:
  rsyslog fails to start (Lubuntu 17.10)

Status in rsyslog package in Ubuntu:
  New

Bug description:
  1) 
  Description:  Ubuntu 17.10
  Release:  17.10

  2) 8.16.0-1ubuntu9

  3) I'd like to see what happened in the system

  4) syslog is empty, messages is obsolete, lastlog shows only pure
  console logins (it maybe unrelated)

  root@user:~# systemctl status rsyslog
  ● rsyslog.service - System Logging Service
 Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2017-10-19 02:24:34 MSK; 1h 
15min ago
   Docs: man:rsyslogd(8)
 http://www.rsyslog.com/doc/
Process: 1858 ExecStart=/usr/sbin/rsyslogd -n (code=exited, 
status=1/FAILURE)
   Main PID: 1858 (code=exited, status=1/FAILURE)

  окт 19 02:24:33 user systemd[1]: rsyslog.service: Main process exited, 
code=exited, stat
  окт 19 02:24:33 user systemd[1]: Failed to start System Logging Service.
  окт 19 02:24:33 user systemd[1]: rsyslog.service: Unit entered failed state.
  окт 19 02:24:33 user systemd[1]: rsyslog.service: Failed with result 
'exit-code'.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Service hold-off time over, 
scheduling
  окт 19 02:24:34 user systemd[1]: Stopped System Logging Service.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Start request repeated too 
quickly.
  окт 19 02:24:34 user systemd[1]: Failed to start System Logging Service.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Unit entered failed state.
  окт 19 02:24:34 user systemd[1]: rsyslog.service: Failed with result 
'exit-code'.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Oct 19 03:59:04 2017
  InstallationDate: Installed on 2017-10-06 (12 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725789] Re: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1725789

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  System froze while re-installing evolution.  This report was generated
  after rebooting.  I don't know if it was the cause or if it was just
  interrupted in mid-process.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportLog: ERROR: apport (pid 5203) Fri Oct 20 23:49:52 2017: called for pid 
3444, signal 3, core limit 0
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  CrashReports:
   600:0:122:333413:2017-10-21 13:30:11.203864336 -0500:2017-10-21 
13:30:12.203864336 -0500:/var/crash/python3-apport.0.crash
   640:0:122:11677:2017-10-21 13:30:10.283984080 -0500:2017-10-21 
13:30:10.263985328 -0500:/var/crash/_usr_bin_py3compile.0.crash
  Date: Sat Oct 21 13:30:10 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725789] [NEW] package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Martin Mayer]

Public bug reported:

System froze while re-installing evolution.  This report was generated
after rebooting.  I don't know if it was the cause or if it was just
interrupted in mid-process.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: python3-apport 2.20.4-0ubuntu4.5
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportLog: ERROR: apport (pid 5203) Fri Oct 20 23:49:52 2017: called for pid 
3444, signal 3, core limit 0
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: i386
CrashReports:
 600:0:122:333413:2017-10-21 13:30:11.203864336 -0500:2017-10-21 
13:30:12.203864336 -0500:/var/crash/python3-apport.0.crash
 640:0:122:11677:2017-10-21 13:30:10.283984080 -0500:2017-10-21 
13:30:10.263985328 -0500:/var/crash/_usr_bin_py3compile.0.crash
Date: Sat Oct 21 13:30:10 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: apport
Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1725789

Title:
  package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  System froze while re-installing evolution.  This report was generated
  after rebooting.  I don't know if it was the cause or if it was just
  interrupted in mid-process.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: python3-apport 2.20.4-0ubuntu4.5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportLog: ERROR: apport (pid 5203) Fri Oct 20 23:49:52 2017: called for pid 
3444, signal 3, core limit 0
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: i386
  CrashReports:
   600:0:122:333413:2017-10-21 13:30:11.203864336 -0500:2017-10-21 
13:30:12.203864336 -0500:/var/crash/python3-apport.0.crash
   640:0:122:11677:2017-10-21 13:30:10.283984080 -0500:2017-10-21 
13:30:10.263985328 -0500:/var/crash/_usr_bin_py3compile.0.crash
  Date: Sat Oct 21 13:30:10 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: apport
  Title: package python3-apport 2.20.4-0ubuntu4.5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[burdandrei]

If i log out from "Ubuntu" and log in to "Ubuntu Gnome", parcellite
works

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in XMind:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  
  That installation is a default Ubuntu , no Mate installed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725785] [NEW] video card not recognized after install on my PC.-ubuntu 17.10

[hohassan444]

Public bug reported:

I have Intel G41 video card...which is recognized by all previous
versions of Ubuntu,,but not recognized by Ubuntu 17.10...though the live
CD version recognize it normally.it appear in system setting/about as
unknown...this leads to very slow and laggy system.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 21:17:26 2017
DistUpgraded: 2017-10-21 15:55:23,430 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated Graphics 
Controller [1458:d000]
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=70de525a-6d7f-41e7-b119-16941407f3bf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
dmi.bios.date: 11/04/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: G41M-ES2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G41M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
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

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


** Tags: amd64 apport-bug artful ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725785

Title:
  video card not recognized after install on my PC.-ubuntu 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Intel G41 video card...which is recognized by all previous
  versions of Ubuntu,,but not recognized by Ubuntu 17.10...though the
  live CD version recognize it normally.it appear in system
  setting/about as unknown...this leads to very slow and laggy system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 21:17:26 2017
  DistUpgraded: 2017-10-21 15:55:23,430 DEBUG icon theme changed, re-reading
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. G41M-ES2L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=70de525a-6d7f-41e7-b119-16941407f3bf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  dmi.bios.date: 11/04/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: G41M-ES2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd11/04/2009:svnGigabyteTechnologyCo.,Ltd.:pnG41M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-ES2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-ES2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: 

[Touch-packages] [Bug 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant

[burdandrei]

I received this trying to run parcellite on ubuntu 17.10.
Workaround with editing the file did not helped =(

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

Title:
  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

Status in XMind:
  Invalid
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Get that error now with each random package upgrade:

  /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error:
  invalid string constant "murrine-scrollbar", expected valid string
  constant

  Looks like related to that change:

  * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP:
  #961679)

   -- Marco Trevisan (Treviño)   Thu, 12 Oct 2017
  05:19:32 +

  
  That installation is a default Ubuntu , no Mate installed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: light-themes 16.10+17.10.20171012.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct 13 14:52:43 2017
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725784] [NEW] Gdebi doesn't show in "open with" menu in Nautilus

[Pavak Paul]

Public bug reported:

When right-clicking on a .deb file in nautilus and choosing "Open With
Other Application", Gdebi doesn't show up in the list. Same with right
click/properties/open with.

Using Ubuntu 17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdebi 0.9.5.7+nmu1ubuntu3
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
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 23:43:47 2017
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful nautilus

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1725784

Title:
  Gdebi doesn't show in "open with" menu in Nautilus

Status in gdebi package in Ubuntu:
  New

Bug description:
  When right-clicking on a .deb file in nautilus and choosing "Open With
  Other Application", Gdebi doesn't show up in the list. Same with right
  click/properties/open with.

  Using Ubuntu 17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdebi 0.9.5.7+nmu1ubuntu3
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:43:47 2017
  InstallationDate: Installed on 2017-10-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[Horst Schirmeier]

Update: After reinstalling pulseaudio, alsa-base, pulseaudio-module-
bluetooth and plasma-pa (for KDE's volume control applet), the problem
reappeared.  Commenting out "load-module module-switch-on-connect" in
/etc/pulse/default.pa (see comment #4) seems to fix the issue
permanently; the module still seems to be loaded due to some other means
of triggering the load (see output of: pactl list modules).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1720519

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Norbert]

I'm sorry. Seems to be my fault. 
I did installation of apt-file, synaptic, aptitude - may be they changed 
sources.list accidentally.

Did another clean installation on QEMU/KVM without any issue.

** No longer affects: ubuntu-mate

** Tags removed: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1697120

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Norbert]

I compared sources.list from normal Ubuntu 17.10 installation and from
MATE. They differ by 4 rows:

--- /etc/apt/sources.list
+++ /media/mate1710/724aac41-cc95-44d2-993b-32b544ab9022/etc/apt/sources.list
@@ -1,7 +1,4 @@
-# deb cdrom:[Ubuntu-MATE 17.10 _Artful Aardvark_ - Release i386 (20171018)]/ 
artful main multiverse restricted universe
-deb http://archive.ubuntu.com/ubuntu/ artful main restricted universe 
multiverse
-deb http://security.ubuntu.com/ubuntu/ artful-security main restricted 
universe multiverse
-deb http://archive.ubuntu.com/ubuntu/ artful-updates main restricted universe 
multiverse
+#deb cdrom:[Ubuntu 17.10 _Artful Aardvark_ - Release amd64 (20171018)]/ artful 
main restricted
 
 # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
 # newer versions of the distribution.


So it seems to be MATE community fault.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1697120

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in ubuntu-mate:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1697120/+subscriptions

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Norbert]

@Julian Andres Klode (juliank)

It was clean fresh installation from official fresh ISO. 
Here is sources.list. I did not touch it.

mate1710@mate1710:~$ cat /etc/apt/sources.list
# deb cdrom:[Ubuntu-MATE 17.10 _Artful Aardvark_ - Release i386 (20171018)]/ 
artful main multiverse restricted universe
deb http://archive.ubuntu.com/ubuntu/ artful main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ artful-security main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu/ artful-updates main restricted universe 
multiverse

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ru.archive.ubuntu.com/ubuntu/ artful main restricted
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ru.archive.ubuntu.com/ubuntu/ artful universe
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful universe
deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful multiverse
deb http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse
# deb-src http://ru.archive.ubuntu.com/ubuntu/ artful-backports main restricted 
universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu artful partner
# deb-src http://archive.canonical.com/ubuntu artful partner

deb http://security.ubuntu.com/ubuntu artful-security main restricted
# deb-src http://security.ubuntu.com/ubuntu artful-security main restricted
deb http://security.ubuntu.com/ubuntu artful-security universe
# deb-src http://security.ubuntu.com/ubuntu artful-security universe
deb http://security.ubuntu.com/ubuntu artful-security multiverse
# deb-src http://security.ubuntu.com/ubuntu artful-security multiverse


It's not my fault. Should we inform Ubuntu MATE developers?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1697120

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in ubuntu-mate:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, 

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Артем Лещев]

** Bug watch added: github.com/Microsoft/BashOnWindows/issues #1878
   https://github.com/Microsoft/BashOnWindows/issues/1878

** Also affects: gnubash via
   https://github.com/Microsoft/BashOnWindows/issues/1878
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1725333

Title:
  do-release-upgrade broke WSL

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Julian Andres Klode]

Norbert: That's not an issue, that's a correct warning. You must have
duplicate sources.list entries for the same URL, component, and
architecture. Don't have duplicates in there.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1697120

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in ubuntu-mate:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1697120/+subscriptions

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Norbert]

Bug exists in Ubuntu 17.10 MATE:

mate1710@mate1710:~$ sudo apt-get install apt-file 
[sudo] password for mate1710: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  libregexp-assemble-perl
The following NEW packages will be installed:
  apt-file libregexp-assemble-perl
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 103 kB of archives.
After this operation, 288 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://archive.ubuntu.com/ubuntu artful/universe i386 
libregexp-assemble-perl all 0.36-1 [77,5 kB]

mate1710@mate1710:~$ sudo aptitude update
Hit http://ru.archive.ubuntu.com/ubuntu artful InRelease
Hit http://ru.archive.ubuntu.com/ubuntu artful-updates InRelease
   
Hit http://ru.archive.ubuntu.com/ubuntu artful-backports InRelease  
 
Hit http://security.ubuntu.com/ubuntu artful-security InRelease 
   
Hit http://archive.ubuntu.com/ubuntu artful InRelease
Get: 1 http://archive.ubuntu.com/ubuntu artful-updates InRelease [65,4 kB]
Fetched 65,4 kB in 0s (71,9 kB/s)   
W: Target Packages (main/binary-i386/Packages) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Packages (main/binary-all/Packages) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Translations (main/i18n/Translation-en_US) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Translations (main/i18n/Translation-en) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Contents-deb (main/Contents-i386) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Contents-deb (main/Contents-all) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Packages (restricted/binary-i386/Packages) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Packages (restricted/binary-all/Packages) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Translations (restricted/i18n/Translation-en_US) is configured 
multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Translations (restricted/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Contents-deb (restricted/Contents-i386) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Contents-deb (restricted/Contents-all) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Packages (universe/binary-i386/Packages) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Packages (universe/binary-all/Packages) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Translations (universe/i18n/Translation-en_US) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Translations (universe/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Contents-deb (universe/Contents-i386) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Contents-deb (universe/Contents-all) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:51
W: Target Packages (multiverse/binary-i386/Packages) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Packages (multiverse/binary-all/Packages) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Translations (multiverse/i18n/Translation-en_US) is configured 
multiple times in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Translations (multiverse/i18n/Translation-en) is configured multiple 
times in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Contents-deb (multiverse/Contents-i386) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Contents-deb (multiverse/Contents-all) is configured multiple times 
in /etc/apt/sources.list:3 and /etc/apt/sources.list:53
W: Target Packages (main/binary-i386/Packages) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Packages (main/binary-all/Packages) is configured multiple times in 
/etc/apt/sources.list:3 and /etc/apt/sources.list:49
W: Target Translations (main/i18n/Translation-en_US) is configured multiple 
times in /etc/apt/sources.list:3 and 

[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.

[Horst Schirmeier]

I'm seeing this as well on a machine with a clean 17.04 installation
that was upgraded to 17.10, using KDE (sound: Intel HDA).  Steps in
comment #2 fixed this problem, at least temporarily.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1720519

Title:
  KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
  at most. Refusing to load.

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio daemon does not start after the update to Kubuntu 17.10
  beta2, because the module fails to load although it is there.

  From 'pulseaudio -vv'

  E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded 
once at most. Refusing to load.
  E: [pulseaudio] main.c: Module load failed.
  E: [pulseaudio] main.c: Failed to initialize daemon.

  PS sorry I am not a seasoned bug reporter. Let me know if I can
  provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   ben2809 F...m chrome
   /dev/snd/controlC0:  ben2809 F chrome
   /dev/snd/timer:  ben2809 f chrome
  CurrentDesktop: KDE
  Date: Sat Sep 30 11:20:55 2017
  InstallationDate: Installed on 2017-04-07 (175 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: B150M-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[Hicks]

A stop job is running for ifup for wlp2s0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1457400

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

Status in lvm2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

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

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

[Touch-packages] [Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

[Hicks]

...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1457400

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

Status in lvm2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I use Ubuntu 15.04 with Unity, I have a SSD drive also. Very recently
  onwards the ubuntu is taking long to shut down nearly 1:30 minutes.

  I checked the shutdown log messages and I get the follow message.

  A stop job is running for Session c2 of user * (25s/ 1min 30 s)

  It count downs till 1:30 minutes and then shutdown the machine.

  Why is it happening.

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

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

[Touch-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

[Domar]

I can confirm this problem for a fresh installation of Ubuntu 17.10

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1663528

Title:
  pulseaudio assert failure: pulseaudio: mixer.c:929:
  snd_mixer_elem_get_callback_private: Assertion `mixer' failed.

Status in pulseaudio package in Ubuntu:
  Confirmed

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

  ---

  Sidenote: Imediatly got that crash after the apt-xapian-index one (
  lp:1663524 ); does not know if it can exist a possible relationship
  between them.

  Got an other crash, and that time 'sound' is fully lost (pulseaudio
  not reloaded). Wonder if lp:1662860 can be concerned.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: pulseaudio 1:10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
  Uname: Linux 4.9.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AssertionMessage: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem4084 F pulseaudio
   /dev/snd/controlC0:  oem4084 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Feb 10 09:55:45 2017
  ExecutablePath: /usr/bin/pulseaudio
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   __assert_fail_base (fmt=, 
assertion=assertion@entry=0x7f92818e7188 "mixer", 
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929, 
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private") 
at assert.c:92
   __GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419 
"mixer.c", line=929, function=0x7f92818e76a0 
"snd_mixer_elem_get_callback_private") at assert.c:101
   snd_mixer_elem_get_callback_private () from 
/usr/lib/x86_64-linux-gnu/libasound.so.2
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
   ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
  Title: pulseaudio assert failure: pulseaudio: mixer.c:929: 
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev 
sambashare sudo users
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

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

Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Len Ovens]

On Sat, 21 Oct 2017, Norbert wrote:
> At least `gparted` and `synaptic` do not run on default fresh clean
> installation of Ubuntu 17.10.
And as standard software installer does not:
a) pass on querries from the package install (so that jackd can be 
properly installed for example)
b) does not alert the user that a package they are installing has to 
remove another package the user still needs. This can leave the user with 
a crippled system.

I have personally helped a number of people fix botched installs. I have 
never had complaints after the user installs synaptic.

synaptic, though old and worn, is the only GUI installer that is safe to 
use in my experience. It is also fast and provides package information 
that allows trouble shooting package problems.

These extras may be confusing for a new computer user or someone coming 
from windows, but points a and b above need to be addressed if new users 
are to keep using Ubuntu longer than a quick try.

--
Len Ovens
www.ovenwerks.net

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In 

[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1718717

Title:
  cupsd crashed with SIGSEGV in avahi_entry_group_free()

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Confirmed

Bug description:
  after updates of cups-filter and reboot

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: cups-daemon 2.2.4-7
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  Date: Thu Sep 21 17:43:42 2017
  ExecutablePath: /usr/sbin/cupsd
  Lpstat:
   device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21
   device for PDF: cups-pdf:/
  MachineType: Dell Inc. OptiPlex 960
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer (w/ options)
   HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended)
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f32dc0c7954 : cmpq   
$0x0,(%rdi)
   PC (0x7f32dc0c7954) ok
   source "$0x0" ok
   destination "(%rdi)" (0x) not located in a known VMA region (needed 
writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: cups
  StacktraceTop:
   avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: cupsd crashed with SIGSEGV in avahi_entry_group_free()
  UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago)
  UserGroups:
   
  dmi.bios.date: 08/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 0Y958C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1725729] Re: Trying to add a google account with the kubuntu online account manager

[bt]

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

hi,
I can't find bug #1723230.
Is there an error in the number ?
otherwise, how can I view and follow it ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1725729

Title:
  Trying to add a google account  with the kubuntu online account
  manager

Status in signon-ui package in Ubuntu:
  New

Bug description:
  no account configured
  fresh kubuntu 17.10 install or live usb.
  Also seen on kubuntu 17.04
  when trying to use the instant messenger embedded with kubuntu, icon on 
bottom right of the screen, I first need to add an existing google account.
  In the "online accounts" tab, I click on "create", then select "google".
  after a few seconds I get the following error:
  Il y a une eu une erreur durant le traitement de la requête : 
userActionFinished error: 2
  -> there has been an error while processing the request : userActionFinished 
error: 2

  Adding an existing jabber account works fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Oct 21 17:10:15 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2017-09-23 (28 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   LANGUAGE=fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f50af6585a0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7f50af6585a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725729/+subscriptions

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

[Touch-packages] [Bug 1725729] Re: Trying to add a google account with the kubuntu online account manager

[Apport retracing service]

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

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 #1723230, 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/1725729/+attachment/4982528/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1725729

Title:
  Trying to add a google account  with the kubuntu online account
  manager

Status in signon-ui package in Ubuntu:
  New

Bug description:
  no account configured
  fresh kubuntu 17.10 install or live usb.
  Also seen on kubuntu 17.04
  when trying to use the instant messenger embedded with kubuntu, icon on 
bottom right of the screen, I first need to add an existing google account.
  In the "online accounts" tab, I click on "create", then select "google".
  after a few seconds I get the following error:
  Il y a une eu une erreur durant le traitement de la requête : 
userActionFinished error: 2
  -> there has been an error while processing the request : userActionFinished 
error: 2

  Adding an existing jabber account works fine.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: signon-ui-x11 0.17+17.10.20170606-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Oct 21 17:10:15 2017
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2017-09-23 (28 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/signon-ui
  ProcEnviron:
   LANGUAGE=fr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f50af6585a0 
<_ZN7QWindow11setModalityEN2Qt14WindowModalityE>:   mov0x8(%rdi),%rax
   PC (0x7f50af6585a0) ok
   source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   QWindow::setModality(Qt::WindowModality) () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? ()
   ?? ()
   ?? ()
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  Title: signon-ui crashed with SIGSEGV in QWindow::setModality()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XsessionErrors:
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",
   (kerneloops-applet:1609): Gtk-WARNING **: Unable to locate theme engine in 
module_path: "adwaita",

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1725729/+subscriptions

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

[Touch-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts

[Rik Mills]

Rebuilding the version for Xenial, 0.17+16.04.20151125-0ubuntu1, for
artful 17.10 seems to produce a working signon via KDE's systemsetting

See test rebuild in: https://launchpad.net/~rikmills/+archive/ubuntu
/kio-grive

Rebuilding any later ubuntu published versions fails to produce a
working version.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1070873

Title:
  kde-telepathy, impossible to connect to gmail accounts

Status in meta-kde-telepathy package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Im running ubuntu 12.10 quantal and i have installed kde, when running
  kde-telepathy i have added a gmail account, and after entering the
  password it has revealed impossible to connect to it, it always says
  that the password is wrong when that is false.

  When using empathy, i have removed the gmail account and have added it
  again, now appears a XMLL window asking ubuntu permission to conenct
  to it, and now i was able to conenct to the gmail account.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Dave]

I had similar problem with cursor jumping randomly on my Dell E5570 with Ubuntu 
16.04, but the solution posted her by Juan Hernandez did not help. 
I found out that my Track Stick (stored in the middle of my keyboard) is source 
of the problem. When I disabled it the problem just disappeared. 
I guess the problem is with the driver for the track stick as it worked just OK 
on Windows.

The following link was very helpful:
https://cederlys.wordpress.com/2010/07/13/disabling-the-track-stick-in-ubuntu/#comment-694

I used the following to list the input devices:
xinput list

and to disable the track stick:
xinput -set-prop "AlpsPS/2 ALPS DualPoint Stick" "Device Enabled" 0 

Hovewer after reboot the trackpad is back on, so I added the above
command to "Startup Applicationns"

Regards

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574667

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session

[Norbert]

At least `gparted` and `synaptic` do not run on default fresh clean
installation of Ubuntu 17.10.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1713313

Title:
  Unable to launch pkexec'ed applications on Wayland session

Status in apport package in Ubuntu:
  New
Status in apt-offline package in Ubuntu:
  New
Status in backintime package in Ubuntu:
  Confirmed
Status in budgie-welcome package in Ubuntu:
  Invalid
Status in caja-admin package in Ubuntu:
  New
Status in cinnamon package in Ubuntu:
  Invalid
Status in ettercap package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed
Status in gnunet-gtk package in Ubuntu:
  Confirmed
Status in gparted package in Ubuntu:
  Invalid
Status in gui-ufw package in Ubuntu:
  Confirmed
Status in guidedog package in Ubuntu:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in italc package in Ubuntu:
  New
Status in laptop-mode-tools package in Ubuntu:
  New
Status in lightdm-gtk-greeter-settings package in Ubuntu:
  Confirmed
Status in nautilus-admin package in Ubuntu:
  New
Status in needrestart-session package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed
Status in policykit-1 package in Ubuntu:
  Invalid
Status in scanmem package in Ubuntu:
  New
Status in scap-workbench package in Ubuntu:
  Confirmed
Status in sirikali package in Ubuntu:
  New
Status in synaptic package in Ubuntu:
  Confirmed
Status in thunar package in Ubuntu:
  New
Status in tuned package in Ubuntu:
  New
Status in ubuntustudio-controls package in Ubuntu:
  New
Status in ubuntustudio-default-settings package in Ubuntu:
  Invalid
Status in update-notifier package in Ubuntu:
  New
Status in xdiagnose package in Ubuntu:
  Confirmed
Status in xubuntu-default-settings package in Ubuntu:
  Invalid
Status in zulucrypt package in Ubuntu:
  Fix Released

Bug description:
  Posting here what gnome says about porting to wayland, and their
  tests:

  GNOME Applications under Wayland
  GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a 
GTK+ application under Wayland simply by:

  GDK_BACKEND=wayland gnome-calculator
  Applications that use Clutter or clutter-gtk also need the Clutter Wayland 
backend enabled:

  GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese

  https://wiki.gnome.org/Initiatives/Wayland/Applications

  ==> so hope the settings are well set at compile time; maybe a
  rebuilt to get sure all apps are ok.

  
  


  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Install backintime-qt4 or gparted application from above list (full may be 
acquired from 
https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4
 )
  3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located 
in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec
  ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec
  Exec=pkexec backintime-qt4)
  3b. Try to launch Gparted from shortcut "GParted" (located in 
/usr/share/applications/gparted.desktop, it uses gparted-pkexec)
  4a.1. Back In Time does not start from GUI.
  4a.2. Back In Time shows error message in console:
  4b. gparted-pkexec does not start, reports error
  $ gparted-pkexec
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-121.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-121.mount.
  Removed /run/systemd/system/tmp.mount.

  $ pkexec backintime-qt4

  Back In Time
  Version: 1.1.12

  Back In Time comes with ABSOLUTELY NO WARRANTY.
  This is free software, and you are welcome to redistribute it
  under certain conditions; type `backintime --license' for details.

  No protocol specified
  app.py: cannot connect to X server :0

  Expected results:
  * backintime-qt4 may be run as root

  Actual results:
  * unable to run backintime-qt4 as root

  Workaround:
  * setting "xhost +si:localuser:root" helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: backintime-qt4 1.1.12-2
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic i686
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Aug 27 14:23:14 2017
  InstallationDate: Installed on 2017-08-26 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  PackageArchitecture: all

[Touch-packages] [Bug 1725693] Re: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()

[Apport retracing service]

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

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 #1664886, 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/1725693/+attachment/4982179/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725693

Title:
  systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()

Status in systemd package in Ubuntu:
  New

Bug description:
  I upgraded to Ubuntu 17.10 from 17.04 using do-release-upgrade and
  logged in GUI session.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  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: Sat Oct 21 15:19:59 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  InstallationDate: Installed on 2014-04-19 (1280 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcCmdline: /lib/systemd/systemd-resolved
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=1ded6525-edff-4835-94fe-a4060f63847e ro persistent quiet splash 
vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f186b636baa:movzbl 0x2f(%rdi),%r8d
   PC (0x7f186b636baa) ok
   source "0x2f(%rdi)" (0x1e2700750134) not located in a known VMA region 
(needed readable region)!
   destination "%r8d" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? () from /lib/systemd/libsystemd-shared-234.so
   internal_hashmap_iterate () from /lib/systemd/libsystemd-shared-234.so
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 01/06/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FH
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFH:bd01/06/2012:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list

[Norbert]

** Tags removed: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1697120

Title:
  artful's apt-file and aptitude complains about Ubuntu sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  apt-file is now difficult to use with about a dozen warnings like this:

  W: Target Contents-deb-legacy (Contents-amd64) is configured multiple
  times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17

  For reference, this is line 6:
  deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted

  And this is line 17:
  deb http://us.archive.ubuntu.com/ubuntu/ artful universe

  This is how Ubuntu's default sources.list has been structured since
  the beginning? (or at least more than a decade).

  What I expect
  -
  The warning isn't specific enough. Lines 6 and 17 are not actually 
duplicates. The warning could be removed or fixed so that it doesn't complain 
about non-duplicates.

  Or the warning could be disabled on Ubuntu.

  See also
  
  LP: #1579372

  [Test case]
  Install apt-file and update, make sure that the warnings are gone.

  [Regression potential]
  Warnings about duplicate index targets containing "legacy" in their 
configured name are not shown anymore, thus it's harder to "fix" servers. But 
apart from that, which was the goal, I don't see any.

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

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

[Touch-packages] [Bug 1712902] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1712902

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I do not know what happened

  Regards,
  --
  Cristian

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Aug 24 15:59:30 2017
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2017-07-05 (49 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim --address 
unix:tmpdir=/tmp/ibus
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-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
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to artful on 2017-07-05 (49 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1242572] Re: xkeyboard-config, console-setup, and ubiquity should use Super+Space for switching keyboard layouts

[Norbert]

Got this bug on installation of fresh Ubuntu 17.10. I selected Russian
keyboard layout on installation. After installation I got both
 and convenient  keyboard layout switchers.

Here is my  /etc/default/keyboard :
# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="us,ru"
XKBVARIANT=","
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"

BACKSPACE="guess"

I like  keyboard layout switcher, it is great.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1242572

Title:
  xkeyboard-config, console-setup, and ubiquity should use Super+Space
  for switching keyboard layouts

Status in xkeyboard-config:
  Fix Released
Status in console-setup package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in console-setup source package in Trusty:
  Confirmed
Status in ubiquity source package in Trusty:
  Confirmed
Status in xkeyboard-config source package in Trusty:
  In Progress

Bug description:
  Super+Space is default combination for switching keyboard layouts in
  gnome3, unity, Mac OS X, Windows. Thus for consistently, Xorg;
  console-setup; and ubiquity should also use Super+Space combination
  for switching keyboard layouts.

  reading xkeyboard-config sources and documentations i don't see that
  xkeyboard-config can support grp:lwin_space and i guess that needs to
  be the first step to properly support super+space.

  
  Original bug report below:

  
  Recently I installed Ubuntu 13.10 and Ubuntu GNOME 13.10.
  I use two keyboard layouts - English and Russian.
  So I select them on the corresponding screen of ubiquity setup wizard.

  It quietly set the keyboard switching shortcut to Alt+Shift and wrote this 
setting to /etc/default/keyboard:
  # ...
  XKBMODEL="pc105"
  XKBLAYOUT="us,ru"
  XKBVARIANT=","
  XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
  # ...

  On first boot of installed system the small notification pop-up showed
  that Ibus will use Super+Space for layout switching.

  Please fix this configuration inconsistency.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  Date: Mon Oct 21 12:16:58 2013
  InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper 
only-ubiquity initrd=/casper/initrd.lz quiet splash --
  InstallationDate: Installed on 2013-10-21 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  MarkForUpload: True
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1242572/+subscriptions

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

[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful

[Jan Rathmann]

I just tested that disabling systemd-resolved seems to be a good
permanent workaround for me (according to the description under
https://askubuntu.com/questions/907246/how-to-disable-systemd-resolved-
in-ubuntu )

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725680

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  New

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
  some other known DNS server.

  On Ubuntu 17.04 this bug is not present.

  The original address in /run/systemd/resolve/stub-resolve.conf is
  127.0.0.53 . I get immediate replies if I ping this address, but
  nevertheless DNS resolution doesn't work.

  It seems that the service systemd-networkd isn't active by default:
  $ sudo systemctl status systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; 
vendo
 Active: inactive (dead)
   Docs: man:systemd-networkd.service(8)

  Manually starting it doesn't seem to help for this bug.

  systemd-resolved is active:

  $ sudo systemctl status systemd-resolved
  ● systemd-resolved.service - Network Name Resolution
 Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor
 Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
   Docs: man:systemd-resolved.service(8)
 https://www.freedesktop.org/wiki/Software/systemd/resolved
 
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
 
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
   Main PID: 1095 (systemd-resolve)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/systemd-resolved.service
 └─1095 /lib/systemd/systemd-resolved

  Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 
49aac11d7b6f644
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 
e06d44b80b8f1d3
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 
10.in-add
  Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
  Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Sat Oct 21 12:26:00 2017
  ExecutablePath: /lib/systemd/systemd-resolved
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Acer Extensa 5635Z
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2009
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V0.3305
  dmi.board.name: BA50-MV
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Extensa 5635Z
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1239475] Re: python-apport is missing python-launchpadlib

[Norbert]

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

** This bug has been marked a duplicate of bug 1171781
   python-apport is not installed properly

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1239475

Title:
  python-apport is missing python-launchpadlib

Status in apport package in Ubuntu:
  New

Bug description:
  $ apport-collect 1239472
  > You need to run 'sudo apt-get install python-apport' for apport-collect to 
work.

  So far so good. So:
  $ sudo apt-get install python-apport
  (...)
  $ apport-collect 1239472
  > ERROR: The launchpadlib Python module is not installed. This functionality 
is not available.

  If that is needed, it should have been installed. That's what apt is
  all about, right?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: python-apport 2.9.2-0ubuntu8.3
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CrashReports:
   644:0:110:0:2013-10-13 23:19:53.522817890 +0200:2013-10-13 
23:19:53.522817890 +0200:/var/crash/_usr_lib_udisks2_udisksd.0.upload
   640:0:110:1367462:2013-10-14 00:44:45.795705318 +0200:2013-10-14 
00:44:46.795705318 +0200:/var/crash/_usr_lib_udisks2_udisksd.0.crash
   664:1000:110:0:2013-10-13 21:44:53.301354033 +0200:2013-10-13 
21:44:53.301354033 +0200:/var/crash/_usr_bin_compiz.1000.upload
   600:106:110:0:2013-10-13 21:44:55.856075967 +0200:2013-10-13 
21:44:55.856075967 +0200:/var/crash/_usr_bin_compiz.1000.uploaded
   640:1000:110:4540839:2013-10-13 21:44:49.854578018 +0200:2013-10-13 
21:44:54.324841999 +0200:/var/crash/_usr_bin_compiz.1000.crash
  Date: Mon Oct 14 01:59:11 2013
  InstallationDate: Installed on 2013-10-11 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1238408] Re: apport seems to be missing a dependency

[Norbert]

** Description changed:

- I'm using Ubuntu 13.10 dev with apport 2.12.5-0ubuntu1 and after
- installing apport with "sudo apt-get install apport" and executng it as
- "apport-collect 1185521" I'm getting the following message: "You need to
- run 'sudo apt-get install python-apport' for apport-collect to work.".
- Im now thinking about if python-apport should be a dependency of apport
- or not. apport-bug seems to be working without it but apport-collect is
- always provided with apport. This is a reason for and a reason against
- such a decision.
+ Steps to reproduce:
+ 1. Install Ubuntu 17.10
+ 2. Try to launch `apport-collect 1712200`
+ 
+ Expected results:
+ apport-collect works out-the-box and collected corresponding info
+ 
+ Actual results:
+ apport-collect does not work and shows message:
+ 
+ "You need to run 'sudo apt-get install python-apport' for apport-collect
+ to work."
+ 
+ Note: manual installation of python-apport adds 15 MB of new packages,
+ after that apport-collect works as expected.

** Summary changed:

- apport seems to be missing a dependency
+ apport-collect is not functional until manual installation of python-apport

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1238408

Title:
  apport-collect is not functional until manual installation of python-
  apport

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to launch `apport-collect 1712200`

  Expected results:
  apport-collect works out-the-box and collected corresponding info

  Actual results:
  apport-collect does not work and shows message:

  "You need to run 'sudo apt-get install python-apport' for apport-
  collect to work."

  Note: manual installation of python-apport adds 15 MB of new packages,
  after that apport-collect works as expected.

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

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

[Touch-packages] [Bug 1246275] Re: python-apport needed by apport-collect to work, while python3-apport should do the job.

[Norbert]

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

** This bug has been marked a duplicate of bug 1150335
   apport collect says "install python-apport", but package deps install 
"python3-apport"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1246275

Title:
  python-apport needed by apport-collect to work, while python3-apport
  should do the job.

Status in apport package in Ubuntu:
  New

Bug description:
  Fresh default Trusty i386 installation

  When apport-collect is used, python3-apport which is the default
  installed package, fail to run apport-collect

  ***You need to run 'sudo apt-get install python-apport' for apport-collect to 
work. 
  --- 
  ApportLog:
   
  ApportVersion: 2.12.6-0ubuntu1
  Architecture: i386
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-25 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
  MarkForUpload: True
  Package: apport 2.12.6-0ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.12.0-1.3-generic 3.12.0-rc7
  Tags:  trusty
  Uname: Linux 3.12.0-1-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Touch-packages] [Bug 1171781] Re: python-apport is not installed properly

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1171781

Title:
  python-apport is not installed properly

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  python-apport is not installed properly (with apt-get). I was told (by
  Bryce Harrington) that

  python-launchpadlib

  should be installed too, and I could install that library package
  manually. And then

  apport-collect

  works. But it should be identified and pulled in as a dependency, at
  least if you want newbies like me to help reporting bugs ;-)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: python-apport 2.9.2-0ubuntu8
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  CasperVersion: 1.330
  Date: Tue Apr 23 09:25:18 2013
  LiveMediaBuild: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1725685] [NEW] Systemd long reboot on OpenVZ

[roma1390]

Public bug reported:

Ubuntu 17.04
systemd: 232-21ubuntu2

short: Systemd on reboot waits extra 90sec for no reason

Other references:
  
https://forum.openvz.org/index.php?t=tree=52177=0012de5a5151a907e13af2b5267cf59d

Env: 
  OpenVZ 2.6.32-openvz-042stab120.19-amd64
  Ubuntu 17.04
  
Packages:
  # dpkg -l | grep systemd
  ii  libsystemd0:amd64232-21ubuntu2 amd64  
  systemd utility library
  ii  systemd  232-21ubuntu2 amd64  
  system and service manager
  ii  systemd-sysv 232-21ubuntu2 amd64  
  system and service manager - SysV links


console log during "problem"
=
Sending SIGTERM to remaining processes...^M
Sending SIGKILL to remaining processes...^M
Sending SIGKILL to PID 338 (systemd-cgroups).^M
Sending SIGKILL to PID 339 (systemd-cgroups).^M
system-shutdown succeeded.^M
Rebooting.^M
=

The "extra" wait is occurring before line:
  system-shutdown succeeded

Problem analysis, steps:
1. PID 1 does exec to /lib/systemd/systemd-shutdown
2. src/core/shutdown.c:main calls broadcast_signal(SIGKILL, true, false);
3. somehow /lib/systemd/systemd-cgroups-agent is started by 
/sys/fs/cgroup/systemd/release_agent
4. src/core/killall.c:broadcast_signal calls killall(sig, pids, send_sighup);
writes message: Sending SIGKILL to PID 338 (systemd-cgroups).
adds pid 338 to pids sed

5. broadcast_signal calls wait_for_children(pids, );
6. in paralel process systemd-cgroups finishes
7. we still in wait_for_children and stuck here for 90 sec

Tried workaround approaches:
1. mount /dev/null -o bind /lib/systemd/systemd-cgroups-agent
will not work, before shutdown mounts are umounted, so we lose that one
2. change /sys/fs/cgroup/systemd/release_agent to /bin/false
still caches running false process and waits 90 sec for finish of it
3. write 0 to /sys/fs/cgroup/systemd/notify_on_release from script in 
/lib/systemd/system-shutdown
this is to late, those scripts runs after long delay

Simple proposed workaround:

disable notify before systemd-shutdown by using wrapper script

  dpkg-divert --add /lib/systemd/systemd-shutdown
  mv /lib/systemd/systemd-shutdown /lib/systemd/systemd-shutdown.distrib
  cat > /lib/systemd/systemd-shutdown < /sys/fs/cgroup/systemd/notify_on_release 
  exec /lib/systemd/systemd-shutdown.distrib "$@"
  EOF
  chmod +x /lib/systemd/systemd-shutdown

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725685

Title:
  Systemd long reboot on OpenVZ

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 17.04
  systemd: 232-21ubuntu2

  short: Systemd on reboot waits extra 90sec for no reason

  Other references:

https://forum.openvz.org/index.php?t=tree=52177=0012de5a5151a907e13af2b5267cf59d

  Env: 
OpenVZ 2.6.32-openvz-042stab120.19-amd64
Ubuntu 17.04

  Packages:
# dpkg -l | grep systemd
ii  libsystemd0:amd64232-21ubuntu2 
amd64systemd utility library
ii  systemd  232-21ubuntu2 
amd64system and service manager
ii  systemd-sysv 232-21ubuntu2 
amd64system and service manager - SysV links

  
  console log during "problem"
  =
  Sending SIGTERM to remaining processes...^M
  Sending SIGKILL to remaining processes...^M
  Sending SIGKILL to PID 338 (systemd-cgroups).^M
  Sending SIGKILL to PID 339 (systemd-cgroups).^M
  system-shutdown succeeded.^M
  Rebooting.^M
  =

  The "extra" wait is occurring before line:
system-shutdown succeeded

  Problem analysis, steps:
  1. PID 1 does exec to /lib/systemd/systemd-shutdown
  2. src/core/shutdown.c:main calls broadcast_signal(SIGKILL, true, false);
  3. somehow /lib/systemd/systemd-cgroups-agent is started by 
/sys/fs/cgroup/systemd/release_agent
  4. src/core/killall.c:broadcast_signal calls killall(sig, pids, send_sighup);
  writes message: Sending SIGKILL to PID 338 (systemd-cgroups).
  adds pid 338 to pids sed

  5. broadcast_signal calls wait_for_children(pids, );
  6. in paralel process systemd-cgroups finishes
  7. we still in wait_for_children and stuck here for 90 sec

  Tried workaround approaches:
  1. mount /dev/null -o bind /lib/systemd/systemd-cgroups-agent
  will not work, before shutdown mounts are umounted, so we lose that one
  2. change /sys/fs/cgroup/systemd/release_agent to /bin/false
  still caches running false process and waits 90 sec for finish of it
  3. write 0 to /sys/fs/cgroup/systemd/notify_on_release from script in 
/lib/systemd/system-shutdown
  this is to late, those scripts runs after long delay

  Simple proposed workaround:

  disable notify 

[Touch-packages] [Bug 1238408] Re: apport seems to be missing a dependency

[Norbert]

** Tags added: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1238408

Title:
  apport-collect is not functional until manual installation of python-
  apport

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10
  2. Try to launch `apport-collect 1712200`

  Expected results:
  apport-collect works out-the-box and collected corresponding info

  Actual results:
  apport-collect does not work and shows message:

  "You need to run 'sudo apt-get install python-apport' for apport-
  collect to work."

  Note: manual installation of python-apport adds 15 MB of new packages,
  after that apport-collect works as expected.

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

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

[Touch-packages] [Bug 1553782] Re: python-apport should be installed by default

[Norbert]

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

Got this bug on fresh installation of 17.10:

artful64@artful64:~$ apport-collect 1712200
You need to run 'sudo apt-get install python-apport' for apport-collect to work.

** This bug has been marked a duplicate of bug 1238408
   apport seems to be missing a dependency

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1553782

Title:
  python-apport should be installed by default

Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  On many occasions have I been asked to for instance to upload
  additional logs to a bug report using 'apport-collect', however I have
  found that one first has to install 'python-apport' as it is not
  installed by default with useful utilities like 'apport'.

  So like the useful utility 'apport' I think that it would be very good
  if 'python-apport' were to also be installed by default as it is very
  useful for handling bug reports, and if you are going to have the
  submitting tool installed by default, you should probably also have
  the handling tool installed by default. As I feel that they sort of
  come (or at least should come) together.

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

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

[Touch-packages] [Bug 1553782] Re: python-apport should be installed by default

[Launchpad Bug Tracker]

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

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1553782

Title:
  python-apport should be installed by default

Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  On many occasions have I been asked to for instance to upload
  additional logs to a bug report using 'apport-collect', however I have
  found that one first has to install 'python-apport' as it is not
  installed by default with useful utilities like 'apport'.

  So like the useful utility 'apport' I think that it would be very good
  if 'python-apport' were to also be installed by default as it is very
  useful for handling bug reports, and if you are going to have the
  submitting tool installed by default, you should probably also have
  the handling tool installed by default. As I feel that they sort of
  come (or at least should come) together.

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

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

[Touch-packages] [Bug 1553782] Re: python-apport should be installed by default

[Norbert]

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

** Tags added: artfuk

** Tags removed: artfuk
** Tags added: artful

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1553782

Title:
  python-apport should be installed by default

Status in Ubuntu GNOME:
  New
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  On many occasions have I been asked to for instance to upload
  additional logs to a bug report using 'apport-collect', however I have
  found that one first has to install 'python-apport' as it is not
  installed by default with useful utilities like 'apport'.

  So like the useful utility 'apport' I think that it would be very good
  if 'python-apport' were to also be installed by default as it is very
  useful for handling bug reports, and if you are going to have the
  submitting tool installed by default, you should probably also have
  the handling tool installed by default. As I feel that they sort of
  come (or at least should come) together.

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

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

[Touch-packages] [Bug 1725680] [NEW] DNS name resolution doesn't work on Artful

[Jan Rathmann]

Public bug reported:

If I boot my laptop with a live image or an installation of Ubuntu
17.10, DNS name resolution doesn't work (which means I can't access any
website).

Steps to reproduce:
- Boot laptop with Ubuntu 17.10 live image
- Connect to my wireless network
- Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
- Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

As a workaround, I can get a temporarily working DNS resolution by
manually editing /etc/resolv.conf (symlink to /run/systemd/resolve/stub-
resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or some
other known DNS server.

On Ubuntu 17.04 this bug is not present.

The original address in /run/systemd/resolve/stub-resolve.conf is
127.0.0.53 . I get immediate replies if I ping this address, but
nevertheless DNS resolution doesn't work.

It seems that the service systemd-networkd isn't active by default:
$ sudo systemctl status systemd-networkd
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendo
   Active: inactive (dead)
 Docs: man:systemd-networkd.service(8)

Manually starting it doesn't seem to help for this bug.

systemd-resolved is active:

$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor
   Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
   https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
 Main PID: 1095 (systemd-resolve)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
   └─1095 /lib/systemd/systemd-resolved

Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 49aac11d7b6f644
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 e06d44b80b8f1d3
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 10.in-add
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.

Kind regards,
Jan

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
Date: Sat Oct 21 12:26:00 2017
ExecutablePath: /lib/systemd/systemd-resolved
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Acer Extensa 5635Z
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: V0.3305
dmi.board.name: BA50-MV
dmi.board.vendor: Acer
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
dmi.product.name: Extensa 5635Z
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725680

Title:
  DNS name resolution doesn't work on Artful

Status in systemd package in Ubuntu:
  New

Bug description:
  If I boot my laptop with a live image or an installation of Ubuntu
  17.10, DNS name resolution doesn't work (which means I can't access
  any website).

  Steps to reproduce:
  - Boot laptop with Ubuntu 17.10 live image
  - Connect to my wireless network
  - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with 
the error message "Name or service not known"
  - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.

  As a workaround, I can get a temporarily working DNS resolution by
  manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
  /stub-resolve.conf) 

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

The change in the fstab seems to have worked only once. Today, it
doesn't boot again (with the changed fstab). I've tried switching from
UEFI to Legacy mode without luck, too.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1725675] [NEW] SIM-Card PIN-Code unlock windows spawns in front of login screen

[Stefan Helmert]

Public bug reported:

Sometimes the PIN-Code request window opens over the session unlock
screen. The window cannot be moved. Entering PIN-Code is possible but
fails.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
Uname: Linux 4.4.0-97-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Oct 21 14:22:26 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
 auto enp0s25
 iface enp0s25 inet manual
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

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

Title:
  SIM-Card PIN-Code unlock windows spawns in front of login screen

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sometimes the PIN-Code request window opens over the session unlock
  screen. The window cannot be moved. Entering PIN-Code is possible but
  fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87
  Uname: Linux 4.4.0-97-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct 21 14:22:26 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   auto enp0s25
   iface enp0s25 inet manual
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2017-08-25 (56 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2017-04-14T17:29:21.619202
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725675/+subscriptions

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

[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL

[Francis Ginther]

** Tags added: id-59ea8773d0c66354e179d305

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1725333

Title:
  do-release-upgrade broke WSL

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I had Ubuntu 17.04 installed in WSL and decided to upgrade it to
  17.10, so I had run do-release-upgrade, as I did before to upgrade to
  17.04. Everything was fine before script started upgrading packages.
  It's started from bash updating, and somehow there is a problem
  revealed that locale files is missing, and locale-gen can't be run
  (because of bug in WSL). I've tried to install language-pack-en as was
  suggested, but problem haven't resolved, any attempt to update leads
  to this error.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bash 4.4-2ubuntu1.1
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Fri Oct 20 18:03:30 2017
  Dmesg:
   
  DpkgTerminalLog:
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  DuplicateSignature:
   package:bash:4.4-2ubuntu1.1
   Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ...
   preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec 
>= 0' failed.
   dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack):
subprocess new pre-installation script was killed by signal (Aborted), core 
dumped
  ErrorMessage: subprocess new pre-installation script was killed by signal 
(Aborted), core dumped
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: bash
  Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new 
pre-installation script was killed by signal (Aborted), core dumped
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)

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

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

[Touch-packages] [Bug 1724718] Re: Fail to install to USB-HD from SDHC card

[Russ Herman]

Please withdraw. Final release installed successfully.

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1724718

Title:
  Fail to install to USB-HD from SDHC card

Status in busybox package in Ubuntu:
  New

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

  dd'd Artful 386 to 4GB SDHC card. Transferred card to ASUS 1005HA
  netbook and booted. After unmounting allowing and overwriting of
  /dev/sdg, began install to 60GB HD /dev/sdg with reformat of existing
  dev/sdg1 that had an old 16.04.02 install + using existing /dev/sdg5
  swap.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: busybox-static 1:1.22.0-19ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  CasperVersion: 1.387
  Date: Thu Oct 19 01:46:48 2017
  Dependencies:
   
  ExecutablePath: /bin/busybox
  LiveMediaBuild: Ubuntu-MATE 17.10 "Artful Aardvark" - Release i386 (20171017)
  ProcCmdline: /bin/busybox tail -f /var/log/installer/debug -f /var/log/syslog 
-q
  ProcEnviron:
   TERM=xterm-256color
   LC_NUMERIC=C.UTF-8
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  Signal: 7
  SourcePackage: busybox
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1725643] Re: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725643

Title:
  package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Fail occurs during upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  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: Sat Oct 21 10:21:00 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
  MachineType: Dell Inc. XPS 8500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725643/+subscriptions

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

[Touch-packages] [Bug 1725644] Re: package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725644

Title:
  package linux-firmware 1.169 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error appears during upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  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: Sat Oct 21 10:33:30 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.169 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725644/+subscriptions

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

[Touch-packages] [Bug 1725638] Re: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725638

Title:
  package linux-image-generic 4.13.0.16.17 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
  code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error appears during system upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.13.0.16.17
  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: Sat Oct 21 10:33:03 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
  MachineType: Dell Inc. XPS 8500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725638/+subscriptions

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

[Touch-packages] [Bug 1725644] [NEW] package linux-firmware 1.169 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Louis-Xavier Brusset]

Public bug reported:

Error appears during upgrade from 17.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-firmware 1.169
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: Sat Oct 21 10:33:30 2017
Dependencies:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: initramfs-tools
Title: package linux-firmware 1.169 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725644

Title:
  package linux-firmware 1.169 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error appears during upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-firmware 1.169
  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: Sat Oct 21 10:33:30 2017
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.169 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725644/+subscriptions

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

[Touch-packages] [Bug 1725641] [NEW] package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

[Vadim Peretokin]

Public bug reported:

Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
finally managed to login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 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
AptOrdering:
 libdb5.3:amd64: Configure
 multiarch-support:amd64: Configure
 libobs0:amd64: Install
 obs-plugins:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 21 10:13:28 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-03-23 (2037 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
PackageArchitecture: all
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
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

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


** Tags: amd64 apport-package artful

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

Title:
  package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in network-manager package in Ubuntu:
  New

Bug description:
  Botched upgrade from 17.04 to 17.10, the bug reporter came up after I
  finally managed to login.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: network-manager-config-connectivity-ubuntu 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
  AptOrdering:
   libdb5.3:amd64: Configure
   multiarch-support:amd64: Configure
   libobs0:amd64: Install
   obs-plugins:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 10:13:28 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-03-23 (2037 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  PackageArchitecture: all
  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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  Title: package network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725641/+subscriptions

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

[Touch-packages] [Bug 1725643] [NEW] package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Louis-Xavier Brusset]

Public bug reported:

Fail occurs during upgrade from 17.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
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: Sat Oct 21 10:21:00 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
MachineType: Dell Inc. XPS 8500
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: grub-pc 2.02~beta3-4ubuntu7
SourcePackage: initramfs-tools
Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0YJPT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: XPS 8500
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725643

Title:
  package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Fail occurs during upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  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: Sat Oct 21 10:21:00 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
  MachineType: Dell Inc. XPS 8500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-16-generic 4.13.0-16.19 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725643/+subscriptions

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

[Touch-packages] [Bug 1725638] [NEW] package linux-image-generic 4.13.0.16.17 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Louis-Xavier Brusset]

Public bug reported:

Error appears during system upgrade from 17.04 to 17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-generic 4.13.0.16.17
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: Sat Oct 21 10:33:03 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
MachineType: Dell Inc. XPS 8500
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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: grub-pc 2.02~beta3-4ubuntu7
SourcePackage: initramfs-tools
Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0YJPT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: XPS 8500
dmi.sys.vendor: Dell Inc.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1725638

Title:
  package linux-image-generic 4.13.0.16.17 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
  code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error appears during system upgrade from 17.04 to 17.10

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-generic 4.13.0.16.17
  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: Sat Oct 21 10:33:03 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=2840141a-e97a-45b4-ba77-708bf58324fa
  MachineType: Dell Inc. XPS 8500
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=271ba9b9-ca1b-4af8-9c5d-6f039ad2a1d6 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: initramfs-tools
  Title: package linux-image-generic 4.13.0.16.17 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YJPT1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd08/28/2013:svnDellInc.:pnXPS8500:pvr:rvnDellInc.:rn0YJPT1:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XPS 8500
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1725638/+subscriptions

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

[Touch-packages] [Bug 1725628] Re: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1725628

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Remove A software to see this bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   gksu: Remove
   ubuntu-minimal: Remove
   sudo: Remove
   y-ppa-manager: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 15:16:12 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-10-16 (4 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: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1725628] [NEW] package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Muzaml Jani]

Public bug reported:

Remove A software to see this bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.5
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptOrdering:
 gksu: Remove
 ubuntu-minimal: Remove
 sudo: Remove
 y-ppa-manager: Remove
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 21 15:16:12 2017
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
InstallationDate: Installed on 2017-10-16 (4 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: sudo
Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK

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


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/1725628

Title:
  package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  New

Bug description:
  Remove A software to see this bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptOrdering:
   gksu: Remove
   ubuntu-minimal: Remove
   sudo: Remove
   y-ppa-manager: Remove
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Oct 21 15:16:12 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-10-16 (4 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: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

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

[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1686189

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Touch-packages] [Bug 1725618] Re: pulseaudio crashed with SIGABRT in pa_mainloop_dispatch()

[Apport retracing service]

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

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 #1366819, 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/1725618/+attachment/4981438/+files/CoreDump.gz

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

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

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

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

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

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

** This bug has been marked a duplicate of bug 1366819
   pulseaudio crashed with SIGABRT in subscribe_callbac() from defer_cb() from 
dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1725618

Title:
  pulseaudio crashed with SIGABRT in pa_mainloop_dispatch()

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Watching youtube videos in firefox triggers this error and either the
  whole browser or just the one tab to crash.  Everything works fine in
  chromium.  Clicking through the "encountered an error" dialogue
  created this bug

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   geoff  2344 F...m pulseaudio
   /dev/snd/controlC1:  geoff  2344 F pulseaudio
   /dev/snd/controlC0:  geoff  2344 F pulseaudio
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Sat Oct 21 20:40:18 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-09-23 (1123 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/pulse-10.0/modules/module-stream-restore.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
  Title: pulseaudio crashed with SIGABRT in pa_mainloop_dispatch()
  UpgradeStatus: Upgraded to artful on 2017-10-21 (0 days ago)
  UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo 
vboxusers www-data
  dmi.bios.date: 07/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G750JS.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G750JS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG750JS.208:bd07/17/2014:svnASUSTeKCOMPUTERINC.:pnG750JS:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG750JS:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G750JS
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[diabloneo]

No, I wasn't using resolvconf.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[Steve Langasek]

Were you not using resolvconf on this system prior to upgrade?
NetworkManager should only have managed /etc/resolv.conf contents if it
did not detect that another system was managing it (resolvconf or
resolved).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1712283] Re: Cannot resolve DNS in artful daily

[diabloneo]

@vorlon

It just contained:

# Generated by NetworkManager
nameserver 127.0.1.1

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1712283

Title:
  Cannot resolve DNS in artful daily

Status in casper package in Ubuntu:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in netcfg package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live
  session / installed session - running on virtualbox 5.1.26.

  However I cannot ping google.com - "Name or service not known"

  Kind of difficult to run ubuntu-bug here without a fully functioning
  network.

  Happy to provide more details - please can someone guide me producing
  a much better bug-report?

  

  my zesty VM is working just fine.  As of a week ago, my artful daily
  was working just fine also.

  

  
  * /etc/resolv.conf is empty file on most images built, which is not right, it 
should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in 
image generation? systemd?

  * Adding a hack, to create /etc/resolv.conf if it does not exist, or
  is empty. src:systemd

  * network-manager does not consider that dns is managed by resolved if
  .53 is present in /etc/resolv.conf or if it points to stub-
  resolv.conf. src:network-manager

  * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf.
  Needs checking / fixing

  * caster has resolvconf integration

  * livecd-rootfs has resolvconf integration

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

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

[Touch-packages] [Bug 1725593] [NEW] 17.10 putty and synaptic Could not open X display Erreur de segmentation (core dumped)

[jean-eric mesmain]

Public bug reported:

these two apps don t show up
 putty
No protocol specified

** (putty:19873): WARNING **: Could not open X display
Erreur de segmentation (core dumped)

synaptic
No protocol specified

** (synaptic:19979): WARNING **: Could not open X display
Erreur de segmentation (core dumped)

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

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

Title:
  17.10 putty and synaptic  Could not open X display Erreur de
  segmentation (core dumped)

Status in network-manager package in Ubuntu:
  New

Bug description:
  these two apps don t show up
   putty
  No protocol specified

  ** (putty:19873): WARNING **: Could not open X display
  Erreur de segmentation (core dumped)

  synaptic
  No protocol specified

  ** (synaptic:19979): WARNING **: Could not open X display
  Erreur de segmentation (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1725593/+subscriptions

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

[Touch-packages] [Bug 1725582] [NEW] System freeze on boot since upgrade to 17.10

[Frederic berat]

Public bug reported:

This freeze appears on each boot since the dist upgrade to 17.10 (from 17.04) 
with the following kernel: linux-image-4.13.0-16-generic.
The ssh connexion becomes available after 3 to 5 minutes, and the login screen 
after more than 20 minutes.

This issue doesn't show up in recovery mode.
This issue doesn't show up with the previous kernel (from 17.04): 
linux-image-4.10.0-37-generic.

I Also tried the mainline drm-current: 
linux-image-4.14.0-996-generic_4.14.0-996.201710202201_amd64.deb
The issue is not visible then, but I don't have ethernet access any longer 
(which may be completely unrelated).

lsb_release -rd:
Description:Ubuntu 17.10
Release:17.10

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Sat Oct 21 08:18:25 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/580] 
[1002:67df] (rev ef) (prog-if 00 [VGA controller])
   Subsystem: Sapphire Technology Limited Radeon RX 570 [1da2:e366]
InstallationDate: Installed on 2017-09-30 (20 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99791e36-3af2-42ca-8376-ce7138f67d70 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0810
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X370-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0810:bd08/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
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

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


** Tags: amd64 apport-bug artful freeze ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1725582

Title:
  System freeze on boot since upgrade to 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  This freeze appears on each boot since the dist upgrade to 17.10 (from 17.04) 
with the following kernel: linux-image-4.13.0-16-generic.
  The ssh connexion becomes available after 3 to 5 minutes, and the login 
screen after more than 20 minutes.

  This issue doesn't show up in recovery mode.
  This issue doesn't show up with the previous kernel (from 17.04): 
linux-image-4.10.0-37-generic.

  I Also tried the mainline drm-current: 
linux-image-4.14.0-996-generic_4.14.0-996.201710202201_amd64.deb
  The issue is not visible then, but I don't have ethernet access any longer 
(which may be completely unrelated).

  lsb_release -rd:
  Description:  Ubuntu 17.10
  Release:  17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Sat Oct 21 08:18:25 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily 

[Touch-packages] [Bug 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1500193

Title:
  systemd-journald crashed with SIGABRT in dev_kmsg_record()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I don't know details

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 27 01:21:55 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-09-26 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Lsusb:
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 064e:c341 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff46d4c1e8) at libc-start.c:289
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __libc_start_main()
  UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/16/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.61
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()

[Apport retracing service]

** Tags added: artful

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1500193

Title:
  systemd-journald crashed with SIGABRT in dev_kmsg_record()

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I don't know details

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 27 01:21:55 2015
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2015-09-26 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  Lsusb:
   Bus 003 Device 002: ID 8087:8000 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 064e:c341 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcCmdline: /lib/systemd/systemd-journald
  ProcEnviron:
   LANG=el_GR.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed 
root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff46d4c1e8) at libc-start.c:289
   ?? ()
  Title: systemd-journald crashed with SIGABRT in __libc_start_main()
  UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/16/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.61
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2166
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.42
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 098B1140410620180
  dmi.sys.vendor: Hewlett-Packard

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

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