[Touch-packages] [Bug 2060809] [NEW] davinci not opening bro

[Mani P]

Public bug reported:

gpu no to supporter

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 10 18:14:28 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
InstallationDate: Installed on 2024-04-08 (1 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
MachineType: ZEBRONICS H110
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/11/2023
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: H110
dmi.board.vendor: ZEBRONICS
dmi.board.version: Ver:2.32
dmi.chassis.type: 3
dmi.chassis.vendor: ZEBRONICS
dmi.chassis.version: H110
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd01/11/2023:br5.12:svnZEBRONICS:pnH110:pvr:rvnZEBRONICS:rnH110:rvrVer2.32:cvnZEBRONICS:ct3:cvrH110:sku:
dmi.product.name: H110
dmi.sys.vendor: ZEBRONICS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  davinci not opening bro

Status in xorg package in Ubuntu:
  New

Bug description:
  gpu no to supporter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-source-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-firmware-535-535.154.05_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-535/nvidia-kernel-common-535_535.154.05-0ubuntu0.22.04.1_amd64.deb
 
./pool/restricted/n/nvidia-graphics-drivers-390/libnvidia-gl-390_390.157-0ubuntu0.22.04.2_i386.deb
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 10 18:14:28 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation HD Graphics 530 [8086:2212]
  InstallationDate: Installed on 2024-04-08 (1 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: ZEBRONICS H110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=f3ebdcea-9cba-4457-97c2-ffcbed104226 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2023
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.name: H110
  dmi.board.vendor: ZEBRONICS
  dmi.board.version: Ver:2.32
  dmi.chassis.type: 3
  dmi.chassis.vendor: ZEBRONICS
  dmi.chassis.version: H110
  dmi.modalias: 

[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start

[Eduardo P. Gomez]

i got an additional error right here. Some syntax error:


==> root@eduapps:/home/eduardo# software-properties-gtk --open-tab=4
/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogMirror.py:197: 
SyntaxWarning: invalid escape sequence '\.'
  elif 
re.match("^((ftp)|(http)|(file)|(rsync)|(https))://([a-z]|[A-Z]|[0-9]|:|/|\.|~)+$",
 uri) == None:
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  
^^^
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
self.backup_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
 ^^
  File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in 
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file
==> root@eduapps:/home/eduardo# software-properties-gtk
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  
^^^
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir,
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
self.backup_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
source_bkp = SourceEntry(line=source.line,file=source.file)
 ^^
  File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, in 
__init__
raise ValueError("Classic SourceEntry cannot be written to .sources file")
ValueError: Classic SourceEntry cannot be written to .sources file

Original Ubuntu flavour, noble. Ran two times the same command.

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 2046055] [NEW] Sound is not coming on startup and after that

[Srinivasan P]

Public bug reported:

Sound is not coming in initial start up and after that and also pulse
audio is not opening

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:srinivasan   1157 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 10 09:27:33 2023
InstallationDate: Installed on 2021-01-04 (1069 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to mantic on 2023-12-04 (6 days ago)
dmi.bios.date: 07/05/2010
dmi.bios.release: 6.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.04
dmi.board.name: 2A8C
dmi.board.vendor: FOXCONN
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.04:bd07/05/2010:br6.4:svnHewlett-Packard:pn:pvr:rvnFOXCONN:rn2A8C:rvr1.0:cvnHewlett-Packard:ct3:cvr:sku:
dmi.product.family: 103C_53316J G=D
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug mantic third-party-packages wayland-session

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

Title:
  Sound is not coming on startup and after that

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sound is not coming in initial start up and after that and also pulse
  audio is not opening

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:srinivasan   1157 F pipewire
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 10 09:27:33 2023
  InstallationDate: Installed on 2021-01-04 (1069 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to mantic on 2023-12-04 (6 days ago)
  dmi.bios.date: 07/05/2010
  dmi.bios.release: 6.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.04
  dmi.board.name: 2A8C
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.04:bd07/05/2010:br6.4:svnHewlett-Packard:pn:pvr:rvnFOXCONN:rn2A8C:rvr1.0:cvnHewlett-Packard:ct3:cvr:sku:
  dmi.product.family: 103C_53316J G=D
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2046055/+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 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[L. P. Luigi Espenlaub]

Thank you Paul.
I did hit a launchpad problem in that the link
https://bugs.launchpad.net/ubuntu/+bug/2043442/+editstatus
returns

"Lost something?

This page does not exist, or you may not have permission to see it.

If you have been to this page before, it is possible it has been
removed.

Check that you are logged in with the correct account, or that you entered
the address correctly, or search for it:"

Could you point me to where to report this launchpad.net broken link?


I have returned to bug 2043442 and confirmed I could select to edit it
there so no problem for me. However, I would like to help others not to
encounter the same error by reporting it properly.

Between you and Gunnar I have learned much, Thanks,

[image: 邏] L. P. Luigi Espenlaub.
luigiwrit...@gmail.com
Passed 3/4 of a Century mark.  My neck was broken. Almost blown up in the
Bermuda Triangle, Thinking "Death Has A Love / Hate Relationship With Me"
might be a good Auto-Bio title.


On Tue, Nov 14, 2023 at 4:06 PM Paul White <2043...@bugs.launchpad.net>
wrote:

> ** Tags added: mantic
>
> ** Package changed: ubuntu => ibus (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2043442
>
> Title:
>   /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
>
> Status in ibus package in Ubuntu:
>   New
>
> Bug description:
>   Apport captured a system freeze [crash] which required a hard reboot.
>   However I could not confirm that the report was successfully uploaded.
>
>   The /var/log/apport.log entry is as follows.
>   
>   ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable
> already crashed 2 times, ignoring
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   Note:The last line may explain why I could not verify the file
>   upload when I performed the following proceedure per:
>   https://help.ubuntu.com/community/ReportingBugs
>
>   ---
>   luigi@l-g905:~$ ubuntu-bug
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>
>   luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
>
> 7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80
>
>
> https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
> No such file or directory
>   -
>
>
>   This upload fialure seemed confirmed when in:
> https://answers.launchpad.net/ubuntu/+questions?
>   a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
>   "ibus-ui-gtk3" is not mentioned in the release notes bugs section.
>
>   In
>   https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
>   text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above
> both returned "phrase not found"
>
>   I reproduced the executable failure using Terminal with these results
>   --
>   ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
>   Returns:
>   ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
>   (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
>   assertion '(offset + len) <= string_length' failed
>
>   (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
>   assertion '(offset + len) <= string_length' failed
>
>   ** (ibus-ui-gtk3:9353): ERROR **: 23:11:04.

Re: [Touch-packages] [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[L. P. Luigi Espenlaub]

should have read bug #1052005 <1052...@bugs.debian.org> first. Looks like
my reading list is already provided. Thanks
 but clarification on the selection in System Settings vs the im-config
command would ease my uncertainty.
   Thanks again
[image: 邏] L. P. Luigi Espenlaub.
luigiwrit...@gmail.com
Passed 3/4 of a Century mark.  My neck was broken. Almost blown up in the
Bermuda Triangle, Thinking "Death Has A Love / Hate Relationship With Me"
might be a good Auto-Bio title.


On Tue, Nov 14, 2023 at 4:30 PM Gunnar Hjalmarsson <
2043...@bugs.launchpad.net> wrote:

> Thanks for your report.
>
> I see Plasma and Wayland, which reminds me of
> <https://askubuntu.com/q/1490498> and <https://bugs.debian.org/1052005>.
>
> * Have you applied the IBus Wayland virtual keyboard?
>
> * If you have, can you please run this command:
>
>   im-config -n none
>
>   and reboot, and then let us know if that improves things.
>
> ** Bug watch added: Debian Bug tracker #1052005
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005
>
> ** Changed in: ibus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2043442
>
> Title:
>   /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Apport captured a system freeze [crash] which required a hard reboot.
>   However I could not confirm that the report was successfully uploaded.
>
>   The /var/log/apport.log entry is as follows.
>   
>   ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable
> already crashed 2 times, ignoring
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   Note:The last line may explain why I could not verify the file
>   upload when I performed the following proceedure per:
>   https://help.ubuntu.com/community/ReportingBugs
>
>   ---
>   luigi@l-g905:~$ ubuntu-bug
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>
>   luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
>
> 7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80
>
>
> https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
> No such file or directory
>   -
>
>
>   This upload fialure seemed confirmed when in:
> https://answers.launchpad.net/ubuntu/+questions?
>   a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
>   "ibus-ui-gtk3" is not mentioned in the release notes bugs section.
>
>   In
>   https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
>   text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above
> both returned "phrase not found"
>
>   I reproduced the executable failure using Terminal with these results
>   --
>   ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
>   Returns:
>   ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daemon-args --xim\ --panel\ disable
>
>   (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
>   assertion '(offset + len) <= string_length' failed
>
>   (ibus-ui-gtk3:9353): IBUS-CRITICAL **: 23:11:04.233: string_substring:
>   assertion '(offset + len) <= string_length' failed
>
>   ** (

Re: [Touch-packages] [Bug 2043442] Re: /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes

[L. P. Luigi Espenlaub]

Thankyou for your quick response and question.
I opened the following to check
Settings > Input Devices > Keyboard > Generic 104-key PC is selected there
Then noticed the object of your question.
IBus Wayland is apparently the default with Ubuntu Studio.
Help me, my assumptions are often suspect, thus this question. Is selecting
Settings > Input Devices > Virtual Keyboard >  [None] the same as
"im-config -n none" in Konsole
I have selected [None] and will reboot.
Also if you have the time.
Does "im" only concern the Virtual Keyboard, or am I turning off other
features as well?
A point to a source that will help me understand "im" will help me in the
future.


[image: 邏] L. P. Luigi Espenlaub.
luigiwrit...@gmail.com
Passed 3/4 of a Century mark.  My neck was broken. Almost blown up in the
Bermuda Triangle, Thinking "Death Has A Love / Hate Relationship With Me"
might be a good Auto-Bio title.


On Tue, Nov 14, 2023 at 4:30 PM Gunnar Hjalmarsson <
2043...@bugs.launchpad.net> wrote:

> Thanks for your report.
>
> I see Plasma and Wayland, which reminds me of
> <https://askubuntu.com/q/1490498> and <https://bugs.debian.org/1052005>.
>
> * Have you applied the IBus Wayland virtual keyboard?
>
> * If you have, can you please run this command:
>
>   im-config -n none
>
>   and reboot, and then let us know if that improves things.
>
> ** Bug watch added: Debian Bug tracker #1052005
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052005
>
> ** Changed in: ibus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2043442
>
> Title:
>   /usr/libexec/ibus-ui-gtk3 --enable-wayland-im system freezes
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Apport captured a system freeze [crash] which required a hard reboot.
>   However I could not confirm that the report was successfully uploaded.
>
>   The /var/log/apport.log entry is as follows.
>   
>   ERROR: apport (pid 17772) 2023-11-13 17:17:02,197: this executable
> already crashed 2 times, ignoring
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,820: called for pid 17786,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 27019) 2023-11-13 21:07:39,821: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 27019) 2023-11-13 21:07:40,821: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   INFO: apport (pid 27019) 2023-11-13 21:07:42,687: wrote report
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,084: called for pid 27746,
> signal 11, core limit 0, dump mode 1
>   INFO: apport (pid 29410) 2023-11-13 21:38:11,085: executable:
> /usr/libexec/ibus-ui-gtk3 (command line "/usr/libexec/ibus-ui-gtk3
> --enable-wayland-im --exec-daemon --daemon-args --xim\ --panel\ disable")
>   ERROR: apport (pid 29410) 2023-11-13 21:38:12,085: gdbus call error:
> Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.gnome.SessionManager was not provided by any .service files
>
>   Note:The last line may explain why I could not verify the file
>   upload when I performed the following proceedure per:
>   https://help.ubuntu.com/community/ReportingBugs
>
>   ---
>   luigi@l-g905:~$ ubuntu-bug
> /var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash
>
>   luigi@l-g905:~$ sudo cat /var/lib/whoopsie/whoopsie-id
>
> 7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80
>
>
> https://errors.ubuntu.com/user/7a0c123f5172023e795f73a584fa57e5efd8e12b9c45fd40142d884f4260a9abe2b1d30152e6d8f6c7cbc21190d542ebda3b4cfc316047ba6be306793ee2fe80:
> No such file or directory
>   -
>
>
>   This upload fialure seemed confirmed when in:
> https://answers.launchpad.net/ubuntu/+questions?
>   a search found no Questions matching "ibus-ui-gtk3" for Ubuntu
>   "ibus-ui-gtk3" is not mentioned in the release notes bugs section.
>
>   In
>   https://errors.ubuntu.com/?release=Ubuntu%2023.10=day
>   text Searches for _usr_libexec_ibus-ui-gtk3 and the "Whoopsie-id" above
> both returned "phrase not found"
>
>   I reproduced the executable failure using Terminal with these results
>   --
>   ~$ /usr/libexec/ibus-ui-gtk3 --enable-wayland-im --exec-daemon
> --daem

[Touch-packages] [Bug 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Tais P. Hansen]

Thanks for the tip. Not sure why both were enabled but disabling
systemd-networkd.service fixes the long wait during boot for me.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Tais P. Hansen]

Tested 252.5-2ubuntu3.2 on Ubuntu 23.04 (lunar) and it still hangs for 2
minutes during boot.

$ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online --timeout=10
Found link 7
Found link 6
Found link 5
Found link 4
Found link 3
Found link 2
Found link 1
lo: link is ignored
wlp6s0: link is not managed by networkd (yet?).
virbr2: link is not managed by networkd (yet?).
enp5s0: link is not managed by networkd (yet?).
enp4s0: link is not managed by networkd (yet?).
virbr0: link is not managed by networkd (yet?).
tailscale0: link is not managed by networkd (yet?).
Timeout occurred while waiting for network connectivity.

Desktop system.

Both systemd-networkd and NetworkManager services are running and
active.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/10-lxc.yaml # Use whatever editor you like
  $ cat /etc/netplan/10-lxc.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2024540] Re: Vulnerability Can Gain Access

[Vaishakh P]

Can rate limiting for ssh can be enabled by default on installation, it
can prevent 80% of the attacks.

** Summary changed:

- Vulnerability Can Gain Access even with Time OTP Enabled
+ Vulnerability Can Gain Access

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

Title:
  Vulnerability Can Gain Access

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

There is an entry called SYSV. It there some problem in it.

** Attachment added: "Screenshot_20230627_163157_Remmina.png"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+attachment/5682254/+files/Screenshot_20230627_163157_Remmina.png

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

Title:
  Vulnerability Can Gain Access

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

I am posting current scan report of rkhunter after connecting with
windows computer using remmina, since i have added Time based OTP, may
be i am saved from installation of XOR DDOS malware this time.

** Attachment added: "rkhunter.log"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+attachment/5681584/+files/rkhunter.log

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

Title:
  Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

I am attaching sshd_config file

** Attachment added: "sshd_config"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+attachment/5681583/+files/sshd_config

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

Title:
  Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

I think when i reinstalled the system i lost the logs, and this post is panic 
driven, i should have analysed my system without reinstalling so i can find out 
wheather it is related to openssh or remmina, i am connecting to a windows 
system using remmina, may be due to that my system is getting infected.
Anyway I am posting sshd and sshd_config files here.

** Attachment added: "sshd"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+attachment/5681582/+files/sshd

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

Title:
  Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

** Summary changed:

- SSH Vulnerability Can Gain Access even with Time OTP Enabled
+ Vulnerability Can Gain Access even with Time OTP Enabled

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

Title:
  Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2024540] Re: SSH Vulnerability Can Gain Access even with Time OTP Enabled

[Vaishakh P]

** Information type changed from Private Security to Public Security

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

Title:
  SSH Vulnerability Can Gain Access even with Time OTP Enabled

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,

  We have noticed that when allowing firewall rule to open SSH port 22
  of my computer, somebody in the local network gets access to the
  system, to prevent it we had added two factor authentication by adding
  Time based OTP using google authenticator and root login is disabled
  in configuration, our network have windows systems which are
  compromised they are infecting this system and installing XOR DDOS
  Malware in my system, the rkhunter log shows variation in lot of
  system binary files, The XOR DDOS is overwriting lot of files before
  installing itself in the system, i think there is some critical bug in
  ssh system, we thought they are bruteforcing ssh password, but even
  after putting time based two factor authentication they are able to
  infiltrate the system and gain access.

  The ubuntu we are using is 22.04 LTS Jammy.
  Our systems are constantly attacked by XOR DDOS Rootkit.
  We had even rate limited the ssh even then they gets access added OTP 
verification also. we think there is some severe security issue with ssh.

  More Details About XOR DDOS Here
  
https://www.microsoft.com/en-us/security/blog/2022/05/19/rise-in-xorddos-a-deeper-look-at-the-stealthy-ddos-malware-targeting-linux-devices/

  Also there is no option to attach multiple files here.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2024540/+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 2023008] Re: cannot install libegl-mesa0 on 22.04.2 LTS

[Jarno P]

** Description changed:

  # Summary
  
  `apt install libegl-mesa0` does not install it due to a dependency
  conflict in the apt repo.
  
  libegl-mesa0 has dependency to explicit versions of:
  * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
  * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)
  
  But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2.
  
  # Expected behavior
  
  These closely linked packages to be up-to-date in the Ubuntu repo.
  
+ 
+ # Workaround
+ 
+ It is possible to install libegl-mesa0 by first downgrading the
+ conflicting package versions:
+ 
+ apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1
+ apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1
+ 
+ and then installing it normally:
+ 
+ apt install libegl-mesa0
+ 
  # Details
- 
  
  ```
  # apt install libegl-mesa0
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
-  libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
- Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
+  libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
+ Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.`
  ```
  
  1) Is the hard dependency (=) really necessary?
  
  2) Or should I just downgrade existing libglapi-mesa and libgbm1
  installs? The difference is minor patch version only so I am hesitant to
  do so (there must have been a reasons for the .2 patch).
  
  # Environment
  
- ## cat /etc/lsb-release 
+ ## cat /etc/lsb-release
  ```
  cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
  ```
  
  # apt-cache policy
  
  ```
  apt-cache policy  libegl-mesa0
  libegl-mesa0:
-   Installed: (none)
-   Candidate: 22.2.5-0ubuntu0.1~22.04.1
-   Version table:
-  22.2.5-0ubuntu0.1~22.04.1 500
- 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
-  22.0.1-1ubuntu2 500
- 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
+   Installed: (none)
+   Candidate: 22.2.5-0ubuntu0.1~22.04.1
+   Version table:
+  22.2.5-0ubuntu0.1~22.04.1 500
+ 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
+  22.0.1-1ubuntu2 500
+ 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  
  ```

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

Title:
  cannot install libegl-mesa0 on 22.04.2 LTS

Status in mesa package in Ubuntu:
  New

Bug description:
  # Summary

  `apt install libegl-mesa0` does not install it due to a dependency
  conflict in the apt repo.

  libegl-mesa0 has dependency to explicit versions of:
  * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
  * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)

  But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2.

  # Expected behavior

  These closely linked packages to be up-to-date in the Ubuntu repo.

  
  # Workaround

  It is possible to install libegl-mesa0 by first downgrading the
  conflicting package versions:

  apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1
  apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1

  and then installing it normally:

  apt install libegl-mesa0

  # Details

  ```
  # apt install libegl-mesa0
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.`
  ```

  1) Is the hard dependency (=) really necessary?

  2) Or should I just downgrade existing libglapi-mesa and libgbm1
  installs? The difference is minor patch version only so I am hesitant
  to do so (there 

[Touch-packages] [Bug 2023008] [NEW] cannot install libegl-mesa0 on 22.04.2 LTS

[Jarno P]

Public bug reported:

# Summary

`apt install libegl-mesa0` does not install it due to a dependency
conflict in the apt repo.

libegl-mesa0 has dependency to explicit versions of:
* libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
* libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)

But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2.

# Expected behavior

These closely linked packages to be up-to-date in the Ubuntu repo.


# Workaround

It is possible to install libegl-mesa0 by first downgrading the
conflicting package versions:

apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1
apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1

and then installing it normally:

apt install libegl-mesa0

# Details

```
# apt install libegl-mesa0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
E: Unable to correct problems, you have held broken packages.`
```

1) Is the hard dependency (=) really necessary?

2) Or should I just downgrade existing libglapi-mesa and libgbm1
installs? The difference is minor patch version only so I am hesitant to
do so (there must have been a reasons for the .2 patch).

# Environment

## cat /etc/lsb-release
```
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
```

# apt-cache policy

```
apt-cache policy  libegl-mesa0
libegl-mesa0:
  Installed: (none)
  Candidate: 22.2.5-0ubuntu0.1~22.04.1
  Version table:
 22.2.5-0ubuntu0.1~22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
 22.0.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

```

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


** Tags: mesa

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

Title:
  cannot install libegl-mesa0 on 22.04.2 LTS

Status in mesa package in Ubuntu:
  New

Bug description:
  # Summary

  `apt install libegl-mesa0` does not install it due to a dependency
  conflict in the apt repo.

  libegl-mesa0 has dependency to explicit versions of:
  * libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
  * libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)

  But the latest in ubuntu repos are versions 22.2.5-0ubuntu0.1~22.04.2.

  # Expected behavior

  These closely linked packages to be up-to-date in the Ubuntu repo.

  
  # Workaround

  It is possible to install libegl-mesa0 by first downgrading the
  conflicting package versions:

  apt install libgbm1=22.2.5-0ubuntu0.1~22.04.1
  apt install libglapi-mesa=22.2.5-0ubuntu0.1~22.04.1

  and then installing it normally:

  apt install libegl-mesa0

  # Details

  ```
  # apt install libegl-mesa0
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libegl-mesa0 : Depends: libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  Depends: libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1) but 
22.2.5-0ubuntu0.1~22.04.2 is to be installed
  E: Unable to correct problems, you have held broken packages.`
  ```

  1) Is the hard dependency (=) really necessary?

  2) Or should I just downgrade existing libglapi-mesa and libgbm1
  installs? The difference is minor patch version only so I am hesitant
  to do so (there must have been a reasons for the .2 patch).

  # Environment

  ## cat /etc/lsb-release
  ```
  cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=22.04
  DISTRIB_CODENAME=jammy
  DISTRIB_DESCRIPTION="Ubuntu 22.04.2 LTS"
  ```

  # apt-cache policy

  ```
  apt-cache policy  libegl-mesa0
  libegl-mesa0:
    Installed: (none)
    Candidate: 22.2.5-0ubuntu0.1~22.04.1
    Version table:
   22.2.5-0ubuntu0.1~22.04.1 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
   22.0.1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  ```

To manage 

[Touch-packages] [Bug 2020662] [NEW] CREATIVE Sound Blaster AE-5 Plus not recognized / seems to use wrong driver

[Maurice P.]

Public bug reported:

Version: Ubuntu 22.10

---

What I expected:
Fresh dual-boot installation, detects my Creative Sound Blaster AE-5 Plus 
Soundcard and lists it as an available audio device using the right driver.

What happened instead:
Soundcard is not listed as usable audio device and seems to use the wrong 
driver. It seems to be detected, based on the output of inxi and lspci. Uses 
snd-hda-intel driver instead of snd-hda-codec-ca0132.

The patch_ca0132.c file of the kernel seems to assign the driver for
Sound Blaster cards, but the card I own seems to have a different chip-
id (0x0012) than the one that is already present in there (0x0191).
Might be another new revisions, as I bought mine at the start of 2023.

---

$ inxi -AaaA

Audio:
  Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series]
driver: snd_hda_intel v: kernel pcie: bus-ID: 3-2.3.1.4:8
chip-ID: 0951:171d gen: 1 class-ID: 0300 speed: 2.5 GT/s lanes: 1
serial: 4100 bus-ID: 04:00.0 chip-ID: 1102:0012 class-ID: 0403
  Device-2: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 1002:ab28
class-ID: 0403
  Device-3: AMD Starship/Matisse HD Audio vendor: ASRock
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-4: Kingston HyperX QuadCast S type: USB
driver: hid-generic,snd-usb-audio,usbhid
  Device-5: Logitech Webcam C270 type: USB driver: snd-usb-audio,uvcvideo
bus-ID: 3-2.3.2:6 chip-ID: 046d:0825 class-ID: 0102 serial: D98AA440
  Device-6: SteelSeries ApS GameDAC type: USB
driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-2.4.2:11
chip-ID: 1038:1282 class-ID: 0300 serial: 
  Sound Server-1: ALSA v: k5.19.0-42-generic running: yes
  Sound Server-2: PulseAudio v: 16.1 running: yes
  Sound Server-3: PipeWire v: 0.3.58 running: no

---

$ lspci  -nn | grep -i audio

04:00.0 Audio device [0403]: Creative Labs Sound Core3D [Sound Blaster
Recon3D / Z-Series] [1102:0012] (rev 01)

08:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Navi
21/23 HDMI/DP Audio Controller [1002:ab28]

0a:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD]
Starship/Matisse HD Audio Controller [1022:1487]

---

https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_ca0132.c#L1313

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.19.0-42.43-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  lubjan 5159 F pulseaudio
 /dev/snd/controlC0:  lubjan 5159 F pulseaudio
 /dev/snd/controlC2:  lubjan 5159 F pulseaudio
 /dev/snd/controlC1:  lubjan 5159 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed May 24 12:36:25 2023
InstallationDate: Installed on 2023-05-21 (2 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to kinetic on 2023-05-22 (1 days ago)
dmi.bios.date: 04/14/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: L2.71
dmi.board.name: B550M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrL2.71:bd04/14/2023:br5.17:svnToBeFilledByO.E.M.:pnB550MPro4:pvrToBeFilledByO.E.M.:rvnASRock:rnB550MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: B550M Pro4
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-05-24T12:36:12.304586

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


** Tags: amd64 apport-bug ca0132 hda kinetic wayland-session

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

Title:
  CREATIVE Sound Blaster AE-5 Plus not recognized / seems to use wrong
  driver

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Version: Ubuntu 22.10

  ---

  What I expected:
  Fresh dual-boot installation, detects my Creative Sound Blaster AE-5 Plus 
Soundcard and lists it as an available audio device using the right driver.

  What happened instead:
  Soundcard is not listed as usable audio device and seems to use the wrong 
driver. It seems to be detected, 

[Touch-packages] [Bug 2007004] Re: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected

[Michael P]

changed package from bluez to linux and updated text

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

** Description changed:

  Ubuntu 22.04.01 /  ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse.
- Fully updated via apt.
  
- Everything worked OK until sometime around early January 2023 (it may
- have started earlier, but I only noticed it the first time I moved to a
- location without WiFi).
+ This problem occurs with the rtw88_8821ce driver
+ Workaround was to blacklist rtw88_8821ce and install rtl8821ce
  
- Since then, everything works OK as long as I am connected to WiFi. The
- moment I disconnect from a WiFi network, or disable WiFi altogether, the
- mouse begins to rapidly disconnect/connect in a loop about 3-4 times a
- second. If I boot up somewhere where I have no WiFi signal, same thing
- happens.
  
- If I boot with an older 22.04.01 live USB  - no problem
- If I boot with a recent 22.10 live USB - same problem
+   root@ithaca:~ # uname -a
+   Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64
+   GNU/Linux
  
-   root@ithaca:~ # uname -a  
-   Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 
-   GNU/Linux
- 
-   root@ithaca:~ # inxi -EMN
-   Machine:
- Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
-   v: 1.0 serial: 
- Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
-   UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
-   Network:
- Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
-   driver: rtw_8821ce
-   Bluetooth:
- Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
- Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1
+   root@ithaca:~ # inxi -EMN
+   Machine:
+ Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
+   v: 1.0 serial: 
+ Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
+   UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
+   Network:
+ Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
+   driver: rtw_8821ce
+   Bluetooth:
+ Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
+ Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1
  
  Output of running bluetoothctl while this happens:
  
-   root@ithaca:/var/log # bluetoothctl
-   Agent registered
- (At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
-  then about 10 seconds elapse, then the below messages start)
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
- (This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
-   [MX Anywhere 2S]# 
-   [MX Anywhere 2S]# 
+   root@ithaca:/var/log # bluetoothctl
+   Agent registered
+ (At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
+  then about 10 seconds elapse, then the below messages start)
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+ (This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
+   [MX Anywhere 2S]#
+   [MX Anywhere 2S]#
  
  kern.log messages while this happens:
  < I disconnect from Wifi>
-   Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from 
de:5d:xx:xx:xx:xx by 
-   local choice (Reason: 3=DEAUTH_LEAVING)
-   Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx 
-   with macid 0 left
-   Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87
-   Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse 
as 

[Touch-packages] [Bug 2007004] [NEW] Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected

[Michael P]

Public bug reported:

Ubuntu 22.04.01 /  ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse.
Fully updated via apt.

Everything worked OK until sometime around early January 2023 (it may
have started earlier, but I only noticed it the first time I moved to a
location without WiFi).

Since then, everything works OK as long as I am connected to WiFi. The
moment I disconnect from a WiFi network, or disable WiFi altogether, the
mouse begins to rapidly disconnect/connect in a loop about 3-4 times a
second. If I boot up somewhere where I have no WiFi signal, same thing
happens.

If I boot with an older 22.04.01 live USB  - no problem
If I boot with a recent 22.10 live USB - same problem

  root@ithaca:~ # uname -a  
  Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 
  GNU/Linux

  root@ithaca:~ # inxi -EMN
  Machine:
Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
  v: 1.0 serial: 
Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
  UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
  Network:
Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
  driver: rtw_8821ce
  Bluetooth:
Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1

Output of running bluetoothctl while this happens:

  root@ithaca:/var/log # bluetoothctl
  Agent registered
(At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
 then about 10 seconds elapse, then the below messages start)
  [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
  [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
  [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
(This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
  [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
  [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
  [MX Anywhere 2S]# 
  [MX Anywhere 2S]# 

kern.log messages while this happens:
< I disconnect from Wifi>
  Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from 
de:5d:xx:xx:xx:xx by 
  local choice (Reason: 3=DEAUTH_LEAVING)
  Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx 
  with macid 0 left
  Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S Keyboard 
as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87
  Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input88
  Feb 11 20:46:33 ithaca kernel: [ 3403.249194] hid-generic 
0005:046D:B01A.0019: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
  Feb 11 20:46:57 ithaca kernel: [ 3427.685563] input: MX Anywhere 2S Keyboard 
as /devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input90
  Feb 11 20:46:57 ithaca kernel: [ 3427.686055] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.001A/input/input91
  Feb 11 20:46:57 ithaca kernel: [ 3427.686305] hid-generic 
0005:046D:B01A.001A: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
< I reconnect to Wifi>
  Feb 11 20:47:10 ithaca kernel: [ 3440.394111] input: MX Anywhere 2S Keyboard 
as /devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input93
  Feb 11 20:47:10 ithaca kernel: [ 3440.399568] input: MX Anywhere 2S Mouse as 
/devices/virtual/misc/uhid/0005:046D:B01A.001B/input/input94
  Feb 11 20:47:10 ithaca kernel: [ 3440.399889] hid-generic 
0005:046D:B01A.001B: input,hidraw3: BLUETOOTH HID v0.03 Keyboard [MX Anywhere 
2S] on 20:4e:xx:xx:xx:xx
  Feb 11 20:47:19 ithaca kernel: [ 3449.263587] wlo1: authenticate with 
de:5d:xx:xx:xx:xx
  Feb 11 20:47:19 ithaca kernel: [ 3449.930945] wlo1: send auth to 
de:5d:xx:xx:xx:xx (try 1/3)
  Feb 11 20:47:19 ithaca kernel: [ 3449.935512] wlo1: authenticated
  Feb 11 20:47:19 ithaca kernel: [ 3449.939267] wlo1: associate with 
de:5d:xx:xx:xx:xx (try 1/3)
  Feb 11 20:47:19 ithaca kernel: [ 3449.943365] wlo1: RX AssocResp from 
de:5d:xx:xx:xx:xx (capab=0x431 status=0 aid=2)
  Feb 11 20:47:19 ithaca kernel: [ 3449.943395] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx joined with macid 0
  Feb 11 20:47:19 ithaca kernel: [ 3449.943789] wlo1: associated
  Feb 11 20:47:19 ithaca kernel: [ 3449.995269] IPv6: ADDRCONF(NETDEV_CHANGE): 
wlo1: link becomes ready

Nothing logged in dmesg

After reconnecting WiFi, everything works OK again.

I assume bluez is the correct package - please let me know if otherwise,

[Touch-packages] [Bug 1993560] [NEW] wlan errors

[P]

Public bug reported:

I do experience intermittent WLAN problems, with connections getting
lost after a few seconds, and continuous (unsuccessful) reconnection
attempts.

Unfortunately, I am unable to provide a specific error description, but
in dmesg I see lines related to iwlwifi which suggest some microcode
does not execute as it should. I add these as attachment.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Oct 19 17:34:47 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:22e7]
InstallationDate: Installed on 2022-10-15 (4 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 21CCS3HD00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=9f272456-a6f0-404d-b699-e1e936418b0c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2022
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET65W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CCS3HD00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CCS3HD00:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CCS3HD00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CCS3HD00
dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy kubuntu ubuntu

** Attachment added: "iwlwifi-related log"
   
https://bugs.launchpad.net/bugs/1993560/+attachment/5625253/+files/iwlwifi.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/1993560

Title:
  wlan errors

Status in xorg package in Ubuntu:
  New

Bug description:
  I do experience intermittent WLAN problems, with connections getting
  lost after a few seconds, and continuous (unsuccessful) reconnection
  attempts.

  Unfortunately, I am unable to provide a specific error description,
  but in dmesg I see lines related to iwlwifi which suggest some
  microcode does not execute as it should. I add these as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
  Uname: Linux 5.15.0-52-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 19 17:34:47 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22e7]
  InstallationDate: Installed on 2022-10-15 (4 days ago)
  InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: LENOVO 21CCS3HD00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic 
root=UUID=9f272456-a6f0-404d-b699-e1e936418b0c ro quiet splash vt.handoff=7
  SourcePa

[Touch-packages] [Bug 1960947] Re: Graphical issues for GtKGL in software rendering

[J-P Nurmi]

I can confirm that libgtk-3-0 3.24.20-0ubuntu1.1 from focal-proposed
fixes the rendering issue.

I have tested with:

1) the attached minimal test case:

gcc -o testcase testcase.c `pkg-config --cflags --libs gtk+-3.0`
./testcase

2) a full-blown flutter app:

snap install --classic flutter
flutter config --enable-linux-desktop
flutter create test_app
cd test_app
flutter run


** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Graphical issues for GtKGL in software rendering

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Fix Committed

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+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 1960947] Re: Graphical issues for GtKGL in software rendering

[J-P Nurmi]

Hi all. The conditions for reproducing the issue: CSD + OpenGL + swrast.

Notice that the GTK GL example doesn't use CSD i.e. it doesn't set a
custom GtkWindow titlebar. I have attached a small test case that
reproduces the issue.

** Attachment added: "testcase.c"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+attachment/5561410/+files/testcase.c

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

Title:
  Graphical issues for GtKGL in software rendering

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Fix Committed

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+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 1913061] Re: systemd-coredump not available for systemd 245.4-4ubuntu3.2

[Georg P]

Okay, turns out it wasn't really a bug... Sorry! I had managed to remove
the focal-updates repository from my sources, and therefore didn't get
the latest version of the package...

Sorry for the inconvenience, this can be closed.

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

Title:
  systemd-coredump not available for systemd 245.4-4ubuntu3.2

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I am trying to install systemd-coredump, but it fails with the
  following error message:

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   systemd-coredump : Depends: systemd (= 245.4-4ubuntu3)
  E: Unable to correct problems, you have held broken packages.

  Following discussion on my question i am opening a bug report (link to
  question:
  https://answers.launchpad.net/ubuntu/+source/systemd/+question/695171)

  As far as i understand i have a version of systemd for which no
  systemd-coredump exists (or is at least not specified). It seems like
  this wasn't necessary for many users that had an older version of
  systemd-coredump installed and simply held the older package, but
  leads to this error if systemd-coredump has not been previously
  installed.

  Thanks a lot, 
  Georg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1913061/+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 1913061] [NEW] systemd-coredump not available for systemd 245.4-4ubuntu3.2

[Georg P]

Public bug reported:

Hi,

I am trying to install systemd-coredump, but it fails with the following
error message:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 systemd-coredump : Depends: systemd (= 245.4-4ubuntu3)
E: Unable to correct problems, you have held broken packages.

Following discussion on my question i am opening a bug report (link to
question:
https://answers.launchpad.net/ubuntu/+source/systemd/+question/695171)

As far as i understand i have a version of systemd for which no systemd-
coredump exists (or is at least not specified). It seems like this
wasn't necessary for many users that had an older version of systemd-
coredump installed and simply held the older package, but leads to this
error if systemd-coredump has not been previously installed.

Thanks a lot, 
Georg

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

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

Title:
  systemd-coredump not available for systemd 245.4-4ubuntu3.2

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I am trying to install systemd-coredump, but it fails with the
  following error message:

  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   systemd-coredump : Depends: systemd (= 245.4-4ubuntu3)
  E: Unable to correct problems, you have held broken packages.

  Following discussion on my question i am opening a bug report (link to
  question:
  https://answers.launchpad.net/ubuntu/+source/systemd/+question/695171)

  As far as i understand i have a version of systemd for which no
  systemd-coredump exists (or is at least not specified). It seems like
  this wasn't necessary for many users that had an older version of
  systemd-coredump installed and simply held the older package, but
  leads to this error if systemd-coredump has not been previously
  installed.

  Thanks a lot, 
  Georg

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

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

[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

It appears that one of the recent updates fixed this 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/1902580

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

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

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

  
  Note: File samples are after reinstalling. (working state)

  Thank You,
  Jeff

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

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

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

[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

systemctl --user status pulseaudio.service

** Attachment added: "systemctl --user status pulseaudio.service"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902580/+attachment/5438826/+files/systemctl_--user_status_pulseaudio.service.txt

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

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

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

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

  
  Note: File samples are after reinstalling. (working state)

  Thank You,
  Jeff

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

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

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

[Touch-packages] [Bug 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS

[Simon P.]

I can confirm this problem for Ubuntu 20.04 and 20.10 on a Thinkpad
X260.

The bluetooth button in the Bluetooth settings does nothing after it is
automatically turned off. However, I can enable Bluetooth again by
turning it off and on again Bluetooth in the menu top bar.

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1774640/+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 1903519] [NEW] Not able to get ppd list from cups server.

[prashant p]

Public bug reported:


Distro Name : Ubuntu 20.10
Printers : All
 
While adding printer through hplip not able to get get ppd list from cups 
server.
>From localhost also not able select hp ppd.
 Steps to reproduce:
1.  Open browser
2.  Go to localhost:631 > administration
3.  Add printer > select printer  ( not ask for custom ppd direct redirect 
to successful window)
 
This issue is inconsistent 5-6 time not working out 10 tries.
The same code is working fine on ubuntu 20.04 which has same cups version as 
20.10.
 
Installed Package:
Cups : 2.3.3
Cups-devel : 2.3.3-3
Cups-image : 2.2.3-3
 
Error with our code:
Error : No ppd found for model “Model name”
 
 
Any update or changes that will fix this issue.

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

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

Title:
  Not able to get ppd list from cups server.

Status in cups package in Ubuntu:
  New

Bug description:
  
  Distro Name : Ubuntu 20.10
  Printers : All
   
  While adding printer through hplip not able to get get ppd list from cups 
server.
  From localhost also not able select hp ppd.
   Steps to reproduce:
  1.Open browser
  2.Go to localhost:631 > administration
  3.Add printer > select printer  ( not ask for custom ppd direct redirect 
to successful window)
   
  This issue is inconsistent 5-6 time not working out 10 tries.
  The same code is working fine on ubuntu 20.04 which has same cups version as 
20.10.
   
  Installed Package:
  Cups : 2.3.3
  Cups-devel : 2.3.3-3
  Cups-image : 2.2.3-3
   
  Error with our code:
  Error : No ppd found for model “Model name”
   
   
  Any update or changes that will fix this issue.

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

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

[Touch-packages] [Bug 1902580] Re: [Asus ZenBook UX425IA] No sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

** Description changed:

  My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.
  
  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.
  
  How I re-install pulseaudio:
  
  sudo apt-get install --reinstall pulseaudio
  
  I have tried just killing the pulseaudio service, and letting it restart
  on it's own. It restarts, but no audio. Reinstalling seems to do the
  trick though.
+ 
+ 
+ Note: File samples are after reinstalling. (working state)
  
  Thank You,
  Jeff
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Status in pulseaudio package in Ubuntu:
  Confirmed

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

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

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

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

  
  Note: File samples are after reinstalling. (working state)

  Thank You,
  Jeff

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

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

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

[Touch-packages] [Bug 1902580] Re: Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

** Summary changed:

- Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after 
every reboot.
+ Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall pulseaudio after 
every reboot.

** Description changed:

- My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I
+ My Xubuntu 20.10 installation has no sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.
  
  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.
  
  How I re-install pulseaudio:
  
  sudo apt-get install --reinstall pulseaudio
  
  I have tried just killing the pulseaudio service, and letting it restart
  on it's own. It restarts, but no audio. Reinstalling seems to do the
  trick though.
  
  Thank You,
  Jeff
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  Xubuntu 20.10 has no sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  New

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

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

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

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

  Thank You,
  Jeff

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

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

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

[Touch-packages] [Bug 1902580] [NEW] Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall pulseaudio after every reboot.

[Jeff P]

Public bug reported:

My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I
reinstall pulseaudio after every reboot.

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

How I re-install pulseaudio:

sudo apt-get install --reinstall pulseaudio

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

Thank You,
Jeff

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

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


** Tags: amd64 apport-bug groovy

** Description changed:

  My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.
  
  pulseaudio does survive a suspend.  Just a hard reset or power cycle
  causes it to fail.
  
- How I re-install pulseaudio (obvious but just in case) Xubuntu 20.10 has
- No Sound (Dummy Output) unless I reinstall pulseaudio after every
- reboot.
+ How I re-install pulseaudio:
  
  sudo apt-get install --reinstall pulseaudio
  
  I have tried just killing the pulseaudio service, and letting it restart
  on it's own. It restarts, but no audio. Reinstalling seems to do the
  trick though.
- 
  
  Thank You,
  Jeff
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Mon Nov  2 13:42:36 2020
  InstallationDate: Installed on 2020-11-02 (0 days ago)
  InstallationMedia: Xubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX425IA.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX425IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX425IA.306:bd08/29/2020:br5.16:efr3.6:svnASUSTeKCOMPUTERINC.:pnZenBookUX425IA_UM425IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX425IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX425IA_UM425IA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

Title:
  Xubuntu 20.10 has No Sound (Dummy Output) unless I reinstall
  pulseaudio after every reboot.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  My Xubuntu 20.10 instsallation has No Sound (Dummy Output) unless I
  reinstall pulseaudio after every reboot.

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

  How I re-install pulseaudio:

  sudo apt-get install --reinstall pulseaudio

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

  Thank You,
  Jeff

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: 

[Touch-packages] [Bug 1896774] Re: Headphone output stopped working after perfoming dist-upgrade

[P Kobel]

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

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

Title:
  Headphone output stopped working after perfoming dist-upgrade

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

Bug description:
  # What happened:

  - Upgraded packages using: sudo apt-get update && sudo apt-get dist-
  upgrade

  - Following packages were installed:
  pulseaudio-utils:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio-module-x11:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio-module-bluetooth:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14
  pulseaudio:amd64 1:8.0-0ubuntu3.12 1:8.0-0ubuntu3.14

  - Find the complete update log attached (dpkg.log written to
  update_log_23_09_20.txt)

  # Bug description:

  - Loudspeaker works fine. Inserting headphones is detected correctly
  in sound settings but no physical output is generated on the headphone
  port.


  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-118.119~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-118-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 2210 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 15:32:02 2020
  InstallationDate: Installed on 2018-01-11 (986 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  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:  pascal 2210 F pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [UX430UQ, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: Upgraded to xenial on 2018-09-20 (734 days ago)
  dmi.bios.date: 07/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UQ.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UQ
  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.:bvrUX430UQ.302:bd07/05/2017:svnASUSTeKCOMPUTERINC.:pnUX430UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1896774/+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 1872551] Re: software-properties-qt: nvidia driver version switch fails

[Hans P . Möller]

could you test adding this to /lib/python3/dist-
packages/softwareproperties/qt/SoftwarePropertiesQt.py
SoftwarePropertiesQt.py ? For me testing with nvidia is not easy

--- /lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py
2020-04-14 09:16:19.370592334 -0400
+++ SoftwarePropertiesQt.py 2020-04-14 09:02:21.894527421 -0400
@@ -78,6 +78,17 @@
   QWidget.__init__(self)
   uic.loadUi("%s/designer/main.ui" % datadir, self)
 
+def get_dependencies(apt_cache, package_name, pattern=None):
+""" Get the package dependencies, which can be filtered out by a pattern 
"""
+dependencies = []
+for or_group in apt_cache[package_name].candidate.dependencies:
+for dep in or_group:
+if dep.rawtype in ["Depends", "PreDepends"]:
+dependencies.append(dep.name)
+if pattern:
+dependencies = [ x for x in dependencies if x.find(pattern) != -1 ]
+return dependencies
+
 class SoftwarePropertiesQt(SoftwareProperties):
   def __init__(self, datadir=None, options=None, parent=None, file=None, 
attachWinID=None):
 """ Provide a Qt-based graphical user interface to configure

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

Title:
  software-properties-qt: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails

[Hans P . Möller]

Could you please test with software-properties-gtk? (you might need to install 
the package)
Then we could know if it is a software-properties-qt or a software-properties-* 
problem.
Thanks!

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

Title:
  kubuntu-driver-manager: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1856376] Re: "Dummy Output" -- built-in audio not detected

[P. Thibault]

I have apparently the same issue on my Lenovo X1 4th gen since recent
upgrade:

lspci -v | grep -A7 -i "audio"
00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio 
Controller (rev 11) (prog-if 80)
Subsystem: Lenovo Cannon Point-LP High Definition Audio Controller
Flags: bus master, fast devsel, latency 64, IRQ 16
Memory at ea33c000 (64-bit, non-prefetchable) [size=16K]
Memory at ea00 (64-bit, non-prefetchable) [size=1M]
Capabilities: 
Kernel driver in use: snd_soc_skl
Kernel modules: snd_hda_intel, snd_soc_skl, sof_pci_dev

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

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

Title:
  "Dummy Output" -- built-in audio not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I no longer seem to be getting audio on my laptop, and only "Dummy
  Output" shows up in the sound settings dialog. This sounds similar to
  LP #1781294 (including the same PCI device), though that seems to have
  been marked expired.

  alex@tapada:~$ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 64, IRQ 159
Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K]
Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  alex@tapada:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  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 23:38:35 2019
  InstallationDate: Installed on 2019-08-31 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  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:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1845645] Re: Emacs logs AT-SPI warnings to console on startup

[Nicholas P]

Launching Emacs outside of gdm seems like a typical use case for a
headless client, for instance using Virtualbox and ssh.  I also noticed
placing this in the environment:

export NO_AT_BRIDGE=1

resolves the error by preventing this AT extension from loading.  My
Emacs load time is much faster.

Why was the change integrated and should it be backed out?

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

Title:
  Emacs logs AT-SPI warnings to console on startup

Status in at-spi2-atk package in Ubuntu:
  New

Bug description:
  When starting up certain (GTK?) applications from console in a custom
  X session, such as emacs or ubuntu-bug, there is a lot of log output
  like:

  
  """
  ** (emacs:4437): WARNING **: 15:05:10.026: AT-SPI: Could not obtain desktop 
path or name
  """

  or

  """
  ** (apport-gtk:175957): WARNING **: 15:16:16.747: AT-SPI: Could not obtain 
desktop path or name
  """


  The issue seems to be related to at-spi2-atk, or at least that's where
  the code that prints the error is:


  In register_reply in bridge.c:
    if (reply)
  {
    gchar *app_name, *obj_path;

    if (strcmp (dbus_message_get_signature (reply), "(so)") != 0)
  {
    g_warning ("AT-SPI: Could not obtain desktop path or name\n");
  }

  
  Which seems to be triggered by an attempt to register the application to ATK:
  static gboolean
  register_application (SpiBridge * app)
  {
    DBusMessage *message;
    DBusMessageIter iter;
    DBusPendingCall *pending;

    g_free (app->desktop_name);
    g_free (app->desktop_path);

    /* These will be overridden when we get a reply, but in practice these
   defaults should always be correct */
    app->desktop_name = g_strdup (ATSPI_DBUS_NAME_REGISTRY);
    app->desktop_path = g_strdup (ATSPI_DBUS_PATH_ROOT);

    message = dbus_message_new_method_call (SPI_DBUS_NAME_REGISTRY,
    ATSPI_DBUS_PATH_ROOT,
    ATSPI_DBUS_INTERFACE_SOCKET,
    "Embed");

    dbus_message_iter_init_append (message, );
    spi_object_append_reference (, app->root);

  if (!dbus_connection_send_with_reply (app->bus, message, , -1)
  || !pending)
  {
  if (pending)
    dbus_pending_call_unref (pending);

  dbus_message_unref (message);
  return FALSE;
  }

  dbus_pending_call_set_notify (pending, register_reply, app, NULL);


  
  It seems to be caused by nobody being available at the ATSPI_DBUS_PATH_ROOT 
to handle the message. I have not yet been able to figure out what *should* be 
handling the message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1845645/+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 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist

[Hans P . Möller]

this should be the diff to be tested:

diff --git a/softwareproperties/qt/SoftwarePropertiesQt.py 
b/softwareproperties/qt/SoftwarePropertiesQt.py
index 8172e25..b210323 100644
--- a/softwareproperties/qt/SoftwarePropertiesQt.py
+++ b/softwareproperties/qt/SoftwarePropertiesQt.py
@@ -709,8 +709,7 @@ class SoftwarePropertiesQt(SoftwareProperties):
 home = QDir.homePath()
 if "SUDO_USER" in os.environ:
 home = os.path.expanduser("~%s" % os.environ["SUDO_USER"])
-url = KUrl.fromPath(home)
-filename = KFileDialog.getOpenFileName(url, 'application/pgp-keys', 
self.userinterface, _("Import key"))
+filename = QFileDialog.getOpenFileName(self.userinterface, _("Import 
key"), home, 'application/pgp-keys')
 if filename:
   if not self.add_key(filename):
 title = _("Error importing selected file")

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

Title:
  software-properties-{qt,kde} attempts to use KUrl but it doesn't exist

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Release: Kubuntu 18.04
  Version: 0.96.24.32.1

  When clicking the "Import Key" button in the "Authentication" section
  of the panel it throws this error:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
 line 667, in add_key_clicked
  url = KUrl.fromPath(home)
  NameError: name 'KUrl' is not defined

  While this doesn't crash the program it causes nothing to happen when
  clicking the button. Running the program in a terminal reveals the
  error being printed to stderr.

  After debugging it appears KUrl doesn't exist anywhere and I'm not
  sure if's a python module that has changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[Marcin P]

Guys, maybe I can somehow help you with this issue?

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852071/+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 1852083] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement

[Marcin P]

After latest Ubuntu updates mouse seems to work properly without having
to execute

$ sudo hcitool lecup --handle 3585 --latency 0 --min 6 --max 8


Versions in my system:

$ uname -a
... 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

$ apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu7.1

I think this ticket can be closed now.

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy
  bluetooth mouse cursor movement

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't 
use Logitech bluetooth dongle, use built in laptop bluetooth)
  2. Move cursor.
  Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate.

  Workaround:
  execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 
--max 8`
  This command must be used every time the mouse is connected to the laptop 
(after turning on the laptop, after some time of mouse inactivity etc.).

  When using Logitech bluetooth dongle this problem never occurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 14:35:49 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:

  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: 
Cannot open /sys/bus/pci/devices/:05:02.0/resource: No such file or 
directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 004: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852083/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

Yes, the speakers behaves perfectly now. Thank you.

When auto-mute is enabled and I disconnect the headphones shouldn't the
global system volume be muted?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

I have some additional observations (on regular kernel: 5.0.0-35-generic
#38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 UTC 2019 x86_64 x86_64 x86_64
GNU/Linux):

I also have a HP docking station which has its own separated built-in
DAC. When laptop is connected to this docking station I can choose from
following sound devices:

- Digital Output (S/PDIF) - USB Audio
- Analog Output - USB Audio
- Speakers - Built-in Audio

When I don't connect headphones I can switch between these devices and
when coming back to built-in speakers the speakers usually work (however
sometimes they don't). But after connecting headphones the speakers will
never work again.

To clarify: all previous tests I did were done on laptop disconnected
from docking station.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

** Attachment added: "alsa-info.txt.still-failed-built-in-speakers"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305011/+files/alsa-info.txt.still-failed-built-in-speakers

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

** Attachment added: "alsa-info.txt.failed-built-in-speaker.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305009/+files/alsa-info.txt.failed-built-in-speaker.txt

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

I installed modified kernal:
5.0.0-34.36+conexant-codec-generic #codec SMP Tue Nov 12 22:40:14 CST 2019 
x86_64 x86_64 x86_64 GNU/Linux

After system startup there is no sound from built-in speakers.
After connecting headphones sound works correctly in headphones.
After disconnecting headphones again there is no sound from built-in speakers.

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

** Attachment added: "alsa-info.txt.success-internal-headphones"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5305010/+files/alsa-info.txt.success-internal-headphones

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

Thank you Hui Wang for your quick answer.

Could you help me with install and then uninstall procedure?
I understand that I have to install all these kernel packages with "sudo dpkg 
-i". But:
1. What is the order of installation of these packages?
2. After installation how can I switch from current kernel to this new kernel? 
Currently I use "5.0.0-35-generic #38~18.04.1-Ubuntu SMP Mon Nov 11 09:16:10 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux"
3. What if this new kernel won't boot my computer? Will be there any backup 
kernel installed?
4. After tests what should I do get back to "stock" kernel?

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

Hi Hui Wang.
Thanks for your reply.
I'm attaching requested files.

** Attachment added: "alsa-info.txt_speaker_ok"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5304483/+files/alsa-info.txt_speaker_ok

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852067] Re: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers wor

[Marcin P]

** Attachment added: "alsa-info.txt_speaker_fail"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+attachment/5304484/+files/alsa-info.txt_speaker_fail

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1852067/+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 1852083] [NEW] [HP ZBook Studio G5, Ubuntu 18.04.3 LTS, bluetooth mouse] Choppy/laggy bluetooth mouse cursor movement

[Marcin P]

Public bug reported:

1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't use 
Logitech bluetooth dongle, use built in laptop bluetooth)
2. Move cursor.
Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate.

Workaround:
execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 
--max 8`
This command must be used every time the mouse is connected to the laptop 
(after turning on the laptop, after some time of mouse inactivity etc.).

When using Logitech bluetooth dongle this problem never occurs.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 14:35:49 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:

InstallationDate: Installed on 2019-04-02 (223 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot 
open /sys/bus/pci/devices/:05:02.0/resource: No such file or directory
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
 Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
 Bus 001 Device 004: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ZBook Studio G5
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.08.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.3A.00
dmi.chassis.asset.tag: 5CD91018X5
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2YN61AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

** Description changed:

  1. Pair Logitech MX Master 3 bluetooth mouse with Ubuntu 18.04.3 LTS (don't 
use Logitech bluetooth dongle, use built in laptop bluetooth)
  2. Move cursor.
- Cursore movement is choppy, laggy, like it's having 20 FPS refresh rate. 
+ Cursor movement is choppy, laggy, like it's having 20 FPS refresh rate.
  
  Workaround:
  execute in terminal: `sudo hcitool lecup --handle 3585 --latency 0 --min 6 
--max 8`
  This command must be used every time the mouse is connected to the laptop 
(after turning on the laptop, after some time of mouse inactivity etc.).
  
  When using Logitech bluetooth dongle this problem never occurs.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 14:35:49 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  
+ 
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: 
Cannot open /sys/bus/pci/devices/:05:02.0/resource: No such file or 
directory
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
-  Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
-  Bus 001 

[Touch-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[Marcin P]

Command `sudo showkey` prints following outputs:

F3
keycode  61 press
keycode  61 release

fn+F3 (identical to fn+F4, fn+F8)
keycode 190 press
keycode 190 release

F4
keycode  62 press
keycode  62 release

fn+F4 (identical to fn+F3, fn+F8)
keycode 190 press
keycode 190 release

F5
keycode  63 press
keycode  63 release

fn+F5
keycode 113 press
keycode 113 release

F6
keycode  64 press
keycode  64 release

fn+F6
keycode 114 press
keycode 114 release

F7
keycode  65 press
keycode  65 release

fn+F7
keycode 115 press
keycode 115 release

F8
keycode  66 press
keycode  66 release

fn+F8 (identical to fn+F3, fn+F4)
keycode 190 press
keycode 190 release

F12
keycode  88 press
keycode  88 release

fn+F12 (double codes?)
keycode  29 press
keycode  56 press
keycode  29 release
keycode  56 release

F13/fn+F13 (the same with and without fn; double codes?)
keycode  29 press
keycode  56 press
keycode  29 release
keycode  56 release

F14/fn+F14 (the same with and without fn; double codes?)
keycode  56 press
keycode 125 press
keycode  56 release
keycode 125 release

F15/fn+F15 (the same with and without fn; double codes?)
keycode  29 press
keycode  56 press
keycode  29 release
keycode  56 release

** Description changed:

  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.
  
  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Device [103c:8428]
+  Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
-  Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
-  Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc.
+  Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
+  Bus 001 Device 004: ID 8087:0aaa Intel Corp.
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function 

[Touch-packages] [Bug 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[Marcin P]

Sound function keys works almost OK:
1) fn+F5 mute/unmute outgoing sound, OK, however LED inside the key is always 
off
2) fn+F6 decrease volume, OK
3) fn+F7 increase volume, OK
4) fn+F8 mute/unmute, OK, however LED inside the key is always off

But there are other function keys doesn't work as they should. For example:
5) fn+F12 Calendar - doesn't open the calendar, but does some weird changes to 
keyboard layout?
6) fn+F13 Share screen - doesn't do anything, LED inside the key is always off
7) fn+F14 "Call" mostly isn't doing anything; in Firefox it shows/hides menu 
bar; LED inside the key is always off
6) fn+F15 "End Call" seems not doing anything, LED inside the key is always off

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook Studio
  dmi.product.name: HP ZBook Studio G5
  dmi.product.sku: 2YN61AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852071/+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 1852071] [NEW] [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys

[Marcin P]

Public bug reported:

1. Press fn+F3.
Ubuntu shows "Internal microphone" turned off OSD pop-up.
Should turn the brightness down.
2. Press fn+F3 again.
Ubuntu shows "Internal microphone" turned on OSD pop-up.
Should turn the brightness down.

1. Press fn+F4.
Ubuntu shows "Internal microphone" turned off OSD pop-up.
Should turn the brightness up.
2. Press fn+F4 again.
Ubuntu shows "Internal microphone" turned on OSD pop-up.
Should turn the brightness up.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 13:23:56 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:8428]
InstallationDate: Installed on 2019-04-02 (223 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
 Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP ZBook Studio G5
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic 
root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.08.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.3A.00
dmi.chassis.asset.tag: 5CD91018X5
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2YN61AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys
  works as microphone mute function keys

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Press fn+F3.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness down.
  2. Press fn+F3 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness down.

  1. Press fn+F4.
  Ubuntu shows "Internal microphone" turned off OSD pop-up.
  Should turn the brightness up.
  2. Press fn+F4 again.
  Ubuntu shows "Internal microphone" turned on OSD pop-up.
  Should turn the brightness up.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 13:23:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:8428]
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
   Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 004: ID 

[Touch-packages] [Bug 1852067] [NEW] [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound from built-in speakers after disconnecting headphones. Prior to connecting headphones speakers w

[Marcin P]

Public bug reported:

Steps to replicate the bug.

1. Start laptop with Ubuntu 18.04.3 LTS.
Sound from built-in speakers works fine.
Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
2. Connect headphones (wired, mini-jack connector).
Sound from headphones works fine. No sound from built-in speakers (which is OK, 
obviously).
Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
3. Disconnect headphones from computer.
No sound from built-in speakers.
Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
help. Only full laptop restart helps.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  marcin 2115 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 11 12:26:58 2019
InstallationDate: Installed on 2019-04-02 (223 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
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:  gdm1672 F pulseaudio
  marcin 2115 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2019
dmi.bios.vendor: HP
dmi.bios.version: Q71 Ver. 01.08.00
dmi.board.name: 8427
dmi.board.vendor: HP
dmi.board.version: KBC Version 16.3A.00
dmi.chassis.asset.tag: 5CD91018X5
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN HP ZBook Studio
dmi.product.name: HP ZBook Studio G5
dmi.product.sku: 2YN61AV
dmi.sys.vendor: HP

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


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

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

Title:
  [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound
  from built-in speakers after disconnecting headphones. Prior to
  connecting headphones speakers works ok.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Steps to replicate the bug.

  1. Start laptop with Ubuntu 18.04.3 LTS.
  Sound from built-in speakers works fine.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio
  2. Connect headphones (wired, mini-jack connector).
  Sound from headphones works fine. No sound from built-in speakers (which is 
OK, obviously).
  Settings -> Sound -> Output shows one device: Headphones - Built-in Audio
  3. Disconnect headphones from computer.
  No sound from built-in speakers.
  Settings -> Sound -> Output shows one device: Speakers - Built-in Audio (ON, 
high volume)

  Changing volume, turning ON -> OFF -> ON, user logout->login doesn't
  help. Only full laptop restart helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marcin 2115 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 11 12:26:58 2019
  InstallationDate: Installed on 2019-04-02 (223 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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:  gdm1672 F pulseaudio
marcin 2115 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ZBook Studio G5, Conexant Generic, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q71 Ver. 01.08.00
  dmi.board.name: 8427
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 16.3A.00
  dmi.chassis.asset.tag: 5CD91018X5
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 

[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

[Sooraj P Suresh]

Same issue using Samsung Notebook Model NP930MBE

The sound in headphone is not clear and no sound at all in internal
speaker

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  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_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+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 1846284] Re: UDEV Symlink Not Created In 19.10

[Greg P]

However, it looks like debian is asking systemd to do this.

Hmmm. I'm talking to a Plex guy in another forum. I'll follow up here,
or he will.

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

Title:
  UDEV Symlink Not Created In 19.10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Upon upgrade from 19.04 to 19.10, the symlink for udev is broken.

  /sbin/udevadm should link to /bin/udev

  It doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Tue Oct  1 19:53:28 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-09-29 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846284/+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 1846284] Re: UDEV Symlink Not Created In 19.10

[Greg P]

Plex for one

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

Title:
  UDEV Symlink Not Created In 19.10

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Upon upgrade from 19.04 to 19.10, the symlink for udev is broken.

  /sbin/udevadm should link to /bin/udev

  It doesn't.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Tue Oct  1 19:53:28 2019
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-09-29 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846284/+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 1843869] Re: System crashes randomly each time with different application

[Sreeram P A]

** Package changed: linux-signed-hwe (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/1843869

Title:
  System crashes randomly each time with different application

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.6 LTS
  Release:  16.04

  Package version: 7.7+13ubuntu3.1

  Fresh system install with Ubuntu 16.04 crashes the system after some
  time. We are running high CPU intensive jobs, but CPU usage never
  crosses 80%.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-62-generic 4.15.0-62.69~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  NonfreeKernelModules: snapapi26
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Sep 13 11:46:12 2019
  InstallationDate: Installed on 2019-09-11 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1843869/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Gregory P Smith]

(Sadly the bug tracker won't let me change the status from "Won't Fix"
to "Confirmed")

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Incomplete
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Won't Fix
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1727202] Re: [17.10 regression] AppArmor ntp denial: Failed name lookup - disconnected path

[Gregory P Smith]

I just diagnosed that openntpd on my 18.04.2 server to be broken
(failing to run, the process died after the apparmor denials, no time
adjustments ever happening) until I manually applied the changes
mentioned in #34.

Neither flags=(attach_disconnected) or "/run/systemd/journal/dev-log w,"
had been present in my apparmor.d/usr.sbin.ntpd config file.  package
version 1:6.2p3-1 installed.

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

Title:
  [17.10 regression] AppArmor ntp denial: Failed name lookup -
  disconnected path

Status in ntp package in Ubuntu:
  Fix Released
Status in openntpd package in Ubuntu:
  Incomplete
Status in ntp source package in Artful:
  Fix Released
Status in openntpd source package in Artful:
  Won't Fix
Status in ntp source package in Bionic:
  Fix Released
Status in openntpd source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

   * NTP has new isolation features which makes it trigger apparmor issues.
   * Those apparmor issues not only clutter the log and make other things
     less readable, they also prevent ntp from reporting its actual
     messages.
   * Fix is opening the apparmor profile to follow ntp through the
     disconnect by the isolation feature.

  [Test Case]

   * This is hard to trigger, but then also not. Which means it is not
     entirely sorted out when it triggers and when not, but the following
     does trigger it in tests of Pitti and also mine (while at the same time
     sometimes it does not - mabye I had other guests or kvm instead of lxd)

   * First install ntp in Artful (or above unless fixed)
     * Install ntp and check demsg for denies
     * Once an issue triggers instead of the error in syslog you'll see the
   apparmor Deny like:
     apparmor="DENIED" operation="sendmsg" info="Failed name lookup -
     disconnected path" error=-13 profile="/usr/sbin/ntpd"
     name="run/systemd/journal/dev-log" pid=5600 comm="ntpd"
     requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  [Regression Potential]

   * We are slightly opening up the apparmor profile which is far lower risk
     than adding more constraints. So safe from that POV.

   * OTOH one could think this might be a security issue, but in fact this
     isn't a new suggestion if you take a look at [1] with an ack by Seth of
     the Security Team.

  [Other Info]

   * n/a

  [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html

  

  Merely installing and starting ntp.service in Ubuntu 17.10 now causes
  this AppArmor violation:

  audit: type=1400 audit(1508915894.215:25): apparmor="DENIED"
  operation="sendmsg" info="Failed name lookup - disconnected path"
  error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log"
  pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0

  (many times). This hasn't happened in earlier Ubuntu releases yet.

  This was spotted by Cockpit's integration tests, as our "ubuntu-
  stable" image now moved to 17.10 after its release.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Wed Oct 25 03:19:34 2017
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1828283] [NEW] Kernel Failure (that's what it says)

[Zhivomira P. Ilieva]

Public bug reported:

After using my computer (op sys Ubuntu 16.04.6 LTS) for a while the wi-
fi refuses to work. Apps and programs run fine, just no wi-fi. After I
open the System Settings menu and try to click on Network the whole
window grays out and stops responding and the whole system crashes. If I
try to reboot the computer it does reboot but after a considerable
amount of time. Meanwhile, I get a black screen and the message
"[75873.475364] BUG: unable to handle kernel paging request at
c9d6e808"

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed May  8 17:59:04 2019
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-142-generic, x86_64: 
installed
 oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-145-generic, x86_64: 
installed
 oem-audio-hda-daily, 0.201710250904~ubuntu16.04.1, 4.4.0-146-generic, x86_64: 
installed
 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-145-generic, x86_64: 
installed
 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-146-generic, x86_64: 
installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Within the last week or two
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Device [1028:083f]
   Subsystem: Dell Jet PRO [Radeon R5 M230] [1028:083f]
InstallationDate: Installed on 2018-12-13 (146 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 3576
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic 
root=UUID=6d8b6200-17f0-42e3-949a-5bfcbc310569 ro acpi_rev_override locale=C 
alx.enable_wol=1 mem_sleep_default=deep splash quiet
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.1
dmi.board.name: 0J11DH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.1:bd05/22/2018:svnDellInc.:pnInspiron3576:pvr:rvnDellInc.:rn0J11DH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 3576
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed May  8 17:48:12 2019
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1680 
 vendor BOE
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug compiz-0.9 failure freeze kernel ubuntu xenial

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

Title:
  Kernel Failure (that's what it says)

Status in xorg package in Ubuntu:
  New

Bug description:
  After using my computer (op sys Ubuntu 16.04.6 LTS) for a while the
  wi-fi refuses to work. Apps and programs run fine, just 

[Touch-packages] [Bug 1825828] [NEW] Display is in upside-down state by default

[DIPIN P JOSEPH]

Public bug reported:

The default state of display is upside-down. I'm observing this issue in
latest kernels(>4.19).

Command "xrandr -o normal" make things normal, but rotating display
welcomes unexpected behavior.

Please Check, Any help is highly appreciated. Thanks

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
Uname: Linux 5.0.0-14-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 22 17:13:37 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series 
Integrated Graphics Controller [8086:2212]
InstallationDate: Installed on 2019-04-22 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:3841 Alcor Micro Corp. 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: iBall Aer3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-14-generic 
root=UUID=6c1f9ed6-db22-4758-9fc4-7ad00307a239 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/26/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G
dmi.board.asset.tag: Default string
dmi.board.name: Aer3
dmi.board.vendor: iBall
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 9
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Aer3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: iBall
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
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 disco ubuntu

** Attachment added: "Screenshot from 2019-04-22 15-34-31.png"
   
https://bugs.launchpad.net/bugs/1825828/+attachment/5257894/+files/Screenshot%20from%202019-04-22%2015-34-31.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/1825828

Title:
  Display is in upside-down state by default

Status in xorg package in Ubuntu:
  New

Bug description:
  The default state of display is upside-down. I'm observing this issue
  in latest kernels(>4.19).

  Command "xrandr -o normal" make things normal, but rotating display
  welcomes unexpected behavior.

  Please Check, Any help is highly appreciated. Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 17:13:37 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Integrated 
Graphics Controller [8086:5a84] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series 
Integrated Graphics Controller [8086:2212]
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:3841 Alcor Micro Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: 

[Touch-packages] [Bug 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover

[Hans P . Möller]

fix is in https://code.launchpad.net/~hmollercl/+git/software-properties
I don't know how to propose merge from that, but tsimonq2 will help merging it.

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

Title:
  lxqt-sudo added to Exec line of software-properties-qt.desktop breaks
  use in KDE Plasma Discover

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Disco:
  Confirmed

Bug description:
  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8

  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).

  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt

  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.

  Context to this is:

  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without
  pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs.
  This was on the condition that despite being renamed to -qt, it
  remained completely as a tool for joint usage between the two
  flavours.

  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.

  It seems that Lubuntu wishes to now have it useable directly from a
  'start'/'search' menu, hence making it visible and adding the lxqt-
  sudo in the Exec line to facilitate launch with privilege escalation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+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 1823306] Re: lxqt-sudo added to Exec line of software-properties-qt.desktop breaks use in KDE Plasma Discover

[Hans P Möller]

** Changed in: software-properties (Ubuntu Disco)
 Assignee: (unassigned) => Hans P Möller (hmollercl)

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

Title:
  lxqt-sudo added to Exec line of software-properties-qt.desktop breaks
  use in KDE Plasma Discover

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Disco:
  Confirmed

Bug description:
  In the upload: https://launchpad.net/ubuntu/+source/software-
  properties/0.97.8

  there is a change in the software-properties-qt.desktop files which is
  (a) not documented in the changelog, and (b) not communicated to other
  flavour users of this application (Kubuntu in this case).

  -Exec=software-properties-qt
  +Exec=lxqt-sudo software-properties-qt

  This results in Plasma Discover not being able to launch software-
  properties-qt, as it uses privilege elevation via kdesu of whatever is
  in the Exec line, and lxqt-sudo added there makes this fail.

  Context to this is:

  For Cosmic release Lubuntu developers requested agreement from Kubuntu
  to the porting of the software-properties-kde package to pure Qt, so
  that it could be used in both Kubuntu and Lubuntu (lxqt) without
  pulling a lot of KDE dependencies into Lubuntu's lqxt images/installs.
  This was on the condition that despite being renamed to -qt, it
  remained completely as a tool for joint usage between the two
  flavours.

  The original sofware-properties-kde was meant to be launched by
  applications and was set not to show in DE menus by default.

  It seems that Lubuntu wishes to now have it useable directly from a
  'start'/'search' menu, hence making it visible and adding the lxqt-
  sudo in the Exec line to facilitate launch with privilege escalation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1823306/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Peter P.]

I have the same problem on two machines running Ubuntu 18.04 with a Sony
WH-1000XM2.

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1811580] Re: systemd fails to start sshd at reboot

[Matt P]

Okay.  I guess I would have expected that if there was a dependency on a
specific kernel version, that I wouldn't be able to install a package
that wasn't compatible and breaks the system by installing a security
update.  It would be preferable to be informed there is a security
update but that I can't install it because I am running an out of date
kernel...then I know I am insecure and that the kernel is the issue.
But I guess that is a topic for the package management guys.  The error
message from systemd-tmpfiles about too many symlinks isn't particularly
helpful either since in this case the problem (apparently) has nothing
to do with symlinks but rather filesystem apis in the old kernel (I
guess?).

Yes of course I can contact the hosting provider and ask them to provide
an updated kernel and the likely result may be that I just have to use
an alternate provider if I want this to work.  Perhaps I should anyway
since the hosting provider having such old kernels isn't a good sign.

I also saw this comment:
https://github.com/systemd/systemd/commit/6a89d671dfdd92c0b1b703d7fcb5b0551cafb570

For now I have worked around this issue by just updating the paths to
point to /run instead of /var/run so systemd-tmpfiles doesn't barf on
the symlinks.

sed -i -e 's;/var/run;/run;g' /usr/lib/tmpfiles.d/*.conf

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got caught by it in the middle of setting up a new server
  yesterday, and it took a whole day to find the source.

  The appropriate fix would be to ensure that systemd can successfully
  'start ssh.service' even when 'UsePrivilegeSeparation yes' is set.
  systemd needs to test that /var/run/sshd/ exists before starting sshd,
  just as the init.d script for sshd does. openssl could also be patched
  so that UsePrivilegeSeparation is no longer enabled by default,
  however that is not going to solve the problem for millions of pre-
  existing config files. Only an update to openssl to force-override
  that flag to 'no' would solve the problem. Thus systemd still needs to
  be responsible for ensuring that it inits sshd properly by ensuring
  that /var/run/sshd/ exists before it sends the 'start' command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+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 1811580] Re: systemd fails to start sshd at reboot

[Matt P]

Same situation.  Ubuntu 16.04 openvz vps image of unknown origin.

Minimized image, ran security updates and rebooted.  openssh server
failed to start due to systemd-tmpfiles failing with

Failed to validate path /var/run/sshd: Too many levels of symbolic
links

Which then causes ssh server to fail to start with error:

Missing privilege separation directory: /var/run/sshd


#
# pre breaking update
#

# uname -a
Linux NJ01 2.6.32-openvz-042stab120.18-amd64 #1 SMP Fri Jan 13 10:33:34 MSK 
2017 x86_64 x86_64 x86_64 GNU/Linux

# cat /usr/lib/tmpfiles.d/sshd.conf
d /var/run/sshd 0755 root root

# systemd-tmpfiles --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
# # success

# ls -ld /
drwxr-xr-x 23 root root 4096 Feb 26 09:35 /
# ls -ld /var
drwxr-xr-x 12 root root 4096 Nov 26  2016 /var
# ls -ld /var/run
lrwxrwxrwx 1 root root 4 Nov 26  2016 /var/run -> /run
# ls -ld /var/run/sshd
drwxr-xr-x 2 root root 40 Feb 26 09:35 /var/run/sshd

# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu12
  Candidate: 229-4ubuntu12
  Version table:
 *** 229-4ubuntu12 100
100 /var/lib/dpkg/status

#---BREAKING UPDATE START

apt-get update

# "minimize" the system
export DEBIAN_FRONTEND=noninteractive
apt-get --assume-yes install aptitude ubuntu-minimal
aptitude --assume-yes markauto 
'~i!?name(ubuntu-minimal~|linux-generic~|openssh-server~|systemd)'
aptitude --assume-yes purge '~c'

# apply security updates
apt-get --assume-yes install unattended-upgrades
unattended-upgrade

# reboot
shutdown -r now

#---BREAKING UPDATE END

# post update (pre-reboot).
# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu21.16
  Candidate: 229-4ubuntu21.16
  Version table:
 *** 229-4ubuntu21.16 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
# ls -ld /
drwxr-xr-x 23 root root 4096 Feb 26 09:03 /
# ls -ld /var
drwxr-xr-x 12 root root 4096 Nov 26  2016 /var
# ls -ld /var/run
lrwxrwxrwx 1 root root 4 Nov 26  2016 /var/run -> /run
# ls -ld /var/run/sshd
drwxr-xr-x 2 root root 40 Feb 26 09:03 /var/run/sshd
# systemd-tmpfiles --version
systemd 229
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
# systemd-tmpfiles --create /usr/lib/tmpfiles.d/sshd.conf
Failed to validate path /var/run/sshd: Too many levels of symbolic links


Anyway, root cause seems to be this systemd-tmpfiles error.  Tmpfile gets 
purged at reboot and doesn't get recreated.  

Seems pretty major that applying security updates would lock you out of
your server.  If I didn't happen to have a serial console with this
particular VPS provider (some others I use don't provide one)...I would
have no idea what was going on.

I get this might be due to weird openvz image or older kernel...but
these ubuntu openvz images are very common.

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

Title:
  systemd fails to start sshd at reboot

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  So far reported issues turned out to be:
  - obsolete/buggy/vulnerable 3rd party provided kernels
  - bad permissions on /

  Please ensure / is owned by root:root.
  Please ensure you are running up to date kernels.

  
  ===

  Ubuntu 16.04.5, systemd 229-4ubuntu21.15

  The latest systemd update has somehow changed the method it uses to
  start 'ssh.service' i.e. 'sshd'. systemd fails to start sshd if
  /etc/ssh/sshd_config contains "UsePrivilegeSeparation yes" and
  /var/run/sshd/ does not already exist. Being as this is the default,
  virtually EVERY Ubuntu 16.04 server in the world has
  UsePrivilegeSeparation set to yes. Furthermore, at the time when the
  user performs 'apt upgrade' and receives the newest version of
  systemd, /var/run/sshd/ already exists, so sshd successfully reloads
  for as long as the server doesn't get rebooted. BUT, as soon as the
  server is rebooted for any reason, /var/run/sshd/ gets cleaned away,
  and sshd fails to start, causing the remote user to be completely
  locked out of his system. This is a MAJOR issue for millions of VPS
  servers worldwide, as they are all about to get locked out of their
  servers and potentially lose data. The next reboot is a ticking time
  bomb waiting to spring. The bomb can be defused by implicitly setting
  'UsePrivilegeSeparation no' in /etc/ssh/sshd_config, however
  unsuspecting administrators are bound to be caught out by the
  millions. I got 

[Touch-packages] [Bug 1801439] Re: Unable to add software sources via the software-properties-qt

[Hans P Möller]

I uploaded solution in 
https://bazaar.launchpad.net/~hmollercl/software-properties/software-properties/revision/1071
waiting for merge

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

Title:
  Unable to add software sources via the software-properties-qt

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Test
  1. Start Software-properties. E.g. sudo software-properties-qt
  2. Navigate to Other Software (Tab), Add -> Add, to add a PPA
  3. Insert the PPA string. E.g. "deb 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the 
example repo given in the dialog, which is not a PPA)
  4. Click Okay.

  The software sources list does not contain the new field. Executing in
  terminal results in the following error message.

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 627, in on_add_clicked
  self.add_source_from_line(line)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_line
  enable_source_code=enable_source_code)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
769, in add_source_from_shortcut
  worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
709, in check_and_add_key_for_whitelisted_shortcut
  self.options.keyserver)})
  AttributeError: type object 'OptionParsed' has no attribute 'keyserver'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-qt 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Nov  3 09:59:52 2018
  InstallationDate: Installed on 2018-10-19 (14 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+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 1815524] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

[Geoffrey P.]

Public bug reported:

Headphones work just fine. Internal speakers do not work. There was a
brief moment where the drum sound played on log-in one time but then the
speakers have never output anything again.

NOTE: A few releases ago: 14.04 LTS?!? (Before 16.04, in any case) the
sound worked perfectly. It hasn't worked since that time. I recently did
a fresh install of Ubuntu 18.04 to se if it would clean up the problem.
It only corrected the issue very briefly.

1) Ubuntu 18.04.2 LTS
2) alsa-base 1.0.25+dfsg-0ubuntu5
3) Sound output through internal speakers
4) No sound output through external speakers. The only sound output possible is 
via headphones. Headphones confirmed to work normally with sound output.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  geoffrey   1971 F pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Mon Feb 11 17:11:25 2019
InstallationDate: Installed on 2019-02-11 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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:  geoffrey   1971 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-0D102G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-0D102G
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug bionic

** Description changed:

  Headphones work just fine. Internal speakers do not work. There was a
  brief moment where the drum sound played on log-in one time but then the
  speakers have never output anything again.
+ 
+ NOTE: A few releases ago: 14.04 LTS?!? (Before 16.04, in any case) the
+ sound worked perfectly. It hasn't worked since that time. I recently did
+ a fresh install of Ubuntu 18.04 to se if it would clean up the problem.
+ It only corrected the issue very briefly.
  
  1) Ubuntu 18.04.2 LTS
  2) alsa-base 1.0.25+dfsg-0ubuntu5
  3) Sound output through internal speakers
  4) No sound output through external speakers. The only sound output possible 
is via headphones. Headphones confirmed to work normally with sound output.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  geoffrey   1971 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  geoffrey   1971 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Feb 11 17:11:25 2019
  InstallationDate: Installed on 2019-02-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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:  geoffrey   1971 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  geoffrey   1971 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: Intel Corp.
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  

[Touch-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

[Scott P]

example of broken video properties


** Attachment added: "example of broken video properties"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5235704/+files/Selection_182.png

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

[Scott P]

example of good video properties

** Attachment added: "example of good video properties"
   
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5235705/+files/Selection_183.png

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

[Scott P]

After testing from a well modified system, the issue appears after I
install the amdgpu driver from AMD.

THAT SAID, this issue is noticeable on videos that I have viewed on this
system since initial install in January.  I constantly view many videos
in Videos (every day) - so I suspect that something changed, that I
cannot undo.


Which specific package should I be verifying?

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

[Scott P]

I'm experiencing this issue as well.  I have an RX550 video card, using
Ubuntu's drivers.

Has anyone reported this to mesa, and if so where?  If someone can share
the right location/component for ME to log a bug, I will do so.

It seems that AMD GPUs are quite useless today, a million things are
broken and I'm strongly considering throwing out this $140 brand new
video card to get a NVidia card that hopefully works 50% better.

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+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 1801439] Re: Unable to add software sources via the software-properties-qt

[Hans P Möller]

** Branch linked: lp:software-properties

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

Title:
  Unable to add software sources via the software-properties-qt

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Test
  1. Start Software-properties. E.g. sudo software-properties-qt
  2. Navigate to Other Software (Tab), Add -> Add, to add a PPA
  3. Insert the PPA string. E.g. "deb 
http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the 
example repo given in the dialog, which is not a PPA)
  4. Click Okay.

  The software sources list does not contain the new field. Executing in
  terminal results in the following error message.

  Traceback (most recent call last):
    File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 627, in on_add_clicked
  self.add_source_from_line(line)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
752, in add_source_from_line
  enable_source_code=enable_source_code)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
769, in add_source_from_shortcut
  worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
709, in check_and_add_key_for_whitelisted_shortcut
  self.options.keyserver)})
  AttributeError: type object 'OptionParsed' has no attribute 'keyserver'

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-qt 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: LXQt
  Date: Sat Nov  3 09:59:52 2018
  InstallationDate: Installed on 2018-10-19 (14 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+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 1561278] Re: internal sound card not detected HP X2

[Michael P]

For what it's worth: An easy solution for audio is a bluetooth headset.
Works great under 18.04. I'd also like to get the main speakers working,
but I suspect the passengers next to me on the plane are happier with
the headset-only arrangement.

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

Title:
  internal sound card not detected HP X2

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  HP Pavilion X2 - No sound card detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Mar 23 18:18:32 2016
  InstallationDate: Installed on 2016-03-18 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  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/11/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 813E
  dmi.board.vendor: HP
  dmi.board.version: 34.10
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.04:bd09/11/2015:svnHP:pnHPPavilionx2Detachable:pvrType1ProductConfigId:rvnHP:rn813E:rvr34.10:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion x2 Detachable
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

[Nikhilesh Reddy P]

Public bug reported:

i can't install deb files like google remote desktop,virtual box etc

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: rsyslog 8.32.0-1ubuntu5
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Fri Oct 26 12:47:54 2018
DuplicateSignature:
 package:rsyslog:8.32.0-1ubuntu5
 Setting up gconf2-common (3.2.6-4.1ubuntu2) ...
 Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", line 
10: Having multiple values in  isn't supported and may not work as 
expected
 dpkg: error processing package gconf2-common (--configure):
  installed gconf2-common package post-installation script subprocess returned 
error exit status 10
ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2018-08-01 (85 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: rsyslog
Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 
10
UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed
  rsyslog package post-installation script subprocess returned error
  exit status 10

Status in rsyslog package in Ubuntu:
  New

Bug description:
  i can't install deb files like google remote desktop,virtual box etc

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: rsyslog 8.32.0-1ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Fri Oct 26 12:47:54 2018
  DuplicateSignature:
   package:rsyslog:8.32.0-1ubuntu5
   Setting up gconf2-common (3.2.6-4.1ubuntu2) ...
   Fontconfig warning: "/etc/fonts/conf.avail/53-monospace-lcd-filter.conf", 
line 10: Having multiple values in  isn't supported and may not work as 
expected
   dpkg: error processing package gconf2-common (--configure):
installed gconf2-common package post-installation script subprocess 
returned error exit status 10
  ErrorMessage: installed rsyslog package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2018-08-01 (85 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.0
  SourcePackage: rsyslog
  Title: package rsyslog 8.32.0-1ubuntu5 failed to install/upgrade: installed 
rsyslog package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1800107/+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 1218442] Re: IPv6 addresses are lost when an interface is shortly down

[Midhun P Madhav]

I am working with 2.6.32 kernel. keep_addr_on_down variable is not
available with this version. How to overcome this issue?

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

Title:
  IPv6 addresses are lost when an interface is shortly down

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  /etc/network/interfaces has been configured with IPv4 and IPv6
  addresses on an interface. There are two networks each:

  $ ip -4 addr show dev eth0
  2: eth0:  mtu 1500 qdisc mq state UP 
qlen 1000
  inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0
  inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0

  $ ip -6 addr show dev eth0
  2: eth0:  mtu 1500 qlen 1000
  inet6 :::201::33/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 :::101::33/64 scope global 
 valid_lft forever preferred_lft forever
  inet6 fe80:::aaff:febb:ccdd/64 scope link 
 valid_lft forever preferred_lft forever

  (Global addresses and MAC address anonymized)

  Both are configured within "manual" entries in
  /etc/network/interfaces.

  
  When I turn down eth0 and bring it up again, the result is:

  $ ip -4 addr show dev eth0
  2: eth0:  mtu 1500 qdisc mq state UP 
qlen 1000
  inet 10.1.1.51/24 brd 10.1.1.255 scope global eth0
  inet 10.2.1.51/24 brd 10.2.1.255 scope global eth0

  $ ip -6 addr show dev eth0
  2: eth0:  mtu 1500 qlen 1000
  inet6 fe80:::aaff:febb:ccdd/64 scope link 
 valid_lft forever preferred_lft forever

  That is, the global IPv6 addresses are lost.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ifupdown 0.7.5ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Thu Aug 29 16:28:46 2013
  InstallationDate: Installed on 2013-08-14 (14 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[matthew p]

This is still an issue for my hardware. The workaround in the comments
does seem to work, but honestly it took finally googling the right
phrase after months of trying to find a solution on and off.

If this bug could actually be fixed by reopening it, I would like to see
it reopened because it might help other people out that aren't as lucky
as the people that find this bug ticket.

aplay -l:
 List of PLAYBACK Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #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/1672822

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

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

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

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

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

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

  More system information:

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

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

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

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

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

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

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

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

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

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

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

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

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

  flat-volumes = no

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

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

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

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

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

  
  Note that the speakers work perfectly fine on windows 10. 

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

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

-- 
Mailing list: 

[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually

[Olli P.]

I am running Ubuntu 18.04 and have Sony WH-1000XM2 bluetooth headphones.
Bluetooth connection is established automatically but in order to get
any sound out of the headphones I need to:

1. Manually disconnect and reconnect the headphones from bluetooth
settings

or

2. Press play/pause button on my headphones (after this a2dp_sink is
available) and go to sound settings to select headphones as output
device.

After the bluetooth connection is automatically established I see the following 
error message in system log:
  pulseaudio[3124]: [pulseaudio] module-bluez5-device.c: Profile a2dp_sink has 
no transport

The command "pacmd list-cards" displays the a2dp_sink as unavailable (full 
device output attached):
   
  ...
  profiles:
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: 
unknown)   
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: no)  

  ...

After pressing play/pause button on the headphones or manually reconnecting, 
a2dp_sink is available:
  ...
  profiles:
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: 
unknown)
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: yes)
off: Off (priority 0, available: yes)
  ...


** Attachment added: "pacmd_list-cards_output"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+attachment/5178575/+files/pacmd_list-cards_output

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

Title:
  Bluetooth headphones only use A2DP when connected manually

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Issue with Sony MDR-1ABT Bluetooth headphones:
  Once paired, the headphones will be connected automatically whenever they are 
switched on. However when connected this way, only the HSP/HFP profile will 
work and trying to change to A2DP in sound settings does nothing.
  If the headphones are then manually disconnected and reconnected from 
Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in 
sound settings will successfully make them use A2DP.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neil   1443 F pulseaudio
   /dev/snd/pcmC0D0c:   neil   1443 F...m pulseaudio
   /dev/snd/controlC0:  neil   1443 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 19:12:59 2017
  InstallationDate: Installed on 2017-10-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: MDR-1ABT
  Symptom_Type: None of the above
  Title: [MDR-1ABT, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: Default string
  dmi.board.name: Z270N-WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z270N-WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1787554] [NEW] my laptop consume much power due to display driver

[Karthik hari R P]

Public bug reported:

my laptop consume much power due to display driver

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 17 14:45:35 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bbswitch, 0.8, 4.15.0-32-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1207]
   Subsystem: Micro-Star International Co., Ltd. [MSI] GP108M [GeForce MX150] 
[1462:1207]
InstallationDate: Installed on 2018-07-09 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 8087:0aa7 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Micro-Star International Co., Ltd. PL62 7RC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=505c78c3-eab6-498f-8626-b52f7c20ebab ro quiet splash nouveau.runpm=0 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16JDIMS.10D
dmi.board.asset.tag: Default string
dmi.board.name: MS-16JD
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10D:bd02/22/2018:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.family: PL
dmi.product.name: PL62 7RC
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  my laptop consume much power due to display driver

Status in xorg package in Ubuntu:
  New

Bug description:
  my laptop consume much power due to display driver

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 17 14:45:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.8, 4.15.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1207]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP108M [GeForce MX150] 
[1462:1207]
  InstallationDate: Installed on 2018-07-09 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. PL62 7RC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  

[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2

[Tais P. Hansen]

** Tags added: xenial

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

Title:
  Alt-f2 switches to virtual terminal 2

Status in console-cyrillic package in Ubuntu:
  Invalid
Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+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 1771962] Re: hanging at boot for about 30 seconds since upgrade to bionic

[Tais P. Hansen]

Note that this also applies if your swap is on ZFS. Ubuntu will attempt
to use it automatically and cause a 30 second delay as the swap
partition will not be available during early boot. Ie.

I: The initramfs will attempt to resume from /dev/zd0
I: (UUID=a0c4e220-8b9f-447b-b2e2-d2abeb2f6c39)
I: Set the RESUME variable to override this.

and

Aug  2 14:58:00 taisph-enodatio kernel: [3.822995] Btrfs loaded, 
crc32c=crc32c-intel
Aug  2 14:58:00 taisph-enodatio kernel: [   35.038644] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)


Setting RESUME=none is currently necessary to work around this.

Tested with initramfs-tools 0.130ubuntu3.1.

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

Title:
  hanging at boot for about 30 seconds since upgrade to bionic

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, even if the swap 
device is ephemeral (i.e. swap encrypted with a random key).  This adds an 
inappropriate 30-second boot delay to any system with randomly-crypted swap, 
which includes any system that was installed with encrypted home directories in 
earlier releases.

  [Test case]
  1. Install the ecryptfs-utils package.
  2. Enable encrypted swap by running 'sudo ecryptfs-setup-swap'.
  3. Run 'update-initramfs -u' to regenerate the initramfs.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language.  An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users.  A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  Since upgrade to Bionic ubuntu is hanging at boot for about 30s. A `dmesg` 
shows

  ```
  [3.407230] clocksource: Switched to clocksource tsc
  [   34.632583] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  ```

  This is 100% reproducable and is always 30s minimum. I do not know in
  which package to report this properly – please excuse me.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: i3
  Date: Fri May 18 09:40:59 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-03 (1444 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to bionic on 2018-05-13 (5 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized

   This incident has been reported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771962/+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 1782950] [NEW] package libkmod2 24-1ubuntu3 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/

[Gordon P. Hemsley]

Public bug reported:

Upgrade failed (or at least reported an error). Ubuntu 18.04.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libkmod2 24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Sat Jul 21 21:01:02 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libkmod2:24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
 Unpacking libkmod2:i386 (24-1ubuntu3) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-enXHF1/11-libkmod2_24-1ubuntu3_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
InstallationDate: Installed on 2014-01-08 (1655 days ago)
InstallationMedia: Custom 13.10 - Release amd64
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: kmod
Title: package libkmod2 24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
UpgradeStatus: Upgraded to bionic on 2018-05-20 (62 days ago)

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


** Tags: amd64 apport-package bionic package-conflict

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

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

Status in kmod package in Ubuntu:
  New

Bug description:
  Upgrade failed (or at least reported an error). Ubuntu 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libkmod2 24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Sat Jul 21 21:01:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libkmod2:24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz]
   Unpacking libkmod2:i386 (24-1ubuntu3) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-enXHF1/11-libkmod2_24-1ubuntu3_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', 
which is different from other instances of package libkmod2:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other 
instances of package libkmod2:i386
  InstallationDate: Installed on 2014-01-08 (1655 days ago)
  InstallationMedia: Custom 13.10 - Release amd64
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: kmod
  Title: package libkmod2 24-1ubuntu3 [modified: 
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is 
different from other instances of package libkmod2:i386
  UpgradeStatus: Upgraded to bionic on 2018-05-20 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1782950/+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 1774757] [NEW] package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from

[Robert John P. Canare]

Public bug reported:

everytime i turn on my pc it shows the error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libgraphite2-3 1.3.11-2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Sat Jun  2 09:52:02 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
DuplicateSignature:
 package:libgraphite2-3:1.3.11-2
 Unpacking libgraphite2-3:i386 (1.3.11-2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
InstallationDate: Installed on 2018-05-24 (8 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: graphite2
Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic package-conflict

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

Title:
  package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz',
  which is different from other instances of package libgraphite2-3:i386

Status in graphite2 package in Ubuntu:
  New

Bug description:
  everytime i turn on my pc it shows the error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgraphite2-3 1.3.11-2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Sat Jun  2 09:52:02 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  DuplicateSignature:
   package:libgraphite2-3:1.3.11-2
   Unpacking libgraphite2-3:i386 (1.3.11-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-WRx3Ga/12-libgraphite2-3_1.3.11-2_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is different from 
other instances of package libgraphite2-3:i386
  InstallationDate: Installed on 2018-05-24 (8 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: graphite2
  Title: package libgraphite2-3 1.3.11-2 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libgraphite2-3/changelog.Debian.gz', which is 
different from other instances of package libgraphite2-3:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1774757/+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 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

[Daniel P. Clark]

** Tags added: bionic

** Package changed: xkeyboard-config (Ubuntu) => ibus (Ubuntu)

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus package in Ubuntu:
  New

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1760308/+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 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

[Daniel P. Clark]

** Description changed:

  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.
  
  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have to
  hold ALT-TAB instead of quickly hitting both simultaneously.
  
  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.
  
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
+ 
+ The "Affects" package may not be accurate as I don't know what the cause
+ application is for this.

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in ibus package in Ubuntu:
  New

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1760308/+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 1760308] Re: Unicode input not working on Bionic with CTRL-SHIFT-U

[Daniel P. Clark]

** Package changed: ubuntu-docs (Ubuntu) => xkeyboard-config (Ubuntu)

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

Title:
  Unicode input not working on Bionic with CTRL-SHIFT-U

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I need to enter Unicode with Unicode escape codes and the Ubuntu
  prescribed way is to use CTRL-SHIFT-U and then enter some numbers to
  input.  This doesn't do anything in the Ubuntu Bionic beta.

  Potentially related the ALT-TAB window switching is delayed in
  recognizing the occurrence of the keys being pressed such that I have
  to hold ALT-TAB instead of quickly hitting both simultaneously.

  This is from a system that was upgraded from a previous Ubuntu version
  without any issues.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  The "Affects" package may not be accurate as I don't know what the
  cause application is for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1760308/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Burt P.]

I spoke too soon, the lock screen is still 640x480, but when unlocked it
returns to 1920x1080. I can live with this, but something is still wrong
with the driver.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Burt P.]

Regarding #43, #44, #51, here is what I did:
* Reset the grub config file
* Removed all nvidia* packages
* Reverted everything to the standard bionic as described here: 
https://askubuntu.com/a/229663
* Removed all the old package information using: dpkg --purge `dpkg 
--get-selections | grep deinstall | cut -f1`
* Installed nvidia-driver-390: apt-get install nvidia-driver-390
* Restarted

Everything seems to work.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Burt P.]

Regarding my comment #43:
The solution suggested in #46 doesn't work. While it does force 1920x1080, even 
after login, the nvidia driver is not working. 

lspci -v does show "Kernel driver in use: nvidia" for the card, but
nvidia-settings behaves as if the driver is not loaded and glxinfo shows
llvmpipe as the OpenGL renderer.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1753966] [NEW] apparmor interfers with saving of PDF from evince

[P]

Public bug reported:

While trying to save an open PDF from evince, I clicked on the "create
folder" button in the save dialog. Apparmor prevented directory creation
in the respective directory. Saving within my "home" directory works.

I consider this a bug. In my case, all user data resides in a separate
data partition. With the current apparmor profiles, saving to this
partition is hindered.

Syslog contains:

Mar  7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400
audit(1520414973.202:39): apparmor="DENIED" operation="mkdir"
profile="/usr/bin/evince" name="x" pid=5393 comm="evince"
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

More generally, this seems to apply to a whole set of apparmor profiles
that were updated or added recently...

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apparmor-profiles (not installed)
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Mar  7 10:32:37 2018
InstallationDate: Installed on 2017-12-01 (95 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

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

Title:
  apparmor interfers with saving of PDF from evince

Status in apparmor package in Ubuntu:
  New

Bug description:
  While trying to save an open PDF from evince, I clicked on the "create
  folder" button in the save dialog. Apparmor prevented directory
  creation in the respective directory. Saving within my "home"
  directory works.

  I consider this a bug. In my case, all user data resides in a separate
  data partition. With the current apparmor profiles, saving to this
  partition is hindered.

  Syslog contains:

  Mar  7 10:29:33 xxx kernel: [ 4569.159240] audit: type=1400
  audit(1520414973.202:39): apparmor="DENIED" operation="mkdir"
  profile="/usr/bin/evince" name="x" pid=5393 comm="evince"
  requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

  More generally, this seems to apply to a whole set of apparmor
  profiles that were updated or added recently...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor-profiles (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar  7 10:32:37 2018
  InstallationDate: Installed on 2017-12-01 (95 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=5c73304c-cd10-4645-99c9-2cf07aa48894 ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1753966/+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 1486445] Re: Lots of zeitgeist errors

[Scott P]

Same class of errors.  Been happening almost forever.  Computer has been
rebooted in past week.  Computer has had its Ubuntu version upgraded
since 2015.

non-standard Packages installed often in use:
Skype (current beta)
SciTE text editor
KeePass2 (from repo in previous Ubuntu version)


user@computer:~$ uname -a
Linux computer 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux


Dec  4 09:54:45 computer org.gnome.zeitgeist.SimpleIndexer[2111]: ** 
(zeitgeist-fts:2968): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1689620
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x167d030
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x16977f0
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1697690
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x1697530
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
WARNING **: recent-manager-provider.vala:106: (null) was not registered in 
RecentInfo item 0x16973b0
Dec  4 09:54:45 computer gnome-session[2366]: ** (zeitgeist-datahub:2948): 
CRITICAL **: string_strip: assertion 'self != NULL' failed
Dec  4 09:54:45 computer gnome-session[2366]: (zeitgeist-datahub:2948): 
Gtk-CRITICAL **: gtk_recent_info_get_application_info: assertion 'app_name != 
NULL' failed

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

Title:
  Lots of zeitgeist errors

Status in Zeitgeist Datahub:
  Confirmed
Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My
  system is behaving weird lately since the upgrade from Ubuntu 14.10 to
  15.04 so I am guessing this might be related. Alright, here the
  relevant log entries:

  Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during 
inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: 
Incomplete event: interpretation, manifestation and actor are required
  ...
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** 
(zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: 
Desktop file for 
"file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project"
 was not found, exec: sublime_text, mime_type: application/octet-stream
  Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: 

[Touch-packages] [Bug 1732050] [NEW] I am unable to receive calls, the phone will be ringing but it looks like screen is locked

[Suneel M P]

Public bug reported:

I recently updated my BQ Aquarius e5 Ubuntu edition. Now I am unable to
receive any calls. Screen will be locked but phone will be ringing.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  I am unable to receive calls, the phone will be ringing but it looks
  like screen is locked

Status in dialer-app package in Ubuntu:
  New

Bug description:
  I recently updated my BQ Aquarius e5 Ubuntu edition. Now I am unable
  to receive any calls. Screen will be locked but phone will be ringing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1732050/+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 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode

[Simon P.]

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

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

Title:
  VLC under Wayland causes system freezes in fullscreen mode

Status in vlc package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Ubuntu version: 17.10 (most recent updates as of October 3rd)
  vlc version:  2.2.6-6

  Whan I expect to happen: When playing a video in vlc and switching to
  fullscreen mode everything should work fine. Also when changing to a
  different position of a movie in fullscreen I expect the player to
  just switch to that position.

  What actually happens: It seems to depend a little on the file type of
  the video, mostly I get problems when going to fullscreen mode and
  then switching to a different position with the playback position bar.
  With some videos it was even enough to just open the fullscreen mode.
  The video freezes just displaying a frame while the audio keeps
  playing. The computer does not react any more to mouse or keyboard
  input, I have to perform a hard reboot.

  This problem only appears under the Wayland session, in the Xorg session 
everything works fine as expected.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-09-30 (2 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  Package: vlc 2.2.6-6
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1720901/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c

[Juan P. Tamayo]

** Also affects: gnome-mplayer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  GLib-CRITICAL **: Source ID was not found when attempting to remove it
  - warning when leaving Network menu of g-c-c

Status in AndroidSDK:
  New
Status in Banshee:
  New
Status in gnome-control-center:
  Incomplete
Status in GParted:
  Unknown
Status in notification-daemon:
  New
Status in anjuta package in Ubuntu:
  Confirmed
Status in consolekit package in Ubuntu:
  Confirmed
Status in f-spot package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Triaged
Status in gnome-mplayer package in Ubuntu:
  New
Status in putty package in Ubuntu:
  Confirmed

Bug description:
  Steps to recreate:
  1. Open gnome-control-center in terminal.
  2. Go to Network.
  3. Go back to All preferences.
  4. Notice that in terminal there is a warning:

  $ gnome-control-center

  (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not
  found when attempting to remove it

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu49
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Dec 26 21:03:52 2013
  InstallationDate: Installed on 2013-10-15 (71 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131015)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1636573] Re: xinit flooding syslog

[Dominik P]

I have the impression that there is no maintainer subscribed to this
issue.

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

Title:
  xinit flooding syslog

Status in pyOpenSSL:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in pyopenssl source package in Yakkety:
  Fix Released
Status in xorg source package in Yakkety:
  Invalid

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pyopenssl/+bug/1636573/+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 1636573] Re: xinit flooding syslog

[Dominik P]

So here I am, back after two months. Now this issue crashes kodi
plugins. Is the backport to the lts planned?

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

Title:
  xinit flooding syslog

Status in pyOpenSSL:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in pyopenssl source package in Yakkety:
  Fix Released
Status in xorg source package in Yakkety:
  Invalid

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pyopenssl/+bug/1636573/+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 1702642] [NEW] package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to install/upgrade: package ubuntu-mono is already installed and configured

[P Gopal Krishnan]

Public bug reported:

I was installing software updates from Ubuntu center, when these issues
corpped up.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ubuntu-mono 14.04+16.04.20161024-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Thu Jul  6 13:01:43 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
DuplicateSignature:
 package:ubuntu-mono:14.04+16.04.20161024-0ubuntu1
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package accountsservice (--configure):
  package accountsservice is already installed and configured
ErrorMessage: package ubuntu-mono is already installed and configured
InstallationDate: Installed on 2017-06-15 (21 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: ubuntu-themes
Title: package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to 
install/upgrade: package ubuntu-mono is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package need-duplicate-check xenial

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

Title:
  package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to
  install/upgrade: package ubuntu-mono is already installed and
  configured

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  I was installing software updates from Ubuntu center, when these
  issues corpped up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-mono 14.04+16.04.20161024-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Thu Jul  6 13:01:43 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   package:ubuntu-mono:14.04+16.04.20161024-0ubuntu1
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package accountsservice (--configure):
package accountsservice is already installed and configured
  ErrorMessage: package ubuntu-mono is already installed and configured
  InstallationDate: Installed on 2017-06-15 (21 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ubuntu-themes
  Title: package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to 
install/upgrade: package ubuntu-mono is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1702642/+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 1700318] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

[Geoffrey P.]

Public bug reported:

1) Description: Ubuntu 16.04.2 LTS
Release:16.04

2) alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu5
  Candidate: 1.0.25+dfsg-0ubuntu5
  Version table:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status

3) I expected to have working sound. On an upgrade from 14.04 LTS I
would get an occasional pop or intro sound as Ubuntu booted up and then
it would be silent. I worked through all of the sound guides I could but
nothing worked. Actually, now I don't even get any sound at all.

4) Silence will fall when the question is asked, happened.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70
Uname: Linux 4.4.0-82-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  geoffrey   2180 F pulseaudio
CurrentDesktop: Unity
Date: Sat Jun 24 22:50:06 2017
InstallationDate: Installed on 2013-08-06 (1418 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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:  geoffrey   2180 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to xenial on 2017-06-13 (11 days ago)
dmi.bios.date: 06/26/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.60
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-0D102G:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite L745
dmi.product.version: PSK0YU-0D102G
dmi.sys.vendor: TOSHIBA
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-24T22:42:56.987018

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


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

** Attachment added: "hardware.txt"
   
https://bugs.launchpad.net/bugs/1700318/+attachment/4902593/+files/hardware.txt

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

Title:
  [Satellite L745, Conexant CX20585, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  1) Description:   Ubuntu 16.04.2 LTS
  Release:  16.04

  2) alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  3) I expected to have working sound. On an upgrade from 14.04 LTS I
  would get an occasional pop or intro sound as Ubuntu booted up and
  then it would be silent. I worked through all of the sound guides I
  could but nothing worked. Actually, now I don't even get any sound at
  all.

  4) Silence will fall when the question is asked, happened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70
  Uname: Linux 4.4.0-82-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  geoffrey   2180 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Jun 24 22:50:06 2017
  InstallationDate: Installed on 2013-08-06 (1418 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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:  geoffrey   2180 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: 

[Touch-packages] [Bug 1699303] [NEW] [MS-7971, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

[Christian P Coseglia]

Public bug reported:

New to Ubuntu not sure what to do. Had similar issue a year or so back
on windows and forgot how to fix it.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
Uname: Linux 4.10.0-24-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  christian   1658 F pulseaudio
 /dev/snd/controlC2:  christian   1658 F pulseaudio
 /dev/snd/controlC1:  christian   1658 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Tue Jun 20 13:18:00 2017
InstallationDate: Installed on 2017-06-19 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI_1 failed
Symptom_Card: HDA ATI HDMI - HDA ATI HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  christian   1658 F pulseaudio
 /dev/snd/controlC2:  christian   1658 F pulseaudio
 /dev/snd/controlC1:  christian   1658 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [MS-7971, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.E0
dmi.board.asset.tag: Default string
dmi.board.name: Z170A PC MATE (MS-7971)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.E0:bd05/02/2017:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnZ170APCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7971
dmi.product.version: 2.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug zesty

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

Title:
  [MS-7971, ATI R6xx HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New to Ubuntu not sure what to do. Had similar issue a year or so back
  on windows and forgot how to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1658 F pulseaudio
   /dev/snd/controlC2:  christian   1658 F pulseaudio
   /dev/snd/controlC1:  christian   1658 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Tue Jun 20 13:18:00 2017
  InstallationDate: Installed on 2017-06-19 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI_1 failed
  Symptom_Card: HDA ATI HDMI - HDA ATI HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   1658 F pulseaudio
   /dev/snd/controlC2:  christian   1658 F pulseaudio
   /dev/snd/controlC1:  christian   1658 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [MS-7971, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.E0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A PC MATE (MS-7971)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.E0:bd05/02/2017:svnMSI:pnMS-7971:pvr2.0:rvnMSI:rnZ170APCMATE(MS-7971):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7971
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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