date:20180124

Yes! Thank you.

Removing gtk3-nocsd fixed it. And compared to a laptop that never had
the problem, that machine never had gtk3-nocsd installed.

** Package changed: ubuntu-themes (Ubuntu) => gtk3-nocsd (Ubuntu)

** No longer affects: ubuntu-themes

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

** No longer affects: mutter (Ubuntu)

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

Title:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing in Wayland logins

Status in gtk3-nocsd package in Ubuntu:
  New

Bug description:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing window buttons + rounding in Wayland logins. Screenshots
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 24 10:15:01 2018
  InstallationDate: Installed on 2017-12-12 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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/gtk3-nocsd/+bug/1745070/+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] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

-- 
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 drops connection and reconnects in 17.10 (But not in
  17.04)

Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

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/linux/+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   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1426228] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [reload: Unknown instance: invo

See also: bug 1682731

** Summary changed:

- package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1 [reload: 
Unknown instance: invoke-rc.d: initscript dbus, action "force-reload" failed.]

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1
  [reload: Unknown instance: invoke-rc.d: initscript dbus, action
  "force-reload" failed.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Balnk screen on start up, so I went to the fails safe boot followed by
  fixing broken packages option, and this is the message resulting.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Fri Feb 27 18:09:53 2015
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-05-05 (1028 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: TOSHIBA Satellite PRO C660
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=70e0e896-ab94-42e6-83d0-ff70ceeba57c ro recovery nomodeset
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to trusty on 2014-09-06 (173 days ago)
  dmi.bios.date: 03/18/2011
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.00
  dmi.board.asset.tag: NULL
  dmi.board.name: PWWHA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.00:bd03/18/2011:svnTOSHIBA:pnSatellitePROC660:pvrPSC1RA-003001:rvnTOSHIBA:rnPWWHA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite PRO C660
  dmi.product.version: PSC1RA-003001
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 68:A3:C4:88:85:33  ACL MTU: 1022:8  SCO MTU: 121:3
UP RUNNING PSCAN 
RX bytes:1064 acl:0 sco:0 events:55 errors:0
TX bytes:1427 acl:0 sco:0 commands:53 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1426228/+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 1717588] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** This bug is no longer a duplicate of bug 1717589
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  I was trying to perform the update on linux 16.04 LTE of my QNAP TS-
  253A NAS server when the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  Uname: Linux 4.2.8 x86_64
  NonfreeKernelModules: vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_scsi 
target_core_mod vhost_net vhost macvtap macvlan tun vringh virtio_scsi 
virtio_pci virtio_net virtio_mmio virtio_console virtio_blk virtio_balloon 
virtio_rng virtio_ring virtio kvm_intel kvm xt_nat rfcomm iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi fbdisk cdc_ether ipt_MASQUERADE 
iptable_nat nf_nat_masquerade_ipv4 nf_nat_ipv4 nf_nat xt_policy xt_mark bonding 
br_netfilter bridge stp 8021q ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core snd_usb_caiaq snd_usb_audio snd_usbmidi_lib snd_seq_midi 
snd_rawmidi fnotify udf isofs sp5100_tco iTCO_wdt tbs_keys ufsd jnl pl2303 
usbserial qm2_i2c intel_ips drbd flashcache dm_tier_btier_algo dm_thin_pool 
dm_bio_prison dm_persistent_data hal_netlink k10temp coretemp r8152 usbnet mii 
igb e1000e mpt3sas mpt2sas scsi_transport_sas raid_class usb_storage xhci_pci 
xhci_hcd usblp uhci_hcd ehci_pci ehci_hcd
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 15 21:39:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InterestingModules: rfcomm
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1005:b155 Apacer Technology, Inc. 
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: consoleblank=0 console=ttyS0,115200n8 
video=HDMI-A-1:800x600@60 video=HDMI-A-2:800x600@60 i915.disable_dp_dual_mode=1 
i915.disable_power_well=0 memmap=2M$0x800 ramoops.mem_address=0x800 
ramoops.mem_size=0x20 ramoops.console_size=0x10 
BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: 
getfacl: /dev/rfkill: No such file or directory
  hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI 
socket.: Address family not supported by protocol
  rfkill: Can't open RFKILL control device: No such file or directory
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717588/+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 1682731] Re: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 [invoke-rc.d: initscript bluetooth,

See also: bug 1426228

** Summary changed:

- package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
+ package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1
  [invoke-rc.d: initscript bluetooth, action "restart" failed.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  passwd root

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 14 10:38:35 2017
  DpkgHistoryLog: Start-Date: 2017-04-14  10:35:52
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-04-02 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: bluez
  Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GDIMS.20G
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GD
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A:
  dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 54:27:1E:9E:18:49  ACL MTU: 820:8  SCO MTU: 255:16
DOWN 
RX bytes:1274 acl:0 sco:0 events:129 errors:0
TX bytes:25311 acl:0 sco:0 commands:129 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1682731/+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 1682751] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

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

** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Here is the terminal display for sudo apt install bluez:

  Lecture des listes de paquets... Fait
  Construction de l'arbre des dépendances   
  Lecture des informations d'état... Fait
  Les NOUVEAUX paquets suivants seront installés :
bluez
  0 mis à jour, 1 nouvellement installés, 0 à enlever et 0 non mis à jour.
  Il est nécessaire de prendre 0 o/899 ko dans les archives.
  Après cette opération, 4 218 ko d'espace disque supplémentaires seront 
utilisés.
  Sélection du paquet bluez précédemment désélectionné.
  (Lecture de la base de données... 205650 fichiers et répertoires déjà 
installés.)
  Préparation du dépaquetage de .../bluez_5.37-0ubuntu5_amd64.deb ...
  Dépaquetage de bluez (5.37-0ubuntu5) ...
  Traitement des actions différées (« triggers ») pour systemd (229-4ubuntu16) 
...
  Traitement des actions différées (« triggers ») pour ureadahead (0.100.0-19) 
...
  ureadahead will be reprofiled on next reboot
  Traitement des actions différées (« triggers ») pour dbus (1.10.6-1ubuntu3.3) 
...
  Traitement des actions différées (« triggers ») pour man-db (2.7.5-1) ...
  Paramétrage de bluez (5.37-0ubuntu5) ...
  Job for bluetooth.service failed because the control process exited with 
error code. See "systemctl status bluetooth.service" and "journalctl -xe" for 
details.
  invoke-rc.d: initscript bluetooth, action "restart" failed.
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
6ms ago
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/FAILURE)
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Blueto...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetoot...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
se...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to 
start...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.servi...
  Hint: Some lines were ellipsized, use -l to show in full.
  dpkg: erreur de traitement du paquet bluez (--configure) :
   le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
-

  Here the terminal display for systemctl status bluetooth.service:

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: failed (Result: exit-code) since ven. 2017-04-14 09:59:14 CEST; 
5min 
   Docs: man:bluetoothd(8)
Process: 10540 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, 
status=1/
   Main PID: 10540 (code=exited, status=1/FAILURE)
 Status: "Starting up"

  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Starting 
Bluetooth service...
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: 
Bluetooth daemon 5.37
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC bluetoothd[10540]: D-Bus 
setup failed: Connection ":1.112" is not allowed to own the service "org.bluez" 
due to own the service "org.bluez" due to security policies in the 
configuration file
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Main process exited, code=exited, status=1/FAILURE
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: Failed to start 
Bluetooth service.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Unit entered failed state.
  avril 14 09:59:14 cid-350V5C-351V5C-3540VC-3440VC systemd[1]: 
bluetooth.service: Failed with result 'exit-code'.

  
-

  Here

[Touch-packages] [Bug 1717589] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I was trying to perform the update on linux 16.04 LTE of my QNAP TS-
  253A NAS server when the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  Uname: Linux 4.2.8 x86_64
  NonfreeKernelModules: vfio_pci vfio_virqfd vfio_iommu_type1 vfio vhost_scsi 
target_core_mod vhost_net vhost macvtap macvlan tun vringh virtio_scsi 
virtio_pci virtio_net virtio_mmio virtio_console virtio_blk virtio_balloon 
virtio_rng virtio_ring virtio kvm_intel kvm xt_nat rfcomm iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi fbdisk cdc_ether ipt_MASQUERADE 
iptable_nat nf_nat_masquerade_ipv4 nf_nat_ipv4 nf_nat xt_policy xt_mark bonding 
br_netfilter bridge stp 8021q ipv6 uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core snd_usb_caiaq snd_usb_audio snd_usbmidi_lib snd_seq_midi 
snd_rawmidi fnotify udf isofs sp5100_tco iTCO_wdt tbs_keys ufsd jnl pl2303 
usbserial qm2_i2c intel_ips drbd flashcache dm_tier_btier_algo dm_thin_pool 
dm_bio_prison dm_persistent_data hal_netlink k10temp coretemp r8152 usbnet mii 
igb e1000e mpt3sas mpt2sas scsi_transport_sas raid_class usb_storage xhci_pci 
xhci_hcd usblp uhci_hcd ehci_pci ehci_hcd
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 15 21:39:42 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InterestingModules: rfcomm
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1005:b155 Apacer Technology, Inc. 
   Bus 001 Device 002: ID 045e:0800 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: consoleblank=0 console=ttyS0,115200n8 
video=HDMI-A-1:800x600@60 video=HDMI-A-2:800x600@60 i915.disable_dp_dual_mode=1 
i915.disable_power_well=0 memmap=2M$0x800 ramoops.mem_address=0x800 
ramoops.mem_size=0x20 ramoops.console_size=0x10 
BOOT_IMAGE=/boot/bzImage root=/dev/ram0 rw
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: 
getfacl: /dev/rfkill: No such file or directory
  hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI 
socket.: Address family not supported by protocol
  rfkill: Can't open RFKILL control device: No such file or directory
  upstart.bluetooth.override: manual

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1717589/+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 1745239] Re: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

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

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


** This bug has been marked a duplicate of bug 1682731
   package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1 [invoke-rc.d: initscript 
bluetooth, action "restart" failed.]

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

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745239/+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 1454297] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

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

** This bug has been marked a duplicate of bug 1426228
   package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Reinstalando o sistema.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  AptOrdering:
   bluez: Configure
   bluez-alsa: Configure
  Architecture: amd64
  Date: Tue May 12 09:01:24 2015
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:sub-processo script 
post-installation instalado retornou estado de saída de erro 1
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2015-05-12 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterestingModules: bnep rfcomm bluetooth
  MachineType: PCDIGIT OEM
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=7aa02f80-5352-4f4a-8952-776e18cc919d ro recovery nomodeset
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: G31MXP
  dmi.board.vendor: Foxconn
  dmi.board.version: FAB:1.1
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/03/2009:svnPCDIGIT:pnOEM:pvrOEM:rvnFoxconn:rnG31MXP:rvrFAB1.1:cvnOEM:ct3:cvrOEM:
  dmi.product.name: OEM
  dmi.product.version: OEM
  dmi.sys.vendor: PCDIGIT
  hciconfig:
   
  rfkill:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1454297/+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 1565240] Re: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces nainštalovaný skript post-installation vrátil chybový kód 1

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

** This bug has been marked a duplicate of bug 1426228
   package bluez 4.101-0ubuntu13.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces
  nainštalovaný skript post-installation vrátil chybový kód 1

Status in bluez package in Ubuntu:
  New

Bug description:
  problem in install

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13.1
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  AptOrdering: bluez: Configure
  Architecture: i386
  Date: Sat Apr  2 12:41:40 2016
  DuplicateSignature: package:bluez:4.101-0ubuntu13.1:podproces nainštalovaný 
skript post-installation vrátil chybový kód 1
  ErrorMessage: podproces nainštalovaný skript post-installation vrátil chybový 
kód 1
  InstallationDate: Installed on 2016-04-02 (0 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  InterestingModules: bnep rfcomm bluetooth
  MachineType: ASUSTeK Computer Inc. F3JC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-83-generic 
root=UUID=9638eded-ec1d-4d33-9ff1-a1853d4405d9 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.11
  SourcePackage: bluez
  Title: package bluez 4.101-0ubuntu13.1 failed to install/upgrade: podproces 
nainštalovaný skript post-installation vrátil chybový kód 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F3JC
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr307:bd06/11/2008:svnASUSTeKComputerInc.:pnF3JC:pvr1.0:rvnASUSTeKComputerInc.:rnF3JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.name: F3JC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565240/+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 1384952] Re: USB Soundcard no microphone (input) device

2018-01-24 Thread Wyatt Childers

I fixed this on my U7 with the info in this post.

https://forums.gentoo.org/viewtopic-t-1025106-start-0.html



For posterity in case the form post disappears...

I found my answer here:

https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Microphone_not_detected_by_PulseAudio

The summary:

I edited /etc/pulse/default.pa to add the line:

Code:   
load-module module-alsa-source device=hw:2,1


...since "arecord -l" showed that my missing mic was Card 2, Device 1

This newly-added line has to precede the lines:

Code:   
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect  


...in my case, this wound up being Line 52 of default.pa

I hope this can help someone else!

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

Title:
  USB Soundcard no microphone (input) device

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  My Asus Xonar U7 Echelon External sound device working without input/capture 
device.
  No input device , Nothing recording with my usb soundcard. 

  ~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 1: Ed [Xonar U7 Echelon Ed.], device 1: USB Audio [USB Audio #1]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ~$ lsusb
  Bus 002 Device 002: ID 1043:85c1 iCreate Technologies Corp.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.17.1-031701-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alper  2249 F pulseaudio
   /dev/snd/pcmC1D0p:   alper  2249 F...m pulseaudio
   /dev/snd/controlC1:  alper  2249 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 24 00:46:11 2014
  InstallationDate: Installed on 2014-10-07 (16 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G46 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.2:bd02/04/2013:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7693
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-10-23T19:38:42.156766

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1384952/+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 1745239] [NEW] package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread Hugo PAIVA RODRIGUES

Public bug reported:

bug

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
Uname: Linux 4.4.0-111-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Wed Jan 24 09:22:04 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-01-16 (739 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
InterestingModules: bnep btusb bluetooth
MachineType: TOSHIBA SATELLITE C875-14H
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: bluez
Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/01/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.80
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: SATELLITE C875-14H
dmi.product.version: PSCBCE-02L002FR
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

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


** Tags: amd64 apport-package package-from-proposed third-party-packages xenial

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

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745239/+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 1745239] Re: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread 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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1745239

Title:
  package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.4.0-111.134-generic 4.4.98
  Uname: Linux 4.4.0-111-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 09:22:04 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-01-16 (739 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: bnep btusb bluetooth
  MachineType: TOSHIBA SATELLITE C875-14H
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-111-generic 
root=UUID=1bb1ab31-fec5-4cde-ac3f-1eed4203d409 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEC875-14H:pvrPSCBCE-02L002FR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE C875-14H
  dmi.product.version: PSCBCE-02L002FR
  dmi.sys.vendor: TOSHIBA
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 24:FD:52:15:9B:97  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:2526 acl:0 sco:0 events:181 errors:0
TX bytes:26261 acl:0 sco:0 commands:181 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1745239/+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 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction

2018-01-24 Thread amk

Now found this bug, I think it is the lightdm who is not reporting idle
status to the system. See
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606 for a
script I run via cron every 15 minutes that overrides active status of
login screens or closing sessions. It also takes care of commands
running under sleep inhibitor.

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

Title:
  IdleAction=suspend specified in logind.conf must systematically be
  inhibited during user interaction

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I want my computer to suspend when there is NO opened user session.

  So, I have activated following lines inside '/etc/systemd/logind.conf' :
  IdleAction=suspend
  IdleActionSec=15min

  -  Systematically , under Ubuntu Vivid (15.04), this works correctly :
 During user interaction, the computer does NOT automatically suspend, but 
stays continuously alive.
 Once all users have closed their session, the computer automatically 
suspends after 15 min.

  -  But systematically , under Ubuntu Wily (15.10 beta2), the computer 
automatically suspends after 15 min EVEN during user interaction.
 Hitting the keyboard makes the computer resume without data loss, but this 
is still annoying.
 In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must 
systematically be inhibited during user interaction.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-14-generic 4.2.0-14.16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  z_admin1665 F pulseaudio
   /dev/snd/controlC1:  z_admin1665 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  8 19:26:59 2015
  HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140
  InstallationDate: Installed on 2015-09-27 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-14-generic N/A
   linux-backports-modules-4.2.0-14-generic  N/A
   linux-firmware1.149
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1504254/+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 1730606] Re: systemd idleaction=suspend not working in multiseat while a screen is showing login prompt

2018-01-24 Thread amk

I run the attached workaround script every 15 minutes from cron.

** Attachment added: "idlecheck.pl"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+attachment/5042477/+files/idlecheck.pl

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

Title:
  systemd idleaction=suspend not working in multiseat while a screen is
  showing login prompt

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04.3 LTS, multiseat setup.
  systemd:  Installed: 229-4ubuntu21
  lightdm:  Installed: 1.18.3-0ubuntu1.1

  logind.conf:IdleAction=suspend
  logind.conf:IdleActionSec=300

  Using multiseat, it is not possible to have gnome settings controlling
  idle suspend, as it would ignore the other seat. IdleAction=suspend in
  /etc/systemd/logind.conf works well, provided both seats are logged in
  or locked.

  After boot, or after logout the seat remains showing login screen and
  the system never suspends.

  loginctl show-session provides IdleHint=yes that allows to determine
  whether the user is active. For some reason Active property is yes all
  the time.

  But for the login screen the show-session does not provide the hint
  about seat idling:

  $ loginctl show-session c9
  Id=c9
  User=108
  Name=lightdm
  Timestamp=Sun 2017-11-05 22:35:37 CET
  TimestampMonotonic=13418600852
  VTNr=7
  Seat=seat0
  Display=:1
  Remote=no
  Service=lightdm-greeter
  Scope=session-c9.scope
  Leader=12431
  Audit=0
  Type=x11
  Class=greeter
  Active=yes
  State=active
  IdleHint=no
  IdleSinceHint=0
  IdleSinceHintMonotonic=0

  Working on a script to check for IdleHint=Yes and Service=lightdm-
  greeter and suspend based on this.

  I am marking this as a bug in lightdm because I think it is not
  correctly reporting the idle status to the system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+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 1510570] [bluez/xenial] possible regression found

2018-01-24 Thread Ubuntu Foundations Team Bug Bot

As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of bluez from xenial-proposed
was performed and bug 1744806 was found. Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1744806 (not this bug). Thanks!

** Tags added: verification-failed

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

When the Bluetooth adapter is not powered on it is not possible to use
it in normal way. We used to have a hack to force powering on by using
an udev rule but this doe snot work anymore. Luckily the BlueZ has
introduced "AutoEnable" option that makes the stack power on adapters by
itself.

Backporting this to xenial will improve life of the desktop users and
will not require them to hack the solution on their own. The fix itself
uses the well known solution to this problem that is floating around
there for a while.

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

. 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
instead of udev rules.

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+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 1411637] Re: apt-get command line upgrade, to know when to restart

2018-01-24 Thread Nikita Yerenkov-Scott

Well, if you are doing this in the command-line, then generally it would
be seen as strange if something GUI wise popped up. And especially so
would it be useless if you were in the console with no GUI or you were
using apt as a dependency of another program. Then this popup might
become quite a nuisance.

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

Title:
  apt-get command line upgrade, to know when to restart

Status in Ubuntu GNOME:
  Confirmed
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  When you run the application Software Updater and I install some
  updates which need a restart of your computer, it tells you that you
  need to restart your computer. But when running this command in
  Terminal: sudo apt-get upgrade

  It is not clear whether or not the packages which you have upgraded
  require a restart of the computer once they have finished upgrading.

  So what would be really useful instead of having to go and look in
  your /var/run/ folder to check if /var/run/reboot-required exists, it
  would be really good if on completion of the command for it to somehow
  just tell you if a restart is required. Even if it just says either:

  RESTART REQUIRED = TRUE

  or

  RESTART REQUIRED = FALSE

  Depending on whether or not a restart is needed. Or as it used to do
  for it to tell you here: Restart_to_complete_updates.bmp

  Image refereed to has been attached.

  System information:

  Description:  Ubuntu 14.10
  Release:  14.10

  Package version information:

  apt:
Installed: 1.0.9.2ubuntu2
Candidate: 1.0.9.2ubuntu2
Version table:
   *** 1.0.9.2ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1411637/+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 1411637] Re: apt-get command line upgrade, to know when to restart

2018-01-24 Thread Julian Andres Klode

You should get the same popup when running apt as you do with update-
manager or any other package management tool for that matter.

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

Title:
  apt-get command line upgrade, to know when to restart

Status in Ubuntu GNOME:
  Confirmed
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  When you run the application Software Updater and I install some
  updates which need a restart of your computer, it tells you that you
  need to restart your computer. But when running this command in
  Terminal: sudo apt-get upgrade

  It is not clear whether or not the packages which you have upgraded
  require a restart of the computer once they have finished upgrading.

  So what would be really useful instead of having to go and look in
  your /var/run/ folder to check if /var/run/reboot-required exists, it
  would be really good if on completion of the command for it to somehow
  just tell you if a restart is required. Even if it just says either:

  RESTART REQUIRED = TRUE

  or

  RESTART REQUIRED = FALSE

  Depending on whether or not a restart is needed. Or as it used to do
  for it to tell you here: Restart_to_complete_updates.bmp

  Image refereed to has been attached.

  System information:

  Description:  Ubuntu 14.10
  Release:  14.10

  Package version information:

  apt:
Installed: 1.0.9.2ubuntu2
Candidate: 1.0.9.2ubuntu2
Version table:
   *** 1.0.9.2ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1411637/+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 1745027] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread robith

Changed vlan ip back to lan and it started

Dňa 24. 1. 2018 18:05 používateľ "Joshua Powers" 
napísal:

> Thanks for taking the time to file a bug!
>
>
> It appears that the post-install failed to start the SSH server. The
> latest version of SSH came only with 4 security fixes so it is not obvious
> what would be causing this:
> http://changelogs.ubuntu.com/changelogs/pool/main/o/openssh/openssh_7.2p2-
> 4ubuntu2.4/changelog
>
> Can you verify your sshd config is valid by running `sudo /usr/sbin/sshd
> -t && echo PASS || echo FAIL` can you also try manually starting the ssh
> server via `sudo systemctl restart ssh.service` and see if any error
> message appear in `sudo systemctl status ssh.service`?
>
>
>
> ** Changed in: openssh (Ubuntu)
>Status: New => Incomplete
>
> ** Changed in: openssh (Ubuntu)
>Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1745027
>
> Title:
>   package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
>   subprocess installed post-installation script returned error exit
>   status 1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/
> 1745027/+subscriptions
>

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Started installing upgrade new kernels.
  But yesterday i did not finish seting up vlan.
  So in sshd config remained a address for vlan.
  in net conf was set up automatic vlan conf

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Tue Jan 23 21:47:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-11-12 (803 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 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/openssh/+bug/1745027/+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 1411637] Re: apt-get command line upgrade, to know when to restart

2018-01-24 Thread Nikita Yerenkov-Scott

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

** Changed in: ubuntu-gnome
   Status: New => Confirmed

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

Title:
  apt-get command line upgrade, to know when to restart

Status in Ubuntu GNOME:
  Confirmed
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  When you run the application Software Updater and I install some
  updates which need a restart of your computer, it tells you that you
  need to restart your computer. But when running this command in
  Terminal: sudo apt-get upgrade

  It is not clear whether or not the packages which you have upgraded
  require a restart of the computer once they have finished upgrading.

  So what would be really useful instead of having to go and look in
  your /var/run/ folder to check if /var/run/reboot-required exists, it
  would be really good if on completion of the command for it to somehow
  just tell you if a restart is required. Even if it just says either:

  RESTART REQUIRED = TRUE

  or

  RESTART REQUIRED = FALSE

  Depending on whether or not a restart is needed. Or as it used to do
  for it to tell you here: Restart_to_complete_updates.bmp

  Image refereed to has been attached.

  System information:

  Description:  Ubuntu 14.10
  Release:  14.10

  Package version information:

  apt:
Installed: 1.0.9.2ubuntu2
Candidate: 1.0.9.2ubuntu2
Version table:
   *** 1.0.9.2ubuntu2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1411637/+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 1745186] [NEW] tune2fs doesn't set UUID on a loopback device after mount/unmount

2018-01-24 Thread Slava Abramov

Public bug reported:

Below is the script we're running.  tune2fs doesn't set UUID (can be
checked with blkid) and exits abnormally (so that commands after tune2fs
call are not getting executed).

If we move tune2fs call above the mount command, everything works fine.
Also, it works fine everywhere else including Ubuntu 16.04.3.

#!/bin/bash
set -e
FOREMAN_SIZE=100
UUID="7b48ec41-a9fc-4937-b368-dfeae01c49f7"
MNT=$(mktemp -d -t mnt.XX)
trap "[[ -z "$MNT" ]] || rm -rf $MNT ||:" 0 1 2 3 15
if [[ -f foreman.tar.xz ]] && [[ ! -f foreman.img ]]; then
echo "Creating \"foreman\" home image ..."
qemu-img create -f raw -o size=${FOREMAN_SIZE}G foreman.img
lo=$(sudo losetup --show -f foreman.img)
echo -e "n\np\n\n\n\nw" | sudo fdisk $lo ||:
sudo kpartx -asv $lo
sudo mkfs.ext4 /dev/mapper/${lo##*/}p1
sudo mount /dev/mapper/${lo##*/}p1 $MNT
sudo tar -C $MNT -Jxvf foreman.tar.xz
sudo umount $MNT
sudo tune2fs /dev/mapper/${lo##*/}p1 -U $UUID
sudo kpartx -d $lo
sudo losetup -d $lo
fi

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: e2fsprogs 1.43.5-1
ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 24 12:02:26 2018
InstallationDate: Installed on 2018-01-10 (14 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
SourcePackage: e2fsprogs
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  tune2fs doesn't set UUID on a loopback device after mount/unmount

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Below is the script we're running.  tune2fs doesn't set UUID (can be
  checked with blkid) and exits abnormally (so that commands after
  tune2fs call are not getting executed).

  If we move tune2fs call above the mount command, everything works
  fine.  Also, it works fine everywhere else including Ubuntu 16.04.3.

  #!/bin/bash
  set -e
  FOREMAN_SIZE=100
  UUID="7b48ec41-a9fc-4937-b368-dfeae01c49f7"
  MNT=$(mktemp -d -t mnt.XX)
  trap "[[ -z "$MNT" ]] || rm -rf $MNT ||:" 0 1 2 3 15
  if [[ -f foreman.tar.xz ]] && [[ ! -f foreman.img ]]; then
  echo "Creating \"foreman\" home image ..."
  qemu-img create -f raw -o size=${FOREMAN_SIZE}G foreman.img
  lo=$(sudo losetup --show -f foreman.img)
  echo -e "n\np\n\n\n\nw" | sudo fdisk $lo ||:
  sudo kpartx -asv $lo
  sudo mkfs.ext4 /dev/mapper/${lo##*/}p1
  sudo mount /dev/mapper/${lo##*/}p1 $MNT
  sudo tar -C $MNT -Jxvf foreman.tar.xz
  sudo umount $MNT
  sudo tune2fs /dev/mapper/${lo##*/}p1 -U $UUID
  sudo kpartx -d $lo
  sudo losetup -d $lo
  fi

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: e2fsprogs 1.43.5-1
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 24 12:02:26 2018
  InstallationDate: Installed on 2018-01-10 (14 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1745186/+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 1745070] Re: Decorations/headerbars are broken in bionic: double bar in Xorg logins and missing in Wayland logins

2018-01-24 Thread Khurshid Alam

Do you have gtk3-nocsd installed? It is supposed to be disabled for
Gnome session. But it is not working properly.

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

Title:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing in Wayland logins

Status in Ubuntu theme:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Decorations/headerbars are broken in bionic: double bar in Xorg logins
  and missing window buttons + rounding in Wayland logins. Screenshots
  attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Wed Jan 24 10:15:01 2018
  InstallationDate: Installed on 2017-12-12 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  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-themes/+bug/1745070/+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 1745027] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-01-24 Thread Joshua Powers

Thanks for taking the time to file a bug!


It appears that the post-install failed to start the SSH server. The latest 
version of SSH came only with 4 security fixes so it is not obvious what would 
be causing this:
http://changelogs.ubuntu.com/changelogs/pool/main/o/openssh/openssh_7.2p2-4ubuntu2.4/changelog

Can you verify your sshd config is valid by running `sudo /usr/sbin/sshd
-t && echo PASS || echo FAIL` can you also try manually starting the ssh
server via `sudo systemctl restart ssh.service` and see if any error
message appear in `sudo systemctl status ssh.service`?



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

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Started installing upgrade new kernels.
  But yesterday i did not finish seting up vlan.
  So in sshd config remained a address for vlan.
  in net conf was set up automatic vlan conf

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Tue Jan 23 21:47:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-11-12 (803 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 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/openssh/+bug/1745027/+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 1745173] Re: dash uses wrong path to dpkg-divert in preinst script

2018-01-24 Thread George Shuklin

My bad, I had some junk in /usr/local/sbin

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

Title:
  dash uses wrong path to dpkg-divert in preinst script

Status in dash package in Ubuntu:
  Invalid

Bug description:
  Preparing to unpack .../dash_0.5.8-2.5ubuntu1_amd64.deb ...
  /var/lib/dpkg/tmp.ci/preinst: line 7: /usr/local/sbin/dpkg-divert: No such 
file or directory
  dpkg: error processing archive 
/var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb (--unpack):
   new dash package pre-installation script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   /var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb

  
  /usr/local/sbin/dpkg-divert is not valid path. /usr/bin/dpkg-divert is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dash 0.5.8-2.3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Jan 24 17:57:03 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1649 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  SourcePackage: dash
  UpgradeStatus: Upgraded to bionic on 2017-06-22 (216 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1745173/+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 1745173] [NEW] dash uses wrong path to dpkg-divert in preinst script

2018-01-24 Thread George Shuklin

Public bug reported:

Preparing to unpack .../dash_0.5.8-2.5ubuntu1_amd64.deb ...
/var/lib/dpkg/tmp.ci/preinst: line 7: /usr/local/sbin/dpkg-divert: No such file 
or directory
dpkg: error processing archive 
/var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb (--unpack):
 new dash package pre-installation script subprocess returned error exit status 
127
Errors were encountered while processing:
 /var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb


/usr/local/sbin/dpkg-divert is not valid path. /usr/bin/dpkg-divert is.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dash 0.5.8-2.3ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Jan 24 17:57:03 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-07-19 (1649 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
SourcePackage: dash
UpgradeStatus: Upgraded to bionic on 2017-06-22 (216 days ago)

** Affects: dash (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug bionic

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

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

Title:
  dash uses wrong path to dpkg-divert in preinst script

Status in dash package in Ubuntu:
  Invalid

Bug description:
  Preparing to unpack .../dash_0.5.8-2.5ubuntu1_amd64.deb ...
  /var/lib/dpkg/tmp.ci/preinst: line 7: /usr/local/sbin/dpkg-divert: No such 
file or directory
  dpkg: error processing archive 
/var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb (--unpack):
   new dash package pre-installation script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   /var/cache/apt/archives/dash_0.5.8-2.5ubuntu1_amd64.deb

  
  /usr/local/sbin/dpkg-divert is not valid path. /usr/bin/dpkg-divert is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dash 0.5.8-2.3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Wed Jan 24 17:57:03 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1649 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  SourcePackage: dash
  UpgradeStatus: Upgraded to bionic on 2017-06-22 (216 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1745173/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2018-01-24 Thread Frank Heimes

** Changed in: ubuntu-power-systems
   Status: Incomplete => Triaged

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Triaged
Status in util-linux source package in Xenial:
  Triaged

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010
  [

[Touch-packages] [Bug 1740484] Re: video corruption with amd RX560 and 2k display

2018-01-24 Thread Luke McKee

This may be EFI bios related / amdgpu.ko kernel driver dpm powerplay
related.

The dmesg.txt attached seems to confirm this in this ticket.

The problem is not software, it's overheating / hardware related. It's
affecting AMI EFI bios code + AMD GPU SBIOS powerplay voltage tables.

See this thread.
https://forum-en.msi.com/index.php?topic=298468.0

Here is an email I just sent to msi support about this saga, as they are
trying to replicate this defect as it's no good when fans either don't
spin up on some cards, or stay locked at 1000rpm out of 3000rpm. No good
= the card crashing corruption etc software issues. This user needs to
monitor his fan speed / temperature when using the GPU. I have emails
about how to that as well if he wants.

I'm using sabayon.org Linux out of the box to reproduce the error. Latest
version I think 18.02 or 17.xx from memory.

╠ @@ Package: sys-kernel/linux-sabayon-4.14.12-r1 branch: 5,
[sabayon-weekly]
╠ Available: version: 4.14.12-r1 ~ tag: NoTag ~ revision: 0
╠ Installed: version: 4.14.12-r1 ~ tag: NoTag ~ revision: 0
╠ Slot: 4.14
╠ Homepage: https://github.com/Sabayon/kernel
╠ Description: Official Sabayon Linux Standard
╠ kernel image

But i'm moving to pure gentoo.org custom compiled everything. Right now
whilst i'm transitioning I"m using an out of the box kernel.

All it matters is if upstream Linux is broken then many linux
distributions by default are broken. And this admgpu driver not handling
modified voltage tables is going to kill cards running linux.

Ubuntu's kernel may have a custom patch to fix this already, that's why you
can't replicate it now. let me look at the sources / patches for ubuntu kernel
now.

https://bugs.freedesktop.org/show_bug.cgi?id=100443

See the original post I put up, that's other people getting it.

Someone else on the internet with the bug in Ubuntu:
http://www.cadalyst.com/%5Blevel-1-with-primary-path%5D/rx-850-ubuntu-driver-problems-34295

"
RX 580 Ubuntu Driver Problems
Wed, 05/31/2017 - 00:40 — Anonymous

I just got a pair of XFX RX 580 card and am having some trouble with the
amdgpu-pro drivers.

On a fresh install of Ubuntu 16.04.2, after updating packages, updating
the kernel to 4.8, installing the AMDGPU-PRO 17.10 drivers, and
rebooting, I see these messages in the log

"
Maybe it's been patched in more recent ubuntu versions.

The goal is to work around the bug in firmware so people who run older
linuxes / unpatched don't get hit. Anything to mitigate this overheating
issue either at the linux kernel or firmware is a good move.

He used 16.04.2 without a kernel update from the CD.

But Ubuntu 16.04.2 has other problems
znmeb commented on 2017-12-04 23:05

This software doesn't even work on Ubuntu 16.04.3 LTS, which AMD
supposedly supports!! See http://support.amd.com/en-us/kb-articles/Pages
/AMDGPU-PRO-Driver-Compatibility-Advisory-with-
Ubuntu-16.04.2-and-16.04.3.aspx

I couldn't even make it work on 16.04.2. I've pretty much given up on AMD.
But could be that Maybe they are putting the spin on the powerplay issue as
something else. Remember AMDGPU-Pro isn't reconmended for most of the AMD GPU
chipsets you sell. AmdGPU "all open" they also bundle with ubuntu is just
their own unmodified but compiled version pure opensource amdgpu.ko kernel
driver, linux-firmware for the polaris10-11, mesa opengl - vaapi etc

You want to do your testing on VANILLA Linux kernels. I .e. learn how to
compile a vanilla kernel in ubuntu or use vanilla kernel source. That's what
all the other non-ubuntu linux distributions are using.

They have ready pre-cooked ones for you here:

https://wiki.ubuntu.com/Kernel/MainlineBuilds

Does it break with any of the < 4.14 Linux kernels from there? Maybe
Ubuntu's patched it already. I'll have a quick look on their bug tracker
to see if I can find it.

<10 mins later >

Hey... I just found someone else yet again who video card was
crashing Who was running Ubuntu... who had no fan control.. Using
the ubuntu bug database. I told you it's a global problem. All these
errors with the video cards crashing at high res, in games in videos etc
is OVERHEATING issues being reported to linux bugtrackers as "software
issues". It's a mess...

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

Look at the dmesg.txt attached to that bug... the error message I kept raving
about about powerplay votlage tables...
https://launchpadlibrarian.net/351532328/CurrentDmesg.txt

He's also got EFI firmware from AMI like you guys use, but not an MSI
card. It's AMI EFI firmware + messed voltage tables + linux kernel =
dead powerplay no fan control I think.

That's me searching the UBUNTU bugs database for 10 mins guys so you
know it's real. Try using an older motherboard like the same as mine
with OLDER AMI EFI bios driver version. That EFI version will be right
at the top of the dmesg. Details

[Touch-packages] [Bug 1667958] Re: Mouse becomes erratiic after a while

2018-01-24 Thread Romain Jolivot

Hello,

I have the same kind of probleme.

After a variable time, when I left click on blank space or on a link in
a browser, I'm redirecting to the previous page.

Happen on Firefox and Chrome.

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

Title:
  Mouse becomes erratiic after a while

Status in xorg package in Ubuntu:
  New

Bug description:
  Standard external usb mouse, after the system has been up for a variable 
time, sometimes a few hours sometimes 2 days the mouse does not properly move 
around the screen and it also does not properly respond to right and left 
click, it will take many attempts before the button presses are recognised.
  A reboot does fix it, but it should not need rebooting so often.

  xorg was used because it seems to be the xorg mouse drivers that are
  in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-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: Sat Feb 25 18:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Skylake Integrated Graphics 
[1458:d000]
  InstallationDate: Installed on 2016-05-03 (297 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=4db7fc40-87b9-494c-8c02-5b4c4ff8abc8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5j
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  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.:bvrF5j:bd01/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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: Thu Feb 23 07:57:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   30934 
   vendor BNQ
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1667958/+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 1710863] Re: Question dialog showing "text" as the question.

2018-01-24 Thread guysoft

The bug was ignored for 4 months and then closed after EOL of Ubuntu
17.04. Its quite likely that it still exists in 17.10+

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

Title:
  Question dialog showing "text" as the question.

Status in apport package in Ubuntu:
  Invalid

Bug description:
  Screenshot that would not disappoint "thedailywtf.com"
  When running apport-collect 1706052,
  After authenticating, I got the following dialog on the screen.
  Just in order to report the bug to #1706052 , I selected "Yes", and you can 
see all the stuff it uploaded to that bug.

  Using Kubuntu 17.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1710863/+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] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)

2018-01-24 Thread Luis Alvarado

Hi Daniel, thank you. How can I mark this ticket as fixed. It has been
about 10 days. No problems whatsoever. I actually lost connection
yesterday but then noticed it was because I did not charge the headset
for the last 2 days. Even with very low power, I was still able to
finish a conversation. Thank you for the help and if you would like as a
gift, I could buy one of this in Amazon and send it to you buddy. They
are pretty awesome. Big hugs friend and think positive.

--
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 drops connection and reconnects in 17.10 (But not in
17.04)

Status in linux package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete

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/linux/+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 : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

2018-01-24 Thread Steve Langasek

** Changed in: util-linux (Ubuntu Xenial)
   Status: Incomplete => Triaged

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Triaged
Status in util-linux source package in Xenial:
  Triaged

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
  [6.017666150,7] HBRT: Calling

[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd

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

** Changed in: systemd (Ubuntu Xenial)
   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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1737570] Re: Add support for RequiredForOnline in networkd

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

** Changed in: systemd (Ubuntu Zesty)
   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/1737570

Title:
  Add support for RequiredForOnline in networkd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Confirmed
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  In Progress
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  Add support for RequiredForOnline in networkd

  
https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be

  RequiredForOnline= denotes a link/network that does/does not require being up
  for systemd-networkd-wait-online to consider the system online; this makes it
  possible to ignore devices without modifying parameters to wait-online.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+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 1743015] Re: Support for SystemD 236+ in 18.04

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

Title:
  Support for SystemD 236+ in 18.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  SystemD 236+ seems to add support for writing to files from unit
  definitions based on https://github.com/systemd/systemd/pull/7198.
  This is very helpful when migrating legacy logging integrations from
  14.04/upstart which is already writing to separate files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1743015/+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 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

2018-01-24 Thread Marc Deslauriers

You're welcome!

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

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

2018-01-24 Thread Jan Martinec

Was working in Ubuntu 17.04, broken after upgrade to 17.10, installing
signon-ui from the PPA
(0.17+17.10.20171027+really20160406-0ubuntu1~ppa1) resolved this for me.

-- 
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 1745132] [NEW] Unable to change curl cipher (ECDHE_RSA_AES_256_GCM_SHA384 is always used)

2018-01-24 Thread Matteo Ferrabone

Public bug reported:

I was doing some tests with curl and libcurl and needed to change the ciphers 
list. 
I tried different ciphers as in the following example:
curl -v --ciphers AES256-SHA256 https://test.com

No matter what, ECDHE_RSA_AES_256_GCM_SHA384 was always used.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: curl 7.50.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
Uname: Linux 4.8.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Jan 24 11:35:42 2018
InstallationDate: Installed on 2017-02-10 (347 days ago)
InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: curl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Unable to change curl cipher (ECDHE_RSA_AES_256_GCM_SHA384 is always
  used)

Status in curl package in Ubuntu:
  New

Bug description:
  I was doing some tests with curl and libcurl and needed to change the ciphers 
list. 
  I tried different ciphers as in the following example:
  curl -v --ciphers AES256-SHA256 https://test.com

  No matter what, ECDHE_RSA_AES_256_GCM_SHA384 was always used.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: curl 7.50.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jan 24 11:35:42 2018
  InstallationDate: Installed on 2017-02-10 (347 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  SourcePackage: curl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1745132/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs

** Merge proposal linked:
   
https://code.launchpad.net/~juliank/ubuntu/+source/multipath-tools/+git/multipath-tools/+merge/336526

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

Title:
  dm-queue-length module is not included in installer/initramfs

Status in hw-detect package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in hw-detect source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in multipath-tools source package in Xenial:
  Fix Released
Status in hw-detect source package in Yakkety:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Invalid
Status in linux source package in Yakkety:
  Fix Released
Status in multipath-tools source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Multipath users using EMC XtremIO storage as boot device or at install time 
may run into this issue. With the module unavailable the device is more often 
than not unavailable. Any users changing path selector to 'queue-length' with 
other storage devices may also be affected.

  [Test case]
  1) Install on multipath system using EMC XtremIO storage / OR:
   a) Start d-i install on qemu with multipath enabled
   b) exit to d-i menu
   c) modify /etc/multipath.conf to define path selector as 'queue-length' for 
the local qemu device.
   d) restart multipathd if necessary.
  2) Try to complete the install, setting up storage as multipath and using the 
multipath device as boot disk.
  3) Reboot to disk.

  In a success case, the install should complete successfully without
  requiring manual configuration from the user to support the multipath
  storage past the normal detection of multipath and partitioning.

  In a failure case, the install may not complete, or rebooting may fail
  or lead to a system booted on a single path of the multipath device
  (ie. / on /dev/sda2 rather than /dev/mpatha2).

  [Regression Potential]
  The inclusion of a new multipath path selector driver should not cause any 
regressions, but any failure to detect, configure or boot on multipath devices 
following this change on XtremIO hardware or otherwise would constitute a 
regression potentially caused by this change.

  ---

  ---Problem Description---
  dm-queue-length module is not included in installer/initramfs

  On Ubuntu, multipath devices using the 'queue-length' path selector
  are non-functional on both the installer and initramfs environments;
  because the 'dm-queue-length' kernel module is not included in them.

  The multipath-modules.udeb (src:linux) does not include it in the installer,
  nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs.

  One example is the EMC XtremIO storage, which has 'queue-length' defined as
  its path selector in the default multipath configuration, at least on 16.04.

  Other products may be affected if they are manually configured to use that
  path selector (e.g., via /etc/multipath.conf), and the mere switch of that
  might render the system _unbootable_ if booting from multipath, since the
  initramfs is affected.

  More recently this and another storage changed default path selectors out
  of 'queue-length', however, it's virtually possible for any storage system
  to be affected, with the described manual configuration change.  So, this
  change is also desired on for the next stable release, 17.04, and later.

  Patches are provided for 16.04 and 17.04.

  Error logs in LP comment #6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1732172] Re: [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

2018-01-24 Thread Amit Khulbe

Marc thanks so much for quickly fixing this. I really appreciate this.

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

Title:
  [CVE] Security Vulnerabilities in OpenSSH on Ubuntu 14.04

Status in openssh package in Ubuntu:
  Fix Released

Bug description:
  Does anyone know when the following OpenSSH venerabilities will be
  patched on Ubuntu 14.04

  CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012,
  CVE-2016-8858

  As these are coming up repeatedly on or security scans

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1732172/+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 1742946] Re: "gio monitor" does not work

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: glib2.0 (Ubuntu)
   Status: New => Confirmed

** Changed in: glib2.0 (Ubuntu)
   Importance: Medium => High

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

Title:
  "gio monitor" does not work

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  # ls -l /etc/adduser.conf
  -rw-r--r-- 1 root root 2981 Mar 11  2012 /etc/adduser.conf
  # gio monitor file:///etc/adduser.conf
  gio: No locations given

  Usage:
gio monitor [OPTION…] [LOCATION...]

  Monitor files or directories for changes.

  Options:
-d, --dir=LOCATIONMonitor a directory (default: depends on type)
-f, --file=LOCATION   Monitor a file (default: depends on type)
-D, --direct=LOCATION Monitor a file directly (notices changes made via 
hardlinks)
-s, --silent=LOCATION Monitors a file directly, but doesn’t report 
changes
-n, --no-movesReport moves and renames as simple 
deleted/created events
-m, --mounts  Watch for mount events

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libglib2.0-bin 2.54.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Fri Jan 12 14:29:42 2018
  InstallationDate: Installed on 2012-03-12 (2131 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120311)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1742946/+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 1743029] Re: glib-pacrunner assert failure: * Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 0x00007f01e80177d0 *

** Description changed:

  please solve this bug
+ 
+ 
+ errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
-  __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
-  malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
-  _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
-  __GI___libc_free (mem=) at malloc.c:3144
-  ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
+  __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
+  malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
+  _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
+  __GI___libc_free (mem=) at malloc.c:3144
+  ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Changed in: glib-networking (Ubuntu)
   Importance: Medium => High

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

Title:
  glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking
  /glib-pacrunner': double free or corruption (!prev):
  0x7f01e80177d0 ***

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  please solve this bug

  
  errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1743029/+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 1743029] Re: glib-pacrunner assert failure: * Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 0x00007f01e80177d0 *

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

** Changed in: glib-networking (Ubuntu)
   Status: New => Confirmed

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

Title:
  glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking
  /glib-pacrunner': double free or corruption (!prev):
  0x7f01e80177d0 ***

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  please solve this bug

  
  errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1743029/+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 1745125] Re: /usr/lib/glib-networking/glib-pacrunner:* Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (out): ADDR *

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

** This bug has been marked a duplicate of bug 1743029
   glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***

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

Title:
  /usr/lib/glib-networking/glib-pacrunner:*** Error in `/usr/lib/glib-
  networking/glib-pacrunner': double free or corruption (out): ADDR ***

Status in glib-networking package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1745125/+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 1745125] [NEW] /usr/lib/glib-networking/glib-pacrunner:* Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (out): ADDR *

2018-01-24 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

** Affects: glib-networking (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic kylin-17.10 trusty xenial zesty

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

Title:
  /usr/lib/glib-networking/glib-pacrunner:*** Error in `/usr/lib/glib-
  networking/glib-pacrunner': double free or corruption (out): ADDR ***

Status in glib-networking package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1745125/+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 1743029] Re: glib-pacrunner assert failure: * Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 0x00007f01e80177d0 *

** Information type changed from Private to Public

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

Title:
  glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking
  /glib-pacrunner': double free or corruption (!prev):
  0x7f01e80177d0 ***

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  please solve this bug

  
  errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1743029/+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 1745044] Re: [Ubuntu 18.04] Screen not recorded by Chrome recording extensions

Thanks for your report. This is intended and a security feature of
wayland. Meanwhile you can select 'Ubuntu on Xorg' in the logging screen
to start xorg instead and screen capture applications should work.

** Tags removed: wayland-session
** Tags added: wayland

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

** Changed in: wayland (Ubuntu)
   Importance: Undecided => Medium

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

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

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

Title:
  [Ubuntu 18.04] Screen not recorded by Chrome recording extensions

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Not sure I report this correctly.
  Since updating to 18.04, all chrome extensions capturing the desktop (es. 
Awesome Screenshot and Screencastify) don't work anymore.
  They capture just a black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 23:27:50 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: webcamstudio, 0.73, 4.14.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 520 [17aa:5053]
  InstallationDate: Installed on 2015-12-07 (778 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 005: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FMS1G400
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.14.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET42W (1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FMS1G400
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET42W(1.16):bd09/20/2016:svnLENOVO:pn20FMS1G400:pvrThinkPadT460:rvnLENOVO:rn20FMS1G400:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460
  dmi.product.name: 20FMS1G400
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  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.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Jan 11 19:43:07 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1745044/+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 1745044] Re: [Ubuntu 18.04] Screen not recorded by Chrome recording extensions