[Touch-packages] [Bug 2043524] Re: audio disappeared after upgrade to Ubuntu 23.10

[Pablo Fontoura]

Same thing  here. Fresh 23.10 installation and no sound. 
My USB headset is working properly.

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

Title:
  audio disappeared after upgrade to Ubuntu 23.10

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Ubuntu 23.10 from 23.04. Everything seems to work except
  there is no audio output on streaming functions. The external
  bluetooth speaker is connected and detected. It is charged and
  responds to testing. Just no sound when playing videos or podcasts.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  owner   975 F wireplumber
   /dev/snd/seq:owner   971 F pipewire
  CasperMD5CheckResult: fail
  CurrentDesktop: KDE
  Date: Tue Nov 14 17:50:17 2023
  InstallationDate: Installed on 2023-04-15 (213 days ago)
  InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-11-09 (5 days ago)
  dmi.bios.date: 07/04/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31/W8 (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV3.0:bd07/04/2012:br4.6:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2043524/+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 2025176] Re: External hard disk fails to automount in /etc/fstab with message FEATURE_C12

[Pablo]

I had built a 23.04 server just to explore the stuff that will be coming
with the next LTS. Shortly afterwards, I had hard drive failures on 2
22.04 LTS systems (both raid1). I decided to use the 23.04 server (also
raid1) for recovery. I created LV's with ext4 fs and copied over the
data from the degraded arrays. I tried to change the 23.04 network to
bridge using the exact procedure that worked flawlessly with 22.04. It
killed networking each time. So I installed 22.04 using the "keep
existing disk layout" method. I did not allow formatting of  the LV's
with data recovered from the degraded raid arrays. Things were looking
good after reboot until I added those volumes to /etc/fstab (with fsck
2nd pass option). On next reboot I discovered this bug. I think it could
be a showstopper for some folks. I now have all that data on volumes
that were reformatted with 22.04 LTS. When 23.10 is released I will
explore it on a VM carefully. I definitely will stick to LTS for backup
storage, nfs, etc. in the future. I think this bug should be assigned an
appropriate importance. I worked around the problem carefully but I can
see how it might cause panic and/or confusion for others and result in
loss of data.

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

Title:
  External hard disk fails to automount in /etc/fstab with message
  FEATURE_C12

Status in e2fsprogs package in Ubuntu:
  Confirmed

Bug description:
  I am having a problem with auto mounting an external 14TB 3.5" hard
  disk on Ubuntu 22.04 (arm64) (arm board). The drive is formatted using
  ext4 however this was done on a amd64 based Ubuntu 23.04 install
  (laptop).

  I tried to automount on the 22.04 install by using /etc/fstab, however
  the system would then fail to boot, entering emergency mode.

  Terminal output:
  [FAILED]: Failed to start File System Check on 
/dev/disk/by-uuuid/xx-xx-xx-xx-xx
  See 'systemctl status "systemd-fsck@dev-disk-by\\xx\\xx\\xx\\xx\\xx'
  [DEPEND] Dependency failed for /mnt/share/external_14tb_drive

  The particular error is:
  /dev/xxx has unsupported feature(s): FEATURE_C12

  /etc/fstab
  UUID=xx-xx-xx-xx-xx /mnt/share/external_14tb_drive ext4 
defaults,noatime,nofail  0   2

  arm board description:Ubuntu 22.04.2 LTS
  Release:  22.04

  apt-cache policy e2fsprogs
  e2fsprogs:
Installed: 1.46.5-2ubuntu1.1
Candidate: 1.46.5-2ubuntu1.1
Version table:
   *** 1.46.5-2ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 
Packages
  100 /var/lib/dpkg/status
   1.46.5-2ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages

  apt-cache policy util-linux
  util-linux:
    Installed: 2.37.2-4ubuntu3
    Candidate: 2.37.2-4ubuntu3
    Version table:
   *** 2.37.2-4ubuntu3 500
  500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
  100 /var/lib/dpkg/status

  Laptop description:   Ubuntu 23.04
  Release:  23.04

  apt-cache policy e2fsprogs
  e2fsprogs:
Installed: 1.47.0-1ubuntu1
Candidate: 1.47.0-1ubuntu1
Version table:
   *** 1.47.0-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  util-linux:
    Installed: 2.38.1-4ubuntu1
    Candidate: 2.38.1-4ubuntu1
    Version table:
   *** 2.38.1-4ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  The only option I have is to manually mount it after boot which is not
  convenient as it a server board.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: util-linux 2.37.2-4ubuntu3
  Uname: Linux 5.10.110-rockchip-rk3588 aarch64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue Jun 27 19:38:40 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2025176/+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 1991507] [NEW] Monitor does not turn on

[Pablo]

Public bug reported:

The main screen does not turn on after the monitors are turned off due
to energy saving (there is no video signal). The secondary screen turns
on correctly. It doesn't happen every time

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct  3 09:17:24 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
InstallationDate: Installed on 2022-09-26 (6 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
 Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
 Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP Z4D06EA#ABE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2019
dmi.bios.release: 2.27
dmi.bios.vendor: HP
dmi.bios.version: P01 Ver. 02.27
dmi.board.name: 8299
dmi.board.vendor: HP
dmi.board.version: KBC Version 06.21
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 6.33
dmi.modalias: 
dmi:bvnHP:bvrP01Ver.02.27:bd04/14/2019:br2.27:efr6.33:svnHP:pnZ4D06EA#ABE:pvr:rvnHP:rn8299:rvrKBCVersion06.21:cvnHP:ct3:cvr:skuZ4D06EA:
dmi.product.family: 103C_53307F HP EliteDesk
dmi.product.name: Z4D06EA#ABE
dmi.product.sku: Z4D06EA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Monitor does not turn on

Status in xorg package in Ubuntu:
  New

Bug description:
  The main screen does not turn on after the monitors are turned off due
  to energy saving (there is no video signal). The secondary screen
  turns on correctly. It doesn't happen every time

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 09:17:24 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8299]
  InstallationDate: Installed on 2022-09-26 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1c4f:00b0 SiGma Micro USB Optical Mouse
   Bus 001 Device 002: ID 03f0:2b4a HP, Inc Business Slim Keyboard
   Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP Z4D06EA#ABE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic 
root=UUID=f28d3bdb-0af0-4cbf-a682-38f39118cb88 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1900098] Re: software-properties-gtk fails to open with error

[Pablo]

I tried reinstalling all the packages, even the python ones and nothing
worked. So I read the code in /lib/python3/dist-
packages/softwareproperties/gtk/SoftwarePropertiesGtk.py and commenting
out line 222 everything worked again!!! self.backend.Reload(); --> #
self.backend.Reload();

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

Title:
  software-properties-gtk fails to open with error

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  When trying to open software-properties-gtk  via Terminal (via GUI:
  “Settings & Livepatch”) the following error is returned in the
  terminal and software-properties-gtk does not open.

  ERROR:dbus.proxies:Introspect error on :1.121:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
  self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.121 was not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.9.2
  ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65
  Uname: Linux 5.4.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 16 08:17:15 2020
  InstallationDate: Installed on 2020-10-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1900098/+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 1981622] Re: mtd device must be supplied (device name is empty)

[Pablo]

Hi, i'm getting same message with Ubuntu 22.04 fresh install but only at a new 
Thinkpad T14 (AMD 7pro, SSD M.2) with dual boot.
Also i can not suspend SO because when wake up crash with message:

EXT4-fs error (device nvme0n1p6): __ext4_find_entry:1612: inode #170139:
comm gmain: reading directory lblock 0

and

systemd-journald[403]: Failed to write entry (9 items, 326 bytes),
ignoring: Read-only file system

Just a blackscreen with this messages over and over. So the only option
i have is to force power-off.

With the old Thinkpad T430 (I5, SSD) Ubuntu 22.04 upgraded from 20.04
everything it's fine.

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1967625] [NEW] package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Pablo Arias]

Public bug reported:

I didn't notice an issue, just a popup window was appearing everytime
asking me to report this

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
Uname: Linux 5.14.0-1027-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Apr  2 11:51:35 2022
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-03-18 (15 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
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I didn't notice an issue, just a popup window was appearing everytime
  asking me to report this

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Apr  2 11:51:35 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-03-18 (15 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
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.14.0-1031-oem 5.14.0-1031.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1967625/+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 1903995] Re: upower report wrong battery percentage for Logitech Unify devices

[Pablo Catalina]

I recharged the mouse, but:

$ solaar show
Unifying Receiver
  Device path  : /dev/hidraw0
  USB id   : 046d:c52b
  Serial   : 23FF9429
Firmware   : 12.10.B0032
Bootloader : 02.15
Other  : AA.AA
  Has 3 paired device(s) out of a maximum of 6.
  Notifications: wireless (0x000100)
  Device activity counters: 1=70, 2=105

  1: Wireless Keyboard K270(unifying)
 Codename : K270(unifying)
 Kind : keyboard
 Wireless PID : 4003
 Protocol : HID++ 2.0
 Polling rate : 20 ms (50Hz)
 Serial number: 1A395FC1
  Firmware: RQK 35.00.B0017
 The power switch is located on the top case.
 Supports 12 HID++ 2.0 features:
 0: ROOT   {}   
 1: FEATURE SET{0001}   
 2: DEVICE FW VERSION  {0003}   
 3: DEVICE NAME{0005}   
 4: BATTERY STATUS {1000}   
 5: unknown:1820   {1820}   hidden
 6: REPROG CONTROLS{1B00}   
 7: WIRELESS DEVICE STATUS {1D4B}   
 8: unknown:1DF0   {1DF0}   hidden
 9: unknown:1DF3   {1DF3}   hidden
10: ENCRYPTION {4100}   
11: KEYBOARD LAYOUT{4520}   
 Has 8 reprogrammable keys:
 0: Play/Pause => Play/Pause
nonstandard
 1: Mute   => Mute  
nonstandard
 2: Volume Down=> Volume Down   
nonstandard
 3: Volume Up  => Volume Up 
nonstandard
 4: MY HOME=> HomePage  
nonstandard, reprogrammable
 5: Mail   => Email 
nonstandard, reprogrammable
 6: SLEEP  => Sleep 
nonstandard, reprogrammable
 7: Calculator => Calculator
nonstandard, reprogrammable
 Battery: 70%, discharging.

  2: Wireless Mouse MX Master
 Codename : MX Master
 Kind : mouse
 Wireless PID : 4071
 Protocol : HID++ 4.5
 Polling rate : 8 ms (125Hz)
 Serial number: F8EBBFD1
Bootloader: BOT 56.10.B0005
  Firmware: MPM 12.10.B0005
  Firmware: MPM 12.10.B0005
 Other: 
 The power switch is located on the base.
 Supports 32 HID++ 2.0 features:
 0: ROOT   {}   
 1: FEATURE SET{0001}   
 2: DEVICE FW VERSION  {0003}   
 3: DEVICE NAME{0005}   
 4: WIRELESS DEVICE STATUS {1D4B}   
 5: RESET  {0020}   
 6: unknown:0021   {0021}   
 7: BATTERY STATUS {1000}   
 8: unknown:1806   {1806}   internal, hidden
 9: CHANGE HOST{1814}   
10: REPROG CONTROLS V4 {1B04}   
11: ADJUSTABLE DPI {2201}   
12: VERTICAL SCROLLING {2100}   
Roller type: 3G
Ratchet per turn: 24
Scroll lines: 0
13: SMART SHIFT{2110}   
14: HIRES WHEEL{2121}   
Multiplier: 8
Has invert
  Normal wheel motion
Has ratchet switch
  Normal wheel mode
High resolution mode
HID notification
15: GESTURE 2  {6501}   
16: unknown:00C2   {00C2}   
17: unknown:1813   {1813}   internal, hidden
18: unknown:1830   {1830}   internal, hidden
19: unknown:1890   {1890}   internal, hidden
20: unknown:1891   {1891}   internal, hidden
21: unknown:18A1   {18A1}   internal, hidden
22: unknown:18C0   {18C0}   internal, hidden
23: unknown:1DF3   {1DF3}   internal, hidden
24: unknown:1E00   {1E00}   hidden
25: unknown:1EB0   {1EB0}   internal, hidden
26: unknown:1803   {1803}   internal, hidden
27: unknown:1861   {1861}   internal, hidden
28: unknown:9001   {9001}   internal, hidden
29: unknown:9200   {9200}   internal, hidden
30: unknown:9202   {9202}   internal, hidden
31: unknown:1805   {1805}   internal, hidden
 Has 8 reprogrammable keys:
 0: LEFT CLICK, default: LeftClick   => 
LEFT CLICK
 mse, pos:0, group:1, gmask:1
 1: RIGHT CLICK   , default: RightClick  => 
RIGHT CLICK   
 mse, pos:0, group:1, gmask:1
 2: MIDDLE BUTTON , default: MiddleMouseButton   => 
MIDDLE BUTTON 
 mse, reprogrammable, divertable, pos:0, group:3, gmask:7
 3: BACK AS BUTTON 4 

[Touch-packages] [Bug 1903995] [NEW] upower report wrong battery percentage for Logitech Unify devices

[Pablo Catalina]

Public bug reported:

The battery percentage reported by upower for Logitech devices connected
using Unify receiver are wrong.  Below are the results for two devices:
Mouse and Keyboard:

* Battery percentages reported by Unify receiver using Solaar:

$ solaar show  | grep -iP "^((  \d: )|(.*batt.*))"
  1: Wireless Keyboard K270(unifying)
 4: BATTERY STATUS {1000}
 Battery: 70%, discharging.
  2: Wireless Mouse MX Master
 7: BATTERY STATUS {1000}
 Battery: 20%, discharging.


* Battery percentages reported by upower:

$ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
  native-path:  hidpp_battery_0
  model:Wireless Keyboard K270
  serial:   4003-1a-39-5f-c1
  power supply: no
  updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
  has history:  yes
  has statistics:   yes
  keyboard
present: yes
rechargeable:yes
state:   discharging
warning-level:   none
battery-level:   normal
percentage:  55% (should be ignored)
icon-name:  'battery-low-symbolic'

$ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
  native-path:  hidpp_battery_1
  model:Wireless Mouse MX Master
  serial:   4071-f8-eb-bf-d1
  power supply: no
  updated:  Thu 12 Nov 2020 14:03:14 CET (27 seconds ago)
  has history:  yes
  has statistics:   yes
  mouse
present: yes
rechargeable:yes
state:   discharging
warning-level:   low
battery-level:   low
percentage:  10% (should be ignored)
icon-name:  'battery-caution-symbolic'


Basically the difference is big so I'm getting a lot of notifications
related to low battery even if the battery is OK:

* Mouse, upower: 10%real (Solaar): 20%
* Keyboard: upower: 70%real (Solaar): 55%


ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: upower 0.99.11-1build2
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
Uname: Linux 5.4.0-53-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 12 13:58:35 2020
InstallationDate: Installed on 2020-04-19 (206 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2020-06-17T11:02:56.934699

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


** Tags: amd64 apport-bug focal

** Description changed:

  The battery percentage reported by upower for Logitech devices connected
  using Unify receiver are wrong.  Below are the results for two devices:
  Mouse and Keyboard:
  
- 
  * Battery percentages reported by Unify receiver using Solaar:
  
  $ solaar show  | grep -iP "^((  \d: )|(.*batt.*))"
-   1: Wireless Keyboard K270(unifying)
-  4: BATTERY STATUS {1000}   
-  Battery: 70%, discharging.
-   2: Wireless Mouse MX Master
-  7: BATTERY STATUS {1000}   
-  Battery: 20%, discharging.
+   1: Wireless Keyboard K270(unifying)
+  4: BATTERY STATUS {1000}
+  Battery: 70%, discharging.
+   2: Wireless Mouse MX Master
+  7: BATTERY STATUS {1000}
+  Battery: 20%, discharging.
  
  
  * Battery percentages reported by upower:
+ 
  $ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
-   native-path:  hidpp_battery_0
-   model:Wireless Keyboard K270
-   serial:   4003-1a-39-5f-c1
-   power supply: no
-   updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
-   has history:  yes
-   has statistics:   yes
-   keyboard
- present: yes
- rechargeable:yes
- state:   discharging
- warning-level:   none
- battery-level:   normal
- percentage:  55% (should be ignored)
- icon-name:  'battery-low-symbolic'
+   native-path:  hidpp_battery_0
+   model:Wireless Keyboard K270
+   serial:   4003-1a-39-5f-c1
+   power supply: no
+   updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
+   has history:  yes
+   has statistics:   yes
+   keyboard
+ present: yes
+ rechargeable:yes
+ state:   discharging
+ warning-level:   none
+ battery-level:   normal
+ percentage:  55% (should be ignored)
+ icon-name:  'battery-low-symbolic'
  
- $ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1 
-   native-path:  hidpp_battery_1
-   model:Wireless Mouse MX Master
-   serial: 

[Touch-packages] [Bug 1902976] Re: [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Uninstalling pipewire fixed the issue. Now both the speakers and the
microphone work properly.

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

Title:
  [Acer Aspire E5-432] After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+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 1902976] [NEW] After boot pulseaudio needs to be restarted

[Pablo Pedrotti]

Public bug reported:

After an upgrade pulseaudio does not run properly after boot unless I
restart the service with the command systemctl --user restart
pulseaudio. Reinstalling the service with the comand apt-get install
--reinstall pulseaudio also solves the issue.

I am currently running Kubuntu 20.10 and the pulseaudio version is
1:13.99.2-1ubuntu2.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
  ppedrotti   5420 F pulseaudio
 /dev/snd/seq:ppedrotti   1567 F pipewire
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Nov  4 23:13:09 2020
InstallationDate: Installed on 2020-10-17 (18 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
dmi.bios.date: 12/07/2015
dmi.bios.release: 0.0
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.10
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Robin_BA
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.10
dmi.ec.firmware.release: 1.7
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
dmi.product.family: BSW
dmi.product.name: Aspire E5-432
dmi.product.sku: Aspire E5-432
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug groovy

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1902976/+attachment/5431303/+files/alsa-info.txt

** Attachment removed: "alsa-info.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+attachment/5431303/+files/alsa-info.txt

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

Title:
  After boot pulseaudio needs to be restarted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After an upgrade pulseaudio does not run properly after boot unless I
  restart the service with the command systemctl --user restart
  pulseaudio. Reinstalling the service with the comand apt-get install
  --reinstall pulseaudio also solves the issue.

  I am currently running Kubuntu 20.10 and the pulseaudio version is
  1:13.99.2-1ubuntu2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ppedrotti   1572 F pipewire-media-
ppedrotti   5420 F pulseaudio
   /dev/snd/seq:ppedrotti   1567 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov  4 23:13:09 2020
  InstallationDate: Installed on 2020-10-17 (18 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (12 days ago)
  dmi.bios.date: 12/07/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Robin_BA
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd12/07/2015:br0.0:efr1.7:svnAcer:pnAspireE5-432:pvrV1.10:rvnAcer:rnRobin_BA:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: BSW
  dmi.product.name: Aspire E5-432
  dmi.product.sku: Aspire E5-432
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902976/+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 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Pablo Pedrotti]

I also has this issue of losing audio and having to reinstall pulseaudio
to get it back to work. The latest pulseaudio update
(1:13.99.2-1ubuntu2) did not seem to solve the issue.


** Attachment added: "alsa-info"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5430501/+files/alsa-info.txt

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

Title:
  [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

  I have tried just killing the pulseaudio service, and letting it
  restart on it's own. It restarts, but no audio. Reinstalling seems to
  do the trick though.

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  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.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+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 1884595] [NEW] Bugged 3D display of multimaterial meshes after last Radeon driver update

[Pablo Roldán]

Public bug reported:

After the last driver update for my Radeon HD 7750 Im having viewport
problems in Blender when displaying meshes with multiple materials (see
attached screenshot).

This happens both with both the latest version of Blender snap and the direct 
download from Blender.org
I also have an older version installed and is having the same problem.

It all worked fine before the driver update.

Just in case these are the last lines from running  grep "upgrade " 
/var/log/dpkg.log
:

2020-06-20 00:48:38 upgrade xserver-xorg-legacy-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
2020-06-20 00:48:39 upgrade xserver-xorg-core-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
2020-06-20 00:48:40 upgrade xserver-xorg-video-amdgpu-hwe-18.04:amd64 
19.0.1-1ubuntu1~18.04.1 19.1.0-1~18.04.1
2020-06-20 00:48:40 upgrade xserver-xorg-video-radeon-hwe-18.04:amd64 
1:19.0.1-1ubuntu1~18.04.1 1:19.1.0-1~18.04.1
2020-06-20 00:48:41 upgrade xserver-xorg-video-ati-hwe-18.04:amd64 
1:19.0.1-1ubuntu1~18.04.1 1:19.1.0-1~18.04.1

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
Date: Mon Jun 22 16:31:31 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 openrazer-driver, 2.8.0, 5.3.0-53-generic, x86_64: installed
 openrazer-driver, 2.8.0, 5.3.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Cape Verde PRO [Radeon HD 7750/8740 / R7 
250E] [1043:0427]
InstallationDate: Installed on 2019-08-03 (324 days ago)
InstallationMedia: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=bf94f108-3b15-444b-a40a-414115dcfedd ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1107
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-M LX3 R2.0
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.:bvr1107:bd02/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
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

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


** Tags: amd64 apport-bug bionic corruption ubuntu

** Attachment added: "Screenshot."
   
https://bugs.launchpad.net/bugs/1884595/+attachment/5386190/+files/Captura%20de%20pantalla%20de%202020-06-22%2016-33-04.png

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

Title:
  Bugged 3D display of multimaterial meshes after last Radeon driver
  update

Status in xorg package in Ubuntu:
  New

Bug description:
  After the last driver update for my Radeon HD 7750 Im having viewport
  problems in Blender when displaying meshes with multiple materials
  (see attached screenshot).

  This happens both with both the latest version of Blender snap and the direct 
download from Blender.org
  I also have an older version installed and is having the same problem.

  It all worked fine before the driver update.

  Just in case these are the last lines from running  grep "upgrade " 
/var/log/dpkg.log
  :

  2020-06-20 00:48:38 upgrade xserver-xorg-legacy-hwe-18.04:amd64 
2:1.20.5+git20191008-0ubuntu1~18.04.1 2:1.20.8-2ubuntu2.1~18.04.1
  2020-06-20 00:48:39 upgrade 

[Touch-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[Pablo A. Garcia]

Previous issue (https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680)
was closed as duplicated of this one.

see https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680#note_328635.

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2134
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/2134

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1680
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/1680

** Changed in: mesa
   Status: Fix Released => Unknown

** Changed in: mesa
 Remote watch: gitlab.freedesktop.org/mesa/mesa/issues #1680 => 
gitlab.freedesktop.org/mesa/mesa/-/issues #2134

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1794033/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address

[Pablo A. Garcia]

Also facing this issue persistently, always when working with little
memory available (as #32).

My system: Dell XPS 13 9370 - Ubuntu 18.04.4 LTS

$ uname -a
Linux charon 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux


$ journalctl --since=-2w | grep -A1 'Failed to submit batchbuffer'
abr 27 17:17:09 charon org.gnome.Shell.desktop[3359]: i965: Failed to submit 
batchbuffer: Dirección incorrecta
abr 27 17:17:09 charon kernel: mce: CPU3: Core temperature above threshold, cpu 
clock throttled (total events = 2304)
--
abr 27 18:23:14 charon /usr/lib/gdm3/gdm-x-session[3239]: i965: Failed to 
submit batchbuffer: Bad address
abr 27 18:23:14 charon org.gnome.Shell.desktop[3359]: 
[9820:9820:0427/182314.955599:ERROR:chrome_browser_main_extra_parts_x11.cc(62)] 
X IO error received (X server probably went away)
--
abr 27 21:59:47 charon org.gnome.Shell.desktop[24418]: i965: Failed to submit 
batchbuffer: Dirección incorrecta
abr 27 21:59:48 charon org.gnome.Shell.desktop[24418]: 
[20630:20630:0427/215948.650070:ERROR:sandbox_linux.cc(374)] 
InitializeSandbox() called with multiple threads in process gpu-process.
--
abr 28 11:32:50 charon /usr/lib/gdm3/gdm-x-session[24313]: i965: Failed to 
submit batchbuffer: Bad address
abr 28 11:32:50 charon dropbox[24681]: dropbox: Fatal IO error 11 (Recurso no 
disponible temporalmente) on X server :0.
--
may 06 11:10:23 charon /usr/lib/gdm3/gdm-x-session[6485]: i965: Failed to 
submit batchbuffer: Bad address
may 06 11:10:23 charon org.gnome.Shell.desktop[6634]: 
[8456:8456:0506/111023.129635:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!
--
may 08 11:07:53 charon /usr/lib/gdm3/gdm-x-session[6255]: i965: Failed to 
submit batchbuffer: Bad address
may 08 11:07:53 charon dropbox[6661]: dropbox: Fatal IO error 11 (Recurso no 
disponible temporalmente) on X server :0.

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

Title:
   i965: Failed to submit batchbuffer: Bad address

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Fedora:
  Unknown

Bug description:
  cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 
  gpu: Intel® HD Graphics 630 (Kaby Lake GT2)
  00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
  00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
  ubuntu: 18.04 LTS bionic
  gnome: 3.28.2
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4
  os type: 64 bit
  kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  mesa-va-drivers:
Installed: 18.0.5-0ubuntu0~18.04.1
Candidate: 18.0.5-0ubuntu0~18.04.1

  from syslog:

  Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit 
batchbuffer: Bad address
  Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO 
error 11 (Resource temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource 
temporarily unavailable) on X server :0.
  Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0" 
   - but 
  (followed by pages upon pages of applications within gnome failing.)

  nothing in kern.log around that time.

  Singular gnome crash, taking down all applications running within it.
  Not yet reproduced. gdm successfully started a new session afterwards.
  Was definitely in a palermoon session on some website or other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1794033/+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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

[Pablo Catalina]

I had the same problem with a Thunderbolt audio device and BT. I removed 
.config/pulse and started working fine again.
Not sure if it will fail, but for the moment is working.

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Pablo Catalina]

I installed Ubuntu 20.04 5 days ago (using the daily iso) and works fine
with Quadro P3200 Mobile and default proprietary drivers installed.

I installed it setting up the user with autologon from the installer.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1873764] [NEW] CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id

[Pablo Catalina]

Public bug reported:

I noted the following messages on a just installed Ubuntu Focal:

$ dmesg | grep cups
[ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 
comm="cups-browsed" capability=23  capname="sys_nice"
[ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" 
name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


It happened after installing Brother DCPL3550CDW Linux drivers.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-daemon 2.3.1-9ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30
Uname: Linux 5.4.0-25-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 20 10:49:08 2020
InstallationDate: Installed on 2020-04-19 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
Lpstat: device for DCPL3550CDW: 
dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4b66edd
MachineType: LENOVO 20MAS0DF03
Papersize: a4
PpdFiles: DCPL3550CDW: Brother DCP-L3550CDW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-lowlatency 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1536353] Re: [Regression] Epson's printer driver packages cannot be installed as lsb package is not available anymore

[Rosendo Pablo]

Thank you so much for this information, I have been googling and
searching the net for 2 weeks for an answer of my Epson L800, I couldn't
installed it in Sparkylinux 5, I added the Debian 9 repository and
charm.

One thing that I don't get it to work is the HubiC cloud, it keeps says
"Warning] Can not synchronise /home/qkeybil/Hubic/: Index was outside
the bounds of the array.. Will retry later.

If there is one out there to help, what is going on?

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

Title:
  [Regression] Epson's printer driver packages cannot be installed as
  lsb package is not available anymore

Status in lsb:
  New
Status in cups-filters package in Ubuntu:
  Fix Released
Status in epson-inkjet-printer-escpr package in Ubuntu:
  Fix Released
Status in lsb package in Ubuntu:
  Fix Released
Status in cups-filters source package in Xenial:
  Fix Released
Status in epson-inkjet-printer-escpr source package in Xenial:
  Fix Released
Status in lsb source package in Xenial:
  Fix Released

Bug description:
  [SRU justification]
  Previous releases were compatible with third-party printer drivers provided 
in LSB package format (and also as .deb packages depending on the lsb package). 
 As of 16.04, because the LSB specifies ABIs for various libraries that are no 
longer supported in Ubuntu as obsolete, the packages for the lsb modules have 
been dropped in both Debian and Ubuntu.  This includes dropping of lsb-core, 
which is the component which provides the LSB-mandated ELF loader path - 
without which no lsb executable will work.

  This SRU will restore the bare minimum of LSB compatibility necessary
  to support known third-party LSB printer driver packages on Ubuntu
  16.04.

  [Regression potential]
  The reintroduced 'lsb' binary package is known to not fully satisfy the 
requirements for a complete LSB-compliant system.  This is a regression vs. 
Ubuntu 14.04; so anyone using LSB packages on Ubuntu 14.04 who upgrades to 
Ubuntu 16.04 may have the upgrade succeed without any warning from the package 
manager.

  As there are very few lsb packages in use in the wild, this is
  considered an acceptable regression, especially as this will land
  before the first 16.04 point release.

  [Test case]
  1. Download the epsion 201106w printer driver package from 
http://download.ebz.epson.net/dsc/op/stable/debian/dists/lsb3.2/main/binary-amd64/epson-inkjet-printer-201106w_1.0.1-1lsb3.2_amd64.deb
  2. Install the package and confirm that its dependencies are not satisfiable.
  3. Enable xenial-proposed.
  4. Install the package again and confirm that the dependencies are satisfied.
  5. Verify that 
/opt/epson-inkjet-printer-201106w/cups/lib/filter/epson_inkjet_printer_filter 
can be run without errors about missing lsb ld.so or missing libraries.

  Starting with Xenial, lsb compatibility packages were dropped (besides
  lsb-release and lsb-base):

  lsb (9.20150826) unstable; urgency=low

    * Drop all the LSB compatibility packages besides lsb-release and lsb-base
  - Drop packages-availability checking in lsb-release
  - Truncate README.Debian to a minimum
  - Document this in lsb-base.NEWS.Debian
    * Change the versioning number to avoid any ambiguity; use joeyh's
  version.date, with version being Debian next stable's

   -- Didier Raboud   Wed, 26 Aug 2015 12:00:00 +0200

  The problem is that downloadable printer drivers (like the ones from
  Openprinting, but also from other available providers) that are
  suggested when installing a printer on Ubuntu depends on lsb, which is
  not available anymore:

  epson-inkjet-printer-201106w:
   Dépend: lsb (>=3.2) but it is not installable

  This triggers a regression where it is not possible to setup a printer
  this way (downloading a driver where no local driver is available)
  anymore.

  I see two possible solutions:

  - Add a proper replaces field to one of the remaining lsb-* packages,
  to hopefully fix missing lsb package (maybe it would be useful to also
  replace other compability packages that are not built anymore).

  - Re-introduce LSB compatibility packages, but that might be an
  overkill.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lsb/+bug/1536353/+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 1871006] Re: add-apt-repository crashed with AttributeError in _get_https_content_py3(): 'InvalidURL' object has no attribute 'reason'

[Pablo]

Hi Sebastien,

I used exactly the same command I used to add the ppa, except that I
added the flag --remove. Here is the command:

sudo add-apt-repository --remove ppa:"deb [arch=amd64]
https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"

The thing here is that, even if the command had the wrong parameter
(which seems to be the case), the exception should still be caught and a
proper error message be shown, shouldn't it?

The command to add this ppa (without the --remove flag) has been taken
from the official Docker page.

In addition to this error, I found that, having this ppa (which could
not be found due to Docker not having released the related version to
"focal"), when doing a refresh from the Software & Updates package, it
fails showing the Report Bug window and freezes, not letting the user to
close it. I guess this bug would appear with any ppa that cannot be
found.

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

Title:
  add-apt-repository crashed with AttributeError in
  _get_https_content_py3(): 'InvalidURL' object has no attribute
  'reason'

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Release: 20.04 Ubuntu Focal Fossa (development branch)
  Package/Program: add-apt-repository
  Command: add-apt-repository --remove

  Expected response:
   Either to get the ppa removed or the exception handled with a message 
"unable to find the URL"

  What happened instead:
   The traceback of an exception was printed in the terminal.

  Traceback:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 138, 
in _get_https_content_py3
  lp_page = urllib.request.urlopen(request,
File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
  return opener.open(url, data, timeout)
File "/usr/lib/python3.8/urllib/request.py", line 525, in open
  response = self._open(req, data)
File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
  result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
  result = func(*args)
File "/usr/lib/python3.8/urllib/request.py", line 1362, in https_open
  return self.do_open(http.client.HTTPSConnection, req,
File "/usr/lib/python3.8/urllib/request.py", line 1319, in do_open
  h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/lib/python3.8/http/client.py", line 1230, in request
  self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.8/http/client.py", line 1241, in _send_request
  self.putrequest(method, url, **skips)
File "/usr/lib/python3.8/http/client.py", line 1092, in putrequest
  self._validate_path(url)
File "/usr/lib/python3.8/http/client.py", line 1183, in _validate_path
  raise InvalidURL(f"URL can't contain control characters. {url!r} "
  http.client.InvalidURL: URL can't contain control characters. 
'/api/devel/~deb [arch=amd64] https/+archive/ubuntu/ppa' (found at least ' ')

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 380, 
in get_ppa_info
  ret = get_ppa_info_from_lp(user, ppa)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 110, 
in get_ppa_info_from_lp
  return get_info_from_lp(lp_url)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, 
in get_info_from_lp
  return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 96, 
in get_info_from_https
  data = func(lp_url=url, accept_json=accept_json, 
retry_delays=retry_delays)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 143, 
in _get_https_content_py3
  "Error reading %s (%d tries): %s" % (lp_url, trynum, e.reason),
  AttributeError: 'InvalidURL' object has no attribute 'reason'

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 138, 
in _get_https_content_py3
  lp_page = urllib.request.urlopen(request,
File "/usr/lib/python3.8/urllib/request.py", line 222, in urlopen
  return opener.open(url, data, timeout)
File "/usr/lib/python3.8/urllib/request.py", line 525, in open
  response = self._open(req, data)
File "/usr/lib/python3.8/urllib/request.py", line 542, in _open
  result = self._call_chain(self.handle_open, protocol, protocol +
File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
  result = func(*args)
File "/usr/lib/python3.8/urllib/request.py", line 1362, in 

[Touch-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted

[Pablo César Galdo Regueiro]

I tried to boot Puppy Linux BionicPup64 8.0 based on Ubuntu Bionic
x86_64 64-bit and sound works out of the box.

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

Title:
  [Toshiba NB250] Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Increasing the headphones volume in alsamixer, speakers start to sound.
If I plug the headphones, it works. When unplug the headphones, alsamixer 
Headphones volume goes to zero and it affects speaker, because headphones 
volume in alsamixer control both speaker and headphones.

** Attachment added: "With volume un Headphone section in alsamixer thre're 
sound"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339031/+files/sound.png

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Just after boot, no sound.
It can't be activated using pavucontrol.
Only with alsamixer.

** Attachment added: "State of alsamixer and pavucontrol on boot"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+attachment/5339029/+files/boot.png

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868131] Re: Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

It is a duplicate of bug #1310121, unsolved from 2014, but
administrators closed it.

Daniel van Vugt (vanvugt) wrote 10 hours ago:   #9

Everyone please report your own new bugs by running:

  ubuntu-bug pulseaudio

This bug is closed.

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: TOSHIBA NB250
  dmi.product.sku: 012345678912345678912345678
  dmi.product.version: PLL2XE-005003AS
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+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 1868131] [NEW] Integrated speakers always muted

[Pablo César Galdo Regueiro]

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

Public bug reported:

Speakers are muted at boot and remains muted after plug and unplug headphones. 
Only can be activated from alsamixer, unmuting the headphones while the 
headphones are unplugged. Both speakers and
headphones muting seems to be controlled in the Headphones area using alsamixer.

Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionic.

I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping
automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-
mixer/paths/analog-output-headphones.conf and executing a bash script at
boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute
100%" in order to prevent the speakers being muted.

There are some issues reported to pulseaudio manteiners. Not the same
but related:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  xubuntu1881 F pulseaudio
CasperVersion: 1.427
CurrentDesktop: XFCE
Date: Thu Mar 19 15:58:26 2020
LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.60
dmi.board.name: PAV10 DDR2
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
dmi.product.name: TOSHIBA NB250
dmi.product.sku: 012345678912345678912345678
dmi.product.version: PLL2XE-005003AS
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug eoan

** Attachment added: "analog-output-headphones.conf"
   
https://bugs.launchpad.net/bugs/1868131/+attachment/5338919/+files/analog-output-headphones.conf

** This bug has been marked a duplicate of bug 1310121
   headphones working while speakers not working

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

Title:
  Integrated speakers always muted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Speakers are muted at boot and remains muted after plug and unplug 
headphones. Only can be activated from alsamixer, unmuting the headphones while 
the headphones are unplugged. Both speakers and
  headphones muting seems to be controlled in the Headphones area using 
alsamixer.

  Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
  base: Ubuntu 18.04 bionic.

  I've "solved" it Linux Mint 19.3 Tricia in a not very good way,
  keeping automute activated in alsamixer, modifiyng
  /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf
  and executing a bash script at boot (sonido.sh) with the command
  "amixer set -c 0 Headphone unmute 100%" in order to prevent the
  speakers being muted.

  There are some issues reported to pulseaudio manteiners. Not the same
  but related:

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu1881 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: XFCE
  Date: Thu Mar 19 15:58:26 2020
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.60
  dmi.board.name: PAV10 DDR2
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: 

[Touch-packages] [Bug 1310121] Re: headphones working while speakers not working

[Pablo César Galdo Regueiro]

There are some issues reported to pulseaudio manteiners. Not the same
but related:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

** Bug watch added: PulseAudio #256
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256

** Bug watch added: PulseAudio #540
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540

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

Title:
  headphones working while speakers not working

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5
  kernel.

  Testing the left and right channel work for headphones output , a
  minijack is connected to the ampli.

  Removing the jack the notebook ( system76 notebook) is like mute. I have 
tried to use alsamixer , all the volume are ok.
  application seem to output their audios... but nothing to through the 
speakers.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francesca   2074 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 20 00:23:09 2014
  InstallationDate: Installed on 2012-10-18 (548 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp8
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp8
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+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 1310121] Re: headphones working while speakers not working

[Pablo César Galdo Regueiro]

Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia
base: Ubuntu 18.04 bionic.

Speakers are muted at boot and remains muted after plug and unplug
headphones. Only can be activated from alsamixer, unmuting the
headphones while the headphones are unplugged. Both speakers and
headphones muting seems to be controlled in the Headphones area using
alsamixer.

I've "solved" it in a not very good way, keeping automute activated in
alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-
output-headphones.conf and executing a bash script at boot (sonido.sh)
with the command "amixer set -c 0 Headphone unmute 100%" in order to
prevent the speakers being muted.

Tomorrow I'm going to send more details and try to reproduce the same
bug using Xubuntu 18.04.

System:
  Host: ROI-TOSHIBA-NB250 Kernel: 5.3.0-42-generic x86_64 bits: 64 
  compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 tk: Gtk 3.22.30 wm: xfwm4 
  dm: LightDM Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic

Machine:
  Type: Laptop System: TOSHIBA product: TOSHIBA NB250 v: PLL2XE-005003AS 
  serial:  Chassis: type: 10 serial:  
  Mobo: TOSHIBA model: PAV10 DDR2 v: 1.00 serial:  BIOS: TOSHIBA 
  v: 1.60 date: 07/30/2010 

CPU:
  Topology: Single Core model: Intel Atom N455 bits: 64 type: MT 
  arch: Bonnell rev: A L2 cache: 512 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 6649 
  Speed: 997 MHz min/max: 1000/1667 MHz Core speeds (MHz): 1: 997 2: 997

Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio 
  vendor: Toshiba America Info Systems driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:27d8 
  Sound Server: ALSA v: k5.3.0-42-generic 

Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: 
/etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://mirrors.evowise.com/linuxmint/packages tricia main upstream 
import backport
  2: deb http://es-mirrors.evowise.com/ubuntu bionic main restricted universe 
multiverse
  3: deb http://es-mirrors.evowise.com/ubuntu bionic-updates main restricted 
universe multiverse
  4: deb http://es-mirrors.evowise.com/ubuntu bionic-backports main restricted 
universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted 
universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ bionic partner
Info:
  Processes: 160 Uptime: 40m Memory: 1.93 GiB used: 927.8 MiB (46.9%) 
  Init: systemd v: 237 runlevel: 5 Compilers: gcc: 7.5.0 alt: 7 Shell: bash 
  v: 4.4.20 running in: xfce4-terminal inxi: 3.0.32 

** Attachment added: "analog-output-headphones.conf"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310121/+attachment/5338626/+files/analog-output-headphones.conf

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

Title:
  headphones working while speakers not working

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  to change kernel does not help, I tried 3.11 kernel, 3.8 kernel, 3.5
  kernel.

  Testing the left and right channel work for headphones output , a
  minijack is connected to the ampli.

  Removing the jack the notebook ( system76 notebook) is like mute. I have 
tried to use alsamixer , all the volume are ok.
  application seem to output their audios... but nothing to through the 
speakers.

  thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  francesca   2074 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Apr 20 00:23:09 2014
  InstallationDate: Installed on 2012-10-18 (548 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (0 days ago)
  dmi.bios.date: 09/27/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Gazelle Professional
  dmi.board.vendor: System76, Inc.
  dmi.board.version: gazp8
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd09/27/2012:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp8:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp8:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: Gazelle Professional
  dmi.product.version: gazp8
  dmi.sys.vendor: System76, Inc.

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

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

[Touch-packages] [Bug 1862264] Re: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount")

[Pablo Copissa]

Reported upstream as issue 2062
(https://gitlab.gnome.org/GNOME/glib/issues/2062)

** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #2062
   https://gitlab.gnome.org/GNOME/glib/issues/2062

** Description changed:

+ Reported upstream as issue 2062
+ (https://gitlab.gnome.org/GNOME/glib/issues/2062)
+ 
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share
  
  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s
  
  Enumeration of files is about 29 times slower when mounted via gio mount
  than via mount -t cifs.
  
  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804
  
  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s
  
  Note that this is almost TWICE AS FAST than the "fast" mount of test #1
  and about 53 times faster than "slow" test #2 !
  
  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They use
  the same underlying infrastructure which test 3 proves is adequately
  fast. And yet, we get this slow down in test 2.
  
  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.
  
  Hope this helps
  
  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)
  
  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).
  
  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)
  
  $ gio mount smb://nas.example.com/share2
  
  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path
  
  $ time ls
  
  ... 528 subdirs approximately ...
  
  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s
  
  $ time ls | wc
- 5281631   10893
+ 5281631   10893
  
  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s
  
  Factor is about 50.

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Reported upstream as issue 2062
  (https://gitlab.gnome.org/GNOME/glib/issues/2062)

  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these b

[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I was able to solve the control volume thing but the root problem still
there. If someone gets to this point I will show you my solution.

I realized (in alsamixer) that I was able to change the speakers volume
controlling PCM device instead of Master one. So I searched about that
and found that you can make pulseaudio to control another device. All
the information is in here: https://askubuntu.com/questions/15069/how-
do-i-change-the-way-ubuntu-adjusts-my-volume-mixer-levels

However, I think this should be fixed. Thank you for your help ^^

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/1596381/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I have the same problem on Asus Zenbook UX430UA (Realtek ALC295) in
Ubuntu 18.04 with 5.3.0-40-generic linux kernel version.

Comment #8 fix's worked for me but now I get the same volume level from
my laptop speakers with 1% volume level, than the one I get with 100%
volume level. The only thing that I can change from volume controls is
that with 0% volume level, the speakers are muted.

I have tried with "options snd-hda-intel model=auto,laptop-dmic" but I
get the expected behaviour with model=auto (speakers works great but no
audio recording from laptop microphone). With "options snd-hda-intel
model=laptop-dmic,auto" I get the same behaviour that the one I get with
"model=laptop-dmic" only (microphone working but volume control doing
nothing).

I thought this was fixed, but maybe I'm doing something wrong.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/1596381/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Pablo Rodríguez Guillén]

I have the same problem on my Asus Zenbook UX430UA (Realtek ALC295)
although I have "5.3.0-40-generic" linux kernel version with Ubuntu
18.04. Comment #8 solved my problem but with "options snd-hda-intel
model=laptop-dmic" in my alsa conf, up and down volume don't change the
speakers volume.

I can only mute the speakers with 0 volume, but I get the same volume
level with 1% volume than the one I get with 100%

With "options snd-hda-intel model=auto" or "options snd-hda-intel
model=alc295" I get the expected behaviour from the speakers but no
record of the internal microphone. I have already tried combining
auto/alc295 with laptop-dmic but I get the behaviour of the first option
I write (like as it were alone)

I thought this was fixed, maybe I am doing something wrong.

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  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/1596381/+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 1862264] Re: Browsing smb share is painfully slow

[Pablo Copissa]

Looks like gio is part of glib, not gvfs, so changed the package accordingly. 
Also made clear in the title that gio vs mount is part of the issue.

** Package changed: gvfs (Ubuntu) => glib2.0 (Ubuntu)

** Summary changed:

- Browsing smb share is painfully slow
+ Browsing smb share is painfully slow when mounted via "gio" (compared with 
"mount")

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

Title:
  Browsing smb share is painfully slow when mounted via "gio" (compared
  with "mount")

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020).
  TEST #1:
  To establish a baseline/expected behavior, we first mount an SMB share via 
mount.cifs and time an ls command:
  $ sudo mount -t cifs -o username=pablo //myserver.example.com/share 
~/mnt/share
  $ cd ~/mnt/share/some/dir
  $ time ls
  ... approx 320 files ...
  real  0m1,080s
  user  0m0,008s
  sys   0m0,005s
  $ sudo umount ~/mnt/share

  TEST #2
  Now we do the same via gio mount:
  $ gio mount smb://myserver.example.com/share
  cd 
/run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir
  $ time ls
  ... same 320 files ...
  real  0m28,999s
  user  0m0,013s
  sys   0m0,032s

  Enumeration of files is about 29 times slower when mounted via gio
  mount than via mount -t cifs.

  TEST #3
  Now for the real weird: while using the gio-mounted folder, we now time ls IN 
COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...):
  $ time ls | wc
     321 3239804

  real  0m0,546s
  user  0m0,006s
  sys   0m0,004s

  Note that this is almost TWICE AS FAST than the "fast" mount of test
  #1 and about 53 times faster than "slow" test #2 !

  The expectation is that Tests 1 and 2 should have similar timings, not
  differing by a factor of 30 or so. More disturbing, there is no good
  reason why tests 2 and 3 differ by an even bigger factor of 53: They
  use the same underlying infrastructure which test 3 proves is
  adequately fast. And yet, we get this slow down in test 2.

  As a final note, these benchmarks are a distilled version of the original 
real-life motivating scenario where a Java-based program would simply take tens 
of minutes to display the same list of 320 files when mounted via gio mount and 
a second or so when mounted via mount -t cifs.
  The same timing difference is of course visible in any file manager.

  Hope this helps

  PS: several old/ancient bug reports exist for a similar issue and I
  deliberately copied the title from one of them (#259771)

  PS2: may or may not be relevant: The remote server is a VM running
  Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu
  stock SSTP).

  PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM)

  $ gio mount smb://nas.example.com/share2

  $ cd /run/user/1000/gvfs/smb-
  share\:server\=nas.example.com\,share\=share2/another/path

  $ time ls

  ... 528 subdirs approximately ...

  real  0m45,075s
  user  0m0,013s
  sys   0m0,058s

  $ time ls | wc
  5281631   10893

  real  0m0,911s
  user  0m0,003s
  sys   0m0,005s

  Factor is about 50.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1862264/+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 1859829] Re: server will not boot after updating lvm2 package

[Pablo SEMINARIO]

Hi,

Same issue here, after a system upgrade today my computer was not able
to boot anymore. On my

It was stuck with the following message:

WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Volume group "ubuntu-vg" not found Cannot process volume group ubuntu-vg

As workaround I downgraded the package from a chroot mount via an USB
key running:

apt-get install lvm2=2.02.176-4.1ubuntu3
liblvm2app2.2=2.02.176-4.1ubuntu3 liblvm2cmd2.02=2.02.176-4.1ubuntu3

and it was able to boot again.

Here's the output of /var/log/dpkg.log:

2020-02-07 12:20:00 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:20 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:36 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2

2020-02-07 15:07:06 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3

Please don't hesitate to ask for more details.

Best,

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

Title:
  server will not boot after updating lvm2 package

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After updating lvm2 from 2.02.176-4.1ubuntu3.18.04.1 to
  2.02.176-4.1ubuntu3.18.04.2, server will not boot.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  2.02.176-4.1ubuntu3.18.04.2

  3) What you expected to happen
  I expect the server to boot.

  4) What happened instead
  The server hangs at boot.

  As the server will not boot, I can not provide any logs.  I can only
  provide a screen captures of the boot failure messages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1859829/+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 1286836] Re: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not co-installable with libpostp

[pablo]

** Changed in: libav (Ubuntu)
 Assignee: (unassigned) => pablo (pablostar)

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

Title:
  package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to
  install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch:
  no) is not co-installable with libpostproc52 which has multiple
  installed instances

Status in libav package in Ubuntu:
  Triaged
Status in libpostproc package in Ubuntu:
  Triaged

Bug description:
   -

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpostproc52 6:0.8.10-0ubuntu0.13.10.1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Mar  3 00:57:47 2014
  Dependencies:
   gcc-4.9-base 4.9-20140222-0ubuntu1
   libavutil51 6:0.8.10-0ubuntu0.13.10.1 [origin: unknown]
   libc6 2.19-0ubuntu2
   libgcc1 1:4.9-20140222-0ubuntu1
   multiarch-support 2.19-0ubuntu2
  ErrorMessage: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  InstallationDate: Installed on 2013-12-12 (79 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: libav
  Title: package libpostproc52 6:0.8.10-0ubuntu0.13.10.1 failed to 
install/upgrade: libpostproc52:amd64 6:0.git20120821-4 (Multi-Arch: no) is not 
co-installable with libpostproc52 which has multiple installed instances
  UpgradeStatus: Upgraded to trusty on 2014-03-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1286836/+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 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Pablo Merighi]

Solved with

sudo apt-get install --reinstall hplip hplip-data
sudo apt-get install --reinstall python3

Thanks

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

Title:
  package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Only Ubuntu Update

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3 3.6.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 28 22:51:28 2018
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2018-04-13 (76 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SourcePackage: python3-defaults
  Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+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 1803470] [NEW] package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

[Juan Pablo Florez]

Public bug reported:


There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-39-generic 4.15.0-39.42
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1187 F pulseaudio
  juan   1898 F pulseaudio
 /dev/snd/controlC0:  gdm1187 F pulseaudio
  juan   1898 F pulseaudio
Date: Wed Nov 14 19:17:20 2018
Df:
 
Dmesg:
 
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b
InstallationDate: Installed on 2018-02-15 (272 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: TOSHIBA Satellite P55t-B
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
UpgradeStatus: Upgraded to bionic on 2018-10-14 (31 days ago)
dmi.bios.date: 12/09/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.50
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG20SQ
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd12/09/2014:svnTOSHIBA:pnSatelliteP55t-B:pvrPSPNVU-03XNC1:rvnTOSHIBA:rnVG20SQ:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: Satellite P55t-B
dmi.product.version: PSPNVU-03XNC1
dmi.sys.vendor: TOSHIBA

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  
  There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-39-generic 4.15.0-39.42
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
   /dev/snd/controlC0:  gdm1187 F pulseaudio
juan   1898 F pulseaudio
  Date: Wed Nov 14 19:17:20 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
  HibernationDevice: RESUME=UUID=45ec2b0c-3e08-4c6c-abb9-645caf9f287b
  InstallationDate: Installed on 2018-02-15 (272 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: TOSHIBA Satellite P55t-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=efe479bd-ea94-4b87-91c8-74190bf43a1b ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.7
  SourcePackage: initramfs-tools
  Title: package linux-image-4.15.0-39-generic 4.15.0-39.42 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 2
 

[Touch-packages] [Bug 1782925] Re: No me deja usar NVIDIA 304.135

[Juan Pablo Montiel]

Si me van a ayudar por favor que sea en mi idioma (Castellano-Español).
Gracias!!!

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

Title:
  No me deja usar NVIDIA 304.135

Status in xorg package in Ubuntu:
  New

Bug description:
  Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
  con una resolución muy mala.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 21 11:26:39 2018
  DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
  InstallationDate: Installed on 2017-04-10 (467 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  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.15.0-29-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-07-18 (3 days ago)
  dmi.bios.date: 05/04/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: ALiveNF6G-VSTA
  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.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  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.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  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
  xserver.bootTime: Sat Jul 21 10:56:17 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1782925/+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 1782925] [NEW] No me deja usar NVIDIA 304.135

[Juan Pablo Montiel]

Public bug reported:

Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
con una resolución muy mala.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jul 21 11:26:39 2018
DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
InstallationDate: Installed on 2017-04-10 (467 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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.15.0-29-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-18 (3 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: ALiveNF6G-VSTA
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.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
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
xserver.bootTime: Sat Jul 21 10:56:17 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install 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/1782925

Title:
  No me deja usar NVIDIA 304.135

Status in xorg package in Ubuntu:
  New

Bug description:
  Instalé NVIDIA-Linux-x86_64-304.135.run pero no me deja usarlo y estoy
  con una resolución muy mala.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 21 11:26:39 2018
  DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
  InstallationDate: Installed on 2017-04-10 (467 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   

[Touch-packages] [Bug 1782498] [NEW] Se tilda pantalla

[Juan Pablo Montiel]

Public bug reported:

Hola amigos!
El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

Juan Pablo Montiel
6551 - Pirovano - Bs As - Argentina

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
Date: Wed Jul 18 23:57:18 2018
DistUpgraded: 2018-07-18 03:54:52,667 DEBUG failed to SystemUnLock() (E:No 
bloqueado)
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation C61 [GeForce 6150SE nForce 430] [1849:03d0]
InstallationDate: Installed on 2017-04-10 (464 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
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.15.0-23-generic 
root=UUID=5ec15496-f7c3-4826-b449-502d83c3141c ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-18 (0 days ago)
dmi.bios.date: 05/04/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: ALiveNF6G-VSTA
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.50:bd05/04/2007:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnALiveNF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
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.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
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
xserver.bootTime: Wed Jul 18 23:05:59 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

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

Title:
  Se tilda pantalla

Status in xorg package in Ubuntu:
  New

Bug description:
  Hola amigos!
  El tema es que siempre y con versiones anteriores (además de con esta) se me 
tilda la pantalla y queda el SO totalmente inmovilizado, con la pantalla en 
algunos de los colores que estaba viendo. Nunca puedo encontrar el porqué, ya 
que el equipo se bloquea y no me deja entrar a las otras terminales como tty1, 
etc.
  Siempre el sistema me dice que les avisará, pero la verdad es que nunca me ha 
llegado un mensaje al respecto.

  Un gran saludo a todos desde Argentina, vivo en un pueblito de 1.500
  habitantes y uso Ubunto hace aproximadamente unos 10 años. Los quiero
  mucho y aprecio mucho lo que hacen por nosotros como usuarios. GRACIAS

  Juan Pablo Montiel
  6551 - Pirovano - Bs As - Argentina

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Packa

[Touch-packages] [Bug 1435421] Re: Dell XPS 15 - audio combo jack - microphone not working

[Jose Pablo]

I am on Arch Linux, same laptop model, same bug, I notice this is a 3
year old issue and I do not know if there has been any update to it in
the meantime. Is there anything I can do to help solve this issue?

(ps I made a thread on the arch forum about my problem
https://bbs.archlinux.org/viewtopic.php?pid=1777240#p1777240 )

** Also affects: alsa-driver (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  Dell XPS 15 - audio combo jack - microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Combo jack (headphones and microphone) working only as headphone
  output. Microphone is not detected at all when plugged-in.

  My exact laptop model is: Dell XPS 15 9530.

  I'm on 14.04 LTS, but I dont think its version-related. What more
  informations shall I collect and post here?

  I have also sent a report via http://www.alsa-project.org/alsa-
  info.sh. Would it help if I include one here?

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bartek 2296 F pulseaudio
   /dev/snd/controlC0:  bartek 2296 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 14.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-19 (218 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS 15 9530
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=a8714bf2-f3fb-4875-bb9e-4354f36a7f66 ro quiet splash nomdmonddf 
nomdmonisw
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-36-generic N/A
   linux-backports-modules-3.13.0-36-generic  N/A
   linux-firmware 1.127.6
  Tags:  trusty
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip libvirtd lpadmin plugdev sambashare sudo 
www-data
  _MarkForUpload: True
  dmi.bios.date: 03/28/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: XPS 15 9530
  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:bd03/28/2014:svnDellInc.:pnXPS159530:pvrA04:rvnDellInc.:rnXPS159530:rvrA04:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A04
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1435421/+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 1759150] [NEW] systemd stopped resolving after back from suspend

[Pablo Catalina]

Public bug reported:

I noted it after back from suspend, but could happens on other
conditions:

systemd-resolved stopped resolving.


$ host google.com 127.0.0.53
Using domain server:
Name: 127.0.0.53
Address: 127.0.0.53#53
Aliases:

Host google.com not found: 2(SERVFAIL)


But resolved service is active without problems.

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 11822 (systemd-resolve)
   Status: "Processing requests..."
Tasks: 1 (limit: 4915)
   CGroup: /system.slice/systemd-resolved.service
   └─11822 /lib/systemd/systemd-resolved

Mar 27 09:28:01 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:28:06 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:28:42 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:29:07 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:29:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:30:11 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:30:32 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:30:37 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:38:10 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.
Mar 27 09:38:15 myhostname systemd-resolved[11822]: Got packet on unexpected IP 
range, refusing.


I checked the network traffic:

09:38:15.476106 IP 10.66.57.54.48901 > 127.0.0.53.53: 7013+ A? google.com. (28)
09:38:15.476205 IP 127.0.0.53.53 > 127.0.0.1.48901: 7013 ServFail [0q] 0/0/0 
(12)


And resolv service works fine:

$ systemd-resolve google.com
google.com: 216.58.214.174

-- Information acquired via protocol DNS in 7.2ms.
-- Data is authenticated: no


ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.3
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 27 09:34:21 2018
InstallationDate: Installed on 2018-02-16 (38 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Apple Inc. MacBookPro11,4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2017
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0177.B00.1708080033
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP114.88Z.0177.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug artful

** Description changed:

  I noted it after back from suspend, but could happens on other
  conditions:
  
  systemd-resolved stopped resolving.
  
- 
- 
+ 
  $ host google.com 127.0.0.53
  Using domain server:
  Name: 127.0.0.53
  Address: 127.0.0.53#53
- Aliases: 
+ Aliases:
  
  Host google.com not found: 2(SERVFAIL)
- 
+ 
  
  But resolved service is active without problems.
  
  ● systemd-resolved.service - Network Name Resolution
-Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
-Active: active (running) since Tue 2018-03-27 09:27:46 CEST; 11min ago
-  Docs: man:systemd-resolved.service(8)
-https://www.freedesktop.org/wiki/Software/systemd/resolved
-
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
-
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
-  Main PID: 11822 (systemd-resolve)
-Status: "Processing requests..."
- Tasks: 1 (limit: 4915)
-CGroup: /system.slice/systemd-resolved.service
-└─11822 /lib/systemd/systemd-resolved
+    Loaded: loaded 

[Touch-packages] [Bug 304345] Re: File chooser dialog doesn't provide network access

[Pablo Fontoura]

Chrome file chooser doesn't show network locations too. 
Ubuntu 16.04 LTS.

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

Title:
  File chooser dialog doesn't provide network access

Status in GTK+:
  Fix Released
Status in One Hundred Papercuts:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Baltix:
  Fix Released

Bug description:
  Binary package hint: audacious

  Audacious cannot open files samba shares. Just like Gringotts and
  Firefox it cannot open (save) to network share.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=8.10
  DISTRIB_CODENAME=intrepid
  DISTRIB_DESCRIPTION="Ubuntu 8.10"

  ii  audacious  1.5.1-3ubuntu1.1
  small and fast audio player which supports

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/304345/+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 1722029] [NEW] package libicu57 57.1-5 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2

[Pablo Fonseca Moncada]

Public bug reported:

I am new in Linux technology, when I started the operating system a pop-
up showed me that I had one error, that is all what I know

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libicu57 57.1-5
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
Date: Sat Oct  7 22:16:59 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 libstdc++6 6.3.0-12ubuntu2
ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
InstallationDate: Installed on 2017-10-08 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4.6~17.04.1
SourcePackage: icu
Title: package libicu57 57.1-5 failed to install/upgrade: el subproceso 
dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 zesty

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

Title:
  package libicu57 57.1-5 failed to install/upgrade: el subproceso dpkg-
  deb --fsys-tarfile devolvió el código de salida de error 2

Status in icu package in Ubuntu:
  New

Bug description:
  I am new in Linux technology, when I started the operating system a
  pop-up showed me that I had one error, that is all what I know

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libicu57 57.1-5
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sat Oct  7 22:16:59 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libstdc++6 6.3.0-12ubuntu2
  ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de 
salida de error 2
  InstallationDate: Installed on 2017-10-08 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: icu
  Title: package libicu57 57.1-5 failed to install/upgrade: el subproceso 
dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1722029/+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 1533670] Re: python 2.7.10 crashes with a QProcess error 1 after reading some files and trying to display them within wxPython

[Juan Pablo Nieri]

Hello, i have the same problem. When i execute a program with WxPython the 
terminal (in ninja) show me, qprocess error. I use Ubuntu 16.04 LTS, ninja-ide, 
python 2.7.3 and the library wxPython version 4.0.0b1.
You can helpme with the solution of the bug?. Sory for my english.

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

Title:
  python 2.7.10 crashes with a QProcess error 1 after reading some files
  and trying to display them within wxPython

Status in dbus package in Ubuntu:
  Invalid

Bug description:
  This bug allready showed up within Ubuntu 14.04, and I thought I this
  was the result of curious installs.

  Thinking it could be a good idea, starting from zero and trying out
  Ubuntu-Mate 15.10, I installed this enviroment completely new and
  everything worked fine. Except for the wrong keyboard usage of the
  system before entering the system, after entering everything is fine (
  will post a seperate error-issue for this).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Jan 13 13:54:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-07 (6 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1533670/+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 988144] Re: Getting error message: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]

[Pablo Piaggio]

This is happening again on: xenial

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

$ uname -a
Linux vaughan 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ rsync --version
rsync  version 3.1.1  protocol version 31
Copyright (C) 1996-2014 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, iconv, symtimes, prealloc

rsync comes with ABSOLUTELY NO WARRANTY.  This is free software, and you
are welcome to redistribute it under certain conditions.  See the GNU
General Public Licence for details.

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

Title:
  Getting error message:  error in rsync protocol data stream (code 12)
  at io.c(605) [sender=3.0.9]

Status in rsync package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Precise 12.04LTS

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Installed: 3.0.9-1ubuntu1
Candidate: 3.0.9-1ubuntu1
Version table:
   *** 3.0.9-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen

  I was using rsync to backup my Home DIrectorys' contents and at one
  point in the backup it gave me this error:

   Downloads/Windows.7.Ultimate.32-64Bit.(2011-02-09).iso
3809312768  83%   21.03MB/s0:00:35  
   rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: 
Broken pipe (32)
   rsync: connection unexpectedly closed (70735 bytes received so far) 
[sender]
   rsync error: error in rsync protocol data stream (code 12) at io.c(605) 
[sender=3.0.9]
   

  This only came about when it was trying to copy my Windows ISO from my
  directory over to my backup drive that I have formatted in EXT4 - so
  I'm not sure of the issue it's having.

  This is the command I used to backup:

  rsync --progress -rEog --exclude Videos/ --exclude converted_music/
  --exclude VirtualBox\ VMs/ --exclude virtual-drives/ --exclude
  Backup_of_boot_sectors/ --exclude examples.desktop --exclude Music/
  --exclude .ecryptfs --exclude .VirtualBox/ --exclude .thumbnails/
  --exclude .thunderbird/ --exclude .vidalia/ --exclude .teamviewer/
  --exclude Templates/ --exclude sources.list --exclude wary-5.3.iso
  --exclude Public/ --exclude .cache/ /home/alex/ /media/backup/12.04
  -Precise-backup_4.23.2012/

  
  Please look into this for me.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/988144/+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 1689825] Re: gnome-keyring not unlocked on boot

[Pablo Sanabria]

Well, this bug also is affecting me, I used the workaround in #10 and it works, 
but I still need to put my password in order to unlock the "Login" Keyring (My 
system don't have autologin enabled btw), the weird thing is that this system 
is fresh installed (no more than a week) and It was working fine until today. 
Maybe there is some package that I installed yesterday that is affecting the 
system.
Google-chrome affected
Online accounts also is affected
I didn't test other apps, but as far I could check those apps were affected by 
this issue
Greetings

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

Title:
  gnome-keyring not unlocked on boot

Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+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 1696580] [NEW] dificultades con kadenlive

[José Pablo Jaramillo]

Public bug reported:

No funciona en el ambiente mate

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
Uname: Linux 4.8.0-36-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Jun  7 16:22:27 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 00 
[VGA controller])
InstallationDate: Installed on 2017-06-07 (0 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
ProcEnviron:
 LANGUAGE=es_CO:es
 PATH=(custom, no user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', 
'-f'] failed with exit code 1: Error: no composite extension
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 090006
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: 7.0
dmi.chassis.asset.tag: 1155-0718-8197-6541-2374-2356-24
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: 7.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
dmi.product.name: Virtual Machine
dmi.product.version: 7.0
dmi.sys.vendor: Microsoft Corporation
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 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: Wed Jun  7 14:25:27 2017
xserver.configfile: default
xserver.devices:
 inputMicrosoft Vmbus HID-compliant Mouse TOUCHSCREEN, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputTPPS/2 IBM TrackPoint MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


** Tags: amd64 apport-bug 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/1696580

Title:
  dificultades con kadenlive

Status in xorg package in Ubuntu:
  New

Bug description:
  No funciona en el ambiente mate

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Jun  7 16:22:27 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard: Microsoft Corporation Hyper-V virtual VGA [1414:5353] (prog-if 
00 [VGA controller])
  InstallationDate: Installed on 2017-06-07 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-36-generic 
root=UUID=b208d30b-42e0-40d6-b53e-f82e15d5e64c ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UnitySupportTest: 

[Touch-packages] [Bug 1693531] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Pablo Vanegas Enríquez]

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

Public bug reported:

I don`t now

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: gconf2-common 3.2.6-3ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering:
 gconf2-common:amd64: Install
 libgconf-2-4:amd64: Install
 gconf-service-backend:amd64: Install
 gconf-service:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu May 25 00:48:34 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-05-25 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gconf
Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in gconf package in Ubuntu:
  New

Bug description:
  I don`t now

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering:
   gconf2-common:amd64: Install
   libgconf-2-4:amd64: Install
   gconf-service-backend:amd64: Install
   gconf-service:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu May 25 00:48:34 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-05-25 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1693531/+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 1691909] Re: Mongolia no longer observes DST

[Pablo Palomero]

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

** This bug has been marked a duplicate of bug 1691092
   outdated timezone information for Mongolia

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

Title:
  Mongolia no longer observes DST

Status in tzdata package in Ubuntu:
  New

Bug description:
  More Info here:
  http://mm.icann.org/pipermail/tz/2017-February/024811.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691909/+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 1691092] [NEW] outdated timezone information for Mongolia

[Pablo Palomero]

Public bug reported:

Mongolia stopped following DST this year. The timezone information in
Ubuntu 16.04.2 LTS is outdated:

$ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
21:15

The correct output is '20:15'.

This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
using 2016j. I guess the previous LTS versions are also affected.

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

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

Title:
  outdated timezone information for Mongolia

Status in tzdata package in Ubuntu:
  New

Bug description:
  Mongolia stopped following DST this year. The timezone information in
  Ubuntu 16.04.2 LTS is outdated:

  $ TZ=Asia/Ulaanbaatar date --date="2017-05-16 12:15 UTC" +%H:%M
  21:15

  The correct output is '20:15'.

  This has been updated in version 2017a of tzdata. My Ubuntu 16.04 is
  using 2016j. I guess the previous LTS versions are also affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1691092/+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 1064916] Re: Excluded directory shown in recent files when accessed

[Pablo Piaggio]

This is still happening in 16.04:

$ uname -a
Linux vanhalen 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename:   xenial

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

Title:
  Excluded directory shown in recent files when accessed

Status in Zeitgeist Framework:
  Triaged
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  With the "Privacy" tool, I set /home/user/Private to be excluded. I
  browsed to the folder in Nautilus, then opened files inside the
  folder. FIles inside the folder are not logged, but the folder itself
  is. Thus "Private" shows up in my recent files, negating the point of
  excluding it.

  Ubuntu 12.04 64-bit.

  user@office:~$ dpkg -l | grep zeitgeist
  ii  libzeitgeist-1.0-1 0.3.18-1ubuntu1
 library to access Zeitgeist - shared library
  ii  python-zeitgeist   0.9.0-1ubuntu1 
 event logging framework - Python bindings
  ii  rhythmbox-plugin-zeitgeist 2.96-0ubuntu4.2
 zeitgeist plugin for rhythmbox music player
  ii  zeitgeist  0.9.0-1ubuntu1 
 event logging framework
  ii  zeitgeist-core 0.9.0-1ubuntu1 
 event logging framework - engine
  ii  zeitgeist-datahub  0.8.2-1ubuntu2 
 event logging framework - passive logging daemon

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

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

Re: [Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Pablo Carranza]

We can try the proposed patched version in one worker at gitlab. It will
get stressed quite fast

On Nov 14, 2016 13:25, "Łukasz Zemczak" <1591...@bugs.launchpad.net>
wrote:

> @Shay: yes, we will prepare an SRU to the currently supported series
> soon - but please note that the current 'fix' is, in fact, just a
> workaround. But it works.
>
> @Simon: I can try finding some people that could reproduce this easily,
> prepare patched-up version of dbus with both the proposed fixes and ask
> them to run tests on them. Would be really cool if a real fix could be
> found this way. I'll take care of this this week and send feedback here
> and the upstream bug.
>
> Thanks again for looking into this further Simon!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1591411
>
> Title:
>   systemd-logind must be restarted every ~1000 SSH logins to prevent a
>   ~25 second delay
>
> Status in D-Bus:
>   Unknown
> Status in systemd:
>   Unknown
> Status in dbus package in Ubuntu:
>   Fix Released
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in dbus source package in Xenial:
>   Confirmed
> Status in systemd source package in Xenial:
>   Invalid
> Status in dbus source package in Yakkety:
>   Confirmed
> Status in systemd source package in Yakkety:
>   Invalid
>
> Bug description:
>   I noticed on a system that accepts large numbers of SSH connections
>   that after awhile, SSH sessions were taking ~25 seconds to complete.
>
>   Looking in /var/log/auth.log, systemd-logind starts failing with the
>   following:
>
>   Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened
> for user ubuntu by (uid=0)
>   Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user
> ubuntu.
>   Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session
> scope: Transport endpoint is not connected
>   Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to
> create session: Message recipient disconnected from message bus without
> replying
>
>   I reproduced this in an LXD container by doing something like:
>
>   lxc launch ubuntu:x test
>   lxc exec test -- login -f ubuntu
>   ssh-import-id 
>
>   Then ran a script as follows (passing in ubuntu@):
>
>   while [ 1 ]; do
>   (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
>   done
>
>   In my case, after 1052 logins, the 1053rd and thereafter were taking
>   25+ seconds to complete. Here are some snippets from the log file:
>
>   $ cat log | grep 0m0 | wc -l
>   1052
>
>   $ cat log | grep 0m25 | wc -l
>   4
>
>   $ tail -5 log
>   real  0m0.222s
>   real  0m25.232s
>   real  0m25.235s
>   real  0m25.236s
>   real  0m25.239s
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: systemd 229-4ubuntu5
>   ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
>   Uname: Linux 4.4.0-22-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2
>   Architecture: amd64
>   Date: Sat Jun 11 00:09:34 2016
>   MachineType: Notebook W230SS
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash
>   SourcePackage: systemd
>   SystemdDelta:
>[EXTENDED]   /lib/systemd/system/rc-local.service →
> /lib/systemd/system/rc-local.service.d/debian.conf
>[EXTENDED]   /lib/systemd/system/systemd-timesyncd.service →
> /lib/systemd/system/systemd-timesyncd.service.d/disable-
> with-time-daemon.conf
>
>2 overridden configuration files found.
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/15/2014
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 4.6.5
>   dmi.board.asset.tag: Tag 12345
>   dmi.board.name: W230SS
>   dmi.board.vendor: Notebook
>   dmi.board.version: Not Applicable
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Notebook
>   dmi.chassis.version: N/A
>   dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:
> svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:
> rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
>   dmi.product.name: W230SS
>   dmi.product.version: Not Applicable
>   dmi.sys.vendor: Notebook
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions
>

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in D-Bus:
  Unknown
Status in systemd:
  Unknown
Status in dbus package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in dbus source package in Yakkety:
  

[Touch-packages] [Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed

[Pablo Catalina]

I have similar problem with flashplugin-installer and ttf-mscorefonts-
installer packages:

flashplugin-installer: processing...
flashplugin-installer: downloading 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20161026.1.orig.tar.gz
Get:1 
http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20161026.1.orig.tar.gz
 [27,2 MB]
Fetched 27,2 MB in 25s (1.085 kB/s) 


W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20161026.1.orig.tar.gz'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
Installing from local file 
/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20161026.1.orig.tar.gz
Flash Plugin installed.
ttf-mscorefonts-installer: processing...
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/andale32.exe
Get:1 http://downloads.sourceforge.net/corefonts/andale32.exe [198 kB]
Fetched 198 kB in 2s (96,3 kB/s)
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/arial32.exe
Get:1 http://downloads.sourceforge.net/corefonts/arial32.exe [554 kB]
Fetched 554 kB in 2s (248 kB/s) 
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/arial32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/arialb32.exe
Get:1 http://downloads.sourceforge.net/corefonts/arialb32.exe [168 kB]
Fetched 168 kB in 2s (71,9 kB/s)
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/arialb32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/comic32.exe
Get:1 http://downloads.sourceforge.net/corefonts/comic32.exe [246 kB]
Fetched 246 kB in 2s (95,3 kB/s)
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/comic32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/courie32.exe
Get:1 http://downloads.sourceforge.net/corefonts/courie32.exe [646 kB]
Fetched 646 kB in 2s (273 kB/s) 
   
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/georgi32.exe
Get:1 http://downloads.sourceforge.net/corefonts/georgi32.exe [392 kB]
Fetched 392 kB in 1s (233 kB/s) 
  
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/georgi32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/impact32.exe
Get:1 http://downloads.sourceforge.net/corefonts/impact32.exe [173 kB]
Fetched 173 kB in 1s (125 kB/s) 
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/impact32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/times32.exe
Get:1 http://downloads.sourceforge.net/corefonts/times32.exe [662 kB]
Fetched 662 kB in 2s (314 kB/s) 
 
W: Can't drop privileges for downloading as file 
'/var/lib/update-notifier/package-data-downloads/partial/times32.exe' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
ttf-mscorefonts-installer: downloading 
http://downloads.sourceforge.net/corefonts/trebuc32.exe
Get:1 http://downloads.sourceforge.net/corefonts/trebuc32.exe [357 kB]
Fetched 357 kB in 1s (212 kB/s) 
  

[Touch-packages] [Bug 1621826] Re: Unity8 does not remember user's preference of Windowed mode

[Pablo Marlasca]

Good news then, thanks! ;)

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

Title:
  Unity8 does not remember user's preference of Windowed mode

Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Hi there :)

  I think there's a weird and inconsistent behaviour when it comes to
  USB mouse. Currently, if I take my phone and plug in a mouse, it stays
  in Staged Mode (no windows). I have to manually open a Unity Tweak app
  and switch to Windowed Mode. However, once in windowed mode, if I
  disconnect the mouse, it automatically changes back to Staged mode.

  I think this is inconsistent. If I have a phone and connect a mouse,
  the only reason I would do it is to manage windows; Windowed Mode
  should be activated automatically. And of course, just like it happens
  currently, when I retire that mouse it should change to Staged Mode.

  I think this would be the most "logic" behaviour. If for any reason
  you don't consider it a right choice, maybe we could have at least an
  indicator switcher to make it easier to switch between both modes.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1621826/+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 1621826] [NEW] Windowed Mode doesn't start automatically when connecting a mouse

[Pablo Marlasca]

Public bug reported:

Hi there :)

I think there's a weird and inconsistent behaviour when it comes to USB
mouse. Currently, if I take my phone and plug in a mouse, it stays in
Staged Mode (no windows). I have to manually open a Unity Tweak app and
switch to Windowed Mode. However, once in windowed mode, if I disconnect
the mouse, it automatically changes back to Staged mode.

I think this is inconsistent. If I have a phone and connect a mouse, the
only reason I would do it is to manage windows; Windowed Mode should be
activated automatically. And of course, just like it happens currently,
when I retire that mouse it should change to Staged Mode.

I think this would be the most "logic" behaviour. If for any reason you
don't consider it a right choice, maybe we could have at least an
indicator switcher to make it easier to switch between both modes.

Thank you!

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

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

Title:
  Windowed Mode doesn't start automatically when connecting a mouse

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi there :)

  I think there's a weird and inconsistent behaviour when it comes to
  USB mouse. Currently, if I take my phone and plug in a mouse, it stays
  in Staged Mode (no windows). I have to manually open a Unity Tweak app
  and switch to Windowed Mode. However, once in windowed mode, if I
  disconnect the mouse, it automatically changes back to Staged mode.

  I think this is inconsistent. If I have a phone and connect a mouse,
  the only reason I would do it is to manage windows; Windowed Mode
  should be activated automatically. And of course, just like it happens
  currently, when I retire that mouse it should change to Staged Mode.

  I think this would be the most "logic" behaviour. If for any reason
  you don't consider it a right choice, maybe we could have at least an
  indicator switcher to make it easier to switch between both modes.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1621826/+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 1618540] [NEW] Delay of 1 second to open an app after clicking on the launcher

[Pablo Marlasca]

Public bug reported:

Hi, it's been a week or so that I noticed that apps no longer open
instantly once you click on them in the Unity launcher; it takes around
one second to see it open and start loading. This didn't happen before,
and gives the user a weird feeling of "maybe I didn't tap well on the
icon".

I'm on rc-proposed, BQ E4.5

Thanks :)

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

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

Title:
  Delay of 1 second to open an app after clicking on the launcher

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi, it's been a week or so that I noticed that apps no longer open
  instantly once you click on them in the Unity launcher; it takes
  around one second to see it open and start loading. This didn't happen
  before, and gives the user a weird feeling of "maybe I didn't tap well
  on the icon".

  I'm on rc-proposed, BQ E4.5

  Thanks :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1618540/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Pablo Carranza]

Thanks for sponsoring Mike!

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in dbus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1591411/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Pablo Carranza]

And Łukasz :)

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in dbus package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in dbus source package in Xenial:
  New
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1591411/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay

[Pablo Carranza]

Hi, for back reference you can see our progress in the GitLab.com issue:
https://gitlab.com/gitlab-com/infrastructure/issues/290

You can see a graph of behavior before and after the dbus update and the
host reboot here: https://gitlab.com/gitlab-
com/infrastructure/issues/290#note_13607928

I think that the is a lot of value on getting this into ubuntu LTS
because it will solve the lockups for ssh session creations under heavy
load.

You can check realtime behavior here:
http://monitor.gitlab.net/dashboard/db/gitlab-status

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

Title:
  systemd-logind must be restarted every ~1000 SSH logins to prevent a
  ~25 second delay

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I noticed on a system that accepts large numbers of SSH connections
  that after awhile, SSH sessions were taking ~25 seconds to complete.

  Looking in /var/log/auth.log, systemd-logind starts failing with the
  following:

  Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for 
user ubuntu by (uid=0)
  Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu.
  Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: 
Transport endpoint is not connected
  Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create 
session: Message recipient disconnected from message bus without replying

  I reproduced this in an LXD container by doing something like:

  lxc launch ubuntu:x test
  lxc exec test -- login -f ubuntu
  ssh-import-id 

  Then ran a script as follows (passing in ubuntu@):

  while [ 1 ]; do
  (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log
  done

  In my case, after 1052 logins, the 1053rd and thereafter were taking
  25+ seconds to complete. Here are some snippets from the log file:

  $ cat log | grep 0m0 | wc -l
  1052

  $ cat log | grep 0m25 | wc -l
  4

  $ tail -5 log
  real  0m0.222s
  real  0m25.232s
  real  0m25.235s
  real  0m25.236s
  real  0m25.239s

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Jun 11 00:09:34 2016
  MachineType: Notebook W230SS
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W230SS
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W230SS
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1591411/+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 1597290] Re: Wallpapers in Windowed Mode are not scaled correctly

[Pablo Marlasca]

Yes, I understand that scaling method, but what I mean is that even
using a 4K landscape wallpaper, when the phone screen is vertical it
looks very blurry (it is not a resolution issue). My phone is a BQ E4.5
(maybe it only happens with this phone model?).

The problem is that the only way of having a sharp background image is
when the screen orientation coincides with the picture "format"
(portrait or landscape).

I attach a screenshot to show the problem: it is a high resolution
landscape wallpaper (2483x1553) that looks blurry when the phone screen
is vertical. The Gallery app is open to show that the same picture looks
much better in it than in the background. Thanks!!

** Attachment added: "screenshot20160630_231806610.png"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1597290/+attachment/4693180/+files/screenshot20160630_231806610.png

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

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1597290/+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 1597290] [NEW] Wallpapers in Windowed Mode are not scaled correctly

[Pablo Marlasca]

Public bug reported:

When you set a new wallpaper from the Settings App, if it's a landscape
wallpaper it will be well scaled if the phone screen is horizontal, but
when it's vertical it will look blurry. When the wallpaper is a portrait
picture, it happens the opposite: it is well scaled if the screen is
vertical but when you rotate it, the wallpaper is blurry. Thanks ;)

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

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

Title:
  Wallpapers in Windowed Mode are not scaled correctly

Status in unity8 package in Ubuntu:
  New

Bug description:
  When you set a new wallpaper from the Settings App, if it's a
  landscape wallpaper it will be well scaled if the phone screen is
  horizontal, but when it's vertical it will look blurry. When the
  wallpaper is a portrait picture, it happens the opposite: it is well
  scaled if the screen is vertical but when you rotate it, the wallpaper
  is blurry. Thanks ;)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1597290/+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 1547990] [NEW] 5.1 output not appearing in system settings->sound ubuntu 14.04

[Pablo]

Public bug reported:

Here is my alsa information http://www.alsa-
project.org/db/?f=28d4f08505741656bfb1905b7bc21e20365ae5de

I am currently outputting audio through SPDIF to a 5.1 system, but I
only get stereo pcm audio option in system settings->sound. I can see no
5.1 ac3 output. I could however see it for a brief time whenever I
logged in as guest or created a new account. Now, the 5.1 output appears
not even there, it just vanished. I followed these instructions to no
avail:

https://help.ubuntu.com/community/DigitalAC-3Pulseaudio

Thanks in advance.

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

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

Title:
  5.1 output not appearing in system settings->sound ubuntu 14.04

Status in alsa-utils package in Ubuntu:
  New

Bug description:
  Here is my alsa information http://www.alsa-
  project.org/db/?f=28d4f08505741656bfb1905b7bc21e20365ae5de

  I am currently outputting audio through SPDIF to a 5.1 system, but I
  only get stereo pcm audio option in system settings->sound. I can see
  no 5.1 ac3 output. I could however see it for a brief time whenever I
  logged in as guest or created a new account. Now, the 5.1 output
  appears not even there, it just vanished. I followed these
  instructions to no avail:

  https://help.ubuntu.com/community/DigitalAC-3Pulseaudio

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1547990/+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 1545838] [NEW] package account-plugin-facebook (not installed) failed to install/upgrade: intentando sobreescribir `/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que es

[Juan Pablo Morelli]

Public bug reported:

Was un-installing kubuntu-desktop and returning to Ubuntu-desktop
configuration

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: account-plugin-facebook (not installed)
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Mon Feb 15 09:46:37 2016
DuplicateSignature: package:account-plugin-facebook:(not installed):intentando 
sobreescribir `/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está 
también en el paquete kaccounts-providers 4:15.08.2-0ubuntu1
ErrorMessage: intentando sobreescribir 
`/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está también en el 
paquete kaccounts-providers 4:15.08.2-0ubuntu1
InstallationDate: Installed on 2016-02-10 (4 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5.1
 apt  1.0.10.2ubuntu1
SourcePackage: account-plugins
Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: intentando sobreescribir 
`/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está también en el 
paquete kaccounts-providers 4:15.08.2-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: account-plugins (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package account-plugin-facebook (not installed) failed to
  install/upgrade: intentando sobreescribir `/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', que está también en el paquete
  kaccounts-providers 4:15.08.2-0ubuntu1

Status in account-plugins package in Ubuntu:
  New

Bug description:
  Was un-installing kubuntu-desktop and returning to Ubuntu-desktop
  configuration

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: account-plugin-facebook (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 15 09:46:37 2016
  DuplicateSignature: package:account-plugin-facebook:(not 
installed):intentando sobreescribir 
`/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está también en el 
paquete kaccounts-providers 4:15.08.2-0ubuntu1
  ErrorMessage: intentando sobreescribir 
`/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está también en el 
paquete kaccounts-providers 4:15.08.2-0ubuntu1
  InstallationDate: Installed on 2016-02-10 (4 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5.1
   apt  1.0.10.2ubuntu1
  SourcePackage: account-plugins
  Title: package account-plugin-facebook (not installed) failed to 
install/upgrade: intentando sobreescribir 
`/etc/signon-ui/webkit-options.d/www.facebook.com.conf', que está también en el 
paquete kaccounts-providers 4:15.08.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1545838/+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 1341256] Re: Press caps lock on bluetooth keyboard then the keyboard go death

[Juan Pablo Villa Russell]

It's been more than a year but is there any news on this? Same problem
with:

Microsoft Sculpt Mobile Keyboard

The only line that I got from dmesg after turning the keyboard off and on again 
is:
unknown main item tag 0x0


Also, the bluetooth keyboard stops responding when pressing caps lock in the 
Bluetooth Keyboard or on a usb keyboard

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

Title:
  Press caps lock on bluetooth keyboard then the keyboard go death

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am typing using the Apple wireless keyboard,When I press 'caps lock',the 
keyboard don't work any more!
  So I go use keyboard on the Macbook.The key case have change,but the light on 
the key do not light on.
  I have to off the bluetooth then make it on again.Then reconnect the wireless 
keyboard.
  Yes,It work again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: bluez 4.101-0ubuntu13
  ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4
  Uname: Linux 3.16.0-3-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 13 17:12:23 2014
  InstallationDate: Installed on 2014-03-08 (126 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140307)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Apple Inc. MacBookPro9,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-3-generic.efi.signed 
root=UUID=6510f595-2f49-4798-953a-ed186346c60d ro irqpoll
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B08.1208081132
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-4B7AC7E43945597E
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-4B7AC7E43945597E
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B08.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
  dmi.product.name: MacBookPro9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 7C:D1:C3:79:A7:25  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:119665 acl:5720 sco:0 events:2443 errors:0
TX bytes:13420 acl:640 sco:0 commands:718 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1341256/+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 982283] Re: Modem is not detected (ever, or for several minutes); computer sometimes freezes; modem-manager sometimes crashes -- Huawei E160

[Pablo]

Try this:

sudo modprobe -r option; sudo modprobe -r usb_wwan; sudo modprobe -r
usbserial; sudo modprobe usbserial vendor=0x12d1 product=0x1003

It worked for me some time ago.
I don't remember if I should plug the stick before, type the command, unplug 
and plug it again, or not.

It also worked to append the modprobe commands to the   /etc/rc.local
file

Good luck

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

Title:
  Modem is not detected (ever, or for several minutes); computer
  sometimes freezes; modem-manager sometimes crashes -- Huawei E160

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Huawei e160 modem isn't consistently detected. It's a hit and miss affair. 
Sometimes requires several attempts of plugging in and out.
  This modem also has a MicroSD card slot and this is probably what is causing 
the issue. However, no additional drive is reported or mounted automatically.
  It just takes 2-5 minutes for the modem to be detected. Following which 
running it is usually hassle free. 

  Using ubuntu 12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.4.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu3
  Architecture: amd64
  Date: Sun Apr 15 17:48:06 2012
  InstallationMedia: This
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 112.79.128.134 
   169.254.0.0/16 dev ppp0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-03-18 (28 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   ttyUSB1gsm   connected 
/org/freedesktop/NetworkManager/Devices/3  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   disconnected  
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled enabled
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC665 Analog [ALC665 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rishi  2189 F pulseaudio
   /dev/snd/controlC0:  rishi  2189 F pulseaudio
   /dev/snd/pcmC0D0p:   rishi  2189 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf0a0 irq 57'
 Mixer name : 'Realtek ALC665'
 Components : 'HDA:10ec0665,1028046e,0013'
 Controls  : 25
 Simple ctrls  : 12
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 17'
 Mixer name : 'Nvidia GPU 14 HDMI/DP'
 Components : 'HDA:10de0014,10de0101,00100100'
 Controls  : 24
 Simple ctrls  : 4
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=cc0cdc76-9415-4970-9655-ebde53ae90cf
  InstallationMedia: This
  IpRoute:
   default via 192.168.2.1 dev wlan0  proto static 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.104  
metric 2
  KnownReport: https://bugs.launchpad.net/bugs/452814
  MachineType: Dell Inc. XPS L501X
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  NonfreeKernelModules: nvidia
  Package: network-manager 0.9.4.0-0ubuntu3
  PackageArchitecture: amd64
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic 
root=UUID=c6230f54-6e0e-4a44-9ad2-f195df33ec06 ro 
resume=UUID=cc0cdc76-9415-4970-9655-ebde53ae90cf quiet splash
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-23-generic N/A
   linux-backports-modules-3.2.0-23-generic  N/A
   linux-firmware1.79
  StagingDrivers: mei
  Tags:  precise staging precise
  Uname: Linux 3.2.0-23-generic x86_64
  UpgradeStatus: Upgraded to precise on 2012-03-18 (39 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0J1VR3
  dmi.board.vendor: 

[Touch-packages] [Bug 1322925] Re: [SRU] Copy, paste stops working randomly in Ubuntu 14.04 nautilus

[Pablo Guevara]

This bug affects me on Ubuntu 14.04.3 LTS

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

Title:
  [SRU] Copy, paste stops working randomly in Ubuntu 14.04 nautilus

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in nautilus source package in Trusty:
  Fix Released
Status in xorg source package in Trusty:
  Confirmed
Status in nautilus source package in Utopic:
  Fix Released
Status in xorg source package in Utopic:
  Confirmed

Bug description:
  The title says it.

  Since upgrade to 14.04, copy / cut / paste of files among various
  folders I have write rights on does not work most of the times.

  Using the terminal to copy / move does work normally.

  nautilus:
Installed: 1:3.10.1-0ubuntu9.1
Candidate: 1:3.10.1-0ubuntu9.1
Version table:
   *** 1:3.10.1-0ubuntu9.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.10.1-0ubuntu8 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

  [Test Case]

  1. Open a Nautilus window and switch to List view
  2. Go to location with write permission
  3. Select a file and try to rename.
  4. When prompted to rename (filename becomes a text entry), open new tab.
  5. Select a file, try to copy and paste. You will see that file is not copied 
and pasted.
  6. Go back to original tab. If the file that was selected in step 3 is still 
selected, unselect it.
  7. Try to copy and paste. It should work.
  8. Try to rename again, and open new tab.
  9. Close old tab, and try to copy and paste. It won't work, and there is no 
way to restore, except opening a new window.

  [Regression Potential]

  Already fixed upstream with
  
https://git.gnome.org/browse/nautilus/commit/?id=8032628adc9c8286050716d609c574dc7273dfcb

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1322925/+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 1466137] Re: unity --replace kills my session

[Pablo]

Is this a duplicate of 1449959? That one has been fixed in gnome-
session3.14.0-2ubuntu5

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

Title:
  unity --replace kills my session

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Running "unity --replace" from the HUD or Dash causes my whole session
  to be killed. Rather than just simply restarting the unity
  applications, I'm punted back to the login window and all my running
  apps are dead.

  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.04
  Release:  15.04
  Codename: vivid

  
  dpkg --list | grep unity
  ii  gir1.2-unity-5.0:amd64   
7.1.4+14.10.20140808-0ubuntu1  amd64GObject introspection 
data for the Unity library
  ii  libmeanwhile11.0.2-5  
  amd64open implementation of the Lotus Sametime 
Community Client protocol
  ii  libunity-action-qt1:amd64
1.1.0+14.04.20140304-0ubuntu1  amd64Unity Action Qt API
  ii  libunity-control-center1 
15.04.0+15.04.20150410-0ubuntu1amd64utilities to configure 
the GNOME desktop
  ii  libunity-core-6.0-9  
7.3.2+15.04.20150420-0ubuntu1  amd64core library for the 
Unity interface
  ii  libunity-gtk2-parser0:amd64  
0.0.0+15.04.20150118-0ubuntu1  amd64GtkMenuShell to 
GMenuModel parser
  ii  libunity-gtk3-parser0:amd64  
0.0.0+15.04.20150118-0ubuntu1  amd64GtkMenuShell to 
GMenuModel parser
  ii  libunity-misc4   
4.0.5+14.04.20140115-0ubuntu1  amd64Miscellaneous functions 
for Unity - shared library
  ii  libunity-protocol-private0:amd64 
7.1.4+14.10.20140808-0ubuntu1  amd64binding to get places 
into the launcher - private library
  ii  libunity-scopes-json-def-desktop 
7.1.4+14.10.20140808-0ubuntu1  all  binding to get places 
into the launcher - desktop def file
  ii  libunity-settings-daemon1
15.04.1+15.04.20150408-0ubuntu1amd64Helper library for 
accessing settings
  rc  libunity-webapps0
2.5.0~+14.04.20140409-0ubuntu1 amd64Web Apps integration 
with the Unity desktop
  ii  libunity9:amd64  
7.1.4+14.10.20140808-0ubuntu1  amd64binding to get places 
into the launcher - shared library
  ii  libunityvoice1:amd64 
0.1+15.04.20150416-0ubuntu1amd64client library for 
Unity voice service
  ii  qtdeclarative5-unity-action-plugin:amd64 
1.1.0+14.04.20140304-0ubuntu1  amd64Unity Action QML 
Components
  ii  unity
7.3.2+15.04.20150420-0ubuntu1  amd64Interface designed for 
efficiency of space and interaction.
  ii  unity-asset-pool 
0.8.24+15.04.20141217-0ubuntu2 all  Unity Assets Pool
  ii  unity-control-center 
15.04.0+15.04.20150410-0ubuntu1amd64utilities to configure 
the GNOME desktop
  ii  unity-control-center-signon  
0.1.7~+14.10.20140814-0ubuntu1 amd64Unity Control Center 
extension for single signon
  ii  unity-greeter15.04.4-0ubuntu1 
  amd64Unity Greeter
  ii  unity-gtk-module-common  
0.0.0+15.04.20150118-0ubuntu1  all  Common files for 
GtkMenuShell D-Bus exporter
  ii  unity-gtk2-module:amd64  
0.0.0+15.04.20150118-0ubuntu1  amd64GtkMenuShell D-Bus 
exporter
  ii  unity-gtk3-module:amd64  
0.0.0+15.04.20150118-0ubuntu1  amd64GtkMenuShell D-Bus 
exporter
  ii  unity-lens-applications  
7.1.0+13.10.20131011-0ubuntu2  amd64Application lens for 
unity
  ii  unity-lens-files 
7.1.0+13.10.20130920-0ubuntu1  amd64File lens for unity
  ii  unity-lens-music 
6.9.0+15.04.20141219-0ubuntu1  amd64Music lens for unity
  ii  unity-lens-photos
1.0+14.04.20140318-0ubuntu1all  Photos lens for Unity
  ii  

[Touch-packages] [Bug 1486483] [NEW] package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: el subproceso instalado el script post-removal devolvió el código de salida de error 1

[Juan Pablo Sarmiento]

Public bug reported:

I can't access to desktop by lightdm after upgrade to 14.04. 
I can access by gdm.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: lightdm 1.10.5-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.11
AptOrdering:
 ubuntu-desktop: Purge
 lightdm: Purge
Architecture: amd64
Date: Wed Aug 19 11:29:04 2015
DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:el subproceso instalado 
el script post-removal devolvió el código de salida de error 1
ErrorMessage: el subproceso instalado el script post-removal devolvió el código 
de salida de error 1
InstallationDate: Installed on 2011-06-25 (1515 days ago)
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
SourcePackage: lightdm
Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: el 
subproceso instalado el script post-removal devolvió el código de salida de 
error 1
UpgradeStatus: Upgraded to trusty on 2015-08-14 (4 days ago)

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


** Tags: amd64 apport-package trusty

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

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

Status in lightdm package in Ubuntu:
  New

Bug description:
  I can't access to desktop by lightdm after upgrade to 14.04. 
  I can access by gdm.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.5-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.11
  AptOrdering:
   ubuntu-desktop: Purge
   lightdm: Purge
  Architecture: amd64
  Date: Wed Aug 19 11:29:04 2015
  DuplicateSignature: package:lightdm:1.10.5-0ubuntu1.1:el subproceso instalado 
el script post-removal devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-removal devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2011-06-25 (1515 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: lightdm
  Title: package lightdm 1.10.5-0ubuntu1.1 failed to install/upgrade: el 
subproceso instalado el script post-removal devolvió el código de salida de 
error 1
  UpgradeStatus: Upgraded to trusty on 2015-08-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1486483/+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 1421889] Re: Ubuntu Touch 15.05 (r1) - Google Contacts not synchronizing

[Pablo]

I've got the same problem in my Meizu MX4 and my BQ4.5.

I tried to desactivate 2factor and delete the Google Account Permission,
and try again, and the same.

In my phone appear 7 random contacts. My Google account have almost 100
contacts, and always see only this 7 contacts.

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

Title:
  Ubuntu Touch 15.05 (r1) - Google Contacts not synchronizing

Status in address-book-app package in Ubuntu:
  Confirmed

Bug description:
  Device: Nexus 4
  OS: Ubuntu Touch 15.04 (r1) 
  Channel: devel

  Steps:
  1.)  Access Contacts app from apps scope
  2.) Prompt: Would you like to sync contacts from your google online accounts 
now?
  3.) Tap Yes
  4.) Enter Google account email and password
  5.) Screen: Ubuntu would like to: Have offline access
  6.) Accept
  7.) Pop-up: Synchronization: Start Sync
  8.) Pop-up: Synchronization: Done

  Expected: Google contacts to appear on Phone

  Result: No contacts appear on phone

  Additionally attempted manual refresh by tapping to refresh button
  Contacts, still no contacts synced.

  Under System Settings -- Accounts -- Google -- Contacts has a check
  mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1421889/+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 1465961] [NEW] Ubuntu shape sometimes becomes pixelated in OTA-4

[Pablo Marlasca]

Public bug reported:

Hi, I have noticed a refinement in Ubuntu shape icons in launcher and
menus in OTA-4, since they now look smoother than before.

However, about 5 or 6 times a day, since I installed the OTA-4 I have
also noticed that sometimes when you make the launcher appear or unlock
the phone, the shape of the icons (launcher and scopes) appears very
pixelated (I attach a pic to illustrate that). It get solved just by
hiding the launcher and showing it again, and the icons are again
correctly shaped. Can you please fix this?

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


** Tags: icon icons pixelated shape smooth ubuntu

** Attachment added: Pixelated Ubuntu shape
   
https://bugs.launchpad.net/bugs/1465961/+attachment/4416130/+files/screenshot20150616_195808064.png

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

Title:
  Ubuntu shape sometimes becomes pixelated in OTA-4

Status in unity8 package in Ubuntu:
  New

Bug description:
  Hi, I have noticed a refinement in Ubuntu shape icons in launcher and
  menus in OTA-4, since they now look smoother than before.

  However, about 5 or 6 times a day, since I installed the OTA-4 I have
  also noticed that sometimes when you make the launcher appear or
  unlock the phone, the shape of the icons (launcher and scopes) appears
  very pixelated (I attach a pic to illustrate that). It get solved just
  by hiding the launcher and showing it again, and the icons are again
  correctly shaped. Can you please fix this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465961/+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 1074706] Re: When closing a window in spread mode, the 'confirm' dialog box is hidden

[Pablo Almeida]

What do you think is needed to fix this? Don't we have a way to check if
a dialog has been created by a Window?

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

Title:
  When closing a window in spread mode, the 'confirm' dialog box is
  hidden

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Hi, everybody. I'm using Ubuntu 12.10, 32 bits (upgraded from 12.04
  some days ago).

  I have noticed that the spread mode now adds a button to allow closing
  windows for any app that has two or more open windows.  However, this
  new feature doesn't behave the best way.

  For example:  open two or more Firefox windows, and then open two or more 
tags inside all of them. Then, try to close any of the open windows by clicking 
the close button that is provided in the spread mode. A dialog box will emerge, 
asking you if you really want to close that window, because it has many open 
tags. The problem is that the dialog box will hide 'somewhere', forcing you to 
get out the spread in order to confirm and finally close the selected window. 
  You will see the same behaviour if you have, for example, two or more unsaved 
LibreOffice Writer documents, and then try to close any of them using the 
spread close button. The dialog box asking you if you want to save the changes 
before closing will appear (only for a while) and will immediately hide.

  Those dialog boxes should appear over the spread mode, and should
  never hide until the user confirms (or not) if he really wants to
  close the selected window.

  Please, fix it.
  Unity is becoming better, but there is still a lot of work to be done.

  Kind regards.
  Roberto.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1074706/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

[Pablo Piaggio]

This affects me.

14.04 trying to connect through ssh to 12.04. Both 64bits.

It stops at the the line: debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

Please help.

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv host is failing for me where host is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server-client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client-server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty host

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1437598] [NEW] Sound-Indicator should provide more advanced options

[Pablo Marlasca]

Public bug reported:

Device: BQ Aquaris E4.5 Ubuntu Edition
OS: Ubuntu 14.10 (r20)

I really love the new experience with the scrollable indicators at the
top panel. They give the possibility to have a lot more room for each
category while being easily accesible. This is why each indicator should
take advantage of this and put all the screen size into good use. Sound
indicator is one of those. I'll explain:

When you scroll down the sound indicator, it just gives you the option
of volume level. But this is a bit confusing as you don't actually
know if you are changing the volume for incoming calls, notifications,
music/games, alarms... So I think this should be expanded and provide
different controls for each category (as I show in the mockup pic I
attach).

If this was implemented, the user would be able to easily change the
volume and vibrating for each type of alert: calls, notifications, media
and alarms. Easy on the eye, accesible with one touch even from blocked
device. Simple. No need for complex Priority or At work or any other
modes as in other OS.

Activating Silence mode button would just make the four categories
mute and vibrating-less, and inactivating the button the controls would
just revert to their last previous state. If from silence mode you
activate one vibration or level up some volume, the button would
automatically turn off as there is no silence mode any more.

Hope you can implement something like this soon in future system
updates, since it's really needed to make basic sound settings much more
clear and easy for the eye. As Shuttleworth would say, Sound settings
at your fingertips :)

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


** Tags: bq options sound sound-indicator volume

** Attachment added: This is how it could look like in action
   https://bugs.launchpad.net/bugs/1437598/+attachment/4358630/+files/sonido.png

** Description changed:

  Device: BQ Aquaris E4.5 Ubuntu Edition
  OS: Ubuntu 14.10 (r20)
  
  I really love the new experience with the scrollable indicators at the
  top panel. They give the possibility to have a lot more room for each
  category while being easily accesible. This is why each indicator should
  take advantage of this and put all the screen size into good use. Sound
  indicator is one of those. I'll explain:
  
  When you scroll down the sound indicator, it just gives you the option
  of volume level. But this is a bit confusing as you don't actually
  know if you are changing the volume for incoming calls, notifications,
  music/games, alarms... So I think this should be expanded and provide
- different controls for each category (as I show in the mockup I attach).
+ different controls for each category (as I show in the mockup pic I
+ attach).
  
  If this was implemented, the user would be able to easily change the
  volume and vibrating for each type of alert: calls, notifications, media
  and alarms. Easy on the eye, accesible with one touch even from blocked
  device. Simple. No need for complex Priority or At work or any other
  modes as in other OS.
  
  Activating Silence mode button would just make the four categories
  mute and vibrating-less, and inactivating the button the controls would
  just revert to their last previous state. If from silence mode you
  activate one vibration or level up some volume, the button would
  automatically turn off as there is no silence mode any more.
  
  Hope you can implement something like this soon in future system
  updates, since it's really needed to make basic sound settings much more
  clear and easy for the eye. As Shuttleworth would say, Sound settings
  at your fingertips :)

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

Title:
  Sound-Indicator should provide more advanced options

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Device: BQ Aquaris E4.5 Ubuntu Edition
  OS: Ubuntu 14.10 (r20)

  I really love the new experience with the scrollable indicators at the
  top panel. They give the possibility to have a lot more room for each
  category while being easily accesible. This is why each indicator
  should take advantage of this and put all the screen size into good
  use. Sound indicator is one of those. I'll explain:

  When you scroll down the sound indicator, it just gives you the option
  of volume level. But this is a bit confusing as you don't actually
  know if you are changing the volume for incoming calls, notifications,
  music/games, alarms... So I think this should be expanded and
  provide different controls for each category (as I show in the mockup
  pic I attach).

  If this was implemented, the user would be able to easily change the
  volume and vibrating for each type of alert: calls, notifications,
  media and alarms. Easy on the eye, accesible with one touch 

[Touch-packages] [Bug 1411641] [NEW] package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-li

[Pablo W]

Public bug reported:

Sorry, no further information available.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libgtk-3-0 3.10.8-0ubuntu1.3
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Fri Jan 16 09:25:54 2015
DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1.3:cannot copy extracted 
data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
InstallationDate: Installed on 2015-01-08 (7 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: gtk+3.0
Title: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot
  copy extracted data for './usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8' to '/usr/lib/i386-linux-
  gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file or stream

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Sorry, no further information available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgtk-3-0 3.10.8-0ubuntu1.3
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Fri Jan 16 09:25:54 2015
  DuplicateSignature: package:libgtk-3-0:3.10.8-0ubuntu1.3:cannot copy 
extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  InstallationDate: Installed on 2015-01-08 (7 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: gtk+3.0
  Title: package libgtk-3-0 3.10.8-0ubuntu1.3 failed to install/upgrade: cannot 
copy extracted data for './usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8' to 
'/usr/lib/i386-linux-gnu/libgtk-3.so.0.1000.8.dpkg-new': unexpected end of file 
or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1411641/+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 1408710] [NEW] package evolution-data-server 3.10.4-0ubuntu1.5 failed to install/upgrade: cannot copy extracted data for './usr/lib/evolution-data-server/addressbook-backends/lib

[Pablo W]

Public bug reported:

Sorry. No further details available.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: evolution-data-server 3.10.4-0ubuntu1.5
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Thu Jan  8 13:13:32 2015
DuplicateSignature: package:evolution-data-server:3.10.4-0ubuntu1.5:cannot copy 
extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
InstallationDate: Installed on 2015-01-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: evolution-data-server
Title: package evolution-data-server 3.10.4-0ubuntu1.5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package evolution-data-server 3.10.4-0ubuntu1.5 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/evolution-
  data-server/addressbook-backends/libebookbackendwebdav.so' to
  '/usr/lib/evolution-data-server/addressbook-
  backends/libebookbackendwebdav.so.dpkg-new': unexpected end of file or
  stream

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Sorry. No further details available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: evolution-data-server 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Thu Jan  8 13:13:32 2015
  DuplicateSignature: package:evolution-data-server:3.10.4-0ubuntu1.5:cannot 
copy extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
  InstallationDate: Installed on 2015-01-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: evolution-data-server
  Title: package evolution-data-server 3.10.4-0ubuntu1.5 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so' 
to 
'/usr/lib/evolution-data-server/addressbook-backends/libebookbackendwebdav.so.dpkg-new':
 unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1408710/+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 1408716] [NEW] package python3-apport 2.14.1-0ubuntu3.6 failed to install/upgrade: cannot copy extracted data for './usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.p

[Pablo W]

Public bug reported:

Sorry. No further details available.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python3-apport 2.14.1-0ubuntu3.6
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Thu Jan  8 13:13:28 2015
DuplicateSignature: package:python3-apport:2.14.1-0ubuntu3.6:cannot copy 
extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
InstallationDate: Installed on 2015-01-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: apport
Title: package python3-apport 2.14.1-0ubuntu3.6 failed to install/upgrade: 
cannot copy extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package python3-apport 2.14.1-0ubuntu3.6 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/python3/dist-
  packages/apport/crashdb_impl/launchpad.py' to '/usr/lib/python3/dist-
  packages/apport/crashdb_impl/launchpad.py.dpkg-new': unexpected end of
  file or stream

Status in apport package in Ubuntu:
  New

Bug description:
  Sorry. No further details available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: python3-apport 2.14.1-0ubuntu3.6
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Thu Jan  8 13:13:28 2015
  DuplicateSignature: package:python3-apport:2.14.1-0ubuntu3.6:cannot copy 
extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2015-01-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: apport
  Title: package python3-apport 2.14.1-0ubuntu3.6 failed to install/upgrade: 
cannot copy extracted data for 
'./usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py' to 
'/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1408716/+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 1408714] [NEW] package libcamel-1.2-45 3.10.4-0ubuntu1.5 failed to install/upgrade: cannot copy extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to '/usr/lib/libcamel-1.2.so

[Pablo W]

Public bug reported:

Sorry. No further details available.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libcamel-1.2-45 3.10.4-0ubuntu1.5
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Thu Jan  8 13:13:33 2015
DuplicateSignature: package:libcamel-1.2-45:3.10.4-0ubuntu1.5:cannot copy 
extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to 
'/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
ErrorMessage: cannot copy extracted data for './usr/lib/libcamel-1.2.so.45.0.0' 
to '/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
InstallationDate: Installed on 2015-01-08 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
SourcePackage: evolution-data-server
Title: package libcamel-1.2-45 3.10.4-0ubuntu1.5 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to 
'/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package libcamel-1.2-45 3.10.4-0ubuntu1.5 failed to install/upgrade:
  cannot copy extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to
  '/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or
  stream

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  Sorry. No further details available.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libcamel-1.2-45 3.10.4-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Thu Jan  8 13:13:33 2015
  DuplicateSignature: package:libcamel-1.2-45:3.10.4-0ubuntu1.5:cannot copy 
extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to 
'/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/libcamel-1.2.so.45.0.0' to 
'/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2015-01-08 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  SourcePackage: evolution-data-server
  Title: package libcamel-1.2-45 3.10.4-0ubuntu1.5 failed to install/upgrade: 
cannot copy extracted data for './usr/lib/libcamel-1.2.so.45.0.0' to 
'/usr/lib/libcamel-1.2.so.45.0.0.dpkg-new': unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1408714/+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 1351642] Re: window alwalys on top malfunction launcher

[Pablo Gabriel Costela]

I activated the option minimize, under compiz manager

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

Title:
  window alwalys on top malfunction launcher

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Window always on top, malfunctioning, pressing pitcher on the
  application in question.

  For example, if we have two windows of the same application open and has the 
status of window always on top, pressing the icon that identifies it in the 
launcher, we should go through three states, namely, 1) show all windows.
  2) minimize windows.
  3) show one and then the other.
  In Section 3, is where one of the two is not shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1351642/+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 1351642] Re: window alwalys on top malfunction launcher

[Pablo Gabriel Costela]

because it is the way I handle the windows, as many users.
did you try?

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

Title:
  window alwalys on top malfunction launcher

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Window always on top, malfunctioning, pressing pitcher on the
  application in question.

  For example, if we have two windows of the same application open and has the 
status of window always on top, pressing the icon that identifies it in the 
launcher, we should go through three states, namely, 1) show all windows.
  2) minimize windows.
  3) show one and then the other.
  In Section 3, is where one of the two is not shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1351642/+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 1374825] Re: VDPAU does not work in libav on Utopic

[Pablo J. E. Rodriguez]

running:
mplayer -vo vdpau -vc ffh264vdpau -aspect 16:9 
http://bglive-a.bitgravity.com/twit/live/high

I get audio but no video and this message:

Forced video codec: ffh264vdpau
Cannot find codec 'h264_vdpau' in libavcodec...
Video decoder init failed for codecs.conf entry ffh264vdpau.

this command line works fine before I update from thrusty to utopic.

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  Invalid
Status in “mplayer” package in Ubuntu:
  Confirmed
Status in “mplayer2” package in Ubuntu:
  Confirmed
Status in “mpv” package in Ubuntu:
  Invalid
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Pablo]

got the same problem now with 14.10 official release.

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline] 
Modeline 15:1920x1080 

[Touch-packages] [Bug 1319490] Re: after install Nvidia-173 driver for trusty black sreen

[Pablo Ramirez]

Same here! Problem lies in this old video card. What I did:

Go to console (Ctrl + Alt + F1), login, then kill gdm, in my case,
lightdm:

sudo killall lightdm

Then, execute:

nvidia-xsettings

 This will create a basic xorg.conf into /etc/X11.

Now, install Gnome Flashback, wich brings two options to start Session:
Gnome Flashback (compiz) and Gnome Flashback (Metacity)

sudo apt-get install gnome-session-flashback

Then, restart gdm, in my case:

sudo service lightdm start

Now, in login screen, open the little foot in the upper right corner ,
and choose Gnome Flashback (metacity). This will allow to start a
session without compiz efects. You should now be able to start session
normally.

The problem here is that this old videocard cant handle Opengl and
Composite effects in new Xorg and kernels. Im trying hard to finetune my
xorg.conf, to see if I can make Compiz works. I will try to downgrade
kernel and Xorg too if necessary, but dont expect too much. If your
problem was you couldnt start session, this workaround should let you do
that. If you are expecting for Compiz to work (remember, Ubuntu desktop
and Gnome Flashback (Compiz), both uses Compiz), there are little
possibilities... but if I cant get it to work, i will let you know.
Sorry my english! Im Spanish speaker :P

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

Title:
  after install Nvidia-173 driver for trusty black sreen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  after install Nvidia-173 driver for trusty black sreen

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 14 19:18:28 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation Device [10de:01b9]
  InstallationDate: Installed on 2014-05-12 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Dell Computer Corporation Dimension 8300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=e5a5dd2c-a210-4eae-8011-361d62ca076b ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A02
  dmi.board.name: 0M2035
  dmi.board.vendor: Dell Computer Corp.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr:
  dmi.product.name: Dimension 8300
  dmi.sys.vendor: Dell Computer Corporation
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  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.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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May 14 18:37:39 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   input USB OPTICAL MOUSE   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nouveau (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nouveau (module does not exist, 0)
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: modesetting

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

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