[Touch-packages] [Bug 1955566] Re: iris driver doesn't load correctly on intel pci_id 0x4688

2021-12-23 Thread Mathew Hodson
** Changed in: mesa (Ubuntu)
   Importance: Undecided => Low

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

Title:
  iris driver doesn't load correctly on intel pci_id 0x4688

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  [Impact]

   * iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
  we expect the Intel GPU uses iris driver.

  [Test Plan]

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Mesa/X.org
  OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
  ...
  OpenGL version string: 3.1 Mesa 21.0.3

   * After applying the fix, it shows:

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) Graphics (ADL-S GT1)
  ...
  OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 
(git-d4975a0dbc)

  [Where problems could occur]

   * This patch is backport the PCI ID mapping for enabling iris driver which 
is expected when users have a GPU.
   * If there is any issue occur then we need to fix it with iris driver.

  [Other Info]

   * It already in upstream and we have a platform which using ADL-HX in OEM 
project. Thus, we need to enable iris on it at least on focal.
   * The patch is simple as to add "CHIPSET(0x4688, adl_gt1, "ADL-S GT1", 
"Intel(R) Graphics")" in "include/pci_ids/iris_pci_ids.h".
   * Patch backported from df5b14969f9869f363bcc8b2a564c85aaa481597

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


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


[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot

2021-12-23 Thread Bin Li
@daniel,

 I reported a new issue. Let's focus on below links. Thanks!

https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1955690

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

Title:
  Prompt error message "Failed to unmount /oldroot" when shutdown or
  reboot

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  root fs is not cleanly unmounted on shutdown

  [test case]

  create a file in /etc/binfmt.d/TestFormat.conf with the following
  content:

  :TestFormat:M::XX::/bin/true:F

  reboot the system, and then shutdown or reboot again, and watch the
  serial console for the error message:

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  [regression potential]

  any regression would likely cause problems on shutdown and/or reboot,
  or may cause problems with unmounted root fs on shutdown/reboot

  [scope]

  this is needed only for f

  this is fixed upstream with PR 15566 which is included in v246, so
  this is fixed already in g and later

  this isn't reproducable on b

  [original description]

  On ubuntu 20.04, with latest kernel and systemd, it will show error on
  ThinkPad X1.

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  systemd 245.4-4ubuntu3.6
  kernel: 5.8.0-53

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


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


[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot

2021-12-23 Thread Bin Li
@daniel,

 Thanks for the solution, and it sounds good, could you help make merge
request to finalrd to ask the maintainer's idea?

 From my side, currently finalrd used by mdadm, I would like to remove
the dependency cause mdadm.

 In systemd/mdadm.shutdown from mdadm, it also do "mdadm --wait-clean
--scan".

$ cat ./debian/mdadm.finalrd
#!/bin/sh
# SPDX-License-Identifier: GPL-3.0-only
set -e

if [ "$1" = "setup" ]
then
. /usr/share/initramfs-tools/hook-functions
copy_exec /sbin/mdadm
copy_exec /sbin/mdmon

exit 0
fi

mdmon --all --takeover
mdadm -vv --wait-clean --scan
mdadm -vv --stop --scan

 Thanks!

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

Title:
  Prompt error message "Failed to unmount /oldroot" when shutdown or
  reboot

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  root fs is not cleanly unmounted on shutdown

  [test case]

  create a file in /etc/binfmt.d/TestFormat.conf with the following
  content:

  :TestFormat:M::XX::/bin/true:F

  reboot the system, and then shutdown or reboot again, and watch the
  serial console for the error message:

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  [regression potential]

  any regression would likely cause problems on shutdown and/or reboot,
  or may cause problems with unmounted root fs on shutdown/reboot

  [scope]

  this is needed only for f

  this is fixed upstream with PR 15566 which is included in v246, so
  this is fixed already in g and later

  this isn't reproducable on b

  [original description]

  On ubuntu 20.04, with latest kernel and systemd, it will show error on
  ThinkPad X1.

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  systemd 245.4-4ubuntu3.6
  kernel: 5.8.0-53

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


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


[Touch-packages] [Bug 1928200] Re: Prompt error message "Failed to unmount /oldroot" when shutdown or reboot

2021-12-23 Thread Daniel
I still have this problem, but I have solved it.


I create files

file: /etc/systemd/system/kill-plymouthd.service
[Unit]
Description=kill plymouthd
After=umount.target
DefaultDependencies=false

[Service] Type=oneshot
ExecStart=/usr/bin/pkill plymouthd

[Install] WantedBy=final.target


file: /etc/systemd/system/rm-nvidia.service
[Unit]
Description=rm nvidia modules
After=umount.target
DefaultDependencies=false

[Service] Type=oneshot
ExecStart=/usr/sbin/rmmod nvidia_uvm
ExecStart=/usr/sbin/rmmod nvidia_drm
ExecStart=/usr/sbin/rmmod nvidia_modeset
ExecStart=/usr/sbin/rmmod nvidia
ExecStart=/usr/sbin/rmmod i2c_nvidia_gpu

[Install]
WantedBy=final.target

execute:
sudo systemctl daemon-reload
sudo systemctl enable rm-nvidia.service
sudo systemctl enable kill-plymouthd.service

for debug this problem i installed finalrd ane created executable

/etc/finalrd/sleep.finalrd

#!/bin/sh

set -x
if [ "$1" = "setup" ] then
. /usr/share/initramfs-tools/hook-functions 
copy_exec /usr/bin/sleep
copy_exec /usr/bin/mount

exit 0
fi  

#your debug script
mount
sleep 30

i have second system with ubuntu and in this second system i do not have
nvidia drivers and i only created kill-plymouthd.service  and this also
work.

 and i did know why plymouthd is not killed befor umount root fs..

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

Title:
  Prompt error message "Failed to unmount /oldroot" when shutdown or
  reboot

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  root fs is not cleanly unmounted on shutdown

  [test case]

  create a file in /etc/binfmt.d/TestFormat.conf with the following
  content:

  :TestFormat:M::XX::/bin/true:F

  reboot the system, and then shutdown or reboot again, and watch the
  serial console for the error message:

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  [regression potential]

  any regression would likely cause problems on shutdown and/or reboot,
  or may cause problems with unmounted root fs on shutdown/reboot

  [scope]

  this is needed only for f

  this is fixed upstream with PR 15566 which is included in v246, so
  this is fixed already in g and later

  this isn't reproducable on b

  [original description]

  On ubuntu 20.04, with latest kernel and systemd, it will show error on
  ThinkPad X1.

  sd-umount[1334]: Failed to unmount /oldroot: Device or resource busy

  systemd 245.4-4ubuntu3.6
  kernel: 5.8.0-53

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


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


Re: [Touch-packages] [Bug 1955664] Re: Richo Aficio SG3110DN Driver Not Working

2021-12-23 Thread Don McCormick
Paul,

Thanks for responding to the bug report. Have been attempting to get 
this Ricoh Aficio SG3110DN printer working on Ubuntu 20.04 for a few 
days now with no success. Works fine with Windows 10, so I am stumped.

Any ideas?

Don McCormick

On 12/23/21 11:22 AM, Paul White wrote:
> ** Tags added: focal
>
> ** Package changed: ubuntu => cups (Ubuntu)
>

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

Title:
  Richo Aficio SG3110DN Driver Not Working

Status in cups package in Ubuntu:
  New

Bug description:
  Just dual booted Ubuntu 20.04 and all works well except the printer driver 
for Ricoh Aficio SG3110DN provided in Add New Printer indicates that the 
printer is not responding. Printer works fine on same machine using Windows 10 
OS. 
  What is the fix?

  Printing trounleshooter:

  Retrieve Journal Entries

  No system journal entries were found. This may be because you are not
  an administrator. To fetch journal entries please run this command:

  su -c 'journalctl -u cups.service --since="None" --until="2021-12-23
  10:02:45"' > troubleshoot-logs.txt

  
  Status Messages:

  There are status messages associated with this queue.

  The printer’s state message is: ‘The printer is not responding.’.

  
  Printing troubleshooter

  Sorry!

  There is not obvious solution to this problem. Your answers have been
  collected together with other useful information. If you would like to
  report a bug, please include this information.

  >Diagnostic Output (Advanced)
  su -c 'journalctl -u cups.service --since="None" --until="2021-12-23 
10:02:45"' > troubleshoot-logs.txt

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


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


[Touch-packages] [Bug 1955664] Re: Richo Aficio SG3110DN Driver Not Working

2021-12-23 Thread Paul White
** Tags added: focal

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

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

Title:
  Richo Aficio SG3110DN Driver Not Working

Status in cups package in Ubuntu:
  New

Bug description:
  Just dual booted Ubuntu 20.04 and all works well except the printer driver 
for Ricoh Aficio SG3110DN provided in Add New Printer indicates that the 
printer is not responding. Printer works fine on same machine using Windows 10 
OS. 
  What is the fix?

  Printing trounleshooter:

  Retrieve Journal Entries

  No system journal entries were found. This may be because you are not
  an administrator. To fetch journal entries please run this command:

  su -c 'journalctl -u cups.service --since="None" --until="2021-12-23
  10:02:45"' > troubleshoot-logs.txt

  
  Status Messages:

  There are status messages associated with this queue.

  The printer’s state message is: ‘The printer is not responding.’.

  
  Printing troubleshooter

  Sorry!

  There is not obvious solution to this problem. Your answers have been
  collected together with other useful information. If you would like to
  report a bug, please include this information.

  >Diagnostic Output (Advanced)
  su -c 'journalctl -u cups.service --since="None" --until="2021-12-23 
10:02:45"' > troubleshoot-logs.txt

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


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


[Touch-packages] [Bug 1955664] [NEW] Richo Aficio SG3110DN Driver Not Working

2021-12-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Just dual booted Ubuntu 20.04 and all works well except the printer driver for 
Ricoh Aficio SG3110DN provided in Add New Printer indicates that the printer is 
not responding. Printer works fine on same machine using Windows 10 OS. 
What is the fix?

Printing trounleshooter:

Retrieve Journal Entries

No system journal entries were found. This may be because you are not an
administrator. To fetch journal entries please run this command:

su -c 'journalctl -u cups.service --since="None" --until="2021-12-23
10:02:45"' > troubleshoot-logs.txt


Status Messages:

There are status messages associated with this queue.

The printer’s state message is: ‘The printer is not responding.’.


Printing troubleshooter

Sorry!

There is not obvious solution to this problem. Your answers have been
collected together with other useful information. If you would like to
report a bug, please include this information.

>Diagnostic Output (Advanced)
su -c 'journalctl -u cups.service --since="None" --until="2021-12-23 10:02:45"' 
> troubleshoot-logs.txt

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


** Tags: focal
-- 
Richo Aficio SG3110DN Driver Not Working
https://bugs.launchpad.net/bugs/1955664
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups in Ubuntu.

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


[Touch-packages] [Bug 1954742] Re: Sound starts delayed (4sec) when using HDMI audio

2021-12-23 Thread DarkTrick
Apparently there was a problem with the sample output rate. I had to
`set both default-sample-rate and alternate-sample-rate to 48000 in
/etc/pulse/daemon.conf`

Apparently switching the output sample rate for devices takes about 4
seconds.

Details:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305#note_1197529


My personal problem is solved by applying the specific configuration.

Open questions:

(1) Could the problem of "it takes 4 seconds to change output sampling rate" be 
a general problem that should be solved (where? in pulseaudio?).
(2) Or should Ubuntu deliver with a defined output sample rate in 
`/etc/pulse/daemon.conf`?

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

Title:
  Sound starts delayed (4sec) when using HDMI audio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Reproduce:
  - Connect notebook to external monitor via HDMI
  - Start random video in youtube / vlc player

  Actual:
  - Sound starts with about 4secs of delay

  Reproducible: 
  always

  
  Misc:
  The package is just a guess.

  
  lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:15.0+dfsg1-1ubuntu2.2
Candidate: 1:15.0+dfsg1-1ubuntu2.2
Version table:
   *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%)
  500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:15.0+dfsg1-1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
  Uname: Linux 5.13.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nimono 2373 F pulseaudio
   /dev/snd/pcmC0D3p:   nimono 2373 F...m pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue Dec 14 15:20:56 2021
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago)
  dmi.bios.date: 01/23/2018
  dmi.bios.release: 1.7
  dmi.bios.vendor: FUJITSU // Insyde Software Corp.
  dmi.bios.version: Version 1.07
  dmi.board.name: FJNB2BB
  dmi.board.vendor: FUJITSU
  dmi.board.version: A2
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku:
  dmi.product.family: LIFEBOOK-JR
  dmi.product.name: FMVWB3U27
  dmi.sys.vendor: FUJITSU
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277

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


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


[Touch-packages] [Bug 1953065] Re: 2.13.0 FTBFS

2021-12-23 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/ust/+git/ust/+merge/413463

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

Title:
  2.13.0 FTBFS

Status in LTTng-UST:
  Unknown
Status in ust package in Ubuntu:
  In Progress

Bug description:
  I tried to merge ust from debian into ubuntu, to fix a build-time
  dependency, but stumbled on an FTBFS with that version.

  I filed upstream bug at https://bugs.lttng.org/issues/1337

  It basically happens in some new test cases that were added in 2.13.0
  and crash when we build it using our default -Wl,-Bsymbolic-flags
  linker option, which we have been using for years in Ubuntu.

  Here is the testsuite log output:
  
 lttng-ust 2.14.0-pre: tests/test-suite.log
  

  # TOTAL: 246
  # PASS:  241
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  4
  # XPASS: 0
  # ERROR: 1

  .. contents:: :depth: 2

  ERROR: regression/abi0-conflict/test_abi0_conflict
  ==

  1..22
  # LD_PRELOAD
  # regression/abi0-conflict/test_abi0_conflict: LD_PRELOAD
  ok 1 - LD_PRELOAD: no-ust app works
  PASS: regression/abi0-conflict/test_abi0_conflict 1 - LD_PRELOAD: no-ust app 
works
  ok 2 - LD_PRELOAD: no-ust app with abi0 preload succeeds
  PASS: regression/abi0-conflict/test_abi0_conflict 2 - LD_PRELOAD: no-ust app 
with abi0 preload succeeds
  ./regression/abi0-conflict/test_abi0_conflict: line 56: 592651 Aborted
 (core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}" 
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
  ok 3 - LD_PRELOAD: no-ust app with abi0 and abi1 preload fails
  PASS: regression/abi0-conflict/test_abi0_conflict 3 - LD_PRELOAD: no-ust app 
with abi0 and abi1 preload fails
  ./regression/abi0-conflict/test_abi0_conflict: line 59: 592652 Aborted
 (core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}" 
"${CURDIR}/app_noust" > "$STD_OUTPUT" 2> "$STD_ERROR"
  ok 4 - LD_PRELOAD: no-ust app with abi1 and abi0 preload fails
  PASS: regression/abi0-conflict/test_abi0_conflict 4 - LD_PRELOAD: no-ust app 
with abi1 and abi0 preload fails
  ok 5 - LD_PRELOAD: ust app works
  PASS: regression/abi0-conflict/test_abi0_conflict 5 - LD_PRELOAD: ust app 
works
  ./regression/abi0-conflict/test_abi0_conflict: line 68: 592669 Aborted
 (core dumped) LD_PRELOAD="${LIBFAKEUST0}" "${CURDIR}/app_ust" > 
"$STD_OUTPUT" 2> "$STD_ERROR"
  ok 6 - LD_PRELOAD: ust app with abi0 preload fails
  PASS: regression/abi0-conflict/test_abi0_conflict 6 - LD_PRELOAD: ust app 
with abi0 preload fails
  ./regression/abi0-conflict/test_abi0_conflict: line 71: 592683 Aborted
 (core dumped) LD_PRELOAD="${LIBFAKEUST0}:${LIBUST1}" 
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
  ok 7 - LD_PRELOAD: ust app with abi0 and abi1 preload fails
  PASS: regression/abi0-conflict/test_abi0_conflict 7 - LD_PRELOAD: ust app 
with abi0 and abi1 preload fails
  ./regression/abi0-conflict/test_abi0_conflict: line 74: 592684 Aborted
 (core dumped) LD_PRELOAD="${LIBUST1}:${LIBFAKEUST0}" 
"${CURDIR}/app_ust" > "$STD_OUTPUT" 2> "$STD_ERROR"
  ok 8 - LD_PRELOAD: ust app with abi1 and abi0 preload fails
  PASS: regression/abi0-conflict/test_abi0_conflict 8 - LD_PRELOAD: ust app 
with abi1 and abi0 preload fails
  # dlopen
  # regression/abi0-conflict/test_abi0_conflict: dlopen
  ok 9 - dlopen: no-ust app works
  PASS: regression/abi0-conflict/test_abi0_conflict 9 - dlopen: no-ust app works
  ok 10 - dlopen: no-ust app with abi1 and abi1 succeeds
  PASS: regression/abi0-conflict/test_abi0_conflict 10 - dlopen: no-ust app 
with abi1 and abi1 succeeds
  ./regression/abi0-conflict/test_abi0_conflict: line 92: 592689 Aborted
 (core dumped) LD_LIBRARY_PATH="$LIBFAKEUST0_PATH:$LIBUST1_PATH" 
"${CURDIR}/app_noust_dlopen" abi0_abi1 > "$STD_OUTPUT" 2> "$STD_ERROR"
  ok 11 - dlopen: no-ust app with abi0 and abi1 fails
  PASS: regression/abi0-conflict/test_abi0_conflict 11 - dlopen: no-ust app 
with abi0 and abi1 fails
  not ok 12 - dlopen: no-ust app with abi1 and abi0 fails
  FAIL: regression/abi0-conflict/test_abi0_conflict 12 - dlopen: no-ust app 
with abi1 and abi0 fails
  #   Failed test 'dlopen: no-ust app with abi1 and abi0 fails'
  # regression/abi0-conflict/test_abi0_conflict: Failed test 'dlopen: no-ust 
app with abi1 and abi0 fails'
  #   in /home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at 
line 300.
  # regression/abi0-conflict/test_abi0_conflict: in 
/home/ubuntu/git/packages/ust/lttng-ust/tests/utils/tap.sh:isnt() at line 300.
  #  got: '0'
  # regression/abi0-conflict/test_abi0_conflict: got: '0'
  # expected: '0'
  # regression/abi0-conflict/test_abi0_conflict: expected: '0'
  ok 13 - dlopen: ust

[Touch-packages] [Bug 1955636] Re: Fails to detect monitors connected to docking stations

2021-12-23 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => libxrandr (Ubuntu)

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

Title:
  Fails to detect monitors connected to docking stations

Status in libxrandr package in Ubuntu:
  New

Bug description:
  The graphics system fails to detect monitors connected to ports on
  docking stations. The ports themselves are detected an reported, but
  stay in state "disconnected" regardless there are monitors connected
  or not.

  Internally the laptop has two Display-Ports, two HDMI-Ports and the build in 
Display. xrandr reports them:
  - eDP-1 (Internal display)
  - DP-1 (Internal Display-Port-1)
  - DP-2 (Internal Display-Port-2)
  - HDMI-1 (Internal HDMI-Port-1)
  - HDMI-2 (Internal HDMI-Port-2)

  
  Two of the four ports are wired to the laptop hardware-ports
  - DP-1 -> Mini-Display-Port
  - HDMI-1 -> HDMI-Port

  Within the docking station there are additional hardware ports wired:
  - HDMI-1 -> VGA
  - DP-1 -> DVI
  - DP-1 -> Display-Port-1
  - HDMI-2 -> HDMI
  - DP-2 -> Display-Port-2

  Connecting displays to any of these ports is reported running Windows
  10, or Ubuntu 21.04. With Ubuntu 21.10 only displays connected to the
  Mini-Display-Port are reported. All other hardware ports are ignored
  and will stay in disconnected state, even if active monitors are
  connected to them.

  This is what xrandr reports if two monitors are connected directly to the 
laptop, one via HDMI, the other via Mini-Display-Port:
  eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
308mm x 173mm
 1920x1080 60.01*+  60.0159.9759.9659.93  
 [...]
 360x202   59.5159.13  
 320x180   59.8459.32  
  DP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y 
axis) 520mm x 330mm
 1920x1200 59.95*+
 [...]
 640x480   75.0059.94  
 720x400   70.08  
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)

  The monitors connected to the build in HDMI are not recognized, as
  those connected to both Display-Ports available on this dock.

  Connecting monitors only to the Dock only the build in display is
  recognized, no other.

  Seen this on:
  - ThinkPad T450s (20BW)
  - ThinkPad T460s (20FA)
  - ThinkPad T470s (20HF, 20HG)

  With ThinkPad Ultra Dock (40A2)

  Then:
  - ThinkPad T480
  - ThinkPad T490
  - ThinkPad T14

  With ThinkPad Ultra Dock (40AJ)

  
  Same Problem exists with
  - Acer TravelMate and Acer-Dock II
  - Dell and Dell-Docks

  The bug might be within the kernel, graphics subsystems, x11, wayland.
  I could verity that going back to Ubuntu 21.04 (hirsute) this bug vanishes. 
And starts showing up again after upgrading to 21.10 (impish).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libxrandr2 2:1.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Thu Dec 23 10:20:55 2021
  DistUpgraded: Fresh install
  DistroCodename: impish
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
  InstallationDate: Installed on 2021-08-18 (127 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: LENOVO 20FAS16K00
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.13.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro quiet splash vt.handoff=1
  SourcePackage: libxrandr
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET52W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS16K00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET52W(1.20):bd11/30/2016:br1.20:efr1.9:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS16K00
  dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1u

[Touch-packages] [Bug 1955636] [NEW] Fails to detect monitors connected to docking stations

2021-12-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The graphics system fails to detect monitors connected to ports on
docking stations. The ports themselves are detected an reported, but
stay in state "disconnected" regardless there are monitors connected or
not.

Internally the laptop has two Display-Ports, two HDMI-Ports and the build in 
Display. xrandr reports them:
- eDP-1 (Internal display)
- DP-1 (Internal Display-Port-1)
- DP-2 (Internal Display-Port-2)
- HDMI-1 (Internal HDMI-Port-1)
- HDMI-2 (Internal HDMI-Port-2)


Two of the four ports are wired to the laptop hardware-ports
- DP-1 -> Mini-Display-Port
- HDMI-1 -> HDMI-Port

Within the docking station there are additional hardware ports wired:
- HDMI-1 -> VGA
- DP-1 -> DVI
- DP-1 -> Display-Port-1
- HDMI-2 -> HDMI
- DP-2 -> Display-Port-2

Connecting displays to any of these ports is reported running Windows
10, or Ubuntu 21.04. With Ubuntu 21.10 only displays connected to the
Mini-Display-Port are reported. All other hardware ports are ignored and
will stay in disconnected state, even if active monitors are connected
to them.

This is what xrandr reports if two monitors are connected directly to the 
laptop, one via HDMI, the other via Mini-Display-Port:
eDP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 308mm 
x 173mm
   1920x1080 60.01*+  60.0159.9759.9659.93  
   [...]
   360x202   59.5159.13  
   320x180   59.8459.32  
DP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 
520mm x 330mm
   1920x1200 59.95*+
   [...]
   640x480   75.0059.94  
   720x400   70.08  
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)

The monitors connected to the build in HDMI are not recognized, as those
connected to both Display-Ports available on this dock.

Connecting monitors only to the Dock only the build in display is
recognized, no other.

Seen this on:
- ThinkPad T450s (20BW)
- ThinkPad T460s (20FA)
- ThinkPad T470s (20HF, 20HG)

With ThinkPad Ultra Dock (40A2)

Then:
- ThinkPad T480
- ThinkPad T490
- ThinkPad T14

With ThinkPad Ultra Dock (40AJ)


Same Problem exists with
- Acer TravelMate and Acer-Dock II
- Dell and Dell-Docks

The bug might be within the kernel, graphics subsystems, x11, wayland.
I could verity that going back to Ubuntu 21.04 (hirsute) this bug vanishes. And 
starts showing up again after upgrading to 21.10 (impish).

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: libxrandr2 2:1.5.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Thu Dec 23 10:20:55 2021
DistUpgraded: Fresh install
DistroCodename: impish
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2233]
InstallationDate: Installed on 2021-08-18 (127 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20FAS16K00
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.13.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_sxscpx ro quiet splash vt.handoff=1
SourcePackage: libxrandr
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET52W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS16K00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET52W(1.20):bd11/30/2016:br1.20:efr1.9:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS16K00
dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.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-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 app

[Touch-packages] [Bug 1955641] [NEW] network frequently becomes unreachable, I run "network-manager restart" and it works again

2021-12-23 Thread starky
Public bug reported:

After recent software update, network stops working frequently.
Fixes with "sudo service network-manager restart".

In syslog, I see messages like

ath10k_pci :02:00.0: firmware crashed!
...
NetworkManager state is now CONNECTED_SITE
...
whoopsie[1891]: [14:01:13] Cannot reach: https://daisy.ubuntu.com

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 23 14:23:41 2021
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-05-03 (964 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2021-01-24 (333 days ago)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
 [connection]
 wifi.powersave = 2
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-11-02T21:33:58.072345
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2021-01-30T10:51:20.495335
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  network frequently becomes unreachable, I run "network-manager
  restart" and it works again

Status in network-manager package in Ubuntu:
  New

Bug description:
  After recent software update, network stops working frequently.
  Fixes with "sudo service network-manager restart".

  In syslog, I see messages like

  ath10k_pci :02:00.0: firmware crashed!
  ...
  NetworkManager state is now CONNECTED_SITE
  ...
  whoopsie[1891]: [14:01:13] Cannot reach: https://daisy.ubuntu.com

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 23 14:23:41 2021
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-05-03 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2021-01-24 (333 days ago)
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2020-11-02T21:33:58.072345
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2021-01-30T10:51:20.495335
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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


[Touch-packages] [Bug 1955632] Re: Screen flickering or going black

2021-12-23 Thread sire Kenggi
(base) ashburry@ashburry-ThinkCentre-M92P:~$ inxi -G
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor 
  Graphics 
  driver: i915 v: kernel 
  Display: x11 server: X.Org 1.20.13 driver: i915 
  resolution: 1680x1050~60Hz 
  OpenGL: 
  renderer: Mesa DRI Intel HD Graphics 2500 (IVB GT1) 
  v: 4.2 Mesa 21.0.3

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

Title:
  Screen flickering or going black

Status in xorg package in Ubuntu:
  New

Bug description:
  I've been using Ubuntu 20.04 for a long time now and have had no problems. 
Then suddenly the screen started flickering. I tried PCLinuxOS but the screen 
just goes black. I found, on Ubuntu, installing brightness-controller and 
putting the screen brightness down below half way and the setting to Clear Blue 
Sky helps quite a lot but is hard to see. It still flickers once in awhile. And 
I cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
  Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
  Uname: Linux 5.14.0-1011-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 23 01:52:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
   rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics 
Controller [17aa:3083]
  InstallationDate: Installed on 2021-10-16 (68 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 3227K45
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem 
root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2018
  dmi.bios.release: 0.6
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9SKT9CAUS
  dmi.board.asset.tag: 640688
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: 3227K45
  dmi.product.sku: LENOVO_MT_3227
  dmi.product.version: ThinkCentre M92P
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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/1955632/+subscriptions


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


[Touch-packages] [Bug 1955632] [NEW] Screen flickering or going black

2021-12-23 Thread sire Kenggi
Public bug reported:

I've been using Ubuntu 20.04 for a long time now and have had no problems. Then 
suddenly the screen started flickering. I tried PCLinuxOS but the screen just 
goes black. I found, on Ubuntu, installing brightness-controller and putting 
the screen brightness down below half way and the setting to Clear Blue Sky 
helps quite a lot but is hard to see. It still flickers once in awhile. And I 
cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
Uname: Linux 5.14.0-1011-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 23 01:52:31 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
 rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[17aa:3083]
InstallationDate: Installed on 2021-10-16 (68 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 3227K45
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1011-oem 
root=UUID=e7536889-191e-4640-ba6f-6e940cb65228 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/11/2018
dmi.bios.release: 0.6
dmi.bios.vendor: LENOVO
dmi.bios.version: 9SKT9CAUS
dmi.board.asset.tag: 640688
dmi.board.name: MAHOBAY
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvr9SKT9CAUS:bd12/11/2018:br0.6:svnLENOVO:pn3227K45:pvrThinkCentreM92P:rvnLENOVO:rnMAHOBAY:rvr0B98401PRO:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_3227:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: 3227K45
dmi.product.sku: LENOVO_MT_3227
dmi.product.version: ThinkCentre M92P
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.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

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


** Tags: amd64 apport-bug focal 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/1955632

Title:
  Screen flickering or going black

Status in xorg package in Ubuntu:
  New

Bug description:
  I've been using Ubuntu 20.04 for a long time now and have had no problems. 
Then suddenly the screen started flickering. I tried PCLinuxOS but the screen 
just goes black. I found, on Ubuntu, installing brightness-controller and 
putting the screen brightness down below half way and the setting to Clear Blue 
Sky helps quite a lot but is hard to see. It still flickers once in awhile. And 
I cannot create a file in /sys/class/backlight to make the change permanent on 
boot. The only major change I can think of is setting LivePatch up that could 
have caused the flickering.
  Thank you, I hope you find the fix as no Linux distros will work on my 
ThinkCentre desktop PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1011.11-oem 5.14.17
  Uname: Linux 5.14.0-1011-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 23 01:52:31 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8821CU, 5.4.1, 5.11.0-43-generic, x86_64: installed
   rtl8821CU, 5.4.1, 5.14.0-1011-oem, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) 

[Touch-packages] [Bug 1955566] Re: iris driver doesn't load correctly on intel pci_id 0x4688

2021-12-23 Thread Dirk Su
** Tags added: originate-from-1954392 somerville

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

Title:
  iris driver doesn't load correctly on intel pci_id 0x4688

Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  New

Bug description:
  [Impact]

   * iris driver doesn't load with pci_id 4688. Instead, it uses llvm.
  we expect the Intel GPU uses iris driver.

  [Test Plan]

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Mesa/X.org
  OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits)
  ...
  OpenGL version string: 3.1 Mesa 21.0.3

   * After applying the fix, it shows:

   * $ DISPLAY=:0 glxinfo | grep -i opengl
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) Graphics (ADL-S GT1)
  ...
  OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 
(git-d4975a0dbc)

  [Where problems could occur]

   * This patch is backport the PCI ID mapping for enabling iris driver which 
is expected when users have a GPU.
   * If there is any issue occur then we need to fix it with iris driver.

  [Other Info]

   * It already in upstream and we have a platform which using ADL-HX in OEM 
project. Thus, we need to enable iris on it at least on focal.
   * The patch is simple as to add "CHIPSET(0x4688, adl_gt1, "ADL-S GT1", 
"Intel(R) Graphics")" in "include/pci_ids/iris_pci_ids.h".
   * Patch backported from df5b14969f9869f363bcc8b2a564c85aaa481597

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


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