[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Daniel van Vugt]

Since this bug is closed, please open new bugs for any ongoing issues.
Just run:

  ubuntu-bug pulseaudio

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

-- 
Mailing list: https://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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Matthew M. Dean]

I still get this issue even on focal, or atleast the fix is the same. I
have a USB headset and upon reboot it always switches to the USB headset
regardless if HDMI was selected last. It's a desktop so things don't get
unplugged.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

-- 
Mailing list: https://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 1855445] Re: Touchpad is not working

[Launchpad Bug Tracker]

[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Touchpad is not working

Status in unattended-upgrades package in Ubuntu:
  Expired

Bug description:
  Day before yesterday, I updated Ubuntu in my laptop, then the next
  morning when I try to use touch-pad it wasn't working, I switched to
  windows to see whether touch-pad was working or not, it was working
  fine. Here's the details

  $ xinput

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ Synaptics TM3252-001id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Logitech USB Receiver   id=10   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=12   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=14   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Logitech USB Receiver   id=18   [slave  
keyboard (3)]

  $ dmesg | grep i2c

  [0.766631] i2c /dev entries driver
  [2.419114] psmouse serio1: synaptics: Your touchpad (PNP: SYN0609 
PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not 
used, you might want to try setting psmouse.synaptics_intertouch to 1 and 
report this to linux-in...@vger.kernel.org.
  [   34.129216] i2c_hid i2c-DELL0792:00: i2c-DELL0792:00 supply vdd not found, 
using dummy regulator
  [   34.837858] input: Synaptics TM3252-001 as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-DELL0792:00/0018:06CB:7F09.0003/input/input13
  [   34.837945] hid-rmi 0018:06CB:7F09.0003: input,hidraw2: I2C HID v1.00 
Mouse [DELL0792:00 06CB:7F09] on i2c-DELL0792:00

  $ locate i2c-designware

  /lib/modules/4.15.0-70-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko
  /lib/modules/4.15.0-72-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko
  /usr/src/linux-headers-4.15.0-70/include/linux/platform_data/i2c-designware.h
  /usr/src/linux-headers-4.15.0-72/include/linux/platform_data/i2c-designware.h

  $ uname -a

  Linux ubuntu-vostro-14-3468 4.15.0-72-generic #81-Ubuntu SMP Tue Nov
  26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  $ lsb_release -crid

  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

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

-- 
Mailing list: https://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 1867712] Re: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 127
  Processing triggers for linux-image-unsigned-5.4.0-18-generic (5.4.0-18.22) 
...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic
  /usr/sbin/mkinitramfs: 88: .: Can't open 
/usr/share/initramfs-tools/scripts/functions
  update-initramfs: failed for /boot/initrd.img-5.4.0-18-generic with 127.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
  dpkg: error processing package linux-image-unsigned-5.4.0-18-generic 
(--configure):
   installed linux-image-unsigned-5.4.0-18-generic package post-installation 
script subprocess returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
   linux-image-unsigned-5.4.0-18-generic

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Tue Mar 17 08:59:49 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2020-01-09 (67 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.10
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-02-13 (32 days ago)

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

-- 
Mailing list: https://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 1867712] [NEW] package initramfs-tools 0.136ubuntu1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 12

[doxa]

Public bug reported:

dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 127
Processing triggers for linux-image-unsigned-5.4.0-18-generic (5.4.0-18.22) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic
/usr/sbin/mkinitramfs: 88: .: Can't open 
/usr/share/initramfs-tools/scripts/functions
update-initramfs: failed for /boot/initrd.img-5.4.0-18-generic with 127.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
dpkg: error processing package linux-image-unsigned-5.4.0-18-generic 
(--configure):
 installed linux-image-unsigned-5.4.0-18-generic package post-installation 
script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
 linux-image-unsigned-5.4.0-18-generic

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
Date: Tue Mar 17 08:59:49 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 127
InstallationDate: Installed on 2020-01-09 (67 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.10
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 127
UpgradeStatus: Upgraded to focal on 2020-02-13 (32 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 127
  Processing triggers for linux-image-unsigned-5.4.0-18-generic (5.4.0-18.22) 
...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic
  /usr/sbin/mkinitramfs: 88: .: Can't open 
/usr/share/initramfs-tools/scripts/functions
  update-initramfs: failed for /boot/initrd.img-5.4.0-18-generic with 127.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
  dpkg: error processing package linux-image-unsigned-5.4.0-18-generic 
(--configure):
   installed linux-image-unsigned-5.4.0-18-generic package post-installation 
script subprocess returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
   linux-image-unsigned-5.4.0-18-generic

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Tue Mar 17 08:59:49 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2020-01-09 (67 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.10
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 127
  UpgradeStatus: Upgraded to focal on 2020-02-13 (32 days ago)

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

-- 
Mailing list: https://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 1867655] Re: cannot run windows programs on playonlinux program especially empire earth 2 which it opens the program but the mouse cursor hangs

[Daniel van Vugt]

** Summary changed:

- intel graphics drivers ubuntu 16.04 32bit
+ cannot run windows programs on playonlinux program especially empire earth 2 
which it opens the program but the mouse cursor hangs

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

Title:
  cannot run windows programs on playonlinux program especially empire
  earth 2 which it opens the program but the mouse cursor hangs

Status in playonlinux package in Ubuntu:
  New

Bug description:
  cannot run windows programs on playonlinux program especially empire
  earth 2 which it opens the program but the mouse cursor hangs

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-88-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar 16 20:13:03 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
  InstallationDate: Installed on 2016-02-11 (1495 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Dell Inc. Latitude E6400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=64a984b3-0627-4713-99e8-1ed3743886ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0RX493
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/17/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 238335] Re: Too many obsolete panel directories in ~/.gconf/apps

[Alberts Muktupāvels]

** Changed in: gnome-panel (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Too many obsolete panel directories in ~/.gconf/apps

Status in GNOME Panel:
  Fix Released
Status in gconf package in Ubuntu:
  Invalid
Status in gconf-editor package in Ubuntu:
  Invalid
Status in gnome-panel package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-panel

  Old (obsolete) gnome panel entries in gconf-editor never get deleted.
  If a user has more than the original two panels at one time, then decides to 
delete a few of them (say they had 5 customized panels, and bringing it down to 
1), the system warns the user that all the settings will be lost. Which is what 
they want.
  But all the deleted panel entries are still located in /apps/panel/toplevels.
  Furthermore, opening ~/.gconf/apps/panel will list all those previous entries.
  They're not loaded when the user starts gnome, but they are nonetheless 
present in that location.
  This situation can get a little overwhelming when a user is used to deleting 
panels and creating new ones frequently (since that's easier than to remove 
every single item on the panel individually).
  For example, I currently have 15 different toplevels which settings I can 
change in gconf-editor, although i only have 2 panels total on my desktop 
(panels 5 and 15). All the others, 1-4 + 6 - 14 are obsolete. Every time I 
massively delete/add new panels, I find myself having to hunt down the 
toplevels listings and playing with the settings to see which panels are the 
ones I actually have available.
  This turn, I only had to do this 15 times... What will I do when the number 
of entries get to 50? 100? 150?
  This situation is just one major headache waiting to happen.

  NOTE: Let me clarify, saying that I _never_ had 15 panels at once at
  any one time on my desktop. Old and obsolete panel entries are not
  overwritten by new ones, which would curb the growth time of the
  problem at the very least; they are still there, taking up space, and
  new ones need to be created.

  I'll end this with a question: At the beginning, notice that i said
  that the system warns you that all your settings for whichever panel
  you are trying to delete will be lost/removed. That prompt makes the
  user falsely assume that the panel entries are indeed deleted. If so,
  why are they still in ~/.gconf/apps/panel ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-panel/+bug/238335/+subscriptions

-- 
Mailing list: https://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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Hui Wang]

@sil2100, it is good to go, please release it.

thx.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

-- 
Mailing list: https://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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Guillaume Martres]

Someone is working on adding wideband support to pulseaudio (this
currently requires ofono):
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/254

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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

[Sebastien Bacher]

** Changed in: libarchive (Ubuntu Disco)
   Status: Triaged => Won't Fix

-- 
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:
  Triaged
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 1867390] Re: Update libarchive to 3.4.2

[Amr Ibrahim]

** Description changed:

- Please update libarchive to 3.4.2.
+ Please update libarchive to 3.4.2, also fixes LP: #1814109.
+ 
+ The bug and security fixes outweighs the new features added in 3.4.1 and
+ 3.4.2.
  
  https://github.com/libarchive/libarchive/releases
  
  Libarchive 3.4.2 is a feature and security release.
  
  New features:
  
  support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
  support for mbed TLS (PolarSSL) (#1301)
  
  Important bugfixes:
  
  security fixes in RAR5 reader (#1280 #1326)
  compression buffer fix in XAR writer (#1317)
  fix uname and gname longer than 32 characters in PAX writer (#1319)
  fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
- fix support for extracting 7z archive entries with Delta filter (#987)
- 
+ fix support for extracting 7z archive entries with Delta filter (fixes LP: 
#1814109) (#987)
  
  Libarchive 3.4.1 is a feature and security release.
  
  New features:
  
  Unicode filename support for reading lha/lzh archives
  New pax write option "xattrhdr"
  
  Important bugfixes:
  
  security fixes in wide string processing (#1276 #1298)
  security fixes in RAR5 reader (#1212 #1217 #1296)
  security fixes and optimizations to write filter logic (#351)
  security fix related to use of readlink(2) (1dae5a5)
  sparse file handling fixes (#1218 #1260)

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

Title:
  Update libarchive to 3.4.2

Status in libarchive package in Ubuntu:
  Triaged
Status in libarchive package in Debian:
  Unknown

Bug description:
  Please update libarchive to 3.4.2, also fixes LP: #1814109.

  The bug and security fixes outweighs the new features added in 3.4.1
  and 3.4.2.

  https://github.com/libarchive/libarchive/releases

  Libarchive 3.4.2 is a feature and security release.

  New features:

  support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
  support for mbed TLS (PolarSSL) (#1301)

  Important bugfixes:

  security fixes in RAR5 reader (#1280 #1326)
  compression buffer fix in XAR writer (#1317)
  fix uname and gname longer than 32 characters in PAX writer (#1319)
  fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
  fix support for extracting 7z archive entries with Delta filter (fixes LP: 
#1814109) (#987)

  Libarchive 3.4.1 is a feature and security release.

  New features:

  Unicode filename support for reading lha/lzh archives
  New pax write option "xattrhdr"

  Important bugfixes:

  security fixes in wide string processing (#1276 #1298)
  security fixes in RAR5 reader (#1212 #1217 #1296)
  security fixes and optimizations to write filter logic (#351)
  security fix related to use of readlink(2) (1dae5a5)
  sparse file handling fixes (#1218 #1260)

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

-- 
Mailing list: https://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

[Amr Ibrahim]

The fix is in 3.4.2 update request LP: #1867390.

-- 
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:
  Triaged
Status in libarchive source package in Disco:
  Triaged

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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

[Łukasz Zemczak]

Hui, does this mean the current SRU shouldn't be released? Or is it
still good to go?

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

-- 
Mailing list: https://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 1797734] Re: slow calculator startup

[Paul Smith]

Hey, if my assertion incentivizes someone to figure out how to do that,
I'm more than willing to admit I was wrong :).

The thing is, IMO "fast enough" for a desktop calculator is pretty darn
fast.  In my opinion the current integrated DEB version is already slow
enough to be frustrating, so there's plenty of work in this area without
even considering the issue of snaps.  People just don't expect to have
to wait for a calculator on their computer: isn't calculating the thing
that computers were built for and are best at?!

I'm not suggesting we should do something like waste users' memory by
preloading the calculator app just so it can be ready to display a
window quickly, though.  In reality probably not enough people use the
app often enough to justify that.

Cheers!

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

Title:
  slow calculator startup

Status in gnome-calculator package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  The calculator starts very slowly. It's a tiny program, but it runs
  like a very big one. In previous versions of Ubuntu, the launch was
  normal, very fast.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 14 08:40:06 2018
  InstallationDate: Installed on 2018-05-06 (160 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session

[naisanza]

`sudo killall -9 gdm` immediately fixes the "unresponsive" problem for
me. But you have to SSH into the box to do this, which is an extreme
bandaid

The screen remains blank even moving the mouse around for a few minutes,
and pressing ESC a couple times.

The monitor shows as "no input"

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

Title:
  black screen, unresponsive, after logout from gnome Wayland session

Status in gdm3 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  on logout the screen is black, the system is unresponsive and has to
  be restarted. (Untested by me yet, but I expect ssh-ing in and
  restarting gdm would work.)

  I believe this may be already reported upstream here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've
  reported this against gdm3 even though I honestly don't know if it
  might be a gnome-shell, gnome-session or mutter based error. (FWIW
  without the upstream bug to link to I'd maybe suspect gnome-shell
  first.)

  NB: This machine's conf has AutomaticLogin enabled, but another
  machine also on 19.10 does not, and it's showing the same thing. On
  *this* machine I found that the *first* time I logged out, it was OK,
  but not the second time. On the other machine, it fails first time
  too. It's as if the gdm login screen can appear exactly once. That
  (and being on gnome 3.33) is why I don't think this is a dupe of
  #1824588.

  Nothing appears in /var/crash as a result of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 10:51:22 2019
  InstallationDate: Installed on 2018-09-11 (351 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641

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

-- 
Mailing list: https://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 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[corrado venturini]

Same problem on a different hardware
corrado@corrado-HP-p5-ff-0303:~$ inxi -SCGx
System:
  Host: corrado-HP-p5-ff-0303 Kernel: 5.4.0-14-generic x86_64 bits: 64
  compiler: gcc v: 9.2.1 Desktop: Gnome 3.35.91
  Distro: Ubuntu 20.04 LTS (Focal Fossa)
CPU:
  Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP
  arch: Haswell rev: 1 L2 cache: 3072 KiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 19156
  Speed: 1541 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 1197 2: 1198
  3: 1197 4: 1197
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard
  driver: i915 v: kernel bus ID: 00:02.0
  Display: x11 server: X.Org 1.20.7 driver: i915 resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2)
  v: 4.5 Mesa 20.0.0 direct render: Yes
corrado@corrado-HP-p5-ff-0303:~$

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1867081] Re: Password textbox misaligned with username

[Hans Joachim Desserud]

Thanks for taking your time to report this issue and help making Ubuntu
better.

I can confirm this issue, both based on your screenshot and what I see
on my own login screen. I'm fairly certain this is a duplicate and that
I've seen the same issue reported earlier, but I cannot find that report
right now.

Also, since I don't believe shadow deal with the graphical parts of
login, I've taken the liberty of moving this to gdm3. Feel free to move
again if this isn't the right place either :)


** Package changed: shadow (Ubuntu) => gdm3 (Ubuntu)

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

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

Title:
  Password textbox misaligned with username

Status in gdm3 package in Ubuntu:
  Confirmed

Bug description:
  When I wake my computer and login the textbox for the password is
  aligned slightly to the right.

  Ubuntu 20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: login 1:4.8.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 21:55:27 2020
  InstallationDate: Installed on 2020-03-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200310)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1867655] [NEW] intel graphics drivers ubuntu 16.04 32bit

[James Anthony]

Public bug reported:

cannot run windows programs on playonlinux program especially empire
earth 2 which it opens the program but the mouse cursor hangs

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-88-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: i386
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Mar 16 20:13:03 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
InstallationDate: Installed on 2016-02-11 (1495 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
MachineType: Dell Inc. Latitude E6400
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=64a984b3-0627-4713-99e8-1ed3743886ff ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0RX493
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/17/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

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

Title:
  intel graphics drivers ubuntu 16.04 32bit

Status in xorg package in Ubuntu:
  New

Bug description:
  cannot run windows programs on playonlinux program especially empire
  earth 2 which it opens the program but the mouse cursor hangs

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-88.88~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-88-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: i386
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Mar 16 20:13:03 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0233]
  InstallationDate: Installed on 2016-02-11 (1495 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release i386 (20180228)
  MachineType: Dell Inc. Latitude E6400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic 
root=UUID=64a984b3-0627-4713-99e8-1ed3743886ff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0RX493
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1867653] [NEW] apt --fix-broken-install thinks I have other options and fails

[fcole90]

Public bug reported:

If I run `sudo apt --fix-broken-install` I receive

```
E: Command line option --fix-broken-install is not understood in combination 
with the other options
```

even if I don't have any other option.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 1.9.10
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Mar 16 19:00:14 2020
InstallationDate: Installed on 2019-02-03 (406 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  apt --fix-broken-install thinks I have other options and fails

Status in apt package in Ubuntu:
  New

Bug description:
  If I run `sudo apt --fix-broken-install` I receive

  ```
  E: Command line option --fix-broken-install is not understood in combination 
with the other options
  ```

  even if I don't have any other option.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 1.9.10
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Mar 16 19:00:14 2020
  InstallationDate: Installed on 2019-02-03 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1867390] Re: Update libarchive to 3.4.2

[Sebastien Bacher]

Thank, when request a version update afer feature freeze please state
why you think that update should be done despite the freeze

Note that it has been reported to Debian also and is being worked there
but non trivial, see https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=953553

** Bug watch added: Debian Bug tracker #953553
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953553

** Changed in: libarchive (Ubuntu)
   Importance: Undecided => Wishlist

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

** Also affects: libarchive (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953553
   Importance: Unknown
   Status: Unknown

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

Title:
  Update libarchive to 3.4.2

Status in libarchive package in Ubuntu:
  Triaged
Status in libarchive package in Debian:
  Unknown

Bug description:
  Please update libarchive to 3.4.2.

  https://github.com/libarchive/libarchive/releases

  Libarchive 3.4.2 is a feature and security release.

  New features:

  support for atomic file extraction (bsdtar -x --safe-writes) (#1289)
  support for mbed TLS (PolarSSL) (#1301)

  Important bugfixes:

  security fixes in RAR5 reader (#1280 #1326)
  compression buffer fix in XAR writer (#1317)
  fix uname and gname longer than 32 characters in PAX writer (#1319)
  fix segfault when archiving hard links in ISO9660 and XAR writers (#1325)
  fix support for extracting 7z archive entries with Delta filter (#987)

  
  Libarchive 3.4.1 is a feature and security release.

  New features:

  Unicode filename support for reading lha/lzh archives
  New pax write option "xattrhdr"

  Important bugfixes:

  security fixes in wide string processing (#1276 #1298)
  security fixes in RAR5 reader (#1212 #1217 #1296)
  security fixes and optimizations to write filter logic (#351)
  security fix related to use of readlink(2) (1dae5a5)
  sparse file handling fixes (#1218 #1260)

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

-- 
Mailing list: https://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 1867607] Re: fail to reinstall all packages together in minimized builds

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.655

---
livecd-rootfs (2.655) focal; urgency=medium

  * minimized: reinstall packages one by one, instead of all of them
together, as otherwise apt fails to immediately configure libc6:amd64
& libgcc-s1. LP: #1867607

 -- Dimitri John Ledkov   Mon, 16 Mar 2020 10:42:35
+

** Changed in: livecd-rootfs (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  fail to reinstall all packages together in minimized builds

Status in apt package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  Chroot chroot dpkg-query -f '${binary:Package}\n' -W | Chroot chroot
  xargs apt-get install --reinstall

  Fails in focal with:

  
  Processing triggers for libc-bin (2.31-0ubuntu6) ...
  E: Could not configure 'libc6:amd64'. 
  E: Could not perform immediate configuration on 'libgcc-s1:amd64'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  As seen at https://launchpadlibrarian.net/469223856
  /buildlog_ubuntu_focal_amd64_ubuntu-base_BUILDING.txt.gz

  doing `xargs -L1` makes it complete. I am not sure if there is
  somekind of an apt bug there. Imho reinstalling all the packages
  should just work fine

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

-- 
Mailing list: https://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 1867157] Re: Improve command-not-found package headers

[Launchpad Bug Tracker]

This bug was fixed in the package python3.8 - 3.8.2-1ubuntu1

---
python3.8 (3.8.2-1ubuntu1) focal; urgency=medium

  * Add XB-Cnf-Visible-Pkgname header on the python*-minimal package to
point command-not-found at the full one. LP: #1867157

 -- Dimitri John Ledkov   Fri, 13 Mar 2020 10:14:16
+

** Changed in: python3.8 (Ubuntu)
   Status: New => Fix Released

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

Title:
  Improve command-not-found package headers

Status in python-defaults package in Ubuntu:
  New
Status in python2.7 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in python3.8 package in Ubuntu:
  Fix Released

Bug description:
  Improve command-not-found package headers

  
  command-not-found uses package metadata, and to improve the UX of the 
misspelled commands / proposed packages.

  python2.7-minimal should gain XB-Cnf-Visible-Pkgname: python2.7

  python3.8-minimal should gain XB-Cnf-Visible-Pkgname: python3.8

  python2-minimal should gain XB-Cnf-Visible-Pkgname: python2

  python3-minimal should gain XB-Cnf-Visible-Pkgname: python3

  This will then improve these messages from:

  """
command 'python2.7' from deb python2.7-minimal (2.7.17-1)
command 'python3.8' from deb python3.8-minimal (3.8.0-5)
command 'python2' from deb python2-minimal (2.7.17-2)
command 'python3' from deb python3-minimal (3.7.5-1ubuntu1)
  """

  To

  """
command 'python2.7' from deb python2.7 (2.7.17-1)
command 'python3.8' from deb python3.8 (3.8.0-5)
command 'python2' from deb python2 (2.7.17-2)
command 'python3' from deb python3 (3.7.5-1ubuntu1)
  """

  
  python3 should drop
  XB-Cnf-Extra-Commands: python
  XB-Cnf-Priority-Bonus: 5

  Such that it stops suggesting that somehow python is available from
  python3 package, which is a lie.

  There is a special case for "python" command hint in command-not-found
  already, which simply points people to "python3".

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

-- 
Mailing list: https://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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

[Launchpad Bug Tracker]

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

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

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Gunnar Hjalmarsson]

Ok, thanks. Since LightDM is not the default DM on Ubuntu 18.04, I set
the importance of this bug to "Low".

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

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

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Borys Sidoruk]

Problem like I described is on LightDM. When I changed to gdm3, problem
is gone.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Gunnar Hjalmarsson]

So did you replace GDM with LightDM on your Ubuntu installs? If you
didn't, this may actually be a gnome-shell and/or gdm3 issue. Please
clarify.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1867372] Re: Auditd failed when changing the Rsyslog configuration

[Dmitriy Kulikov]

After many experiments, I discovered an inconspicuous syntax error in 
audit.rules
Here are two seemingly identical lines:
-a exit,always -F arch=b64 -F euid=0 -S execve –k root_actions
-a exit,always -F arch=b64 -F euid=0 -S execve -k root_actions

Their only difference is that in the first line (copy-pasted from another 
source), the dash before "–k" is not the standard dash character, although it 
appears exactly the same in the console.
When changing to a standard dash, the mentioned error is "error in line 6 of 
/etc/audit/audit.rules" was eliminated.

I absolutely don`t understand the role of Rsyslog configuration changes
in this. But paradoxically, this error in the dash character only
manifests itself in this case. Before that, a string with a non-standard
dash in audit.rules was accepted by auditd without problems on both my
servers.

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

Title:
  Auditd failed when changing the Rsyslog configuration

Status in audit package in Ubuntu:
  New

Bug description:
  I found that when changing the Rsyslog configuration 
(/etc/rsyslog.d/50-default.conf) an Auditd failure occurs with distinctive 
strings in syslog:
  ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE)
  .
  There was an error in line 6 of /etc/audit/audit.rules

  
  Other sign:
  
  # systemctl status auditd
  ● auditd.service - Security Auditing Service
 Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2020-03-13 17:49:55 MSK; 12min ago
   Docs: man:auditd(8)
 https://github.com/linux-audit/audit-documentation
Process: 985 ExecStartPost=/sbin/augenrules --load (code=exited, 
status=1/FAILURE)
Process: 883 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS)
   Main PID: 928 (auditd)
  Tasks: 4 (limit: 4915)
 CGroup: /system.slice/auditd.service
 ├─928 /sbin/auditd
 └─932 /sbin/audispd

  
  The problem was confirmed on two modern physical Linux Ubuntu servers with 
all the latest system updates.
  Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-88-generic x86_64)
  ---
  auditd/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed]
  libaudit-common/bionic,bionic,now 1:2.8.2-1ubuntu1 all [installed]
  libaudit1/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed]
  +
  rsyslog/bionic,now 8.32.0-1ubuntu4 amd64 [installed,automatic]

  
  The first time I found a problem trying to reconfigure Auditd logging 
according to the recommendations:
  
https://serverfault.com/questions/792766/what-is-the-syslog-facility-for-auditd-logs
  When I found the problem, I checked its causes on the Rsyslog side on another 
server.
  It is confirmed that it is not associated with changes in the configuration 
of Auditd.

  
  Example of replication: 
  ---
  1. Edit /etc/rsyslog.d/50-default.conf
  Insert strings for new log facility:
  *.*;auth,authpriv.none,cron.none,mail.none,local5.none,local6.none
-/var/log/syslog
  ###
  ###*.*;auth,authpriv.none,cron.none,mail.none,local5.none 
-/var/log/syslog

  local6.*
  /var/log/audit/audit_syslog.log

  2. # systemctl restart rsyslog

  3. # systemctl restart auditd

  4. # systemctl status auditd
  ● auditd.service - Security Auditing Service
 Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Fri 2020-03-13 18:12:32 MSK; 6s ago
   Docs: man:auditd(8)
 https://github.com/linux-audit/audit-documentation
Process: 3211 ExecStartPost=/sbin/augenrules --load (code=exited, 
status=1/FAILURE)
Process: 3183 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS)
   Main PID: 3186 (auditd)
  Tasks: 4 (limit: 4915)
 CGroup: /system.slice/auditd.service
 ├─3186 /sbin/auditd
 └─3190 /sbin/audispd

  Mar 13 18:12:32 uk1 augenrules[3211]: failure 1
  Mar 13 18:12:32 uk1 augenrules[3211]: pid 3186
  Mar 13 18:12:32 uk1 augenrules[3211]: rate_limit 0
  Mar 13 18:12:32 uk1 augenrules[3211]: backlog_limit 8192
  Mar 13 18:12:32 uk1 augenrules[3211]: lost 0
  Mar 13 18:12:32 uk1 augenrules[3211]: backlog 0
  Mar 13 18:12:32 uk1 augenrules[3211]: backlog_wait_time 0
  Mar 13 18:12:32 uk1 systemd[1]: Started Security Auditing Service.
  Mar 13 18:12:32 uk1 auditctl[3225]: There was an error in line 6 of 
/etc/audit/audit.rules
  Mar 13 18:12:32 uk1 audispd[3190]: node=uk1 type=SERVICE_START 
msg=audit(1584112352.783:142): pid=1 uid=0 auid=4294967295 ses=4294967295 
msg='unit=auditd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? 
terminal=? res=success'

  
  But the main problem is that this failure cannot be fixed by deleting changes 
from the Rsyslog 

Re: [Touch-packages] [Bug 1770961] Re: Add options to set the snappy refresh schedule

[dee bee]

On Thu, Mar 5, 2020 at 12:35 PM Ads2 <1770...@bugs.launchpad.net> wrote:
>
> Another piece of documentation refers to all the options around snap
> refreshes: https://snapcraft.io/docs/keeping-snaps-up-to-date
>
> These include holding refreshes when the connection is metered and
> manual holds (specific delay of an update exceptional to the usual
> refresh schedule set by the user).
>
> Popey's video at https://youtu.be/gVZOBgTDJWc?t=514 is also helpful for
> understanding all the options now available for controlling snap
> updates.
>

All the options but the most useful one - - - - - the OFF switch!

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Borys Sidoruk]

My bad, its GNOME.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1867607] Re: fail to reinstall all packages together in minimized builds

[Dimitri John Ledkov]

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Committed

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

Title:
  fail to reinstall all packages together in minimized builds

Status in apt package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Committed

Bug description:
  Chroot chroot dpkg-query -f '${binary:Package}\n' -W | Chroot chroot
  xargs apt-get install --reinstall

  Fails in focal with:

  
  Processing triggers for libc-bin (2.31-0ubuntu6) ...
  E: Could not configure 'libc6:amd64'. 
  E: Could not perform immediate configuration on 'libgcc-s1:amd64'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  As seen at https://launchpadlibrarian.net/469223856
  /buildlog_ubuntu_focal_amd64_ubuntu-base_BUILDING.txt.gz

  doing `xargs -L1` makes it complete. I am not sure if there is
  somekind of an apt bug there. Imho reinstalling all the packages
  should just work fine

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

-- 
Mailing list: https://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 1867607] [NEW] fail to reinstall all packages together in minimized builds

[Dimitri John Ledkov]

Public bug reported:

Chroot chroot dpkg-query -f '${binary:Package}\n' -W | Chroot chroot
xargs apt-get install --reinstall

Fails in focal with:


Processing triggers for libc-bin (2.31-0ubuntu6) ...
E: Could not configure 'libc6:amd64'. 
E: Could not perform immediate configuration on 'libgcc-s1:amd64'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

As seen at https://launchpadlibrarian.net/469223856
/buildlog_ubuntu_focal_amd64_ubuntu-base_BUILDING.txt.gz

doing `xargs -L1` makes it complete. I am not sure if there is somekind
of an apt bug there. Imho reinstalling all the packages should just work
fine

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

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Status: New

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

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

Title:
  fail to reinstall all packages together in minimized builds

Status in apt package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  Chroot chroot dpkg-query -f '${binary:Package}\n' -W | Chroot chroot
  xargs apt-get install --reinstall

  Fails in focal with:

  
  Processing triggers for libc-bin (2.31-0ubuntu6) ...
  E: Could not configure 'libc6:amd64'. 
  E: Could not perform immediate configuration on 'libgcc-s1:amd64'. Please see 
man 5 apt.conf under APT::Immediate-Configure for details. (2)

  As seen at https://launchpadlibrarian.net/469223856
  /buildlog_ubuntu_focal_amd64_ubuntu-base_BUILDING.txt.gz

  doing `xargs -L1` makes it complete. I am not sure if there is
  somekind of an apt bug there. Imho reinstalling all the packages
  should just work fine

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

-- 
Mailing list: https://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 1867581] Lsusb-t.txt

[corrado venturini]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337474/+files/Lsusb-t.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] Lsusb-v.txt

[corrado venturini]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337475/+files/Lsusb-v.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] xdpyinfo.txt

[corrado venturini]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337485/+files/xdpyinfo.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] XorgLog.txt

[corrado venturini]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337482/+files/XorgLog.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] XorgLogOld.txt

[corrado venturini]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337483/+files/XorgLogOld.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] UdevDb.txt

[corrado venturini]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1867581/+attachment/5337481/+files/UdevDb.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] Xrandr.txt

[corrado venturini]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1867581/+attachment/5337484/+files/Xrandr.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] ProcEnviron.txt

[corrado venturini]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337478/+files/ProcEnviron.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] ProcModules.txt

[corrado venturini]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337480/+files/ProcModules.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] ProcInterrupts.txt

[corrado venturini]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337479/+files/ProcInterrupts.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] ProcCpuinfoMinimal.txt

[corrado venturini]

apport information

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

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] Lsusb.txt

[corrado venturini]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1867581/+attachment/5337473/+files/Lsusb.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] ProcCpuinfo.txt

[corrado venturini]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337476/+files/ProcCpuinfo.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] Re: Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[corrado venturini]

apport information

** Tags added: apport-collected focal reproducible single-occurrence
ubuntu

** Description changed:

  ubuntu-bug mesa does not work, i don't see a package named mesa
  
  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.
  
  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$
  
  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu20
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDesktop: ubuntu:GNOME
+ DistUpgraded: Fresh install
+ DistroCodename: focal
+ DistroRelease: Ubuntu 20.04
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
+Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
+ InstallationDate: Installed on 2020-03-09 (6 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: mesa (not installed)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
+ Tags:  focal ubuntu single-occurrence reproducible
+ Uname: Linux 5.4.0-14-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/11/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.10
+ dmi.board.name: H110M-G/M.2
+ 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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.100-4
+ version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
+ version.libgl1-mesa-glx: libgl1-mesa-glx N/A
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337470/+files/CurrentDmesg.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: 

[Touch-packages] [Bug 1867581] DpkgLog.txt

[corrado venturini]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1867581/+attachment/5337471/+files/DpkgLog.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867581] Lspci.txt

[corrado venturini]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1867581/+attachment/5337472/+files/Lspci.txt

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2020-03-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: mesa (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=4d1039f0-80c2-4131-b9f9-31f9bf0173f7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Tags:  focal ubuntu single-occurrence reproducible
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  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.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1770961] Re: Add options to set the snappy refresh schedule

[Matthew Paul Thomas]

A revision of the label I mentioned above has now been implemented:
“Snap package updates are checked routinely and installed
automatically.”

In  I wrote: “Sometimes I
design things in the hope that someone will implement them someday. I
haven’t had time to do that with this dialog. But if anyone here is
interested, a simple first step — useful and releasable by itself —
would be to add a caption below the new label, of the form ‘Last check:
Yesterday 16:27’. If someone submits a merge proposal to do that, then
I’ll design the next bit.”

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

Title:
  Add options to set the snappy refresh schedule

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Snappy has a feature where the user can state when in a month to
  refresh (update) their snaps. Please provide options in Software &
  Updates to control this.

  https://docs.snapcraft.io/system-options

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun May 13 15:10:07 2018
  InstallationDate: Installed on 2017-08-03 (282 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (21 days ago)

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

-- 
Mailing list: https://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 1865519] Re: apparmor depends on python3

[Samuele Pedroni]

** Changed in: snapd
   Status: Triaged => Invalid

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

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

Title:
  apparmor depends on python3

Status in snapd:
  Invalid
Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  The TL;DR;
  - AppArmor depends on python3 to support aa-status.
  - snapd depends on apparmor.
  - buildd images have no python
  - building snaps requires snapd
  - snapd does not require aa-status
  - building snaps unnecessarily installs python3 onto the system

  Proposal:
  - Split runtime requirements from apparmor into apparmor-minimal
  - have apparmor depend on apparmor-minimal
  - change snapd's dependency on apparmor to apparmor-minimal

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

-- 
Mailing list: https://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 1553669] Re: Annoying "call from" message when connecting Bose devices

[Daniel van Vugt]

As hinted in comment #8, disabling voice prompts on the Bose device may
help. To do that, press and hold the + and - buttons simultaneously
until you hear “voice prompts off.”

** Tags removed: artful wily
** Tags added: eoan focal

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

-- 
Mailing list: https://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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps

[Samuele Pedroni]

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

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

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

Title:
  ubuntu-bug doesn't know how to file bugs against snaps

Status in Snapcraft:
  New
Status in snapd:
  Triaged
Status in Snap Store:
  New
Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Hello, I had problems with subiquity in the focal live server install
  image. I tried to use 'ubuntu-bug subiquity' to report the bug, but
  ubuntu-bug apparently cannot file bug reports against snaps.

  This is frustrating that users need to know which portions of Ubuntu
  are delivered via debs, which portions are delivered by snaps, and try
  to find a way to report bugs correctly.

  ubuntu-bug should know how to report bugs for Canonical software.

  Thanks

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

-- 
Mailing list: https://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 1553669] Re: Annoying "call from" message when connecting Bose devices

[David Mortals]

This problem is still present in Ubuntu 20.04 (DEV).

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Gunnar Hjalmarsson]

That's distro... I think Marc asked about if you use Ubuntu with GNOME,
Xubuntu, Lubuntu, or Budgie etc.

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Borys Sidoruk]

We currently using few machines and issue exist on this ubuntu environment: 
Distribution: Ubuntu 18.04.3 LTS
Architecture: amd64
Running kernel: 4.15.0-88-generic
Kernel version: 4.15.0.88.88

Regarding to model machines: 
Dell Precision 5530
Dell Precision 5520
Dell Precision 5510
Precision Tower 3630,
Precision Tower 3620,
Dell Latitude 5400

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

-- 
Mailing list: https://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 1867581] [NEW] Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

[corrado venturini]

Public bug reported:

ubuntu-bug mesa does not work, i don't see a package named mesa

On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
shows the characters reduced to small rectangles and the image of the moon is 
empty.
On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
The problem happens with both sessions X11 and Wayland.
I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
and you may see the result of the malfunction on this page
but the problem seems due to mesa 20.

I have an intel CPU and Graphic unit
corrado@corrado-x5-ff-0309:~$ inxi -Gxx
Graphics:
  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
  bus ID: 00:02.0 chip ID: 8086:5912
  Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
  resolution: 1920x1080~60Hz
  OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
  direct render: Yes
corrado@corrado-x5-ff-0309:~$

I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
so now I'm opening this problem
if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug

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

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

Title:
  Mesa 20.0.0 causes malfunction to Virtual Moon Atlas

Status in mesa package in Ubuntu:
  New

Bug description:
  ubuntu-bug mesa does not work, i don't see a package named mesa

  On Ubuntu 20.04 with Mesa 20.0.0 the program atlun - Virtual Moon Atlas from 
https://sourceforge.net/projects/virtualmoon/
  shows the characters reduced to small rectangles and the image of the moon is 
empty.
  On Ubuntu 20.04 with Mesa 19.2.8 atlun had no problems.
  The problem happens with both sessions X11 and Wayland.
  I also opened a problem to atlun https://www.ap-i.net/mantis/view.php?id=2291
  and you may see the result of the malfunction on this page
  but the problem seems due to mesa 20.

  I have an intel CPU and Graphic unit
  corrado@corrado-x5-ff-0309:~$ inxi -Gxx
  Graphics:
Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel
bus ID: 00:02.0 chip ID: 8086:5912
Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell
resolution: 1920x1080~60Hz
OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.0.0
direct render: Yes
  corrado@corrado-x5-ff-0309:~$

  I asked a question for this problem: 
https://answers.launchpad.net/ubuntu/+question/689328
  so now I'm opening this problem
  if you suggest me the package name to be used opening the problem with 
ubuntu-bug i will open a new bug

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

-- 
Mailing list: https://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 1867575] Re: Unusual Home Screen Bug and Application Menu Bug(Refer video attachment))

[Daniel van Vugt]

Please reword this bug to cover a single issue and move the other issues
into new bug reports.

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

** Changed in: gnome-shell (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/1867575

Title:
  Unusual Home Screen Bug and Application Menu Bug(Refer video
  attachment))

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
  Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

  NOTE: Please find the video file attached to it as i have recorded it
  to help you reproduce the bug.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 11:28:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Apple Inc. MacBookPro9,2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 229.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867576] Re: Unusual Home Screen Bug and Application Menu Bug(Refer video attachment))

[Daniel van Vugt]

*** This bug is a duplicate of bug 1867575 ***
https://bugs.launchpad.net/bugs/1867575

** This bug has been marked a duplicate of bug 1867575
   Unusual Home Screen Bug and Application Menu Bug(Refer video attachment))

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

Title:
  Unusual Home Screen Bug and Application Menu Bug(Refer video
  attachment))

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
  Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

  NOTE: Please find the video file attached to it as i have recorded it
  to help you reproduce the bug.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 11:28:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fa]
  InstallationDate: Installed on 2020-03-14 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  MachineType: Apple Inc. MacBookPro9,2
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 229.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-6F01561E16C75D06
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-6F01561E16C75D06
  dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1867576] [NEW] Unusual Home Screen Bug and Application Menu Bug(Refer video attachment))

[Shubham Rajesh Kale]

Public bug reported:

Hello,
I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

NOTE: Please find the video file attached to it as i have recorded it to
help you reproduce the bug.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 11:28:24 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
InstallationDate: Installed on 2020-03-14 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
MachineType: Apple Inc. MacBookPro9,2
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2019
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 229.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal reproducible third-party-packages ubuntu

** Attachment added: "Bug produced and recording of the same is attached 
here.Please refer thankyou."
   
https://bugs.launchpad.net/bugs/1867576/+attachment/5337400/+files/Ubuntu_Display_Menu_Bug.mp4

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

Title:
  Unusual Home Screen Bug and Application Menu Bug(Refer video
  attachment))

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
  Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

  NOTE: Please find the video file attached to it as i have recorded it
  to help you reproduce the bug.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 11:28:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 

[Touch-packages] [Bug 1867575] [NEW] Unusual Home Screen Bug and Application Menu Bug(Refer video attachment))

[Shubham Rajesh Kale]

Public bug reported:

Hello,
I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

NOTE: Please find the video file attached to it as i have recorded it to
help you reproduce the bug.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 11:28:24 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa]
InstallationDate: Installed on 2020-03-14 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
MachineType: Apple Inc. MacBookPro9,2
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-18-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2019
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 229.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-6F01561E16C75D06
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro9,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-6F01561E16C75D06
dmi.modalias: 
dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro9,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal reproducible third-party-packages ubuntu

** Attachment added: "Bug produced and recording of the same is attached here."
   
https://bugs.launchpad.net/bugs/1867575/+attachment/5337382/+files/Ubuntu_Display_Menu_Bug.mp4

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

Title:
  Unusual Home Screen Bug and Application Menu Bug(Refer video
  attachment))

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,
  I have sent my dock position to the right side and also have auto-hide dock 
option enabled but still, the dock is not hiding as the way it is intended to 
and there is an unusual change in the clock on the top of the screen and the 
application and shortcuts that are pinned on the desktop.
  Moreover when I use show applications button the application icon resize 
themselves and have a shrinking animation when it happens please fix this issue.

  NOTE: Please find the video file attached to it as i have recorded it
  to help you reproduce the bug.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 16 11:28:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed