[Touch-packages] [Bug 1850748] [NEW] hud-tools depends on obsolete python-polib

[Steve Langasek]

Public bug reported:

The Ubuntu-specific hud-tools package depends on python-polib, which has
been dropped from the polib source package in Debian and focal-proposed.
To remain in Ubuntu 20.04 and beyond, this package will need to be
updated to not depend on python-polib.

It also appears that the hud-tools package does not comply with the
python packaging policy, because it depends on python-polib and python-
lxml but does not depend on python at all.  Given that future versions
of the system will not ship /usr/bin/python as a python2 interpreter,
it's important that this be fixed as well if the intent is to continue
shipping hud-tools.

** Affects: hud (Ubuntu)
 Importance: Critical
 Status: Triaged

** Changed in: hud (Ubuntu)
   Importance: Undecided => Critical

** Changed in: hud (Ubuntu)
   Status: New => Triaged

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

Title:
  hud-tools depends on obsolete python-polib

Status in hud package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu-specific hud-tools package depends on python-polib, which
  has been dropped from the polib source package in Debian and focal-
  proposed.  To remain in Ubuntu 20.04 and beyond, this package will
  need to be updated to not depend on python-polib.

  It also appears that the hud-tools package does not comply with the
  python packaging policy, because it depends on python-polib and
  python-lxml but does not depend on python at all.  Given that future
  versions of the system will not ship /usr/bin/python as a python2
  interpreter, it's important that this be fixed as well if the intent
  is to continue shipping hud-tools.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1850748/+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 1849859] Re: error when connecting to smb server

[Christian Ehrhardt ]

Hiho,
keine Angst "von Interesse" ist erst einmal jede Meldung. Ich selbst bin nur 
nicht so fit mit dem Druckteil von Samba und Co.

I think we should add cups and system-config-printer bug tasks as I
think this isn't really a samba things.

Ich Fasse mal zusammen:
- printer setup that worked with 18.04, but fails with 20.04
- no authentication configured on the printer side
- authentication pop up then fails missing said authentication (see trace in 
terminal.bmp)
- Maybe related to bug 1849859 or similar

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

** Also affects: system-config-printer (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1849859] Re: error when connecting to smb server

[Christian Ehrhardt ]

@Till - does any of this look familiar from a printing POV?

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

Title:
  error when connecting to smb server

Status in cups package in Ubuntu:
  New
Status in samba package in Ubuntu:
  New
Status in system-config-printer package in Ubuntu:
  New

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Mathew Hodson]

** No longer affects: gnome-shell (Ubuntu)

** Changed in: systemd (Ubuntu Eoan)
   Importance: Undecided => High

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

Title:
  Unable to shutdown or restart from log-in screen

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1847896/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

[Bug Watch Updater]

** Changed in: glib2.0 (Debian)
   Status: Confirmed => Fix Released

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1850702] UdevDb.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

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

[Filipe Garrett]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1850702/+attachment/5301637/+files/WifiSyslog.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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
 

[Touch-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Filipe Garrett]

Tried the apport-collect command, but it fails because it says it didn't
found linux and alsa-driver packages.

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG 

[Touch-packages] [Bug 1850702] ProcCpuinfoMinimal.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcCpuinfo.txt

[Filipe Garrett]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1850702/+attachment/5301629/+files/ProcCpuinfo.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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcCpuinfoMinimal.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] RfKill.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] PulseList.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] RfKill.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] ProcModules.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcEnviron.txt

[Filipe Garrett]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1850702/+attachment/5301631/+files/ProcEnviron.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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] PulseList.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] ProcInterrupts.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] Lspci.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] Lsusb.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] IwConfig.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] CRDA.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] CurrentDmesg.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] UdevDb.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] AlsaInfo.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

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

[Filipe Garrett]

apport information

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

** Description changed:

  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.
  
  When I plug a headphone, I can hear the sound being played very faintly.
  If I bump the volume to the maximum, that is. The sound is very
  distorted, like a buzz effect being applied over it.
  
  I noticed that if I delete /.config/pulse the distortion goes away, but
  the sound remains very low. After some time, the buzzing effect comes
  back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  filipe 1294 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-10-29 (1 days ago)
+ InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-19-generic N/A
+  linux-backports-modules-5.3.0-19-generic  N/A
+  linux-firmware1.183.1
+ Tags:  eoan
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/10/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P02REZ.040.190610.FL
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: NP760XBE-XW1BR
+ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.chassis.version: N/A
+ dmi.modalias: 

[Touch-packages] [Bug 1850702] ProcInterrupts.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcModules.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcEnviron.txt

[Filipe Garrett]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1850702/+attachment/5301616/+files/ProcEnviron.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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] ProcCpuinfo.txt

[Filipe Garrett]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1850702/+attachment/5301614/+files/ProcCpuinfo.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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] IwConfig.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] Lsusb.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] Lspci.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] CurrentDmesg.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: 

[Touch-packages] [Bug 1850702] CRDA.txt

[Filipe Garrett]

apport information

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Touch-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Filipe Garrett]

apport information

** Tags added: apport-collected

** Description changed:

  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.
  
  When I plug a headphone, I can hear the sound being played very faintly.
  If I bump the volume to the maximum, that is. The sound is very
  distorted, like a buzz effect being applied over it.
  
  I noticed that if I delete /.config/pulse the distortion goes away, but
  the sound remains very low. After some time, the buzzing effect comes
  back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  filipe 1294 F pulseaudio
+ CurrentDesktop: KDE
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-10-29 (1 days ago)
+ InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
+ RelatedPackageVersions:
+  linux-restricted-modules-5.3.0-19-generic N/A
+  linux-backports-modules-5.3.0-19-generic  N/A
+  linux-firmware1.183.1
+ Tags:  eoan
+ Uname: Linux 5.3.0-19-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/10/2019
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P02REZ.040.190610.FL
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: NP760XBE-XW1BR
+ dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
+ dmi.product.family: Notebook 7 Series
+ dmi.product.name: 760XBE
+ dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
+ dmi.product.version: P02REZ
+ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:

[Touch-packages] [Bug 1850702] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1850702

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Filipe Garrett]

Yes, I'm on a dual-boot setup.

I think it's also worth mentioning that I've tried Manjaro and
experienced the same problems.

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

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

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Daniel van Vugt]

I'm assuming when you say Windows works fine that you mean Windows on
this same laptop...?

** Summary changed:

- [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is 
faint and distorted
+ [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is 
faint and distorted (but works fine in Windows)

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

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

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1802007] Re: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dp

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to
  install/upgrade: unable to open '/usr/share/icons/ubuntu-mono-
  light/status/22/gnome-netstatus-rx.svg.dpkg-new': Operation not
  permitted

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  asdf

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-1018.21-oem 4.15.18
  Uname: Linux 4.15.0-1018-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Wed Oct 31 23:53:13 2018
  DuplicateSignature:
   package:ubuntu-mono:16.10+18.04.20180421.1-0ubuntu1
   Unpacking ubuntu-mono (16.10+18.04.20181005-0ubuntu1) over 
(16.10+18.04.20180421.1-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-NjXhHv/37-ubuntu-mono_16.10+18.04.20181005-0ubuntu1_all.deb
 (--unpack):
unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  ErrorMessage: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-08-30 (68 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: ubuntu-themes
  Title: package ubuntu-mono 16.10+18.04.20180421.1-0ubuntu1 failed to 
install/upgrade: unable to open 
'/usr/share/icons/ubuntu-mono-light/status/22/gnome-netstatus-rx.svg.dpkg-new': 
Operation not permitted
  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/1802007/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted

[Filipe Garrett]

First of all, thanks for replying!

I did this already when I noticed the problem a couple days ago with my
main pair and with some gaming gear to no avail. But, since you asked, I
did it again with all the wired headphones I could find around, even
some crappy cellphone headphones and the results are the same: extremely
low sound and heavily distorted. I even tried with a P2 cable extender
and the problem remains, I'm 100% sure that it isn't my headphones.

Also tried all those headphones and cable extender on Windows and
everything works fine.

(all of them work perfectly on other devices running Android, on my PS4
through the DualShock jack and with my smart TV)

It's important to point out that I know of at least another user of this
machine facing the same issue. He posted about HDMI output problems -
that I can confirm on my laptop as well - on the Linux Mint (link down
below) forums and I got in touch with him, so I don't think that this
has something to do with the physical connection, specially since the
distortion goes away for a bit if you delete the /.config/pulse
directory.

I didn't file a bug report about the HDMI output because it isn't as important 
as the headphone output for my workflow.
https://forums.linuxmint.com/viewtopic.php?f=49=303303

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted

[Daniel van Vugt]

Thanks for the bug report. This kind of sound problem is usually a bad
connection between the audio socket and the headphones. Usually it is
because of the differing standards in common use:

https://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/

and/or just slight imperfections in how the connectors come into
contact.

So please try some different headphones as a test. Please also try using
any kind of adapter or other audio cable you have to see if it gets a
better connection and improves the sound.


** Summary changed:

- [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack]No sound output with 
headphones
+ [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is 
faint and distorted

** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1850681] Re: TREKSTOR Primebook C11B touchpad and touchscreen not working

[Daniel van Vugt]

Thanks for the bug report. Your kernel log mentions some errors
regarding what looks like a Synaptics touchpad:

[5.550275] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vdd not found, 
using dummy regulator
[5.550304] i2c_hid i2c-SYNA3602:00: Linked as a consumer to regulator.0
[5.550306] i2c_hid i2c-SYNA3602:00: i2c-SYNA3602:00 supply vddl not found, 
using dummy regulator

[5.568184] i2c_hid i2c-SYNA3602:00: unexpected HID descriptor
bcdVersion (0x)

So this sounds like a kernel bug, or a BIOS or hardware problem.

** Summary changed:

- Touchpad and touchsrceen not working
+ TREKSTOR Primebook C11B touchpad and touchscreen not working

** Package changed: xorg (Ubuntu) => linux (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/1850681

Title:
  TREKSTOR Primebook C11B touchpad and touchscreen not working

Status in linux package in Ubuntu:
  New

Bug description:
  touchpad not working, only usb-mouse is recognized. touchscreen functionality 
not working, but that would be rather less important. Everything else is 
perfectly fine. (18.04 LTS)
  TREKSTOR Primebook C11B

  Thanks :-)

  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.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 18:43:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TREKSTOR Primebook C11B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.1.2
  dmi.board.asset.tag: Default string
  dmi.board.name: Apollolake_alk_V01
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: Primebook C11B
  dmi.product.sku: CFALKWW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR
  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/linux/+bug/1850681/+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 1850635] Re: Some applications don't redraw their windows correctly

[Daniel van Vugt]

You seem to be using FVWM and the old Intel driver (not the current
one). So I would try eliminating those as possible causes.

1. Does the bug also occur in Gnome Shell Xorg sessions? (log into
'Ubuntu')

2. Please edit or move or delete /etc/X11/xorg.conf so that Xorg does
not load the 'intel' driver. We would prefer it to load the newer
'modeset' driver.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

** Also affects: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: New => Incomplete

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

Title:
  Some applications don't redraw their windows correctly

Status in fvwm package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After updating from 19.04 to 19.10 I noted that some apps don't redraw
  their window(s) correctly.  Affected apps include (it seems) all Qt-
  based apps (including KDE and VirtualBox), as well as
  firefox/thunderbird.

  Unaffected apps include emacs, chrome, xterm.

  The symptom is that an affected app will only redraw its window when
  another X window redraws its window.  If there is no other window,
  then the app's window is not redrawn at all.

  This is best illustrated with a video, which shows the problem using
  konsole and kpat (both KDE apps) :-

  https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA

  I am using the intel graphics driver (no graphics card).

  Other info as requested below :-

  $ lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  $ apt-cache policy xserver-xorg
  xserver-xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Oct 30 11:50:09 2019
  DistUpgraded: 2019-10-21 13:25:02,550 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
  InstallationDate: Installed on 2016-01-02 (1396 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=8af2cd02-0009-4ce5-9ec6-e6cdf44c9411 ro nopti
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (8 days ago)
  dmi.bios.date: 07/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   #enabled=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-01-06T17:10:43.876145
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  

[Touch-packages] [Bug 1850646] Re: Sound output device switched on DP/MST connect

[Daniel van Vugt]

Switching on connect is an intentional design choice for Ubuntu. If you
would like to disable it then please just comment out this line:

  load-module module-switch-on-connect

in /etc/pulse/default.pa

So this isn't a bug, but it does seem to overlap with bug 1847570 so
please see that too.

** Package changed: gnome-shell (Ubuntu) => pulseaudio (Ubuntu)

** Changed in: pulseaudio (Ubuntu)
   Status: New => Invalid

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

Title:
  Sound output device switched on DP/MST connect

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  1. Starting with sound output set to line-out with DP/MST/HDMI monitor 
connected.
  2. Disconnect monitor. Sound output remains on line-out. Music continues 
playing etc.
  3. Re-connect monitor. Music/sound stops being produced. Sound output device 
is switched to HDMI/Display Port 6 device. 

  Sound output device should remain on user-selected device unless user
  interactively changes the output device. Or add configurable option
  for "sound output device auto switching".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.3.7-050307-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 10:14:02 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-04 (329 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (7 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:59:11.363686

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850646/+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 1850668] Re: No conozco el error

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  No conozco el error

Status in Ubuntu:
  Incomplete

Bug description:
  NO se que le pasa

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 30 17:33:50 2019
  DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 430.50, 5.0.0-32-generic, x86_64: installed
   nvidia, 430.50, 5.3.0-19-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1261]
  InstallationDate: Installed on 2019-08-19 (72 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Acer Aspire A717-72G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux 
acpi_backlight=vendor quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago)
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charizard_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.22
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A717-72G
  dmi.product.sku: 
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer
  nvidia-settings:
   ERROR: Unable to load info from any available system
   
   
   ERROR: Unable to load info from any available system
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Wed Oct 30 16:11:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4509 
   vendor AUO
  xserver.version: 2:1.20.5+git20191008-0ubuntu1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1850646] [NEW] Sound output device switched on DP/MST connect

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1. Starting with sound output set to line-out with DP/MST/HDMI monitor 
connected.
2. Disconnect monitor. Sound output remains on line-out. Music continues 
playing etc.
3. Re-connect monitor. Music/sound stops being produced. Sound output device is 
switched to HDMI/Display Port 6 device. 

Sound output device should remain on user-selected device unless user
interactively changes the output device. Or add configurable option for
"sound output device auto switching".

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
Uname: Linux 5.3.7-050307-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 30 10:14:02 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-04 (329 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-23 (7 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2019-01-08T10:59:11.363686

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


** Tags: amd64 apport-bug eoan
-- 
Sound output device switched on DP/MST connect
https://bugs.launchpad.net/bugs/1850646
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

[Daniel van Vugt]

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: High
   Status: Invalid

** Also affects: systemd (Ubuntu Focal)
   Importance: High
   Status: Fix Released

** No longer affects: gnome-shell (Ubuntu Eoan)

** No longer affects: gnome-shell (Ubuntu Focal)

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1849416] Re: Xubuntu ping command leading to all of sessions closed

[Yang yanbo]

Sorry for that I haven't received logs. I have tested the session with
ping and the session dropped down,then I used "journalctl _PID=25564"
command in root with no related logs return.("lsof -i" was used for
checking the session number)

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

Title:
  Xubuntu ping command leading to all of sessions closed

Status in iputils package in Ubuntu:
  Incomplete

Bug description:
  Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command,
  all the sessions will  be closed and returned socket error 10053.
  However,it is normal when I ping the valid address likes: ping -c 4
  bugs.launchpad.net. But when I ping other address which would  return
  "Destination Host Unreachable", all the distal session in putty or
  another shell would be colsed with "Connection closed by foreign
  host". Other commands like netcat have the same error.

  I checked the syslog without no returned error after using ping for
  this strange phenomenon, through syslog included some related
  information:

  syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time 
server 91.189.89.199:123 (ntp.ubuntu.com).
  syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for 
reply from 91.189.89.199:123 (ntp.ubuntu.com).

  or

  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)

  I guess some daemon programs may peform their function via ping or
  other ways. User sessions always be closed immediately and connection
  refusion time usually takes no more than 1 min, and it won't kill
  running jobs in closed session.

  Especially, this phenomenon never happens in apt-get and conda or wget
  command.

  I have no idea what lead to this strange phenomenon. Please give me
  advice.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1849416/+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 1848200] Autopkgtest regression report (gdb/8.1-0ubuntu3.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gdb (8.1-0ubuntu3.2) for bionic have 
finished running.
The following regressions have been reported in tests triggered by the package:

apport/2.20.9-0ubuntu7.8 (i386, amd64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#gdb

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  Fix Committed
Status in gdb source package in Disco:
  Invalid
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack]No sound output with headphones

[Filipe Garrett]

** Summary changed:

- No sound output with headphones
+ [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack]No sound output with 
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/1850702

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack]No sound
  output with headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

** Package changed: ibus (Debian) => glib2.0 (Debian)

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 package in Debian:
  Confirmed

Bug description:
  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed! 
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1844853/+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 1850704] Re: networkd doesn't set MTUBytes if interface is already up

[Bug Watch Updater]

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

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

Title:
  networkd doesn't set MTUBytes if interface is already up

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  if a networkd .network file specifies a [Link] section with
  MTUBytes=XXX set, networkd will only apply that mtu if the interface
  is down when networkd starts; if the interface is already up, the mtu
  won't be applied.

  [test case]

  on a bionic system, create a .network file like:

  [Match]
  Name=ens8

  [Link]
  MTUBytes=

  then, reboot.  The interface should be set correctly with that mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  
  now, manually change the interface back to 1500 mtu, and restart networkd, 
then recheck the mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo ip l set mtu 1500 dev ens8
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo systemctl restart systemd-networkd
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  [regression potential]

  low, but any regression would likely involve failure to correctly set
  the configured mtu.

  this is needed only in bionic, it's fixed in disco and later already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1850704/+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 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Thanks for the quick feedback!

I have just uploaded this fix to Ubuntu, it is waiting in the review
queue. Per the procedure, when it is accepted you will be asked to test
the fix again, this time installing the packages from bionic-proposed
repository.

Also updated the bug description to contain the needed fields for stable
release procedure.

** Description changed:

  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677
  
- In Qt5 applications, print dialog (Printer Properties) always defaults
- to A4 paper size, even when Letter is set as a default in all system and
- KDE preferences. After changing manually, Letter-size pages print
- correctly, but the setting does not stick. The issue also affects other
- print settings, e.g. margins, though the aforementioned patch does not
- deal with these. A similar issue regarding the duplex setting was
- reported as Launchpad bug 1776173, and subsequently fixed, but other
- print settings continue to cause problems.
+ [Impact]
+ In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.
  
- Behavior expected: Print dialog would default to Letter paper size,
- which is set in all available system and KDE preferences, and that was
- selected for previous prints.
+ This impacts users of Qt applications who print things and live in
+ countries where ISO 216 is not default, most notably the United States.
  
- Behavior observed: Print dialog always defaults to A4, and page size
- needs to be changed manually before every print.
+ [Test Case]
+ 1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
+ 2) Open any Qt application (e.g. KWrite or Falkon).
+ 3) Open a print dialog.
+ 4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.
+ 
+ [Regression Potential]
+ Two possibilities for regressions that I can imagine are:
+ - crashes because something is not defined;
+ - wrong default paper size (A4 wanted but CUPS returns something else).
+ 
+ [Additional Information]
+ The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.
  
  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  [Impact]
  In Qt5 applications, print dialog (Printer Properties) always defaults to A4 
paper size, even when Letter is set as a default in all system and KDE 
preferences. After changing manually, Letter-size pages print correctly, but 
the setting does not stick.

  This impacts users of Qt applications who print things and live in
  countries where ISO 216 is not default, most notably the United
  States.

  [Test Case]
  1) Use system settings (KDE preferences, gnome-control-center or 
system-config-printer) to set the printer size to Letter.
  2) Open any Qt application (e.g. KWrite or Falkon).
  3) Open a print dialog.
  4) Behavior expected: Print dialog would default to Letter paper size and not 
A4.

  [Regression Potential]
  Two possibilities for regressions that I can imagine are:
  - crashes because something is not defined;
  - wrong default paper size (A4 wanted but CUPS returns something else).

  [Additional Information]
  The issue also affects other print settings, e.g. margins, though the 
aforementioned patch does not deal with these. A similar issue regarding the 
duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, 
but other print settings continue to cause problems.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1671951] Re: networkd should allow configuring IPV6 MTU

[Ryan Harper]

@Dan,

Ill try the ppa and report back.

cloud-init is not doing anything special here, we render the config and call 
netplan generate.
If we take cloud-init out of the picture, and just have a file in /etc/netplan 
it will still fail due to the udev issue you specify. Shouldn't netplan itself 
handle container-based rendering if [Link] sections when running inside a 
container?

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions

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

[Touch-packages] [Bug 1849416] Re: Xubuntu ping command leading to all of sessions closed

[Sebastien Bacher]

Could you add a journalctl log of a session having the issue?

** Changed in: iputils (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Xubuntu ping command leading to all of sessions closed

Status in iputils package in Ubuntu:
  Incomplete

Bug description:
  Hi,my server version is Ubuntu 18.04.3 LTS. When I use ping command,
  all the sessions will  be closed and returned socket error 10053.
  However,it is normal when I ping the valid address likes: ping -c 4
  bugs.launchpad.net. But when I ping other address which would  return
  "Destination Host Unreachable", all the distal session in putty or
  another shell would be colsed with "Connection closed by foreign
  host". Other commands like netcat have the same error.

  I checked the syslog without no returned error after using ping for
  this strange phenomenon, through syslog included some related
  information:

  syslog.1:Oct 22 21:15:16 dell systemd-timesyncd[1298]: Synchronized to time 
server 91.189.89.199:123 (ntp.ubuntu.com).
  syslog.1:Oct 22 21:17:35 dell systemd-timesyncd[1298]: Timed out waiting for 
reply from 91.189.89.199:123 (ntp.ubuntu.com).

  or

  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
  messages:Oct 22 23:14:53 dell blueman.desktop[3974]: 
ERROR:dbus.proxies:Introspect error on org.bluez:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to 
activate service 'org.bluez': timed out (service_start_timeout=25000ms)

  I guess some daemon programs may peform their function via ping or
  other ways. User sessions always be closed immediately and connection
  refusion time usually takes no more than 1 min, and it won't kill
  running jobs in closed session.

  Especially, this phenomenon never happens in apt-get and conda or wget
  command.

  I have no idea what lead to this strange phenomenon. Please give me
  advice.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1849416/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Paul White]

Comment #10 means fixed in focal (20.04) only for now.
Stable Release Update in eoan (19.10) to follow in due course.

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1671951] Re: networkd should allow configuring IPV6 MTU

[Dan Streetman]

@raharper could you give the systemd in this ppa a test:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd

also, you're setting the MTUBytes via .link file, but that won't work
inside an lxd container as that setting only has any effect during udev
processing of interface 'add' uevent, which doesn't happen inside an lxd
container because 1) the interface already exists when the container
boots up and 2) systemd-udev-trigger.service has no effect (unlike bare
metal systems or vms) because unprivileged containers can't force uevent
generation by writing to sysfs uevent nodes.  Instead try adding a
[Link] section to the .network file with the MTUBytes; that will get
applied every time networkd starts.

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger 

[Touch-packages] [Bug 1849907] Re: Add Online Account Nextcloud no Connect button on Unity

[Sebastien Bacher]

** Package changed: gnome-online-accounts (Ubuntu) => unity-control-
center (Ubuntu)

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

Title:
  Add Online Account Nextcloud no Connect button on Unity

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I am trying to add an online account, nextcloud

  three fields show, server, username and password.

  There is no Apply or OK button.

  I cannot add the account.

  Resizing the window does not help. Fields just get longer, still no
  buttons.

  Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1849907/+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 1848784] Re: Crash in Qt 5.12.2

[Dmitry Shachnev]

** Information type changed from Public to Public Security

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

Title:
  Crash in Qt 5.12.2

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  Originally reported by Robert Loehning in
  :

  Every application based on Qt will crash when opening a crafted plain
  text file. Could you please add the patch below to your builds to fix
  this?

  https://codereview.qt-project.org/c/qt/qtbase/+/271889

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1848784/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Scott Dennis]

i got an email about released. I also notice on here that a fix has been
released. I don't see it as an update via software updates. How to I get
the fix.

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1846821] Re: Qt print dialog has wrong default page size

[Maciej Puzio]

I can confirm that the patch fixes the problem, i.e. Qt print dialog now 
defaults to page size as set in System Settings Printers applet. To apply the 
fix, it was enough to add the PPA repository, upgrade libqt5printsupport5 
package, and then close and reopen applications that were affected by the bug.
Thank you very much for your work.

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1850159] Re: dhclient can't obtain IPv6 addr

[Sebastien Bacher]

closing since the description isn't clear, feel free to reopen if the
requested screenshot showing the problem is added though

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  dhclient can't obtain IPv6 addr

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  gnome-control-center reports Ethernet Connection Failure with TLS
  Authentication

  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Show Connected for Wired Connection
  4) Show Disconnected for Wired Connection

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 28 17:06:43 2019
  InstallationDate: Installed on 2019-08-01 (88 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850159/+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 1850704] Re: networkd doesn't set MTUBytes if interface is already up

[Dan Streetman]

** Bug watch added: github.com/systemd/systemd/issues #9254
   https://github.com/systemd/systemd/issues/9254

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/9254
   Importance: Unknown
   Status: Unknown

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

Title:
  networkd doesn't set MTUBytes if interface is already up

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  if a networkd .network file specifies a [Link] section with
  MTUBytes=XXX set, networkd will only apply that mtu if the interface
  is down when networkd starts; if the interface is already up, the mtu
  won't be applied.

  [test case]

  on a bionic system, create a .network file like:

  [Match]
  Name=ens8

  [Link]
  MTUBytes=

  then, reboot.  The interface should be set correctly with that mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  
  now, manually change the interface back to 1500 mtu, and restart networkd, 
then recheck the mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo ip l set mtu 1500 dev ens8
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo systemctl restart systemd-networkd
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  [regression potential]

  low, but any regression would likely involve failure to correctly set
  the configured mtu.

  this is needed only in bionic, it's fixed in disco and later already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1850704/+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 1850702] [NEW] No sound output with headphones

[Filipe Garrett]

Public bug reported:

I can't get sound of my laptop (Samsung Notebook 7 Force) through the
headphone jack. The speakers work fine.

When I plug a headphone, I can hear the sound being played very faintly.
If I bump the volume to the maximum, that is. The sound is very
distorted, like a buzz effect being applied over it.

I noticed that if I delete /.config/pulse the distortion goes away, but
the sound remains very low. After some time, the buzzing effect comes
back.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Wed Oct 30 16:03:41 2019
InstallationDate: Installed on 2019-10-29 (1 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: alsa-driver amd64 eoan

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

** Package changed: ubuntu-release-upgrader (Ubuntu) => alsa-driver
(Ubuntu)

** Description changed:

  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.
  
  When I plug a headphone, I can hear the sound being played very faintly.
  If I bump the volume to the maximum, that is. The sound is very
  distorted, like a buzz effect being applied over it.
  
  I noticed that if I delete /.config/pulse the distortion goes away, but
- the sound remains very low.
+ the sound remains very low. After some time, the buzzing effect comes
+ back.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  No sound output with headphones

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1850702/+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 1850704] [NEW] networkd doesn't set MTUBytes if interface is already up

[Dan Streetman]

Public bug reported:

[impact]

if a networkd .network file specifies a [Link] section with MTUBytes=XXX
set, networkd will only apply that mtu if the interface is down when
networkd starts; if the interface is already up, the mtu won't be
applied.

[test case]

on a bionic system, create a .network file like:

[Match]
Name=ens8

[Link]
MTUBytes=

then, reboot.  The interface should be set correctly with that mtu:

$ ip l show ens8
3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff


now, manually change the interface back to 1500 mtu, and restart networkd, then 
recheck the mtu:

$ ip l show ens8
3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
$ sudo ip l set mtu 1500 dev ens8
$ ip l show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
$ sudo systemctl restart systemd-networkd
$ ip l show ens8
3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

[regression potential]

low, but any regression would likely involve failure to correctly set
the configured mtu.

this is needed only in bionic, it's fixed in disco and later already.

** Affects: systemd
 Importance: Unknown
 Status: Unknown

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu Bionic)
   Status: New => In Progress

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

Title:
  networkd doesn't set MTUBytes if interface is already up

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [impact]

  if a networkd .network file specifies a [Link] section with
  MTUBytes=XXX set, networkd will only apply that mtu if the interface
  is down when networkd starts; if the interface is already up, the mtu
  won't be applied.

  [test case]

  on a bionic system, create a .network file like:

  [Match]
  Name=ens8

  [Link]
  MTUBytes=

  then, reboot.  The interface should be set correctly with that mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  
  now, manually change the interface back to 1500 mtu, and restart networkd, 
then recheck the mtu:

  $ ip l show ens8
  3: ens8:  mtu  qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo ip l set mtu 1500 dev ens8
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff
  $ sudo systemctl restart systemd-networkd
  $ ip l show ens8
  3: ens8:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:30:4c:1e brd ff:ff:ff:ff:ff:ff

  [regression potential]

  low, but any regression would likely involve failure to correctly set
  the configured mtu.

  this is needed only in bionic, it's fixed in disco and later already.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1850704/+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 1850702] [NEW] No sound output with headphones

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I can't get sound of my laptop (Samsung Notebook 7 Force) through the
headphone jack. The speakers work fine.

When I plug a headphone, I can hear the sound being played very faintly.
If I bump the volume to the maximum, that is. The sound is very
distorted, like a buzz effect being applied over it.

I noticed that if I delete /.config/pulse the distortion goes away, but
the sound remains very low.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Wed Oct 30 16:03:41 2019
InstallationDate: Installed on 2019-10-29 (1 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: alsa-driver amd64 eoan
-- 
No sound output with headphones
https://bugs.launchpad.net/bugs/1850702
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 1846821] Re: Qt print dialog has wrong default page size

[Dmitry Shachnev]

Can you please test the packages in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3833?

The patch did not apply to 5.9 branch so I had to make some changes to
it.

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

Title:
  Qt print dialog has wrong default page size

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  Please backport Qt patch 213677 to qtbase-opensource-src
  https://codereview.qt-project.org/c/qt/qtbase/+/213677

  In Qt5 applications, print dialog (Printer Properties) always defaults
  to A4 paper size, even when Letter is set as a default in all system
  and KDE preferences. After changing manually, Letter-size pages print
  correctly, but the setting does not stick. The issue also affects
  other print settings, e.g. margins, though the aforementioned patch
  does not deal with these. A similar issue regarding the duplex setting
  was reported as Launchpad bug 1776173, and subsequently fixed, but
  other print settings continue to cause problems.

  Behavior expected: Print dialog would default to Letter paper size,
  which is set in all available system and KDE preferences, and that was
  selected for previous prints.

  Behavior observed: Print dialog always defaults to A4, and page size
  needs to be changed manually before every print.

  Software versions:
  lsb_release: Ubuntu 18.04.3 LTS
  libqt5core5a: 5.9.5+dfsg-0ubuntu2.3
  Kernel: 5.0.0-25-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1850681] [NEW] Touchpad and touchsrceen not working

[Frank Lettau]

Public bug reported:

touchpad not working, only usb-mouse is recognized. touchscreen functionality 
not working, but that would be rather less important. Everything else is 
perfectly fine. (18.04 LTS)
TREKSTOR Primebook C11B

Thanks :-)

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.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 30 18:43:32 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:2212]
InstallationDate: Installed on 2019-10-26 (4 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: TREKSTOR Primebook C11B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/03/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.1.2
dmi.board.asset.tag: Default string
dmi.board.name: Apollolake_alk_V01
dmi.board.vendor: TS_weibu
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 31
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring:
dmi.product.family: Notebook
dmi.product.name: Primebook C11B
dmi.product.sku: CFALKWW03
dmi.product.version: Default string
dmi.sys.vendor: TREKSTOR
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

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

Title:
  Touchpad and touchsrceen not working

Status in xorg package in Ubuntu:
  New

Bug description:
  touchpad not working, only usb-mouse is recognized. touchscreen functionality 
not working, but that would be rather less important. Everything else is 
perfectly fine. (18.04 LTS)
  TREKSTOR Primebook C11B

  Thanks :-)

  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.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 18:43:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TREKSTOR Primebook C11B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.1.2
  dmi.board.asset.tag: Default string
  dmi.board.name: Apollolake_alk_V01
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: Primebook C11B
  dmi.product.sku: CFALKWW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  

[Touch-packages] [Bug 1850681] Re: Touchpad and touchsrceen not working

[Frank Lettau]

Thanks again :-)

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

Title:
  Touchpad and touchsrceen not working

Status in xorg package in Ubuntu:
  New

Bug description:
  touchpad not working, only usb-mouse is recognized. touchscreen functionality 
not working, but that would be rather less important. Everything else is 
perfectly fine. (18.04 LTS)
  TREKSTOR Primebook C11B

  Thanks :-)

  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.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 18:43:32 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2019-10-26 (4 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TREKSTOR Primebook C11B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=efc3c4a6-eb3c-4dc1-8a8e-0f53d786817d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.1.2
  dmi.board.asset.tag: Default string
  dmi.board.name: Apollolake_alk_V01
  dmi.board.vendor: TS_weibu
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 31
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.1.2:bd05/03/2018:svnTREKSTOR:pnPrimebookC11B:pvrDefaultstring:rvnTS_weibu:rnApollolake_alk_V01:rvrDefaultstring:cvn:ct31:cvrDefaultstring:
  dmi.product.family: Notebook
  dmi.product.name: Primebook C11B
  dmi.product.sku: CFALKWW03
  dmi.product.version: Default string
  dmi.sys.vendor: TREKSTOR
  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/1850681/+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 1850258] Re: First breakpoint at AVX instruction with memory operand causes SIGSEGV when tring to continue execution

[Pauli]

Another instruction which appears to have issues with memory operands
and breakpoint on the instruction is vpmuludq. This time it didn't crash
but I was looking at completely incorrect multiplication results
compared to incoming values to the instruction. To me this indicates
like vpmuludq read the memory operand from wrong address which happened
to be a mapped address.

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

Title:
  First breakpoint at AVX instruction with memory operand causes SIGSEGV
  when tring to continue execution

Status in gdb package in Ubuntu:
  New

Bug description:
  I noticed random looking SIGSEGV to application when trying to
  continue execution after first breakpoint. I now seem to have narrowed
  the issue to SIMD instruction with memory operand as first breakpoint
  location. I haven't managed to figure out why the SIGSEGV is delivered
  to the debugger application.

  It is important have first breakpoint exactly at a problematic
  instructions. If I first break on a different instruction then later
  breakpoints won't reproduce that crash

  I haven't tested if this is a hardware specific issue.

  I managed to write a simple test case which reproduces the crash if
  breakpoint is set. I attached the test.cc which includes compilation
  and testing instructions. test.cc is supposed to generate a simple
  main function like:

  Dump of assembler code for function main():
  => 0x4520 <+0>:   vmovdqa 0x1af8(%rip),%xmm0# 
0x6020 
     0x4528 <+8>:   vmovd  %xmm0,%eax
     0x452c <+12>:  retq

  I set breakpoint with:
  b main

  Then either continue or stepping causes SIGSEGV to the debugged
  application.

  This was happening already with disco. I only now figured out enough
  details to make a simple test case which is worth a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdb 8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 29 09:44:52 2019
  InstallationDate: Installed on 2037-12-25 (-6632 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdb
  UpgradeStatus: Upgraded to eoan on 2019-10-27 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1850258/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Robie Basak]

Hello Miroslav, or anyone else affected,

Accepted gdb into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdb/8.1-0ubuntu3.2 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: gdb (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  Fix Committed
Status in gdb source package in Disco:
  Invalid
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1850668] [NEW] No conozco el error

[Ismael Vieitez Porto]

Public bug reported:

NO se que le pasa

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CompositorRunning: None
Date: Wed Oct 30 17:33:50 2019
DistUpgraded: 2019-10-23 18:48:24,042 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso 
hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8))
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 430.50, 5.0.0-32-generic, x86_64: installed
 nvidia, 430.50, 5.3.0-19-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:125f]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1261]
InstallationDate: Installed on 2019-08-19 (72 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Acer Aspire A717-72G
ProcEnviron:
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=a2aeaa4e-4f3c-4b06-b9e5-ba7fe9d5ee08 ro acpi_osi=Linux 
acpi_backlight=vendor quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-10-23 (6 days ago)
dmi.bios.date: 10/31/2018
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.22
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Charizard_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.22
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.22
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.22:bd10/31/2018:svnAcer:pnAspireA717-72G:pvrV1.22:rvnCFL:rnCharizard_CFS:rvrV1.22:cvnAcer:ct10:cvrV1.22:
dmi.product.family: Aspire 7
dmi.product.name: Aspire A717-72G
dmi.product.sku: 
dmi.product.version: V1.22
dmi.sys.vendor: Acer
nvidia-settings:
 ERROR: Unable to load info from any available system
 
 
 ERROR: Unable to load info from any available system
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Wed Oct 30 16:11:57 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id4509 
 vendor AUO
xserver.version: 2:1.20.5+git20191008-0ubuntu1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  No conozco el error

Status in xorg package in Ubuntu:
  New

Bug description:
  NO se que le pasa

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Oct 30 17:33:50 2019
  DistUpgraded: 2019-10-23 18:48:24,042 

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Robie Basak]

** Tags added: regression-update

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  Invalid
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Balint Reczey]

Fixed in Focal, to be SRU-d to Eoan.

** Also affects: gnome-shell (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1847896] Re: Unable to shutdown or restart from log-in screen

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: New => Confirmed

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  [Impact]

   * Shutdown and restart options don't work from the login screen, when
  the user is not logged in.

  [Test Case]

   * Start the system and don't log in, or log out in case the system is set up 
with autologin.
   * Restart, then shut down the system using the option in the upper right 
corner of the login screen.
   * Observe both operations working.

  [Regression Potential]

   * The fix is treating treating the greeter as user display sessions
  by cherry-picking upstream's change released in v243. The fix itself
  is very small, but there may be non-obvious security implications.

  [Original Bug Text]

  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1849544] Re: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package initramfs-tools 0.133ubuntu10 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  problem occurred becauuse symlink /initrd.imgpointed to old disco
  initrd, resolved by forcibly recreating it, for now...?

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Oct 21 17:24:50 2019
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-02-20 (610 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to eoan on 2019-10-21 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1849544/+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 1844743] Re: ufw missing .conf for syslog-ng

[Jamie Strandboge]

** Changed in: ufw (Ubuntu)
   Status: New => Triaged

** Changed in: ufw (Ubuntu)
   Importance: Undecided => Medium

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

** Changed in: ufw
   Status: New => Triaged

** Changed in: ufw
   Importance: Undecided => Medium

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

Title:
  ufw missing .conf for syslog-ng

Status in ufw:
  Triaged
Status in ufw package in Ubuntu:
  Triaged

Bug description:
  ufw package contains /etc/rsyslog.d/20-ufw.conf, but no 
/etc/syslog-ng/conf.d/ufw.conf
  distro: any
  ufw: any

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1844743/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Simon Déziel]

I feel really bad now :/

The initial commit that went in doesn't even fix the problem due to a
typo/confusion. The proposed manual workaround was OK but the merge
proposal was not.

 "/usr/sbin/rsyslog mr," != "/usr/sbin/rsyslogd mr,"

I'm failing the verification and have proposed a new MP. Sorry.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-disco
** Tags added: verification-failed verification-failed-bionic 
verification-failed-disco

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Committed
Status in rsyslog source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/374922

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Committed
Status in rsyslog source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1726068] Proposed package upload rejected

[Robie Basak]

An upload of packagekit to disco-proposed has been rejected from the
upload queue for the following reason: "Incomplete SRU information and
no response to requests to fix it".

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

Title:
  debconf socket closes if aptdaemon/PK client exits

Status in apper package in Ubuntu:
  New
Status in aptdaemon package in Ubuntu:
  Fix Released
Status in packagekit package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Invalid
Status in apper source package in Bionic:
  New
Status in aptdaemon source package in Bionic:
  New
Status in packagekit source package in Bionic:
  New
Status in apper source package in Disco:
  New
Status in aptdaemon source package in Disco:
  New
Status in packagekit source package in Disco:
  Incomplete

Bug description:
  [Impact]
  Closing an application using PackageKit or aptdaemon to install packages 
kills the debconf endpoint (because it's a subprocess that's cleaned up), 
causing debconf to use defaults which might lead to wrong results, or even 
cause installations to fail.

  [Solution]
  The solution is to move the end point into a socket-activated systemd unit, 
so that it is independent of the graphical frontend that started the 
transaction. The other advantage is that this offers us restart if the end 
point crashes.

  [Test case]
  1. Install opera deb using packagekit, ensure service is activated
  2. Install opera deb using aptdaemon, ensure service is activated

  Alternatively, you might use another deb that has debconf prompts.

  [Regression potential]
  Systems that do not yet use systemd will fall back to the old method, so 
should not regress.

  Otherwise, if there are bugs, they'd affect the ability to show
  debconf prompts, and behavior would revert to using the defaults.

  There might be some uncertainty if you restart your desktop while the
  helper is running and it does not pick up the new X/Wayland display
  until it restarts (it should fail to connect and restart). Given that
  the helper times out, this should not be an issue in practice, as
  you'd have to logout, login, and start a new install within 60
  seconds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apper/+bug/1726068/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Robie Basak]

Hello Simon, or anyone else affected,

Accepted rsyslog into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/8.32.0-1ubuntu7.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, details of your testing
will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Tags added: block-proposed-bionic block-proposed-disco

** Changed in: rsyslog (Ubuntu Disco)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-disco

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Committed
Status in rsyslog source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage 

[Touch-packages] [Bug 1827253] Please test proposed package

[Robie Basak]

Hello Simon, or anyone else affected,

Accepted rsyslog into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/8.32.0-1ubuntu4.1 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  Fix Committed
Status in rsyslog source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => 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/1845909

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 
'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 
9890, using a commit that does not correctly fix the issue and was never 
accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  
https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845909/+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 1845909] Re: [SRU] IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

[Zhang Youfu]

filed an upstream issue

** Bug watch added: github.com/systemd/systemd/issues #13882
   https://github.com/systemd/systemd/issues/13882

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

** Changed in: systemd
 Remote watch: github.com/systemd/systemd/issues #12886 => 
github.com/systemd/systemd/issues #13882

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

Title:
  [SRU] IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  when a networkd interface is configured with LinkLocalAddressing=no,
  networkd still assigns a link-local address to it

  [test case]

  see comment 3.

  note I was only able to reproduce this at boot time; if the vlan
  interface is removed (i.e. 'sudo ip l del pppoe') and then networkd
  restarted, the pppoe interface is created and does not have a link-
  local address.

  [regression potential]

  this moves the point when ipv6ll is configured; regressions would most
  likely involve failure to correctly configure an ipv6ll address when
  desired.

  [other info]

  this bug was attempted to be fixed by 
'debian/patches/networkd-honour-LinkLocalAddressing.patch' from upstream issue 
9890, using a commit that does not correctly fix the issue and was never 
accepted upstream:
  https://github.com/systemd/systemd/issues/9890#issuecomment-455168751

  this SRU completely reverts that patch, and adds the correct fix which
  was merged upstream:
  
https://github.com/systemd/systemd/commit/0e2fdb83bb5e22047e0c7cc058b415d0e93f02cf

  that commit is already included in Eoan so this sru is needed only for
  Disco.

  original description:

  --

  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1845909/+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 1830865] Re: Integer overflow in bson_ensure_space (bson.c:613)

[Francis Ginther]

** Tags added: id-5d6412d0de485863a95da846

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

Title:
  Integer overflow in bson_ensure_space (bson.c:613)

Status in whoopsie package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu Security Team,

  I would like to report an integer overflow vulnerability in whoopsie.
  In combination with issue 1830858, this vulnerability may enable an
  local attacker to read arbitrary files on the system.

  I have attached a proof-of-concept which triggers the vulnerability. I
  have tested it on an up-to-date Ubuntu 18.04. Run it as follows:

  bunzip2 PoC.tar.bz2
  tar -xf PoC.tar
  cd PoC
  make
  ./killwhoopsie2

  The PoC works by creating a file named
  `/var/crash/killwhoopsie.crash`, just over 2GB in size. It then
  creates a file named `/var/crash/killwhoopsie.upload`, which prompts
  whoopsie to start processing the .crash file.

  This is the source location of the integer overflow bug:

  http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/698/lib/bson/bson.c#L613

  The problem is that the types of pos, bytesNeeded, and b->dataSize are
  all int. My PoC triggers an integer overflow in the calculation of pos
  + bytesNeeded, which causes bson_ensure_space to return immediately on
  line 614 without allocating more space. This leads subsequently to a
  heap buffer overflow on line 738:

  http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/698/lib/bson/bson.c#L738

  Please let me know when you have fixed the vulnerability, so that I
  can coordinate my disclosure with yours. For reference, here is a link
  to Semmle's vulnerability disclosure policy:
  https://lgtm.com/security#disclosure_policy

  Thank you,

  Kevin Backhouse

  Semmle Security Research Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1830865/+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 1830862] Re: Apport reads arbitrary files if ~/.config/apport/settings is a symlink

[Francis Ginther]

** Tags added: id-5db7d829ab21655404d94dff

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

Title:
  Apport reads arbitrary files if ~/.config/apport/settings is a symlink

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu Security Team,

  I would like to report a local denial of service vulnerability in
  Apport. This issue is a variant of issue 1830858, but I believe it is
  less severe because I was only able to use it to trigger a denial of
  service. To trigger the bug:

  mkdir -p ~/.config/apport
  ln -s /dev/zero ~/.config/apport/settings
  gcc segv.c -o segv
  ./segv

  (I have tested these steps on an up-to-date Ubuntu 18.04.)

  Apport will happily follow the symlink, even if it points to a file
  that requires root privileges to read. The reason why it is more
  difficult to exploit than issue 1830858 is that Apport will error out
  if the file is not formatted correctly. But if the symlink points to
  /dev/zero then Apport will keep reading until it uses all the system's
  memory, thereby DOS-ing the machine.

  Please let me know when you have fixed the vulnerability, so that I
  can coordinate my disclosure with yours. For reference, here is a link
  to Semmle's vulnerability disclosure policy:
  https://lgtm.com/security#disclosure_policy

  Thank you,

  Kevin Backhouse

  Semmle Security Research Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1830862/+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 1839414] Re: Apport follows symbolic links in path components when creating core dump file

[Francis Ginther]

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

** Tags added: id-5d640f669cd10e562c3038cf

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

Title:
  Apport follows symbolic links in path components when creating core
  dump file

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  In data/apport, Apport (implicitly) protects against symbolic link
  following for to be created core dump files, but not sufficiently:

  181 core_path = os.path.join(cwd, 'core')
  ...
  186 core_file = os.open(core_path, os.O_WRONLY | os.O_CREAT | 
os.O_EXCL, 0o600)

  When Apport opens (creates, actually) the core dump file in the
  second line, symbolic link following is (implicitly) prevented due to
  the combination of "os.O_CREAT" and "os.O_EXCL".  However, this only
  applies to the final path component of "core_path" (the core dump file
  name of "core"), _not_ for the earlier path components (taken from
  "cwd").  For those path components, no such prevention is explicitly
  applied either.  Thus, symbolic links in path components before "core"
  are followed.  Combined with a different issue of "cwd" being replaced
  after reading out the current working directory but before using the "cwd"
  variable's value, users may be able to replace any path component of the
  "cwd" file system entry with a symbolic link pointing to an arbitrary
  location on the file system.

  This can for example be used to place core dumps in arbitrary (but
  user-writable) directories different than the actual current working
  directory of the crashed process, or even (user-writable) directories
  outside the root directory in case of a chroot()ed crashed process or
  outside of a container / sandbox in case of a containerized / sandboxed
  process (because Apport is ran from the host's root file system, not
  within such environment).

  Proposed fix: make Apport not follow symbolic links in non-last path
  components when writing core dump files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1839414/+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 1839417] Re: Potentially existing (legitimate, root owned) lock file getting deleted by Apport daily cron(8) script

[Francis Ginther]

** Tags added: id-5d640fd329dff226b88f059a

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

Title:
  Potentially existing (legitimate, root owned) lock file getting
  deleted by Apport daily cron(8) script

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  As an unintended side effect of removing old crash reports,
  Apport's etc/cron.daily/apport daily cron(8) job file also deletes
  the /var/crash/.lock file, a lock file which Apport normally creates
  (as root) when it first runs:

4 find /var/crash/. ! -name . -prune -type f \( \( -size 0 -a \!
  -name '*.upload*' -a \! -name '*.drkonqi*' \) -o -mtime +7 \) -exec rm
  -f -- '{}' \;

  The /var/crash/.lock lock file not already existing, i.e., Apport not
  having run yet, is a precondition for a different issue (the issue of
  /var/crash/.lock being fully user controllable due to it being placed
  in a world-writable directory) to get exploited.  However, removing the
  file on a daily basis means that precondition is then met, even if the
  lock file existed beforehand.  This means exploit possibilities for that
  other issue are opened up again on a daily basis, even when a legitimate
  lock file was previously present.

  On a side note: issues might or might not arise in case the lock file
  happens to get deleted during a run of Apport, i.e., when Apport is using
  it or having set a lock on it.  This might or might not especially apply
  in combination with the "30 seconds timeout" code in check_lock().

  Proposed fix: exclude the lock file from being deleted by the daily
  cron(8) job (but note that there may also be other packages cleaning up
  /var/crash/, potentially not excluding the lock file) from being deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1839417/+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 1839420] Re: Per-process user controllable Apport socket file

[Francis Ginther]

** Tags added: id-5d9e45ccd0f15c2eef59e1b0

** Tags added: id-5db7d7dd9955e4200bf58f02

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

Title:
  Per-process user controllable Apport socket file

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  As defined in data/apport, when Apport thinks a crash
  originated in a container it will forward the crash handling to a
  /proc//root/run/apport.socket file, using /proc/ information from
  the crashed process:

  424 if not is_same_ns(host_pid, "pid") and not is_same_ns(host_pid, 
"mnt"):
  425 # If the crash came from a container, don't attempt to handle
  426 # locally as that would just result in wrong system 
information.
  427
  428 # Instead, attempt to find apport inside the container and
  429 # forward the process information there.
  ...
  436 try:
  437 sock.connect('/proc/%d/root/run/apport.socket' % host_pid)

  Normally, a user can't change the root directory of a process since the
  chroot(2) system call can only be used by root / privileged processes.
  This also means only processes set up by the super user may have a
  different root directory, e.g., legitimate LXC containers, and that root
  can trust the value of the root directory.

  However, a user can create a user namespace using unshare(2), define
  itself root in it, and then in fact be able to use chroot(2).  Then,
  /proc//root/ for that process can lead anywhere.  Thus, the root
  directory should not be trusted by Apport, since it is user controllable,
  meaning the /root/run/apport.socket path can't be trusted either to
  be in fact an actual, legitimate Apport socket file within an actual,
  legitimate container.

  The same applies to the /run/ directory within the root directory of the
  process, even when not using chroot(2): the user can define a /run mount
  point within a user namespace when combined with unsharing the mount
  namespace (actually equal to what is the case with an actual container
  OS), and Apport on the host OS would access that in-namespace mount
  point via /proc//root/run/.

  Thus, both /proc//root/ and /proc//root/run/ are
  user-controllable, and neither can be trusted by Apport.

  Example of manipulating the root directory via a user namespace:

 user@ubuntu$ chroot /bin/ ./busybox sleep 100 # normal situation, 
chroot(2) not permitted
 chroot: cannot change root directory to '/bin/': Operation not permitted

 user@ubuntu$ unshare -Ufmpr chroot /bin/ ./busybox sleep 100 # this
  works

 root@ubuntu# readlink /proc/$(pgrep busybox)/root
 /bin

  Example of manipulating /run/ via a user namespace (the two command
  lines are started simultaneously):

 user@ubuntu$ echo 'sleep 5; mount -t tmpfs tmpfs /run; touch
  /run/apport.socket; sleep 5' | unshare -Ufmpr sh

 root@ubuntu# sleep 2; ls /proc/$(pgrep unshare)/root/run/apport.socket; 
sleep 5; ls /proc/$(pgrep unshare)/root/run/apport.socket
 ls: cannot access '/proc/6118/root/run/apport.socket': No such file or 
directory
 /proc/6118/root/run/apport.socket

  Thus, per-process, the user controls the socket file (via two separate
  path locations, as shown above).

  This can for example be abused to "catch" a core dump of a "tainted"
  process: for such process a "core" core dump file is normally not
  written, and the crash report file in /var/crash/ is created as root.
  This makes a user unable to read such core dump, which is intended for
  security since it might contain privileged contents.  However, using
  the methods above the apport.socket file is user controllable and may
  for example be an (altered) Apport systemd socket file registered to a
  "systemd --user" user initiated systemd process, so that the host Apport
  instance can still communicate properly with the socket.  Such altered
  and user controlled apport.socket file may then for example save the
  core dump in a file owned by the user effectively making a tainted,
  "privileged" core dump user readable to the user (instead of just to
  root) and thus defeating the intention of "fs.suid_dumpable=2" dumping a
  "tainted" core dump non-readable to the user, as root.  Due to things
  happening in a root user namespace this might be difficult to exploit
  for a setuid process, but it it easily doable for non-readable binaries,
  as those also fall under the category of "tainted" core dumps.

  As a different exploit example, the /proc//root/run/apport.socket
  file may be created as a symbolic link pointing to an arbitrary file
  (which could even point to a destination outside the unshared namespace),
  for example an actual socket file, enabling other damage / 

[Touch-packages] [Bug 1839415] Re: Fully user controllable lock file due to lock file being located in world-writable directory

[Francis Ginther]

** Tags added: id-5d640fd329dff226b88f059a

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

Title:
  Fully user controllable lock file due to lock file being located in
  world-writable directory

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  In data/apport, Apport creates a lock file:

   35 # create a lock file
   36 lockfile = os.path.join(apport.fileutils.report_dir, '.lock')
   37 try:
   38 fd = os.open(lockfile, os.O_WRONLY | os.O_CREAT | 
os.O_NOFOLLOW)

  The value of "apport.fileutils.report_dir" is /var/crash/, which is a
  world-writable (but sticky) directory.

  Placing the lock file in a world-writable directory as done here
  effectively makes the lock file fully controllable by any user, at least
  as long as the lock file does not already exist, i.e., in case Apport has
  not been executed before (but a different issue exists which completely
  defeats this precondition).

  This issue can be exploited in several ways, with various impacts.

  Probably being its most severe impact, a simple shell one-liner like
  the following will lead to a complete system DoS, i.e., DoS on the OS
  resource level (e.g., memory):

 $ mkfifo /var/crash/.lock && while sleep 100 & do sleep 1; kill -11
  "$!"; kill -9 "$!"; done

  This will make the os.open() in data/apport stall forever due to the FIFO
  file, as well as create more than one and up to an indefinite amount of
  (root owned) Apport processes due to the failing of the locking mechanism,
  which should normally prevent subsequent Apport processes from running,
  because the lock is not yet set at that point.  The "kill -9" prevents
  the user from hitting its "RLIMIT_NPROC" limit, and "RLIMIT_CORE" itself
  does not apply to the root user.

  The locking mechanism failing when using a FIFO file, i.e., circumventing
  the locking mechanism thus making it possible to run more than one
  Apport process at the same time (even when they are in a stalled state)
  is an impact on its own, not just in the OS DoS scenario in which it is
  abused up to the point creating many Apport instances ultimately leading
  to OS DoS.

  Also, the issue in the first place leads to DoS for Apport both for
  individual instances as well as it as a service as a whole, i.e., making
  Apport unable to function, as one user could create a /var/crash/.lock
  FIFO file and prevent Apport from doing its work in case of program
  crashes of other users.

  This issue when used with a FIFO file can also be abused to "time"
  Apport, i.e., let Apport stall for some period of time (and do whatever
  is needed to control the further flow of Apport during that time, e.g.,
  as part of a larger exploit scenario) and have it continue at a specific,
  user defined moment by then reading out the FIFO file.

  As a different method of exploitation of this issue, a user can simply
  create /var/crash/.lock (as a regular file) and put an indefinite lock
  on it, thereby preventing Apport from succesfully doing its work, again
  leading to service DoS for Apport.  Apport DoS could also be achieved by
  for example creating /var/crash/.lock as a directory or as a socket file,
  meaning Apport can't os.open() /var/crash/.lock as a file, again making
  Apport fail (i.e., service DoS).

  The above scenarios prevent legitimate Apport processes from creating,
  opening and / or locking the lock file, leading to DoS for both invidual
  Apport instances as well as Apport as a whole, i.e., service DoS.

  Note that the impact of this issue might be even worse on systems without
  sysctl(8)'s "fs.protected_symlinks=1" set, which in default installations
  provides effective protection due to /var/crash/ being a sticky directory,
  or without "fs.protected_hardlinks=1" being set.

  Also note that, besides all of the impacts above due to /var/crash/
  being world-writable, /var/crash/ isn't a logical location to place a
  lock file to begin with; using a more appropriate location like /var/lock/
  would make more sense, and is also the proposed fix for this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1839415/+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 1839413] Re: TOCTTOU ("time of check to time of use") "cwd" variable race condition

[Francis Ginther]

** Tags added: id-5d640ed806b8601dd0ea00ab

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

Title:
  TOCTTOU ("time of check to time of use") "cwd" variable race condition

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  In data/apport, Apport reads out the current working directory of a
  crashed process in get_pid_info() and puts it into the "cwd" variable:

   83 cwd = os.readlink('/proc/' + pid + '/cwd')

  Later, this variable gets used in calls to write_user_coredump() for
  writing the core dump file:

  181 core_path = os.path.join(cwd, 'core')

  The time between setting the "cwd" variable and using the variable forms
  a TOCTTOU issue, and can be abused by a user to create a core dump file
  in a different directory than the actual current working directory of
  the crashed process (being Apport's intended destination directory for
  the core dump file).  This can for example be abused replacing (any path
  component of) the directory to which "cwd" points with a FUSE bindfs(1)
  or similar file system mount point, or by a symbolic link to an arbitrary
  (and potentially root owned) directory.

  Moreover, when using FUSE, basically "anything" could be put behind the
  "mount point" leading to various potential exploitation scenarios, e.g.,
  an indefinite sleep() would lead to (some form of) DoS for Apport.

  Proposed fix: if possible, use a file descriptor for handling "cwd".

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1839413/+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 1839418] Re: Partially user controllable lock file due to incorrect, too broad permissions

[Francis Ginther]

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

** Tags added: id-5d640fd329dff226b88f059a

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

Title:
  Partially user controllable lock file due to incorrect, too broad
  permissions

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  Apport creates its lock file, /var/crash/.lock, without providing a
  file permission mode.  Thus, the file gets created with file permission
  mode 777.  Users can exploit this, leading to system storage resource
  DoS issues (either for mount point "/", or for a potentialy separate
  "/var" mount point) as well as Apport service DoS.

  Users can thus fill up disks / partitions (although probably not including
  the root reserved blocks: even though the file is root owned, the process
  writing to the file would be started by the user, not by root, thus
  the reserved blocks can probably not be used up).  Also, the user may
  "hide" data in the file, as well as circumvent a potentially existing
  disk quota set on their account.  Also, a user putting a lock on the
  file leads to DoS on Apport, both individual Apport instances as well
  as Apport as a service, as new Apport instances are not able to acquire
  the lock and can thus not run.  In addition, the file being executable
  could have separate security implication on itself.

  Note: this issue does not appear on all Ubuntu releases, and / or not when
  Ubuntu is installed in an LXC container.  This might be due to differences
  in the kernel version, differences in the Python version or perhaps
  because Ubuntu 14.04 ESM, on which the file gets mode 660 for example,
  does not have systemd.  More specifically, the issue is probably due to
  Apport being called by the kernel via sysctl(8)'s "kernel.core_pattern"
  and the kernel not having applied an umask, combined with Python not
  creating regular files with "a-x" (as shells do).  Also, in the LXC case,
  Apport in an LXC container gets called by Apport on the host OS, which
  is a "plain" root owned process to which the umask then _does_ apply.

  In any case Apport should simply set the correct permissions itself
  (probably permission mode 600), which is also the proposed fix for
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1839418/+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 1850635] [NEW] Some applications don't redraw their windows correctly

[Aaron A Aardvark]

Public bug reported:

After updating from 19.04 to 19.10 I noted that some apps don't redraw
their window(s) correctly.  Affected apps include (it seems) all Qt-
based apps (including KDE and VirtualBox), as well as
firefox/thunderbird.

Unaffected apps include emacs, chrome, xterm.

The symptom is that an affected app will only redraw its window when
another X window redraws its window.  If there is no other window, then
the app's window is not redrawn at all.

This is best illustrated with a video, which shows the problem using
konsole and kpat (both KDE apps) :-

https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA

I am using the intel graphics driver (no graphics card).

Other info as requested below :-

$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

$ apt-cache policy xserver-xorg
xserver-xorg:
  Installed: 1:7.7+19ubuntu12
  Candidate: 1:7.7+19ubuntu12
  Version table:
 *** 1:7.7+19ubuntu12 500
500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Oct 30 11:50:09 2019
DistUpgraded: 2019-10-21 13:25:02,550 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd HD Graphics 530 [1458:d000]
InstallationDate: Installed on 2016-01-02 (1396 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=8af2cd02-0009-4ce5-9ec6-e6cdf44c9411 ro nopti
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-10-21 (8 days ago)
dmi.bios.date: 07/23/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z170X-Gaming 5
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 #enabled=1
 enabled=0
mtime.conffile..etc.default.apport: 2016-01-06T17:10:43.876145
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan ubuntu

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

Title:
  Some applications don't redraw their windows correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  After updating from 19.04 to 19.10 I noted that some apps don't redraw
  their window(s) correctly.  Affected apps include (it seems) all Qt-
  based apps (including KDE and VirtualBox), as well as
  firefox/thunderbird.

  Unaffected apps include emacs, chrome, xterm.

  The symptom is that an affected app will only redraw its window when
  another X window redraws its window.  If there is no other window,
  then the app's window is not redrawn at all.

  This is best illustrated with a video, which shows the problem using
  konsole and kpat (both KDE apps) :-

  https://photos.app.goo.gl/hd7UtTt2k6Pn9GBLA

  I am using the intel graphics driver (no graphics card).

  Other info as requested below :-

  $ lsb_release 

[Touch-packages] [Bug 1839795] Re: PID recycling enables an unprivileged user to generate and read a crash report for a privileged process

[Francis Ginther]

** Tags added: id-5db7d98b9aa43003f76d70d0

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

Title:
  PID recycling enables an unprivileged user to generate and read a
  crash report for a privileged process

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Dear Ubuntu Security Team,

  I would like to report a vulnerability in Apport, which enables an
  unprivileged user to read important information about a privileged
  process.

  From an attacker's point of view, the main value of the vulnerability
  is that it enables them to obtain the ASLR offsets for a privileged
  process, provided that they have the ability to deliberately crash the
  privileged process. This is very useful for an attacker if they have
  discovered a memory corruption vulnerability in a privileged service.
  It is often very difficult to obtain code execution from a memory
  corruption vulnerability unless you have access to the ASLR offsets.
  But it is usually very easy to trigger a crash by corrupting the
  memory with random data. The vulnerability in Apport enables the
  attacker to obtain the ASLR offsets for the service after it is has
  restarted due to an attacker-controlled crash.

  I have attached an exploit proof of concept which demonstrates the
  vulnerability on the whoopsie process. As you know, whoopsie has a
  memory corruption vulnerability which is currently still unfixed:
  1830865. The vulnerability in whoopsie is very difficult to exploit
  without knowing the ASLR offsets. But it is easy for an unprivileged
  user to cause whoopsie to crash. The PoC uses this to deliberately
  crash whoopsie and obtain ASLR offsets for the new whoopsie after it
  has been restarted automatically by systemd.

  To run the PoC:

  gunzip Apport_PoC.tar.gz
  tar -xf Apport_PoC.tar
  cd Apport_PoC/
  make
  ./restart_whoopsie init 10

  The PoC is slightly non-deterministic, so it might take several tries
  before it succeeds. (It will print messages to tell you what is going
  on while it is running.) When it succeeds, Apport will create a file
  named something like this:

  /var/crash/_usr_bin_whoopsie.1001.crash

  If you run apport-unpack on that crash report then you will see that
  it contains the ProcMaps file for the currently running whoopsie.

  The source of the problem is here:

  
https://git.launchpad.net/ubuntu/+source/apport/tree/data/apport?h=applied/ubuntu
  /bionic-devel=20c98691144e843bf1ab8428603beedd34e993ad#n452

  Apport determines which user the crashed process belongs to by reading
  the contents of /proc/[pid]. But pids can get recycled. The exploit
  works by pausing Apport while it is in the middle of generating a
  crash report and then sending a SIGKILL to the crashed process so that
  its pid gets recycled. When Apport resumes, it starts generating a
  crash report for a new process which has been assigned the same pid as
  the crashed process.

  I am happy to help out if you would like to discuss what the best
  solution is for this vulnerability. I have some ideas, but they might
  be naive. This is a very tricky area of the code and I am sure that I
  am not yet aware of all the subtle reasons why it is currently written
  the way it is.

  Please let me know when you have fixed the vulnerability, so that I
  can coordinate my disclosure with yours. For reference, here is a link
  to Semmle's vulnerability disclosure policy:
  https://lgtm.com/security#disclosure_policy

  Thank you,

  Kevin Backhouse

  Semmle Security Research Team

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1839795/+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 1794640] Re: package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  This bug shows up when install gparted

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_22_24_generic_42
  ApportLog:
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: called for pid 2019, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: executable: 
/usr/sbin/gpartedbin (command line "/usr/sbin/gpartedbin")
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
   ERROR: apport (pid 2101) Thu Sep 27 08:53:22 2018: apport: report 
/var/crash/_usr_sbin_gpartedbin.0.crash already exists and unseen, doing 
nothing to avoid disk usage DoS
  ApportVersion: 2.20.9-0ubuntu7.3
  AptOrdering:
   cups-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CrashReports:
   600:0:117:63803:2018-09-27 08:20:48.565904617 +0700:2018-09-27 
08:20:49.565904617 +0700:/var/crash/apport.0.crash
   640:0:117:1694840:2018-09-26 17:10:45.873321080 +0700:2018-09-26 
17:10:43.941266328 +0700:/var/crash/_usr_sbin_gpartedbin.0.crash
  Date: Thu Sep 27 08:20:49 2018
  DpkgHistoryLog:
   Start-Date: 2018-09-27  08:20:47
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: cups-common:amd64 (2.2.7-1ubuntu2, 2.2.7-1ubuntu2.1)
  DuplicateSignature:
   package:apport:2.20.9-0ubuntu7.3
   Setting up cups-common (2.2.7-1ubuntu2.1) ...
   dpkg: error processing package apport (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-05-09 (141 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: apport
  Title: package apport 2.20.9-0ubuntu7.3 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1794640/+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 1849856] Re: ip commands error with mellanox devices in switchdev mode

[James Page]

FWIW same is seem with the 5.3.0 kernel that's just appeared in HWE
edge.

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

Title:
  ip commands error with mellanox devices in switchdev mode

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel: using 5.0.0-23-generic from hwe-edge

  Configuring a mellanox connectx device with configured VF's into
  switchdev (rather than legacy) mode result in the ip cli tool erroring
  when trying to query the interface state:

  $ sudo ip link
  Error: Buffer too small for object.
  Dump terminated

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: iproute2 4.15.0-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Fri Oct 25 14:55:36 2019
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: iproute2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+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 1839420] Re: Per-process user controllable Apport socket file

[Alex Murray]

** Description changed:

  Author: Sander Bos, 
  
  Date: 2019-07-30
  
  
  As defined in data/apport, when Apport thinks a crash
  originated in a container it will forward the crash handling to a
  /proc//root/run/apport.socket file, using /proc/ information from
  the crashed process:
  
  424 if not is_same_ns(host_pid, "pid") and not is_same_ns(host_pid, 
"mnt"):
  425 # If the crash came from a container, don't attempt to handle
  426 # locally as that would just result in wrong system 
information.
  427
  428 # Instead, attempt to find apport inside the container and
  429 # forward the process information there.
  ...
  436 try:
  437 sock.connect('/proc/%d/root/run/apport.socket' % host_pid)
  
  Normally, a user can't change the root directory of a process since the
  chroot(2) system call can only be used by root / privileged processes.
  This also means only processes set up by the super user may have a
  different root directory, e.g., legitimate LXC containers, and that root
  can trust the value of the root directory.
  
  However, a user can create a user namespace using unshare(2), define
  itself root in it, and then in fact be able to use chroot(2).  Then,
  /proc//root/ for that process can lead anywhere.  Thus, the root
  directory should not be trusted by Apport, since it is user controllable,
  meaning the /root/run/apport.socket path can't be trusted either to
  be in fact an actual, legitimate Apport socket file within an actual,
  legitimate container.
  
  The same applies to the /run/ directory within the root directory of the
- process, even when the user did not use chroot(2), as the user can define
- a /run/ mount point within a user namespace when combined with unsharing
- the mount namespace (and due to the fact that the /run/ directory gets
- accessed by Apport via /proc/ instead of via an actual file system
- path, making it "see" such in-namespace mount point).  Thus, not only
- /proc//root/ is user-controllable, but also /proc//root/run/,
- and neither can be trusted.
+ process, even when not using chroot(2): the user can define a /run mount
+ point within a user namespace when combined with unsharing the mount
+ namespace (actually equal to what is the case with an actual container
+ OS), and Apport on the host OS would access that in-namespace mount
+ point via /proc//root/run/.
+ 
+ Thus, both /proc//root/ and /proc//root/run/ are
+ user-controllable, and neither can be trusted by Apport.
  
  Example of manipulating the root directory via a user namespace:
  
 user@ubuntu$ chroot /bin/ ./busybox sleep 100 # normal situation, 
chroot(2) not permitted
 chroot: cannot change root directory to '/bin/': Operation not permitted
-user@ubuntu$ unshare -Ufmpr chroot /bin/ ./busybox sleep 100 # this works
+ 
+user@ubuntu$ unshare -Ufmpr chroot /bin/ ./busybox sleep 100 # this
+ works
  
 root@ubuntu# readlink /proc/$(pgrep busybox)/root
 /bin
  
  Example of manipulating /run/ via a user namespace (the two command
  lines are started simultaneously):
  
 user@ubuntu$ echo 'sleep 5; mount -t tmpfs tmpfs /run; touch
  /run/apport.socket; sleep 5' | unshare -Ufmpr sh
  
 root@ubuntu# sleep 2; ls /proc/$(pgrep unshare)/root/run/apport.socket; 
sleep 5; ls /proc/$(pgrep unshare)/root/run/apport.socket
 ls: cannot access '/proc/6118/root/run/apport.socket': No such file or 
directory
 /proc/6118/root/run/apport.socket
  
  Thus, per-process, the user controls the socket file (via two separate
  path locations, as shown above).
  
  This can for example be abused to "catch" a core dump of a "tainted"
  process: for such process a "core" core dump file is normally not
  written, and the crash report file in /var/crash/ is created as root.
  This makes a user unable to read such core dump, which is intended for
  security since it might contain privileged contents.  However, using
  the methods above the apport.socket file is user controllable and may
  for example be an (altered) Apport systemd socket file registered to a
  "systemd --user" user initiated systemd process, so that the host Apport
  instance can still communicate properly with the socket.  Such altered
  and user controlled apport.socket file may then for example save the
  core dump in a file owned by the user effectively making a tainted,
  "privileged" core dump user readable to the user (instead of just to
  root) and thus defeating the intention of "fs.suid_dumpable=2" dumping a
  "tainted" core dump non-readable to the user, as root.  Due to things
  happening in a root user namespace this might be difficult to exploit
  for a setuid process, but it it easily doable for non-readable binaries,
  as those also fall under the category of "tainted" core dumps.
  
- Moreover, the apport.socket file may be created as a symbolic
- link pointing to an arbitrary 

[Touch-packages] [Bug 1839414] Re: Apport follows symbolic links in path components when creating core dump file

[Alex Murray]

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

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1839414

Title:
  Apport follows symbolic links in path components when creating core
  dump file

Status in Apport:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  Author: Sander Bos, 

  Date: 2019-07-30

  
  In data/apport, Apport (implicitly) protects against symbolic link
  following for to be created core dump files, but not sufficiently:

  181 core_path = os.path.join(cwd, 'core')
  ...
  186 core_file = os.open(core_path, os.O_WRONLY | os.O_CREAT | 
os.O_EXCL, 0o600)

  When Apport opens (creates, actually) the core dump file in the
  second line, symbolic link following is (implicitly) prevented due to
  the combination of "os.O_CREAT" and "os.O_EXCL".  However, this only
  applies to the final path component of "core_path" (the core dump file
  name of "core"), _not_ for the earlier path components (taken from
  "cwd").  For those path components, no such prevention is explicitly
  applied either.  Thus, symbolic links in path components before "core"
  are followed.  Combined with a different issue of "cwd" being replaced
  after reading out the current working directory but before using the "cwd"
  variable's value, users may be able to replace any path component of the
  "cwd" file system entry with a symbolic link pointing to an arbitrary
  location on the file system.

  This can for example be used to place core dumps in arbitrary (but
  user-writable) directories different than the actual current working
  directory of the crashed process, or even (user-writable) directories
  outside the root directory in case of a chroot()ed crashed process or
  outside of a container / sandbox in case of a containerized / sandboxed
  process (because Apport is ran from the host's root file system, not
  within such environment).

  Proposed fix: make Apport not follow symbolic links in non-last path
  components when writing core dump files.

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