[Touch-packages] [Bug 2039391] [NEW] pakage broken

[aditya raj ahirwar]

Public bug reported:

instaler pakage broken

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
Uname: Linux 5.4.0-164-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Oct 15 22:20:43 2023
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 intel-hid, 3.1, 4.4.0-210-generic, x86_64: installed
 oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-210-generic, x86_64: 
installed
 oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-210-generic, x86_64: 
installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
InstallationDate: Installed on 2023-07-12 (95 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 15-3568
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic 
root=UUID=ecd93531-cc0b-4642-b530-68a5e7081e61 ro acpi_rev_override 
locale=en_IN alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/19/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.0
dmi.board.name: 05HRPP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd04/19/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 15-3568
dmi.product.sku: 0793
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun Oct 15 21:52:15 2023
xserver.configfile: default
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.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.13-1ubuntu1~20.04.8

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


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

Title:
  pakage broken

Status in xorg package in Ubuntu:
  New

Bug description:
  instaler pakage broken

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
  Uname: Linux 5.4.0-164-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Oct 15 22:20:43 2023
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   intel-hid, 3.1, 4.4.0-210-generic, x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-210-generic, 
x86_64: installed
   oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-210-generic, x86_64: 
installed
  ExtraDebuggingInterest: I just need to 

[Touch-packages] [Bug 2031352] Re: Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

[Aditya Thyagarajan]

yes I'm experiencing the same issue.

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

Title:
  Ubuntu 22.04.3 LTS stuck on power-off/reboot screen

Status in linux-hwe-6.2 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux-hwe-6.2 source package in Jammy:
  Confirmed

Bug description:
  After updating to Kernel 6.2 a few days ago, I have been experiencing
  issues with my system's shutdown and reboot functions. During these
  processes, the system becomes unresponsive and hangs on a black
  screen, which displays both the Dell and Ubuntu logos. This issue is
  inconsistent; it happens sporadically. Currently, the only workaround
  I've found to successfully shut down the system is to forcibly power
  off the machine by holding down the power button for 5 seconds.

  I've also tested a fresh installation of Ubuntu 22.04.3.

  

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: systemd 249.11-0ubuntu3.9
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 14 22:41:14 2023
  InstallationDate: Installed on 2023-08-14 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 2023.08.13 LTS (20230813)
  MachineType: Dell Inc. XPS 8930
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic 
root=UUID=14d1ee7a-565f-4ba4-b6dd-7bc16e487451 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2023
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.30
  dmi.board.name: 0T88YD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.30:bd03/14/2023:br1.1:svnDellInc.:pnXPS8930:pvr1.1.30:rvnDellInc.:rn0T88YD:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:sku0859:
  dmi.product.family: XPS
  dmi.product.name: XPS 8930
  dmi.product.sku: 0859
  dmi.product.version: 1.1.30
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-08-13T20:57:27
  mtime.conffile..etc.systemd.system.conf: 2023-08-13T20:57:27

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2031352/+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 1971090] [NEW] OS fully crashes when I exit an app folder.

[Aditya Shah]

Public bug reported:

When I leave a app folder in a specific place, the OS crashes and I need
to do a force shut down to restart.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vim (not installed)
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun May  1 10:17:57 2022
InstallationDate: Installed on 2021-05-31 (334 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  OS fully crashes when I exit an app folder.

Status in vim package in Ubuntu:
  New

Bug description:
  When I leave a app folder in a specific place, the OS crashes and I
  need to do a force shut down to restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  1 10:17:57 2022
  InstallationDate: Installed on 2021-05-31 (334 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1971090/+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 1947329] [NEW] package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Aditya Sharma]

Public bug reported:

Pop up comes in just after turn on.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3 3.8.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Uname: Linux 5.4.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct 15 01:40:29 2021
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
InstallationDate: Installed on 2021-10-05 (10 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: python3-defaults
Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago)

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

Title:
  package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed
  python3 package post-installation script subprocess returned error
  exit status 4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Pop up comes in just after turn on.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
  Uname: Linux 5.4.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 15 01:40:29 2021
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2021-10-05 (10 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2021-10-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1947329/+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 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later

[Aditya]

This also affect me on Ubuntu 18.04.4 LTS with kernel 5.3.0-53-generic
  * AMD® Ryzen 7 3750h with radeon vega mobile gfx × 8 
  * GeForce GTX 1650/PCIe/SSE2

Rolling back to 5.3.0-51-generic will solves the problem

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

Title:
  Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel
  versions 5.3.0-52 and later

Status in DRI:
  Unknown
Status in libdrm package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed

Bug description:
  When booting up Ubuntu 18.04 with a kernel version of 5.3.0-52 or
  later (including 5.3.0-53), everything seems to be working as usual.
  However, when I shutdown, the system will only soft shutdown, with the
  CPU still running at full power, forcing me to hold down the power
  button to fully power off affected systems. If I reboot, it will cause
  the system to hang and not respond. Either way, a hard reset or
  poweroff will be required, and this is not an option for systems being
  remotely accessed. It is not possible for me to collect kernel logs at
  this point, unless something wrong is happening in those kernel
  versions before the actual shutdown.

  It is possible that this may also occur on Ubuntu 20.04 with kernel
  versions 5.4.0-29 and later, but I have not yet tested this out. This
  problem is occurring on both my desktop and laptop computers which
  respectively are:

  * AsRock B450 Pro4 with AMD Ryzen 3 3200G APU
  * Lenovo ThinkPad A485 with AMD Ryzen 5 Pro 2500U mobile APU

  In the meantime, I am stuck on kernel version 5.3.0-51, as that is the
  last working 5.3.x kernel version offered in the standard Ubuntu
  repositories that doesn't have this problem, without me having to use
  PPAs. I don't know if this problem also occurs on systems with Intel
  CPUs, as I don't own any recently-made system (last 3 years from 2017)
  with such CPUs to test if this problem occurs on them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1880041/+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 1881721] [NEW] Sound of my pc doesn't works 7483AG8, Analog Devices AD1882, Green Headphone Out, Front] No sound at all

[Aditya Pandey]

Public bug reported:

I setted sound using alsamixer on my Ubuntu Desktop but it works when i started 
pc & set sound using alsamixer using terminal for few times . After shutdown pc 
then i started pc then it doesn't work. 
How to solve sound problem permanently ?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  adityaastha  25030 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun  2 13:23:22 2020
InstallationDate: Installed on 2019-12-07 (177 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  adityaastha  25030 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [7483AG8, Analog Devices AD1882, Green Headphone Out, Front] No sound at 
all
UpgradeStatus: Upgraded to focal on 2020-05-25 (8 days ago)
dmi.bios.date: 09/07/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 5CKT54AUS
dmi.board.name: LENOVO
dmi.board.vendor: LENOVO
dmi.board.version: NONE
dmi.chassis.asset.tag: �
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT54AUS:bd09/07/2009:svnLENOVO:pn7483AG8:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.family: NONE
dmi.product.name: 7483AG8
dmi.product.sku: NONE
dmi.product.version: ThinkCentre M58p
dmi.sys.vendor: LENOVO
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-29T11:41:48.526522

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


** Tags: amd64 apport-bug focal

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

Title:
  Sound of my pc doesn't works  7483AG8, Analog Devices AD1882, Green
  Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I setted sound using alsamixer on my Ubuntu Desktop but it works when i 
started pc & set sound using alsamixer using terminal for few times . After 
shutdown pc then i started pc then it doesn't work. 
  How to solve sound problem permanently ?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adityaastha  25030 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun  2 13:23:22 2020
  InstallationDate: Installed on 2019-12-07 (177 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adityaastha  25030 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [7483AG8, Analog Devices AD1882, Green Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to focal on 2020-05-25 (8 days ago)
  dmi.bios.date: 09/07/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT54AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NONE
  dmi.chassis.asset.tag: �
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT54AUS:bd09/07/2009:svnLENOVO:pn7483AG8:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.family: NONE
  dmi.product.name: 7483AG8
  dmi.product.sku: NONE
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-29T11:41:48.526522

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

-- 
Mailing list: 

[Touch-packages] [Bug 1880296] [NEW] Unable to upate my graphic driver

[aditya]

Public bug reported:

I get an prompt regarding the graphic update process. I am unable to
update my graphic driver.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 23 16:10:00 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
   Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0456]
InstallationDate: Installed on 2020-03-22 (61 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. Inspiron N4010
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 050VP6
dmi.board.vendor: Dell Inc.
dmi.board.version: A13
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A13
dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/31/2011:svnDellInc.:pnInspironN4010:pvrA13:rvnDellInc.:rn050VP6:rvrA13:cvnDellInc.:ct8:cvrA13:
dmi.product.name: Inspiron N4010
dmi.product.version: A13
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
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

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


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

Title:
  Unable to upate my graphic driver

Status in xorg package in Ubuntu:
  New

Bug description:
  I get an prompt regarding the graphic update process. I am unable to
  update my graphic driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 23 16:10:00 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0456]
  InstallationDate: Installed on 2020-03-22 (61 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron N4010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A13
  dmi.board.name: 050VP6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A13
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A13
  dmi.modalias: 
dmi:bvnDellInc.:bvrA13:bd03/31/2011:svnDellInc.:pnInspironN4010:pvrA13:rvnDellInc.:rn050VP6:rvrA13:cvnDellInc.:ct8:cvrA13:
  dmi.product.name: Inspiron N4010
  dmi.product.version: A13
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  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/xorg/+bug/1880296/+subscriptions

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

[Touch-packages] [Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[aditya lele]

The only workaround that I have found till now is using a bluetooth
headset. It works perfectly well.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[aditya lele]

Same problem with Asus Zenbook UX533FD.

Also, can someone please specify the windows shutdown method?
"i.e. go to shutdown on the windows start menu and hold shift while pressing 
restart. A screen will appear where you can select to shutdown." This doesn't 
work.

I am dual booting Win10 and Ubuntu 18.04.

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/1784485/+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 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Aditya Kumar Praharaj]

I am also one of the affected users. I want to contribute towards fixing
this / writing enhancements in the ALSA / pulseaudio. How do I get
started with audio driver development?

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1672822/+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 367211] Re: sed -i destroys symlink

[Aditya Gnaneshwar]

can we have a similar option for a hard link file?

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

Title:
  sed -i destroys symlink

Status in sed package in Ubuntu:
  Fix Released

Bug description:
  When using 'sed -i' on a symlink the symlink gets destroyed.
  Observe:

  % ls -l myfile symlink
  -rw-rw-r-- 1 miekg miekg 12 Apr 26 10:53 myfile
  lrwxrwxrwx 1 miekg miekg  6 Apr 26 10:53 symlink -> myfile

  # do an edit
  % sed -i 's/hello//' symlink

  % ls -l myfile symlink
  -rw-rw-r-- 1 miekg miekg 12 Apr 26 10:53 myfile
  -rw-rw-r-- 1 miekg miekg  7 Apr 26 10:54 symlink

  And gone is your symlink.

  This either a feature or a bug :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sed/+bug/367211/+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 1704596] Re: Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher are black)

[Aditya]

On 16.04 LTS release, the recent update of mesa (17.0.7) packages, broke
VA-API.

$ LIBVA_DRIVER_NAME='i965' vainfo 
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns -1
libva info: User requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_39
vainfo: intel_driver.c:100: intel_driver_init: Assertion `(((struct drm_state 
*)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_DRI1)) || (((struct drm_state 
*)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_DRI2)) || (((struct drm_state 
*)(ctx)->drm_state)->auth_type == (VA_DRM_AUTH_CUSTOM))' failed.
Aborted (core dumped)

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

Title:
  Mesa 17 (Ubuntu 16.04 HWE) breaks the dash's blur (dash and launcher
  are black)

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  System: Ubuntu 16.04 32-bit + HWE
  Video card: GF 7300GT
  Driver: nouveau

  I'm testing the latest HWE stack. With Mesa 17 and enabled blur
  activating the dash results in all transparent elements getting black.
  Also, the launcher and panel are dark when the windows spread/scale is
  active.

  Disabling the blur or reverting to Mesa 12 solves the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1704596/+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 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup

[Aditya]

Yup, still present in 16.04.2 Xubuntu. Couldn't log in due to this.
Returns back to the login screen. After restarting lightdm.service from
another tty, I could log in.

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

Title:
  VT_WAITACTIVE does not work well with a multiseat setup

Status in Light Display Manager:
  In Progress
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Related to the fix introduced in bug #851612 .

  Saw this in lightdm.log (system call interrupted because of ctrl-alt-del 
pressed):
  [+2.97s] DEBUG: New display ready, switching to it
  [+2.97s] DEBUG: Activating VT 8
  [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted 
system call
  [+77.56s] DEBUG: Got signal 15 from process 1
  [+77.56s] DEBUG: Caught Terminated signal, shutting down

  And in x-1-greeter.log:
  [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts
  [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001
  [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000
  [+50.56s] WARNING: Error getting session list from 
org.freedesktop.DisplayManager: Timeout was reached

  On vt7, unity-greeter would get stuck after password input.
  On vt8, unity-greeter appears after that "getting session list timeout", 
which is about a minute later than vt7, and does not have a password input 
field.

  lightdm blocked by VT_WAITACTIVE may be the cause...

  Tested with lightdm 1.2.0-0ubuntu2 in precise.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/997483/+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 1694600] [NEW] package whoopsie 0.2.52.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Aditya Sahay]

Public bug reported:

I ran "sudo apt-get install -f" on my terminal and selected "y" on prompt.
After that, I got the following logs:

(Reading database ... 305447 files and directories currently installed.)
Preparing to unpack .../libwhoopsie0_0.2.52.3_amd64.deb ...
Unpacking libwhoopsie0:amd64 (0.2.52.3) over (0.2.52.2) ...
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Setting up libwhoopsie0:amd64 (0.2.52.3) ...
dpkg: error processing package whoopsie (--configure):
 package is in a very bad inconsistent state; you should
 reinstall it before attempting configuration
Processing triggers for libc-bin (2.23-0ubuntu7) ...
Errors were encountered while processing:
 whoopsie
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: whoopsie 0.2.52.3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
 libwhoopsie0: Install
 libwhoopsie0: Configure
 whoopsie: Configure
 NULL: ConfigurePending
Architecture: amd64
CrashReports:
 640:1000:116:38189263:2017-05-30 11:10:06.496968406 +0530:2017-05-30 
11:10:07.008974568 +0530:/var/crash/_usr_share_nylas-mail_nylas.1000.crash
 640:1000:116:75985:2017-05-31 10:59:36.494395912 +0530:2017-05-31 
10:59:36.710448121 +0530:/var/crash/_usr_bin_update-manager.1000.crash
 600:0:116:416287:2017-05-31 11:00:14.342133998 +0530:2017-05-31 
11:00:15.342133998 +0530:/var/crash/whoopsie.0.crash
 640:1000:116:54173:2017-05-30 11:10:08.964998106 +0530:2017-05-30 
11:10:09.201000946 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
Date: Wed May 31 11:00:14 2017
DuplicateSignature:
 package:whoopsie:0.2.52.3
 Setting up libwhoopsie0:amd64 (0.2.52.3) ...
 dpkg: error processing package whoopsie (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-01-21 (129 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
Title: package whoopsie 0.2.52.3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package autoreport-false need-duplicate-check xenial

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

Title:
  package whoopsie 0.2.52.3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in whoopsie package in Ubuntu:
  New

Bug description:
  I ran "sudo apt-get install -f" on my terminal and selected "y" on prompt.
  After that, I got the following logs:

  (Reading database ... 305447 files and directories currently installed.)
  Preparing to unpack .../libwhoopsie0_0.2.52.3_amd64.deb ...
  Unpacking libwhoopsie0:amd64 (0.2.52.3) over (0.2.52.2) ...
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Setting up libwhoopsie0:amd64 (0.2.52.3) ...
  dpkg: error processing package whoopsie (--configure):
   package is in a very bad inconsistent state; you should
   reinstall it before attempting configuration
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Errors were encountered while processing:
   whoopsie
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.52.3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  AptOrdering:
   libwhoopsie0: Install
   libwhoopsie0: Configure
   whoopsie: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   640:1000:116:38189263:2017-05-30 11:10:06.496968406 +0530:2017-05-30 
11:10:07.008974568 +0530:/var/crash/_usr_share_nylas-mail_nylas.1000.crash
   640:1000:116:75985:2017-05-31 10:59:36.494395912 +0530:2017-05-31 
10:59:36.710448121 +0530:/var/crash/_usr_bin_update-manager.1000.crash
   600:0:116:416287:2017-05-31 11:00:14.342133998 +0530:2017-05-31 
11:00:15.342133998 +0530:/var/crash/whoopsie.0.crash
   640:1000:116:54173:2017-05-30 11:10:08.964998106 +0530:2017-05-30 
11:10:09.201000946 +0530:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  Date: Wed May 31 11:00:14 2017
  DuplicateSignature:
   package:whoopsie:0.2.52.3
   Setting up libwhoopsie0:amd64 (0.2.52.3) ...
   dpkg: error processing package whoopsie (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  

[Touch-packages] [Bug 1694364] [NEW] package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Aditya Nath Swami]

Public bug reported:

When I try to open Synaptic package manager, it will get the error
message of above package and says the broken or something.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: cups 2.2.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.1
AptOrdering: NULL: ConfigurePending
Architecture: amd64
Date: Tue May 30 10:17:52 2017
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2017-05-12 (17 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: LENOVO 20287
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: cups
Title: package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/24/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DCN40WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: 31900059STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z510
dmi.modalias: 
dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
dmi.product.name: 20287
dmi.product.version: Lenovo IdeaPad Z510
dmi.sys.vendor: LENOVO

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

Title:
  package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in cups package in Ubuntu:
  New

Bug description:
  When I try to open Synaptic package manager, it will get the error
  message of above package and says the broken or something.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cups 2.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Tue May 30 10:17:52 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2017-05-12 (17 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20287
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=972db810-907d-4134-8ecd-3d483b27125b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: cups
  Title: package cups 2.2.2-1ubuntu1 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z510
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
  dmi.product.name: 20287
  dmi.product.version: Lenovo IdeaPad Z510
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1694364/+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 1548300] Re: XDG_RUNTIME_DIR not set when using sudo -i

[Aditya]

Isn't sudo supposed to use libpam-systemd which performs all these tasks
involved in registering user sessions with the systemd login manager
logind?

** Tags added: sudo

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

Title:
  XDG_RUNTIME_DIR not set when using sudo -i

Status in sudo:
  New
Status in sudo package in Ubuntu:
  Confirmed
Status in sudo package in Debian:
  New

Bug description:
  According to the man page `sudo -i` will run the command with an
  environment "similar" to the one a user would receive at log in.

  When trying to use tools that use D-Bus, specifically: systemctl
  --user, it will be impossible to control them via sudo.

  While there is a workaround; setting the XDG_RUNTIME_DIR manually,
  this means any configuration change that causes the XDG_RUNTIME_DIR to
  change will have to be applied in several locations.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sudo/+bug/1548300/+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 1639017] Re: Unable to have Higher Resolution on Ubuntu 16.04

[Aditya Duggal]

I am connecting my monitor through the VGA port and I don't have a any
DisplayPort, DVI or HDMI.

Any solution on VGA I could have since its bamboozling me to the core
since so many days.

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

Title:
  Unable to have Higher Resolution on Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am only able to view the screen in 1024x768 resolution here is my
  output for lshw -c Video

*-display   
 description: VGA compatible controller
 product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:25 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  I think the xorg driver is fully updated but still I am unable to run
  in higher resolution on ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Nov  4 00:33:25 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
  InstallationDate: Installed on 2016-10-31 (3 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61MS
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Nov  4 00:10:15 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639017/+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 1639017] [NEW] Unable to have Higher Resolution on Ubuntu 16.04

[Aditya Duggal]

Public bug reported:

Hi,

I am only able to view the screen in 1024x768 resolution here is my
output for lshw -c Video

  *-display   
   description: VGA compatible controller
   product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:25 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

I think the xorg driver is fully updated but still I am unable to run in
higher resolution on ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Nov  4 00:33:25 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-10-31 (3 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=361b7ddd-636c-40e8-98a4-6f7c6ceb1f69 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61MS
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MS:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Nov  4 00:10:15 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  Unable to have Higher Resolution on Ubuntu 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am only able to view the screen in 1024x768 resolution here is my
  output for lshw -c Video

*-display   
 description: VGA compatible controller
 product: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
 vendor: Intel Corporation
 physical id: 2
 bus info: pci@:00:02.0
 version: 09
 width: 64 bits
 clock: 33MHz
 capabilities: msi pm vga_controller bus_master cap_list rom
 configuration: driver=i915 latency=0
 resources: irq:25 memory:f780-f7bf 

[Touch-packages] [Bug 1382963] [NEW] [K42F, Realtek ALC269VB, Black Headphone Out, Right] No sound at all

[muhammad c. aditya]

Public bug reported:

I experience this after accidentaly start rhytmbox and audacity in same
time. after that, there is no sound at all with jack audio. built in
speaker still works.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caisar11372 F pulseaudio
CurrentDesktop: Unity
Date: Sun Oct 19 19:35:31 2014
InstallationDate: Installed on 2014-10-11 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  caisar11372 F pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [K42F, Realtek ALC269VB, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/08/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 422
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K42F
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr422:bd12/08/2010:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K42F
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: apport-bug i386 trusty

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

Title:
  [K42F, Realtek ALC269VB, Black Headphone Out, Right] No sound at all

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  I experience this after accidentaly start rhytmbox and audacity in
  same time. after that, there is no sound at all with jack audio. built
  in speaker still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caisar11372 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 19 19:35:31 2014
  InstallationDate: Installed on 2014-10-11 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caisar11372 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [K42F, Realtek ALC269VB, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 422
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K42F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr422:bd12/08/2010:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K42F
  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/1382963/+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