[Touch-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)

2021-01-21 Thread Daniel van Vugt
** Package changed: pulseaudio (Ubuntu) => alsa-ucm-conf (Ubuntu)

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

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

Title:
  sounds not working on Dell XPS 17 (9700)

Status in alsa-ucm-conf package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  My investigation process:

  Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds
  worked.

  I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm 
headphones,
  using linux-image-5.4.0-42-generic, I did not try blutooth.

  I sudo apt upgrade, dist-upgrade to get kernels

  linux-image-5.8.0-38-generic
  linux-image-5.8.0-40-generic

  Sounds did not work.
  I download linux-image-unsigned-5.10.9-051009-generic.
  Sounds did not work.

  I upgrade Dell XPS 9700 firmware from 1.3 to 1.63.
  Sounds did not work.

  After googling I found this solution in the comments:
  https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700

  """

  Download and install dkms module:

  https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem-
  dkms/+packages

  Alternatively, you can install linux-oem-20.04, it will install
  the 5.6 kernel with the above driver. Your system may be more stable
  with 5.4 kernel since it is in wide use.

  Manually install sof-firmware from Arch Linux:

  https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof-
  firmware-1.5.1-1-any.pkg.tar.zst.html

  You will need to delete the existing "sof" and "sof-tplg" files
  from the Ubuntu linux-firmware package first. Note if this package
  gets updated from Canoncial and they don't update these, you will have
  to delete and then reextract. Files go into the
  /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg
  folders.

  Manually install the ucm2 files:

  http://xps17.ddns.net/sof-soundwire.zip

  These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the
  contents of the existing sof-soundwire folder (if you have it) and
  replace them with the ones from the archive.

  Reboot. You should now have all your audio devices available. If speakers 
do not play, you may need to run alsamixer (non-root) from a terminal and 
unmute and set the mixer levels all the way up.
  """


  This solution worked for me on linux-image-5.6.0-1042-oem AFTER
  manually opening alsa-mixer and changing soundcard to sof. The sound
  would otherwise just show 'dummy'.

  My sounds still do not work on 5.8 or 5.10, full name listed above. I
  did not get to test this temporary fix with 5.4.

  my full alsa-info:
  http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff

  based on some google research, this seems to be a common problem:
  
https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/
  
https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/
  
https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/
  etc...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19
  Uname: Linux 5.6.0-1042-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  neoh   1786 F pulseaudio
   /dev/snd/pcmC1D0p:   neoh   1786 F...m pulseaudio
   /dev/snd/controlC0:  neoh   1786 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 21 12:08:45 2021
  InstallationDate: Installed on 2021-01-20 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0CXCCY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1912670] Re: Mouse buttons and keyboard unresponsive after idle time

2021-01-21 Thread Daniel van Vugt
Thanks for the bug report. This sounds a power management problem.

1. If you have 'tlp' installed the please uninstall it. It's known to
cause bugs like this.

2. Try installing 'powertop' and then look in its 'Tunables' section. By
changing some of those to 'Bad' (which is actually better than 'Good' in
this case) you can stop them suspending so much.

3. The kernel team should have some more ideas. I will move this bug
there...


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

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

Title:
  Mouse buttons and keyboard unresponsive after idle time

Status in linux package in Ubuntu:
  New

Bug description:
  If I leave my desktop (Xubuntu 20.04.1 LTS, Xfce xfdesktop4 4.14.2-1,
  Xorg 1:7.7+19ubuntu14) idle for a few minutes, the mouse buttons and
  most keyboard presses become unresponsive. My "system power saving"
  setting is disabled (set to "never") and "display power management" is
  set to blank after 15 minutes, but the problem seems to occur sooner
  than that. Unplugging and re-inserting the mouse after a few seconds
  has no effect.

  The only keystrokes that have any effect are Ctrl+Alt+F1 for a
  terminal session (where I can type normally). Returning to the desktop
  with Ctrl+Alt+F7 the mouse and keyboard remain unresponsive as before.
  This occurs with kernel 5.4.0-62, and I also installed the 5.4.0-26
  kernel and the problem happens with that too. When I reboot the
  machine everything works fine again, but after a few minutes of idle
  time, the same problem occurs again. I've only noticed the problem
  occurring in the last ~2-3 weeks.

  When I leave a terminal window open on the desktop running the command:
tail -f /var/log/Xorg.0.log
  and allow lots of time for the problem to occur, no lines are appended in the 
terminal even after the problem has happened, but when I then use Ctrl+Alt+F1 
and log in at the terminal console, the following additional lines appear in 
/var/log/xorg.0.log :
  [  3805.283] (II) event1  - Power Button: device removed
  [  3805.296] (II) event0  - Power Button: device removed
  [  3805.312] (II) event3  - Logitech USB Optical Mouse: device removed
  [  3805.344] (II) event4  - Eee PC WMI hotkeys: device removed
  [  3805.364] (II) event2  - AT Translated Set 2 keyboard: device removed

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78
  Uname: Linux 5.4.0-62-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 16:37:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:8501]
  InstallationDate: Installed on 2020-05-17 (249 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-62-generic 
root=UUID=c8acacab-7716-4698-b0e0-6041467d4517 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5406
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X470-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5406:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX470-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage 

[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

2021-01-21 Thread Daniel van Vugt
"Because of Bluetooth" sounds like a stretch. Hedda, please open a new
bug by running:

  ubuntu-bug gnome-shell

so we can analyse your issue separately.

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

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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


[Touch-packages] [Bug 1912575] Re: [regression] gpm no longer starts automatically, service must be started manually

2021-01-20 Thread Daniel van Vugt
** Bug watch added: Debian Bug tracker #980726
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980726

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

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

Title:
  [regression] gpm no longer starts automatically, service must be
  started manually

Status in gpm package in Ubuntu:
  New
Status in gpm package in Debian:
  Unknown

Bug description:
  gpm no longer starts automatically, service must be started manually.

  The problem started this past week, so maybe in version 1.20.7-7

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gpm 1.20.7-7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 11:49:14 2021
  InstallationDate: Installed on 2020-11-27 (54 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125)
  SourcePackage: gpm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1912575] [NEW] [regression] gpm no longer starts automatically, service must be started manually

2021-01-20 Thread Daniel van Vugt
Public bug reported:

gpm no longer starts automatically, service must be started manually.

The problem started this past week, so maybe in version 1.20.7-7

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gpm 1.20.7-7
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu55
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 21 11:49:14 2021
InstallationDate: Installed on 2020-11-27 (54 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125)
SourcePackage: gpm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute regression regression-release

** Tags added: regression-release

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

Title:
  [regression] gpm no longer starts automatically, service must be
  started manually

Status in gpm package in Ubuntu:
  New

Bug description:
  gpm no longer starts automatically, service must be started manually.

  The problem started this past week, so maybe in version 1.20.7-7

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gpm 1.20.7-7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 11:49:14 2021
  InstallationDate: Installed on 2020-11-27 (54 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125)
  SourcePackage: gpm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1912575] Re: [regression] gpm no longer starts automatically, service must be started manually

2021-01-20 Thread Daniel van Vugt
Looks like gpm.service was just introduced. It probably needs some
tweaking.

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

Title:
  [regression] gpm no longer starts automatically, service must be
  started manually

Status in gpm package in Ubuntu:
  New

Bug description:
  gpm no longer starts automatically, service must be started manually.

  The problem started this past week, so maybe in version 1.20.7-7

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gpm 1.20.7-7
  ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 11:49:14 2021
  InstallationDate: Installed on 2020-11-27 (54 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201125)
  SourcePackage: gpm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Daniel van Vugt
The hardware data in comment #4 does explicitly say:

  Supported sample rates (kHz): 48

but I don't know if the Linux audio stack (PulseAudio + ALSA) is smart
enough to honour that automatically. Sounds like it's not.

Try making a new file ~/.config/pulse/daemon.conf with:

  default-sample-rate = 48000

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Daniel van Vugt
There are a few sample rate-related settings in /etc/pulse/daemon.conf
(or just make your own personal ~/.config/pulse/daemon.conf). You can
edit that file and remove the ';' prefix to enable any settings.

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
 

[Touch-packages] [Bug 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed

2021-01-20 Thread Daniel van Vugt
Sounds reasonable to me...

https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules
/#module-bluetooth-policy

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

Title:
  Add automatic switching to HSP/HFP from A2DP when a mic is needed

Status in PulseAudio:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

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


[Touch-packages] [Bug 1912426] Re: clock is obscured by item on top bar

2021-01-19 Thread Daniel van Vugt
Is that icon an app indicator or from some other extension?

** 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/1912426

Title:
  clock is obscured by item on top bar

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  the clock display is the middle of the top bar and items are added to
  the top bar from the right with the result that an item can overlap
  with the clock -- see attached

  Crazy.

  Put the clock at the right end of the top bar and the problem
  disappears

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 20 14:16:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821CU, 5.4.1, 5.8.0-38-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  InstallationDate: Installed on 2021-01-14 (6 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 2.48
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.48
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.39
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.57
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: L1G76AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1912364] Re: Xorg freeze

2021-01-19 Thread Daniel van Vugt
Thanks for the bug report. I can't see any information about freezes or
crashes in the attached files so next time the issue happens, please
reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also check for crashes by following these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Summary changed:

- Xorg freeze
+ Freeze/crash

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

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

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

Title:
  Freeze/crash

Status in Ubuntu:
  Incomplete

Bug description:
   Hi! When it started to crash, the only way was to reinstall
  everything, but the problem continued. Only safe mode works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 19 12:02:43 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [1028:0611]
  InstallationDate: Installed on 2021-01-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Inspiron 3647
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=fa06ad05-1858-419e-bbeb-f3dbb4c59017 username quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 02YRK5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd06/29/2015:svnDellInc.:pnInspiron3647:pvr:rvnDellInc.:rn02YRK5:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 3647
  dmi.product.sku: 0611
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2021-01-19 Thread Daniel van Vugt
Or maybe use bug 1905627 from now on :)

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

2021-01-19 Thread Daniel van Vugt
** Tags added: raspi

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

Title:
  Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1

Status in bluez package in Ubuntu:
  New
Status in bluez source package in Groovy:
  New
Status in bluez source package in Hirsute:
  New

Bug description:
  Bluetooth stops working after updating to bluez version
  5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization
  timed out". Bluetooth is working again if bluez is reverted to version
  5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt.

  Release:  20.10
  bluez:
Installed: 5.55-0ubuntu1.1
Candidate: 5.55-0ubuntu1.1
Version table:
   *** 5.55-0ubuntu1.1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 
Packages
  100 /var/lib/dpkg/status
   5.55-0ubuntu1 500
  500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14
  Uname: Linux 5.8.0-1007-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: arm64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 25 16:09:03 2020
  ImageMediaBuild: 20200423.1
  InterestingModules: bnep bluetooth
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 
25EE
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
   |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 
smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 
vc_mem.mem_size=0x3ff0  dwc_otg.lpm_enable=0 console=tty1 
root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: bluez
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago)
  acpidump:
   
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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


[Touch-packages] [Bug 1843733] Re: fftw3 ftbfs in eoan (armhf only)

2021-01-19 Thread Daniel van Vugt
** Bug watch added: Debian Bug tracker #943396
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943396

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

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

Title:
  fftw3 ftbfs in eoan (armhf only)

Status in FFTW:
  New
Status in fftw3 package in Ubuntu:
  Fix Released
Status in fftw3 source package in Eoan:
  Won't Fix
Status in fftw3 package in Debian:
  Unknown

Bug description:
  fftw3 ftbfs in eoan (armhf only).

  https://launchpadlibrarian.net/441265031/buildlog_ubuntu-eoan-
  armhf.fftw3_3.3.8-2_BUILDING.txt.gz

  ( cd tests ; /usr/bin/make smallcheck )
  make[1]: Entering directory '/<>/tests'
  perl -w ./check.pl -r -c=1 -v `pwd`/bench
  Executing "/<>/tests/bench --verbose=1   --verify 
'ok7e10x12bv29' --verify 'ik7e10x12bv29' --verify '//obr2304' --verify 
'//ibr2304' --verify '//ofr2304' --verify '//ifr2304' --verify 'obr2304' 
--verify 'ibr2304' --verify 'ofr2304' --verify 'ifr2304' --verify '//obc2304' 
--verify '//ibc2304' --verify '//ofc2304' --verify '//ifc2304' --verify 
'obc2304' --verify 'ibc2304' --verify 'ofc2304' --verify 'ifc2304'"
  ok7e10x12bv29 1.71318e-07 1.44516e-06 2.00887e-07
  ik7e10x12bv29 1.66737e-07 1.44901e-06 1.76717e-07
  Segmentation fault (core dumped)
  FAILED /<>/tests/bench:  --verify 'ok7e10x12bv29' --verify 
'ik7e10x12bv29' --verify '//obr2304' --verify '//ibr2304' --verify '//ofr2304' 
--verify '//ifr2304' --verify 'obr2304' --verify 'ibr2304' --verify 'ofr2304' 
--verify 'ifr2304' --verify '//obc2304' --verify '//ibc2304' --verify 
'//ofc2304' --verify '//ifc2304' --verify 'obc2304' --verify 'ibc2304' --verify 
'ofc2304' --verify 'ifc2304'
  make[1]: *** [Makefile:723: smallcheck] Error 1
  make[1]: Leaving directory '/<>/tests'

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

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


[Touch-packages] [Bug 1903048] Re: [SRU] Bluetooth won't activate on the pi 400

2021-01-19 Thread Daniel van Vugt
yonailo, that must be a different issue. :(

Please open a new bug by running:

  ubuntu-bug bluez

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

Title:
  [SRU] Bluetooth won't activate on the pi 400

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Groovy:
  Fix Released
Status in bluez source package in Hirsute:
  Triaged

Bug description:
  [Impact]

  Without these patches, Bluetooth is inoperable on the recently
  released Raspberry Pi 400.

  [Test Case]

  * Boot the Ubuntu Desktop for Pi image on a Pi 400.
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is not enabled and attempting to activate it fails
  * Enable the -proposed repository for the release (groovy)
  * sudo apt update
  * sudo apt install bluez
  * sudo reboot
  * Start the Settings application and switch to the Bluetooth tab
  * Verify that Bluetooth is active and that Bluetooth devices (e.g. mice, 
mobile phones, headphones, etc.) can connect and operate correctly

  [Regression Potential]

  Extremely low (on groovy in particular, this has the same version of
  bluez as hirsute). The only significant risk is to non-Pi platforms or
  dongles which also use the Broadcom 43xx (or Cypress 305) chips for
  Bluetooth which might be inadvertently affected by these patches.

  [Original Description]

  The new Pi 400 has a slightly different Wifi/BT chip to the Pi4.
  Whilst wifi works happily, Bluetooth fails to operate. This doesn't
  appear to be an issue with either the firmware (the latest versions
  from upstream Raspbian have been tried), or the kernel (a known-good
  raspi kernel has been tested under Ubuntu), but with Bluez itself.
  Specifically, tracing the initialization with btmon on Raspbian and
  Ubuntu, the stack consistently fails when attempting to "Set Default
  PHY" on the latter. Curiously, under Ubuntu the adapter also appears
  to lack a MAC address.

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

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


[Touch-packages] [Bug 1911030] Re: Graphical flashes on a raspi 4

2021-01-18 Thread Daniel van Vugt
Full KMS hardware support is available in newer kernels (5.10.x I think)
so please try installing a newer arm64 kernel like:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.8/

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

Title:
  Graphical flashes on a raspi 4

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1911030/+subscriptions

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


[Touch-packages] [Bug 1912275] Re: Xorg freeze

2021-01-18 Thread Daniel van Vugt
Thanks for the bug report.

I can't see any crashes or freezes in the attached files. Next time the
problem happens, please reboot and then in a Terminal run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also follow these steps to check for past crashes:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Summary changed:

- Xorg freeze
+ The system crashes/hangs

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

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

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

Title:
  The system crashes/hangs

Status in Ubuntu:
  Incomplete

Bug description:
  the system crashes/hangs and sound loops when watching videos.  please
  help as this laptop is needed for my child's home schooling

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 18 22:46:57 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom: added
   broadcom-sta, 6.30.223.271, 5.8.0-38-generic, x86_64: installed
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:227e]
  InstallationDate: Installed on 2021-01-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=1abcb365-cc5b-42e1-8f23-09c6b2cfd2b6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2014
  dmi.bios.release: 15.52
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 77.53
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd12/19/2014:br15.52:efr77.53:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227E:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.sku: J5B67EA#ABU
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open

2021-01-18 Thread Daniel van Vugt
In that case you probably want:

  bt-obex -s -y

But still it's just a workaround for the original problem.

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

Title:
  Can't receive files over bluetooth unless settings dialog is open

Status in bluez package in Ubuntu:
  New
Status in gnome-user-share package in Ubuntu:
  New

Bug description:
  On 18.04 I could send files from my phone to my laptop at any time.
  On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
  I need to be able to send files (mostly photos and videos) from my phone to 
my laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

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

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


[Touch-packages] [Bug 1911887] Re: Xorg freeze

2021-01-17 Thread Daniel van Vugt
Thanks for the bug report. It appears you have the proprietary Nvidia
kernel driver installed but also are using the open source Xorg driver,
which is the wrong one. Please try removing and then reinstalling the
Nvidia driver in the 'Additional Drivers' app and then reboot.



** Summary changed:

- Xorg freeze
+ [nvidia] Xorg freeze

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-340
(Ubuntu)

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Incomplete

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

Title:
  [nvidia] Xorg freeze

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I just installed Ubuntu 20.04.
  but sometimes, the screen is freezing. This is very very bothering me.
  Please help me.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 15 03:37:42 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard: NVIDIA Corporation GT218 [GeForce G210] [10de:0a60] (rev a2) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2021-01-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID :3825   USB OPTICAL MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 480M
   |__ Port 7: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: Onda technology corporation ONDA H110S QG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=d1643fe1-2ea9-43a9-bce2-476592a525ca ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 2016/04/29
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: Default string
  dmi.board.name: ONDA H110S QG
  dmi.board.vendor: Onda technology corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd2016/04/29:svnOndatechnologycorporation:pnONDAH110SQG:pvrDefaultstring:rvnOndatechnologycorporation:rnONDAH110SQG:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ONDA H110S QG
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Onda technology corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  

[Touch-packages] [Bug 1912069] Re: app-notification style class does not appear correctly

2021-01-17 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1912069

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.


** Package changed: ubuntu-themes (Ubuntu) => yaru-theme (Ubuntu)

** Changed in: yaru-theme (Ubuntu)
   Status: New => Incomplete

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

Title:
  app-notification style class does not appear correctly

Status in yaru-theme package in Ubuntu:
  Incomplete

Bug description:
  app-notification style class show without transparency like in
  attachment.

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

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


[Touch-packages] [Bug 1912083] Re: the icons are longer

2021-01-17 Thread Daniel van Vugt
Please clarify which icons, where. Can you attach a screenshot or photo
of the problem?

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

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

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

Title:
  the icons are longer

Status in Ubuntu:
  Incomplete

Bug description:
  the icons are longer than they should be

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 17 11:12:46 2021
  DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
  ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
   Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 348 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 15.21
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86CD
  dmi.board.vendor: HP
  dmi.board.version: 98.08
  dmi.chassis.asset.tag: 5CG0351KMK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 98.8
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/11/2020:br15.21:efr98.8:svnHP:pnHP348G7:pvrType1ProductConfigId:rvnHP:rn86CD:rvr98.08:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP Notebook
  dmi.product.name: HP 348 G7
  dmi.product.sku: 7HC08AV
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1912083/+subscriptions

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


[Touch-packages] [Bug 1911858] Re: i am not aware what are these errors

2021-01-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1911857 ***
https://bugs.launchpad.net/bugs/1911857

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

** This bug has been marked a duplicate of bug 1911857
   cant tell whats wrong

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

Title:
  i am not aware what are these errors

Status in Ubuntu:
  New

Bug description:
  cant tell what are these errors releted too...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jan 15 12:32:10 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2017-03-15 (1401 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep 
alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2017
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 01HYMY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0794
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Wed Jan 13 10:43:27 2021
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.9-2ubuntu1.1

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

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


[Touch-packages] [Bug 1911456] Re: Can't receive files over bluetooth unless settings dialog is open

2021-01-17 Thread Daniel van Vugt
I'm not sure if this is a bug or a security feature. You might be able
to keep it enabled in the 'bluetoothctl' tool. Or try something like
'bt-obex -s'.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't receive files over bluetooth unless settings dialog is open

Status in bluez package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  On 18.04 I could send files from my phone to my laptop at any time.
  On 20.04 I can't get files to be accepted by the laptop over bluetooth. After 
much frustration and experimenting, I figured out that it will work, but only 
if the bluetooth settings dialog is open. If the settings dialog is not open, 
the incoming file is rejected.  If the dialog is closed after the file transfer 
begins, the transfer continues but the file is discarded when the transfer is 
complete.  This is very frustrating.
  I need to be able to send files (mostly photos and videos) from my phone to 
my laptop without having to open the settings dialog on the laptop, just like I 
could before upgrading.

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

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


[Touch-packages] [Bug 1911857] Re: cant tell whats wrong

2021-01-17 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  cant tell whats wrong

Status in Ubuntu:
  Incomplete

Bug description:
  cant tell whats wrong

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jan 15 12:30:06 2021
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0794]
  InstallationDate: Installed on 2017-03-15 (1401 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=a024a4c4-d7d6-404c-be82-173672511ace ro acpi_rev_override 
alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep 
alx.enable_wol=1 mem_sleep_default=deep drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/15/2017
  dmi.bios.release: 1.7
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.07.00
  dmi.board.name: 01HYMY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.07.00:bd02/15/2017:br1.7:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn01HYMY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0794
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Wed Jan 13 10:43:27 2021
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.9-2ubuntu1.1

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

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


[Touch-packages] [Bug 1820866] Re: File dialog extremely slow scanning network mounts

2021-01-17 Thread Daniel van Vugt
** Changed in: gtk+3.0 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  File dialog extremely slow scanning network mounts

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  From any application where you have a "save as" or "open" option, the
  dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2
  SSD's, so the machine is not slow. However, if I use gedit and click
  open / Other documents it takes 6 to 7 seconds before the file dialog
  is properly displayed. This does not even get better with reuse. I
  opened gedit just now and the first time it took 7 seconds. Then I
  pressed Cancel and repeated the process - it still took more than 6
  seconds before the dialog was properly displayed. Often I would only
  see "Other locations" and then default places (Home, Documents etc)
  and bookmarks (I have about 8 bookmarks of which 2 are network shares)
  are displayed. These items are added one by one - maybe one every half
  second. Often it takes a few seconds before the first location other
  than "Other Locations" is displayed. Even the file panel is not
  immediate at first and you can see how lines are added one by one.
  Take into account that my home folder is on an SSD, so populating a
  file list should be lightning fast. I have looked at the CPU activity,
  but it does not go over about 10% during display of open and close
  dialogs.

  Just be aware that this is not specific to gedit - all applications
  using gnome file dialog has the same problem.

  Please see the attached screen recording.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 19 16:14:16 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 
'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-12-02 (107 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+subscriptions

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


[Touch-packages] [Bug 1911369] Re: screen corruption after last update.

2021-01-12 Thread Daniel van Vugt
Please try an older kernel like:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.89/amd64/

** Tags added: radeon

** Summary changed:

- screen corruption after last update.
+ [radeon] Horizontal lines of screen corruption after last update.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu)

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

** No longer affects: xserver-xorg-video-ati (Ubuntu)

** Tags added: regression-update

** Also 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1911369

Title:
  [radeon] Horizontal lines of screen corruption after last update.

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  A clean install is fine if I don't take updates.  If I do take the
  updates and reboot then I get heavy video corruption.  This just
  started today.

  This is a dual boot system.  The windows system has no issues.
  Appears to be software and not a hardware issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 21:18:27 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950/8950 OEM / 
R9 280] [1002:679a] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO2 [Radeon HD 
7950 Boost] [1002:3000]
  InstallationDate: Installed on 2021-01-13 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP Z420 Workstation
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=e1d90a30-a65a-46c5-bae3-c39bbf1a4e0e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2019
  dmi.bios.release: 3.96
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J61 v03.96
  dmi.board.name: 1589
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 0.00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ61v03.96:bd10/29/2019:br3.96:svnHewlett-Packard:pnHPZ420Workstation:pvr:rvnHewlett-Packard:rn1589:rvr0.00:cvnHewlett-Packard:ct6:cvr:
  dmi.product.family: 103C_53335X G=D
  dmi.product.name: HP Z420 Workstation
  dmi.product.sku: D8N02UC#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1911237] Re: Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black (lose signal) after logging in

2021-01-12 Thread Daniel van Vugt
** Summary changed:

- Thinkpad P1 2nd gen and Thunderbold 3 Workstation Dock
+ Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go black 
(lose signal) after logging in

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

Title:
  Screens attached to Thinkpad Thunderbolt 3 Workstation Dock (40AN) go
  black (lose signal) after logging in

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The dock is Type 40AN .

  I already reported a bug, and was asked to run ubuntu-bug xorg, which I did 
and arrived here.
  Probably you want to merge them. Please also mind the tons of reports from 
other users, which report the same or similar issues in the Ubuntu Forum, in 
the thread which I did open. Please see the other bug for a link.

  In the current configuration I did downgrade the dock to an older
  firmware version as mentioned in my other bug ticket, and also by many
  other users in the Ubuntu Forum, since this is the only way it works
  at least partially, so that I'm able to submit this bug report.

  The symptom right now is that I bootet with two 4 K Monitors connected, and 
could see at least for a while (at time of login screen) the magenta 
background, but then, after logging in, the 2 external Monitors get black and 
say something similar to 'Input Signal not Found'. 
  Opposed to this, when I open within Gnome the Settings > Displays ( or 
similar, I have it in German), then it tells me there that I have 2 external 
Monitors connected, which I can move around in that dialog, choose primary 
dialog etc.

  On the console, where I run ubuntu-bug, I get this messages
  (repeatedly):

  Errors:
  Program binary could not be loaded. Binary is not compatible with current 
driver/hardware combination. Driver build date Oct 22 2020. Please check build 
information of source that generated the binary.

  wind:~ $ [8190:8190:0112/191237.346935:ERROR:shared_context_state.cc(74)] 
Skia shader compilation error
  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  Uname: Linux 5.4.35-custom-patched-26c16f9d9 x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 19:09:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
   nvidia, 455.38, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-58-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.35-custom-patched-26c16f9d9, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:229f]
  InstallationDate: Installed on 2020-05-05 (251 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20QT000RGE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.35-custom-patched-26c16f9d9 
root=UUID=07e75e73-7d85-45e9-90a7-a83ea1f47c1c ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET49W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QT000RGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  

[Touch-packages] [Bug 1911219] Re: Xorg freeze

2021-01-12 Thread Daniel van Vugt
Next time the freeze happens, please reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Please also check for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment


** Tags added: nouveau

** Summary changed:

- Xorg freeze
+ [nouveau] Xorg freeze

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

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

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

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

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

Title:
  [nouveau] Xorg freeze

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  
  Also freezes when trying to open Libre Office new documents

  Not sure if it is the video that is causing issues

  Mouse and keyboard seems to be frozen and cant do anything without a
  hard reboot

  Some times the video keeps playing even if everything is frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 12 11:29:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1212]
  InstallationDate: Installed on 2021-01-09 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=598990d0-29d6-4e5b-a8aa-3c75c00bd284 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10
  dmi.board.name: GA-970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-970A-D3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

2021-01-12 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  New

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-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: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-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: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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


[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-01-11 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  GDK/GTK app crash when performing drag operation

Status in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 

[Touch-packages] [Bug 1911030] Re: graphical flashes on a raspi 4

2021-01-11 Thread Daniel van Vugt
** Tags added: raspi raspi-gfx

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

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

** Summary changed:

- graphical flashes on a raspi 4
+ Graphical flashes on a raspi 4

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

Title:
  Graphical flashes on a raspi 4

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Using gnome-shell - activities - see attached video

  Graphics flash - more prominent with more than one app running.

  If you install ubuntu-budgie-desktop and simply move through the menu
  categories the flashing is even more prominent.

  I'm guessing this is xorg related - but I do note the recent mesa
  uplift has made things worse

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18
  Uname: Linux 5.8.0-1011-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu55
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 16:49:14 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ImageMediaBuild: 20201225
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 
snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 
smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  dwc_otg.lpm_enable=0 console=tty1 
root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet 
splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump:
   
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  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/1911030/+subscriptions

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


[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

2021-01-11 Thread Daniel van Vugt
Thanks. It looks like the kernel has everything turned on:

1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

Do you still have a 'bluetoothd' process when the problem occurs? Also,
can you run 'bluetoothctl' successfully when the bug is happening?

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.455
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.10
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: LENOVO 20SL
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: bluez 5.55-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Tags:  groovy
  Uname: Linux 5.8.0-25-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: 11/18/2020
  dmi.bios.release: 1.22
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DJCN22WW
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ThinkBook 14-IIL
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrDJCN22WW:bd11/18/2020:br1.22:efr1.18:svnLENOVO:pn20SL:pvrLenovoThinkBook14-IIL:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoThinkBook14-IIL:
  dmi.product.family: Thinkbook 14-IIL
  dmi.product.name: 20SL
  dmi.product.sku: LENOVO_MT_20SL_BU_idea_FM_Thinkbook 14-IIL
  dmi.product.version: Lenovo ThinkBook 14-IIL
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 18:26:49:C4:B9:6C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:19913 acl:0 sco:0 events:3169 errors:0
TX bytes:770617 acl:0 sco:0 commands:3167 errors:0

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

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


[Touch-packages] [Bug 1820866] Re: File dialog extremely slow scanning network mounts

2021-01-11 Thread Daniel van Vugt
Please check if the bug still occurs in a newer version of Ubuntu:

   https://ubuntu.com/download/desktop

If it does then please next open a GTK bug for the issue here:

  https://gitlab.gnome.org/GNOME/gtk/-/issues

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

Title:
  File dialog extremely slow scanning network mounts

Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  From any application where you have a "save as" or "open" option, the
  dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2
  SSD's, so the machine is not slow. However, if I use gedit and click
  open / Other documents it takes 6 to 7 seconds before the file dialog
  is properly displayed. This does not even get better with reuse. I
  opened gedit just now and the first time it took 7 seconds. Then I
  pressed Cancel and repeated the process - it still took more than 6
  seconds before the dialog was properly displayed. Often I would only
  see "Other locations" and then default places (Home, Documents etc)
  and bookmarks (I have about 8 bookmarks of which 2 are network shares)
  are displayed. These items are added one by one - maybe one every half
  second. Often it takes a few seconds before the first location other
  than "Other Locations" is displayed. Even the file panel is not
  immediate at first and you can see how lines are added one by one.
  Take into account that my home folder is on an SSD, so populating a
  file list should be lightning fast. I have looked at the CPU activity,
  but it does not go over about 10% during display of open and close
  dialogs.

  Just be aware that this is not specific to gedit - all applications
  using gnome file dialog has the same problem.

  Please see the attached screen recording.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 19 16:14:16 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 
'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']"
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-12-02 (107 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+subscriptions

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


[Touch-packages] [Bug 1910962] Re: Display freeze

2021-01-11 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

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

Title:
  Display freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Even Mouse cursor could not be moved, had to do a hard power on reset

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  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:Unity7:ubuntu
  Date: Mon Jan 11 16:46:58 2021
  DistUpgraded: 2020-09-29 20:14:07,287 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0]
  InstallationDate: Installed on 2017-12-02 (1135 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX310UAK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic 
root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-09-29 (103 days ago)
  dmi.bios.date: 04/18/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX310UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX310UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: UX310UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Mon Jan 11 16:44:45 2021
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.9-2ubuntu1.1~20.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

2021-01-11 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1910928

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

Title:
  Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  After I have installed the Ubuntu - I have noticed, that Bluetooth won't go 
turn on after Suspend. 
  The only way to get it working - reboot the system. 
  WiFi Adapter - AX201
  I have tried the latest kernel (5.11.rc2) - no luck.

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

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


[Touch-packages] [Bug 1910938] Re: Ubuntu don't show text anymore

2021-01-10 Thread Daniel van Vugt
Please:

1. Try disabling/uninstalling any gnome-shell extensions you might have
installed.

2. Attach a photo or screenshot of the problem.

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

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

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

Title:
  Ubuntu don't show text anymore

Status in Ubuntu:
  Incomplete

Bug description:
  Hello [happy new year :) ! ]

  Text information in the Ubuntu dialogs aren't displayed, or some times just a 
part of it.
  I don't see the hours, but i see the icons like Firefox actually opened, my 
battery etc. and notifications are empty (just the "!" icon).
  Text normally displayed when mouse-hover the applications icons is not 
displayed, when Ubuntu ask for my password the frame display only 3 or 4 
characters, when i put the computer in standby and reopen it doesn't change 
anything, and the bullets of my password aren't displayed when i login.
  The text normally displayed on the menus aren't displayed too, same for the 
application menu (when hitting the bottom left corner button) and icons of 
applications (like Discord options on the top right of the screen).
  The only text from xorg that is displayed (if it's from xorg…) is the 
window's title (like "#Room - Discord" for Discord application, or 
"me@computer: ~/" above the terminal).
  What is left works : Firefox can display text, and text is displayed in 
settings for example.

  P.S: a reboot solved the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 11 02:26:55 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo HD Graphics 620 [17aa:39e9]
  InstallationDate: Installed on 2020-11-15 (56 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 80V0
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=2342b448-1302-426d-9afd-b40fd298cdab ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN20WW(V2.04)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN20WW(V2.04):bd07/03/2018:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910840] Re: Xorg freeze

2021-01-10 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  After login the screen freezes with mouse pointer duplicating. No
  operations can be performed .Need to do hard reboot.This started
  happening after upgrade(5.0.58)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 11:46:45 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.138, 5.4.0-58-generic, x86_64: installed
   nvidia, 390.138, 5.4.0-59-generic, x86_64: installed
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04b6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6]
  InstallationDate: Installed on 2020-11-02 (68 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic 
root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.product.sku: System SKUNumber
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.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/+bug/1910840/+subscriptions

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


[Touch-packages] [Bug 1910811] Re: Video not playing correctly when scaling is 125%

2021-01-10 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1871849 ***
https://bugs.launchpad.net/bugs/1871849

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1871849, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: xrandr-scaling

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

** This bug has been marked a duplicate of bug 1871849
   Full screen videos suddenly change scale when using fractional scaling

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

Title:
  Video not playing correctly when scaling is 125%

Status in mutter package in Ubuntu:
  New

Bug description:
  When I play video with scaling 100% it is working fine but when I
  increase scaling to 125% it corrupts the whole screen and show random
  glitches and black screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  9 01:05:19 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8329]
 Subsystem: Hewlett-Packard Company Radeon R7 M520 [103c:8329]
  InstallationDate: Installed on 2021-01-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5d5 Chicony Electronics Co., Ltd HP TrueVision 
HD Camera
   Bus 001 Device 002: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic 
root=UUID=a99d194c-5997-492d-818a-c6dc3589c1d4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2019
  dmi.bios.release: 15.52
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8329
  dmi.board.vendor: HP
  dmi.board.version: 23.70
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 23.70
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:br15.52:efr23.70:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8329:rvr23.70:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.sku: 3FQ15PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910751] Re: picture sometimes get broken

2021-01-10 Thread Daniel van Vugt
Please attach a photo of the problem so we can better understand it.

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

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

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

Title:
  picture sometimes get broken

Status in Ubuntu:
  Incomplete

Bug description:
  parts of the screen get broken, so you can't even recognize what's
  displayed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Jan  8 13:35:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-60-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-60-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21cf]
  MachineType: LENOVO 424067G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic 
root=UUID=d78820b2-11bc-45fc-928b-02c1664cd562 ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET66WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 424067G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn424067G:pvrThinkPadT520:rvnLENOVO:rn424067G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T520
  dmi.product.name: 424067G
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910537] Re: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI

2021-01-10 Thread Daniel van Vugt
Thanks. That EDID seems to mention stereo audio support. So that's good.
But also I wonder if the DRM property needs tweaking. Please try running
this command:

  xrandr --output HDMI-1 --set audio on

If it still doesn't work then try logging in again after that.



Full EDID data:

EDID version: 1.3
Manufacturer: HXA Model 0 Serial Number 1
Made in week 38 of 2006
Digital display
Maximum image size: 71 cm x 40 cm
Gamma: 2.50
RGB color display
First detailed timing is preferred timing
Color Characteristics
  Red:   0.6396, 0.3447
  Green: 0.2910, 0.6347
  Blue:  0.1630, 0.0927
  White: 0.2880, 0.2958
Established Timings I & II: none
Standard Timings: none
Detailed mode: Clock 148.500 MHz, 708 mm x 398 mm
   1920 2008 2052 2200 ( 88  44 148)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 67.500 kHz
Detailed mode: Clock 148.500 MHz, 708 mm x 398 mm
   1920 2008 2052 2640 ( 88  44 588)
   1080 1084 1089 1125 (  4   5  36)
   +hsync +vsync
   VertFreq: 50.000 Hz, HorFreq: 56.250 kHz
Display Product Name: BMD HDMI
Display Range Limits
  Monitor ranges (GTF): 50-60 Hz V, 31-68 kHz H, max dotclock 80 MHz
Has 1 extension block
Checksum: 0xf7



CTA-861 Extension Block Revision 3
Basic audio support
Supports YCbCr 4:2:2
4 native detailed modes
27 bytes of CTA data blocks
  Video Data Block
 1920x1080i  60.000 Hz  16:933.750 kHz  74.250 MHz (VIC   5, native)
 1280x72060.000 Hz  16:945.000 kHz  74.250 MHz (VIC   4, native)
 1920x1080i  50.000 Hz  16:928.125 kHz  74.250 MHz (VIC  20, native)
 1280x72050.000 Hz  16:937.500 kHz  74.250 MHz (VIC  19, native)
 1920x1080   24.000 Hz  16:927.000 kHz  74.250 MHz (VIC  32, native)
 1920x1080   25.000 Hz  16:928.125 kHz  74.250 MHz (VIC  33, native)
 1920x1080   30.000 Hz  16:933.750 kHz  74.250 MHz (VIC  34, native)
 1920x1080   50.000 Hz  16:956.250 kHz 148.500 MHz (VIC  31, native)
 1920x1080   60.000 Hz  16:967.500 kHz 148.500 MHz (VIC  16, native)
  Audio Data Block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48
  Supported sample sizes (bits): 24 20 16
  Speaker Allocation Data Block
Speaker map:
  FL/FR - Front Left/Right
  Vendor-Specific Data Block, OUI 0x000c03 (HDMI)
Source physical address 3.0.0.0
Maximum TMDS clock: 150 MHz
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
   1280 1390 1430 1650 (110  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 60.000 Hz, HorFreq: 45.000 kHz
Detailed mode: Clock 74.250 MHz, 708 mm x 398 mm
   1280 1720 1760 1980 (440  40 220)
720  725  730  750 (  5   5  20)
   +hsync +vsync
   VertFreq: 50.000 Hz, HorFreq: 37.500 kHz
Checksum: 0xd2


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

** Summary changed:

- incorrect audio-EDID on HDMI, blocking audio transmission over HDMI
+ HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID 

[Touch-packages] [Bug 1910537] Re: incorrect audio-EDID on HDMI, blocking audio transmission over HDMI

2021-01-07 Thread Daniel van Vugt
> Their guess is that the linux notebook is not setting EDID
> configuration correctly and thus not recognized by the ATEM,
> while the cheap LCD screen propably does not care about EDID
> and just plays everything, therefore a wrong EDID information
> would not matter.

EDIDs work the other way round. An EDID is not "set" by Linux. It is
hard-coded in the monitor and only read by the computer. However it is
sadly common for monitor manufacturers (probably not Blackmagic) to ship
monitors that advertise faulty EDID data. That's probably what an "EDID
manager" is to fix, but I don't know of and have no experience with any
on Linux.

I would like to analyse the EDID being advertised by your ATEM, but
Xrandr.txt seems to show it was not plugged into HDMI when you logged
this bug. Please plug it in and then run:

  xrandr --verbose > xrandr2.txt

and attach the resulting file here.

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

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

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

Title:
  incorrect audio-EDID on HDMI, blocking audio transmission over HDMI

Status in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 

[Touch-packages] [Bug 1910538] Re: Cannot set scale of screen

2021-01-07 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736

** This bug is no longer a duplicate of bug 1910539
   [nvidia] Cannot set scale of screen
** This bug has been marked a duplicate of bug 1870736
   [nvidia] Screen scaling 125% gives 200%

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

Title:
  Cannot set scale of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor
  (3840x2160) both 27inch

  Obviously to extend display correctly (join displays) I need to put my
  4k monitor at scale of 125 and 2K monitor at 100% scale.

  I arrange two monitors side by side, then select 125% on 4K monitor
  (Fractional scaling is on) and click apply, both my monitors go to
  wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange
  bottom and top of each other.

  also login appears on wrong monitor (secondary) instead of selected
  primary

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.45.01  Thu Nov  5 
23:03:56 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 20:41:50 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] 
[19da:4509]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0229
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B360M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910539] Re: Cannot set scale of screen

2021-01-07 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1870736 ***
https://bugs.launchpad.net/bugs/1870736

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1870736, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: nvidia xrandr-scaling

** Summary changed:

- Cannot set scale of screen
+ [nvidia] Cannot set scale of screen

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

** This bug has been marked a duplicate of bug 1870736
   [nvidia] Screen scaling 125% gives 200%

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

Title:
  [nvidia] Cannot set scale of screen

Status in mutter package in Ubuntu:
  New

Bug description:
  I have 2 monitors a 2K monitor (2560x1440) and a 4k monitor
  (3840x2160) both 27inch

  Obviously to extend display correctly (join displays) I need to put my
  4k monitor at scale of 125 and 2K monitor at 100% scale.

  I arrange two monitors side by side, then select 125% on 4K monitor
  (Fractional scaling is on) and click apply, both my monitors go to
  wrong scaling 2K goes to 50% and 4K goes to 200% and displays arrange
  bottom and top of each other.

  also login appears on wrong monitor (secondary) instead of selected
  primary

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.45.01  Thu Nov  5 
23:03:56 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 20:41:50 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.45.01, 5.4.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
   NVIDIA Corporation TU104 [GeForce RTX 2070 SUPER] [10de:1e84] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. TU104 [GeForce RTX 2070 SUPER] 
[19da:4509]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=e2e0340b-66fb-4930-908c-7e6767941743 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0229
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B360M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0229:bd02/26/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB360M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1910503] Re: latest kernel breaks display full sizing in virtualbox

2021-01-07 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

Title:
  latest kernel breaks display full sizing in virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel 5.8.0-34 breaks display full size/resizing in VirtualBox 6.1
  going back to kernel 5.4.0-59 makes full size display working again

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 09:12:44 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox-guest, 6.1.10, 5.4.0-58-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
   virtualbox-guest, 6.1.10, 5.4.0-59-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-05-01 (250 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=71747bce-f255-4284-aefc-caee0698739c ro quiet splash noibrs noibpb 
nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable 
no_stf_barrier mds=off tsx=on tsx_async_abort=off mitigations=off
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1910405] Re: bluetoothd hangs and cannot be killed

2021-01-06 Thread Daniel van Vugt
A process that cannot be killed usually means it's blocked in a kernel
call. So this sounds like a bug in the kernel Bluetooth code...

Please:

1. Run this command to gather more system info:

   apport-collect 1910405

2. Try a newer Ubuntu release or just a newer kernel from
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D


** Tags added: bionic

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

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

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

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

Title:
  bluetoothd hangs and cannot be killed

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

Bug description:
  Hi,

  When having a bluetooth headphone (JBL Live) connected  using the A2DP
  pulseaudio sink, the output sound suddenly stops during a music
  streaming of videocall session. Sometimes just disconnecting and
  reconnecting the headphone works, but some times reconnection is not
  possible anymore due to the hanging of bluetoothd. Bluetoothd still
  appears in the processes list, but cannot be killed, neither with
  "sudo service bluetooth stop" or "kill -9":

  $ ps afx | grep blue
   9597 tty2 Sl+0:01  |   \_ gnome-control-center bluetooth
   5405 ?Ss 0:00  \_ /usr/lib/bluetooth/obexd
  10694 pts/0S+ 0:00  \_ grep blue
  20548 ?Ds 0:03 /usr/lib/bluetooth/bluetoothd

  All programs keep working normally, only bluetooth is affected as well
  as the bluetooth settings page.

  The only solution is a hard reboot. A soft reboot doesn't even work:
  the systems keeps trying to end the bluetoothd process so one needs to
  press the power button for a few seconds to terminate the process.

  $ bluetoothd --version
  5.48

  $ uname -a
  Linux omer 5.4.0-58-generic #64~18.04.1-Ubuntu SMP Wed Dec 9 17:11:11 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  Using Ubuntu 18.04.5 LTS preinstalled on a Dell XPS13, which has been
  working nice for over one year now just like previous versions.

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

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


[Touch-packages] [Bug 1910435] Re: display texts are gone noting will show

2021-01-06 Thread Daniel van Vugt
Thanks for the bug report.

Please attach a screenshot or photo of the problem.

Also, do you find the problem only occurs after suspend/hibernate?

** Tags added: nvidia

** Summary changed:

- display texts are gone noting will show
+ [nvidia] display texts are gone noting will show

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

** Also affects: nvidia-graphics-drivers-450 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: nvidia-graphics-drivers-450 (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/1910435

Title:
  [nvidia] display texts are gone noting will show

Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Incomplete

Bug description:
  no text showing even restart and shutdown button's text

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 02:17:02 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
   nvidia, 450.80.02, 5.4.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:8627]
  InstallationDate: Installed on 2020-12-24 (12 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter 
(Unitek Y-247A)
   Bus 001 Device 003: ID 1038:170a SteelSeries ApS SteelSeries Rival 100 Dell 
China
   Bus 001 Device 002: ID 0c45:672e Microdia USB DEVICE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic 
root=UUID=15221e3c-7bd7-41a8-b8bc-27f5c93ca2a5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3806
  dmi.board.asset.tag: Default string
  dmi.board.name: H110M-F
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3806:bd05/09/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-F:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen

2021-01-05 Thread Daniel van Vugt
It's not surprising this bug would only affect Xorg sessions because
only Xorg sessions supported the fullscreen unredirect optimization,
until recently.

** No longer affects: xorg (Ubuntu)

** Summary changed:

- dock and top bar flashing non-stop at fullscreen
+ dock and top bar flashing non-stop at fullscreen in Xorg sessions

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

Title:
  dock and top bar flashing non-stop at fullscreen in Xorg sessions

Status in gnome-shell-extension-autohidetopbar package in Ubuntu:
  New
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  New
Status in gnome-shell-extension-dashtodock package in Ubuntu:
  New
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04.1 LTS

  
  This problem affects all extensions that alter the dock and top bar. 
Including the standard extension "Ubuntu dock". All extensions are duly updated 
to the present date.

  I hoped that when entering full screen it would be possible to bring
  the dock and the top bar when placing the mouse over the respective
  corners. And in fact it is partially possible.

  However, both are flashing, making it impossible to use them in full
  screen. They blink very fast and you need to click on the correct
  timing to open the programs on the dock, for example. It is possible
  to click, but it is as if they were triggered several times, as if I
  were placing and removing the mouse from the corner very quickly.

  I enter the program. Everything is OK. The problem arises when I use
  the fullscreen. Sometimes the docks and the top bar work perfectly for
  a while, and then they start flashing.

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 22 14:07:57 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-07-24 (120 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-07-24 (121 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
  Tags:  focal
  Uname: Linux 5.4.0-54-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-10-23 (30 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare
  _MarkForUpload: True
  mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 
2020-07-25T15:59:00.336431

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

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


[Touch-packages] [Bug 1909944] Re: Dell XPS 13 Synaptics touch screen does not work after boot but will work after resume from sleep?

2021-01-05 Thread Daniel van Vugt
Please try selecting 'Ubuntu on Wayland' on the login screen, just
before you enter your password. Does the touch screen work any better in
a Wayland session?


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

** Summary changed:

- Dell XPS 13 Synaptics touch screen does not work after boot but will work 
after resume from sleep?
+ Dell XPS 13 9333 Synaptics touch screen does not work after boot but will 
work after resume from sleep?

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

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

Title:
  Dell XPS 13 9333 Synaptics touch screen does not work after boot but
  will work after resume from sleep?

Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I freshly installed Ubuntu 20.10 and noticed that the touch screen
  does not work. Tried xinput --list and then xinput disable/enable
  [correct-id] but with no avail.

  However, if I close the laptop lid and open it, after the system
  resumes from sleep, the touch screen starts working.

  BUT, another anomaly happens, this could not necessarily be after the
  1st resume from sleep, it could be the 2nd+ ---> the "Windows" key on
  the keyboard stops working? So, I can't start apps by type and search?
  And when this happens, the whole screen sometimes freezes and becomes
  unresponsive ex. moving around the mouse (synaptic touch pad and not
  touchscreen), no matter where I click, no reaction... I tried
  CTRL+ALT+F1 then switch back and somehow it started working again? It
  also happened, that the synaptic touch pad was not moving the mouse
  cursor on the screen (and the mouse cursor just disappeared)? Luckily,
  the keyboard was still reacting for the CTRL+ALT+T and the terminal
  window showed up, from where I used sudo modprobe -r psmouse and then
  sudo modprobe psmouse and also xinput disable/enable [touch-pad-id]
  and it got back to work.

  Many things happen in this one bug it seems?

  NOTE: when running 20.10 from USB (Live CD), then the touchscreen
  works perfectly! Only after install do these anomalies happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  3 22:55:01 2021
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
  InstallationDate: Installed on 2021-01-01 (2 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS13 9333
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=fe6e5482-378f-4c13-9039-8b11eba4af45 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2015
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/31/2015:br0.1:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/libinput/+bug/1909944/+subscriptions

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


[Touch-packages] [Bug 1910287] Re: Touchpad Scrolling and Cursor Speed Reset on Awakening

2021-01-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1899206, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1899206
   Input device settings not applied on hotplug/reconnect/resume in Xorg 
sessions

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

Title:
  Touchpad Scrolling and Cursor Speed Reset on Awakening

Status in xorg package in Ubuntu:
  New

Bug description:
  As a user, when my computer reawakens from sleep, often the touchpad
  (Apple Touchpad 2) settings are "reset to default" meaning that
  natural scrolling becomes unnatural, right click is disabled, and
  cursor speed is slow again. Sometimes the trackpad becomes altogether
  unresponsive and needs disconnection and reconnection.

  Ubuntu 20.04 LTS

  I then have to open settings and cycle all the toggles for the old
  settings to reengage.

  That's about all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan  5 13:05:51 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-54-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GP102 [TITAN X] [10de:1b00] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: NVIDIA Corporation GP102 [TITAN X] [10de:119a]
   ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 30) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family [1043:85f9]
  InstallationDate: Installed on 2020-07-17 (172 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. Z10PE-D16 WS
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=1c2a4ecb-99e5-4bb1-bc33-e9769d76de0f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/10/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3407
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z10PE-D16 WS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr3407:bd03/10/2017:svnASUSTeKCOMPUTERINC.:pnZ10PE-D16WS:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PE-D16WS:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: Server
  dmi.product.name: Z10PE-D16 WS
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
 

[Touch-packages] [Bug 1909834] Re: [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card

2021-01-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1897965, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio
  fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  sound card disappeared
  just see rtp multicast sink - no sound card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  evstratios  10958 F pipewire-media-
   /dev/snd/seq:evstratios  10946 F pipewire
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Jan  1 17:49:50 2021
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Title: [Inspiron 3793, Intel Icelake HDMI, Digital Out, HDMI] Pulseaudio 
fails to detect card
  UpgradeStatus: Upgraded to groovy on 2020-12-31 (1 days ago)
  dmi.bios.date: 11/13/2020
  dmi.bios.release: 1.13
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0JF2P0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:br1.13:svnDellInc.:pnInspiron3793:pvr:rvnDellInc.:rn0JF2P0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3793
  dmi.product.sku: 097A
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1909776] Re: Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

2021-01-05 Thread Daniel van Vugt
Thanks for the bug report.

* Do you mean a mouse or touchpad?

* If it's an actual mouse then please try plugging in a different mouse.

* Are there any other apps affected?

* Please also try a newer kernel:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

  or more simply, try booting a newer Ubuntu release:

  https://ubuntu.com/download/desktop


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

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

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

Title:
  Left Mouse Button Sometimes Gets Stuck in Unity same as bug #1040844

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  It seems like this is an old bug and I'm noticing only in the last few
  months.

  Sometimes, after I leave my PC on or after a standby, my left mouse
  button seems stuck in two appimage applications (freecad 0.18.4 and
  cura 4.8.0).

  I found no way to workaround this if not just after a reboot.

  Thanks in advance,

  Massimo

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
  Uname: Linux 4.15.0-128-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.20
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 31 18:59:29 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:3906]
  InstallationDate: Installed on 2015-12-12 (1846 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 80HE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic 
root=UUID=691bfdf1-ec74-4a27-bfe5-b660d9b9531f ro noprompt quiet splash 
pcie_aspm i915.lvds_downclock=1 i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 
resume=UUID=9aa74165-44e7-42e8-8792-f50b6d875421 net.ifnames=0 biosdevname=0 
i8042.reset vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A6CN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 3 Pro-1370
  dmi.modalias: 
dmi:bvnLENOVO:bvrA6CN58WW:bd08/06/2015:svnLENOVO:pn80HE:pvrLenovoYOGA3Pro-1370:rvnLENOVO:rnVIUU4:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYOGA3Pro-1370:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80HE
  dmi.product.version: Lenovo YOGA 3 Pro-1370
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Dec 31 12:49:57 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.8
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1909496] Re: Blinking login screen

2021-01-04 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Blinking login screen

Status in linux package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Hello,
  I am facing this issue since the upgrade of Ubuntu to Ubuntu 20.04.1 LTS. The 
issue still persists even after re-installing Ubuntu 20.04.1 LTS.

  Due to inactivity the system goes to the Suspend mode. On restoring from the 
suspend mode the login screen appears but it starts to blink continuously 
making it impossible to use the system.
  The only option is to force restart the system.

  Please let me know if this is an already known issue/bug and if there
  is a solution available for the same.

  Thank You

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 28 19:21:12 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-12-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=44a1973f-ce3f-46bb-ab72-156c1d047556 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909670] Re: Screen gets corrupted

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1896091 ***
https://bugs.launchpad.net/bugs/1896091

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1896091, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 1896091
   [i915] Noise-like lines of graphics corruption when moving windows in Xorg 
sessions

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

Title:
  Screen gets corrupted

Status in linux package in Ubuntu:
  New

Bug description:
  There is a huge corruption in the screen. My laptop is lenovo-
  ideapad-330-151kb. Please fix. Thanking you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 30 19:42:03 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821ce, 5.5.2.1, 5.8.0-31-generic, x86_64: installed
   rtl8821ce, 5.5.2.1, 5.8.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3965]
  InstallationDate: Installed on 2020-11-21 (38 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 002: ID 0bc2:231a Seagate RSS LLC Expansion Portable
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58ea Realtek Semiconductor Corp. EasyCamera
   Bus 001 Device 002: ID 0bda:c024 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81DE
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=0d397bc8-aadd-4e17-ba85-a15afd730cd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2020
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8TCN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.ec.firmware.release: 1.7
  dmi.modalias: 
dmi:bvnLENOVO:bvr8TCN58WW:bd06/18/2020:br1.58:efr1.7:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81DE
  dmi.product.sku: LENOVO_MT_81DE_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/linux/+bug/1909670/+subscriptions

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


[Touch-packages] [Bug 1909387] Re: Xorg crash (libinput related) on middle mouse click with firefox icognito window

2021-01-04 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- Xorg crash (libinput related) on middle mouse click with firefox icognito 
window
+ Xorg crashed with SEGV in miPointerMoveNoEvent from miPointerSetPosition from 
positionSprite from positionSprite from fill_pointer_events

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

Title:
  Xorg crashed with SEGV in miPointerMoveNoEvent from
  miPointerSetPosition from positionSprite from positionSprite from
  fill_pointer_events

Status in xorg-server package in Ubuntu:
  New

Bug description:
  What happens:
  ==
  Xorg crashes, all unsaved data will be lost.

  Reproduce
  ==
  I can't reproduce it on demand. But it happens after a while.
  - Usually I browse within a Firefox incognito window and use my middle mouse 
button. 
  - In todays particular case, I pressed the middle mouse button to close a 
window.
  - Note: I have `EasyStroke` setup to run on middle-mouse-button click 
(Program to enable mouse gestures). From experience, I strongly believe this is 
related.
  - Maybe `suspend`ing the computer several times is related to this problem.

  Backtrace
  ==
  Reading symbols from /usr/lib/xorg/Xorg...
  Reading symbols from 
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
  [New LWP 1106]
  [New LWP 1092]
  [New LWP 1094]
  [New LWP 1093]
  [New LWP 1096]
  [New LWP 978]
  [New LWP 1097]
  [New LWP 1098]
  [New LWP 1095]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -noliste'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280, 
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
  at ../../../../mi/mipointer.c:570
  570   ../../../../mi/mipointer.c: No such file or directory.
  [Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
  (gdb) bt full
  #0  miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280, 
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
  at ../../../../mi/mipointer.c:570
  pPointer = 0x0
  pScreenPriv = 0x56198f0b2eb0
  #1  0x56198e979d2c in miPointerSetPosition
  (pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0, 
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508, 
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
  at ../../../../mi/mipointer.c:669
  pScreenPriv = 
  pScreen = 0x56198f0b2810
  newScreen = 0x7fd0004d
  x = 981
  y = 77
  switch_screen = 0
  should_constrain_barriers = 1
  i = 
  pPointer = 0x56198f2249a0
  #2  0x56198e840e90 in positionSprite
  (dev=dev@entry=0x56198f5dc280, mode=mode@entry=0, 
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510, 
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500, 
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at 
../../../../dix/getevents.c:961
  scr = 
  tmpx = 981.15761067398421
  tmpy = 77.59964237213
  #3  0x56198e84141c in positionSprite
  (events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508, 
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510, 
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at 
../../../../dix/getevents.c:952
  scr = 0x56198f0b2810
  num_events = 2
  event = 
  raw = 0x7fd069d6b010
  screenx = 981.15761067398421
  screeny = 77.59964237213
  devx = 981.15761067398421
  devy = 77.59964237213
  sx = 
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0 
}, unaccelerated = {0 }}
  scr = 
  --Type  for more, q to quit, c to continue without paging--
  num_barrier_events = 0
  #4  fill_pointer_events (events=0x7fd069d6bc20, 
  events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6, 
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10, 
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
  num_events = 2
  event = 
  raw = 0x7fd069d6b010
  screenx = 981.15761067398421
  screeny = 77.59964237213
  devx = 981.15761067398421
  devy = 77.59964237213
  sx = 
  sy = 0
  mask = 
  {last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask = 
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0 
}, unaccelerated = {0 }}
  scr = 
  

[Touch-packages] [Bug 1909791] Re: Pulseaudio profiles not available (analouge stereo) so no sound

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965

This is probably another case of bug 1897965 so please check out the
suggestions there.

** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  Pulseaudio profiles not available (analouge stereo) so no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  regression-update bug 1876065
  I am running Pulseaudio version 1:13.99.2-1Ubuntu2.1 which I assume is a 
newer release than 1:13.99.1-1ubuntu3.3 as described in bug 1876065.

  I am trying to use and set analogue stereo sound as my default sound.

  On each boot Pulse reverts to these available profiles (extract only,
  full text as attachment)

  pacmd list-cards
  name: 
  ...
  profiles:
  input:analog-stereo: Analogue Stereo Input (priority 65, available: 
no)
  output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, 
available: unknown)
  output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) 
Output + Analogue Stereo Input (priority 5565, available: no)
  off: Off (priority 0, available: unknown)
  active profile: 
  ...

  After deleting the files in ~/.config/Pulse and entering: pulseaudio
  -k, the output changes to:

  pacmd list-cards
  name: 
  ...
  profiles:
  input:analog-stereo: Analogue Stereo Input (priority 65, available: 
no)
  output:analog-stereo: Analogue Stereo Output (priority 6500, 
available: unknown)
  output:analog-stereo+input:analog-stereo: Analogue Stereo Duplex 
(priority 6565,  available: no)
  output:iec958-stereo: Digital Stereo (IEC958) Output (priority 5500, 
available: unknown)
  output:iec958-stereo+input:analog-stereo: Digital Stereo (IEC958) 
Output + Analogue Stereo Input (priority 5565, available: no)
  off: Off (priority 0, available: unknown)
  active profile: 
  ...

  Having discovered the correct sink and profile one would proceed to make them 
the default by adding these 2 lines to /etc/pulse/default.pa:
  1/ set-default-sink alsa_output.pci-_09_00.3.analog-stereo
  2/ set-card-profile alsa_card.pci-_09_00.3 output:analog-stereo: Analogue 
Stereo Output, or,
 set-card-profile alsa_card.pci-_09_00.3 
output:analog-stereo+input:analog-stereo: Analogue Stereo Duplex

  Setting the default sink (1) causes no problems but only allows
  selection of iec958 stereo but attempting to set the default profile
  (2) and rebooting and opening PulseAudio Volume Control leads to a
  pop-up window displaying: establishing connection to PulseAudio please
  wait...  In other words PulseAudio is not running.

  So in summary I can get sound by buggering around each boot but cannot
  fix the issue on a permanent basis. This PC was release upgraded to
  20.10 yesterday.

  This is the 3rd PC in the last several months I have had to spend
  significant time to get sound working, the others I found a permanent
  work-around for. All are fairly new, the other PCs are running a Ryzon
  3000 and 5000 series CPU and Kubuntu 20.04 and 20.10. Having sound is
  something that should work out of the box.

  Operating System: Kubuntu 20.10
  KDE Plasma Version: 5.19.5
  KDE Frameworks Version: 5.74.0
  Qt Version: 5.14.2
  Kernel Version: 5.8.0-33-generic
  OS Type: 64-bit
  Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor
  Memory: 15.6 GiB of RAM
  Graphics Processor: GeForce GTX 1080/PCIe/SSE2

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

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


[Touch-packages] [Bug 1909877] Re: Clock in top bar doesn't update

2021-01-04 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2973
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2973

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2973
   Importance: Unknown
   Status: Unknown

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

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

** Tags added: fixed-in-3.38.2 fixed-upstream

** Also affects: mutter (Ubuntu Hirsute)
   Importance: Undecided
   Status: Fix Released

** Also affects: mutter (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Groovy)
   Status: New => Fix Committed

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

Title:
  Clock in top bar doesn't update

Status in GNOME Shell:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Groovy:
  Fix Committed
Status in mutter source package in Hirsute:
  Fix Released

Bug description:
  When exiting fullscreen from chromium (YouTube), the clock widget in
  the top bar seems stuck and only updates after being updated from the
  mouse hovering over it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.45.01  Thu Nov  5 
23:03:56 UTC 2020
   GCC version:  gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1)
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan  2 21:56:27 2021
  DistUpgraded: 2020-12-27 18:29:34,023 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.45.01, 5.4.0-58-generic, x86_64: installed
   nvidia, 455.45.01, 5.8.0-33-generic, x86_64: installed
   virtualbox, 6.1.14, 5.4.0-58-generic, x86_64: installed
   virtualbox, 6.1.14, 5.8.0-33-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] UHD Graphics 630 (Mobile) [1025:1264]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] 
[1025:1265]
  InstallationDate: Installed on 2020-12-11 (22 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Acer Nitro AN515-52
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=8753fbc2-cbcd-41b4-ad44-9e1a6f940ddf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-12-27 (6 days ago)
  dmi.bios.date: 08/05/2019
  dmi.bios.release: 1.28
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:br1.28:efr1.26:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1909352] Re: (1) video hangs or (2) screen goes blank and case fan turns on

2021-01-04 Thread Daniel van Vugt
It sounds like something is crashing or spinning. Also the attached Xorg
logs seem to be from 2019, which is confusing. So those should be
ignored... Please:

1. Run this command:

   journalctl -b0 > journal.txt

   and attach the resulting text file here.

2. Follow these instructions to check for crashes:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** Tags added: nvidia

** Summary changed:

- (1) video hangs or (2) screen goes blank and case fan turns on
+ [nvidia] (1) video hangs or (2) screen goes blank and case fan turns on

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-455
(Ubuntu)

** Changed in: nvidia-graphics-drivers-455 (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/1909352

Title:
  [nvidia] (1) video hangs or (2) screen goes blank and case fan turns
  on

Status in nvidia-graphics-drivers-455 package in Ubuntu:
  Incomplete

Bug description:
  Recover system by press and release reset switch.  Log in again.

  Had these issues with Ubuntu 18.04.  Updated to Nvidia drivers and issues 
resolved.  Updated to 20.04.1 and issues have returned.  Checked and see that 
Nvidia drivers newer than those packaged for use.  Available at Nvidia / Newest 
package and in use:
GeForce Game Ready Driver
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
Driver Version: 455.45 - Release Date: Tue Nov 17, 2020

GeForce Game Ready Driver
LINUX X64 (AMD64/EM64T) DISPLAY DRIVER
Driver Version: 455.38 - Release Date: Thu Oct 29, 2020

  Hopefully the command
  ubuntu-bug xorg
  attached all the information you may need.

  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:09:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 26 09:54:40 2020
  DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-56-generic, x86_64: installed
   nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150]
  InstallationDate: Installed on 2018-03-03 (1029 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F8
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350-Gaming 3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap

2021-01-04 Thread Daniel van Vugt
** Tags added: focal

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

Title:
  Keyboard layout used in the second place breaks keymap

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  It's hard to really summarize the issue here. If you use the Neo2
  layout somewhere, the keymap becomes garbled in a very specific way
  (see below). I am not really sure if it affects other keyboard layouts
  or what happens internally. I have selected gnome-control-center as
  the affected package, because this is, where it all starts. There are
  two issues, which are somehow connected.

  
  Reproduction steps (first issue):

  1. Open "Region & Language Settings" in gnome-control-center
  2. In "Input Sources" use "German (no dead keys)" in the FIRST place and 
"German (Neo 2)" in the second place (order matters!)
  3. Open your favorite text editor
  4. Use Super+Alt+Backspace to change to the Neo2 layout
  5. Press and hold the Mod4 key (right of Left Shift) and 3.
  6. You get a 3, expected would be №.

  Reproduction steps (second issue):

  1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" 
in the FIRST place and "German (no dead keys)" in the SECOND place
  2. Open Chromium and open any web page (it does not work with any other 
application)
  3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout
  4. Press Ctrl+F
  5. Instead of the In-Page-Search opening, you go to the search bar, which 
means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press 
Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even 
though Neo2 is selected, the old keymap is still somehow active.

  Info:

  1) Release: Ubuntu 20.04.1 LTS
  2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2
  3/4) See reproduction steps above

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

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


[Touch-packages] [Bug 1909327] Re: Lenovo T450s trackpad doesn't work after sleep

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1901350 ***
https://bugs.launchpad.net/bugs/1901350

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1901350, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** This bug has been marked a duplicate of bug 1901350
   [Lenovo ThinkPad T450s] Touchpad stops working after sleep

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

Title:
  Lenovo T450s trackpad doesn't work after sleep

Status in Ubuntu:
  New

Bug description:
  After sleep, the Lenovo T450s trackpad stops working. I have to rmmod
  psmouse and modprobe psmouse to get it to work again, or just use an
  external mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xserver-xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 25 12:29:17 2020
  DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  MachineType: LENOVO 20BWS1D61J
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (62 days ago)
  dmi.bios.date: 02/23/2019
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET72WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS1D61J
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS1D61J
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1909327/+subscriptions

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


[Touch-packages] [Bug 1909152] Re: color calibration fails when using gnome gui on 20.10

2021-01-04 Thread Daniel van Vugt
Sounds like bug 1719143. I wonder if your log contains the same "no
sensor" message?

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  color calibration fails when using gnome gui on 20.10

Status in colord package in Ubuntu:
  Incomplete
Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  in the past, I've used DisplayCalGUI to calibrate my displays.
  however, that software hasn't been updated to use Python3 properly, so
  it doesn't run on recent Ubuntu releases. I thought I'd try the
  builtin gnome calibration, but it seems completely broken on 20.10.
  I've tried two difference systems with fresh minimal installs, each
  has a different display and a different brand of colour calibration
  hardware. in both cases, they get to testing the coloured swatches,
  and fail, with an error saying:

  "Calibration failed!

  An internal error occurred that could not be recovered. You can remove
  the calibration device."

  
  however, looking in the output from `journalctl`, colord seems to claim that 
it succeeded in generating a profile. So I'm guessing there's something broken 
in the integration between colord and gnome-settings? all I know is it reports 
that it failed, and gnome doesn't show any new profile to use. here's the 
`journalctl` output:

  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: No of test patches = 64
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Omitted 0 zero 
measurements
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Find white & black 
points
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Initial white point = 
1.051779 0.999535 0.796168
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix...
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [46B blob data]
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.615651 
0.622859 0.645454
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]:  0.647113 
0.653246 0.680660
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]:  0.531396 
0.531212 0.553325
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Creating matrix and 
single gamma curve...
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: [26B blob data]
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Matrix = 0.009811 
0.389211 0.558809
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]:  0.144281 
0.347751 0.505066
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]:  0.198306 
0.283542 0.312788
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Gamma = -1.574397
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Doing White point fine 
tune:
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Before fine tune, rel 
WP = XYZ 0.95783065 0.99709777 0.79463644, Lab 99.887672 -0.619729 2.283133
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: After fine tune, rel 
WP = XYZ 0.96420288 1. 0.82490540, Lab 100.00 0.00 0.00
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]:  abs 
WP = XYZ 1.04542265 0.99666916 0.76687003, Lab 99.871064 14.218222 4.582465
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 
1.04542265 0.99666916 0.76687003, Lab = 99.871064 14.218222 4.582465
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Scaling White Point by 
1.003342 to make Y = 1.0
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Display Luminance = 
0.940928
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: White point XYZ = 
1.048916 1.00 0.769433
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Black point XYZ = 
1.048916 1.00 0.769433
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Done gamma/shaper and 
matrix creation
  Dec 23 13:47:29 krait.sudo.prv colord-session[514703]: Profile done

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: colord 1.4.4-2build1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: X-Cinnamon
  Date: Wed Dec 23 13:51:43 2020
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1909194] Re: Intel driver not installed properly

2021-01-04 Thread Daniel van Vugt
The correct kernel driver for Intel graphics is 'i915'. And the correct
Xorg driver for Intel graphics is 'modeset'. The attached files seem to
show both are working.

What exactly is the problem you are trying to solve?


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

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

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

Title:
  Intel driver not installed properly

Status in Ubuntu:
  Incomplete

Bug description:
  Intel driver not installed properly

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 24 14:14:13 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [8086:2017]
  InstallationDate: Installed on 2020-12-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a8184a82-57ed-4426-b8a0-55b2f2740603 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BEH6110H.86A.0044.2012.0531.1710
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61WW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG23116-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBEH6110H.86A.0044.2012.0531.1710:bd05/31/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-302:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909241] Re: Unreadable text with two monitors

2021-01-04 Thread Daniel van Vugt
There doesn't seem to be any external monitor connected in the attached
files. Please attach it and then run:

  xrandr --verbose > xrandr2.txt

and attach the resulting text file to this bug.


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

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

** Also affects: nvidia-graphics-drivers-450 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-450 (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/1909241

Title:
  Unreadable text with two monitors

Status in nvidia-graphics-drivers-450 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  - Machine: Dell 15 Inspiron Gaming Laptop (7567)
  - External 1080p60 monitor connected (recognized by X as 1080i60). Changing 
resolution manually fixes the resolution until next reboot.

  When external monitor is already connected before boot, and turning
  system on, X calculates wrong resolution/dpi for the monitors,
  rendering fonts very small. On default Gnome3 desktop, only the window
  titles are affected. On Kubuntu, all SDDM items and several desktop
  resources are affected too, rendering Kubuntu desktop unusable.

  Running gome-tricks applet restore font size when clicking on "Fonts" and 
changing font sizes.
  On Kubuntu, changing font settings does not have any effect. One can run on a 
root terminal "xrandr --dpi 96" as a workaround. But it solves only for the 
next window opening of a program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 24 11:50:44 2020
  DistUpgraded: 2020-08-23 11:50:00,001 DEBUG icon theme changed, re-reading
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-48-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-56-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:0798]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798]
  InstallationDate: Installed on 2020-03-22 (277 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  ProcEnviron:
   LANGUAGE=pt_BR:
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0a93686d-0008-4b58-8574-fe382bc8eda1 ro locale=pt_BR quiet splash 
intel_iommu=on vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-23 (123 days ago)
  dmi.bios.date: 06/19/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.asset.tag: H70NVN2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1909108] Re: Second static mouse pointer on two screen setup

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1873052 ***
https://bugs.launchpad.net/bugs/1873052

There are two known causes of this:

1. A bug in the 'amdgpu' kernel driver, supposedly fixed in future focal
kernel 5.4.69. Not sure about the 5.8 kernel series you are using...

2. A bug in Ubuntu's fractional scaling support.

Unfortunately you seem to be using both :( Still, bug 1873052 covers
both.

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

** This bug has been marked a duplicate of bug 1873052
   Showing two cursors after login

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

Title:
  Second static mouse pointer on two screen setup

Status in Ubuntu:
  New

Bug description:
  I have two screens and a Bluetooth mouse. When I wake PC up from the suspend 
the second frozen cursor is left on the screen.
  Screenshot tool does not see it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 23 11:06:00 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 4100] 
[1002:67e3] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon Pro WX 
4100] [1002:0b0d]
  InstallationDate: Installed on 2020-12-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Micro-Star International Co., Ltd. MS-7B89
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=2426cc97-af0d-4826-80aa-a05ec1ef1e8e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2020
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.70
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M MORTAR MAX (MS-7B89)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.70:bd04/21/2020:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B89
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1909108/+subscriptions

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


[Touch-packages] [Bug 1909132] Re: wavy diagonal line when scrolling in firefox

2021-01-04 Thread Daniel van Vugt
Does the problem only happen in full screen mode?

Also, please attach a photo of the issue if you can.

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

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

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

Title:
  wavy diagonal line when scrolling in firefox

Status in Ubuntu:
  Incomplete

Bug description:
  Scrolling in Firefox moves the web page up and down, but also causes a wavy 
line to appear, that extends horizontally and diagonally across the page, and 
disappears once you stop scrolling.
  i use ubuntu20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 23 21:32:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia-srv, 450.80.02, 5.4.0-58-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1b10]
 Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:1b10]
  InstallationDate: Installed on 2020-12-19 (4 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3496 IMC Networks 
   Bus 001 Device 003: ID 13d3:5a01 IMC Networks USB2.0 VGA UVC WebCam
   Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless 
Keyboard/Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X542URV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-58-generic 
root=UUID=2b8aa80b-3a8c-4397-9c75-472b469e71ec ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542URV.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542URV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542URV.308:bd05/21/2019:svnASUSTeKCOMPUTERINC.:pnX542URV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542URV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X542URV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909006] Re: Split screen

2021-01-04 Thread Daniel van Vugt
Please:

1. Take a photo of the problem and attach it here.

2. Try selecting 'Ubuntu on Wayland' on the login screen just before you
enter your password. Does a Wayland session have the same bug?


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

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

Title:
  Split screen

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My screen is split in 4 and forums have directed me to try and update
  my video graphics drivers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 14:52:26 2020
  DistUpgraded: 2020-08-03 22:59:11,316 DEBUG inhibit gnome-session idle
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1179:fb30]
  InstallationDate: Installed on 2020-02-09 (316 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: TOSHIBA Satellite C850-F74T
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=ed9c77f9-c96b-4904-8ba9-1576f2c3a198 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-08-03 (140 days ago)
  dmi.bios.date: 08/31/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.00:bd08/31/2012:svnTOSHIBA:pnSatelliteC850-F74T:pvrPSCBWF-011004F3:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: Satellite C850-F74T
  dmi.product.sku: PSCBWF
  dmi.product.version: PSCBWF-011004F3
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909131] Re: [radeon] wayland - cursor is not affected by night light mode

2021-01-04 Thread Daniel van Vugt
** Summary changed:

- wayland - cursor is not affected by night light mode
+ [radeon] wayland - cursor is not affected by night light mode

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

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

** Tags added: radeon

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

Title:
  [radeon] wayland - cursor is not affected by night light mode

Status in linux package in Ubuntu:
  New

Bug description:
  Even with the night light mode activated, the cursor remains blue (the
  filter is not applied).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 23 14:54:37 2020
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
  InstallationDate: Installed on 2020-07-24 (151 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-23 (61 days ago)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1892439] Re: [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all

2021-01-04 Thread Daniel van Vugt
** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No
  sound at all

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

Bug description:
  ThinkPad T410s. No audio from DisplayPort. Can't even select it as the audio 
source.
  Video works fine

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  voorhees857 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 20 21:46:38 2020
  InstallationDate: Installed on 2020-08-04 (16 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  voorhees857 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [2901A3U, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET38WW (1.16 )
  dmi.board.name: 2901A3U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET38WW(1.16):bd06/07/2010:svnLENOVO:pn2901A3U:pvrThinkPadT410s:rvnLENOVO:rn2901A3U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410s
  dmi.product.name: 2901A3U
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1908758] Re: no more HDMI devices after upgrade to 20_04

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1892439 ***
https://bugs.launchpad.net/bugs/1892439

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1892439, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1892439
   [Lenovo ThinkPad T410s, Intel IbexPeak HDMI, Digital Out, HDMI] No sound at 
all

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

Title:
  no more HDMI devices after upgrade to 20_04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Some two hours ago, I listened to audio through the extenal monitor,
  also used as display. Then I upgraded to 20_04 from 18_04. Now the
  display still works, but pulseaudio doesn't see nor offer the HDMI
  sink any longer on my lenovo T410s.

  What a bad mishap ... . And what to do now?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.8
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  udippel1690 F pulseaudio
   /dev/snd/pcmC0D0p:   udippel1690 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Dec 18 22:35:06 2020
  InstallationDate: Installed on 2018-08-30 (841 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924WZ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410s
  dmi.product.name: 2924WZ6
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1908758] Re: no more HDMI devices after upgrade to 20_04

2021-01-04 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1892439 ***
https://bugs.launchpad.net/bugs/1892439

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1897965, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

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

Title:
  no more HDMI devices after upgrade to 20_04

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Some two hours ago, I listened to audio through the extenal monitor,
  also used as display. Then I upgraded to 20_04 from 18_04. Now the
  display still works, but pulseaudio doesn't see nor offer the HDMI
  sink any longer on my lenovo T410s.

  What a bad mishap ... . And what to do now?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.8
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  udippel1690 F pulseaudio
   /dev/snd/pcmC0D0p:   udippel1690 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Dec 18 22:35:06 2020
  InstallationDate: Installed on 2018-08-30 (841 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to focal on 2020-12-18 (0 days ago)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6UET70WW (1.50 )
  dmi.board.name: 2924WZ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WZ6:pvrThinkPadT410s:rvnLENOVO:rn2924WZ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410s
  dmi.product.name: 2924WZ6
  dmi.product.version: ThinkPad T410s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1908273] Re: Segfault in iris_dri.so

2021-01-03 Thread Daniel van Vugt
Please try running this command in a Terminal window to find out the ID:

sudo more /var/lib/whoopsie/whoopsie-id

** Summary changed:

- Software stopped working
+ Segfault in iris_dri.so

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

Title:
  Segfault in iris_dri.so

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After update to Ubuntu 20.04.1 LTS some of my software stopped
  working, all of it is visualization software: VMD, Discovery Studio,
  PyMOL, Gmolden, Avogadro.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 15 14:41:52 2020
  DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego 
„./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie 
powiodło (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:8537]
  InstallationDate: Installed on 2020-05-20 (208 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 440 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago)
  dmi.bios.date: 04/27/2020
  dmi.bios.vendor: HP
  dmi.bios.version: R71 Ver. 01.11.01
  dmi.board.name: 8537
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 51.2A.00
  dmi.chassis.asset.tag: 5CD0097RK4
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G6
  dmi.product.sku: 5PQ09EA#AKD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

2021-01-03 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1897965 ***
https://bugs.launchpad.net/bugs/1897965

Yeah let's assume this is the same issue as bug 1897965. We'll only know
it's not after that one is fixed.

** This bug has been marked a duplicate of bug 1897965
   PulseAudio doesn't work when pipewire is installed (ie. KDE)

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

Title:
  [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After every reboot, the profile named "Analog Stereo Duplex" keeps
  disappearing on my laptop; only "Analog Stereo Input" and "Analog
  Stereo Output" are present. Without "duplex", I cannot use both the
  built-in microphone and the speakers/headphones at the same time.

  A workaround I found is to remove the user's configuration for
  pulseaudio and restart it:

  rm -rf .config/pulse
  pulseaudio -k

  This brings the "Analog Stereo Duplex" profile back until the next
  reboot.

  This problem started after an upgrade from Ubuntu 20.04 to 20.10.

  I made a screencast of this: https://youtu.be/Vlz5471EYVQ

  The laptop is MSI WE73-8SK.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov 11 10:50:54 2020
  InstallationDate: Installed on 2019-01-08 (673 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago)
  dmi.bios.date: 05/20/2019
  dmi.bios.release: 1.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C5IWS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: WE
  dmi.product.name: WE73 8SK
  dmi.product.sku: 17C5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Touch-packages] [Bug 1887968] Re: Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

2021-01-03 Thread Daniel van Vugt
** No longer affects: bluez (Ubuntu)

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

Title:
  Pairing with Bluetooth LE mice fails on a Huawei Matebook 13 AMD
  laptop with Realtek RTL8822CE Wifi/Bluetooth combo adapter

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 20.04 on a Huawei Matebook 13 AMD laptop which seems
  to use a Realtek RTL8822CE Wifi/Bluetooth combo adapter.

  I've been unsuccessful to pair with 2 different bluetooth mice.
  However bluetooth seems to work with other devices. I'm under the
  impression that this problem only happens with Bluetooth LE devices.

  Trying to pair using bluetoothctl fails with the
  org.bluez.Error.AuthenticationCanceled error:

  [bluetooth]# pair E5:5B:67:2A:09:76
  Attempting to pair with E5:5B:67:2A:09:76
  [CHG] Device E5:5B:67:2A:09:76 Connected: yes
  [CHG] Device E5:5B:67:2A:09:76 Connected: no
  Failed to pair: org.bluez.Error.AuthenticationCanceled

  A quick google search for org.bluez.Error.AuthenticationCanceled
  reported nothing relevant.

  Running btmon while trying to pair with the device gives me the
  following:

  Bluetooth monitor ver 5.53
  = Note: Linux version 5.4.0-40-generic (x86_64)   
0.998188
  = Note: Bluetooth subsystem version 2.22  
0.998193
  = New Index: E8:6F:38:9C:2B:3C (Primary,USB,hci0) 
 [hci0] 0.998194
  = Open Index: E8:6F:38:9C:2B:3C   
 [hci0] 0.998195
  = Index Info: E8:6F:38:9C:2B:3C (Realtek Semiconductor Corporation)   
 [hci0] 0.998197
  @ MGMT Open: bluetoothd (privileged) version 1.14 
   {0x0001} 0.998198
  @ MGMT Open: btmon (privileged) version 1.14  
   {0x0002} 0.998310
  @ MGMT Command: Pair Device (0x0019) plen 8   
{0x0001} [hci0] 8.162442
  LE Address: E5:5B:67:2A:09:76 (Static)
  Capability: KeyboardDisplay (0x04)
  < HCI Command: LE Set Extended Scan Parameters (0x08|0x0041) plen 8   
  #1 [hci0] 8.162527
  Own address type: Public (0x00)
  Filter policy: Ignore not in white list (0x01)
  PHYs: 0x01
  Entry 0: LE 1M
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 30.000 msec (0x0030)
  > HCI Event: Command Complete (0x0e) plen 4   
  #2 [hci0] 8.284618
LE Set Extended Scan Parameters (0x08|0x0041) ncmd 2
  Status: Success (0x00)
  < HCI Command: LE Set Extended Scan Enable (0x08|0x0042) plen 6   
  #3 [hci0] 8.284654
  Extended scan: Enabled (0x01)
  Filter duplicates: Enabled (0x01)
  Duration: 0 msec (0x)
  Period: 0.00 sec (0x)
  > HCI Event: Command Complete (0x0e) plen 4   
  #4 [hci0] 8.289616
LE Set Extended Scan Enable (0x08|0x0042) ncmd 2
  Status: Success (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 52 
  #5 [hci0] 8.343614
LE Extended Advertising Report (0x0d)
  Num reports: 1
  Entry 0
Event type: 0x0013
  Props: 0x0013
Connectable
Scannable
Use legacy advertising PDUs
  Data status: Complete
Legacy PDU Type: ADV_IND (0x0013)
Address type: Random (0x01)
Address: E5:5B:67:2A:09:76 (Static)
Primary PHY: LE 1M
Secondary PHY: No packets
SID: no ADI field (0xff)
TX power: 127 dBm
RSSI: -20 dBm (0xec)
Periodic advertising invteral: 0.00 msec (0x)
Direct address type: Public (0x00)
Direct address: 00:00:00:00:00:00 (OUI 00-00-00)
Data length: 0x1a
  03 19 c2 03 02 01 05 03 03 12 18 0e 09 52 61 7a  .Raz
  

[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

2021-01-03 Thread Daniel van Vugt
** No longer affects: mesa (Ubuntu)

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

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1490347] Re: [Regression] 16:04 and later - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

2021-01-03 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
 Assignee: Konrad Zapałowicz (kzapalowicz) => (unassigned)

** No longer affects: bluez (Ubuntu Wily)

** No longer affects: bluez

** Tags removed: wily
** Tags added: focal

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

Title:
  [Regression] 16:04 and later - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

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

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


[Touch-packages] [Bug 1908728] Re: Xorg crash

2021-01-03 Thread Daniel van Vugt
Also this might not be Xorg crashing, but gnome-shell. So I will remove
it from the 'xorg' package until we find out what process is crashing.

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

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

Title:
  Xorg crash

Status in Ubuntu:
  Incomplete

Bug description:
  Usually after the screen lock has been engaged for some time this
  error occurs. X will freeze and eventually crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 18 16:13:18 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 
1660 Ti] [1462:3750]
  InstallationDate: Installed on 2020-08-04 (135 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1908728] Re: Xorg crash

2021-01-03 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

Title:
  Xorg crash

Status in Ubuntu:
  Incomplete

Bug description:
  Usually after the screen lock has been engaged for some time this
  error occurs. X will freeze and eventually crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 18 16:13:18 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 455.38, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 
1660 Ti] [1462:3750]
  InstallationDate: Installed on 2020-08-04 (135 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B08911
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V8.1
  dmi.board.name: MS-78511
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 3.1
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV8.1:bd07/20/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B08911:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-78511:rvr3.1:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
  dmi.product.name: MS-B08911
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909322] Re: bug

2021-01-03 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => ubuntu

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

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

Title:
  bug

Status in Ubuntu:
  Incomplete

Bug description:
  no

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  455.38  Thu Oct 22 06:06:59 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 25 19:15:30 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 455.38, 5.4.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:39fe]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo GP107M [GeForce GTX 1050 Mobile] [17aa:39fe]
  InstallationDate: Installed on 2020-12-24 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated 
Camera (1280x720@30)
   Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81FV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=bb4f7afe-3371-42d3-b8a9-db84a78b4bbf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8JCN54WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion Y530-15ICH
  dmi.modalias: 
dmi:bvnLENOVO:bvr8JCN54WW:bd06/15/2020:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH:
  dmi.product.family: Legion Y530-15ICH
  dmi.product.name: 81FV
  dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH
  dmi.product.version: Lenovo Legion Y530-15ICH
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1909563] Re: Unknown to me

2021-01-03 Thread Daniel van Vugt
What are the errors you are referring to?

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

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

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

Title:
  Unknown to me

Status in Ubuntu:
  Incomplete

Bug description:
  Just Returning to Ubuntu and system produced some errors, reporting
  them but don't know how they were produced or how to repeat them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
  Uname: Linux 4.15.0-128-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Dec 29 13:47:12 2020
  DistUpgraded: 2020-12-29 12:56:20,466 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
 Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:30d8]
  InstallationDate: Installed on 2020-12-28 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: Hewlett-Packard HP Compaq 6720s
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic 
root=UUID=cec6ddcf-c54f-459c-97a6-0e6a2b0640f5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-12-29 (0 days ago)
  dmi.bios.date: 01/10/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.09
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0E
  dmi.chassis.asset.tag: CNU8090376
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.09:bd01/10/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.09:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.09
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Dec 29 12:59:58 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.8
  xserver.video_driver: modeset

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

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


[Touch-packages] [Bug 1909028] Re: Lines coming up on screen

2021-01-03 Thread Daniel van Vugt
Please attach a photo or video of the problem so we can understand what
kind of problem it is.

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

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

Title:
  Lines coming up on screen

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Multiple times I see that the scrolling/ video playing is not smooth
  and things come up in layers. This issue is especially visible while
  scrolling in vertical (tablet) orientation and watching videos with a
  lot of motion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 22 22:43:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 450.80.02, 5.4.0-42-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-58-generic, x86_64: installed (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:80d0]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 930M] [103c:80d0]
  InstallationDate: Installed on 2020-12-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 0bda:57c4 Realtek Semiconductor Corp. HP Truevision HD
   Bus 001 Device 007: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel 
Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ENVY x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=2518abd7-c310-4c54-84cb-86e6f8d53f4a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.19
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D0
  dmi.board.vendor: HP
  dmi.board.version: 84.29
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.19:bd12/07/2015:svnHP:pnHPENVYx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D0:rvr84.29:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP ENVY x360 Convertible
  dmi.product.sku: T5Q56PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

2020-12-17 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1797002 ***
https://bugs.launchpad.net/bugs/1797002

Hmm, maybe it depends on which project the bug is assigned to.

Certainly I and other people do see plenty of private bugs. But we can't
prove that we see all private bugs.

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM

2020-12-16 Thread Daniel van Vugt
Oops. It appears this was fixed in gdm3 in 2017. If you have any more
problems then please open new bugs.

** Tags added: a2dp

** No longer affects: gdm3 (Ubuntu Zesty)

** No longer affects: pulseaudio (Ubuntu Zesty)

** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #323
   https://gitlab.gnome.org/GNOME/gdm/-/issues/323

** Changed in: gdm
   Importance: Medium => Unknown

** Changed in: gdm
   Status: Expired => Unknown

** Changed in: gdm
 Remote watch: GNOME Bug Tracker #784856 => gitlab.gnome.org/GNOME/gdm/-/issues 
#323

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/340

** Changed in: pulseaudio
   Importance: Medium => Unknown

** Changed in: pulseaudio
 Remote watch: freedesktop.org Bugzilla #57167 => 
gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #340

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

** No longer affects: bluez (Ubuntu Xenial)

** No longer affects: gdm3 (Ubuntu Xenial)

** No longer affects: pulseaudio (Ubuntu Xenial)

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

** No longer affects: bluez (Ubuntu)

** No longer affects: pulseaudio (Ubuntu)

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

Title:
  Bluetooth audio devices/profiles are missing after logging in from GDM

Status in gdm:
  Unknown
Status in PulseAudio:
  Unknown
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 package in Debian:
  New

Bug description:
  This is actually a PulseAudio bug, but the workaround is to disable
  Bluetooth audio in GDM.

  Further discussion (and the source of my understanding about this
  issue) upstream are here:

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

  To summarise:

  GDM opens the A2DP profile for a11y purposes to allow screenreaders to
  output over BT audio devices. However Pulse doesn't release those
  devices when no audio is being played and the upshot is that once in
  the users session A2DP is not available for any Bluetooth audio
  devices, this means that you can only use the low quality profile
  HSP/HFP.

  There is a proposed workaround, but this means that a11y tools which
  need to output audio won't be able to use Bluetooth devices within
  GDM.

  I think that for 17.10 shipping this work-around is acceptable, and we
  should revisit in the 18.04 cycle to try and get a proper fix in PA.
  The suggested PA bug is:

  https://bugs.freedesktop.org/show_bug.cgi?id=57167

  but that hasn't seen movement since 2012.

  = The work around =

  From the Debian wiki:  https://wiki.debian.org/BluetoothUser/a2dp

  Disable the Bluetooth sink in the GDM PA daemon.

  Add this to /var/lib/gdm3/.config/pulse/default.pa

  #!/usr/bin/pulseaudio -nF
  #

  # load system wide configuration
  .include /etc/pulse/default.pa

  ### unload driver modules for Bluetooth hardware
  .ifexists module-bluetooth-policy.so
unload-module module-bluetooth-policy
  .endif

  .ifexists module-bluetooth-discover.so
unload-module module-bluetooth-discover
  .endif


  I have tested this, and I can confirm that it allows access to A2DP
  again in the user session.

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

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


[Touch-packages] [Bug 1908314] Re: Flicking screen on intel card

2020-12-15 Thread Daniel van Vugt
I'm guessing this would be bug 1896091, but to be sure please attach a
photo or video of the problem.

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

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

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

Title:
  Flicking screen on intel card

Status in Ubuntu:
  Incomplete

Bug description:
  Flicking screen on intel card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 15 22:46:01 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:07a0]
  InstallationDate: Installed on 2020-12-10 (5 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Latitude 7480
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-33-generic 
root=UUID=2d2eba82-dddc-469c-8508-b0cc7269226b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2020
  dmi.bios.release: 1.19
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.19.0
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.19.0:bd07/26/2020:br1.19:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1908314/+subscriptions

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


[Touch-packages] [Bug 1908273] Re: Software stopped working

2020-12-15 Thread Daniel van Vugt
The only relevant error I can see is a crash in your graphics driver is
affecting some Python app:

[681600.192682] python3.8[1480136]: segfault at 24 ip 7fbbd34a3c14 sp 
7ffc3c62aef0 error 6 in iris_dri.so[7fbbd2a72000+d49000]
[681600.192702] Code: 2b 7e 30 01 c7 81 ff ff ff 00 00 0f 87 9d 17 00 00 48 01 
c8 48 89 46 38 48 85 c9 0f 84 10 06 00 00 83 ea 01 81 ca 00 00 09 78 <89> 11 48 
8d 51 04 45 85 ff 74 76 41 8d 47 ff 48 8d 4c c1 0c 0f 1f

Please try:

1. Launching the affected apps from a Terminal window then copy and
paste any errors you see here.

2. Check for crash reports using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

** Changed in: mesa (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/1908273

Title:
  Software stopped working

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  After update to Ubuntu 20.04.1 LTS some of my software stopped
  working, all of it is visualization software: VMD, Discovery Studio,
  PyMOL, Gmolden, Avogadro.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 15 14:41:52 2020
  DistUpgraded: 2020-11-21 20:16:19,197 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Wykonanie procesu potomnego 
„./xorg_fix_proprietary.py” (Nie ma takiego pliku ani katalogu) się nie 
powiodło (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 (Whiskey Lake) 
[103c:8537]
  InstallationDate: Installed on 2020-05-20 (208 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. 
   Bus 001 Device 002: ID 0408:5373 Quanta Computer, Inc. HP HD Camera
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 440 G6
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=d81f0b8d-3e0f-4039-a46f-5c1c780cac2c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-21 (23 days ago)
  dmi.bios.date: 04/27/2020
  dmi.bios.vendor: HP
  dmi.bios.version: R71 Ver. 01.11.01
  dmi.board.name: 8537
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 51.2A.00
  dmi.chassis.asset.tag: 5CD0097RK4
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR71Ver.01.11.01:bd04/27/2020:svnHP:pnHPProBook440G6:pvr:rvnHP:rn8537:rvrKBCVersion51.2A.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G6
  dmi.product.sku: 5PQ09EA#AKD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1908265] Re: bad heating

2020-12-15 Thread Daniel van Vugt
I can't see any explanation for such a problem in the attached files.
Please run 'top' in a Terminal window and tell us what processes are
using the most CPU.

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

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

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

Title:
  bad heating

Status in Ubuntu:
  Incomplete

Bug description:
  i had dell pre-installed ubuntu, 
  but i had erase it.
  now i am facing heating issues

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
  Uname: Linux 4.15.0-124-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 15 17:59:23 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08c8]
  InstallationDate: Installed on 2020-12-11 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:5520 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 27c6:5301  
   Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 3480
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-124-generic 
root=UUID=4f0e25d7-2cd2-474f-9088-9df1ffccd1ce ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2020
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0H40C6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd02/12/2020:svnDellInc.:pnVostro3480:pvr:rvnDellInc.:rn0H40C6:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3480
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open

2020-12-15 Thread Daniel van Vugt
Yeah OK... Anyone experiencing this bug please also report it to BlueZ
upstream:

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers=Bluetooth

and then tell us the new bug ID.

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

Title:
  Bluetooth audio skips while the settings dialog is open

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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


[Touch-packages] [Bug 1797002] Re: Bluetooth audio skips while the settings dialog is open

2020-12-15 Thread Daniel van Vugt
Can anyone experiencing this bug please report it upstream?

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues

And then tell us the new issue ID.

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

Title:
  Bluetooth audio skips while the settings dialog is open

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  all my bluetooth headsets skips terribly after today's system update.
  it is heavy noticeable even on audio setting test form.
  it work just fine today before i applied updates.

  even reinstall ubuntu from scratch - didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  9 18:40:44 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-10-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ENVY 17 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1968
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG32907G7
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 17 Notebook PC
  dmi.product.version: 088510305B0610100
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 68:17:29:62:BE:6A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:16831 acl:64 sco:0 events:1798 errors:0
TX bytes:688571 acl:2399 sco:0 commands:125 errors:0

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

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


[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

2020-12-14 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1797002 ***
https://bugs.launchpad.net/bugs/1797002

Bug 1797002 is still open. We don't consider it resolved so this is now
a duplicate of that.

Yes you are free to delete any attachments from this bug that you wish.
In future if you are concerned about the privacy of attachments you can
mark your bugs as Private at the top-right of the page. Then only a very
small team of bug reviewers will be able to see them.

** This bug has been marked a duplicate of bug 1797002
   Bluetooth audio skips while the settings dialog is open

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Touch-packages] [Bug 1907905] Re: buging

2020-12-14 Thread Daniel van Vugt
Please attach a photo or video of the problem so we can understand what
you are seeing.

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

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

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

Title:
  buging

Status in Ubuntu:
  Incomplete

Bug description:
  just have a lot of gren points and com`s and disapiering picture

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:32:53 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1908071] Re: The video card driver is not working well

2020-12-14 Thread Daniel van Vugt
You appear to have the 'oibaf' PPA installed which is not supported and
is known to cause bugs.

Please use the 'ppa-purge' tool to remove that PPA from the system, then
reboot and if you experience any more problems then open a new bug.


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

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

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

Title:
  The video card driver is not working well

Status in Ubuntu:
  Invalid

Bug description:
  1)lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  2)apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu15
Candidate: 1:7.7+19ubuntu15
Version table:
   *** 1:7.7+19ubuntu15 500
  500 http://ua.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  3)Normal work

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Dec 14 15:49:46 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86a0]
  InstallationDate: Installed on 2020-12-13 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 413c:8505 Dell Computer Corp. Dell Universal Receiver
   Bus 001 Device 002: ID 04ca:7095 Lite-On Technology Corp. HP HD Camera
   Bus 001 Device 004: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ProBook 450 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic 
root=UUID=227ec1da-8070-4974-9577-9fe4a7428d90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2020
  dmi.bios.release: 6.1
  dmi.bios.vendor: HP
  dmi.bios.version: S71 Ver. 01.06.01
  dmi.board.name: 86A0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 02.2D.00
  dmi.chassis.asset.tag: 5CD024GVZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 2.45
  dmi.modalias: 
dmi:bvnHP:bvrS71Ver.01.06.01:bd10/19/2020:br6.1:efr2.45:svnHP:pnHPProBook450G7:pvr:rvnHP:rn86A0:rvrKBCVersion02.2D.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 450 G7
  dmi.product.sku: 6YY26AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.103+git2012121830.d034db~oibaf~g
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0~git2012130730.6a34a6~oibaf~g
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-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/+bug/1908071/+subscriptions

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


[Touch-packages] [Bug 1908064] Re: [Multiple bluetooth speakers, playback] Stuttering sound

2020-12-14 Thread Daniel van Vugt
1. This is probably an issue with the Bluetooth kernel driver. Please
run:

   lspci -kv > lspci.txt
   lsusb > lsusb.txt

   and attach the resulting text files here.

2. Please ensure the latest driver is installed by running:

   sudo apt install bcmwl-kernel-source

   and then reboot.

3. Try closing Settings, in case you are experiencing bug 1797002.


** Tags added: a2dp

** Tags added: a2dp-skip

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

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

Title:
  [Multiple bluetooth speakers, playback] Stuttering sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Constant stuttering sound, stuttering at maybe 10 times/second. More
  than one speaker with the same symptoms.

  Speakers work in Windows 10 / macOS 10.14+ running on same hardware.

  Same speakers work on Ubuntu Mate 18.04 32 bit running on different
  hardware.

  Remote control commands work (play/pause button on speakers).

  Initial pairing and connection requires from 2 to about 10 retries.
  All tested within 1 m distance.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  username3486 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 14 13:49:26 2020
  InstallationDate: Installed on 2020-10-30 (45 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=sv_SE.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Crossbeat
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [Crossbeat, playback] Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2020
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 264.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2E6FAB96566FE58C
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2E6FAB96566FE58C
  dmi.modalias: 
dmi:bvnAppleInc.:bvr264.0.0.0.0:bd06/10/2020:br0.1:svnAppleInc.:pnMacBookAir5,2:pvr1.0:rvnAppleInc.:rnMac-2E6FAB96566FE58C:rvrMacBookAir5,2:cvnAppleInc.:ct10:cvrMac-2E6FAB96566FE58C:
  dmi.product.family: MacBook Air
  dmi.product.name: MacBookAir5,2
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Touch-packages] [Bug 1907886] Re: avinfo is missing

2020-12-14 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: New => Triaged

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

** Tags added: focal groovy

** Tags removed: groovy
** Tags added: hirsute

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

Title:
  avinfo is missing

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  The "avinfo" command line tools available in bluez/tools
  (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not
  available in the package.

  The package bluez-tools (https://packages.ubuntu.com/groovy/bluez-
  tools) seems to map another project external to bluez
  (https://github.com/khvzak/bluez-tools) and not the "tools" folder of
  bluez.

  "avinfo" is used for example in order to check which codecs are
  supported by a headphone set (see https://github.com/EHfive
  /pulseaudio-modules-bt/issues/31#issuecomment-462717049).

  Maybe have "bluez-tools" map the "tools" folder of bluez, and move the
  other project to another package?

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

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


[Touch-packages] [Bug 1907906] Re: i want some support

2020-12-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => 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/1907906

Title:
  i want some support

Status in Ubuntu:
  Incomplete

Bug description:
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-32.34~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 12 15:39:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:5000]
  InstallationDate: Installed on 2020-11-14 (27 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 33663VG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-32-generic 
root=UUID=d4192c33-e4f0-4468-8ebe-426000ec3852 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2013
  dmi.bios.release: 2.54
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H0ET94WW (2.54 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33663VG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 2.54
  dmi.modalias: 
dmi:bvnLENOVO:bvrH0ET94WW(2.54):bd08/02/2013:br2.54:efr2.54:svnLENOVO:pn33663VG:pvrThinkPadEdgeE530c:rvnLENOVO:rn33663VG:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad Edge E530c
  dmi.product.name: 33663VG
  dmi.product.sku: LENOVO_MT_3366
  dmi.product.version: ThinkPad Edge E530c
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1~ubuntu0.20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1907882] Re: paprefs does not find modules

2020-12-14 Thread Daniel van Vugt
** Tags added: groovy

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

Title:
  paprefs does not find modules

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  on ubuntu 20.10 paprefs does not find modules, as it uses a hardcoded path.
  workaround:
  cd /usr/lib
  sudo ln -s pulse-13.99.2 pulse-13.99

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

  strace paprefs 2>&1 |grep /lib/pulse
  access("/usr/lib/pulse-13.99/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-13.99/modules/module-rygel-media-server.so", F_OK) = 
-1 ENOENT (No such file or directory)

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

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


[Touch-packages] [Bug 1907865] Re: Xorg crash

2020-12-14 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

** Summary changed:

- Xorg crash
+ Session crash

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

Title:
  Session crash

Status in Ubuntu:
  Incomplete

Bug description:
  I can't reliably reproduce this crash, and I don't know, even
  approximately, what's causing it, or what I might be doing to possibly
  cause it.  It just randomly crashes, and dumps me back to the login
  screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 11 15:35:06 2020
  DistUpgraded: 2020-10-07 09:25:09,468 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de]
  InstallationDate: Installed on 2016-12-06 (1466 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5470
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.name: 0VHKV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5470
  dmi.product.sku: 06DE
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Fri Aug 17 21:02:51 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1523 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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


[Touch-packages] [Bug 1903903] Re: [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

2020-12-14 Thread Daniel van Vugt
If you're using KDE on 20.10 then you might want to look at bug 1897965.

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

Title:
  [MSI MS-17C5] "Analog Stereo Duplex" profile keeps disappearing

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After every reboot, the profile named "Analog Stereo Duplex" keeps
  disappearing on my laptop; only "Analog Stereo Input" and "Analog
  Stereo Output" are present. Without "duplex", I cannot use both the
  built-in microphone and the speakers/headphones at the same time.

  A workaround I found is to remove the user's configuration for
  pulseaudio and restart it:

  rm -rf .config/pulse
  pulseaudio -k

  This brings the "Analog Stereo Duplex" profile back until the next
  reboot.

  This problem started after an upgrade from Ubuntu 20.04 to 20.10.

  I made a screencast of this: https://youtu.be/Vlz5471EYVQ

  The laptop is MSI WE73-8SK.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2 [modified: 
usr/share/pulseaudio/alsa-mixer/paths/analog-output-speaker.conf]
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Nov 11 10:50:54 2020
  InstallationDate: Installed on 2019-01-08 (673 days ago)
  InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-29 (13 days ago)
  dmi.bios.date: 05/20/2019
  dmi.bios.release: 1.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E17C5IWS.10F
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-17C5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE17C5IWS.10F:bd05/20/2019:br1.15:svnMicro-StarInternationalCo.,Ltd.:pnWE738SK:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: WE
  dmi.product.name: WE73 8SK
  dmi.product.sku: 17C5.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Touch-packages] [Bug 1871641] Re: Ubuntu never finishes booting: A start job is running for Hold until boot process finishes up (3min 7s / no limit) -- removing 'splash' kernel parm fixes it

2020-12-14 Thread Daniel van Vugt
Mordi,

Please ensure you have the latest updates installed:

  sudo apt update
  sudo apt full-upgrade

then reboot and tell us if you still experience the problem.

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

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

Title:
  Ubuntu never finishes booting: A start job is running for Hold until
  boot process finishes up (3min 7s / no limit) -- removing 'splash'
  kernel parm fixes it

Status in plymouth package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Boot process freezes at the splash screen and nothing happens after
  that. The computer can be suspended and it is able to return from
  suspend. Boot is possible by pressing escape early in the process to
  bypass plymouth.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: plymouth 0.9.4git20200323-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Wed Apr  8 14:30:13 2020
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2020-04-08 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 7469A23
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e12af5fd-b700-4292-8727-70345cb61c8e ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET72WW (3.22 )
  dmi.board.name: 7469A23
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET72WW(3.22):bd10/25/2012:svnLENOVO:pn7469A23:pvrThinkPadX200s:rvnLENOVO:rn7469A23:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X200s
  dmi.product.name: 7469A23
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1812556] Re: Screen lock does not work

2020-12-08 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen when using lightdm with gnome-shell

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

Title:
  Screen lock does not work

Status in lightdm package in Ubuntu:
  New

Bug description:
  Since upgrading to 18.04 the screen lock no longer works. The screen
  will not lock automatically despite the setting and even Ctrl+Alt+L
  and Super+L fail to do anything.

  I've checked that

  $ gsettings get org.gnome.desktop.lockdown disable-lock-screen
  false

  I'm not sure if lightdm is the correct package. I'm using lightdm,
  since gdm just gave me a black screen. But not sure which package
  should handle the lock.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 20 13:00:21 2019
  InstallationDate: Installed on 2012-11-10 (2261 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to bionic on 2019-01-17 (2 days ago)

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

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


[Touch-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend

2020-12-08 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen when using lightdm with gnome-shell

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

Title:
  lightdm does not greet or present login prompt when resuming from
  laptop suspend

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Expected result: when opening laptop lid the lock screen presents
  itself so I can unlock my session

  Actual result: the contents of my desktop are visible (windows, etc)
  and I can move my mouse cursor around but I cannot interact with the
  desktop session at all. Hovering over UI elements or clicking them has
  no effect.

  In order to get the login prompt I have to ctrl+alt+f1, login at the
  console, and run sudo systemctl restart lightdm, then I can login
  normally and resume whatever I was doing from before I closed the
  laptop lid.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 23 09:08:32 2019
  InstallationDate: Installed on 2019-11-09 (14 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1870803] Re: LightDM unlocks without Password

2020-12-08 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen when using lightdm with gnome-shell

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

Title:
  LightDM unlocks without Password

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When doing `dm-tool lock` the screen locks. Then pressing CTRL+ALT+F7
  immediately returns me to my Session without any need to type the
  password. When logging in mutliple users I can switch between the
  users with CTRL+ALT+F7 and CTRL+ALT+F8 without needing any of the
  users passwords.

  I tested this with both lightdm-gtk-greeter and slick-greeter and the
  behavior is the same for both.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-screensaver (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Sat Apr  4 17:05:51 2020
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen locking issue
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

2020-12-08 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715435 ***
https://bugs.launchpad.net/bugs/1715435

** This bug has been marked a duplicate of bug 1715435
   Can't lock screen when using lightdm with gnome-shell

-- 
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:
  Confirmed

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


  1   2   3   4   5   6   7   8   9   10   >