[Touch-packages] [Bug 1886330] Re: pulseaudio not working in Virtualbox

2020-07-06 Thread BertN45
Pulseaudio was running, but the music did not start. It stayed in the
initial position. I have the impression that Firefox creates the
problem. The music in quodlibet played. I stopped it and I started
Firefox to play a music video from youtube, it did not play. Afterwards
quodlibet stopped playing music also.

Remember I only have the problem with Xubuntu and with none of the other
Ubuntu flavors.

I attached the journal.txt file.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886330/+attachment/5390061/+files/journal.txt

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

Title:
  pulseaudio not working in Virtualbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I run my "work" VMs and in Xubuntu pulse audio often does not start.
  In this dump I tried to start music through Firefox and through my
  media player quodlibet and none of the audio starts.

  See attachment with the pulseaudio volume control and quodlibet stuck
  on time 0:00 like Firefox.

  I do not have the problem with plain Ubuntu, Ubuntu Mate nor with
  Ubuntu Studio.

  The problem is annoying, because I use Xubuntu for office and
  communication like Email and the WhatsApp/Firefox/ICE combination and
  with this bug WhatsApp is useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1490 F pulseaudio
   /dev/snd/pcmC0D0c:   bertadmin   1490 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1490 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1490 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jul  5 11:33:48 2020
  InstallationDate: Installed on 2018-03-11 (847 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1886330] Re: pulseaudio not working in Virtualbox

2020-07-06 Thread Daniel van Vugt
I can see a few issues in the log from your VM:

1. Buggy audio in the VM's kernel driver (says pulseaudio):

jul 05 11:05:21 VM-Xubuntu-2004 pulseaudio[1406]: ALSA woke us up to write new 
data to the device, but there was actually nothing to write.
jul 05 11:05:21 VM-Xubuntu-2004 pulseaudio[1406]: Most likely this is a bug in 
the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA 
developers.
jul 05 11:05:21 VM-Xubuntu-2004 pulseaudio[1406]: We were woken up with POLLOUT 
set -- however a subsequent snd_pcm_avail() returned 0 or another value < 
min_avail.
jul 05 11:05:21 VM-Xubuntu-2004 pulseaudio[1406]: Disabling timer-based 
scheduling because running inside a VM.

2. More problems with the VM's kernel driver:

jul 05 11:05:28 VM-Xubuntu-2004 pulseaudio[1406]: Unable to set sw params: 
Permission denied
jul 05 11:05:28 VM-Xubuntu-2004 pulseaudio[1406]: Failed to set software 
parameters: Permission denied
jul 05 11:05:28 VM-Xubuntu-2004 pulseaudio[1406]: Error opening PCM device 
front:0: No such file or directory
jul 05 11:05:28 VM-Xubuntu-2004 systemd[1399]: pulseaudio.service: Succeeded.

3. A couple of kernel crashes apparently relating to running out of
memory in the VM.

So I suggest:

  * Giving the VM more memory.
  * Running fewer apps in the VM.
  * Configuring the VM with a different type of virtual audio device (if you 
can).


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

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

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

Title:
  pulseaudio not working in Virtualbox

Status in linux package in Ubuntu:
  New

Bug description:
  I run my "work" VMs and in Xubuntu pulse audio often does not start.
  In this dump I tried to start music through Firefox and through my
  media player quodlibet and none of the audio starts.

  See attachment with the pulseaudio volume control and quodlibet stuck
  on time 0:00 like Firefox.

  I do not have the problem with plain Ubuntu, Ubuntu Mate nor with
  Ubuntu Studio.

  The problem is annoying, because I use Xubuntu for office and
  communication like Email and the WhatsApp/Firefox/ICE combination and
  with this bug WhatsApp is useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1490 F pulseaudio
   /dev/snd/pcmC0D0c:   bertadmin   1490 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1490 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1490 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jul  5 11:33:48 2020
  InstallationDate: Installed on 2018-03-11 (847 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-06 Thread Noctis Bennington
** Description changed:

  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.
  
  I tried with nouveau drivers and I have the same results btw.
  
  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300
  
  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.
  
  I have this with xrandr:
  
  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)
+ 
+ PD: When you select a specific resolution, the second monitor "works",
+ but it blinks, the image showed via HDMI on the second monitor blinks.
+ So is impossible to work with it. Since all this time I was searching
+ about this and I'm almost sure this is a problem of the GPU's Intel. But
+ I saw this problem on askubuntu just with laptops with hybrid graphics.
+ Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if
+ they have the same problem here).

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that 

[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

2020-07-06 Thread Alex Murray
Ok, since I can't reproduce this locally, if you are interested / able
to help with debugging it, could you please attach the core dump. Or if
this contains potentially sensitive details, you could install the dbg
versions of the packages and reproduce the crash and this would provide
a more complete stack trace.

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

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

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1886330] Re: pulseaudio not working in Virtualbox

2020-07-06 Thread Daniel van Vugt
The main reason why PulseAudio exists is so that multiple apps can play
sounds simultaneously, without having to stop and restart each app to
get access to the audio hardware in turn. So I don't think having two
windows open should be a problem.

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

Title:
  pulseaudio not working in Virtualbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I run my "work" VMs and in Xubuntu pulse audio often does not start.
  In this dump I tried to start music through Firefox and through my
  media player quodlibet and none of the audio starts.

  See attachment with the pulseaudio volume control and quodlibet stuck
  on time 0:00 like Firefox.

  I do not have the problem with plain Ubuntu, Ubuntu Mate nor with
  Ubuntu Studio.

  The problem is annoying, because I use Xubuntu for office and
  communication like Email and the WhatsApp/Firefox/ICE combination and
  with this bug WhatsApp is useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1490 F pulseaudio
   /dev/snd/pcmC0D0c:   bertadmin   1490 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1490 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1490 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jul  5 11:33:48 2020
  InstallationDate: Installed on 2018-03-11 (847 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 608894] Re: dash does not handle ^C trap the same way that bash does

2020-07-06 Thread Jarno Suni
I do not know any other shell than Bash that would run EXIT trap on
signal that has its default action.

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

Title:
  dash does not handle ^C trap the same way that bash does

Status in dash package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: dash

  The problems with making /bin/sh symlink to dash instead of bash are
  known (#141481), but I haven't seen this particular problem reported
  yet.

  dash and bash process the ^C (INT) signal differently.  Try running
  the following script (then type ^C) with both bash and dash:

  <<<
  tint() { echo int; }
  thup() { echo hup; }
  tchld() { echo chld; }
  tterm() { echo term; }
  texit() { echo exit; }

  # trap tint INT
  trap thup HUP
  trap tchld CHLD
  trap tterm TERM
  trap texit EXIT

  echo type ^C...
  sleep 100
  >>>

  bash triggers the EXIT.  dash triggers no trap.

  If you uncomment the INT trap, bash triggers INT and EXIT, and dash
  triggers INT, CHLD, and EXIT.

  I don't know what POSIX dictates or which is correct, I am guessing
  that any exit should trigger EXIT (so dash is wrong).

  Either way, the shells behave differently, and the difference is
  causing problems in existing Ubuntu scripts.  (I found it in /usr/bin
  /xeno-test.)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: dash 0.5.5.1-3ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  Architecture: i386
  Date: Thu Jul 22 15:12:27 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash

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

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


[Touch-packages] [Bug 1886330] Re: pulseaudio not working in Virtualbox

2020-07-06 Thread BertN45
Note that I run Firefox twice in two different windows. One window is
for the WhatsApp website, the other windows is for youtube. This is the
ONLY system, where I use two windows of Firefox both potentially using
pulseaudio. The WhatsApp windows has used or tried to use pulseaudio in
the past.

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

Title:
  pulseaudio not working in Virtualbox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I run my "work" VMs and in Xubuntu pulse audio often does not start.
  In this dump I tried to start music through Firefox and through my
  media player quodlibet and none of the audio starts.

  See attachment with the pulseaudio volume control and quodlibet stuck
  on time 0:00 like Firefox.

  I do not have the problem with plain Ubuntu, Ubuntu Mate nor with
  Ubuntu Studio.

  The problem is annoying, because I use Xubuntu for office and
  communication like Email and the WhatsApp/Firefox/ICE combination and
  with this bug WhatsApp is useless.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   1490 F pulseaudio
   /dev/snd/pcmC0D0c:   bertadmin   1490 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   1490 F...m pulseaudio
   /dev/snd/timer:  bertadmin   1490 f pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Jul  5 11:33:48 2020
  InstallationDate: Installed on 2018-03-11 (847 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Touch-packages] [Bug 892317] Re: set -e reverses order of signal handlers

2020-07-06 Thread Jarno Suni
The behavior seems to have changed in later version. I tested dash 0.5.10.2-6.
There EXIT trap is not run at all, if -e is used, and you use Ctrl-C. But if 
you remove the 'exit 2' from the signal trap, EXIT trap will be run regardless 
of -e setting, when you press Ctrl-C. That is not intuitive. So I think EXIT 
trap should be run even in case of -e. However, if you do not need custom exit 
status for the signal trap, you could just remove the exit builtin.

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

Title:
  set -e reverses order of signal handlers

Status in dash:
  New
Status in dash package in Ubuntu:
  New

Bug description:
  When `-e` is not specified, an INT signal handler runs before an EXIT
  signal handler; when -e is specified, the EXIT signal handler is run
  (but only one of its statements) and then the INT signal handler is
  run.

  :;  /bin/dash < ./trap.sh 
  ^Ctrapped: SIG_
  trapped: EXIT 2
  next part
  :;  /bin/dash -e < ./trap.sh 
  ^Ctrapped: EXIT 130
  trapped: SIG_

  With `bash --posix` or `busybox sh`, the order of signal handlers is
  the same no matter whether `-e` is specified or no. Please see the
  attached script, `trap.sh`.

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

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


[Touch-packages] [Bug 892317] Re: set -e reverses order of signal handlers

2020-07-06 Thread Jarno Suni
If you can confirm, please update the report.

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

Title:
  set -e reverses order of signal handlers

Status in dash:
  New
Status in dash package in Ubuntu:
  New

Bug description:
  When `-e` is not specified, an INT signal handler runs before an EXIT
  signal handler; when -e is specified, the EXIT signal handler is run
  (but only one of its statements) and then the INT signal handler is
  run.

  :;  /bin/dash < ./trap.sh 
  ^Ctrapped: SIG_
  trapped: EXIT 2
  next part
  :;  /bin/dash -e < ./trap.sh 
  ^Ctrapped: EXIT 130
  trapped: SIG_

  With `bash --posix` or `busybox sh`, the order of signal handlers is
  the same no matter whether `-e` is specified or no. Please see the
  attached script, `trap.sh`.

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

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


[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

2020-07-06 Thread arno
What command beside mpv/Celluloid are suffered at your side?

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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


[Touch-packages] [Bug 673119] Re: dash "set -e" breaks "trap action INT"

2020-07-06 Thread Jarno Suni
Output by dash 0.5.10.2-6:
3
^CIgnored 1
Ignored 2
Back
EXIT

bash 5.0.3 works the same way.

To get the output you want, you can use the following code:
--
#!/bin/sh
#set -e

trap '' INT
trap 'echo EXIT' EXIT

sorry() {
  echo "Ignored 1"; echo "Ignored 2"
  sleep 1
  echo Back
}

for i in 3 2 1; do
echo "$i"
(
trap 'sorry; exit 0' INT
sleep 1
) # || :
done

echo OUT
-

If you use bash, instead of dash, it would work even if "set -e" was
used and "trap '' INT" was not used. If "set -e" was used with dash, you
would have to uncomment "|| :" to make it work.

See also Bug #892317

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

Title:
  dash "set -e" breaks "trap action INT"

Status in dash package in Ubuntu:
  New

Bug description:
  Binary package hint: dash

  With set -e, dash executes only the first command of an INT (Ctrl-C)
  trap handler:

  #!/bin/sh
  set -e

  trap 'sorry' INT
  trap 'echo EXIT' EXIT

  zero() {
return 0;
  }

  sorry() {
#zero
echo "Ignored 1"; echo "Ignored 2"
sleep 1
echo Back
  }

  for i in 3 2 1; do
  echo "$i"
  sleep 1 # || true
  done

  echo OUT

  Actual result:

  $ ./x  # Press ^C right away
  3
  ^CIgnored 1
  EXIT

  Expected result:

  3
  ^CIgnored 1
  Ignored 2
  Back
  2
  1
  OUT
  EXIT

  By un-commenting the call to function zero, or the "|| true" in the
  main loop, the problem disapears.

  Bash also exits prematurely, but at least it runs the "trap INT"
  handler code to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: dash 0.5.5.1-3ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Tue Nov  9 19:12:41 2010
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash

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

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


[Touch-packages] [Bug 1883694] Re: [SRU] New upstream release 2.64.3

2020-07-06 Thread Iain Lane
I've retried them all and it's green now.

Just verified this SRU in a VM. I upgraded to the proposed glib2.0 and
then tried logging in and launching and using various GNOME
applications.

  - gedit
  - epiphany-browser (to test glib-networking & webkit)
  - totem (GStreamer)

All seems good to me.

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

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

Title:
  [SRU] New upstream release 2.64.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  +glib2.0 (2.64.3-1~ubuntu20.04.1) UNRELEASED; urgency=medium
  +
  +  * No-change backport from unstable / groovy to focal.
  +
  + -- Iain Lane   Tue, 16 Jun 2020 11:53:34 +0100
  +
  +glib2.0 (2.64.3-1) unstable; urgency=medium
  +
  +  * Team upload
  +
  +  [ Laurent Bigonville ]
  +  * Drop the libgio-fam package, and install the fam GIO plugin in
  +libglib2.0-0 on Hurd ports. See: #885011 (Closes: #875915)
  +  * Stop building the libgio-fam package on kFreeBSD ports.
  +It is no longer necessary now that gkqueuefilemonitor is available.
  +
  +  [ Simon McVittie ]
  +  * Clarify changelog entry regarding Hurd and kFreeBSD
  +  * New upstream stable release
  +
  + -- Simon McVittie   Fri, 29 May 2020 20:24:33 +0100

  The gio-fam related changes do not affect Ubuntu, as they are for
  hurd/kfreebsd only.

  Upstream NEWS diff:

  * Stability improvements for various unit tests

  * Bugs fixed:
   - #1954 gdbus-server-auth intermittent failure
   - #2094 Deprecation warnings when compiling with 
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_28 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_28
   - !1470 Backport !1440 -Wformat-nonliteral fixes to glib-2-64
   - !1471 Backport !1448 memory monitor test dependency fixes to glib-2-64
   - !1473 CI: Switch to new Windows runners (2.64)
   - !1478 Backport !1477 D-Bus keyring handling fixes to glib-2-64
   - !1483 Backport !1481 “array: fix corrupt state of GPtrArray after 
g_ptr_array_extend_and_steal()” to glib-2-64
   - !1484 Backport !1480 “CI: Make sure we use meson 0.49.2 in MSYS2” to 
glib-2-64
   - !1486 Backport !1472 “gthread: ignore deprecated declarations in static 
inline functions” to glib-2-64
   - !1495 Backport !1493 “meson: Remove stray ], in O_DIRECTORY check” to 
glib-2-64
   - !1501 Backport !1439 “Fix stpcpy() detection“ to glib-2-64

  * Translation updates:
   - Chinese (Taiwan)
   - German

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ Regression potential ]

  Various fixes in multiple places so multiple apps could be affected.
  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1883694/+subscriptions

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


[Touch-packages] [Bug 1045062] Re: No option to save without BOM (Byte Order Mark)

2020-07-06 Thread Benno Schulenberg
Thomas?  Nano does not add a BOM to any file.  If you want to know
whether any file contains a BOM, you can start nano with the +1 cursor-
positioning directive (like so: nano +1 thefilename) and then type
.  If the upper right corner then says "Modified", an
invisible character (most likely a BOM) was deleted before the first
visible one.  If so, type ^S and ^X and you're done.  If "Modified" does
not appear, there is no BOM, and you can simply type ^X to exit.

To summarize: to make sure a file does not contain a Byte Order Mark,
run 'nano +1' followed by the filename, and type:  ^S ^X.

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

Title:
  No option to save without BOM (Byte Order Mark)

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  This may be a wishlist type bug.

  Currently, Nano in precise saves with BOM (Byte Order Mark) by
  default.  There is no way within nano to save without BOM, which
  requires me to download remote server documents to this system and
  then update and reupload the documents after using gedit, kate, or
  some other editor.

  This sometimes screws up remote PHP programs and scripts, which means
  it may be prudent to give the option to decide whether to save with or
  without the Byte Order Mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nano 2.2.6-1
  ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
  Uname: Linux 3.2.0-29-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Sun Sep  2 14:36:54 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nano
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1876670] Re: nfs does not mount at boot with bridge

2020-07-06 Thread Dan Streetman
> May 06 17:35:45 bowser systemd[1]: Mounting NAS devices...
> May 06 17:35:46 bowser mount[751]: mount.nfs: Network is unreachable

it looks like your network isn't actually configured when your mount
tries to run. check your journalctl output to see what's going on. If
you can't figure it out maybe you should just add the mount to
/etc/fstab instead of crafting your own mount unit.

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

Title:
  nfs does not mount at boot with bridge

Status in systemd package in Ubuntu:
  Expired

Bug description:
  I am running a Ubuntu 20.04 server with lxd and kvm/qemu. 
  I try to connect a nfs share at boot. It is working while I do not configure 
any bridge with netplan. I am creating directly a systemd service for the NFS 
mount but I have the same problem if I edit the fstab file.

  #/etc/systemd/system/mnt-nas.mount
  [Unit]
  Description=NAS devices
  After=network.target

  [Mount]
  What=192.168.1.20:/volume2/media
  Where=/mnt/nas
  Type=nfs
  Options=_netdev,auto

  [Install]
  WantedBy=multi-user.target

  ## TEST WITHOUT BRIDGE

  #/etc/netplan/01-netcfg.yaml 
  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes

  root@bowser:~# ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether f8:75:a4:00:be:ad brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eno1
 valid_lft 86244sec preferred_lft 86244sec
  inet6 fe80::fa75:a4ff:fe00:bead/64 scope link 
 valid_lft forever preferred_lft forever
  3: wlp1s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 60:f2:62:38:d7:c2 brd ff:ff:ff:ff:ff:ff

  root@bowser:~# journalctl -b
  ...
  May 04 08:58:08 bowser systemd-networkd[535]: eno1: Gained carrier
  May 04 08:58:08 bowser kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None
  May 04 08:58:08 bowser kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link 
becomes ready
  May 04 08:58:08 bowser systemd[1]: systemd-rfkill.service: Succeeded.
  May 04 08:58:08 bowser set-cpufreq[795]: Setting powersave scheduler for all 
CPUs
  May 04 08:58:08 bowser systemd[1]: ondemand.service: Succeeded.
  May 04 08:58:08 bowser systemd[1]: dmesg.service: Succeeded.
  May 04 08:58:09 bowser systemd-networkd[535]: eno1: Gained IPv6LL
  May 04 08:58:09 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd[535]: eno1: DHCPv4 address 
192.168.1.100/24 via 192.168.1.1
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd-wait-online[611]: managing: eno1
  May 04 08:58:10 bowser systemd[1]: Finished Wait for Network to be Configured.
  May 04 08:58:10 bowser systemd[1]: Reached target Network is Online.
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Login to 
default iSCSI targets being skipped.
  May 04 08:58:10 bowser systemd[1]: Reached target Remote File Systems (Pre).
  May 04 08:58:10 bowser systemd[1]: Mounting NAS devices...
  May 04 08:58:10 bowser systemd[1]: Starting Availability of block devices...
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Pollinate to 
seed the pseudo random number generator being skipped.
  May 04 08:58:10 bowser systemd[1]: Starting OpenBSD Secure Shell server...
  May 04 08:58:10 bowser systemd[1]: Finished Availability of block devices.
  May 04 08:58:10 bowser kernel: FS-Cache: Loaded
  May 04 08:58:10 bowser sshd[952]: Server listening on 0.0.0.0 port 22.
  May 04 08:58:10 bowser sshd[952]: Server listening on :: port 22.
  May 04 08:58:10 bowser systemd[1]: Started OpenBSD Secure Shell server.
  May 04 08:58:10 bowser kernel: FS-Cache: Netfs 'nfs' registered for caching
  May 04 08:58:10 bowser kernel: NFS: Registering the id_resolver key type
  May 04 08:58:10 bowser kernel: Key type id_resolver registered
  May 04 08:58:10 bowser kernel: Key type id_legacy registered
  May 04 08:58:10 bowser systemd[1]: /lib/systemd/system/rpc-statd.service:16: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file 
accordingly.
  May 

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2020-07-06 Thread md shoeb lincoln
** Changed in: resolvconf (Ubuntu)
 Assignee: Dimitri John Ledkov (xnox) => md shoeb lincoln (lincolntgl1987)

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in Cubic:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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


[Touch-packages] [Bug 1003842] Re: SDFEEWRDSsdfdasfsdf

2020-07-06 Thread Colin Watson
** Changed in: dnsmasq (Ubuntu)
   Status: New => Triaged

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

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

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

** Summary changed:

- SDFEEWRDSsdfdasfsdf
+ dnsmasq sometimes fails to resolve private names in networks with 
non-equivalent nameservers

** Tags added: precise xenial

** Description changed:

- dfasfwerwq2323sf
+ A number of reports already filed against network-manager seem to
+ reflect this problem, but to make things very clear I am opening a new
+ report.  Where appropriate I will mark other reports as duplicates of
+ this one.
+ 
+ Consider a pre-Precise system with the following /etc/resolv.conf:
+ 
+ nameserver 192.168.0.1
+ nameserver 8.8.8.8
+ 
+ The first address is the address of a nameserver on the LAN that can
+ resolve both private and public domain names.  The second address is the
+ address of a nameserver on the Internet that can resolve only public
+ names.
+ 
+ This setup works fine because the GNU resolver always tries the first-
+ listed address first.
+ 
+ Now the administrator upgrades to Precise and instead of writing the
+ above to resolv.conf, NetworkManager writes
+ 
+ server=192.168.0.1
+ server=8.8.8.8
+ 
+ to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
+ resolv.conf.  Resolution of private domain names is now broken because
+ dnsmasq treats the two upstream nameservers as equals and uses the
+ faster one, which could be 8.8.8.8.

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

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

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


[Touch-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition

2020-07-06 Thread Pedro Guimarães
Using focal desktop and I am seeing the same issue.
I was seeing tracker-store and tracker-miner-fs taking an entire core of my 
notebook.
Tried: tracker reset --hard and reboot.
Did not work for me.

Only effective solution was to disable search engine on "Settings".

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

Title:
  tracker-store uses 100% cpu and fills all the disk space in home
  partition

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I recently noticed that several tracker related programs were using
  100% cpu on my system and in particular tracker-store filled up
  completely all the available disk space in my home partition.

  I rerun tracker-preferences to make sure that indexing would not
  proceed if less than 20% of free space is available, but it seems that
  tracker-store ignores it.  After I noticed that I had left only 44Kb
  free on the home partition,  I deleted the cache from another program
  and I noticed that tracker-store filled up again the disk space that I
  freed few minutes before.

  This is the content of my .cache/tracker/ directory:
  totale 772068
  -rw-r--r-- 1 eclipse eclipse  3072 2011-06-26 22:56 contents.db
  -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt
  -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt
  -rw-r--r-- 1 eclipse eclipse  3072 2010-12-05 21:29 email-contents.db
  -rw-r--r-- 1 eclipse eclipse  3072 2009-05-06 19:16 email-fulltext.db
  -rw-r--r-- 1 eclipse eclipse   2359292 2011-06-26 22:54 email-index.db
  -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db
  -rw-r--r-- 1 eclipse eclipse  17062912 2011-06-26 19:30 file-contents.db
  -rw-r--r-- 1 eclipse eclipse  15014912 2010-01-12 20:26 file-fulltext.db
  -rw-r--r-- 1 eclipse eclipse  75609207 2011-06-26 22:54 file-index.db
  -rw-r--r-- 1 eclipse eclipse  37027840 2011-06-26 19:31 file-meta.db
  -rw--- 1 eclipse eclipse   1180048 2009-05-05 22:57 file-update-index.db
  -rw-r--r-- 1 eclipse eclipse  28376064 2011-10-20 09:34 fulltext.db
  -rw-r--r-- 1 eclipse eclipse  1024 2012-01-04 21:24 meta.db
  -rw-r--r-- 1 eclipse eclipse   4653056 2012-01-04 21:26 meta.db-shm
  -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal
  -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 
miner-applications-locale.txt
  -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb

  and this is  how much space I have left on my home partition after I KILLED 
the tracker-store process:
  /dev/sda8  31G   30G  418M  99% /home
  --- 
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  DistroRelease: Ubuntu 11.10
  Package: tracker 0.10.24-1build2
  PackageArchitecture: i386
  ProcEnviron:
   LANGUAGE=it_IT:it:en_GB:en
   PATH=(custom, user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9
  Tags:  oneiric
  Uname: Linux 3.0.0-14-generic i686
  UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago)
  UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser 
pulse-access sambashare src video

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

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


[Touch-packages] [Bug 1886421] [NEW] [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Speaker, Internal] No sound at all

2020-07-06 Thread Anandhavishnu V
Public bug reported:

In dual boot Windows, Ubuntu. No audio issues happen when booting to
Ubuntu after booting into Windows. If I suspend(sleep) the Ubuntu then
reopen ubuntu the audio will come back. Restarting will not bring the
audio back.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  av 1953 F pulseaudio
 /dev/snd/pcmC0D0p:   av 1953 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  6 17:29:30 2020
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1412 F pulseaudio
  root   1435 F pulseaudio
  av 1953 F pulseaudio
 /dev/snd/pcmC0D0p:   av 1953 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2019
dmi.bios.vendor: Insyde
dmi.bios.version: F.32
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F9
dmi.board.vendor: HP
dmi.board.version: 46.53
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd05/10/2019:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.53:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.sku: 3CW23PA#ACJ
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug focal

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

Title:
  [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  In dual boot Windows, Ubuntu. No audio issues happen when booting to
  Ubuntu after booting into Windows. If I suspend(sleep) the Ubuntu then
  reopen ubuntu the audio will come back. Restarting will not bring the
  audio back.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  av 1953 F pulseaudio
   /dev/snd/pcmC0D0p:   av 1953 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  6 17:29:30 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1412 F pulseaudio
root   1435 F pulseaudio
av 1953 F pulseaudio
   /dev/snd/pcmC0D0p:   av 1953 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Pavilion Laptop 15-cc1xx, Realtek ALC295, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83F9
  dmi.board.vendor: HP
  dmi.board.version: 46.53
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd05/10/2019:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.53:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cc1xx
  dmi.product.sku: 3CW23PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1003842] Re: SDFEEWRDSsdfdasfsdf

2020-07-06 Thread Nick Moffitt
** Information type changed from Private to Public

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Triaged
Status in network-manager source package in Precise:
  Invalid
Status in dnsmasq package in Debian:
  New

Bug description:
  dfasfwerwq2323sf

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

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


[Touch-packages] [Bug 1886412] Re: $ ubuntu-bug xorg

2020-07-06 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
$ ubuntu-bug xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  I cannot open system settings so I can set up a sleep mode after
  leaving offfor a spell.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.137  Thu Sep 14 13:51:03 
PDT 2017
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  6 11:57:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 304.137, 4.15.0-108-generic, x86_64: installed
   nvidia, 304.137, 4.15.0-109-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] 
[1043:83a4]
  InstallationDate: Installed on 2012-09-29 (2837 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M-LE-V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jul  3 12:16:20 2020
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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


[Touch-packages] [Bug 1814109] Re: Nautilus corrupts 7z archive files when extracting via 'Extract here' context menu

2020-07-06 Thread Amr Ibrahim
Fix released in groovy.

** Changed in: libarchive (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Nautilus corrupts 7z archive files when extracting via 'Extract here'
  context menu

Status in libarchive package in Ubuntu:
  Fix Released
Status in libarchive source package in Disco:
  Won't Fix

Bug description:
  Nautilus corrupts 7z archive files when extracting via 'Extract here' context 
menu.
  Extractions completes without errors, but the files are corrupted (mangled 
bytes, wrong size).
  This does happen only when extracting with 'Extract here' context menu action.
  Using 7z or p7zip via command line or opening the archive via file-roller and 
then drag
  single files or directory to a folder works well.
  This only happens with this particular archive, others 7z archives are 
extracted correctly.

  Original 7z archive:
  https://drive.google.com/open?id=1eZJm1ST3P-52tFSvHXbUn9-WSe_B3Ag9

  Re-zipped corrupted archive here:
  https://drive.google.com/open?id=1N--99RuWdmg6oUGrAz7pLoRpuJOIBEE5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: nautilus 1:3.26.4-0ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 15:03:45 2019
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'222'
   b'org.gnome.nautilus.window-state' b'geometry' b"'1133x703+51+273'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-05-31 (245 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (103 days ago)
  usr_lib_nautilus:

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

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


[Touch-packages] [Bug 1886557] [NEW] [HDA-Intel - HDA ATI SB, playback] No sound at all

2020-07-06 Thread Jean Flies
Public bug reported:

I cannot install any of the installed players. Always messages: error

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
Uname: Linux 5.3.0-62-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jean   6364 F pulseaudio
 /dev/snd/controlC0:  jean   6364 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  6 19:47:29 2020
InstallationDate: Installed on 2020-07-03 (2 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
Symptom_Card: Eingebautes Tongerät - HDA ATI SB
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  jean   6364 F pulseaudio
 /dev/snd/controlC0:  jean   6364 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA ATI SB, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2011
dmi.bios.vendor: Packard Bell
dmi.bios.version: V1.10
dmi.board.name: EasyNote TK11BZ
dmi.board.vendor: Packard Bell
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnPackardBell:bvrV1.10:bd04/15/2011:svnPackardBell:pnEasyNoteTK11BZ:pvrV1.10:rvnPackardBell:rnEasyNoteTK11BZ:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: EasyNote TK11BZ
dmi.product.sku: 123456789
dmi.product.version: V1.10
dmi.sys.vendor: Packard Bell

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


** Tags: amd64 apport-bug eoan

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

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

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I cannot install any of the installed players. Always messages: error

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18
  Uname: Linux 5.3.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jean   6364 F pulseaudio
   /dev/snd/controlC0:  jean   6364 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  6 19:47:29 2020
  InstallationDate: Installed on 2020-07-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed
  Symptom_Card: Eingebautes Tongerät - HDA ATI SB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jean   6364 F pulseaudio
   /dev/snd/controlC0:  jean   6364 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA ATI SB, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2011
  dmi.bios.vendor: Packard Bell
  dmi.bios.version: V1.10
  dmi.board.name: EasyNote TK11BZ
  dmi.board.vendor: Packard Bell
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPackardBell:bvrV1.10:bd04/15/2011:svnPackardBell:pnEasyNoteTK11BZ:pvrV1.10:rvnPackardBell:rnEasyNoteTK11BZ:rvrV1.10:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: EasyNote TK11BZ
  dmi.product.sku: 123456789
  dmi.product.version: V1.10
  dmi.sys.vendor: Packard Bell

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

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


[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

2020-07-06 Thread Lahfa Samy
So far vlc/Vlc Media Player and this specific terminal
https://github.com/Swordfish90/cool-retro-term.

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

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

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


[Touch-packages] [Bug 1862667] Re: systemd autopkgtest 'boot-and-services' fails with linux-kvm

2020-07-06 Thread Dan Streetman
after checking the focal linux-kvm kernel, it does have dm-multipath
enabled as a module, so there should be no change needed in the systemd
test.

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

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

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: linux-kvm (Ubuntu Bionic)

** Changed in: linux-kvm (Ubuntu Focal)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu Focal)
   Status: In Progress => Won't Fix

** Changed in: linux-kvm (Ubuntu)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu)
   Status: In Progress => Won't 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/1862667

Title:
  systemd autopkgtest 'boot-and-services' fails with linux-kvm

Status in linux-kvm package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in linux-kvm source package in Eoan:
  Won't Fix
Status in systemd source package in Eoan:
  Won't Fix
Status in linux-kvm source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Won't Fix

Bug description:
  [impact]

  systemd autopkgtest 'boot-and-services' fails when running with linux-
  kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so
  the test detects failed services.

  [test case]

  check the autopkgtest results, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  test_no_failed (__main__.ServicesTest)
  No failed units ...  journal for failed service multipathd.service 
---
  -- Logs begin at Mon 2020-02-10 03:26:38 UTC, end at Mon 2020-02-10 13:56:23 
UTC. --
  Feb 10 13:56:07 autopkgtest systemd[1]: Starting Device-Mapper Multipath 
Device Controller...
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_alua not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_emc not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
scsi_dh_rdac not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest modprobe[194]: modprobe: WARNING: Module 
dm-multipath not found in directory /lib/modules/5.3.0-1010-kvm
  Feb 10 13:56:07 autopkgtest multipathd[195]: start up
  Feb 10 13:56:07 autopkgtest multipathd[195]: read /etc/multipath.conf
  Feb 10 13:56:07 autopkgtest multipathd[195]: DM multipath kernel driver not 
loaded
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 10 13:56:07 autopkgtest systemd[1]: multipathd.service: Failed with 
result 'exit-code'.
  Feb 10 13:56:07 autopkgtest systemd[1]: Failed to start Device-Mapper 
Multipath Device Controller.
  FAIL

  ==
  FAIL: test_no_failed (__main__.ServicesTest)
  No failed units
  --
  Traceback (most recent call last):
    File 
"/tmp/autopkgtest.WQ5GyY/build.RUe/src/debian/tests/boot-and-services", line 
68, in test_no_failed
  self.assertEqual(failed, [])
  AssertionError: Lists differ: ['multipathd.service loaded failed failed [38 
chars]ler'] != []

  First list contains 1 additional elements.
  First extra element 0:
  'multipathd.service loaded failed failed Device-Mapper Multipath Device 
Controller'

  + []
  - ['multipathd.service loaded failed failed Device-Mapper Multipath Device '
  -  'Controller']

  [regression potential]

  This updates the test case to ignore failure of multipathd.service if
  it looks like the dm-multipath module isn't available, so any
  regression would be limited to incorrectly passing or failing test
  case.

  [scope]

  This is needed at least in Eoan, and probably Focal.

  This doesn't fail on Bionic or Xenial, but that seems to be because
  the multipath-utils package (which provides multipathd.service) is not
  installed during the test for those releases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1862667/+subscriptions

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


[Touch-packages] [Bug 1826387] Re: systemd-networkd restart brings down bond slaves

2020-07-06 Thread Dan Streetman
** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Won't 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/1826387

Title:
  systemd-networkd restart brings down bond slaves

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  Reported upstream as https://github.com/systemd/systemd/issues/10118

  Ubuntu bionic, systemd version 237-3ubuntu10.19

  When systemd-networkd is used to manage network bonds, upon systemd-
  networkd, bonds are brought down for ~10 seconds affecting
  connectivity to the server. From networkd logs (truncated to:

  ```
  # journalctl -b -u systemd-networkd | grep enp3s0f
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring 
/etc/systemd/network/01-enp3s0f1.network, because it's not a regular file with 
suffix .netdev.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: Ignoring 
/etc/systemd/network/00-enp3s0f0.network, because it's not a regular file with 
suffix .netdev.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: 
+SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link 6 added
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: udev initialized 
link
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Saved original 
MTU: 9000
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Flags change: 
+SLAVE +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link 3 added
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: udev initialized 
link
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Saved original 
MTU: 9000
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link state is 
up-to-date
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: found matching 
network '/etc/systemd/network/01-enp3s0f1.network'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link is not 
managed by us
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Started LLDP.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Enslaving by 
'bond0'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f1' was 
up when attempting to enslave it. Bringing link down.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Bringing link 
down
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 
'enp3s0f1'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Link state is 
up-to-date
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: found matching 
network '/etc/systemd/network/00-enp3s0f0.network'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Link does not 
request DHCPv6 prefix delegation
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Started LLDP.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Enslaving by 
'bond0'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Link 'enp3s0f0' was 
up when attempting to enslave it. Bringing link down.
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f0: Bringing link 
down
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: bond0: Enslaving link 
'enp3s0f0'
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Flags change: 
-UP -LOWER_UP -RUNNING
  Apr 25 12:45:33 compute01 systemd-networkd[30824]: enp3s0f1: Stopped LLDP.
  Apr 

[Touch-packages] [Bug 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

2020-07-06 Thread Dan Streetman
** Tags removed: ddstreet

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

Title:
  systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error

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

Bug description:
  The functionality exists to allow users to revert to the traditional ifupdown 
  package for network configuration. Alongside this, systemd's often-buggy 
  resolver can be disabled. However, there's a logic error in the systemd-
  supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system
  from populating /etc/resolv.conf properly when systemd-resolved is disabled. 
  The issue is here:

  if [ -x /lib/systemd/systemd-resolved ] ; then

  Instead of checking to see if the systemd-resolved service is enabled or 
  active, which would be the correct behaviour, this checks for the existence of
  a binary, assuming that if it exists it's supposed to be used.

  I've not tested this in the absence of resolvconf, but if systemd-resolved 
  isn't enabled, it's difficult to imagine this code wanting to run. I've 
tested 
  this with resolvconf and ifupdown driving dhclient, and it corrects the 
  behaviour that was broken with the introduction of systemd-resolved.

  I'm attaching a patch, and am also including it here for easy access:

  *** resolved.broken 2019-11-19 15:01:28.785588838 +
  --- resolved2019-11-19 15:08:06.519430073 +
  ***
  *** 14,20 
#   (D) = master script downs interface
#   (-) = master script does nothing with this

  ! if [ -x /lib/systemd/systemd-resolved ] ; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in
  --- 14,21 
#   (D) = master script downs interface
#   (-) = master script does nothing with this

  ! systemctl is-active systemd-resolved > /dev/null 2>&1
  ! if [ $? -eq 0 ]; then
# For safety, first undefine the nasty default make_resolv_conf()
make_resolv_conf() { : ; }
case "$reason" in

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

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


[Touch-packages] [Bug 1886493] [NEW] Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04)

2020-07-06 Thread FAUVE Sylvain
Public bug reported:

Ubuntu Release : ubuntu 20.04 LTS release 20.04
Driver : alsa-base : 1.0.25+dfsg-0ubuntu5

On Galaxy Book Ion (model NP950XCJ-X01, from 2020)
The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp
Profile : Play HiFi quality music

But I get no sound either from the speakers of headphone jack.
Guessing a driver issue, hardware not properly detected.

Note : Laptop was provided with windows10, sound is ok on windows (so
it's not an hardware issue).

Thanks.

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

** Description changed:

  Ubuntu Release : ubuntu 20.04 LTS release 20.04
  Driver : alsa-base : 1.0.25+dfsg-0ubuntu5
  
  On Galaxy Book Ion (model NP950XCJ-X01, from 2020)
  The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp
  Profile : Play HiFi quality music
  
  But I get no sound either from the speakers of headphone jack.
  Guessing a driver issue, hardware not properly detected.
  
- Note : Laptop was provided with windows10, no sound ok here (so it's not
- an hardware issue).
- 
+ Note : Laptop was provided with windows10, sound is ok on windows (so
+ it's not an hardware issue).
  
  Thanks.

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

Title:
  Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Ubuntu Release : ubuntu 20.04 LTS release 20.04
  Driver : alsa-base : 1.0.25+dfsg-0ubuntu5

  On Galaxy Book Ion (model NP950XCJ-X01, from 2020)
  The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp
  Profile : Play HiFi quality music

  But I get no sound either from the speakers of headphone jack.
  Guessing a driver issue, hardware not properly detected.

  Note : Laptop was provided with windows10, sound is ok on windows (so
  it's not an hardware issue).

  Thanks.

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

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


[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2020-07-06 Thread Steve Langasek
** Changed in: resolvconf (Ubuntu)
 Assignee: md shoeb lincoln (lincolntgl1987) => Dimitri John Ledkov (xnox)

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in Cubic:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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


[Touch-packages] [Bug 1886027] Re: libcgal-dev invalid header lazy, h

2020-07-06 Thread Brian Murray
** Package changed: apport (Ubuntu) => cgal (Ubuntu)

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

Title:
  libcgal-dev invalid header lazy,h

Status in cgal package in Ubuntu:
  New

Bug description:
  When i try to compile the recent version of white_dune (not the ubuntu
  white_dune version, it can not use CGAL), i get the following
  errormessge:

  /usr/include/CGAL/Lazy.h: In constructor ‘CGAL::Lazy_rep_n::Lazy_rep_n(const AC&, const EC&, LL&& ...)’:
  /usr/include/CGAL/Lazy.h:333:63: error: parameter packs not expanded with 
‘...’:
333 | this->set_depth((std::max)( -1, (int)CGAL::depth(ll)) + 1);

  AFAIK this not valid C++...

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

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


[Touch-packages] [Bug 1876831] Re: Microbit WebUSB Udev Rule Missing

2020-07-06 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
   Status: Expired => 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/1876831

Title:
  Microbit WebUSB Udev Rule Missing

Status in systemd package in Ubuntu:
  New

Bug description:
  
  Expected Result: Micro:Bit shows under Web USB devices in chrome as in 19.10
  What happened: Micro:bit does not show under Web USB Devices unless Udev 
rules are added.

  I re-installed my computer recently to 20.04 as my SSD Died around the
  time it came out so decided to use it as a chance to upgrade at the
  same time.

  I noticed when trying to use the WebUSB Feature of the Micro:bit it
  was no longer detected by chrome (not via the snap and was direct deb)
  and to confirm this issue I tried on my Ubuntu 19.10 laptop and it
  detected the micro:bit via webusb no issue.

  After looking around I added the Udev rule from the microbit site at
  https://support.microbit.org/support/solutions/articles/19000105428
  -webusb-troubleshooting#Linux

  and it did start to work under 20.04.

  I would call this a bug, as for many users going from where it's
  working on one version to not on another I suspect I won't be the only
  user wondering why it isn't working. If it is where Ubuntu 19.10 and
  19.04 (and maybe even earlier) worked then I wouldn't be opening this
  bug.


  Thanks -
  Ryan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 50-microbit.rules 60-brother-libsane-type1-inst.rules 
.50-microbit.rules.swp 70-snap.snapd.rules
  Date: Tue May  5 00:13:23 2020
  InstallationDate: Installed on 2020-04-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f28437b5-488a-45d8-b5e1-5e26fb587038 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 AORUS M
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1881982] Re: DoS vulnerability: cause resource exhaustion

2020-07-06 Thread Leonidas S. Barbosa
** Changed in: whoopsie (Ubuntu)
   Status: New => Confirmed

** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Alex Murray (alexmurray)

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

Title:
  DoS vulnerability: cause resource exhaustion

Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  # Vulnerability description
  The parse_report() function in whoopsie.c allows attackers to cause a denial 
of service (memory leak) via a crafted file. 
  Exploitation of this issue causes excessive memory consumption which results 
in the Linux kernel triggering OOM killer on arbitrary process.
  This results in the process being terminated by the OOM killer.

  
  # Details 
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

  
  # PoC (*Please check the below PoC: whoopsie_killer.py)
  1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
  2) Trigger the whoopsie to read the generated crash file.
  3) After then, the whoopsie process has been killed.

  
  # Mitigation (*Please check the below patch: g_hash_table_memory_leak.patch)
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

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

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


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-06 Thread Balint Reczey
I'm also uploading to Groovy so the SRU can be accepted according to the
process.

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

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


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-06 Thread Dan Streetman
@chih sorry for the delay, i'll be uploading today.

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

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


[Touch-packages] [Bug 1861177] Re: seccomp_rule_add is very slow

2020-07-06 Thread Ioanna Alifieraki
Currently, there are autopkgtest regressions on Groovy for the docker.io 
package :
https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_excuses.html#libseccomp

These regressions are not due to the new libseccomp (can be reproduced
with previous libseccomp version). They are due to a bug in cloud-init
when in lxd container, where 'cloud-init status' status returns error.
See bug https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1886531

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

Title:
  seccomp_rule_add is very slow

Status in snapd:
  Invalid
Status in libseccomp package in Ubuntu:
  In Progress
Status in libseccomp source package in Xenial:
  In Progress
Status in libseccomp source package in Bionic:
  In Progress
Status in libseccomp source package in Eoan:
  In Progress
Status in libseccomp source package in Focal:
  In Progress
Status in libseccomp source package in Groovy:
  In Progress

Bug description:
  [IMPACT]
  There is a known and patched issue with version 2.4 of libseccomp where 
certain operations have a large performance regression. This is causing some 
packages that use libseccomp such as container orchestration systems to 
occasionally time out or otherwise fail under certain workloads.

  Please consider porting the patch into the various Ubuntu versions
  that have version 2.4 of libseccomp and into the backports. The
  performance patch from version 2.5 (yet to be released) applies
  cleanly on top of the 2.4 branch of libseccomp.

  For more information, and for a copy of the patch (which can also be
  cherry picked from the upstream libseccomp repos) see the similar
  Debian issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

  Upstream issue : https://github.com/seccomp/libseccomp/issues/153
  Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

  [Test Case]

  For this test case we use Docker on Ubuntu Groovy (20.10) :

  --> Current libseccomp version
  #dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu3 
 amd64high level interface to Linux seccomp filter

  ## pull ubuntu image
  # docker pull ubuntu
  ## create a container
  # docker run --name test_seccomp -it 74435f89ab78 /bin/bash

  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m10,319s
  user  0m0,018s
  sys   0m0,033s

  
  --> Patched libseccomp version

  # dpkg -l | grep libseccomp
  ii  libseccomp2:amd64  2.4.3-1ubuntu4 
 amd64high level interface to Linux seccomp filter

  # docker start test_seccomp
  ## run test case
  # for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
  ...
  MAX TIME :
  real  0m3,650s
  user  0m0,025s
  sys   0m0,028s

  [Regression Potential]

  The first of the 2 patches cleans up the code that adds rules to a
  single filter without changing the logic of the code. The second patch
  introduces the idea of shadow transactions. On a successful
  transaction commit the old transaction checkpoint is preserved and is
  brought up to date with the current filter. The next time a new
  transaction starts, it checks is the a shadow transaction exist and if
  so the shadow is used instead of creating a new checkpoint from
  scratch [1]. This is the patch that mitigates the performance
  regression. Any potential regression will involve the parts of the
  code that add rules to filters and/or the code that creates and checks
  the shadow transactions.

  
  [Other]

  Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

  [1]
  
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

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

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


[Touch-packages] [Bug 1886314] Re: preinstall `earlyoom` by default

2020-07-06 Thread Brian Murray
** Tags added: rls-gg-incoming

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

Title:
  preinstall `earlyoom` by default

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom

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

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


[Touch-packages] [Bug 1884326] Re: SRU the current 2.48.7 stable update

2020-07-06 Thread Olivier Tilloy
I updated librsvg to 2.48.7-1ubuntu0.20.04.1 from focal-proposed in an 
otherwise fully up-to-date focal VM (amd64), logged out and back in, and did 
some extensive smoke testing, both targetted (opening and manipulating various 
SVG images in eog and gimp), and general (launched several applications and 
verified that they render correctly their UI and content).
Everything looks fine, I couldn't spot any regression.

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

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

Title:
  SRU the current 2.48.7 stable update

Status in librsvg package in Ubuntu:
  Fix Released
Status in librsvg source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, which fixes a number of issues: 
https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Smoke testing by opening SVG images with eog or importing them with
  gimp can be performed to ensure there are no regressions.

  * Regression potential

  This is a bugfix-only stable micro-release, however librsvg is a core
  component with a number of reverse dependencies. A combination of
  autopkgtests and manual smoke testing to try and detect SVG rendering
  issues should be performed.

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

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


[Touch-packages] [Bug 1886430] [NEW] debian/tests/tests-in-lxd fails when /etc/fstab is missing from the LXC container

2020-07-06 Thread Balint Reczey
Public bug reported:

In LP: #1877078 /etc/fstab has been removed from LXD images and now the
workaround also removing it in the test started failing . :-(

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

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

Title:
  debian/tests/tests-in-lxd fails when /etc/fstab is missing from the
  LXC container

Status in systemd package in Ubuntu:
  New

Bug description:
  In LP: #1877078 /etc/fstab has been removed from LXD images and now
  the workaround also removing it in the test started failing . :-(

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

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


[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-07-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/386923

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions

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


[Touch-packages] [Bug 1886573] [NEW] Graphics driver issue

2020-07-06 Thread Sarwat Firoz
Public bug reported:

Graphics driver issue. I can't fetch info. I can't update it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  7 01:21:30 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
 tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
InstallationDate: Installed on 2020-06-20 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20042
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=575bc930-4ddd-48a7-bab4-a8aeb466b45b ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 29CN41WW(V2.18)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnLENOVO:bvr29CN41WW(V2.18):bd02/02/2012:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: Intel_Mobile
dmi.product.name: 20042
dmi.product.sku: Calpella_CRB
dmi.product.version: Lenovo G560
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages 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/1886573

Title:
  Graphics driver issue

Status in xorg package in Ubuntu:
  New

Bug description:
  Graphics driver issue. I can't fetch info. I can't update it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 01:21:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
  InstallationDate: Installed on 2020-06-20 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20042
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=575bc930-4ddd-48a7-bab4-a8aeb466b45b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 29CN41WW(V2.18)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 

[Touch-packages] [Bug 1886572] [NEW] Remove uptime from the motd-news user agent

2020-07-06 Thread Dean Henrichsmeyer
Public bug reported:

I don't why that was included but it shouldn't be. Please remove it.

** Affects: base-files (Ubuntu)
 Importance: High
 Assignee: Andreas Hasenack (ahasenack)
 Status: New

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  New

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions

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


[Touch-packages] [Bug 1886573] Re: Graphics driver issue

2020-07-06 Thread Sarwat Firoz
** Changed in: xorg (Ubuntu)
   Status: New => Invalid

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

Title:
  Graphics driver issue

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Graphics driver issue. I can't fetch info. I can't update it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 01:21:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
  InstallationDate: Installed on 2020-06-20 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20042
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=575bc930-4ddd-48a7-bab4-a8aeb466b45b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 29CN41WW(V2.18)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnLENOVO:bvr29CN41WW(V2.18):bd02/02/2012:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: 20042
  dmi.product.sku: Calpella_CRB
  dmi.product.version: Lenovo G560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

2020-07-06 Thread guenthert
Hmmh, if I see this right, there's a systemd-dbg package available for
Ubuntu 16.04, but not for 18.04.

FWIW, I attached the original core file as bug1886115.core .

** Attachment added: "original core dump of systemd-237-3ubuntu10.41 with 
libseccomp2-2.4.3-1ubuntu3"
   
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1886115/+attachment/5390306/+files/bug1886115.core

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in libc-2.27.so[7f17ebed7000+1e7000]
  -->8--
  . 

To me that looked a bit like Bug 669702 of Gentoo
  (https://bugs.gentoo.org/669702) and indeed one of the (few) updates
  applied just prior the reboot was the update of libseccomp.

I was able to circumvent the problem by disabling (commenting out) the 
syscall filtering requested by systemd (on my system, only 
/etc/systemd/system/dbus-org.freedesktop.resolve1.service needed to be 
modified).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Apple Inc. Macmini5,1
  NonfreeKernelModules: wl
  Package: systemd 237-3ubuntu10.41 [modified: 
lib/systemd/system/systemd-resolved.service]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-62-generic 
root=UUID=891c2e06-2b40-4e79-a57f-6e550be932bb ro recovery nomodeset
  ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18
  Tags:  bionic
  Uname: Linux 5.3.0-62-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM51.88Z.0077.B10.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-8ED6AF5B48C039E1
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini5,1
  dmi.chassis.type: 16
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-8ED6AF5B48C039E1
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM51.88Z.0077.B10.1201241549:bd01/24/2012:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1:
  dmi.product.family: Macmini
  dmi.product.name: Macmini5,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: MATE
  Dependencies:
   gcc-8-base 8.4.0-1ubuntu1~18.04
   libc6 2.27-3ubuntu1
   libgcc1 1:8.4.0-1ubuntu1~18.04
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-03-30 (460 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  

[Touch-packages] [Bug 1886598] [NEW] [Inspiron 3185, Realtek ALC3204, Mic, Internal] Underruns, dropouts or crackling sound

2020-07-06 Thread and
Public bug reported:

After recording my voice with a microphone, I hear a crackle when I play
the voice.

Noise can be confirmed with Audacity and Cheese.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul  7 10:30:36 2020
InstallationDate: Installed on 2020-04-28 (69 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
Symptom_Card: 内部オーディオ - HD-Audio Generic
Symptom_Jack: Mic, Internal
Symptom_PulseAudioLog:
 7月 07 10:28:15 Inspiron-3185 dbus-daemon[635]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.35' (uid=125 pid=820 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  7月 07 10:28:36 Inspiron-3185 systemd[805]: pulseaudio.service: Succeeded.
  7月 07 10:28:45 Inspiron-3185 systemd[805]: pulseaudio.socket: Succeeded.
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [Inspiron 3185, Realtek ALC3204, Mic, Internal] Underruns, dropouts or 
crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.0
dmi.board.name: 05NKJF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.3.0
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3185:pvr1.3.0:rvnDellInc.:rn05NKJF:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3185
dmi.product.sku: 087F
dmi.product.version: 1.3.0
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [Inspiron 3185, Realtek ALC3204, Mic, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After recording my voice with a microphone, I hear a crackle when I
  play the voice.

  Noise can be confirmed with Audacity and Cheese.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 10:30:36 2020
  InstallationDate: Installed on 2020-04-28 (69 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: 内部オーディオ - HD-Audio Generic
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioLog:
   7月 07 10:28:15 Inspiron-3185 dbus-daemon[635]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.35' (uid=125 pid=820 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
7月 07 10:28:36 Inspiron-3185 systemd[805]: pulseaudio.service: Succeeded.
7月 07 10:28:45 Inspiron-3185 systemd[805]: pulseaudio.socket: Succeeded.
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Inspiron 3185, Realtek ALC3204, Mic, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 05NKJF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.3.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3185:pvr1.3.0:rvnDellInc.:rn05NKJF:rvrA00:cvnDellInc.:ct10:cvr1.3.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3185
  dmi.product.sku: 087F
  dmi.product.version: 1.3.0
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-07-06 Thread Kai-Chuan Hsieh
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Changed in: oem-priority
   Status: In Progress => Confirmed

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions

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


[Touch-packages] [Bug 1886115] Re: libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

2020-07-06 Thread Alex Murray
Thanks - in Ubuntu releases 18.04 onwards debug symbols are provided via
the separate -dbgsyms packages which require extra configuration -
https://wiki.ubuntu.com/DebuggingProgramCrash

TL;DR:

echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe 
multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list
echo -e "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted 
universe multiverse\ndeb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed 
main restricted universe multiverse" | sudo tee -a 
/etc/apt/sources.list.d/ddebs.list
sudo apt install ubuntu-dbgsym-keyring
sudo apt update
sudo apt install systemd-dbgsym
gdb /sbin/init bug1886115.core
(gdb) bt

Which gives the following more complete stack trace (sadly a bunch of
stuff has been optimised out, but also since this is crashing in freep()
it seems that memory corruption has already occurred prior to this point
and we don't have any info as to where this happened):

#0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
#1  0x563b957223b7 in crash (sig=11) at ../src/core/main.c:196
#2  
#3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
#4  0x563b9577c22e in freep () at ../src/basic/alloc-util.h:61
#5  unit_fail_if_noncanonical (u=, where=) at 
../src/core/unit.c:4774
#6  0x563b957672d6 in mount_enter_mounting (m=0x563b9782dba0) at 
../src/core/mount.c:946
#7  mount_start.lto_priv.216 (u=0x563b9782dba0) at ../src/core/mount.c:1092
#8  0x563b9576ba22 in unit_start (u=0x563b9782dba0) at 
../src/core/unit.c:1861
#9  job_perform_on_unit.lto_priv.424 (j=0x7ffe78153248) at ../src/core/job.c:553
#10 0x563b9574f51a in job_run_and_invalidate (j=) at 
../src/core/job.c:618
#11 manager_dispatch_run_queue.lto_priv.429 (source=, 
userdata=, userdata=) at 
../src/core/manager.c:1830
#12 0x7f16803a509a in source_dispatch (s=s@entry=0x563b9780e8c0) at 
../src/libsystemd/sd-event/sd-event.c:2341
#13 0x7f16803a53ea in sd_event_dispatch (e=, 
e@entry=0x563b9780e620) at ../src/libsystemd/sd-event/sd-event.c:2663
#14 0x7f16803a5579 in sd_event_run (e=, 
timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2723
#15 0x563b9572a49d in manager_loop (m=0x563b97810d90) at 
../src/core/manager.c:2541
#16 invoke_main_loop (m=0x563b97810d90, ret_reexecute=0x7ffe7815347a, 
ret_retval=, ret_shutdown_verb=, 
ret_fds=0x7ffe78153480, ret_switch_root_dir=0x7ffe781534a8, 
ret_switch_root_init=0x7ffe781534a0, ret_error_message=0x7ffe78153490)
at ../src/core/main.c:1778
#17 0x563b9571560c in main (argc=, argv=) at 
../src/core/main.c:2561


What is really needed is to try and catch the memory corruption as it happens - 
I am not sure if it is possible to run systemd via valgrind but this could be 
one option.

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

Title:
  libseccomp 2.4.3-1ubuntu3.18.04.2 causes systemd to segfault on boot

Status in libseccomp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
  i5-2415M CPU) failed to complete the boot process.  A few seconds into
  the boot, the last message displayed is "/var mounted".  The system
  then appears to hang indefinitely.

Luckily, the 'rescue' boot image allows the boot process to proceed 
sufficiently far to allow a root shell to be spawned.  Unfortunately no log 
files were written during the unsuccessful attempts to boot.  Spawning a 2nd 
root shell (# nohup getty tty5) on a 2nd virtual terminal (tty5) I was able to 
observe the message 'systemd freezing execution' after I closed the first root 
shell and resumed the boot process.  Further a core file was created (belonging 
to /sbin/init) in the root fs
  --8<--
  (gdb) bt
  #0  0x7f16807ba187 in kill () at ../sysdeps/unix/syscall-template.S:78
  #1  0x563b957223b7 in ?? ()
  #2  
  #3  __GI___libc_free (mem=0x4a60d140dfd9a5) at malloc.c:3103
  #4  0x563b9577c22e in ?? ()
  #5  0x563b957672d6 in ?? ()
  #6  0x563b9576ba22 in ?? ()
  #7  0x563b9574f51a in ?? ()
  #8  0x7f16803a509a in ?? () from /lib/systemd/libsystemd-shared-237.so
  #9  0x7f16803a53ea in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-237.so
  #10 0x7f16803a5579 in sd_event_run () from 
/lib/systemd/libsystemd-shared-237.so
  #11 0x563b9572a49d in ?? ()
  #12 0x563b9571560c in ?? ()
  #13 0x7f168079cb97 in __libc_start_main (main=0x563b957139c0, argc=3, 
argv=0x7ffe78153758, 
  init=, fini=, rtld_fini=, 
  stack_end=0x7ffe78153748) at ../csu/libc-start.c:310
  #14 0x563b957164fa in ?? ()
  (gdb) 
  -->8--
   and the kernel message buffer lists 
  --8<--
  traps: systemd[1] general protection fault ip:7f17ebf6e98d sp:7ffd774d6020 
error:0 in 

[Touch-packages] [Bug 1886573] Re: Graphics driver issue

2020-07-06 Thread Daniel van Vugt
It appears you have an Intel GPU so there is no supported way to update
the graphics driver.

Instead, please tell us what kind of problem you are experiencing.

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

Title:
  Graphics driver issue

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Graphics driver issue. I can't fetch info. I can't update it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 01:21:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
  InstallationDate: Installed on 2020-06-20 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20042
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=575bc930-4ddd-48a7-bab4-a8aeb466b45b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 29CN41WW(V2.18)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnLENOVO:bvr29CN41WW(V2.18):bd02/02/2012:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: Intel_Mobile
  dmi.product.name: 20042
  dmi.product.sku: Calpella_CRB
  dmi.product.version: Lenovo G560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1886412] Re: $ ubuntu-bug xorg

2020-07-06 Thread Sebastien Bacher
Thank you for taking the time to report this bug and help 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!

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

** Changed in: xorg (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/1886412

Title:
$ ubuntu-bug xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I cannot open system settings so I can set up a sleep mode after
  leaving offfor a spell.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.137  Thu Sep 14 13:51:03 
PDT 2017
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  6 11:57:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 304.137, 4.15.0-108-generic, x86_64: installed
   nvidia, 304.137, 4.15.0-109-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. C61 [GeForce 7025 / nForce 630a] 
[1043:83a4]
  InstallationDate: Installed on 2012-09-29 (2837 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=6eb98a42-bc12-42f1-992b-97782d05bb24 ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4N68T-M-LE-V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-LE-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Jul  3 12:16:20 2020
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

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

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


[Touch-packages] [Bug 1886336] Re: Network Manager permissions issue

2020-07-06 Thread Sebastien Bacher
Thank you for your bug report, you would probably have a better chance
to have a reply upstream for taht issue on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Network Manager permissions issue

Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 20.04 LTS
  Release:20.04

  network-manager:
Installed: 1.22.10-1ubuntu2.1
Candidate: 1.22.10-1ubuntu2.1
Version table:
   *** 1.22.10-1ubuntu2.1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  Having recently updated from 19.19 to 20.04, I am now unable to
  add/edit any connections. When I try, a dialogue box pops up saying;

  "Failed to activate {SSID}
  Not authorized to control networking."

  I have spent some time trawling the web but no obvious solution was
  found, but one post mentioned "nmcli g permissions" which I tried as
  user and using sudo.

  User output;

  PERMISSION VALUE
  org.freedesktop.NetworkManager.enable-disable-network no
  org.freedesktop.NetworkManager.enable-disable-wifi no
  org.freedesktop.NetworkManager.enable-disable-wwan no
  org.freedesktop.NetworkManager.enable-disable-wimax no
  org.freedesktop.NetworkManager.sleep-wake no
  org.freedesktop.NetworkManager.network-control auth
  org.freedesktop.NetworkManager.wifi.share.protecte d no
  org.freedesktop.NetworkManager.wifi.share.open no
  org.freedesktop.NetworkManager.settings.modify.sys tem no
  org.freedesktop.NetworkManager.settings.modify.own auth
  org.freedesktop.NetworkManager.settings.modify.hos tname auth
  org.freedesktop.NetworkManager.settings.modify.glo bal-dns auth
  org.freedesktop.NetworkManager.reload auth
  org.freedesktop.NetworkManager.checkpoint-rollback auth
  org.freedesktop.NetworkManager.enable-disable-statistics no
  org.freedesktop.NetworkManager.enable-disable-connectivity-check no
  org.freedesktop.NetworkManager.wifi.scan unknown

  Sudo output;

  org.freedesktop.NetworkManager.enable-disable-network yes
  org.freedesktop.NetworkManager.enable-disable-wifi yes
  org.freedesktop.NetworkManager.enable-disable-wwan yes
  org.freedesktop.NetworkManager.enable-disable-wimax yes
  org.freedesktop.NetworkManager.sleep-wake yes
  org.freedesktop.NetworkManager.network-control yes
  org.freedesktop.NetworkManager.wifi.share.protecte d yes
  org.freedesktop.NetworkManager.wifi.share.open yes
  org.freedesktop.NetworkManager.settings.modify.sys tem yes
  org.freedesktop.NetworkManager.settings.modify.own yes
  org.freedesktop.NetworkManager.settings.modify.hos tname yes
  org.freedesktop.NetworkManager.settings.modify.glo bal-dns yes
  org.freedesktop.NetworkManager.reload yes
  org.freedesktop.NetworkManager.checkpoint-rollback yes
  org.freedesktop.NetworkManager.enable-disable-statistics yes
  org.freedesktop.NetworkManager.enable-disable-connectivity-check yes
  org.freedesktop.NetworkManager.wifi.scan unknown

  Now it seems to me that I should have more permissions as a user.

  I have checked what the User output is when you boot into the live ISO
  and it has all the same permissions as the Sudo output shown above. So
  my guess would be that this is what myproblem is.

  How can I fix these permission issues as a workaround while you
  investigate this bug.

  Thanks.

  Jim!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Sun Jul  5 19:07:19 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-13 (1361 days ago)
  InstallationMedia: It
  IpRoute:
   default via 192.168.0.2 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.176 metric 
600
  ProcEnviron:
   LANGUAGE=en_GB
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-03-14 (113 days ago)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2020-01-01T15:53:38.227396
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN  

[Touch-packages] [Bug 1886272] Re: Request to package webp pixbuf

2020-07-06 Thread Sebastien Bacher
** Changed in: libwebp (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Request to package webp pixbuf

Status in libwebp package in Ubuntu:
  New

Bug description:
  It is not currently possible to open a WebP image in any standard
  application on Ubuntu (except Firefox). There is a now a small
  extension for gdk-pixbuf to support webp: https://github.com/aruiz
  /webp-pixbuf-loader

  Such extension has already been packaged for HEIF (heif-gdk-pixbuf),
  it'd be nice to have it for WebP too.

  Once installed, any standard Gnome program can support reading such
  image, and in particular, eog.

  An example file:
  https://www.gstatic.com/webp/gallery/1.webp

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

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


[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-07-06 Thread Andreas Hasenack
** Changed in: base-files (Ubuntu)
   Status: New => In Progress

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions

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


[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-07-06 Thread Andreas Hasenack
There is this comment next to the uptime grabbing:
# Some messages may only be pertinent before or after some amount of uptime
read up idle < /proc/uptime
uptime="uptime/$up/$idle"

As far as I know, this was never used, as the server serves static
content.

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  In Progress

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions

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


[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps

2020-07-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/coreutils/+git/coreutils/+merge/386911

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

Title:
  disk space info inadvertently provides all installed snaps

Status in apt package in Ubuntu:
  Fix Released
Status in coreutils package in Ubuntu:
  New
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  When apport is reporting a crash, it includes the output of the "df" utility, 
to list the free disk space information per mount point.

  That output nowadays will inadvertently include all snaps that the
  user may have installed, including their revision numbers.

  Here is a simple df output:
  andreas@nsn7:~$ df
  Filesystem  1K-blocksUsed Available Use% Mounted on
  udev  8119680   0   8119680   0% /dev
  tmpfs 16301561828   1628328   1% /run
  nsn7/ROOT/ubuntu433084288 2500608 430583680   1% /
  tmpfs 8150776   1   8131888   1% /dev/shm
  tmpfs5120   4  5116   1% /run/lock
  tmpfs 8150776   0   8150776   0% 
/sys/fs/cgroup
  nsn7/var/log430763136  179456 430583680   1% /var/log
  nsn7/var/tmp430583808 128 430583680   1% /var/tmp
  /dev/sda2 1032088  160336871752  16% /boot
  /dev/sda1  5232482720520528   1% /boot/efi
  nsn7/home   430651264   67584 430583680   1% /home
  nsn7/var/cache  430653312   69632 430583680   1% /var/cache
  nsn7/var/mail   430583808 128 430583680   1% /var/mail
  nsn7/var/spool  430583808 128 430583680   1% /var/spool
  tmpfs 1630152  16   1630136   1% /run/user/120
  tmpfs 100   0   100   0% 
/var/lib/lxd/shmounts
  tmpfs 100   0   100   0% 
/var/lib/lxd/devlxd
  tmpfs 1630152  36   1630116   1% 
/run/user/1000
  nsn7/lxd/containers/squid-ds216 431444096  860416 430583680   1% 
/var/lib/lxd/storage-pools/default/containers/squid-ds216
  /dev/loop0  83712   83712 0 100% 
/snap/core/4206
  /dev/loop1 102144  102144 0 100% 
/snap/git-ubuntu/402

  You can see I have the core snap at revision 4206, and git-ubuntu at
  revision 402.

  There are already many bug reports in launchpad where one can see this
  information.

  Granted, the user can review it, refuse to send this data, etc. This
  bug is about the unexpectedness of having that information in the disk
  space data.

  If the user sees a prompt like "Would you like to include disk free
  space information in your report?", or "Would you like to include the
  output of the df(1) command in your report?", that doesn't immediately
  translate to "Would you like to include disk free space information
  and a list of all installed snaps and their revision numbers in your
  report?".

  [Test case]
  Do something that triggers the apport hook and make sure you don't see snaps 
in there.

  For example, install xterm, then add exit 1 to the start of the prerm,
  then run apt remove xterm, and investigate /var/crash/xterm.0.crash
  after that (delete before running apt).

  [Regression potential]
  Fix consists of adding -x squashfs to df output, so might hide other non-snap 
squashfs images.

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

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


[Touch-packages] [Bug 1876831] Re: Microbit WebUSB Udev Rule Missing

2020-07-06 Thread Dan Streetman
I believe you have some udev rule, probably located in
/lib/udev/rules.d/, that's setting the device group to 'plugdev' so that
you can access it - just like your custom rule does in focal. I think
you'll have to determine which rule it is so we can check for changes
between 19.10 and 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/1876831

Title:
  Microbit WebUSB Udev Rule Missing

Status in systemd package in Ubuntu:
  New

Bug description:
  
  Expected Result: Micro:Bit shows under Web USB devices in chrome as in 19.10
  What happened: Micro:bit does not show under Web USB Devices unless Udev 
rules are added.

  I re-installed my computer recently to 20.04 as my SSD Died around the
  time it came out so decided to use it as a chance to upgrade at the
  same time.

  I noticed when trying to use the WebUSB Feature of the Micro:bit it
  was no longer detected by chrome (not via the snap and was direct deb)
  and to confirm this issue I tried on my Ubuntu 19.10 laptop and it
  detected the micro:bit via webusb no issue.

  After looking around I added the Udev rule from the microbit site at
  https://support.microbit.org/support/solutions/articles/19000105428
  -webusb-troubleshooting#Linux

  and it did start to work under 20.04.

  I would call this a bug, as for many users going from where it's
  working on one version to not on another I suspect I won't be the only
  user wondering why it isn't working. If it is where Ubuntu 19.10 and
  19.04 (and maybe even earlier) worked then I wouldn't be opening this
  bug.


  Thanks -
  Ryan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 50-microbit.rules 60-brother-libsane-type1-inst.rules 
.50-microbit.rules.swp 70-snap.snapd.rules
  Date: Tue May  5 00:13:23 2020
  InstallationDate: Installed on 2020-04-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f28437b5-488a-45d8-b5e1-5e26fb587038 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 AORUS M
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1219529] Re: df -x tmpfs fails to exclude udev (/dev)

2020-07-06 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~bryce/ubuntu/+source/coreutils/+git/coreutils/+merge/386911

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

Title:
  df -x tmpfs fails to exclude udev (/dev)

Status in coreutils:
  New
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  The command:

  $ /bin/df -x tmpfs

  should exclude all filesystems of type tmpfs. The udev filesystem
  mounted at /dev is of this type:

  $ stat -f /dev
File: "/dev"
  ID: 0Namelen: 255 Type: tmpfs
  Block size: 4096   Fundamental block size: 4096
  Blocks: Total: 4109101Free: 4109098Available: 4109098
  Inodes: Total: 4109101Free: 4108501

  However, df still displays this filesystem:

  $ df -l -x tmpfs
  Filesystem  1K-blocks  Used  Available Use% Mounted on
  ...
  udev 1643640412   16436392   1% /dev
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: coreutils 8.20-3ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sun Sep  1 15:05:40 2013
  InstallationDate: Installed on 2013-08-31 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1841745] Re: Update to 1.2.0

2020-07-06 Thread Sebastien Bacher
** Changed in: libxt (Ubuntu)
   Status: New => Triaged

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

Title:
  Update to 1.2.0

Status in libxt package in Ubuntu:
  Triaged
Status in libxt package in Debian:
  New

Bug description:
  The new version has non trivial change and is not in Debian/Fedora yet

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

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


[Touch-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

2020-07-06 Thread Sebastien Bacher
Could you add the 'journalctl -b 0' log from the system after getting
the error?

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

Title:
  https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  OS: Pop!_OS 20.04 LTS x86_64 
  Host: XPS 13 9370 
  Kernel: 5.4.0-7634-generic 
  Uptime: 2 hours, 50 mins 
  Packages: 1817 (dpkg), 20 (snap) 
  Shell: bash 5.0.16 
  Resolution: 1920x1080 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Pop 
  Theme: Pop-dark [GTK2/3] 
  Icons: Pop [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  Memory: 3322MiB / 15729MiB 

  Summary(cont) - Attempt to input Google account info into online
  account util and get error--> TLS/SSL support not available; install
  glib-networking.

   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
  Referenced this BUG REPORT

  ##Downloaded Deb build but I'm having an issue applying appropriate
  inputs in the provided documentation. Please help!##

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+subscriptions

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


[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled

2020-07-06 Thread Jérôme de Bretagne
Hi You-Sheng,

Sorry for this very late feedback, I just saw your message a few minutes
ago as I was not subscribed to this bug.

I've now tested your backport of the patches and I can confirm that it
is indeed working on my machine (Dell Latitude 7275).

FYI, I was also pointed out that there is an on-going discussion about suspend 
failures following these patches, details here: 
https://bugzilla.kernel.org/show_bug.cgi?id=207629
but I'm not seeing this issue in my case.

Cheers,
Jérôme

** Bug watch added: Linux Kernel Bug Tracker #207629
   https://bugzilla.kernel.org/show_bug.cgi?id=207629

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

Title:
  System wakes up immediately after suspend if Bluetooth is still
  enabled

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After replacing my USB mouse with a BT mouse, I noticed my machine
  would no longer suspend without immediately waking up. i.e. I suspend
  and see the light go into the slow fade in and out for one cycle and
  then goes solid and the display wakes up again. If I disable BT (via
  blueman applet) suspend works fine.

  I've fixed this by shutting down the BT service before suspend, and
  starting it back up on wake, as indicated here:
  https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately-
  after-suspend

  Perhaps this script should be included in blueZ as suspend issues seem
  very hard to debug and the immediate wake after suspend could be
  caused many any number of things.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1 [modified: 
lib/systemd/system/bluetooth.service]
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Apr  3 13:16:14 2019
  InstallationDate: Installed on 2019-02-09 (53 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems NUC8i3BEH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BECFL357.86A.0051.2018.1015.1513
  dmi.board.name: NUC8BEB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J72693-304
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC8i3BEH
  dmi.product.version: J72753-303
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:BB:60:50:92:5D  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:1912660 acl:106009 sco:0 events:337 errors:0
TX bytes:12331 acl:74 sco:0 commands:204 errors:0

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

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


[Touch-packages] [Bug 1882636] Re: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

2020-07-06 Thread Marcus Urso-Bernick
No problem, I'm away from my laptop now but will be able to send
you`journalctl -b 0` by 2230 UTC

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

Title:
  https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777

Status in glib-networking package in Ubuntu:
  Incomplete

Bug description:
  OS: Pop!_OS 20.04 LTS x86_64 
  Host: XPS 13 9370 
  Kernel: 5.4.0-7634-generic 
  Uptime: 2 hours, 50 mins 
  Packages: 1817 (dpkg), 20 (snap) 
  Shell: bash 5.0.16 
  Resolution: 1920x1080 
  DE: GNOME 
  WM: Mutter 
  WM Theme: Pop 
  Theme: Pop-dark [GTK2/3] 
  Icons: Pop [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i5-8250U (8) @ 3.400GHz 
  GPU: Intel UHD Graphics 620 
  Memory: 3322MiB / 15729MiB 

  Summary(cont) - Attempt to input Google account info into online
  account util and get error--> TLS/SSL support not available; install
  glib-networking.

   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1873777
  Referenced this BUG REPORT

  ##Downloaded Deb build but I'm having an issue applying appropriate
  inputs in the provided documentation. Please help!##

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1882636/+subscriptions

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


[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-07-06 Thread Dan Streetman
Ok, I'm going to revert this from the queued-up focal commits before
uploading, as IIUC the /dev/disk/by-uuid/ symlink shouldn't actually
matter, since the symlink that should be used is /dev/bcache/by-uuid/.
And based on comment 47 it sounds like that's accurate, and the real fix
needs to go into bcache-utils to properly create the dev/bcache/by-uuid/
symlink.

This can be added back to the focal queue if I've misread the patch.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions

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


[Touch-packages] [Bug 1838329] Re: Cryptswap periodically fails to mount at boot due to missing a udev notification

2020-07-06 Thread Dan Streetman
** Description changed:

+ [impact]
+ 
+ systems using cryptsetup-based encrypted swap may hang during boot due
+ to udevd missing the notification that swap has been setup on the newly
+ created swap device.
+ 
+ [test case]
+ 
+ see original description, and reproduction is intermittent based on
+ timing
+ 
+ [regression potential]
+ 
+ any regression would likely occur during, or after, boot when creating
+ an encrypted swap device and/or while waiting to activate the new swap
+ device. Regressions may cause failure to correctly enable swap and/or
+ hung boot waiting for the swap device.
+ 
+ [scope]
+ 
+ this was (potentially) fixed upstream with PR 15836, which is not yet
+ included in any upstream release, so this is needed in all releases,
+ including groovy.
+ 
+ also note while the upstream bug is closed, and code review seems to
+ indicate this *should* fix this specific issue, there are some comments
+ in the upstream bug indicating it may not completely solve the problem,
+ although there is no further debug of the new reports.
+ 
+ [original description]
+ 
  On some systems, cryptsetup-based encrypted swap partitions cause
  systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
  the rate of occurrence varies from one system to another. Some hardware
  will not experience the issue at all, others will only occasionally
  experience the issue, and then there are the unlucky who are unable to
  boot at all, no matter how many times they restart.
  
  The workaround is for the cryptsetup-generator to generate cryptswap
  service entries that call `udevadm trigger` after `mkswap`. This will
  ensure that the udev event is triggered, so that systemd is notified
  that the encrypt swap partition is ready to activate. This patch has
  already been submitted upstream to systemd, but it was not accepted
  because it is a workaround for the side effect of systemd not seeing the
  udev event upon creating the swap partition.

** Tags removed: bionic ddstreet disco eoan

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

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

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

** Changed in: systemd (Ubuntu Groovy)
   Status: In Progress => 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/1838329

Title:
  Cryptswap periodically fails to mount at boot due to missing a udev
  notification

Status in systemd:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  New

Bug description:
  [impact]

  systems using cryptsetup-based encrypted swap may hang during boot due
  to udevd missing the notification that swap has been setup on the
  newly created swap device.

  [test case]

  see original description, and reproduction is intermittent based on
  timing

  [regression potential]

  any regression would likely occur during, or after, boot when creating
  an encrypted swap device and/or while waiting to activate the new swap
  device. Regressions may cause failure to correctly enable swap and/or
  hung boot waiting for the swap device.

  [scope]

  this was (potentially) fixed upstream with PR 15836, which is not yet
  included in any upstream release, so this is needed in all releases,
  including groovy.

  also note while the upstream bug is closed, and code review seems to
  indicate this *should* fix this specific issue, there are some
  comments in the upstream bug indicating it may not completely solve
  the problem, although there is no further debug of the new reports.

  [original description]

  On some systems, cryptsetup-based encrypted swap partitions cause
  systemd to get stuck at boot. This is a timing-sensitive Heisenbug, so
  the rate of occurrence varies from one system to another. Some
  hardware will not experience the issue at all, others will only
  occasionally experience the issue, and then there are the unlucky who
  are unable to boot at all, no matter how many times they restart.

  The workaround is for the cryptsetup-generator to generate cryptswap
  service entries that call `udevadm trigger` after `mkswap`. This will
  ensure that the udev event is triggered, so that systemd is notified
  that the encrypt swap partition is ready to activate. This patch has
  already been submitted upstream to systemd, but it was not accepted
  because it is a workaround for the side effect of systemd not seeing
  the udev event upon creating the swap partition.

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

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

[Touch-packages] [Bug 1880541] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces zainstalowany pakiet udev skrypt post-installation returned error code 1

2020-07-06 Thread Dan Streetman
** Description changed:

- During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
- configure interrupting the upgrade.
+ [impact]
+ 
+ during upgrade, udev may fail to configure, interrupting the upgrade
+ 
+ [test case]
+ 
+ on 18.04, create a non-system group 'kvm', then upgrade to 20.04
+ 
+ [regression potential]
+ 
+ any regression would likely result in a kvm group that was not properly
+ created, possibly restricting users from using kvm acceleration until
+ the problem was fixed.
+ 
+ [scope]
+ 
+ this is needed only for focal, as it occurs only on upgrade to focal.
+ 
+ [original description]
+ 
+ 
+ During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to configure 
interrupting the upgrade.
  
  dpkg complained that kvm already exist but it is not a system group.
  
  From what I saw my user was the only member of kvm group
  I don't recall installing kvm manually but I do have Android emulator 
installed so it is possible that it is related.
  
  Removing kvm group via
  groupdel kvm
- allowed 
- dpkg --configure -a 
+ allowed
+ dpkg --configure -a
  to succeed
  
  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
  Date: Mon May 25 11:01:36 2020
  ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 
zwrócił kod błędu 1
  InstallationDate: Installed on 2017-10-18 (949 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic 
root=UUID=1c3374a5-d07b-4588-8159-7607318eb2c9 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: podproces 
zainstalowany pakiet udev skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: Upgraded to focal on 2020-05-25 (0 days ago)
  dmi.bios.date: 07/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.80
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.80:bd07/18/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: podproces
  zainstalowany pakiet udev skrypt post-installation returned error code
  1

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New

Bug description:
  [impact]

  during upgrade, udev may fail to configure, interrupting the upgrade

  [test case]

  on 18.04, create a non-system group 'kvm', then upgrade to 20.04

  [regression potential]

  any regression would likely result in a kvm group that was not
  properly created, possibly restricting users from using kvm
  acceleration until the problem was fixed.

  [scope]

  this is needed only for focal, as it occurs only on upgrade to focal.

  [original description]

  
  During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to configure 
interrupting the upgrade.

  dpkg complained that kvm already exist but it is not a system group.

  From what I saw my user was the only member of kvm group
  I don't recall installing kvm manually but I do have Android emulator 
installed so it is possible that it is related.

  Removing kvm group via
  groupdel kvm
  allowed
  dpkg --configure -a
  to succeed

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 56-hpmud.rules 70-snap.core.rules
  Date: Mon May 25 11:01:36 2020
  ErrorMessage: podproces zainstalowany pakiet udev skrypt post-installation 

[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-06 Thread Dan Streetman
** Description changed:

  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.
  
  One event is from intel-hid and the other one is from hp-wireless.
  
  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.
  
  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.
  
  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.
+ 
+ any regression would likely result in missed rfkill events.
+ 
+ [scope]
+ 
+ this is fixed upstream by commit
+ d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
+ version yet, so this is needed for f and g.
+ 
+ @kaihengfeng is this needed on b and/or x as well?

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

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


[Touch-packages] [Bug 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

2020-07-06 Thread Kai-Chuan Hsieh
** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+subscriptions

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


[Touch-packages] [Bug 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

2020-07-06 Thread Kai-Heng Feng
I think we can skip B/X, I haven't seen any wireless hotkey bug report
for these two series.

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+subscriptions

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


Re: [Touch-packages] [Bug 1886573] Re: Graphics driver issue

2020-07-06 Thread Sarwat Firoz
Hey Daniel,

Thank you so much for your quick response.

I have understood it can't be updated. The information was fetched.

I have marked the bug inactive. I will close it.

Thanks & Regards,

Sarwat Firoz


On Tue, 7 Jul 2020, 07:30 Daniel van Vugt, <1886...@bugs.launchpad.net>
wrote:

> It appears you have an Intel GPU so there is no supported way to update
> the graphics driver.
>
> Instead, please tell us what kind of problem you are experiencing.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1886573
>
> Title:
>   Graphics driver issue
>
> Status in xorg package in Ubuntu:
>   Invalid
>
> Bug description:
>   Graphics driver issue. I can't fetch info. I can't update it.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
>   Uname: Linux 5.4.0-37-generic x86_64
>   NonfreeKernelModules: wl
>   ApportVersion: 2.20.11-0ubuntu27.3
>   Architecture: amd64
>   BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
>   CasperMD5CheckResult: skip
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jul  7 01:21:30 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   DkmsStatus:
>acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
>bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
>tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Intel Corporation Core Processor Integrated Graphics Controller
> [8086:0046] (rev 02) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo Core Processor Integrated Graphics Controller
> [17aa:3920]
>   InstallationDate: Installed on 2020-06-20 (16 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   MachineType: LENOVO 20042
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic
> root=UUID=575bc930-4ddd-48a7-bab4-a8aeb466b45b ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 02/02/2012
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 29CN41WW(V2.18)
>   dmi.board.asset.tag: Base Board Asset Tag
>   dmi.board.name: Base Board Product Name
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Base Board Version
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnLENOVO:bvr29CN41WW(V2.18):bd02/02/2012:svnLENOVO:pn20042:pvrLenovoG560:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.family: Intel_Mobile
>   dmi.product.name: 20042
>   dmi.product.sku: Calpella_CRB
>   dmi.product.version: Lenovo G560
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1886573/+subscriptions
>

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

Title:
  Graphics driver issue

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Graphics driver issue. I can't fetch info. I can't update it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul  7 01:21:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-37-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:3920]
  

[Touch-packages] [Bug 1877216] Re: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

2020-07-06 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Problem keeps appearing when video is played. video keeps playing but
  no sound is heard thru headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ernest 1095 F pulseaudio
   /dev/snd/controlC1:  ernest 1095 F pulseaudio
   /dev/snd/controlC0:  ernest 1095 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 09:55:52 2020
  InstallationDate: Installed on 2020-04-25 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ernest 1095 F pulseaudio
   /dev/snd/controlC1:  ernest 1095 F pulseaudio
   /dev/snd/controlC0:  ernest 1095 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-VDH MAX (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 8.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 8.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 8.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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