[Touch-packages] [Bug 1952542] Re: systemd randomly crashes

2021-11-27 Thread Chris Guiver 
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 1952542

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.

ie. this bug report should have been filed with
`ubuntu-bug /var/crash/_usr_lib_systemd_systemd.0.crash`
as an uploaded file added as an attachment is less useful than the fields being 
populated from details from your machine which is done when apport tools are 
used.


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

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

Title:
  systemd randomly crashes

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  When screensaver is on, I often can't wake the system back up again.
  Screen comes, up, clock shows but frozen and login does nothing.

  I have a file `/var/crash/_usr_lib_systemd_systemd.0.crash` from
  around the incident time, so I guess it's systemd itself that's
  crashing.

  Trying to dig into the crash report, this is how far I get:

  ```
  $ gdb `cat ExecutablePath` CoreDump
  GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/lib/systemd/systemd...
  (No debugging symbols found in /usr/lib/systemd/systemd)
  [New LWP 2241488]
  [New LWP 1]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/sbin/init recovery dis_ucode_ldr'.
  Program terminated with signal SIGABRT, Aborted.
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  120   ../sysdeps/unix/syscall-template.S: No such file or directory.
  [Current thread is 1 (LWP 2241488)]
  (gdb) bt
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
  at ../csu/libc-start.c:409
  #14 0x561ece72c6f5 in ?? ()
  (gdb) 
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)

[Touch-packages] [Bug 1952542] Re: systemd randomly crashes

2021-11-27 Thread Leo Wandersleb 
Forgot to go through the checklist ...

$ lsb_release -rd
Description:Ubuntu 21.10
Release:21.10
$ apt-cache policy systemd
systemd:
  Installed: 248.3-1ubuntu8
  Candidate: 248.3-1ubuntu8
  Version table:
 *** 248.3-1ubuntu8 500
500 http://mirror.uchile.cl/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

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

Title:
  systemd randomly crashes

Status in systemd package in Ubuntu:
  New

Bug description:
  When screensaver is on, I often can't wake the system back up again.
  Screen comes, up, clock shows but frozen and login does nothing.

  I have a file `/var/crash/_usr_lib_systemd_systemd.0.crash` from
  around the incident time, so I guess it's systemd itself that's
  crashing.

  Trying to dig into the crash report, this is how far I get:

  ```
  $ gdb `cat ExecutablePath` CoreDump
  GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /usr/lib/systemd/systemd...
  (No debugging symbols found in /usr/lib/systemd/systemd)
  [New LWP 2241488]
  [New LWP 1]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/sbin/init recovery dis_ucode_ldr'.
  Program terminated with signal SIGABRT, Aborted.
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  120   ../sysdeps/unix/syscall-template.S: No such file or directory.
  [Current thread is 1 (LWP 2241488)]
  (gdb) bt
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
  at ../csu/libc-start.c:409
  #14 0x561ece72c6f5 in ?? ()
  (gdb) 
  #0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
  #1  0x561ece72cb5c in ?? ()
  #2  
  #3  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139637107291648) at pthread_kill.c:44
  #4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
  #5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
  #6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #7  0x7effcc9777b7 in __GI_abort () at abort.c:79
  #8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
  #9  0x561ece7758c4 in ?? ()
  #10 0x561ece77a7aa in ?? ()
  #11 0x561ece72b8a7 in ?? ()
  #12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
  #13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, 
argc=3, argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
  at ../csu/libc-start.c:409
  #14 0x561ece72c6f5 in ?? ()
  quit) 
  ```

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


-- 
Mailing list: https://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 1952542] [NEW] systemd randomly crashes

2021-11-27 Thread Leo Wandersleb 
Public bug reported:

When screensaver is on, I often can't wake the system back up again.
Screen comes, up, clock shows but frozen and login does nothing.

I have a file `/var/crash/_usr_lib_systemd_systemd.0.crash` from around
the incident time, so I guess it's systemd itself that's crashing.

Trying to dig into the crash report, this is how far I get:

```
$ gdb `cat ExecutablePath` CoreDump
GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/systemd/systemd...
(No debugging symbols found in /usr/lib/systemd/systemd)
[New LWP 2241488]
[New LWP 1]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/sbin/init recovery dis_ucode_ldr'.
Program terminated with signal SIGABRT, Aborted.
#0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
120 ../sysdeps/unix/syscall-template.S: No such file or directory.
[Current thread is 1 (LWP 2241488)]
(gdb) bt
#0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
#1  0x561ece72cb5c in ?? ()
#2  
#3  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139637107291648) 
at pthread_kill.c:44
#4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
#5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
#6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#7  0x7effcc9777b7 in __GI_abort () at abort.c:79
#8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
#9  0x561ece7758c4 in ?? ()
#10 0x561ece77a7aa in ?? ()
#11 0x561ece72b8a7 in ?? ()
#12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
#13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, argc=3, 
argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
at ../csu/libc-start.c:409
#14 0x561ece72c6f5 in ?? ()
(gdb) 
#0  0x7effcc99175b in kill () at ../sysdeps/unix/syscall-template.S:120
#1  0x561ece72cb5c in ?? ()
#2  
#3  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139637107291648) 
at pthread_kill.c:44
#4  __pthread_kill_internal (signo=6, threadid=139637107291648) at 
pthread_kill.c:80
#5  __GI___pthread_kill (threadid=139637107291648, signo=signo@entry=6) at 
pthread_kill.c:91
#6  0x7effcc991476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#7  0x7effcc9777b7 in __GI_abort () at abort.c:79
#8  0x7effccced6fe in ?? () from /lib/systemd/libsystemd-shared-248.so
#9  0x561ece7758c4 in ?? ()
#10 0x561ece77a7aa in ?? ()
#11 0x561ece72b8a7 in ?? ()
#12 0x7effcc978fd0 in __libc_start_call_main 
(main=main@entry=0x561ece729330, argc=argc@entry=3, 
argv=argv@entry=0x7ffc9cbad768) at ../sysdeps/nptl/libc_start_call_main.h:58
#13 0x7effcc97907d in __libc_start_main_impl (main=0x561ece729330, argc=3, 
argv=0x7ffc9cbad768, init=, fini=, 
rtld_fini=, stack_end=0x7ffc9cbad758)
at ../csu/libc-start.c:409
#14 0x561ece72c6f5 in ?? ()
quit) 
```

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

** Attachment added: "_usr_lib_systemd_systemd.0.crash"
   
https://bugs.launchpad.net/bugs/1952542/+attachment/5543850/+files/_usr_lib_systemd_systemd.0.crash

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

Title:
  systemd randomly crashes

Status in systemd package in Ubuntu:
  New

Bug description:
  When screensaver is on, I often can't wake the system back up again.
  Screen comes, up, clock shows but frozen and login does nothing.

  I have a file `/var/crash/_usr_lib_systemd_systemd.0.crash` from
  around the incident time, so I guess it's systemd itself that's
  crashing.

  Trying to dig into the crash report, this is how far I get:

  ```
  $ gdb `cat ExecutablePath` CoreDump
  GNU gdb (Ubuntu 11.1-0ubuntu2) 11.1
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is

[Touch-packages] [Bug 1952534] [NEW] [USB-Audio - Blue Microphones, recording] No sound at all

2021-11-27 Thread SuchBlue 
Public bug reported:

The microphone is recognised, but there is no sound coming out of it. Whenever 
I unplug and replug the microphone, it starts working as intended again. It is 
very impractical to have to do this each time I have to reboot.
I am using Ubuntu 20.04.3 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 27 21:49:48 2021
InstallationDate: Installed on 2021-11-27 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Microphones failed
Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 7 8 :  
 r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_Type: No sound at all
Title: [USB-Audio - Blue Microphones, recording] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.D0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MPG X570 GAMING PRO CARBON WIFI (MS-7B93)
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:bvnAmericanMegatrendsInternational,LLC.:bvr1.D0:bd07/05/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B93:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPROCARBONWIFI(MS-7B93):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B93
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

** Description changed:

- The microphone is recognised, but there is no sound coming out of it. 
+ The microphone is recognised, but there is no sound coming out of it. 
Whenever I unplug and replug the microphone, it starts working as intended 
again. It is very impractical to have to do this each time I have to reboot.
  I am using Ubuntu 20.04.3 LTS.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 21:49:48 2021
  InstallationDate: Installed on 2021-11-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Microphones 
failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 7 8 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_Type: No sound at all
  Title: [USB-Audio - Blue Microphones, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.D0
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING PRO CARBON WIFI (MS-7B93)
  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:bvnAmericanMegatrendsInternational,LLC.:bvr1.D0:bd07/05/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B93:pvr1.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPROCARBONWIFI(MS-7B93):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7B93
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

Title:
  [USB-Audio - Blue Microphones, recording] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The microphone is recogni

[Touch-packages] [Bug 1952533] [NEW] [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

2021-11-27 Thread John D Sheehan 
Public bug reported:

Sometimes if I run `pulseaudio -k` a few times, sound returns.
Sometimes if I run `sudo alsa force-reload`, sound returns.
Sometimes if I shutdown and start the laptop, sound returns.

This first occurred a few months ago when I was running 20.04, and I
upgraded to 21.10 in the hope it would fix the issue. It did not - sound
continues to be intermittent.

I use the Brave browser, not firefox.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  sheehan3636 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 27 20:21:47 2021
InstallationDate: Installed on 2021-10-15 (43 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_IE:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
 Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated successfully.
Symptom_Type: Sound works for a while, then breaks
Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/09/2021
dmi.bios.release: 1.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.0
dmi.board.name: 0F6P3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

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


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

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

Title:
  [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sometimes if I run `pulseaudio -k` a few times, sound returns.
  Sometimes if I run `sudo alsa force-reload`, sound returns.
  Sometimes if I shutdown and start the laptop, sound returns.

  This first occurred a few months ago when I was running 20.04, and I
  upgraded to 21.10 in the hope it would fix the issue. It did not -
  sound continues to be intermittent.

  I use the Brave browser, not firefox.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sheehan3636 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 27 20:21:47 2021
  InstallationDate: Installed on 2021-10-15 (43 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IE.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   Nov 27 19:00:54 xps systemd[1436]: pulseaudio.service: Deactivated 
successfully.
   Nov 27 19:01:05 xps systemd[1436]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2021
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/09/2021:br1.16:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-11-27T18:59:43.285943

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


-- 
Ma

[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault

2021-11-27 Thread Frank Heimes 
Many thx, Dmitry!

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Focal:
  In Progress
Status in qtwebkit-opensource-src source package in Hirsute:
  In Progress
Status in qtwebkit-opensource-src source package in Impish:
  In Progress
Status in qtwebkit-opensource-src source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the property offset as pointer size (hence 64 bit) value:

  2141: instructions[i + 6].u.pointer =
  reinterpre

[Touch-packages] [Bug 1950193] Re: libqt5svg5 affected by CVE-2021-38593

2021-11-27 Thread Dmitry Shachnev 
** Package changed: qtsvg-opensource-src (Ubuntu) => qtbase-opensource-
src (Ubuntu)

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: qtbase-opensource-src (Ubuntu)
 Assignee: (unassigned) => Dmitry Shachnev (mitya57)

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

Title:
  libqt5svg5 affected by CVE-2021-38593

Status in qtbase-opensource-src package in Ubuntu:
  In Progress

Bug description:
  libqt5svg5 5.12.8-0ubuntu1 in Ubuntu 20.04 is affected by CVE-2021-38593:
  https://nvd.nist.gov/vuln/detail/CVE-2021-38593

  Trying to open the attached svg file will block one core at 100% and occupy 
much memory. Depending on the configuration, it might even run out of memory 
and crash. This is fixed upstream by:
  https://codereview.qt-project.org/c/qt/qtbase/+/377942

  The original issue is public since July 29th. If I'm allowed to upload
  further files, I'll send a simple test program.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5svg5 5.12.8-0ubuntu1
  ProcVersionSignature: Ubuntu 5.14.0-1005.5-oem 5.14.9
  Uname: Linux 5.14.0-1005-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Mon Nov  8 20:24:34 2021
  InstallationDate: Installed on 2012-07-06 (3411 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtsvg-opensource-src
  UpgradeStatus: Upgraded to focal on 2020-10-03 (400 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1950193/+subscriptions


-- 
Mailing list: https://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 1941938] Re: systemd trying to unmount non-existent file system

2021-11-27 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd trying to unmount non-existent file system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This output is copied from here: 
https://github.com/systemd/systemd/issues/20516
  because I have not been able to capture the error messages. However what I am 
seeing is identical.

  sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy
   sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy
   sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy
   shutdown[1]: Failed to finalize  file systems, ignoring

  This has happened consistently since I upgraded to Ubuntu 20.04 two
  weeks ago, and is really annoying. Is there an actual problem or is it
  just noise that can be safely ignored?

  The only other thing referencing oldroot in its config was snap, which
  I have completely uninstalled to isolate the problem.

  /lib/systemd/systemd-shutdown also contains this string:
  # strings systemd-shutdown |grep old
  /oldroot
  sigprocmask(SIG_BLOCK, &mask, &oldmask) == 0
  sigprocmask(SIG_SETMASK, &oldmask, NULL) == 0

  I have never had an /oldroot mount and there isn't one now. I gather
  it is something the upgrade process might create, or it could perhaps
  be something broken in finalrd.

  Bin Li, who posted the above error to the systemd bug portal, got
  short shrift there and was told to contact the distro. So I am, as my
  version of systemd is 245, same as his. This problem is 100%
  repeateable and I see it every time I shutdown or restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
  Uname: Linux 5.4.0-81-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Aug 28 14:28:03 2021
  InstallationDate: Installed on 2017-05-26 (1554 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:0708 Acer, Inc Integrated Camera
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 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/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: LENOVO 20EVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic 
root=UUID=3be3-50c9-41cc-94b5-eab06cff1d17 ro quiet splash
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2021-08-05 (22 days ago)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R00ET49W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR00ET49W(1.24):bd12/01/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E560
  dmi.product.name: 20EVCTO1WW
  dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560
  dmi.product.version: ThinkPad E560
  dmi.sys.vendor: LENOVO

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


-- 
Mailing list: https://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 1951470] Re: webkit javascript segmentation fault

2021-11-27 Thread Dmitry Shachnev 
I have uploaded Focal, Impish and Hirsute debdiffs, they are now waiting
for approval in review queues.

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Focal:
  In Progress
Status in qtwebkit-opensource-src source package in Hirsute:
  In Progress
Status in qtwebkit-opensource-src source package in Impish:
  In Progress
Status in qtwebkit-opensource-src source package in Jammy:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the property offset as po

[Touch-packages] [Bug 1952496] Re: ubuntu 20.04 LTS network problem

2021-11-27 Thread Steven Abner 
** Package changed: ubuntu => avahi (Ubuntu)

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

Title:
  ubuntu 20.04 LTS network problem

Status in avahi package in Ubuntu:
  New

Bug description:
  Network afp only partially works. Two tries, Elementary OS 6, Ubuntu
  20.04 installs both have identical problem. Resolved by reinstalling
  Ubuntu 18.04 LTS. Using different kernels doesn't matter. Specific
  problem is with afp protocol name resolution. Searching local network
  for ip address using afp://ip_address did connect, but using GUI
  Files/Other Locations/Networks with named hosts will not. Always
  returns can't resolve hostname.local. Tried multiple edits of
  different network files, even installed netatalk in attempts. Again,
  solution is to go back to downgrade, works right out of the box, as
  did on another, and this before upgrade. This was only attempted with
  2 other computers, one mac, one ubuntu/elementary.

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


-- 
Mailing list: https://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 1952496] [NEW] ubuntu 20.04 LTS network problem

2021-11-27 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

Network afp only partially works. Two tries, Elementary OS 6, Ubuntu
20.04 installs both have identical problem. Resolved by reinstalling
Ubuntu 18.04 LTS. Using different kernels doesn't matter. Specific
problem is with afp protocol name resolution. Searching local network
for ip address using afp://ip_address did connect, but using GUI
Files/Other Locations/Networks with named hosts will not. Always returns
can't resolve hostname.local. Tried multiple edits of different network
files, even installed netatalk in attempts. Again, solution is to go
back to downgrade, works right out of the box, as did on another, and
this before upgrade. This was only attempted with 2 other computers, one
mac, one ubuntu/elementary.

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


** Tags: bot-comment
-- 
ubuntu 20.04 LTS network problem
https://bugs.launchpad.net/bugs/1952496
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to avahi 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