from:"fred"

[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

2024-07-17 Thread Fred Jupiter

Yes, 5.15.0-116-generic fixes my problem as well. Everything running
perfectly without "nomodeset".

I had reported my problem here; this bug is fixed for me:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068793

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738

Title:
  AMD GPUs fail with null pointer dereference when IOMMU enabled,
  leading to black screen

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

2024-06-26 Thread Fred Jupiter

Yes, I agree with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2068738/comments/32
.

I updated to -113 today on Kubuntu 22.04. There is no improvement on
-112.

The only things that is a workaround for me is "nomodeset" in GRUB or
using the -107 kernel.

Updating to -113 kernel leaves black screen, backlit, on restart.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738

Title:
  AMD GPUs fail with null pointer dereference when IOMMU enabled,
  leading to black screen

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063150] Re: No sound, stutters and clicks after upgrade to 24.04

2024-06-11 Thread Fred Vkigg

Problem that no sound device is available on my Dell Precission 5520 was
solved by a recent system update. No blacklisting of 'snd_soc_avs' was
required.

Could be that the later kernel avoids the problem or that the update
changes some kernel/system settings. The kernel after the upgrade is
6.8.0-35-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound, stutters and clicks after upgrade to 24.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068793] Re: Black screen on restart after update: fix "nomodeset"

2024-06-10 Thread Fred Jupiter

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

Yes, the broken kernel probably actually is Kernel 5.15.0-112-generic.

I help people over the phone, or very quickly, and then I don't have
access to the machines any more.

I was able to have a quick look just now: Kernel 5.15.0-112-generic is
the most current. I assume this kernel is causing the trouble.

Sorry about the wrong information.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068793

Title:
  Black screen on restart after update: fix "nomodeset"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068738] Re: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs

2024-06-10 Thread Fred Jupiter

I had this problem, too, with a PC (I'm sorry, I can't access the PC; this is 
from my written/saved records):
CPU: AMD Ryzen 3 2200G, 4x 3.50GHz, boxed (YD2200C5FBBOX)
Graphics: AMD Vega 8
Kubuntu 22.04, fully updated today

Expected:
PC starts

Actual:
PC monitor stays black after logo of mainboard manufacturer.

Attempts at fixing this:
Because I had problems with startup where the addition of "nomodeset" in GRUB 
helped, I tried this. This time it did not help. The computer actually started 
- more than before - but got stuck at various stages of the boot process.

The PC would not fully start with kernel 5.15.0-112-generic.

I chose 5.15.0-107-generic in GRUB. 107 worked without a hitch.

At the moment the workaround is simply using 5.15.0-107-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738

Title:
  Kernel update 5.15.0-112 might cause severe problems with specific AMD
  GPUs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068735] Re: I updated my linux mint system today and after rebbot I received black screen

2024-06-08 Thread Fred Jupiter

oh yes, the key to press for the GRUB menu after booting with a modern
(U)EFI bios is: ESC, not Shift (as mentioned in the link above).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068735

Title:
  I updated my linux mint system today and after rebbot I received black
  screen

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068793] Re: Black screen on restart after update: fix "nomodeset"

2024-06-08 Thread Fred Jupiter

oh yes, the key to press for the GRUB menu after booting with a modern
(U)EFI bios is: ESC, not Shift (as mentioned in the link above).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068793

Title:
  Black screen on restart after update: fix "nomodeset"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068738] Re: Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs

2024-06-08 Thread Fred Jupiter

Try this ("Temporary" first to gain access to the computer again), if
you want to use the new kernel:

It worked for me.

Workaround:
Temporary:
Add "nomodeset" before "quiet splash" via editing of GRUB menu.

See: https://askubuntu.com/questions/162075/my-computer-boots-to-a-
black-screen-what-options-do-i-have-to-fix-it

Permanent:
Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Add the word 
"nomodeset" before "quiet splash".
- Run "sudo update-grub"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738

Title:
  Kernel update 5.15.0-112 might cause severe problems with specific AMD
  GPUs

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068735] Re: I updated my linux mint system today and after rebbot I received black screen

2024-06-08 Thread Fred Jupiter

Try this ("Temporary" first to gain access to the computer again).

Workaround:
Temporary:
Add "nomodeset" before "quiet splash" via editing of GRUB menu.

See: https://askubuntu.com/questions/162075/my-computer-boots-to-a-
black-screen-what-options-do-i-have-to-fix-it

Permanent:
Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Add the word 
"nomodeset" before "quiet splash".
- Run "sudo update-grub"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068735

Title:
  I updated my linux mint system today and after rebbot I received black
  screen

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2068793] [NEW] Black screen on restart after update: fix "nomodeset"

2024-06-08 Thread Fred Jupiter

Public bug reported:

Kubuntu 22.04
Updated to Kernel 5.15.0-107-generic on 6 June 2024 (I think)
Notebook HP 17-ca1010ng
AMD Ryzen 5 3500U
AMD Radeon Vega 8 (IGP)

Expected:
After updating via Muon (incl. the kernel, see above, I think), the computer 
should restart normally.

Actual:
After the HP logo, the computer displays a black screen, backlit. Nothing 
happens, completely unresponsive.

Workaround:
Temporary:
Add "nomodeset" before "quiet splash" via editing of GRUB menu.

See: https://askubuntu.com/questions/162075/my-computer-boots-to-a-
black-screen-what-options-do-i-have-to-fix-it

Permanent:
Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Add the word 
"nomodeset" before "quiet splash".
- Run "sudo update-grub"

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068793

Title:
  Black screen on restart after update: fix "nomodeset"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2030759] Re: Crashes when passing ssl=True

2024-05-12 Thread Fred

** Attachment added: "example.py"
   
https://bugs.launchpad.net/ubuntu/+source/python-gbulb/+bug/2030759/+attachment/511/+files/example.py

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2030759

Title:
  Crashes when passing ssl=True

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2030759] Re: Crashes when passing ssl=True

2024-05-12 Thread Fred

Run the example.py from the terminal, click on the "Connect!" button in
the UI, then close the application and see the output in the terminal.

TypeError: GLibBaseEventLoop._make_ssl_transport() got an unexpected
keyword argument 'ssl_shutdown_timeout'

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2030759

Title:
  Crashes when passing ssl=True

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with "quiet splash" (Grub)

2024-05-04 Thread Fred Jupiter

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

** This bug has been marked a duplicate of bug 2064815
   Always black screen on first reboot after fresh install 24.04, Intel and AMD 
GPU

** This bug is no longer a duplicate of bug 2064815
   Always black screen on first reboot after fresh install 24.04, Intel and AMD 
GPU

** This bug has been marked a duplicate of bug 2064815
   Always black screen on first reboot after fresh install 24.04, Intel and AMD 
GPU

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with
  "quiet splash" (Grub)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2064815] [NEW] Always black screen on first reboot after fresh install 24.04, Intel and AMD GPU

2024-05-04 Thread Fred Jupiter

Public bug reported:

Always completely unresponsive black screen on first reboot after fresh
install 24.04 Kubuntu, both Intel and AMD GPU. Actually, the computer
should show the manufacturer logo, and then start the desktop (in this
case KDE Plasma).

I followed this advice:
https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button

It seems that "quiet splash" is the actual problem, not a possible
solution with adding "nomodeset".

I edited the GRUB entry as follows (with results added):

1) With only "quiet splash" (no "nomodeset"), default installation,
fresh install of Kubuntu 24.04: only black screen, nothing happens. Only
hard reset will do anything.

2) Add "nomodeset" to "quiet splash": everything works perfectly. Also
works permanently with editing of /etc/default/grub.

3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete
"nomodeset", if previously added): everything works perfectly (see
Reddit link above).

4) Delete "nomodeset", after having added it to /etc/default/grub and
updated grub previously, but leave the 'original' "quiet splash":
computer hangs, completely unresponsive, after showing the following
code:

Booting a command list
Loading Linux 6.8.0-31-generic ...
Loading initial ramdisk ...

5) Again, boot without both "quiet splash" or "nomodeset": everything works 
perfectly. Also works permanently with /etc/default/grub.
It went quite fast, but after "Loading initial ramdisk ..." I think the next 
code line was "secure boot is enabled". It might be a problem with "secure 
boot" and "quiet splash". Secure boot is enabled in both my installations, so I 
can't try the other option ("secure boot" disabled in the EFI BIOS before 
installation).

Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the 
words "quiet splash" (leave the quotation marks '').
- Run sudo update-grub

Systems used (two different notebooks):
1) Kubuntu 24.04, VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Barcelo (rev c2) (prog-if 00 [VGA controller]) DeviceName: AMD Radeon 
Integrated Graphics Subsystem: Hewlett-Packard Company Barcelo-.
2) Kubuntu 24.04, VGA compatible controller: Intel Corporation Raptor Lake-P 
[Iris Xe Graphics] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Lenovo 
Raptor Lake-P [Iris Xe Graphics].

See log file from notebook No., 2 Iris Xe Graphics, attached. This is
what I did:

- "quiet splash" deleted by me from /etc/default/grub = everything fine.
- Added "quiet splash" to /etc/default/grub again = black screen.
- Hard reset, and then deleted "quiet splash" from GRUB after ESC, editing with 
"e" and CTRL + x = computer starts.
- entered sudo journalctl -k -b -1 > /tmp/kernel.log in a terminal. The output 
is attached.

If you need 1) cat /proc/version_signature > version.log and/or 2) sudo
lspci -vnvn > lspci-vnvn.log please say so. I can't get at the computers
at the moment. But if it will help, all get both logs mentioned for both
computers and upload them.

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

** Attachment added: "2024-05-02_kernel.log"
   
https://bugs.launchpad.net/bugs/2064815/+attachment/5774882/+files/2024-05-02_kernel.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064815

Title:
  Always black screen on first reboot after fresh install 24.04, Intel
  and AMD GPU

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2061498] Re: Localization Dutch language not working at all

2024-05-04 Thread Fred

Same problem with Dutch language.
$ locale
LANG=C.UTF-8
LANGUAGE=nl:en
LC_CTYPE="C.UTF-8"
LC_NUMERIC=C.UTF-8
LC_TIME=C.UTF-8
LC_COLLATE="C.UTF-8"
LC_MONETARY=C.UTF-8
LC_MESSAGES="C.UTF-8"
LC_PAPER=C.UTF-8
LC_NAME=C.UTF-8
LC_ADDRESS=C.UTF-8
LC_TELEPHONE=C.UTF-8
LC_MEASUREMENT=C.UTF-8
LC_IDENTIFICATION=C.UTF-8
LC_ALL=

Tried:
$ sudo dpkg-reconfigure locales

ii  language-pack-gnome-nl  1:24.04+20240419   all GNOME translation updates 
for language Dutch; Flemish
ii  language-pack-gnome-nl-base  1:24.04+20240419  all  GNOME translations for 
language Dutch; Flemish
ii  language-pack-nl 1:24.04+20240419  alltranslation updates 
for language Dutch; Flemish
ii  language-pack-nl-base1:24.04+20240419all  translations for 
language Dutch; Flemish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061498

Title:
  Localization Dutch language not working at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-provision/+bug/2061498/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with "quiet splash" (Grub)

2024-05-04 Thread Fred Jupiter

** Summary changed:

- Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU without 
nomodeset
+ Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with "quiet 
splash" (Grub)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU with
  "quiet splash" (Grub)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU without nomodeset

2024-05-03 Thread Fred Jupiter

Okay, but I changed the heading of this bug report: Identical behaviour
with "Intel Iris Xe GPU". Just to  mention this. See also:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983/comments/13

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU
  without nomodeset

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

2024-05-03 Thread Fred Jupiter

I've just read https://bugs.launchpad.net/systemd/+bug/2063143

Just two observations:
- In my two cases (AMD and Intel GPU notebooks) the black screen was 100%, not 
a fraction of boot processes. With "quiet splash" "on" I was never able to 
boot. The behaviour was also absolutely identical with AMD and Intel GPU.
- I was never using Wayland (Kubuntu "out of the box": Plasma (X11)).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

2024-05-02 Thread Fred Jupiter

If you tell me how to "gather the full kernel log from when the system
booted to black screen", I might try that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU without nomodeset

2024-05-02 Thread Fred Jupiter

Deleting "quiet splash" is the better workaround, rather than
"nomodeset". I can confirm that without either "quiet splash" AND
"nomodeset" in GRUB all energy saving works in the HP notebook with AMD
Radeon Integrated Graphics (see above).

The following is copied from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063983 :

I followed this advice:
https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button

It seems that "quiet splash" is the actual problem, not "nomodeset"
(solution).

I edited the GRUB entry as follows (with results added):

1) With only "quiet splash" (no "nomodeset"), default installation,
fresh install of Kubuntu 24.04: only black screen, nothing happens.

2) Add "nomodeset" to "quiet splash": everything works perfectly. Also
works permanently with editing of /etc/default/grub.

3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete
"nomodeset", if previously added): everything works perfectly (see
Reddit link above).

4) Delete "nomodeset", after having added it to /etc/default/grub and
updated grub previously, but leave the 'original' "quiet splash":
computer hangs, completely unresponsive, after showing the following
code:

Booting a command list
Loading Linux 6.8.0-31-generic ...
Loading initial ramdisk ...

5) Again, boot without both "quiet splash" or "nomodeset": everything works
perfectly. Also works permanently with /etc/default/grub.
It went quite fast, but after "Loading initial ramdisk ..." I think the next
code line was "secure boot is enabled". It might be a problem with "secure
boot" and "quiet splash". Secure boot is enabled in both my installations, so I
can't try the other option ("secure boot" disabled in the EFI BIOS before
installation).

Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the
words "quiet splash" (leave the quotation marks '').
- Run sudo update-grub

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU
without nomodeset

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

2024-05-02 Thread Fred Jupiter

I followed this advice (mentioned above):
https://www.reddit.com/r/Kubuntu/comments/1cdko49/comment/l1uf573/?utm_source=share_medium=web3x_name=web3xcss_term=1_content=share_button

It seems that "quiet splash" is the actual problem, not "nomodeset"
(solution).

I edited the GRUB entry as follows (with results added):

1) With only "quiet splash" (no "nomodeset"), default installation,
fresh install of Kubuntu 24.04: only black screen, nothing happens.

2) Add "nomodeset" to "quiet splash": everything works perfectly. Also
works permanently with editing of /etc/default/grub.

3) Delete "quiet splash" in GRUB and do not add "nomodeset" (or delete
"nomodeset", if previously added): everything works perfectly (see
Reddit link above).

Booting a command list
Loading Linux 6.8.0-31-generic ...
Loading initial ramdisk ...

5) Again, boot without both "quiet splash" or "nomodeset": everything works
perfectly. Also works permanently with /etc/default/grub.
It went quite fast, but after "Loading initial ramdisk ..." I think the next
code line was "enabling secure boot". It might be a problem with "secure boot"
and "quiet splash". Secure boot is enabled in both my installations, so I can't
try the other option ("secure boot" disabled in the EFI BIOS before
installation).

Workaround (for me):
- Edit /etc/default/grub: the line "GRUB_CMDLINE_LINUX_DEFAULT=". Delete the
words "quiet splash" (leave the quotation marks '').
- Run sudo update-grub

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983

Title:
24.04 Upgrade/Fresh Install results in black screen on reboot on
AMDGPU system

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

2024-05-02 Thread Fred Jupiter

... oh yes, I had the same problem with AMD Radeon Integrated Graphics; see the 
same bug report:
https://bugs.launchpad.net/ubuntu/+bug/2063877

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063983] Re: 24.04 Upgrade/Fresh Install results in black screen on reboot on AMDGPU system

2024-05-02 Thread Fred Jupiter

I think this bug also affects Intel GPUs. I did an installation today that 
resulted in a black screen without "nomodeset". See:
https://bugs.launchpad.net/ubuntu/+bug/2063877

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063983

Title:
  24.04 Upgrade/Fresh Install results in black screen on reboot on
  AMDGPU system

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo GPU without nomodeset

2024-05-02 Thread Fred Jupiter

I can confirm that this bug also affects the notebook Lenovo V17 G4 IRU
83A20009GE (also called: Lenovo V17 Gen 4 i) with Intel Iris Xe
Graphics.


I've just installed Kubuntu 24.04 LTS on it ("secure boot" enabled in EFI Bios; 
otherwise simply by attaching installation USB stick). The installation worked 
smoothly and perfectly.

First reboot brought a black screen. Nothing at all happened after the
Lenovo logo. I tried this with a hard reset a couple of times. Then I
executed the following workaround.

- It's an UEFI installation, so pressed ESC key once after hard reset (after 
Lenovo logo).
- Edited GRUB via pressing "e".
- added "nomodeset" to line beginning "Linux ..."
- started OS with CTRL + x
- It worked, perfectly.

OS does NOT work without nomodeset.

Unlike the HP notebook (see above), the energy saving options seem to
work. So this bug seems not to be so serious for the Lenovo notebook. I
could return from manually induced "Standby" mode by simply pressing any
key.

Editing /etc/default/grub by adding "nomodeset" to
"GRUB_CMDLINE_LINUX_DEFAULT:" line works permanently as well.

lspci -v | less: 00:02.0 VGA compatible controller: Intel Corporation
Raptor Lake-P [Iris Xe Graphics] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Lenovo Raptor Lake-P [Iris Xe Graphics] Flags: bus master,
fast devsel, latency 0, IRQ 255, IOMMU group 0 Memory at 60
(64-bit, non-prefetchable) [size=16M] Memory at 40 (64-bit,
prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at
000c [virtual] [disabled] [size=128K] Capabilities: 
Kernel modules: i915, xe

sudo dmidecode -s bios-version: MCCN24WW

** Summary changed:

- Only black screen on boot with AMD Barcelo GPU without nomodeset
+ Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU without 
nomodeset

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo and Intel Iris Xe GPU
  without nomodeset

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] Re: Only black screen on boot with AMD Barcelo GPU without nomodeset

2024-04-26 Thread Fred Jupiter

I just closed the lid of the notebook, probably entering "suspend" mode.
Yes, the screen was black, frozen, no mouse no keyboard. Only a hard
reset helped. The notebook started - with the help of nomodeset - like
before.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo GPU without nomodeset

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063877] [NEW] Only black screen on boot with AMD Barcelo GPU without nomodeset

2024-04-26 Thread Fred Jupiter

Public bug reported:

I have a HP 17-cp1147ng notebook from the end of 2022.

The notebook worked "out of the box" with the Kubuntu 22.04 LTS. No
black screen there.

I've just installed Kubuntu 24.04 LTS on it.

I get a black screen after the HP logo on starting up (first time). Only
a hard reset would let me do anything with the computer again, no mouse,
now keyboard, no picture.

I followed this advice (section "Black/purple screen after you boot
Ubuntu for the first time"): My computer boots to a black screen, what
options do I have to fix it?

https://askubuntu.com/questions/162075/my-computer-boots-to-a-black-
screen-what-options-do-i-have-to-fix-it

It worked (once). So I followed the advice specified there, and went to:
"How do I set 'nomodeset' after I've already installed Ubuntu?"

https://askubuntu.com/questions/38780/how-do-i-set-nomodeset-after-ive-
already-installed-ubuntu

Nomodeset works permanently for booting. But after a short "test drive"
I think all energy-saving states equally result in a black screen
requiring a hard reset (I would have to check that by trying all kind of
states [screensaver, sleep-mode etc.)

I installed only Kubuntu on the entire hard disc, with no bells and
whistles.

amdgpu is installed, I checked that: xserver-xorg-video-amdgpu
23.0.0-1build1

Additional hardware information:

lspci -v | less: VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Barcelo (rev c2) (prog-if 00 [VGA controller]) DeviceName: AMD
Radeon Integrated Graphics Subsystem: Hewlett-Packard Company Barcelo
Flags: bus master, fast devsel, latency 0, IRQ 255, IOMMU group 11
Memory at fce000 (64-bit, prefetchable) [size=256M] Memory at
fcf000 (64-bit, prefetchable) [size=2M] I/O ports at 1000 [disabled]
[size=256] Memory at d040 (32-bit, non-prefetchable) [size=512K]
Capabilities: Kernel modules: amdgpu

sudo dmidecode -s bios-version: F.03

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063877

Title:
  Only black screen on boot with AMD Barcelo GPU without nomodeset

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063150] Re: No sound after upgrade to 24.04

2024-04-26 Thread Fred Vkigg

Strangely changing the installed system to use the 'nouveau' Nvidia
driver does NOT fix the problem.

If it help I can try a fresh 24.04 install without initially installing
the propitiatory Nvidia driver.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound after upgrade to 24.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063150] Re: No sound after upgrade to 24.04

2024-04-26 Thread Fred Vkigg

Bug occurs with released 24.04 where the kernel is 6.8.0-31-generic

Strangely the live version of 24.04 booted on same machine form the
released desktop ISO image does NOT have the problem with the same
kernel version.

The Precision 5520 had hybrid graphics with both integrated Intel (HD
P630) and discrete Nvidia (GM197GLM) processors.

The live system is using the 'nouveau' driver for the Nvidia graphics. I
suspect the problem is being indirectly caused by the Nvidia drivers
HDMI HD Audio support combined with the Intel AVS audio driver

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound after upgrade to 24.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063150] Re: No sound after upgrade to 24.04

2024-04-25 Thread Fred Vkigg

alsa-info from a Dell Precision 5520

** Attachment added: "alsa-info.txt.1IMNEYShPL"
   
https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2063150/+attachment/5770168/+files/alsa-info.txt.1IMNEYShPL

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound after upgrade to 24.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2063150] Re: No sound after upgrade to 24.04

2024-04-25 Thread Fred Vkigg

Problem lies in the Intel kernel driver 'snd_soc_avs' which is becoming
active but fail to support the HDA sound hardware correctly.

Workaround is to blacklist 'snd_soc_avs'.

Problem is well know and seems to be already in Kernel 6.7. See for
example https://bbs.archlinux.org/viewtopic.php?id=294655

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063150

Title:
  No sound after upgrade to 24.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1847088] Re: Cups appends extra page with %EndDocument %%EOF to every print

2024-03-31 Thread Fred Richardson

I'm having this same problem with a different distro - it's the
raspberrypi "bookworm" distro.  Everything works fine except that I get
these extra pages with "%%EndDocument" carriage return, a bunch of
whitespace and then "%%EOF".  I take it this is a cups issue?  Or maybe
it is a specific problem with my Xerox Phaser driver?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847088

Title:
  Cups appends extra page with %EndDocument %%EOF to every print

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059830] [NEW] Port software-properties-gtk to GTK 4

2024-03-30 Thread Fred

Public bug reported:

It still uses old GTK 3. Please upgrade it to GTK 4!

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059830

Title:
  Port software-properties-gtk to GTK 4

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

2024-03-29 Thread Fred

To get my network connectivity restored I had to run:

sudo dhcpcd

The repository have been fixed so I was able to install network-manager
back again:

sudo apt install network-manager

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059651

Title:
  network-manager gets uninstalled on apt full-upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057773] Re: After the latest kernel update if you toggle wifi on and off the system crashes

2024-03-28 Thread Fred

** Summary changed:

- After the latest Kernal update if you toggle wifi on and off the system 
crashes
+ After the latest kernel update if you toggle wifi on and off the system 
crashes

** Description changed:

- I got a kernal update today and updated it.
+ I got a kernel update today and updated it.
  So after i updated it and toggled wifi on and off the system soft locked it 
is nonfunctional but the mouse still works.
  It even can't do a sudo reboot or reboot at all.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 6.5.0-25.25-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 13 15:23:23 2024
  InstallationDate: Installed on 2024-01-22 (51 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  IpRoute:
-  default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600 
-  169.254.0.0/16 dev wlp2s0 scope link metric 1000 
-  192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600
+  default via 192.168.0.1 dev wlp2s0 proto dhcp src 192.168.2.37 metric 600
+  169.254.0.0/16 dev wlp2s0 scope link metric 1000
+  192.168.0.0/22 dev wlp2s0 proto kernel scope link src 192.168.2.37 metric 600
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
-  running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057773

Title:
  After the latest kernel update if you toggle wifi on and off the
  system crashes

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1858777] Re: Processing triggers for man-db lasting extremely long

2024-03-12 Thread Fred

I had a similar issue where the system load would be very high when
installing packages. The issue disappeared after uninstall the gnome-
menus package.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858777

Title:
  Processing triggers for man-db lasting extremely long

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2057706] [NEW] High CPU load when installing packages

2024-03-12 Thread Fred

Public bug reported:

I had high CPU load on my system and the system would freeze for 15
seconds when installing or reinstalling packages with apt.

The issue disappeared after uninstalling the gnome-menus package.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-menus 3.36.0-1.1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Mar 12 22:11:34 2024
Dependencies:
 
InstallationDate: Installed on 2013-12-26 (3729 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: gnome-menus
UpgradeStatus: Upgraded to noble on 2024-03-12 (0 days ago)

** Affects: gnome-menus (Ubuntu)
 Importance: Undecided
 Status: New


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2057706

Title:
  High CPU load when installing packages

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2038925] Re: Many hangs during apt full-upgrade

2024-03-12 Thread Fred

Do these freezes occur when updating, installing and reinstalling
packages too?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038925

Title:
  Many hangs during apt full-upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-03-12 Thread Fred

A workaround is to set the environment variable MOZ_ASSUME_USER_NS=0.

You can run it as:
env MOZ_ASSUME_USER_NS=0 /home/bob/Downloads/firefox/firefox 
--name=firefox-nightly %u

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2046844

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1956404] [NEW] package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-04 Thread Fred Mitchell

Public bug reported:

na

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.24
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
Date: Tue Jan  4 19:46:50 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
Lspci:
 
Lspci-vt: -[:00]-
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:
 
Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
PackageArchitecture: all
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-43-generic 
root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2021
dmi.bios.release: 4.1
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v4.1
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v4.1
dmi.chassis.asset.tag: 1609-2687-7949-1311-7755-6991-40
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v4.1
dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.1:bd05/05/2021:br4.1:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.1:skuNone:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.1:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.1:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.sku: None
dmi.product.version: Hyper-V UEFI Release v4.1
dmi.sys.vendor: Microsoft Corporation

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956404

Title:
  package linux-firmware 1.187.24 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-11-17 Thread Fred

Thank you Christian,
I think I managed to repair my system.
Here is how I did, if it can help others.
By the way, Jonas, it is impossible to remove broken files/folders, so the 
strategy I suggest is to destroy the dataset and restore it from a backup, 
while running from a bootable media.
One can backup everything in the dataset except the corrupted files, and 
finally try to restore these by other means: reinstalling package, or using 
eventual backups for personnal files.

I scanned every dataset with find and fstat, as suggested in this thread, until 
fstat got stalled, for example with /var (I did it for /, /var, /opt and /home, 
which all had their own datasets):
```
sudo find /var -mount -exec echo '{}' \; -exec stat {} \;
```
At the same time I monitored kernel errors:
```
tail -f /var/log/kern.log
```
When it freezes on a file, its name is printed by the echo command (this is the 
last thing printed out), and a stack trace appears in the log.

I was lucky, only one file got corrupted: `/var/lib/app-
info/icons/ubuntu-impish-universe/48x48/plasma-workspace_preferences-
desktop-color.png`.

Each time a corrupted file is found, it is necessary to restart the scan from 
the beginning, while excluding it, example:
```
sudo find /var -mount -not -path 
'/var/lib/app-info/icons/ubuntu-impish-universe/*' -exec echo '{}' \; -exec 
stat {} \;
```


Apparently, my corrupted file did not belong to any package (I checked with 
`apt-file search `), and in the end, I figured out it was recreated 
automatically, I don´t know how...
Otherwise, I would have reinstalled the package after restoring the rest.

I backed up the whole /var with tar:
```
sudo tar --exclude=/var/lib/app-info/icons/ubuntu-impish-universe/48x48 --acls 
--xattrs --numeric-owner --one-file-system -zcpvf backup_var.tar.gz /var
```
At first I did not put --numeric-owner, but the owners where all messed up, and 
it prevented it from going to graphical mode (GDM was complaining not the have 
write access to some /var/lib/gdm3/.config/)
It is probably because by default, owner/group are saved as text, and are 
assigned different uid/gid on the bootable media.

The backup process shall not get stalled, otherwise there might be other
corrupted files, not seen by fstat, I don't know if it is possible.

In order to be extra sure about non-corruption of my root dir (/), I
also created a backup of it, looking for a possible freeze, but it did
not occur.

I created a bootable USB media with Ubuntu 21.04, and booted it.
I accessed my ZFS pool:
```
sudo mkdir /mnt/install
sudo zpool import -f -R /mnt/install rpool
zfs list
```
I destroyed and recreated the dataset for /var (with options from my 
installation notes):
```
sudo zfs destroy -r rpool/root/var
sudo zfs create -o quota=16G -o mountpoint=/var rpool/root/var
```
It is necessary to reopen the pool, otherwise, a simple mount does not allow 
populating the new dataset (for me, /var was created in the root dataset):
```
sudo zpool export -a
sudo zpool import -R /mnt/install rpool
sudo zfs mount -l -a
zfs list
```

Now we can restore the backup:
```
sudo tar --acls --xattrs -zxpvf /home/user/backup_var.tar.gz -C /mnt/install
```
Check if the new dataset has the correct size and content:
```
zfs list
ll /mnt/install/var
```
Close and reboot:
```
sudo zfs umount -a
sudo reboot
```

Of course, it can get more complex if the corrupted files are more sensitive 
system files.
It might be necessary to chroot in order to reinstall the packages where 
corrupted files come from.

Hope it helps...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906476

Title:
  PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
  sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
  >z_sa_hdl)) failed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1906476] Re: PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 == sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED, >z_sa_hdl)) failed

2021-11-15 Thread Fred

As many people here, I upgraded my encrypted ZFS Ubuntu system to 21.10,
unaware of the issues with ZFS,

I only used 5.13.0-19 for a day, and began to notice odd things, like:
incapacity to suspend to RAM, freezes, some process were impossible to kill.
I updated my kernel to 5.13.0-20 and then 5.13.0-21, but I still have issues
with my ZFS encrypted filesystem. It seems the kernel update does not fix
everything.

Even now it is unable to suspend (it says some process refuse to suspend),
which is really annoying for a laptop. Moreoever, automatically scheduled
"updatedb" and "apt update" get stuck.
Even system shutdown often takes a long time, to the point I have to force it
with power button. Many times it seems to get stuck waiting for AppArmor.
In addition I keep getting errors with stack traces in dmesg, I put an example
in attachment.

Now I am wondering what I should do to repair it ? I considered trying
to downgrade my kernel to 5.11.0-37 which was my version before
upgrading to 21.10, but it was automatically removed, and it does not
seem very easy to put it back. I am wondering if it is worth the hassle.

Besides, the ZFS version was also upgraded in the process, and it is not clear
to me whether I could keep the new version with the old kernel, or not. It
seems to have evolved from 0.8.4-1ubuntu11.3 to 2.0.2-1ubuntu5.1, and then
2.0.2-1ubuntu5.2, and 2.0.6-1ubuntu2 (though oddly I cannot find any trace of
this last version being installed in apt logs).
I am wondering if rolling back to 0.8.4 can do any good ?

My whole system is based on ZFS, if I have to reinstall it all, it will take me
days to put everything back. Is there a real corruption on the filesystem,
which would be interpreted as such by an older ZFS version, or is it just new
2.0.x versions that are disturbed by it ?
Would there be a way to fix the corruption ? Deleting some files or changing
meta-data ?

Any help would be greatly appreciated !
Thank you.

** Attachment added: "zfs_panic_trace_2025.log"

https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1906476/+attachment/5540947/+files/zfs_panic_trace_2025.log

--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906476

Title:
PANIC at zfs_znode.c:335:zfs_znode_sa_init() // VERIFY(0 ==
sa_handle_get_from_db(zfsvfs->z_os, db, zp, SA_HDL_SHARED,
>z_sa_hdl)) failed

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

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1948438] [NEW] Printer kan niet worden gestart. Controleer de configuratie van uw printer

2021-10-22 Thread Fred K.

Public bug reported:

My Canon MP499 printer is recognized, but if i try to use it in
LibreOffice Writer, a message appears (see above). Using translate, it
shows this message:

Printer cannot be started. Check your printer's configuration


fred@fred-Latitude-E6430:~$ lpstat 
fred@fred-Latitude-E6430:~$ lpstat -t
scheduler is running
no system default destination
device for DCP-L3550CDW: 
dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4dc9c43
device for MP495-series: usb://Canon/MP495%20series?serial=24F65A=1
DCP-L3550CDW accepting requests since vr 23 jul 2021 12:55:49 CEST
MP495-series accepting requests since vr 22 okt 2021 10:58:01 CEST
printer DCP-L3550CDW is idle.  enabled since vr 23 jul 2021 12:55:49 CEST
printer MP495-series is idle.  enabled since vr 22 okt 2021 10:58:01 CEST
fred@fred-Latitude-E6430:~$ sudo service cups status 
[sudo] wachtwoord voor fred: 
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice

[Bug 1943251] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 - I do have Secur

2021-09-10 Thread Fred Reimer

Apparently I was out of space on my /boot partition.  Maybe a more
descriptive error message?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943251

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1 - I do have SecureBoot enabled

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1943251] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 - I do have Sec

2021-09-10 Thread Fred Reimer

Public bug reported:

I have Secure Boot enabled.  The MOK key is already configured in the
EFI.  Have VMware Workstation installed and signed the modules so that
would work.  Not sure what initramfs is trying to do.  I didn't kick
anything off, this ran by itself in the background and just popped up
with a warning.  So I don't know if it is involved with Secure Boot, or
if initramfs needs to sign a new image when it creates one, but the MOK
key is there in the right place so it should be able to do so if it
needs to.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Sep 10 07:43:46 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-09-05 (5 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943251

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1 - I do have SecureBoot enabled

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1941948] [NEW] Installation process crashed with grub fatal error

2021-08-28 Thread Fred Rocha

Public bug reported:

I think this is related to the EFI partition. I created my partitions
manually.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.461
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 28 12:59:32 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
RebootRequiredPkgs:
 linux-image-5.11.0-31-generic
 linux-base
 linux-image-5.11.0-16-generic
 linux-base
 linux-base
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute ubiquity-21.04.19 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1941948

Title:
  Installation process crashed with grub fatal error

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other

2021-07-16 Thread Fred

I had this issue too, it got solved by rebooting and running Software
Update (update-manager).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934936

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

1 2 3 4 5 6 7 8 9 10 >

1 - 100 of 3332 matches

Mail list logo