[Touch-packages] [Bug 2037794] [NEW] [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at all

[Jose Miguel Sanchez Vargas]

Public bug reported:

Not sound at all

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 30 15:00:02 2023
InstallationDate: Installed on 2023-08-28 (33 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: UX482EA.311
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX482EA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX482EA_UX482EA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

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

Title:
  [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Not sound at all

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 30 15:00:02 2023
  InstallationDate: Installed on 2023-08-28 (33 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook UX482EA_UX482EA, Realtek ALC294, Speaker, Internal] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UX482EA.311
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX482EA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX482EA.311:bd10/21/2021:br5.19:svnASUSTeKCOMPUTERINC.:pnZenBookUX482EA_UX482EA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX482EA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX482EA_UX482EA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2037794/+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 2026757] Re: dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

[Miguel Lavalle]

I'll bring it up in the next weekly Neutron meeting for visibility
purposes

** Changed in: neutron
   Importance: Undecided => Low

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

Title:
  dnsmasq on Ubuntu Jammy/Lunar crashes on neutron-dhcp-agent updates

Status in Ironic:
  New
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  The Ironic project's CI has been having major blocking issues moving
  to utilizing Ubuntu Jammy and with some investigation we were able to
  isolate the issues down to the dhcp updates causing dnsmasq to crash
  on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 7fff9bf416d0 error 5 in libc.so.6[7f21dd302000+195000]
  [235022.163362] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 

[Touch-packages] [Bug 1977916] [NEW] package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: tryin

[Miguel Cortez]

Public bug reported:

trying to install wine 7 version

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libdbus-1-3 1.12.16-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun  8 00:49:06 2022
DuplicateSignature:
 package:libdbus-1-3:1.12.16-2ubuntu2.2 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz]
 Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', 
which is different from other instances of package libapparmor1:i386
ErrorMessage: trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', 
which is different from other instances of package libdbus-1-3:i386
InstallationDate: Installed on 2022-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: dbus
Title: package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz 
usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is 
different from other instances of package libdbus-1-3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check package-conflict

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

Title:
  package libdbus-1-3 1.12.16-2ubuntu2.2 [modified:
  usr/share/doc/libdbus-1-3/NEWS.gz
  usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other
  instances of package libdbus-1-3:i386

Status in dbus package in Ubuntu:
  New

Bug description:
  trying to install wine 7 version

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libdbus-1-3 1.12.16-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun  8 00:49:06 2022
  DuplicateSignature:
   package:libdbus-1-3:1.12.16-2ubuntu2.2 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz usr/share/doc/libdbus-1-3/changelog.Debian.gz]
   Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from 
other instances of package libapparmor1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libdbus-1-3/NEWS.gz', which is different from other instances 
of package libdbus-1-3:i386
  InstallationDate: Installed on 2022-06-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: dbus
  Title: package libdbus-1-3 1.12.16-2ubuntu2.2 [modified: 
usr/share/doc/libdbus-1-3/NEWS.gz 
usr/share/doc/libdbus-1-3/changelog.Debian.gz] failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libdbus-1-3/NEWS.gz', which is 
different from other instances of package libdbus-1-3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1977916/+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 1977917] [NEW] package libxau6 1:1.0.9-0ubuntu1 [modified: usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to overwri

[Miguel Cortez]

Public bug reported:

trying to install wine 7 version

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Wed Jun  8 00:52:50 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0622]
InstallationDate: Installed on 2022-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. Inspiron 3847
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: libxau
Title: package libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/07/2019
dmi.bios.release: 65.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 088DT1
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/07/2019:br65.10:svnDellInc.:pnInspiron3847:pvr:rvnDellInc.:rn088DT1:rvrA01:cvnDellInc.:ct3:cvr:sku0622:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 3847
dmi.product.sku: 0622
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-package focal ubuntu

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

Title:
  package libxau6 1:1.0.9-0ubuntu1 [modified:
  usr/share/doc/libxau6/changelog.Debian.gz
  usr/share/doc/libxau6/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libxau6/changelog.Debian.gz', which
  is different from other instances of package libxau6:i386

Status in libxau package in Ubuntu:
  New

Bug description:
  trying to install wine 7 version

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libxau6 1:1.0.9-0ubuntu1 [modified: 
usr/share/doc/libxau6/changelog.Debian.gz usr/share/doc/libxau6/copyright]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Wed Jun  8 00:52:50 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libxau6/changelog.Debian.gz', which is different from other 
instances of package libxau6:i386
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0622]
  InstallationDate: Installed on 2022-06-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. Inspiron 3847
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: libxau
  Title: package 

[Touch-packages] [Bug 1977914] [NEW] package libapparmor1 2.13.3-7ubuntu5.1 [modified: usr/share/doc/libapparmor1/changelog.Debian.gz usr/share/doc/libapparmor1/copyright] failed to install/upgrade: t

[Miguel Cortez]

Public bug reported:

trying to install wine version 7

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libapparmor1 2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun  8 00:49:06 2022
DuplicateSignature:
 package:libapparmor1:2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright]
 Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', 
which is different from other instances of package libapparmor1:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from 
other instances of package libapparmor1:i386
InstallationDate: Installed on 2022-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: apparmor
Title: package libapparmor1 2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is 
different from other instances of package libapparmor1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check package-conflict

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

Title:
  package libapparmor1 2.13.3-7ubuntu5.1 [modified:
  usr/share/doc/libapparmor1/changelog.Debian.gz
  usr/share/doc/libapparmor1/copyright] failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different
  from other instances of package libapparmor1:i386

Status in apparmor package in Ubuntu:
  New

Bug description:
  trying to install wine version 7

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libapparmor1 2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun  8 00:49:06 2022
  DuplicateSignature:
   package:libapparmor1:2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright]
   Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from 
other instances of package libapparmor1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from 
other instances of package libapparmor1:i386
  InstallationDate: Installed on 2022-06-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-48-generic 
root=UUID=0522bd09-f431-472d-a066-6c45ce00f83c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: apparmor
  Title: package libapparmor1 2.13.3-7ubuntu5.1 [modified: 
usr/share/doc/libapparmor1/changelog.Debian.gz 
usr/share/doc/libapparmor1/copyright] failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', which is 
different from other instances of package libapparmor1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1977914/+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 1977915] [NEW] package libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to overwrite share

[Miguel Cortez]

Public bug reported:

trying to install wine version 7

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libbsd0 0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz 
usr/share/doc/libbsd0/copyright]
ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jun  8 00:49:06 2022
DuplicateSignature:
 package:libbsd0:0.10.0-1 [modified: usr/share/doc/libbsd0/changelog.Debian.gz 
usr/share/doc/libbsd0/copyright]
 Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
  trying to overwrite shared '/usr/share/doc/libapparmor1/changelog.Debian.gz', 
which is different from other instances of package libapparmor1:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other 
instances of package libbsd0:i386
InstallationDate: Installed on 2022-06-07 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: libbsd
Title: package libbsd0 0.10.0-1 [modified: 
usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other 
instances of package libbsd0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check package-conflict

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

Title:
  package libbsd0 0.10.0-1 [modified:
  usr/share/doc/libbsd0/changelog.Debian.gz
  usr/share/doc/libbsd0/copyright] failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libbsd0/changelog.Debian.gz', which
  is different from other instances of package libbsd0:i386

Status in libbsd package in Ubuntu:
  New

Bug description:
  trying to install wine version 7

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libbsd0 0.10.0-1 [modified: 
usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright]
  ProcVersionSignature: Ubuntu 5.13.0-48.54~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun  8 00:49:06 2022
  DuplicateSignature:
   package:libbsd0:0.10.0-1 [modified: 
usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright]
   Unpacking libapparmor1:i386 (2.13.3-7ubuntu5.1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-9whLYQ/04-libapparmor1_2.13.3-7ubuntu5.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libapparmor1/changelog.Debian.gz', which is different from 
other instances of package libapparmor1:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other 
instances of package libbsd0:i386
  InstallationDate: Installed on 2022-06-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: libbsd
  Title: package libbsd0 0.10.0-1 [modified: 
usr/share/doc/libbsd0/changelog.Debian.gz usr/share/doc/libbsd0/copyright] 
failed to install/upgrade: trying to overwrite shared 
'/usr/share/doc/libbsd0/changelog.Debian.gz', which is different from other 
instances of package libbsd0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1977915/+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 1932579] Re: snap pt_BR locale shows warning every time

[Miguel Pires]

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Miguel Pires (miguelpires1)

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time

[Miguel Pires]

Hi (or Olá for the PT crowd). I think snapd just wasn't refreshed,
@ioguis' output doesn't show it:

```
$ sudo snap install snapd --edge || sudo snap refresh snapd --edge
[sudo] senha para my-user:
2021/09/18 12:54:59.334587 main.go:176: description of prepare-image's 
"" is lowercase in locale "pt_BR": "o directório de destino"
snap "snapd" já está instalado, consulte 'snap help refresh'
```

`snap install ` (when run on an already installed snap) returns 0.
So the right-side of the `||` didn't run and snapd wasn't refreshed to
edge.

@iogui, can you run `sudo snap refresh snapd --edge` and let us know if
`snap list` logs the warning? I've just tested with edge and the fix
seems to be working. If you still see the warning, then could you please
run `snap version` and post the output? Thanks for your help

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

Title:
  snap pt_BR locale shows warning every time

Status in snapd:
  Fix Committed
Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1932579/+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 1882179] Re: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Miguel López]

I fixed this by running:

sudo apt purge lvm2

sudo apt install lvm2

But I wasn't using LVM and had no volumes set, so it wasn't risky for
me.

By the way, you could have run:

sudo apt install virt-manager

all the other packets you have expressly typed, with the exception of
bridge-utils, are dependencies or recommends, and will get installed no
matter what all those YouTube tutorials say.

I have no idea why lvm2 fails to install/upgrade though...

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

Title:
  package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I had run "sudo apt install qemu qemu-kvm libvirt-clients libvirt-
  daemon-system bridge-utils virt-manager", when this system problem
  detected error came. Please check it if it causes any issue.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  5 09:40:05 2020
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-08-17 (292 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: lvm2
  Title: package lvm2 2.03.07-1ubuntu1 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-08 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1882179/+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 1876018] [NEW] 40-vm-hotadd.rules attempts to set non-existent sysfs parameters

[Jose Miguel Parrella]

Public bug reported:

In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes resulting
in warnings such as:

Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
/usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
argument

Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
removed, or something else. This behavior is present on systems upgraded
from 18.04 (via d-r-u) as well as new focal systems, upon first reboot
of the VM.

udev: 245.4-4ubuntu3

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

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

Title:
  40-vm-hotadd.rules attempts to set non-existent sysfs parameters

Status in systemd package in Ubuntu:
  New

Bug description:
  In focal, udev's 40-vm-hotadd.rules (from debian/extra/rules-ubuntu)
  tries to write to invalid (as of 5.4.0-1010-azure) sysfs nodes
  resulting in warnings such as:

  Apr 29 22:36:46 focal01 systemd-udevd[266]: memory7:
  /usr/lib/udev/rules.d/40-vm-hotadd.rules:9 Failed to write
  ATTR{/sys/devices/system/memory/memory7/state}, ignoring: Invalid
  argument

  Perhaps 40-vm-hotadd.rules needs to be updated for 5.4 semantics,
  removed, or something else. This behavior is present on systems
  upgraded from 18.04 (via d-r-u) as well as new focal systems, upon
  first reboot of the VM.

  udev: 245.4-4ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876018/+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 1841420] [NEW] Xorg freeze

[Miguel Ângelo Leal Pereira]

Public bug reported:

Constant video freeze

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 26 10:17:38 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 anbox, 1, 4.15.0-55-generic, x86_64: installed
 anbox, 1, 4.15.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: I don't know
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:124d]
   Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
InstallationDate: Installed on 2018-08-20 (370 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. X550CC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Constant video freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 26 10:17:38 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-55-generic, x86_64: installed
   anbox, 1, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
  InstallationDate: Installed on 2018-08-20 (370 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. X550CC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1841421] [NEW] Xorg freeze

[Miguel Ângelo Leal Pereira]

Public bug reported:

Constant video freeze

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 26 10:17:38 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 anbox, 1, 4.15.0-55-generic, x86_64: installed
 anbox, 1, 4.15.0-58-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: I don't know
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:124d]
   Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
InstallationDate: Installed on 2018-08-20 (370 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: ASUSTeK COMPUTER INC. X550CC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.213
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.213:bd06/26/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Constant video freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 26 10:17:38 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-55-generic, x86_64: installed
   anbox, 1, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
  InstallationDate: Installed on 2018-08-20 (370 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. X550CC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-58-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550CC.213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550CC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1810840] Re: whoopsie can't remember "always report" setting

[Miguel Guedes]

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

Can confirm that on Ubuntu 18.04.2 LTS, whoopsie-preferences had not
previously been installed and I'm pretty sure I've not removed it.

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

Title:
  whoopsie can't remember "always report" setting

Status in whoopsie-preferences package in Ubuntu:
  Confirmed

Bug description:
  After ticking the checkbox for whoopsie to automatically always send
  crash reports, I get the following error dialog (screenshot attached):

  *Can't remember send report status settings*
  Saving crash report state failed. Can't set auto or never reporting mode.
  Command '['/usr/bin/gdbus', 'call', '-y', '-d', 
'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', 
'-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned
  non-zero exit status 1.

  I'm pretty sure this error happens because whoopsie-preferences was not 
installed; afterwards I installed whoopsie-preferences and manually ran in a 
terminal:
  $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o 
/com/ubuntu/WhoopsiePreferences -m 
com.ubuntu.WhoopsiePreferences.SetReportCrashes true

  and got a return value of () but no errors or warnings.

  This computer was freshly-installed with Xubuntu 18.04 less than 2
  weeks ago... I've kept a record of everything I changed since then,
  and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome-
  mines, pidgin, mousepad).  If whoopsie-preferences is not included in
  a fresh install of (X)ubuntu, then perhaps it should be; in any case,
  if it isn't installed then the checkbox for making crash reporting
  automatic should not be visible.

  
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy whoopsie
  whoopsie:
Installed: 0.2.62
Candidate: 0.2.62
Version table:
   *** 0.2.62 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy whoopsie-preferences 
  whoopsie-preferences:
Installed: (none)
Candidate: 0.19
Version table:
   0.19 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1810840/+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 1812095] Re: console login loop after entering username followed by RETURN

[Miguel Angel Blanco Muñpz]

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

Bug confirmed in Ubuntu 18.04.2 LTS with 4.15.0-45-generic kernel

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1803059] Re: Nullpointer dereference

[Miguel]

Thank you, the bug is fixed for me.

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1803059] Re: Nullpointer dereference

[Miguel]

Problem seems to be still present, possibly due to previous change.
Crashes when opening PDF files since last update in Ubuntu

** Changed in: poppler (Ubuntu)
   Status: Fix Committed => Confirmed

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Confirmed
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1803059] Re: Nullpointer dereference

[Miguel]

I am getting reproducible crashes after update from poppler
0.62.0-2ubuntu2.2 to poppler 0.62.0-2ubuntu2.4

Test PDF file attached.

Crashed experiences since following upgrades:
libpoppler-cpp-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-cpp0v5 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-glib8 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-private-dev (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler-qt5-1 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
libpoppler73 (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4
poppler-utils (0.62.0-2ubuntu2.2) to 0.62.0-2ubuntu2.4

Reverting to previous versions fixes the crashes.

System: 18.04.1 LTS bionic (32 bit)
Linux 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:10 UTC 2018 i686 i686 
i686 GNU/Linux
PC

gdb trace:
Starting program: /usr/bin/evince 
Bureau/evince/test_CGV_FORFAIT_hors_opt_20170308.pdf
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb5b82b40 (LWP 6602)]
[New Thread 0xb51ffb40 (LWP 6603)]
[New Thread 0xb47ffb40 (LWP 6604)]
warning: Error reading shared library list entry at 0x6840
warning: Error reading shared library list entry at 0x5a60
[New Thread 0xb3c77b40 (LWP 6608)]
warning: Error reading shared library list entry at 0x75e0
[New Thread 0xb1356b40 (LWP 6609)]
warning: Error reading shared library list entry at 0x5130
warning: Error reading shared library list entry at 0x97b0

Thread 6 "EvJobScheduler" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb1356b40 (LWP 6609)]
0xb096a379 in Parser::makeStream(Object&&, unsigned char*, CryptAlgorithm, int, 
int, int, int, bool) () from /usr/lib/i386-linux-gnu/libpoppler.so.73


** Attachment added: "With poppler 0.62.0-2ubuntu2.4, evince and other PDF 
readers will immediately crash on my system"
   
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+attachment/5220277/+files/test_CGV_FORFAIT_hors_opt_20170308.pdf

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

Title:
  Nullpointer dereference

Status in poppler package in Ubuntu:
  Fix Committed
Status in poppler source package in Bionic:
  Fix Released
Status in poppler source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  Evince segfaults on some pdf documents

  * Test case
  Download and try to open 
https://bugs.freedesktop.org/attachment.cgi?id=138927 with evince, it shouldn't 
segfault

  * Regression potential
  Nothing special to test, make sure evince still opens pdfs without issue

  -

  System Info: Linux zero 4.15.0-38-generic #41-Ubuntu SMP Wed Oct 10
  10:59:38 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  Evince version: GNOME Document Viewer 3.28.4

  While fuzzing evince v3.28.4, on linux 4.15.0-38-generic (Ubuntu 18.04
  LTS), a null-pointer dereference was observed, initially this was
  reported to evince but the evince team advised that the issue is in
  poppler, the library used by evince to render PDF, poppler version:
  0.62.0-2ubuntu2.2 is vulnerable to null-pointer dereference, however
  the issue is already fixed in poppler 0.70, but this will still crash
  your evince v3.28.4 in ubuntu if poppler is not updated to v.0.70.

  Fuzzing result showing a very important vulnerability in a package
  currently shipped by a major Linux distribution is still of interest,
  even if that Linux distribution does not package the latest released
  upstream version. I think Ubuntu is still using,

  Source: poppler
  Version: 0.62.0-2ubuntu2.2

  So, most of the systems will be affected to this issue.

  Upstream: https://gitlab.freedesktop.org/poppler/poppler/issues/664

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1803059/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

[José Miguel Sarasola]

Coming back from Pop!_OS 18.10 (Based on Ubuntu 18.10,
4.18.0-10-generic)

Still haven't tried with Audacity, but gnome-sound-recorded and Telegram
Desktop have been fixed in my case.

All I did this time was setting

default-sample-rate = 48000

on /etc/pulse/daemon.conf and restarting (Probably restarting pulseaudio
is enough).

before this, trying to send an audio recording through Telegram would
end in an "muted" audio. Now it's working perfectly.

You can try with arecord

arecord -f cd -d 10 test.wav -> For recording
aplay test.wav -> For playing (Probably gonna end up in noise)

arecord -f cd -d 10 -r 48000 test-mic.wav -> recording with the 48000
sample rate should provide good results

PD: Remember to increase a bit the mic volume from the sound settings

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

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in sound-2.6 (alsa-kernel):
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1764965/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

[José Miguel Sarasola]

Hi!

Asus Crosshair VI Hero here with Linux 4.15.0-33-generic on Pop!_OS
18.04 (Ubuntu based). This problem is also affecting me, but I could fix
it more or less. I'm using alsa for this specific device, so the audio
control center for gnome is still usable and the DisplayPort audio
(AMDGPU) is still working.

In my case all I needed to do was loading the module this way:

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

I found the corresponding device using the instructions from this web-
page:

https://frdmtoplay.com/gigabyte-front-panel-audio-with-linux/

It will make a duplicate entry on the audio input list of Gnome audio
settings, but now recording is working for me.

Once you try the command above and you verify it works, you can add it
to the default.pa file of pulse settings (/etc/pulse/default.pa or
~/.config/pulse/default.pa) and add it after the hardware detection (In
my case, line 58)

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
.endif

load-module module-alsa-source device=hw:1,2   < Add this line

Now with pulseaudio -k or restarting everything should be working
without needing to do anything

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

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in sound-2.6 (alsa-kernel):
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:

[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Miguel Prates]

Hi, I'm having the same problem with 18.04. 
The command "sudo kbd_mode -s" (scancode (RAW) mode) works fine as well as the 
"-k" argument (key code mode (MEDIUMRAW)) as well. As opposed, "-u" (UTF-8 
(UNICODE) mode) and "-a" (ASCII mode (XLATE)) arguments bring the bug back.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1779592] [NEW] I have video lagging errors

[Miguel Fernandez]

Public bug reported:

In browser (Chrome) and VLC.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  1 20:03:55 2018
DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3]
InstallationDate: Installed on 2018-04-21 (71 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: Dell Inc. Inspiron 5437
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago)
dmi.bios.date: 09/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0DM6M9
dmi.board.vendor: Dell Inc.
dmi.board.version: A04
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5437
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  I have video lagging errors

Status in xorg package in Ubuntu:
  New

Bug description:
  In browser (Chrome) and VLC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  1 20:03:55 2018
  DistUpgraded: 2018-04-29 10:40:39,012 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05f3]
  InstallationDate: Installed on 2018-04-21 (71 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Dell Inc. Inspiron 5437
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=86eb9f96-102c-4576-a37c-b2a420b78479 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-04-29 (63 days ago)
  dmi.bios.date: 09/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0DM6M9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A04
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd09/06/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DM6M9:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  

[Touch-packages] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

[Miguel Ibarra]

Hello

Also in xenial but in the apache log I found

Jun 20 10:44:05 localhost apache2: DIGEST-MD5 common mech free
Jun 20 10:44:53 localhost apache2: message repeated 22 times: [ DIGEST-MD5 
common mech free]

dpkg -l libsasl2-modules
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version Architecture
Description
+++-=-===-===-===
ii  libsasl2-modules:amd642.1.26.dfsg1-14buil amd64   Cyrus 
SASL - pluggable authentication modules

Cheers
Miguel

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Trusty:
  Triaged
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1771839] [NEW] keyboard

[Miguel Velasco Ortega]

Public bug reported:

The keyboard is desconfigurated for spanish.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-41-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May 17 10:03:40 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake Integrated Graphics [1028:06fb]
InstallationDate: Installed on 2017-04-21 (390 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: Dell Inc. Vostro 3250
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.5.2
dmi.board.name: 0J4NFV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
dmi.product.family: Vostro
dmi.product.name: Vostro 3250
dmi.product.version: X00
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu May 17 08:46:00 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputDP-1  HDMI-1
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  keyboard

Status in xorg package in Ubuntu:
  New

Bug description:
  The keyboard is desconfigurated for spanish.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu May 17 10:03:40 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06fb]
  InstallationDate: Installed on 2017-04-21 (390 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Dell Inc. Vostro 3250
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-generic.efi.signed 
root=UUID=dc72dcd9-c240-4235-8887-e0f5bbeb954c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.5.2
  dmi.board.name: 0J4NFV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.5.2:bd12/07/2017:svnDellInc.:pnVostro3250:pvrX00:rvnDellInc.:rn0J4NFV:rvrA01:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3250
  dmi.product.version: X00
  dmi.sys.vendor: Dell Inc.
  version.compiz: 

[Touch-packages] [Bug 1768001] [NEW] En Thinkpad T430 con controlador BCM20702A0

[Miguel]

Public bug reported:

loa dispositivos se intentan conectar y se conectan/desconectan
continuamente. Se hace inutilizable el bluetooth.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 30 13:26:49 2018
InstallationDate: Installed on 2018-04-27 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: LENOVO 2349I62
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b9f1f5f8-77c7-404e-92e8-a58f7bd5fa9e ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/25/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: G1ETB4WW (2.74 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2349I62
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349I62:pvrThinkPadT430:rvnLENOVO:rn2349I62:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430
dmi.product.name: 2349I62
dmi.product.version: ThinkPad T430
dmi.sys.vendor: LENOVO
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 74:E5:43:C5:85:87  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1196 acl:0 sco:0 events:88 errors:0
TX bytes:4095 acl:0 sco:0 commands:86 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  En Thinkpad T430 con controlador BCM20702A0

Status in bluez package in Ubuntu:
  New

Bug description:
  loa dispositivos se intentan conectar y se conectan/desconectan
  continuamente. Se hace inutilizable el bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 13:26:49 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349I62
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b9f1f5f8-77c7-404e-92e8-a58f7bd5fa9e ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349I62
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349I62:pvrThinkPadT430:rvnLENOVO:rn2349I62:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349I62
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:E5:43:C5:85:87  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1196 acl:0 sco:0 events:88 errors:0
TX bytes:4095 acl:0 sco:0 commands:86 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1768001/+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 1749662] [NEW] package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Miguel Angel Diaz]

Public bug reported:

apt upgrade
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias   
Leyendo la información de estado... Hecho
Calculando la actualización... Hecho
Se actualizarán los siguientes paquetes:
  libblkid1 libfdisk1 libmount1 libsmartcols1 libunity-control-center1 libuuid1 
libuuid1:i386 mount unity-control-center unity-control-center-faces util-linux 
uuid-runtime
12 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
1 no instalados del todo o eliminados.
Se necesita descargar 2.546 kB de archivos.
Se utilizarán 8.192 B de espacio de disco adicional después de esta operación.
¿Desea continuar? [S/n] s
Des:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 util-linux 
amd64 2.27.1-6ubuntu3.4 [849 kB]
Des:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 mount amd64 
2.27.1-6ubuntu3.4 [121 kB]
Des:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 uuid-runtime 
amd64 2.27.1-6ubuntu3.4 [26,1 kB]
Des:4 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 libuuid1 i386 
2.27.1-6ubuntu3.4 [16,3 kB]
Des:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libuuid1 amd64 
2.27.1-6ubuntu3.4 [15,2 kB]
Des:6 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libblkid1 
amd64 2.27.1-6ubuntu3.4 [107 kB]
Des:7 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libfdisk1 
amd64 2.27.1-6ubuntu3.4 [139 kB]
Des:8 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libmount1 
amd64 2.27.1-6ubuntu3.4 [114 kB]
Des:9 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libsmartcols1 
amd64 2.27.1-6ubuntu3.4 [62,8 kB]
Des:10 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libunity-control-center1 amd64 15.04.0+16.04.20171130-0ubuntu1 [81,1 kB]
Des:11 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center amd64 15.04.0+16.04.20171130-0ubuntu1 [835 kB]
Des:12 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
unity-control-center-faces all 15.04.0+16.04.20171130-0ubuntu1 [180 kB]
Descargados 2.546 kB en 2s (957 kB/s)
(Leyendo la base de datos ... 287355 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../util-linux_2.27.1-6ubuntu3.4_amd64.deb ...
Desempaquetando util-linux (2.27.1-6ubuntu3.4) sobre (2.27.1-6ubuntu3.3) ...
Procesando disparadores para ureadahead (0.100.0-19) ...
Procesando disparadores para man-db (2.7.5-1) ...
Procesando disparadores para mime-support (3.59ubuntu1) ...
Configurando util-linux (2.27.1-6ubuntu3.4) ...
insserv: Script lwsmd is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if empty.
insserv: warning: script 'K01GlassFish_aytohuelva' missing LSB tags and 
overrides
insserv: warning: script 'K01postgresql-9.4' missing LSB tags and overrides
insserv: Script likewise is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if empty.
insserv: Script lwsmd is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if empty.
insserv: Script likewise is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if empty.
insserv: Script likewise is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if empty.
insserv: Script lwsmd is broken: incomplete LSB comment.
insserv: missing `Provides:' entry: please add.
insserv: missing `Required-Start:' entry: please add even if empty.
insserv: missing `Required-Stop:'  entry: please add even if empty.
insserv: missing `Default-Start:'  entry: please add even if empty.
insserv: missing `Default-Stop:'   entry: please add even if 

[Touch-packages] [Bug 1718089] [NEW] package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: package libsystemd0:i386 is already installed and configured

[Miguel]

Public bug reported:

new ubunt installed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsystemd0:i386 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
Uname: Linux 4.4.0-96-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 600:0:116:482909:2017-09-18 22:16:02.783586740 -0400:2017-09-18 
22:16:03.783586740 -0400:/var/crash/libxau6:i386.0.crash
 600:0:116:482922:2017-09-18 22:16:02.615631103 -0400:2017-09-18 
22:16:03.615631103 -0400:/var/crash/libsystemd0:i386.0.crash
 640:0:116:112106:2017-09-18 16:17:02.395902395 -0400:2017-09-18 
16:17:03.395902395 -0400:/var/crash/_usr_sbin_cron.0.crash
 600:0:116:482919:2017-09-18 22:16:03.671616324 -0400:2017-09-18 
22:16:03.619630059 -0400:/var/crash/libjson-c2:i386.0.crash
Date: Mon Sep 18 22:16:02 2017
DuplicateSignature:
 package:libsystemd0:i386:229-4ubuntu19
 Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
 Rebuilding /usr/share/applications/bamf-2.index...
 dpkg: error processing package libsystemd0:i386 (--configure):
  package libsystemd0:i386 is already installed and configured
ErrorMessage: package libsystemd0:i386 is already installed and configured
InstallationDate: Installed on 2017-09-18 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: systemd
Title: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: 
package libsystemd0:i386 is already installed and configured
UpgradeStatus: Upgraded to xenial on 2017-09-18 (0 days ago)

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


** Tags: already-installed apport-package i386 xenial

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

Title:
  package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade:
  package libsystemd0:i386 is already installed and configured

Status in systemd package in Ubuntu:
  New

Bug description:
  new ubunt installed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libsystemd0:i386 229-4ubuntu19
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CrashReports:
   600:0:116:482909:2017-09-18 22:16:02.783586740 -0400:2017-09-18 
22:16:03.783586740 -0400:/var/crash/libxau6:i386.0.crash
   600:0:116:482922:2017-09-18 22:16:02.615631103 -0400:2017-09-18 
22:16:03.615631103 -0400:/var/crash/libsystemd0:i386.0.crash
   640:0:116:112106:2017-09-18 16:17:02.395902395 -0400:2017-09-18 
16:17:03.395902395 -0400:/var/crash/_usr_sbin_cron.0.crash
   600:0:116:482919:2017-09-18 22:16:03.671616324 -0400:2017-09-18 
22:16:03.619630059 -0400:/var/crash/libjson-c2:i386.0.crash
  Date: Mon Sep 18 22:16:02 2017
  DuplicateSignature:
   package:libsystemd0:i386:229-4ubuntu19
   Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
   Rebuilding /usr/share/applications/bamf-2.index...
   dpkg: error processing package libsystemd0:i386 (--configure):
package libsystemd0:i386 is already installed and configured
  ErrorMessage: package libsystemd0:i386 is already installed and configured
  InstallationDate: Installed on 2017-09-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: systemd
  Title: package libsystemd0:i386 229-4ubuntu19 failed to install/upgrade: 
package libsystemd0:i386 is already installed and configured
  UpgradeStatus: Upgraded to xenial on 2017-09-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718089/+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 1708500] [NEW] [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound at all. Rebooting does not fix & unmuting via alsamixer addresses the issue but audio plays

[Miguel Mendoza]

Public bug reported:

Rebooting does not fix & unmuting via alsamixer addresses the issue but
audio plays from internal speakers AND headphones

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
Uname: Linux 4.4.0-87-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
CurrentDesktop: Unity
Date: Thu Aug  3 10:28:03 2017
InstallationDate: Installed on 2015-09-29 (674 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
 /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
 /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
dmi.bios.date: 05/13/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 06HN6G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7450
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound
  at all. Rebooting does not fix & unmuting via alsamixer addresses the
  issue but audio plays from internal speakers AND headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Rebooting does not fix & unmuting via alsamixer addresses the issue
  but audio plays from internal speakers AND headphones

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug  3 10:28:03 2017
  InstallationDate: Installed on 2015-09-29 (674 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mmendoza   2636 F pulseaudio
   /dev/snd/pcmC1D0p:   mmendoza   2636 F...m pulseaudio
   /dev/snd/controlC1:  mmendoza   2636 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Latitude E7450, Realtek ALC3235, Green Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to xenial on 2016-10-01 (305 days ago)
  dmi.bios.date: 05/13/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 06HN6G
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd05/13/2015:svnDellInc.:pnLatitudeE7450:pvr01:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7450
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1708500/+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 1442896] Re: Bluetooth mouse disconnects and reconnects every few seconds

[Miguel Cumpa]

Hi, I use ubuntu 16.04 and I have the same problem. The bluetooth is 
disconnected and when I try to connect it manually I can not.
My laptop is a lenovo z470 and i have the same model of mouse genius traveler 
9005bt.

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Fri 2017-05-05 15:38:57 PET; 33min ago
 Docs: man:bluetoothd(8)
 Main PID: 18775 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
   └─18775 /usr/lib/bluetooth/bluetoothd

May 05 15:56:28 cumpa bluetoothd[18775]: Can't get HIDP connection info
May 05 15:56:33 cumpa bluetoothd[18775]: connect error: Host is down (112)


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

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

Title:
  Bluetooth mouse disconnects and reconnects every few seconds

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I have a bluetooth mouse (Genius Traveller 9005BT) that I have been
  using without problems with Ubuntu for over a year. Since a few weeks
  ago, however, it started disconnecting and reconnected from the
  computer. The symptoms are like this:

  1. The mouse works, and the bluetooth icon on the computer is visible (in 
gnome-shell's top bar)
  2. The mouse stops working, but the bluetooth icon is still visible. This 
state lasts between 1 and 10 seconds.
  3. The bluetooth icon vanishes. This can last for half a second if I keep 
trying to use the mouse, to forever I I leave the mouse alone
  4. The bluetooth icon reappears and the mouse starts working again. This 
state last from 2-3 seconds if I don't move the mouse, to seemingly forever if 
I continuously move the mouse

  This seems to occur only after a suspend/resume cycle, and rebooting
  the computer fixes the issue.

  The only thing I see in syslog is this when the mouse reconnects:
  Apr 11 10:03:10 tadzim3 kernel: [52026.494469] hid-generic 
0005:0458:0139.002F: unknown main item tag 0x0
  Apr 11 10:03:10 tadzim3 kernel: [52026.494540] input: Traveler 9005BT as 
/devices/pci:00/:00:14.0/usb2/2-4/2-4:1.0/bluetooth/hci0/hci0:512/0005:0458:0139.002F/input/input59
  Apr 11 10:03:10 tadzim3 kernel: [52026.494899] hid-generic 
0005:0458:0139.002F: input,hidraw3: BLUETOOTH HID v3.12 Mouse [Traveler 9005BT] 
on e8:2a:ea:8b:a5:5f

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Apr 11 09:49:37 2015
  InstallationDate: Installed on 2015-01-23 (77 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to utopic on 2015-01-31 (69 days ago)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: E8:2A:EA:8B:A5:5F  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:1873821 acl:123158 sco:0 events:2377 errors:0
TX bytes:29044 acl:238 sco:0 commands:218 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1442896/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Miguel Rubio-Roy]

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

Same problem after an upgrade from 16.04 to 16.10 via "do-release-upgrade". 
Ethernet and WiFi not managed.
Solved it creating blank file at 
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf
as per comment #6

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1674163] [NEW] imposibilidad de instalar una impresora

[Miguel Mateu]

Public bug reported:

Cada vez que intento instalarla marca error del sistema.
No admite otra forma de instalarla

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
 See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Mar 19 17:40:15 2017
DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
InstallationDate: Installed on 2016-11-12 (127 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 LANG=es_AR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic 
root=UUID=8bc8c59a-fb09-421e-99b0-9f139eff2ea1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-27 (81 days ago)
dmi.bios.date: 07/13/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: G41M-GS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/13/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnG41M-GS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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: Sun Mar 19 09:35:30 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 739 
 vendor SAM
xserver.version: 2:1.18.4-0ubuntu0.2

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


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

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

Title:
  imposibilidad de instalar una impresora

Status in xorg package in Ubuntu:
  New

Bug description:
  Cada vez que intento instalarla marca error del sistema.
  No admite otra forma de instalarla

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   [FAILED] Failed to start Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.7-usb1-1\x2d2).
   See 'systemctl status 
"udev-configure-printer@-devices-pci:00-:00:1d.7-usb1-1\\x2d2.service"' 
for details.
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Mar 19 17:40:15 2017
  DistUpgraded: 2016-12-27 18:52:03,292 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation 4 Series Chipset Integrated Graphics 
Controller [1849:2e32]
  

Re: [Touch-packages] [Bug 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks

[Miguel Fernandez]

sorry, I gave up and I gave the laptop to a family member who is going to
reinstall an OS.

Miguel

On 3 January 2017 at 11:42, Michael Mess <1603...@bugs.launchpad.net>
wrote:

> Can you check the password in network-manager view and edit it there?
>
> I think that the "wrong password - enter new"-dialog does not save the
> entered password and thus a reconnect with the old wrong password always
> fails.
> See also Bug #1542733 which I have experienced together with this one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603815
>
> Title:
>   after updating to ubuntu 16.04 the network manager is unable to
>   connect me to the wifi network. I can see the network, but once I
>   introduce the password, it asks me for the password after a few
>   seconds and never connects.
>
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   after updating to ubuntu 16.04 the network manager is unable to
>   connect me to the wifi network. I can see the network, but once I
>   introduce the password, it asks me for the password after a few
>   seconds and never connects. I use different devices connected to the
>   same wifi so it is not a problem of writting the wrong password.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: network-manager 1.1.93-0ubuntu4
>   ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
>   Uname: Linux 4.4.0-31-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Jul 17 16:58:17 2016
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2016-07-16 (1 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   IpRoute:
>default via 192.168.2.1 dev enp2s0  proto static  metric 100
>169.254.0.0/16 dev enp2s0  scope link  metric 1000
>192.168.2.0/24 dev enp2s0  proto kernel  scope link  src
> 192.168.2.242  metric 100
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   nmcli-con:
>NAME UUID  TYPE
>  TIMESTAMP   TIMESTAMP-REALAUTOCONNECT
> AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH
>  ACTIVE  DEVICE  STATE  ACTIVE-PATH
>Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13
> 802-3-ethernet   1468789026  dom 17 jul 2016 16:57:06 CDT  yes
> 4294966297no/org/freedesktop/NetworkManager/Settings/2
> yes enp2s0  activated  /org/freedesktop/NetworkManager/
> ActiveConnection/1
>BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6
> 802-11-wireless  0   never yes  0
>no/org/freedesktop/NetworkManager/Settings/1
> no  --  -- --
>   nmcli-dev:
>DEVICETYPE  STATE DBUS-PATH
>   CONNECTION   CON-UUID  CON-PATH
>enp2s0ethernet  connected /org/freedesktop/NetworkManager/Devices/1
> Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13
> /org/freedesktop/NetworkManager/ActiveConnection/1
>wlp3s0b1  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/0
> --   ----
>loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/2
> --   ----
>   nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit
> code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+
> subscriptions
>

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

Title:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and ne

[Touch-packages] [Bug 1652471] [NEW] package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[miguel]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.2
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
Date: Fri Dec 16 17:45:36 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2010-02-21 (2498 days ago)
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: dbus
Title: package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 package-from-proposed xenial

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

Title:
  package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in dbus package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Fri Dec 16 17:45:36 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2010-02-21 (2498 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1652471/+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 1651698] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Miguel Vega]

Public bug reported:

The pc freezes sometimes

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Wed Dec 21 01:09:25 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
FontConfigLog:
 /usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs
 /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
 /usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs
 /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
 /usr/share/fonts/X11/encodings/large: Bus error (core dumped)
InstallationDate: Installed on 2016-12-08 (12 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.15ubuntu0.2
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in fontconfig package in Ubuntu:
  New

Bug description:
  The pc freezes sometimes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Wed Dec 21 01:09:25 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  FontConfigLog:
   /usr/share/fonts: caching, new cache contents: 0 fonts, 5 dirs
   /usr/share/fonts/X11: caching, new cache contents: 0 fonts, 4 dirs
   /usr/share/fonts/X11/Type1: caching, new cache contents: 8 fonts, 0 dirs
   /usr/share/fonts/X11/encodings: caching, new cache contents: 0 fonts, 1 dirs
   /usr/share/fonts/X11/encodings/large: Bus error (core dumped)
  InstallationDate: Installed on 2016-12-08 (12 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1651698/+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 1639483] [NEW] cgange resolution

[Miguel Galindez]

Public bug reported:

After the last update sotware Submitted by ubuntu screen resolution of
800x600 and Change Every Time I boot ubuntu manually Fix 1024x768.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDmesg:
 [   34.778187] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [  826.163504] audit: type=1400 audit(1478367307.183:18): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2751 comm="apparmor_parser"
 [  826.163517] audit: type=1400 audit(1478367307.183:19): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2751 comm="apparmor_parser"
 [  826.164164] audit: type=1400 audit(1478367307.183:20): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2751 comm="apparmor_parser"
Date: Sat Nov  5 14:59:50 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. M4A785TD Motherboard [1043:83a2]
InstallationDate: Installed on 2015-11-14 (357 days ago)
InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic 
root=UUID=7bf112e5-6b74-44d0-8c32-7610a6b032b1 ro splash quiet plymouth:debug=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/25/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0506
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A785TD-V EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0506:bd11/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785TD-VEVO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sat Nov  5 14:21:57 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputPS/2+USB Mouse   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2~trusty3
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  cgange resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last update sotware Submitted by ubuntu screen resolution of
  800x600 and Change Every Time I boot ubuntu manually Fix 1024x768.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDmesg:
   [   34.778187] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [  826.163504] audit: type=1400 audit(1478367307.183:18): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" 
name="/usr/lib/cups/backend/cups-pdf" pid=2751 comm="apparmor_parser"
   [  826.163517] audit: type=1400 audit(1478367307.183:19): apparmor="STATUS" 
operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" 
pid=2751 comm="apparmor_parser"
   [  

[Touch-packages] [Bug 1638590] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Héctor Miguel Villa Loyola]

Public bug reported:

no

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 03:56:47 2016
DuplicateSignature:
 package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-04 (211 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check yakkety

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  no

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638590/+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 1638586] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status

[Héctor Miguel Villa Loyola]

Public bug reported:

no se instalo al actualizar version

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov  2 03:56:47 2016
DuplicateSignature:
 package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
 Cannot start click due to a conflict with a different locally-installed Python 
'click' package.  Remove it using Python packaging tools and try again.
 dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-04 (211 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

** Affects: unity-scopes-api (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check yakkety

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

Title:
  package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  no se instalo al actualizar version

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Nov  2 03:56:47 2016
  DuplicateSignature:
   package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2
   Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
   Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
   dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-04 (211 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: unity-scopes-api
  Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-11-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1638586/+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 1603815] [NEW] after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks m

[Miguel Fernandez]

Public bug reported:

after updating to ubuntu 16.04 the network manager is unable to connect
me to the wifi network. I can see the network, but once I introduce the
password, it asks me for the password after a few seconds and never
connects. I use different devices connected to the same wifi so it is
not a problem of writting the wrong password.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 17 16:58:17 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-16 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.2.1 dev enp2s0  proto static  metric 100 
 169.254.0.0/16 dev enp2s0  scope link  metric 1000 
 192.168.2.0/24 dev enp2s0  proto kernel  scope link  src 192.168.2.242  metric 
100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  802-3-ethernet   
1468789026  dom 17 jul 2016 16:57:06 CDT  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/2  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6  802-11-wireless  0  
 never yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --
nmcli-dev:
 DEVICETYPE  STATE DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
 enp2s0ethernet  connected /org/freedesktop/NetworkManager/Devices/1  
Conexión cableada 1  9e376788-1744-46de-a314-eeb07aad8c13  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp3s0b1  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--   ----   
  
 loloopback  unmanaged /org/freedesktop/NetworkManager/Devices/2  
--   ----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug xenial

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

Title:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects.

Status in network-manager package in Ubuntu:
  New

Bug description:
  after updating to ubuntu 16.04 the network manager is unable to
  connect me to the wifi network. I can see the network, but once I
  introduce the password, it asks me for the password after a few
  seconds and never connects. I use different devices connected to the
  same wifi so it is not a problem of writting the wrong password.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 17 16:58:17 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-16 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.2.1 dev enp2s0  proto static  metric 100 
   169.254.0.0/16 dev enp2s0  scope link  metric 1000 
   192.168.2.0/24 dev enp2s0  proto kernel  scope link  src 192.168.2.242  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE 
TIMESTAMP   

[Touch-packages] [Bug 1588303] Re: OTA 11 - Can't add new accounts

[Miguel]

Before I do: turn WIFI off/on, change timezone form auto to manual and back 
again to auto and reboot all accounts can't be created and don't sync.
After that, the account that is failing, ie, don't get data, is fitbit.

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

Title:
  OTA 11 - Can't add new accounts

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  After OTA 11 I can't add new accounts

  Device E4.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1588303/+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 1588303] Re: OTA 11 - Can't add new accounts

[Miguel]

Yes the device have the correct time zone.

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

Title:
  OTA 11 - Can't add new accounts

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  After OTA 11 I can't add new accounts

  Device E4.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1588303/+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 1588303] Re: OTA 11 - Can't add new accounts

[Miguel]

Hi Alberto,
Like I've answer to the mailing list:
This occurs after the upgrade to OTA 11

I turn WIFI off/on, change timezone form auto to manual and back again
to auto

reboot
Now can add accounts.

My activity now don't sync with fitbit.

Regards

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

Title:
  OTA 11 - Can't add new accounts

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  After OTA 11 I can't add new accounts

  Device E4.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1588303/+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 1582027] [NEW] package libssl-dev 1.0.2g-1ubuntu4.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libcrypto.a' to '/usr/lib/x86_64-linux-g

[Miguel]

Public bug reported:

i don't know why, was when i started my laptop

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl-dev 1.0.2g-1ubuntu4.1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri May 13 21:31:41 2016
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libcrypto.a' to 
'/usr/lib/x86_64-linux-gnu/libcrypto.a.dpkg-new': unexpected end of file or 
stream
InstallationDate: Installed on 2015-09-22 (236 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: openssl
Title: package libssl-dev 1.0.2g-1ubuntu4.1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libcrypto.a' to 
'/usr/lib/x86_64-linux-gnu/libcrypto.a.dpkg-new': unexpected end of file or 
stream
UpgradeStatus: Upgraded to xenial on 2016-04-22 (23 days ago)

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


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

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

Title:
  package libssl-dev 1.0.2g-1ubuntu4.1 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/x86_64-linux-gnu/libcrypto.a' to
  '/usr/lib/x86_64-linux-gnu/libcrypto.a.dpkg-new': unexpected end of
  file or stream

Status in openssl package in Ubuntu:
  New

Bug description:
  i don't know why, was when i started my laptop

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-dev 1.0.2g-1ubuntu4.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May 13 21:31:41 2016
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/libcrypto.a' to 
'/usr/lib/x86_64-linux-gnu/libcrypto.a.dpkg-new': unexpected end of file or 
stream
  InstallationDate: Installed on 2015-09-22 (236 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: openssl
  Title: package libssl-dev 1.0.2g-1ubuntu4.1 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/x86_64-linux-gnu/libcrypto.a' to 
'/usr/lib/x86_64-linux-gnu/libcrypto.a.dpkg-new': unexpected end of file or 
stream
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (23 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1582027/+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 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show

[Miguel]

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

This has happened to me after updating yesterday.

Recovered network access as per #2 instructions.

It's weird that this is happening to my system after several months.

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

Title:
  NetworkManager crashes after upgrade, preventing nm-applet to show

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps
  crashing.

  after `sudo service network-manager start` I get the following output
  in dmesg:

  [2016-01-31 14:28:47]  traps: NetworkManager[11040] general protection 
ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11040) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11049] general protection 
ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11049) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11062] general protection 
ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11062) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11076] general protection 
ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11076) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11088] general protection 
ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11088) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11092] general protection 
ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11092) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11096] general protection 
ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11096) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11100] general protection 
ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11100) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11104] general protection 
ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11104) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11108] general protection 
ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11108) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  init: network-manager main process (2) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager respawning too fast, stopped

  
  This problem prevents me to see nm-applet, and makes me unable to connect to 
WiFi network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+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 1441253] Re: hanging suspend job prevents shutdown

[Miguel A. Martinez]

Same problem here, Ubuntu 16.04 on dell xps 13 9350 4.4.0-21-generic

After a suspend I can not shutdown nor reboot, getting the error
mentioned.

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

Title:
  hanging suspend job prevents shutdown

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  poweroff (systemd poweroff) and reboot no longer work

  running sudo sytemd poweroff generates this:

  Failed to start poweroff.target: Transaction is destructive.

  journal log also shows:

  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 
[/usr/bin/pkttyagent --notify-fd 5 --fallback], object path 
/org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
  Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing 
jobs: Transaction is destructive.
  Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered 
Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, 
object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale 
en_US.UTF-8) (disconnected from bus)

  
  Output of systemctl list-jobs
   JOB UNITTYPE  STATE  
  6009 suspend.target  start waiting
  6010 systemd-suspend.service start running
  6014 anacron-resume.service  start waiting

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-6ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  Date: Tue Apr  7 18:32:27 2015
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic 
root=UUID=90fa42f5-708d-4432-9241-315b9c08ba98 ro nomodeset rootflags=subvol=@
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to vivid on 2015-03-02 (36 days ago)
  dmi.bios.date: 08/04/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.50
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.50:bd08/04/2014:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253/+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 1518928] [NEW] No Sound in Ubuntu 14.04

[Nuno Miguel Mendes Simão]

Public bug reported:

Hi all

I've just made a fresh install of Ubuntu 14.04.3 in a PC with the motherboard 
Asus Maximus VIII Gene. It has a Realtek Audio.
Can you please help me on this?

Thank you

The output of  'bash alsa-info.sh --stdout' is :

upload=true=true=
!!
!!ALSA Information Script v 0.4.64
!!

!!Script ran on: Thu Nov 19 13:09:03 UTC 2015


!!Linux Distribution
!!--

Ubuntu 14.04.3 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
14.04.3 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu
14.04.3 LTS" HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;


!!DMI Information
!!---

Manufacturer:  System manufacturer
Product Name:  System Product Name
Product Version:   System Version
Firmware Version:  1102


!!Kernel Information
!!--

Kernel release:3.19.0-33-generic
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: x86_64
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: k3.19.0-33-generic
Library version:1.0.27.2
Utilities version:  1.0.27.2


!!Loaded ALSA modules
!!---

snd_hda_intel
snd_usb_audio


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

 1 [NVidia ]: HDA-Intel - HDA NVidia
  HDA NVidia at 0xdf08 irq 17
 2 [U0x46d0x825]: USB-Audio - USB Device 0x46d:0x825
  USB Device 0x46d:0x825 at usb-:00:14.0-7, high speed


!!PCI Soundcards installed in the system
!!--

00:1f.3 Audio device: Intel Corporation Device a170 (rev 31)
01:00.1 Audio device: NVIDIA Corporation Device 0fb0 (rev a1)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:1f.3 0403: 8086:a170 (rev 31)
Subsystem: 1043:8691
--
01:00.1 0403: 10de:0fb0 (rev a1)
Subsystem: 3842:4995


!!Modprobe options (Sound related)
!!

snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2


!!Loaded sound module options
!!---

!!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
1,32,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
model : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
patch : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
position_fix : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
power_save : 0
power_save_controller : Y
probe_mask : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
probe_only : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
single_cmd : N
snoop : -1

!!Module: snd_usb_audio
autoclock : Y
device_setup : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
ignore_ctl_error : N
index : 
-2,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
pid : 

[Touch-packages] [Bug 1342400] Re: avahi-daemon constantly reporting "Invalid response packet from host"

[Miguel Rubio-Roy]

I confirm that the patch in https://github.com/lathiat/avahi/issues/10
solves the problem and returns calm to our logs.

apt-get source libavahi-core7
cd avahi-0.6.31
change avahi-core/server.c according to patch
apt-get build-dep libavahi-core7
debuild -b -uc -us
cd ..
dpkg -i libavahi-core7_0.6.31-4ubuntu4_amd64.deb
systemctl restart avahi-daemon

Please include this in any future update. It is very annoying.

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

Title:
  avahi-daemon constantly reporting "Invalid response packet from host"

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 14.04 (Release: 14.04) and looking for other
  information in /var/log/syslog, I see that syslog is being flooded by
  "Invalid response packet from host" messages from avahi-daemon.

  I searched around to see why this might be and ran across the following avahi 
mailing list post along with a patch to fix it:
  http://lists.freedesktop.org/archives/avahi/2012-July/002171.html

  >>>
  I would say you can safely ignore it, since any machine on your
  network running a recent OSX version will cause these messages.
  Here's a patch with what we change to avoid these messages flooding
  syslog.

  -Justin
  <<<

  The patch which fixes this is here:
  
http://lists.freedesktop.org/archives/avahi/attachments/20120719/1e71846e/attachment.obj

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400/+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 1411640] Re: Super+Space key shortcut for Unity's launcher not always works

[Miguel Rubio-Roy]

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

I've observed that Super+Space actually works when space is pressed
very rapidly after Super. The delay must not exceed roughly half a
second.

This bug is probably a duplicate of
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1245136
and
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1201679

** This bug has been marked a duplicate of bug 1201679
   ibus' Super+Space shortcut (usually) doesn't work

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

Title:
  Super+Space key shortcut for Unity's launcher not always works

Status in Unity:
  New
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  When using the Super+Space key shortcut to show the launcher of
  Unity, sometimes I need to press several times the key combination to
  get the desired action.

  I've changed the default key shortcut using the Unity Tweak Tool. If
  I use Super+Rkey the shortcut always works the first time.

  I've had this problem during a year, first with 13.10 and now with
  14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1411640/+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 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work

[Miguel Rubio-Roy]

In 15.04 I've observed that Super+Space actually works when Space is
pressed very rapidly after Super. The delay must not exceed roughly
half a second.

** Changed in: unity
   Status: Expired = Confirmed

** Changed in: unity (Ubuntu)
   Status: Expired = Confirmed

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

Title:
  ibus' Super+Space shortcut (usually) doesn't work

Status in One Hundred Papercuts:
  Expired
Status in Unity:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Expired
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  1. Add the ubuntu-desktop PPA on Ubuntu 13.10 Saucy
  sudo add-apt-repository ppa:ubuntu-desktop/ppa
  sudo apt-get update
  sudo apt-get upgrade
  sudo apt-get install indicator-keyboard
  2. Log out and log back in.
  2. Open System SettingsRegion  Language
  3. Switch to the Text Entry tab.
  4. Click the + button to add at least two more keyboard layouts.
  5. Log out and log back in.
  6. Try to use the (new) default Super+Space keyboard shortcut to switch 
between keyboard layouts.

  What happens
  ---
  Usually, Super+Space is ignored. It worked for me once on login but every 
other time I tested it didn't work.
  It works fine in GNOME Shell but not in Unity.

  gsettings reset org.gnome.settings-daemon.plugins.media-keys 
switch-input-source
  seems to be enough to nudge Unity into respecting the Super+Space keyboard 
shortcut.

  My guess is that Unity is too aggressive in binding the Super key to
  itself.

  Workaround
  -
  Shift+Super+Space, the keyboard shortcut to switch backward between keyboard 
layouts works.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.0.2+13.10.20130705.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Tue Jul 16 00:28:27 2013
  InstallationDate: Installed on 2013-06-14 (31 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1201679/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared

[Miguel Barrio Orsikowsky]

Compiz workaround also works for me: force full screen redraws (buffer swap) on 
repaint [x]
Ubuntu 14.04.1 fully updated
nVidia driver versión 346.35 (from xorg edgers PPA)
nVidia GeForce GTX 570

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

Title:
  Flickering with Ubuntu 14.04 and nvidia card reappeared

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  As requested in Bug #1310633 I'm opening a new bug.

  With a previous version of Ubuntu I already had this flickering. With
  additional options for the kernel module I was able to fix the
  flickering.

  options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x
  NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0

  With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the
  flickering reappeared although the line is still present in
  options.conf.

  Using modprobe --resolve-alias nvidia I found the correct driver
  module name which in my case is nvidia_331. Changing the module name
  in options.conf to nvidia_331 X doesn't start anymore. Removing the
  NVreg_ModifyDeviceFiles option X is starting again, but does not solve
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue Apr 29 21:09:41 2014
  DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1521]
  InstallationDate: Installed on 2012-11-17 (528 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 29 21:06:04 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+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 1376794] Re: aws ec2 two network cards

[Fernando Miguel]

apport information

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

** No longer affects: netcfg (Ubuntu)

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

** Tags added: apport-collected ec2-images trusty

** Description changed:

  aws ec2 t2.micro instance
  ubuntu server 14.04
  create two subnets on a VPC
  add two network cards to the VM
  add an ip for each subnet
  launch
  
  eth1 wont be enable on boot.
  adding /etc/network/interfaces.d/eth1.cfg 
  OR
  adding /etc/network/interfaces 
  auto eth1
  iface eth1 inet dhcp
  reboot
  
  *machine is unreachable*
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.4
+ Architecture: amd64
+ DistroRelease: Ubuntu 14.04
+ Ec2AMI: ami-2c90315b
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: eu-west-1a
+ Ec2InstanceType: t2.micro
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ Package: network
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
+ Tags:  trusty ec2-images
+ Uname: Linux 3.13.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/1376794/+attachment/4222584/+files/Dependencies.txt

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

Title:
  aws ec2 two network cards

Status in “ifupdown” package in Ubuntu:
  New
Status in “network” package in Ubuntu:
  New

Bug description:
  aws ec2 t2.micro instance
  ubuntu server 14.04
  create two subnets on a VPC
  add two network cards to the VM
  add an ip for each subnet
  launch

  eth1 wont be enable on boot.
  adding /etc/network/interfaces.d/eth1.cfg 
  OR
  adding /etc/network/interfaces 
  auto eth1
  iface eth1 inet dhcp
  reboot

  *machine is unreachable*
  --- 
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-2c90315b
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: network
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Tags:  trusty ec2-images
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1376794/+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 1361621] [NEW] gtk_label_set_line_wrap makes hello world application crash

[Miguel Tadeu]

Public bug reported:

Hi,

I'm testing a crash so I came up with this small application:

#include gtk/gtk.h

int main( int   argc, char *argv[] )
{
gtk_init (argc, argv);

GtkWidget *window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
gtk_signal_connect (GTK_OBJECT (window), destroy, 
GTK_SIGNAL_FUNC(gtk_main_quit), NULL);

GtkWidget *label = gtk_label_new(Referenced table has no candidate columns 
with a compatible type for group.groupcol.\nHint: source column has type 
VARCHAR(45),\nPK of referenced table is INT(11).);
gtk_label_set_line_wrap (GTK_LABEL(label), true);

gtk_container_add (GTK_CONTAINER (window), label);

gtk_widget_show (label);
gtk_widget_show  (window);

gtk_main ();

return 0;
}


I'm building using the following command:

 g++ main.cpp -o main `pkg-config --cflags --libs gtk+-2.0`

runnuing ./main will result in a crash

*** Error in `./main': malloc(): memory corruption: 0x01b169b0 ***
Aborted (core dumped)

Core dump is attached.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libgtk2.0-0 2.24.23-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Aug 26 12:43:45 2014
InstallationDate: Installed on 2013-06-04 (448 days ago)
InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
SourcePackage: gtk+2.0
UpgradeStatus: Upgraded to trusty on 2014-07-02 (55 days ago)

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


** Tags: amd64 apport-bug trusty

** Attachment added: core dump
   https://bugs.launchpad.net/bugs/1361621/+attachment/4187298/+files/core

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

Title:
  gtk_label_set_line_wrap makes hello world application crash

Status in “gtk+2.0” package in Ubuntu:
  New

Bug description:
  Hi,

  I'm testing a crash so I came up with this small application:

  #include gtk/gtk.h

  int main( int   argc, char *argv[] )
  {
  gtk_init (argc, argv);

  GtkWidget *window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
  gtk_signal_connect (GTK_OBJECT (window), destroy, 
GTK_SIGNAL_FUNC(gtk_main_quit), NULL);

  GtkWidget *label = gtk_label_new(Referenced table has no candidate 
columns with a compatible type for group.groupcol.\nHint: source column has 
type VARCHAR(45),\nPK of referenced table is INT(11).);
  gtk_label_set_line_wrap (GTK_LABEL(label), true);

  gtk_container_add (GTK_CONTAINER (window), label);

  gtk_widget_show (label);
  gtk_widget_show  (window);

  gtk_main ();

  return 0;
  }

  
  I'm building using the following command:

   g++ main.cpp -o main `pkg-config --cflags --libs gtk+-2.0`

  runnuing ./main will result in a crash

  *** Error in `./main': malloc(): memory corruption: 0x01b169b0 ***
  Aborted (core dumped)

  Core dump is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk2.0-0 2.24.23-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Aug 26 12:43:45 2014
  InstallationDate: Installed on 2013-06-04 (448 days ago)
  InstallationMedia: Kubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to trusty on 2014-07-02 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1361621/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared

[Miguel Ángel Molina]

Still not fixed in nvidia driver 340.32.
This issue doesn't occur with nouveau driver in 14.04.1 neither with nvidia 
driver and ubuntu 12.04.4

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

Title:
  Flickering with Ubuntu 14.04 and nvidia card reappeared

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  As requested in Bug #1310633 I'm opening a new bug.

  With a previous version of Ubuntu I already had this flickering. With
  additional options for the kernel module I was able to fix the
  flickering.

  options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x
  NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0

  With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the
  flickering reappeared although the line is still present in
  options.conf.

  Using modprobe --resolve-alias nvidia I found the correct driver
  module name which in my case is nvidia_331. Changing the module name
  in options.conf to nvidia_331 X doesn't start anymore. Removing the
  NVreg_ModifyDeviceFiles option X is starting again, but does not solve
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue Apr 29 21:09:41 2014
  DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1521]
  InstallationDate: Installed on 2012-11-17 (528 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 29 21:06:04 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared

[Miguel Ángel Molina]

The bug is not fixed in 340.24.

With 14.04.1 desktop 64b and this nvidia driver version the issue is
still there. I checked the Force full screen redraws (buffer swap) on
repaint option in compiz and this works for me.

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

Title:
  Flickering with Ubuntu 14.04 and nvidia card reappeared

Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  As requested in Bug #1310633 I'm opening a new bug.

  With a previous version of Ubuntu I already had this flickering. With
  additional options for the kernel module I was able to fix the
  flickering.

  options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x
  NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0

  With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the
  flickering reappeared although the line is still present in
  options.conf.

  Using modprobe --resolve-alias nvidia I found the correct driver
  module name which in my case is nvidia_331. Changing the module name
  in options.conf to nvidia_331 X doesn't start anymore. Removing the
  NVreg_ModifyDeviceFiles option X is starting again, but does not solve
  the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Tue Apr 29 21:09:41 2014
  DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1521]
  InstallationDate: Installed on 2012-11-17 (528 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 29 21:06:04 2014
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+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 1160638] Re: usb printer works intermittently after upgrade to Precise

[Miguel Gastelum]

I have three thermal receipt printers connected to Xubuntu 14.04 with
Model Generic / Text only driver when print command three jobs, one for
each printer, sometimes one or two printers stops are left with the job
without printing, and the queue print says that the printer is turned
off or disconnected.

If I send a new print job to the printer that has been standing prints
the job that had been printed and the new, but the new print was
incomplete.

This is used in a restaurant so that these errors can not happen.

And I hope you can help me with this problem.

CUPS Version:  cups 1.7.2-0ubuntu1  amd64

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

Title:
  usb printer works intermittently after upgrade to Precise

Status in “cups” package in Ubuntu:
  Fix Released

Bug description:
  I have a Canon MF4150 mono laser printer...was in use on Oneric with
  no problems.  Testing Precise (12.04) on another machine before
  cutting over  found printing problems with this printer.  Tried to
  research the issue but have not found a fix.

  When first powered up, the printer works fine initially.  After a few
  jobs, it stops working.  It appears that after the last successful
  job, the printer is left in a hung state...visible evidence is the
  Processing Data indicator on the printer remains on...forever.  In
  normal operation, this indicator goes off immediately after the last
  page of the job is completed.  Once in thsi state, the printer never
  prints again until power is cycled.

  However, while in this state, Cups still appears to send print jobs,
  but nothing actually prints.  The cups log indicates that cups is
  sending data to the printer in a sequence of transfers (8192 bytes
  each).  So cups apparently thinks the printer is accepting the job.
  I've compared the log sequence for jobs that print and jobs that don't
  and I can find no difference in the information reported in the cups
  log (at full debug level logging).

  The problem is unlikely to be related to drivers since the printer is
  operating in raw mode (the machine is a samba server for Windows
  printing clients).

  Have tried uni-directional constraint suggested in various places.
  This printer does not work at all if this option is applied.

  I have tried blacklisting the usblp module.  This does not solver the
  problem.

  Since it does not happen every time, it seems related to the sequence
  or timing of usb transactions.  Were there significant changes in usb
  behavior that would have affected raw printer handling between Oneric
  and Precise?

  Need to move forward from Oneric...printer testing is my last issue.
  Help would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu6
  ProcVersionSignature: Ubuntu 3.2.0-39.62-generic-pae 3.2.39
  Uname: Linux 3.2.0-39-generic-pae i686
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: i386
  Date: Tue Mar 26 19:05:11 2013
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  Lpstat:
   device for Canon_iP6000D: usb://Canon/iP6000D?serial=1020CF
   device for Canon_MF4100_Series: 
usb://Canon/MF4100%20Series?serial=SDF690291911Binterface=1
   device for Canon_MF4150_Linux: cnusb:/dev/usb/lp1
  MarkForUpload: True
  Papersize: letter
  PpdFiles: Canon_MF4150_Linux: Canon MF4100 Series UFRII LT ver.2.5
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-39-generic-pae 
root=UUID=350ae1ab-5bf6-44d2-b966-a72404d9a30c ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33FB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81072-306
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-306:cvn:ct3:cvr:
  mtime.conffile..etc.cups.cupsd.conf: 2013-03-24T23:56:10.278670

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1160638/+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 1046335] Re: USB Printer: some times the jobs are printed and some times not

[Miguel Gastelum]

I have three thermal receipt printers connected to Xubuntu 14.04 with
Model Generic / Text only driver when print command three jobs, one for
each printer, sometimes one or two printers stops are left with the job
without printing, and the queue print says that the printer is turned
off or disconnected.

If I send a new print job to the printer that has been standing prints
the job that had been printed and the new, but the new print was
incomplete.

CUPS Version:  cups 1.7.2-0ubuntu1  amd64

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

Title:
  USB Printer: some times the jobs are printed and some times not

Status in “cups” package in Ubuntu:
  Fix Released

Bug description:
  This is a Samsung ML-1860 laser monochromatic printer, attached at
  usb.

  The problem is: only some pages are printed. Example: I send 6 copies
  of some page to print but only 4 are actually printed. Or some times
  none of them. Rarely all of them are printed. If I disconnect from
  usb, then send the job and reconnect, the chance of get the print done
  is increased.

  More technical information:

  ~$ lsmod | grep usb
  usblp  18307  0

  ~$ tail -f /var/log/syslog
  Sep  5 10:42:54 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:42:54 desguai3 udev-configure-printer: Device already handled
  Sep  5 10:45:12 desguai3 wpa_supplicant[1135]: WPA: Group rekeying completed 
with 1c:7e:e5:46:5b:9d [GTK=TKIP]
  Sep  5 10:46:43 desguai3 kernel: [ 6539.488475] usb 2-1.1: USB disconnect, 
device number 9
  Sep  5 10:46:43 desguai3 kernel: [ 6539.488755] usblp0: removed
  Sep  5 10:46:43 desguai3 udev-configure-printer: remove 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:46:43 desguai3 udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:46:43 desguai3 udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:46:43 desguai3 udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1860-Series has matching device URI
  Sep  5 10:46:43 desguai3 udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/ML-1860-Series as the corresponding device was 
unplugged or turned off
  Sep  5 10:47:05 desguai3 kernel: [ 6560.789503] usb 2-1.1: new high-speed USB 
device number 10 using ehci_hcd
  Sep  5 10:47:05 desguai3 kernel: [ 6560.885528] usblp0: USB Bidirectional 
printer dev 10 if 0 alt 0 proto 2 vid 0x04E8 pid 0x330C
  Sep  5 10:47:05 desguai3 mtp-probe: checking bus 2, device 10: 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:47:05 desguai3 mtp-probe: bus: 2, device: 10 was not an MTP device
  Sep  5 10:47:05 desguai3 udev-configure-printer: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0
  Sep  5 10:47:05 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:47:05 desguai3 udev-configure-printer: Device vendor/product is 
04E8:330C
  Sep  5 10:47:05 desguai3 udev-configure-printer: add 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/usb/lp0
  Sep  5 10:47:05 desguai3 udev-configure-printer: failed to claim interface
  Sep  5 10:47:05 desguai3 udev-configure-printer: device devpath is 
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1
  Sep  5 10:47:05 desguai3 udev-configure-printer: MFG:Samsung MDL:ML-1860 
Series SERN:- serial:Z5M7BDAB501185X.
  Sep  5 10:47:06 desguai3 kernel: [ 6562.056195] usblp0: removed
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI contains USB serial 
number
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI match: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X.
  Sep  5 10:47:06 desguai3 kernel: [ 6562.061236] usblp0: USB Bidirectional 
printer dev 10 if 0 alt 0 proto 2 vid 0x04E8 pid 0x330C
  Sep  5 10:47:06 desguai3 udev-configure-printer: Consider also queues with 
/usb/lp0 or /usblp0 in their URIs as matching
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:47:06 desguai3 udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X., normalized: samsung ml 
1860 series serial z5m7bdab501185x
  Sep  5 10:47:06 desguai3 udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1860-Series has matching device URI
  Sep  5 10:47:06 desguai3 udev-configure-printer: Re-enabled printer 
ipp://localhost:631/printers/ML-1860-Series
  Sep  5 10:47:06 desguai3 udev-configure-printer: add