[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload

2020-04-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  cupsd cause apparmor denials for /etc/ld.so.preload

Status in apparmor package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  There is a constant flood of messages in dmesg:

  [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 
comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0
  [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 
comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0
  [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" 
operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 
comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: X-Cinnamon
  Date: Mon Apr 18 10:56:37 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-19 (1003 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100
  MachineType: LENOVO 4298R86
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic 
root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago)
  dmi.bios.date: 12/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4298R86
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4298R86
  dmi.product.version: ThinkPad X220 Tablet
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1571531/+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 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

2020-04-26 Thread Dimitri John Ledkov
@travis-downs this issue was fixed and is no longer monitored, if you
have a new bug report against perf, can you please open a new issue?

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

Title:
  Valgrind doesn't work in disco [Fatal error at startup: a function
  redirection which is mandatory for this platform-tool combination
  cannot be set up.]

Status in base-files package in Ubuntu:
  Won't Fix
Status in valgrind package in Ubuntu:
  Fix Released

Bug description:
  $ valgrind /bin/ls
  ==25995== Memcheck, a memory error detector
  ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
  ==25995== Command: /bin/ls
  ==25995== 

  valgrind:  Fatal error at startup: a function redirection
  valgrind:  which is mandatory for this platform-tool combination
  valgrind:  cannot be set up.  Details of the redirection are:
  valgrind:  
  valgrind:  A must-be-redirected function
  valgrind:  whose name matches the pattern:  strlen
  valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
  valgrind:  was not found whilst processing
  valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
  valgrind:  
  valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
  valgrind:  package on this machine.  (2, longer term): ask the packagers
  valgrind:  for your Linux distribution to please in future ship a non-
  valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
  valgrind:  that exports the above-named function using the standard
  valgrind:  calling conventions for this platform.  The package you need
  valgrind:  to install for fix (1) is called
  valgrind:  
  valgrind:On Debian, Ubuntu: libc6-dbg
  valgrind:On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
  valgrind:  
  valgrind:  Note that if you are debugging a 32 bit process on a
  valgrind:  64 bit system, you will need a corresponding 32 bit debuginfo
  valgrind:  package (e.g. libc6-dbg:i386).
  valgrind:  
  valgrind:  Cannot continue -- exiting now.  Sorry.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: valgrind 1:3.14.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  Date: Fri Dec 14 17:06:03 2018
  InstallationDate: Installed on 2018-12-04 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: valgrind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+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 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-26 Thread Hui Wang
If you remove dmic_detect=0, your alsa card could not be showed up in
gnome. So I guess there are some errors in the audio driver
initialization, I need the log to debug.

Could you remove dmic_detect=0 temporarily, then boot and upload the
dmesg, let me see what happens on the audio driver.

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

2020-04-26 Thread Hui Wang
Or you could run alsamixer, press F4, navigate to "Input Source" or
"Capture Source", use up or down to change the preferred options. then
press ESC.

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

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

2020-04-26 Thread Travis Downs
> we can't think of anything besides gdb, valgrind, and libunwind that
uses /usr/lib/debug

That seems like quite an incredible statement! I can imagine that many
debugging and profiling tools will want symbols.

For example, this change is breaking perf right now, as it looks for say
libc symbols in /usr/lib/debug/usr/lib/x86_64-linux-gnu/, but the
symbols are actually in /usr/lib/debug/lib/x86_64-linux-gnu/.

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

Title:
  Valgrind doesn't work in disco [Fatal error at startup: a function
  redirection which is mandatory for this platform-tool combination
  cannot be set up.]

Status in base-files package in Ubuntu:
  Won't Fix
Status in valgrind package in Ubuntu:
  Fix Released

Bug description:
  $ valgrind /bin/ls
  ==25995== Memcheck, a memory error detector
  ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
  ==25995== Command: /bin/ls
  ==25995== 

  valgrind:  Fatal error at startup: a function redirection
  valgrind:  which is mandatory for this platform-tool combination
  valgrind:  cannot be set up.  Details of the redirection are:
  valgrind:  
  valgrind:  A must-be-redirected function
  valgrind:  whose name matches the pattern:  strlen
  valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
  valgrind:  was not found whilst processing
  valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
  valgrind:  
  valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
  valgrind:  package on this machine.  (2, longer term): ask the packagers
  valgrind:  for your Linux distribution to please in future ship a non-
  valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
  valgrind:  that exports the above-named function using the standard
  valgrind:  calling conventions for this platform.  The package you need
  valgrind:  to install for fix (1) is called
  valgrind:  
  valgrind:On Debian, Ubuntu: libc6-dbg
  valgrind:On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
  valgrind:  
  valgrind:  Note that if you are debugging a 32 bit process on a
  valgrind:  64 bit system, you will need a corresponding 32 bit debuginfo
  valgrind:  package (e.g. libc6-dbg:i386).
  valgrind:  
  valgrind:  Cannot continue -- exiting now.  Sorry.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: valgrind 1:3.14.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  Date: Fri Dec 14 17:06:03 2018
  InstallationDate: Installed on 2018-12-04 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
  SourcePackage: valgrind
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+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 1874925] Re: Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

2020-04-26 Thread Adam Dyess
Thanks... that at least lets them show up in gnome.. but my internal
audio array isn't an option.  If i plugin an analog mic it works though.
Just the realtek audio array doesn't work

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

Title:
  Comet Lake PCH-LP cAVS (Audio, Voice, Speech)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone doesn't show up as an audio source.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  addyess   106482 F pulseaudio
   /dev/snd/controlC1:  addyess   106482 F pulseaudio
   /dev/snd/controlC0:  addyess   106482 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 24 16:56:54 2020
  InstallationDate: Installed on 2019-11-05 (171 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 
(20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.10
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 863F
  dmi.board.vendor: HP
  dmi.board.version: 54.13
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 15-df0xxx
  dmi.product.sku: 8LK66UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1874925/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

2020-04-26 Thread Douglas Silva
Running amixer sset 'Capture Source' 'Internal Mic' returns error:

amixer: Unable to find simple control 'Capture Source',0

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

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2020-04-26 Thread Jim Carpenter
Just tried upgrading my Xubuntu 19.10 desktop to 20.04 and I'm now
getting the same staircase effect. Video card is an AMD Radeon RX 5700
XT which is connected with a DisplayPort -> DVI-D cable to an ancient LG
W2252TQ monitor with a resolution of, yes, 1680x1050. It is the only
monitor connected.

Just thought I'd share. Rolling back to 19.10 now. I'll try again with
the point release.

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 

[Touch-packages] [Bug 1834192] Re: apparmor mult_mount regression test fails in eoan

2020-04-26 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

Title:
  apparmor mult_mount regression test fails in eoan

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  In running adt testing on 5.2-based kernels for eoan, I'm seeing
  failures from the apparmor mult_mount regression test. Running the
  test case manually with -x yields:

   + dd if=/dev/zero of=/tmp/sdtest.2210-22387-i6UxxQ/image.ext3 bs=4096 
count=20
   + mkfs.ext2 -F -m 0 -N 10 /tmp/sdtest.2210-22387-i6UxxQ/image.ext3
   ++ error_handler
   ++ fatalerror 'Unexpected shell error. Run with -x to debug'

  Running the following manually in a shell also fails in eoan with the
  5.0 kernel copied forward from disco, while it passes in disco:

   $ uname -a
   Linux ee-apparmor 5.0.0-17-generic #18-Ubuntu SMP Tue Jun 4 15:34:08 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
   $ dd if=/dev/zero of=test.img bs=4096 count=20
   20+0 records in
   20+0 records out
   81920 bytes (82 kB, 80 KiB) copied, 0.000406443 s, 202 MB/s
   $ mkfs.ext2 -F -m 0 -N 10 test.img
   mke2fs 1.45.2 (27-May-2019)
   test.img: Not enough space to build proposed filesystem while setting up 
superblock

  So this seems likely to be due to some change with mke2fs; not sure if
  this is a regression there or if the test was getting away with doing
  something invalid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1834192/+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 1875249] Re: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

2020-04-26 Thread Hui Wang
Please run amixer sset 'Capture Source' 'Internal Mic' or 'Headset Mic'
first, make sure the capture source is not headphone mic,

then plug the headset/earphone, choose correct option from the pop-up
dialogue.

thx.

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

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 11-3162
  dmi.product.sku: 0725
  dmi.product.version: 2.4.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875249/+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 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-26 Thread Dominique Poulain
** Tags added: seg

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
   └─1650 /lib/systemd/systemd-networkd

  Jan 26 16:39:28 firebolt systemd[1]: Starting Network Service...
  Jan 26 16:39:28 firebolt 

[Touch-packages] [Bug 1870975] Re: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up.

2020-04-26 Thread Hui Wang
@Seija,

After problem happens, please run "apport-collect 1870975.

Looks like all log were collected when there was no problem.

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

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1835660] Re: initramfs unpacking failed

2020-04-26 Thread Eromatic
USB 2.0 flash drive install of ubuntu-20.04-desktop-amd64.iso
UNetbootin 677-1~bionic1 
AMD Athlon II X4 640
ASRock N68-S

The first time that I ran the USB install, the live version of Ubuntu
20.04 succeeded in booting without issue. Now each and every time I
attempt to boot the live USB, I get the following display which prevents
me from installing Ubuntu 20.04:

[0.391406] Initramfs unpacking failed: Decoding failed
[0.571137] Failed to execute /init (error -2)
[0.571241] Kernel panic - not syncing: No working init found. Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[0.571349] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu
[0.571434] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N68-S, 
BIOS P2.00 12/15/2009
[0.571521] Call Trace:
[0.571593]  dump_stack+0x6d/0x9a
[0.571661]  ? rest_init+0x30/0xb0
[0.571729]  panic+0x101/0x2e3
[0.571797]  ? do_execve+0x25/0x30
[0.571863]  ? rest_init+0xb0/0xb0
[0.571930]  kernel_init+0xfb/0x100
[0.571998]  ret_from_fork+0x22/0x40
[0.572091] Kernel Offset: 0x29a0 from 0x8100 (relocation range: 
0x8000-0xbfff)
[0.572182] ---[ end Kernel panic - not syncing: No working init found.  Try 
passing init= option to kernel. See Linux Documentation/admin-guide/init.rst 
for guidance. ]---


Think that maybe something got corrupted on the flash drive, I redid the 
UNetbootin install, but the issue still remains. MD5 of 
ubuntu-20.04-desktop-amd64.iso checked good before procceeding.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+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 1670507] Re: why is hud-service using so much memory?

2020-04-26 Thread Haw Loeung
|   PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
| 59333 hloeung   20   0 1187352 891992   1500 S   0.3  11.1   3:40.03 
hud-service

It's been bounced a few times and only has been up for a few days:

| [hloeung@dharkan tmp]$ systemctl --user status hud.service
| ● hud.service - Unity HUD
|  Loaded: loaded (/usr/lib/systemd/user/hud.service; static; vendor 
preset: enabled)
| Drop-In: /run/user/3134/systemd/user/hud.service.d
|  └─graphical-session-pre.conf
|  Active: active (running) since Fri 2020-04-24 14:54:55 AEST; 2 days ago
|Main PID: 59333 (hud-service)
|  CGroup: /user.slice/user-3134.slice/user@3134.service/hud.service
|  └─59333 /usr/lib/x86_64-linux-gnu/hud/hud-service

| [hloeung@dharkan tmp]$ apt-cache policy hud
| hud:
|   Installed: 14.10+17.10.20170619-0ubuntu3.1
|   Candidate: 14.10+17.10.20170619-0ubuntu3.1
|   Version table:
|  *** 14.10+17.10.20170619-0ubuntu3.1 500
| 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages
| 100 /var/lib/dpkg/status

** Also affects: hud (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  why is hud-service using so much memory?

Status in hud package in Ubuntu:
  Confirmed
Status in hud source package in Focal:
  New

Bug description:
  When inspecting why my computer was sluggish I found hud-service using
  a lot of memory:

  
PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
   3142 sarnold   20   0 1208.1m 515.9m   9.9m S   0.0  3.3   1:44.69 
hud-service

  
  Why are menus I never use taking over five hundred megabytes of my memory and 
so much CPU time?

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: hud 14.10+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar  6 14:43:07 2017
  InstallationDate: Installed on 2012-10-18 (1600 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  SourcePackage: hud
  UpgradeStatus: Upgraded to xenial on 2016-04-30 (310 days ago)
  upstart.hud.log: void 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/44040199"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1670507/+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 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30

2020-04-26 Thread Avijit
I got the same error after upgrading to Ubuntu 20.04 from 18.04

Thanks,
Avijit

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

Title:
  gsettings-desktop-schemas 3.31 breaks mutter 3.30

Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Won't Fix
Status in ukwm package in Ubuntu:
  Fix Released

Bug description:
  We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
  gsettings-desktop-schemas.

  Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
  gdm/gnome-shell being unable to start.

  Also, ukwm is a fork of mutter so the Kylin devs need to backport the
  relevant commits from mutter.

  The problematic gsettings commit was:
  https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c

  I think the mutter commits can be found at
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/133

  We could easily add a dummy key with the old name but I'm thinking the
  way forward is just to package the newer mutter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+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 1875249] [NEW] [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound output from earphones

2020-04-26 Thread Douglas Silva
Public bug reported:

Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is no
sound output when you plug an earphone/headset. The built-in speakers,
on the other hand, are working properly. This is a laptop, Dell Inspiron
11 3162.

I checked volume levels with alsamixer, I played with the device
selection in the Pulseaudio mixer application, but nothing worked. I
also tested Firefox (playing a YouTube video) and system sounds. None of
them worked. The audio test made by apport-bug played no sound through
the earphone.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 3990 F pulseaudio
  dsilva 4791 F alsamixer
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sun Apr 26 18:12:06 2020
InstallationDate: Installed on 2020-04-24 (2 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dsilva 3990 F pulseaudio
  dsilva 4791 F alsamixer
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.4.0
dmi.board.name: 0NM68T
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr2.4.0:bd01/31/2018:svnDellInc.:pnInspiron11-3162:pvr2.4.0:rvnDellInc.:rn0NM68T:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 11-3162
dmi.product.sku: 0725
dmi.product.version: 2.4.0
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal

** Summary changed:

- No sound output from earphones
+ [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No sound 
output from earphones

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

Title:
  [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No
  sound output from earphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Starting from Ubuntu 20.04 (tested Xubuntu and Ubuntu MATE), there is
  no sound output when you plug an earphone/headset. The built-in
  speakers, on the other hand, are working properly. This is a laptop,
  Dell Inspiron 11 3162.

  I checked volume levels with alsamixer, I played with the device
  selection in the Pulseaudio mixer application, but nothing worked. I
  also tested Firefox (playing a YouTube video) and system sounds. None
  of them worked. The audio test made by apport-bug played no sound
  through the earphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 26 18:12:06 2020
  InstallationDate: Installed on 2020-04-24 (2 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dsilva 3990 F pulseaudio
dsilva 4791 F alsamixer
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Inspiron 11-3162, Realtek ALC3234, Black Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.4.0
  dmi.board.name: 0NM68T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 

[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately

2020-04-26 Thread Chris Boyle
I can confirm that Ubuntu 20.04 suffers from the same issue. I'm still
unable to link a Google Account due to being in Google's Advanced
Protection Program, which requires a Security Key to authenticate. I'm
able to authenticate in everything but Gnome's Online Accounts area.

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

Title:
  Google Online Account Two Factor with hardware key fails immediately

Status in gnome-online-accounts:
  Unknown
Status in Webkit:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  The hardware key authentication two factor fails immediately with a
  web based retry dialogue when connecting a Google account to the
  online accounts in settings using a hardware key second factor.

  Steps to reproduce:
  1. Set Google Account to default to a hardware security key like a Yubikey or 
other FIDO standard key after having two factor authentication enabled on your 
Google Account.
  2. Open Online accounts
  3. Add a Google Account
  4. Enter google email address
  5. Enter google password
  6. (this is the login flow of two factor, if default is the hardware key the 
error should appear).

  Work around:
  Choose use another method to authenticate: enter the authentication code and 
you will proceed.

  Expectations were:
  The ability to use the hardware key to authenticate as the second factor.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-control-center 1:3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
  Uname: Linux 4.13.0-16-lowlatency x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 17 16:01:11 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-control-center
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1875200] Re: Entire computer freezes shortly after bootup

2020-04-26 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1875200

Title:
  Entire computer freezes shortly after bootup

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm not sure if this bug was filed completely; I used the "ubuntu-bug"
  command which gathered a lot of information and files, but then the
  bugs.launchpad.net site timeouted and I'm not sure if the information
  I entered before and the files that were gathered have actually been
  submitted.

  Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes
  some seconds after bootup. It does not even reply to pings anymore and
  remote logins stop working as well. When booting it in recovery mode
  and then immediately using the menu option to continue booting, it
  appears to work reliably, but it only detects one monitor and there is
  no 3d acceleration.

  I've seen freezes happening at the following points:

  a) at the stage of a black screnen saying "lenovo" in the middle and
  "ubuntu" at the bottom (of both monitors)

  b) when asking for username and password to login

  c) after login

  
  When I was using the same computer with Ubuntu 19.10, there was no such 
problem.

  
  The computer is a Lenovo ThinkCentre M920x, the graphics card used is

  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
  [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef)

  with two monitors (3840x2160) connected via MiniDisplayPort

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 14:29:19 2020
  DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135]
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller])
 Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin 
[Radeon RX 550 640SP / RX 560/560X] [1642:1725]
  InstallationDate: Installed on 2020-03-29 (28 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 10S1002NMZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
  XorgLogOld:
   
  dmi.bios.date: 02/17/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M1UKT50A
  dmi.board.name: 3135
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN 3305220985042
  dmi.chassis.type: 35
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone:
  dmi.product.family: ThinkCentre M920x
  dmi.product.name: 10S1002NMZ
  dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x
  dmi.product.version: ThinkCentre M920x
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875200/+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 1875200] [NEW] Entire computer freezes shortly after bootup

2020-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm not sure if this bug was filed completely; I used the "ubuntu-bug"
command which gathered a lot of information and files, but then the
bugs.launchpad.net site timeouted and I'm not sure if the information I
entered before and the files that were gathered have actually been
submitted.

Summary: after an upgrade to Ubuntu 20.04 my entire computer freezes
some seconds after bootup. It does not even reply to pings anymore and
remote logins stop working as well. When booting it in recovery mode and
then immediately using the menu option to continue booting, it appears
to work reliably, but it only detects one monitor and there is no 3d
acceleration.

I've seen freezes happening at the following points:

a) at the stage of a black screnen saying "lenovo" in the middle and
"ubuntu" at the bottom (of both monitors)

b) when asking for username and password to login

c) after login


When I was using the same computer with Ubuntu 19.10, there was no such problem.


The computer is a Lenovo ThinkCentre M920x, the graphics card used is

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Baffin [Radeon RX 550 640SP / RX 560/560X] (rev ef)

with two monitors (3840x2160) connected via MiniDisplayPort

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 14:29:19 2020
DistUpgraded: 2020-04-25 14:33:16,904 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Continuously
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Subsystem: Lenovo UHD Graphics 630 (Desktop 9 Series) [17aa:3135]
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 550 640SP / RX 
560/560X] [1002:67ff] (rev ef) (prog-if 00 [VGA controller])
   Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Baffin [Radeon 
RX 550 640SP / RX 560/560X] [1642:1725]
InstallationDate: Installed on 2020-03-29 (28 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: LENOVO 10S1002NMZ
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=ff61fce1-cc83-4bbe-bc88-09cdd2ac7471 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-25 (0 days ago)
XorgLogOld:
 
dmi.bios.date: 02/17/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: M1UKT50A
dmi.board.name: 3135
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN 3305220985042
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:svnLENOVO:pn10S1002NMZ:pvrThinkCentreM920x:rvnLENOVO:rn3135:rvrSDK0T08861WIN3305220985042:cvnLENOVO:ct35:cvrNone:
dmi.product.family: ThinkCentre M920x
dmi.product.name: 10S1002NMZ
dmi.product.sku: LENOVO_MT_10S1_BU_Think_FM_ThinkCentre M920x
dmi.product.version: ThinkCentre M920x
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu
-- 
Entire computer freezes shortly after bootup
https://bugs.launchpad.net/bugs/1875200
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1875234] [NEW] Apport typo causes it to say "but you also a have snap" instead of "but you also have a snap" whenever I run ubuntu-bug for a program that has a .deb and a snap on

2020-04-26 Thread Seija Kijin
Public bug reported:

When I ran "ubuntu-bug snapd" I got a message stating I have a snap and
a deb installed. However, the error message has a typo in it; the words
"have" and "a" are switched around. This causes the message to read "You
are about to report a bug against the deb package, but you also a have
snap published by canonical installed."

The words "a" and "have" are switched up, and "canonical" should have an
uppercase C, since it is referring to Canonical, the company behind
Ubuntu.

This issue occurs whenever you run "ubuntu-bug snapd"

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu27
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 15:43:21 2020
InstallationDate: Installed on 2020-04-26 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-26 15-42-39.png"
   
https://bugs.launchpad.net/bugs/1875234/+attachment/5361040/+files/Screenshot%20from%202020-04-26%2015-42-39.png

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

Title:
  Apport typo causes it to say "but you also a have snap" instead of
  "but you also have a snap" whenever I run ubuntu-bug for a program
  that has a .deb and a snap on the machine

Status in apport package in Ubuntu:
  New

Bug description:
  When I ran "ubuntu-bug snapd" I got a message stating I have a snap
  and a deb installed. However, the error message has a typo in it; the
  words "have" and "a" are switched around. This causes the message to
  read "You are about to report a bug against the deb package, but you
  also a have snap published by canonical installed."

  The words "a" and "have" are switched up, and "canonical" should have
  an uppercase C, since it is referring to Canonical, the company behind
  Ubuntu.

  This issue occurs whenever you run "ubuntu-bug snapd"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 15:43:21 2020
  InstallationDate: Installed on 2020-04-26 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1875234/+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 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

2020-04-26 Thread Julian Andres Klode
Marking this as fix released in PackageKit then, seeing that we ship
1.1.13.

Given that we never used that updating stuff, I don't think it is worth
fixing that in old releases.


** Changed in: packagekit (Ubuntu)
   Status: New => Fix Released

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

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  Fix Released

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1872443] Re: /etc/securetty missing: dovecot not working

2020-04-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  /etc/securetty missing: dovecot not working

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
  "login" package (4.8.1-1ubuntu4).

  This leads to errors such as in /var/log/mail.log when a dovecot auth
  is tried:

  Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)

  It seems that pam_unix still needs /etc/securetty, but login no longer
  provides it.

  There was a similar bug in debian that seems to be related:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931899

  To my understanding, this is a problem between pam and login packages
  in 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+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 1875073] Re: Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

2020-04-26 Thread Sjoerd Nijboer
I tried getting a debug log of drm.i915 using "drm.debug=0x06" as a kernel 
parameter.
In the log dmesg.txt there's a "hotplug event received" in batches, everytime 
one of those appears, my screen flickers.
Which is weird to me since I don't unplug my fixed laptop screen.
It's likely that this is not a hardware faillure since this problem is not 
reproducible on Windows.

** Attachment added: "dmesg log with kernel parameter "drm.debug=0x06""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875073/+attachment/5361005/+files/dmesg.txt

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

Title:
  Screen flickering in Kubuntu 20.04 on Lenovo Yoga C940 14-IIL

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm experiencing a problem extremely similar to 
https://gitlab.freedesktop.org/drm/intel/-/issues/272
  My screen flickers too on a fresh install of Kubuntu 20.04LTS 
https://imgur.com/a/FoWI1sp

  Results of `inxi -Gx`  
  `
  Graphics:  Device-1: Intel Iris Plus Graphics G7 vendor: Lenovo driver: i915 
v: kernel bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.8 driver: modesetting resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa Intel Iris Plus Graphics (ICL GT2) 
 v: 4.6 Mesa 20.1.0-devel (git-a64d266 2020-04-25 focal-oibaf-ppa) 
direct render: Yes 
  `

  I've tried 915.enable_psr=0 as a boot parameter, didn't work.
  nomodeset does get me into a bootable image, but I'm looking into getting a 
working driver.

  Fedora 31 was having a similar issue, there was barely any flickering up 
untill some recent kernel updates. (about a couple small ones every 10 minutes 
or so)
  Kubuntu 19.10 was quite stable too, untill I installed a lenovo provided 
firmware update (from AUCN45WW to AUCN54WW), which made it slightly worse.
  I also tried a couple of other kernel parameters that haven't had any effect.
  Running kernel 5.6 on Kubuntu did have thesame issue as regular kubuntu 20.04.
  Running kernel 5.7-rc2 did fix the problem, but networking and sound was 
dead, so it's only half a solution.
  I highly suspect it's an issue with i915, but I don't know how I would trace 
it down.
  I don't know why and I don't know how.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr 25 20:49:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3801]
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 81Q9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=5d977dfa-1fa5-412b-9d83-644cef18af6e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AUCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga C940-14IIL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL:
  dmi.product.family: Yoga C940-14IIL
  dmi.product.name: 81Q9
  dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL
  dmi.product.version: Lenovo Yoga C940-14IIL
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101+git2004241830.bf63f8~oibaf~f
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.1~git2004250730.a64d26~oibaf~f
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1870975] WifiSyslog.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5361003/+files/WifiSyslog.txt

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

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

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] RfKill.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1870975/+attachment/5361001/+files/RfKill.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] UdevDb.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1870975/+attachment/5361002/+files/UdevDb.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] PulseList.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5361000/+files/PulseList.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Lsusb-v.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360996/+files/Lsusb-v.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] ProcModules.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360999/+files/ProcModules.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Lsusb-t.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360995/+files/Lsusb-t.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] ProcInterrupts.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360998/+files/ProcInterrupts.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Lspci-vt.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360994/+files/Lspci-vt.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] ProcCpuinfoMinimal.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360997/+files/ProcCpuinfoMinimal.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Lspci.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1870975/+attachment/5360993/+files/Lspci.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] CurrentDmesg.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360990/+files/CurrentDmesg.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] IwConfig.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360992/+files/IwConfig.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Dependencies.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360991/+files/Dependencies.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] CRDA.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1870975/+attachment/5360989/+files/CRDA.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1474 F pulseaudio
   /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  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 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: pulseaudio 1:13.99.1-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1870975/+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 1870975] Re: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up.

2020-04-26 Thread Seija Kijin
apport information

** Tags added: apport-collected focal

** Description changed:

  When I closed my laptop lid while sound was playing in Audacity and then
  opened the lid back up, the device woke up from sleep. However, my
  headphones were plugged in at the time, and Ubuntu acted as if the audio
  resumed.
  
  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the headphones.
  
  Description: Ubuntu 18.04.4 LTS
  Release: 18.04
  
  I am forced to reboot my machine as a workaround.
  
  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  seija  1474 F pulseaudio
+  /dev/snd/pcmC0D0p:   seija  1474 F...m pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-25 (1 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ 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 0c45:6a06 Microdia Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Inspiron 5570
+ Package: pulseaudio 1:13.99.1-1ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=a21f3206-ba56-4281-9754-2206135879a0 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-26-generic N/A
+  linux-backports-modules-5.4.0-26-generic  N/A
+  linux-firmware1.187
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/15/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.3
+ dmi.board.name: 09YTN7
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5570
+ dmi.product.sku: 0810
+ dmi.sys.vendor: Dell Inc.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1870975/+attachment/5360988/+files/AlsaInfo.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/1870975

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  when I close my laptop lid while audio is playing and then open it
  back up.

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

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a 

[Touch-packages] [Bug 1875199] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all

2020-04-26 Thread Robert Boerner
Problem also occurs in Ubuntu 19.10 and Ubuntu 18.04

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875199/+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 1772537] Re: Wrong combining sequence in Compose for the Finnish locale

2020-04-26 Thread Bug Watch Updater
** Changed in: xlibs
   Status: New => Fix Released

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

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in xlibs:
  Fix Released
Status in libx11 package in Ubuntu:
  Triaged

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/xlibs/+bug/1772537/+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 1875091] Re: opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2"

2020-04-26 Thread Shan
I thought I'd reported this as package "mesa", since the problem appears
in mesa-opencl-icd.  Maybe I misclicked or something.  If someone
changed it to the Nvidia drivers package, could you please pick the
correct package for AMD drivers instead?

** Package changed: nvidia-graphics-drivers-440 (Ubuntu) => mesa
(Ubuntu)

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

Title:
  opencl fails with "pipe_radeonsi.so: undefined symbol:
  amdgpu_cs_query_reset_state2"

Status in mesa package in Ubuntu:
  New

Bug description:
  Both luxmark and leelaz, the two OpenCL applications I have, fail at
  runtime with the same error, looking for
  "amdgpu_cs_query_reset_state2" in /usr/lib/x86_64-linux-gnu/gallium-
  pipe/pipe_radeonsi.so

  This is on a system with a relatively new AMD GPU, freshly upgraded
  from 18.04.  Leela zero worked correctly in 18.04, and I've tried
  various compiler options, openCL config and such with no success.  I
  don't know about luxmark but installed it to test.  Since it reports
  the same error, I think it's a bug to report here.

  Platform Name Clover
  Device Name   AMD Radeon (TM) RX Graphics 
(POLARIS11, DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1)
  Device Name   AMD RAVEN (DRM 3.36.0, 
5.6.7-050607-generic, LLVM 9.0.1)

  01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin 
[Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev c0)
  04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875091/+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 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all

2020-04-26 Thread Anuhbav Mishra
Hi Hui,

Running the command before plugging in headphone didn't work.
So I plugged in, choose as Headphone and then run the command - $ amixer
sset 'Input Source' "Headset Mic"
and it did worked. I can now hear the sound, but only till the time I
didn't plug out and plug in again. So clearly it is not a solution at all.
Though I am not much troubled by this, but fixing this issue will be
beneficial for other users particularly new Ubuntu users.

And there is nothing weird that you can record audio with a pure headphone.
This feature was already in previous Ubuntu versions and Windows also.
Its quite cool and fun. I would be glad if you try this.

Thank you for your response. I just learned a few new tricks with
terminal.

Thanks and Regards,
Anubhav Mishra

On Sun, Apr 26, 2020 at 8:32 PM Hui Wang  wrote:

> It is weird that you could record sound with a pure headphone, I have no
> idea how that happened.
>
> And could you please test:
>
> run amixer sset 'Input Source' "Headset Mic" or "Rear Mic" or "Line" first,
> then plug in the headphone and choose headphone, does the sound output
> from headphone?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875032
>
> Title:
>   [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
>   all
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   This problem only occurs when I plug my headphone and choose Headphone
> in option.
>   If I choose Headset, though plugging either headphone or headset, it
> works perfectly.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  prm1856 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 25 20:05:01 2020
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-osp1-20171027-1
>   InstallationDate: Installed on 2018-09-28 (575 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20171027-10:57
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  prm1856 F pulseaudio
>   Symptom_Jack: Black Headphone Out, Front
>   Symptom_Type: No sound at all
>   Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No
> sound at all
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   dmi.bios.date: 05/29/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 2.13.0
>   dmi.board.name: 03NJH0
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A01
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr:
>   dmi.product.family: Vostro
>   dmi.product.name: Vostro 3470
>   dmi.product.sku: 0869
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+subscriptions
>

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

Title:
  [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem only occurs when I plug my headphone and choose Headphone in 
option.
  If I choose Headset, though plugging either headphone or headset, it works 
perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prm1856 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:05:01 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2018-09-28 (575 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  

[Touch-packages] [Bug 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

2020-04-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "patch removing pk_backend_get_distro_upgrades and
disabling the feature" seems to be a patch.  If it isn't, please remove
the "patch" flag from the attachment, remove the "patch" tag, and if you
are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  New

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1875091] [NEW] opencl fails with "pipe_radeonsi.so: undefined symbol: amdgpu_cs_query_reset_state2"

2020-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Both luxmark and leelaz, the two OpenCL applications I have, fail at
runtime with the same error, looking for "amdgpu_cs_query_reset_state2"
in /usr/lib/x86_64-linux-gnu/gallium-pipe/pipe_radeonsi.so

This is on a system with a relatively new AMD GPU, freshly upgraded from
18.04.  Leela zero worked correctly in 18.04, and I've tried various
compiler options, openCL config and such with no success.  I don't know
about luxmark but installed it to test.  Since it reports the same
error, I think it's a bug to report here.

Platform Name Clover
Device Name   AMD Radeon (TM) RX Graphics 
(POLARIS11, DRM 3.36.0, 5.6.7-050607-generic, LLVM 9.0.1)
Device Name   AMD RAVEN (DRM 3.36.0, 
5.6.7-050607-generic, LLVM 9.0.1)

01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Baffin 
[Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] (rev c0)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven 
Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c4)

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


** Tags: amdgpu focal opencl
-- 
opencl fails with "pipe_radeonsi.so: undefined symbol: 
amdgpu_cs_query_reset_state2"
https://bugs.launchpad.net/bugs/1875091
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

-- 
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 1875190] Re: Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available.

2020-04-26 Thread Julian Andres Klode
I'm not aware of any performance issues in those parts of apt, and spent
a considerable time optimizing it.

You probably want to strace or gdb apt when it's hanging and figure out
where the issue is, because there's nothing that can be done here by
anyone else so far.

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

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

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+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 1875199] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all

2020-04-26 Thread Robert Boerner
Public bug reported:

No sound output. Only a 'Dummy' audio output device is listed in the
Gnome Sound application.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rboerner   1205 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 12:12:49 2020
InstallationDate: Installed on 2020-04-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  rboerner   1205 F pulseaudio
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2020
dmi.bios.vendor: Intel Corp.
dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
dmi.board.name: NUC8CCHB
dmi.board.vendor: Intel Corporation
dmi.board.version: K44767-502
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: CH
dmi.product.name: NUC8CCHK
dmi.product.sku: BKNUC8CCHKR
dmi.product.version: K44798-502
dmi.sys.vendor: Intel(R) Client Systems

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  No sound output. Only a 'Dummy' audio output device is listed in the
  Gnome Sound application.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 12:12:49 2020
  InstallationDate: Installed on 2020-04-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rboerner   1205 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2020
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CHAPLCEL.0048.2020.0225.1640
  dmi.board.name: NUC8CCHB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: K44767-502
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0:
  dmi.product.family: CH
  dmi.product.name: NUC8CCHK
  dmi.product.sku: BKNUC8CCHKR
  dmi.product.version: K44798-502
  dmi.sys.vendor: Intel(R) Client Systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875199/+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 1872902] Re: Upgrade to Focal now removes chrony

2020-04-26 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~xnox/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/382970

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Triaged

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
 Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  I'd ask you to revise the dependencies that got changes in systemd
  245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays
  installed as that was an opt-in chances are quite high people would
  want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1872902] Re: Upgrade to Focal now removes chrony

2020-04-26 Thread Dimitri John Ledkov
I see that

Installed tasks are: {'standard', 'server', 'openssh-server', 'minimal',
'cloud-image'}

and then we try to force mark each package in those to be
installed/upgraded. However standard & minimal, are already handled via
BaseMetaPkgs, and should not be "force installed".

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Triaged

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
 Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  I'd ask you to revise the dependencies that got changes in systemd
  245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays
  installed as that was an opt-in chances are quite high people would
  want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1872902] Re: Upgrade to Focal now removes chrony

2020-04-26 Thread Dimitri John Ledkov
When I ignore "standard" and "minimal" tasks from "installedTasks" I get
better results:

Installed tasks are: {'openssh-server', 'cloud-image', 'server'}

53 new packages are going to be installed. 419 packages are going to 
be upgraded. 


And chrony remains installed.

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Triaged

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
 Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  I'd ask you to revise the dependencies that got changes in systemd
  245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays
  installed as that was an opt-in chances are quite high people would
  want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1875190] ProcCpuinfoMinimal.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1875190/+attachment/5360891/+files/ProcCpuinfoMinimal.txt

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

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  New

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+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 1875189] [NEW] Screen Flickers when it wakes from suspend/sleep.

2020-04-26 Thread Dhruv Gadhavi
Public bug reported:

I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 ( Raven
Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh rate of
120Hz.

Whenever I shut the laptop lid or it auto-suspends it catches screen
flickers when it wakes up.

I think it's some kernel issue some deadlock maybe.

I already filed a bug on fedora bugzilla forum for the same aswell.

Here is the link for the same :

https://bugzilla.redhat.com/show_bug.cgi?id=1748042

I hope it gets' fixed this time :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 20:33:46 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Picasso [1043:18f1]
InstallationDate: Installed on 2020-04-26 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT
ProcKernelCmdLine: audit=0  BOOT_IMAGE=/@/boot/vmlinuz-5.6.0-7.1-liquorix-amd64 
root=UUID=c6a5aea4-fe87-480e-9b59-d3b0077d5842 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FX505DT.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: FX505DT
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.:bvrFX505DT.310:bd12/24/2019:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: TUF Gaming
dmi.product.name: TUF Gaming FX505DT_FX505DT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Video showing screen flickers."
   
https://bugs.launchpad.net/bugs/1875189/+attachment/5360868/+files/video_2020-04-26_20-47-46.mp4

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

Title:
  Screen Flickers when it wakes from suspend/sleep.

Status in xorg package in Ubuntu:
  New

Bug description:
  I got some laptop having optimus/hybrid GPUs setup : AMD Vega 8 (
  Raven Ridge ) + Nvidia GTX 1650 GPUs and  a display having refresh
  rate of 120Hz.

  Whenever I shut the laptop lid or it auto-suspends it catches screen
  flickers when it wakes up.

  I think it's some kernel issue some deadlock maybe.

  I already filed a bug on fedora bugzilla forum for the same aswell.

  Here is the link for the same :

  https://bugzilla.redhat.com/show_bug.cgi?id=1748042

  I hope it gets' fixed this time :)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.6.0-7.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 20:33:46 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU117M [GeForce GTX 1650 Mobile / Max-Q] 
[1043:109f]
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Picasso 

[Touch-packages] [Bug 1875190] [NEW] Apt update takes around a full minute to read state information when I run it for the first time since boot even though there are no updates available.

2020-04-26 Thread Seija Kijin
Public bug reported:

When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
repositories. However, when it was reading state information, that
process took a full minute even though there were no new updates.

This is too slow, even though the subsequent time I ran the command, it
was much faster. No, this was not the first time I ever ran the command
on the current install, as I ran it the day before without reinstalling
Ubuntu, on Ubuntu 20.04, and the process took less than 15 seconds.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 2.0.2
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 11:42:21 2020
InstallationDate: Installed on 2020-04-25 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-25 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: apt 2.0.2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Tags:  focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

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


** Tags: amd64 apport-bug apport-collected focal

** Attachment added: "My Terminal"
   
https://bugs.launchpad.net/bugs/1875190/+attachment/5360887/+files/Screenshot%20from%202020-04-26%2011-45-55.png

** Tags added: apport-collected

** Description changed:

  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.
  
  This is too slow, even though the subsequent time I ran the command, it
  was much faster. No, this was not the first time I ever ran the command
  on the current install, as I ran it the day before without reinstalling
  Ubuntu, on Ubuntu 20.04, and the process took less than 15 seconds.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2020-04-25 (1 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: apt 2.0.2
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  New

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  

[Touch-packages] [Bug 1875190] Dependencies.txt

2020-04-26 Thread Seija Kijin
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1875190/+attachment/5360890/+files/Dependencies.txt

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

Title:
  Apt update takes around a full minute to read state information when I
  run it for the first time since boot even though there are no updates
  available.

Status in apt package in Ubuntu:
  New

Bug description:
  When I ran "sudo apt update && sudo apt dist-upgrade", apt hit all the
  repositories. However, when it was reading state information, that
  process took a full minute even though there were no new updates.

  This is too slow, even though the subsequent time I ran the command,
  it was much faster. No, this was not the first time I ever ran the
  command on the current install, as I ran it the day before without
  reinstalling Ubuntu, on Ubuntu 20.04, and the process took less than
  15 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:42:21 2020
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-25 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: apt 2.0.2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1875190/+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 1873384] Re: Headphone has no sound out

2020-04-26 Thread 黄闫
Update:
I find out that in PulseAudio Panel the settings of input device should be 
choose as 'Internal Microphone' rather than 'Headset Microphone' or 
'Microphone', and the speakers of my headset can work properly.

My laptop's 1 jack hole connection and headset can work properly on
Windows, both headset speaker and mic can work.

Suggestion:
Add correct support for 1 jack headset in linux audio frameworks, no matter 
PulseAudio, Alsa and so on.
1 jack headset can save 1 x 3.5mm hole position from traditional 2 x 3.5mm 
headset, more and more laptop will accept such kind of headset connection.

** Attachment added: "The photo of my 1 jack hole headset connection of 
inspiron 15 gaming 5577"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+attachment/5360855/+files/20200426_232901.jpg

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

Title:
  Headphone has no sound out

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Computer:
  Dell inspiron 15 5577 Gaming
  intel i5 7300HQ version
  System:
  Kubuntu 20.04
  Bug:
  Plug-in headphone has no sound out, meanwhile computer's speaker is okay when 
unplugged the headphone.
  Additional information:
  Headphone is okay when kubuntu 18.04.3 is installed on the computer.
  Alsamixer is checked and headphone are not mute.
  Headphone plugin state can be correctly detected, and speaker can 
automatically mute until headphone unplugged.
  External usb soundcard is usable with headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.12
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 11:14:43 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash nomodeset ---
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherlockholmes   1242 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  MachineType: Dell Inc. Inspiron 5577
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic 
root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 090HMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 1.1.3
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873384/+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 1875162] [NEW] Crash when using scummvm with SDL.

2020-04-26 Thread roland
Public bug reported:

Relevant line from dmesg:

[   44.809342] scummvm[2866]: segfault at a0 ip 7f203f4a3838 sp 
7ffc2144a5e0 error 4 in iris_dri.so[7f203ea73000+d48000]
[   44.809349] Code: 44 24 18 48 c7 44 24 10 00 00 00 00 48 c7 44 24 18 00 00 
00 00 50 4c 8d 4c 24 18 e8 d2 0b b6 ff 48 8b 44 24 18 31 d2 48 89 ef <4c> 8b b0 
a0 00 00 00 4c 89 f6 e8 79 91 fd ff 48 8b bd 28 01 00 00

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 11:58:21 2020
DistUpgraded: 2020-04-23 22:04:58,240 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 440.64, 5.3.0-48-generic, x86_64: installed
 nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
InstallationDate: Installed on 2019-10-07 (201 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20QDCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-23 (2 days ago)
dmi.bios.date: 03/18/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2HET47W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 7th
dmi.product.name: 20QDCTO1WW
dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
dmi.product.version: ThinkPad X1 Carbon 7th
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: 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/1875162

Title:
  Crash when using scummvm with SDL.

Status in xorg package in Ubuntu:
  New

Bug description:
  Relevant line from dmesg:

  [   44.809342] scummvm[2866]: segfault at a0 ip 7f203f4a3838 sp 
7ffc2144a5e0 error 4 in iris_dri.so[7f203ea73000+d48000]
  [   44.809349] Code: 44 24 18 48 c7 44 24 10 00 00 00 00 48 c7 44 24 18 00 00 
00 00 50 4c 8d 4c 24 18 e8 d2 0b b6 ff 48 8b 44 24 18 31 d2 48 89 ef <4c> 8b b0 
a0 00 00 00 4c 89 f6 e8 79 91 fd ff 48 8b bd 28 01 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:58:21 2020
  DistUpgraded: 2020-04-23 22:04:58,240 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-48-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-10-07 (201 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  

[Touch-packages] [Bug 1875162] Re: Crash when using scummvm with SDL.

2020-04-26 Thread roland
The bug is reproducable with glxgears:

[  624.327290] glxgears[10550]: segfault at 24 ip 7f916366f1d4 sp 
7ffc10214aa0 error 6 in iris_dri.so[7f9162c3e000+d48000]
[  624.327297] Code: 2b 7e 30 01 c7 81 ff ff ff 00 00 0f 87 9d 17 00 00 48 01 
c8 48 89 46 38 48 85 c9 0f 84 10 06 00 00 83 ea 01 81 ca 00 00 09 78 <89> 11 48 
8d 51 04 45 85 ff 74 76 41 8d 47 ff 48 8d 4c c1 0c 0f 1f



** Attachment added: "Image of a black glxgears"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875162/+attachment/5360815/+files/Screenshot%20from%202020-04-26%2012-06-33.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/1875162

Title:
  Crash when using scummvm with SDL.

Status in xorg package in Ubuntu:
  New

Bug description:
  Relevant line from dmesg:

  [   44.809342] scummvm[2866]: segfault at a0 ip 7f203f4a3838 sp 
7ffc2144a5e0 error 4 in iris_dri.so[7f203ea73000+d48000]
  [   44.809349] Code: 44 24 18 48 c7 44 24 10 00 00 00 00 48 c7 44 24 18 00 00 
00 00 50 4c 8d 4c 24 18 e8 d2 0b b6 ff 48 8b 44 24 18 31 d2 48 89 ef <4c> 8b b0 
a0 00 00 00 4c 89 f6 e8 79 91 fd ff 48 8b bd 28 01 00 00

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 26 11:58:21 2020
  DistUpgraded: 2020-04-23 22:04:58,240 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.64, 5.3.0-48-generic, x86_64: installed
   nvidia, 440.64, 5.4.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292]
  InstallationDate: Installed on 2019-10-07 (201 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20QDCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-26-generic 
root=UUID=298d5179-f5b4-410d-aafb-92630b5b48a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-23 (2 days ago)
  dmi.bios.date: 03/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET47W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875162/+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 1873384] Re: Headphone has no sound out

2020-04-26 Thread 黄闫
I've installed Ubuntu Desktop and now I find out the problem's temporary
solve. Please someone can notify the teams that can solve this problem.

In Ubuntu Desktop, when I plug in the headphone(headset actually, it
have speaker and mic and can work properly on mobile phone, one 3.5mm
jack), the pop-dialogue show up and give me 3 choose items---
Headphone Headset and Speaker

When I choose the headphone item, my headset speakers can work properly. I 
didn't test the mic because my laptop have a build-in one. 
When I choose the headset, the problem shows up, my headset can't work.

In KDE Desktop and Xfce, they both use PulseAudio Control Panel.
PulseAudio detects headphone automatically without pop-up dialogue, and
the problem shows up.

Maybe the PulseAudio detects the headset correctly, but it treat the
headset as old fashioned 2 x 3.5mm jacks kind. Now the new kinds of
headset have only one 3.5mm jack with speaker & mic channel on it. My
Inspiron 15 Gaming 5577 have the 2-in-1 3.5mm jack hole so when system
use old fashion mode it can't work properly.

It can also explain why it can work in headphone mode. Headphone mode is
compatible with the 1 jack headset but can't use headset's mic.

Suggestions: Provide KDE and Xfce4 Desktop environment 'Headphone plug-
in' pop-up dialogue so that we can choose 'headphone'compatible mode at
least. Separate headset mode into '1 jack headset' and '2 jack headset'
mode to make headset work properly in different platform.

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

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => 黄闫 (prayerholmes)

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

Title:
  Headphone has no sound out

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Computer:
  Dell inspiron 15 5577 Gaming
  intel i5 7300HQ version
  System:
  Kubuntu 20.04
  Bug:
  Plug-in headphone has no sound out, meanwhile computer's speaker is okay when 
unplugged the headphone.
  Additional information:
  Headphone is okay when kubuntu 18.04.3 is installed on the computer.
  Alsamixer is checked and headphone are not mute.
  Headphone plugin state can be correctly detected, and speaker can 
automatically mute until headphone unplugged.
  External usb soundcard is usable with headphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.12
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 17 11:14:43 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash nomodeset ---
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sherlockholmes   1242 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200416)
  MachineType: Dell Inc. Inspiron 5577
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic 
root=UUID=18303cc3-5e85-4677-8bca-60324bae9608 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-24-generic N/A
   linux-backports-modules-5.4.0-24-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.3
  dmi.board.name: 090HMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn090HMC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5577
  dmi.product.sku: 07E1
  dmi.product.version: 

[Touch-packages] [Bug 984249] Re: [HP ProBook 4320s, IDT 92HD81B1X5, Mic, Internal] Background noise or low volume

2020-04-26 Thread Zingam
** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [HP ProBook 4320s, IDT 92HD81B1X5, Mic, Internal] Background noise or
  low volume

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Lots of backround noise when using the internal microphone. Pulse
  audio crashed and I cannot lower the volume of the recorded sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd460 irq 48'
 Mixer name : 'IDT 92HD81B1X5'
 Components : 'HDA:111d7605,103c1421,00100402'
 Controls  : 17
 Simple ctrls  : 10
  Card1.Amixer.info:
   Card hw:1 'Generic'/'HD-Audio Generic at 0xd452 irq 49'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Date: Tue Apr 17 21:24:55 2012
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Intel successful
  Symptom_Type: High background noise, or volume is too low
  Title: [HP ProBook 4320s, IDT 92HD81B1X5, Mic, Internal] Background noise or 
low volume
  UpgradeStatus: Upgraded to precise on 2012-04-09 (8 days ago)
  dmi.bios.date: 09/09/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68AHH Ver. F.20
  dmi.board.name: 1421
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 53.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68AHHVer.F.20:bd09/09/2011:svnHewlett-Packard:pnHPProBook4320s:pvr:rvnHewlett-Packard:rn1421:rvrKBCVersion53.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4320s
  dmi.sys.vendor: Hewlett-Packard
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-17T20:55:00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/984249/+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 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

2020-04-26 Thread Niklas Sombert
** Patch added: "patch removing pk_backend_get_distro_upgrades and disabling 
the feature"
   
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1709699/+attachment/5360831/+files/remove-get-distro-upgrades.patch

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

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  New

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1709699] Re: gpk-update-viewer fails with "Spawn of helper 'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ... (No such file or directory)"

2020-04-26 Thread Niklas Sombert
I think this is really a bug in packagekit. On 18.04 I can also trigger
this by just running pkcon get-distro-upgrades in a terminal:

Transaction:Getting upgrades
Status: Waiting in queue
Status: Starting
Status: Finished
Results:
Fatal error: Spawn of helper 
'/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed: failed to 
spawn /usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to 
execute child process 
?/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py?

The problem seems to be that in debian/rules this file is being deleted:

  58   │ # Ubuntu-specific, broken
  59   │ rm -f 
$(INSTALLDIR)/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py


But it is still referenced in backends/aptcc/pk-backend-aptcc.cpp:

 287   │ /**
 288   │  * pk_backend_get_distro_upgrades:
 289   │  */
 290   │ void pk_backend_get_distro_upgrades(PkBackend *backend, PkBackendJob 
*job)
 291   │ {
 292   │ pk_backend_spawn_helper(spawn, job, "get-distro-upgrade.py", 
"get-distro-upgrades", NULL);
 293   │ }

Newer upstream versions of PackageKit (1.1.13) seem to have this file
removed - and also the reference in backends/aptcc/pk-backend-aptcc.cpp.

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

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

Title:
  gpk-update-viewer fails with "Spawn of helper
  'usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' failed ...
  (No such file or directory)"

Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in packagekit package in Ubuntu:
  New

Bug description:
  gpk-update-viewer fails with
  Spawn of helper '/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py' 
failed: failed to spawn 
/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py: Failed to execute 
child process “/usr/share/PackageKit/helpers/aptcc/get-distro-upgrade.py” (No 
such file or directory)

  This was detected by Robert Reinsch on a Ubuntu 17.04 system and was
  verified by me on a 17.10 daily build from 2017-08-09

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-packagekit 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Aug  9 21:00:48 2017
  ExecutablePath: /usr/bin/gpk-update-viewer
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807)
  SourcePackage: gnome-packagekit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-packagekit/+bug/1709699/+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 1854314] Re: Legacy directory /var/run in /lib/systemd/system/dbus.socket

2020-04-26 Thread maravento
Ubuntu 20.04 LTS x64

Apr 26 09:19:11 mrv systemd[1]: /lib/systemd/system/dbus.socket:5: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
Apr 26 09:19:11 mrv systemd[1]: /lib/systemd/system/squid.service:15: PIDFile= 
references a path below legacy directory /var/run/, updating /var/run/squid.pid 
→ /run/squid.pid; please update the unit file accordingly.
Apr 26 09:19:11 mrv systemd[1]: /etc/systemd/system/anydesk.service:9: PIDFile= 
references a path below legacy directory /var/run/, updating 
/var/run/anydesk.pid → /run/anydesk.pid; please update the unit file 
accordingly.

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

Title:
  Legacy directory /var/run in /lib/systemd/system/dbus.socket

Status in D-Bus:
  New
Status in dbus package in Ubuntu:
  Fix Committed
Status in dbus package in Debian:
  Fix Released

Bug description:
  dbus/focal-proposed,now 1.12.16-2ubuntu1 amd64

  Re(o)curring after each new upgrade of dbus, for quite some time and
  still...

  $ dmesg|grep accordingly
  systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a 
path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket 
→ /run/dbus/system_bus_socket; please update the unit file accordingly.

  Originally:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/var/run/dbus/system_bus_socket

  After change:
  $cat /lib/systemd/system/dbus.socket
  [Unit]
  Description=D-Bus System Message Bus Socket

  [Socket]
  ListenStream=/run/dbus/system_bus_socket

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1854314/+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 1856366] Re: PCI/internal sound card not detected on a Swift SF314-57

2020-04-26 Thread G Aswin
** Also affects: sound-2.6
   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/1856366

Title:
  PCI/internal sound card not detected on a Swift SF314-57

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

Bug description:
  No sound card detected with kernel 5.5.0-050500rc1-generic

  1. Description:   Ubuntu 19.10
  Release:  19.10

  2. linux-image-
  unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb

  3. have at least one soundcard

  4. cat /proc/asound/cards reports:
  --- no soundcards ---

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.5.0-050500rc1-generic x86_64
  NonfreeKernelModules: hda_intel
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 22:09:17 2019
  InstallationDate: Installed on 2019-12-13 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.07
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd09/05/2019:svnAcer:pnSwiftSF314-57:pvrV1.07:rvnIL:rnFloris_IL:rvrV1.07:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF314-57
  dmi.product.sku: 
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T20:34:57.551680

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1856366/+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 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all

2020-04-26 Thread Hui Wang
It is weird that you could record sound with a pure headphone, I have no
idea how that happened.

And could you please test:

run amixer sset 'Input Source' "Headset Mic" or "Rear Mic" or "Line" first,
then plug in the headphone and choose headphone, does the sound output from 
headphone?

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

Title:
  [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem only occurs when I plug my headphone and choose Headphone in 
option.
  If I choose Headset, though plugging either headphone or headset, it works 
perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prm1856 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 20:05:01 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  InstallationDate: Installed on 2018-09-28 (575 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prm1856 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.13.0
  dmi.board.name: 03NJH0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3470
  dmi.product.sku: 0869
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+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 1822587] Re: wifi service stops occasionally.

2020-04-26 Thread Justin Hall
*** This bug is a duplicate of bug 1864505 ***
https://bugs.launchpad.net/bugs/1864505

This behaviour has become noticeably worse since the recent updates the
last couple days (26 April 2020 today).

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1822587/+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 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

2020-04-26 Thread Abdul Rauf
I can also confirm this issue in focal

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1850966/+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 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide

2020-04-26 Thread Jeroenst
Did you find any information in the journalctl which points to this
problem?

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

Title:
  avahi-browse -av is empty, mdns not working in arduino ide

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  When I started the arduino IDE my port list is empty. This list relies
  on multicast DNS which is served by avahi.

  When running the avahi-browse -av command on ubuntu 18.04 I get a list
  of al mdns devices. On ubuntu 20.04 the're no mdns devices reported.

  The avahi-daemon is running. And when executing netstat -nlp | grep
  5353 I see avahi-daemon is listening. When also running tcpdump port
  5353 I see mdns packages arriving. But still avahi-browse -av is
  empty.

  iptables -A shows no rules and policies are accept
  ufw is disabled

  I also removed apparmor but also that didn't make any difference.

  On both ubuntu 18.04 and 20.04 the avahi version is 0.7.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: avahi-daemon 0.7-4ubuntu7
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1874021/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-04-26 Thread Sebastian Unger
Ok, I tried again but changed the command with the version above to:

make SUBLEVEL=0 EXTRAVERSION=-46-generic modules_prepare

Now I get in dmesg:

[ 7851.540982] usb 10-1: new full-speed USB device number 4 using xhci_hcd
[ 7851.788016] usb 10-1: New USB device found, idVendor=0a12, idProduct=0001, 
bcdDevice=88.91
[ 7851.788022] usb 10-1: New USB device strings: Mfr=0, Product=2, 
SerialNumber=0
[ 7851.788026] usb 10-1: Product: CSR8510 A10
[ 7851.802391] usbcore: registered new interface driver btusb
[ 7851.963660] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 7851.963662] Bluetooth: BNEP filters: protocol multicast
[ 7851.963667] Bluetooth: BNEP socket layer initialized
[ 7853.817073] Bluetooth: hci0: command 0x1001 tx timeout
[ 7861.977389] Bluetooth: hci0: CSR: Local version failed (-110)

seb@eragon:~/btDongleTest/linux-source-5.3.0[0]$ hciconfig 
hci0:   Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1

seb@eragon:~/btDongleTest/linux-source-5.3.0[1]$ sudo hciconfig hci0 reset
Can't init device hci0: Connection timed out (110)


Otherwise behaviour is unchanged.

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

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-04-26 Thread Sebastian Unger
Here are the steps I followed (all on Eoan):

sudo apt install kernel-package linux-source flex bison libssl-dev libelf-dev
tar xf /usr/src/linux-source-5.3.0.tar.bz2
cd linux-source-5.3.0
make mrproper
cp /usr/lib/modules/5.3.0-46-generic/build/{.config,Module.symvers} .
make oldconfig
patch -p1 < ../btusb-Enablement-of-HCI_QUIRK_BROKEN_STORED_LINK_KEY-quirk.patch
make EXTRAVERSION=-ubuntu1-1 modules_prepare
make M=drivers/bluetooth
xz drivers/bluetooth/btusb.ko
sudo cp -f drivers/bluetooth/btusb.ko.xz 
/usr/lib/modules/5.3.0-46-generic/updates
sudo depmod
sudo modprobe -r btusb

Now when I insert the dongle, I get
[ 4831.984499] btusb: version magic '5.3.18-ubuntu1-1 SMP mod_unload ' should 
be '5.3.0-46-generic SMP mod_unload '

Obviously, the EXTRAVERSION isn't right yet, but why is that module
reporting itself as 5.3.18 when I built it from 5.3.0 source?

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

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1875032] Re: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at all

2020-04-26 Thread Anuhbav Mishra
Hi There,

Thank you for quick response.
I just discovered that I can even record my voice with my headphone speaker
instead using a microphone because of a bug in Ubuntu 20.04.
Though I already know one can record audio with speaker only, but you can
do it in Ubuntu 20.04 surprised me.
When I plug my JBL T250SI headphone (without mic) and select Headphone to
Select as Audio Device. I am unable to hear any sound, later I discovered
that, in Sound Settings Built in Microphone is selected as Input device.
When I speak I also noticed change in the output. So I recorded a audio
clip which is attached below.
After recording audio I plugged out and plugged in again and select Headset
as Audio Device. And now I can hear every sound and even my own recording
but can't record anymore.
My system specs is already shared with you and there is no built in
microphone and speaker in it. I have also shared specs of my headphone so
that you can be sure there is no microphone in it.
Attachment Details :
1. Sound clip recorded with headphone speaker.
2. My headphone specs.
3. Sound Settings Window

I have every time plugged my headphone in the front audio jack.
*Attention: Play the recording at optimum volume as it has loud high pitch
sound.*

Thanks and Regards,
Anubahv Mishra

On Sun, Apr 26, 2020 at 9:11 AM Hui Wang  wrote:

> I guess after new install of ubuntu os, the default active input source
> should be "Headset Mic". If it is not, please tell me, this is worth to
> investigate.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875032
>
> Title:
>   [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
>   all
>
> Status in alsa-driver package in Ubuntu:
>   New
>
> Bug description:
>   This problem only occurs when I plug my headphone and choose Headphone
> in option.
>   If I choose Headset, though plugging either headphone or headset, it
> works perfectly.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  prm1856 F pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 25 20:05:01 2020
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-osp1-20171027-1
>   InstallationDate: Installed on 2018-09-28 (575 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20171027-10:57
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Symptom_DevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  prm1856 F pulseaudio
>   Symptom_Jack: Black Headphone Out, Front
>   Symptom_Type: No sound at all
>   Title: [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No
> sound at all
>   UpgradeStatus: Upgraded to focal on 2020-04-24 (0 days ago)
>   dmi.bios.date: 05/29/2019
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 2.13.0
>   dmi.board.name: 03NJH0
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A01
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr2.13.0:bd05/29/2019:svnDellInc.:pnVostro3470:pvr:rvnDellInc.:rn03NJH0:rvrA01:cvnDellInc.:ct3:cvr:
>   dmi.product.family: Vostro
>   dmi.product.name: Vostro 3470
>   dmi.product.sku: 0869
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875032/+subscriptions
>


** Attachment added: "speaker_recorded_audio.ogx"
   
https://bugs.launchpad.net/bugs/1875032/+attachment/5360730/+files/speaker_recorded_audio.ogx

** Attachment added: "headphone-specs"
   
https://bugs.launchpad.net/bugs/1875032/+attachment/5360731/+files/headphone-specs

** Attachment added: "soud-settings.png"
   
https://bugs.launchpad.net/bugs/1875032/+attachment/5360732/+files/soud-settings.png

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

Title:
  [Vostro 3470, Realtek ALC891, Black Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This problem only occurs when I plug my headphone and choose Headphone in 
option.
  If I choose Headset, though plugging either headphone or headset, it works 
perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: 

[Touch-packages] [Bug 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-04-26 Thread You-Sheng Yang
https://www.reddit.com/r/AnnePro/comments/e76ij8/csr_40_bluetooth_dongle_on_linux/
It seems this dongle currently takes an additional patch to enable. Does it 
work for you?

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

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started

2020-04-26 Thread Sebastian Unger
Gave it another try with linux-image-unsigned-5.7.0-999-generic on Eoan,
same behaviour.

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

Title:
  CSR8510 based BTA-402 Bluetooth device cannot be started

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In the GUI, I can go to the Bluetooth settings and it shows BT to be
  off. I turn on the little switch at the top but nothing else changes.
  If I navigate away from this page and then back, the switch is off
  again.

  If I try to reset the device on the command line I get:

  seb@eragon:~$ sudo hciconfig hci0 reset
  Can't init device hci0: Connection timed out (110)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu5.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 14:39:55 2020
  EcryptfsInUse: Yes
  InterestingModules: bnep btusb bluetooth
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic 
root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash 
vt.handoff=1 pti=off
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 990FXA-UD3
  dmi.board.vendor: AMD Corporation
  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.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:1 errors:1
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

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