[Bug 2072517] [NEW] package bash 5.2.15-2ubuntu1 failed to install/upgrade: installed bash package post-installation script subprocess returned error exit status 1

[Per Mortensen]

Public bug reported:

Tried to upgrade from 22.04 to 24.04

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bash 5.2.15-2ubuntu1
Uname: Linux 5.10.160-rockchip aarch64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: arm64
CasperMD5CheckResult: unknown
CloudArchitecture: aarch64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: config-disk (/dev/nvme0n1p1)
Date: Mon Jul  8 19:43:03 2024
DuplicateSignature:
 package:bash:5.2.15-2ubuntu1
 Setting up bash (5.2.15-2ubuntu1) ...
 /bin/bash: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found 
(required by /bin/bash)
 dpkg: error processing package bash (--configure):
  installed bash package post-installation script subprocess returned error 
exit status 1
ErrorMessage: installed bash package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.3
 apt  2.4.12
SourcePackage: bash
Title: package bash 5.2.15-2ubuntu1 failed to install/upgrade: installed bash 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2024-07-08 (0 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2024-01-30T20:16:56

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


** Tags: apport-package arm64 mantic third-party-packages uec-images

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

Title:
  package bash 5.2.15-2ubuntu1 failed to install/upgrade: installed bash
  package post-installation script subprocess returned error exit status
  1

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


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

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Per Overgaard]

levitan89: Read my comment #32

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

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


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

[Bug 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver

[Per Overgaard]

Another Workaround:
This is using the Nvidia driver and not nouveau, right? I believe this is a 
driver in the Nvidia driver that is not asking for the conflicting framebuffers 
to be unregistered.
You can try to add "initcall_blacklist=simpledrm_platform_driver_init" to your  
kernel command line parameters to prevent the simpledrm driver to not be loaded.

Add to your kernel command line this. Open your terminal:
sudo nano /etc/default/grub
add "initcall_blacklist=simpledrm_platform_driver_init" to where it says 
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash..., so it looks like this:
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash 
initcall_blacklist=simpledrm_platform_driver_init”
ctrl+O for save and ctrl+X for quit. Back in the terminal write:
sudo update-grub
rebbot


This fixed the issue for me.

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

Title:
  Phantom "Unknown Display" shown in Settings after installing the
  Nvidia driver

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


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

Re: [Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo

[Per-Inge]

Updated and tested.
There is no crash at logout or restart

Den tis 5 okt. 2021 kl 17:05 skrev Launchpad Bug Tracker <
1943...@bugs.launchpad.net>:

> This bug was fixed in the package gnome-shell - 40.5-1ubuntu2
>
> ---
> gnome-shell (40.5-1ubuntu2) impish; urgency=medium
>
>   [ Daniel van Vugt ]
>   * debian/patches: Avoid full meta context finalization.
> To workaround (prevent) shutdown crashes (LP: #1936826, #1942031,
> #1942121,
> LP: #1943406, #1944054, #1945010, #1945116, #1944388)
>
>  -- Marco Trevisan (Treviño)   Tue, 05 Oct 2021
> 04:52:11 +0200
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: Confirmed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1944583).
> https://bugs.launchpad.net/bugs/1943406
>
> Title:
>   [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
>   release_expired_buffers_locked() from pb_cache_add_buffer() from
>   pb_destroy() from pb_reference_with_winsys() from
>   radeon_bo_reference()
>
> Status in Mutter:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-shell.  This problem was most recently seen with package
> version 40.2-1ubuntu6, the problem page at
> https://errors.ubuntu.com/problem/17edbc90dd7001a4a55edc878d9b3719dd3a4815
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mutter/+bug/1943406/+subscriptions
>
>

-- 
Skickat från min Sony Xperia eller Ubuntu

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

Title:
  [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
  release_expired_buffers_locked() from pb_cache_add_buffer() from
  pb_destroy() from pb_reference_with_winsys() from
  radeon_bo_reference()

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


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

[Bug 1943406] Re: [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in release_expired_buffers_locked() from pb_cache_add_buffer() from pb_destroy() from pb_reference_with_winsys() from radeon_bo_ref

[Per-Inge]

Now I get a problem that cannot be reported


** Attachment added: "Screenshot from 2021-09-28 16-27-45.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943406/+attachment/5528718/+files/Screenshot%20from%202021-09-28%2016-27-45.png

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

Title:
  [amdgpu] [radeon] gnome-shell crashed with SIGSEGV in
  release_expired_buffers_locked() from pb_cache_add_buffer() from
  pb_destroy() from pb_reference_with_winsys() from
  radeon_bo_reference()

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


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

[Bug 1943308] Re: can't connect to chromecast

[Per Johansson]

Likely https://github.com/muammar/mkchromecast/issues/334

Which indicates that mkchromecast doesn't work with python3-zeroconf
version 0.24.1

** Bug watch added: github.com/muammar/mkchromecast/issues #334
   https://github.com/muammar/mkchromecast/issues/334

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

Title:
  can't connect to chromecast

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


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

[Bug 1868502] Re: Synchronization with earlier Ubuntu versions or a recent Debian version fails

[Per Turbatus]

Unison does not support syncing between two different versions. Hence,
syncing across different ubuntu releases this problem will necessarily
occur unless they contain many unison versions in the future.

Workaround:

1) On both machines delete the unison cache:

rm -r ~/.unison

2) Make sure no version of unison is installed on the machine with the
newer Ubuntu release.

3) On the machine with the newer Ubuntu release download the unison .deb
file of the older release. For example the .deb file of the unison
version of Ubuntu 18.04 can be found here:

https://ubuntu.pkgs.org/18.04/ubuntu-universe-
amd64/unison_2.48.4-1ubuntu1_amd64.deb.html

Install this unison version via the graphical interface.

4) On the machine with the newer Ubuntu release freeze the unison
version you just installed. Warning you will not get security updates!

sudo apt-mark hold unison

5) Sync both machines using unison.

Have fun!

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

Title:
  Synchronization with earlier Ubuntu versions or a recent Debian
  version fails

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


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

[Bug 1929326] Re: Bluetooth WH-1000XM3 headphones disconnects and reconnects

[Per Larsson]

You can do one of two things;

1. Wait for Ubuntu 21.10 to be released and upgrade to that version.
That will install the new firmware package automatically.

or

1. Download this file: 
https://launchpad.net/ubuntu/+source/linux-firmware/1.198/+build/21596077/+files/linux-firmware_1.198_all.deb
2a. Install it by double-clicking on it in a file manager.
or
2b. If you're comfortable using the terminal or a command shell, you can type 
in the command "sudo dpkg -i 
/path_to_download_folder/linux-firmware_1.198_all.deb" to accomplish the same 
thing.
3. You will need to completely power off your computer and power it back on 
again after the firmware package is installed. A simple reboot is not enough.

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

Title:
  Bluetooth WH-1000XM3 headphones disconnects and reconnects

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


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

[Bug 1923335] Re: At shutdown the spinner logo disappears and a second later it comes back frozen for a while (in kernel 5.11 but 5.10.16 works)

[Per-Inge]

My Impish installation don't behave like that.
At restart
I see the spinner for about 4 sec, then black screen for about 12 sec until I 
see the "Asus logo" and a second later the grub menu.
The only customization is some extensions:
ArcMenu
Just Perfection to move the panel to bottom of the screen
Places Status Indicator
Vitals
Weather in The Clock
Ubuntu Dock is turned off
p-i@pi-asus-b550m-wifi:~$ inxi -Fz
System:Kernel: 5.13.0-14-generic x86_64 bits: 64 Desktop: GNOME 40.2 
Distro: Ubuntu 21.10 (Impish Indri) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
   Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804 
   date: 02/02/2021 
CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP cache: 
L2: 3 MiB 
   Speed: 2876 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 2876 2: 
2878 3: 3599 4: 2875 5: 3595 6: 2876 7: 2446 
   8: 2236 9: 2235 10: 2238 11: 2236 12: 2885 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
   v: kernel 
   Device-2: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
   Display: wayland server: X.Org 1.21.1.2 driver: loaded: amdgpu note: 
n/a (using device driver) 
   resolution: 2560x1440~60Hz 
   OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.41.0 
5.13.0-14-generic LLVM 12.0.1) v: 4.6 Mesa 21.1.4 
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
   Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
   Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
   Sound Server-1: ALSA v: k5.13.0-14-generic running: yes 
   Sound Server-2: PulseAudio v: 15.0 running: yes 
   Sound Server-3: PipeWire v: 0.3.32 running: yes 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
   IF: wlp6s0 state: down mac:  
   Device-2: Realtek RTL8125 2.5GbE driver: r8169 
   IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:  
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb 
   Report: hciconfig ID: hci0 state: up address:  bt-v: 3.0 
Drives:Local Storage: total: 1.36 TiB used: 55.86 GiB (4.0%) 
   ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB 
   ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 
GiB 
   ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 
GiB 
Partition: ID-1: / size: 456.89 GiB used: 55.83 GiB (12.2%) fs: ext4 dev: 
/dev/sda2 
   ID-2: /boot/efi size: 511 MiB used: 33.9 MiB (6.6%) fs: vfat dev: 
/dev/nvme0n1p1 
Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile 
Sensors:   System Temperatures: cpu: 35.6 C mobo: 40.0 C gpu: amdgpu temp: 42.0 
C 
   Fan Speeds (RPM): fan-1: 730 fan-2: 938 fan-3: 720 fan-7: 929 gpu: 
amdgpu fan: 0 
Info:  Processes: 373 Uptime: 3m Memory: 15.54 GiB used: 1.81 GiB (11.7%) 
Shell: Bash inxi: 3.3.06 
p-i@pi-asus-b550m-wifi:~$

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

Title:
  At shutdown the spinner logo disappears and a second later it comes
  back frozen for a while (in kernel 5.11 but 5.10.16 works)

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


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

[Bug 1929326] Re: Bluetooth WH-1000XM3 headphones disconnects and reconnects

[Per Larsson]

This appears to be related to a problem with the firmware for the Intel
AX200 bluetooth adapter. After installing the linux-firmware package for
Ubuntu 21.10, downloaded from https://launchpad.net/ubuntu/+source
/linux-firmware/1.198, which contains an updated firmware for that
adapter, the problem seems to have gone away. A full power cycle of the
computer was required for the firmware to load, not a simple reboot.

I have not done extensive testing since installing the updated linux-
firmware package 2 days ago, but I have not since been able to reproduce
the problem.

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

Title:
  Bluetooth WH-1000XM3 headphones disconnects and reconnects

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

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

[Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

[Per Olav Kroka]

Please disregard my last comment (#5).  The problem I had was not this
one but related to using other connector agents in addition to
NetworkManager, in my case the openvpn3 command line.

(Automatic connection to the VPN is not there, but that is probably
safest.)

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

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

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

Re: [Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

[Per-Inge]

Installed Ubuntu 20.04.
Enabled "Developer Options".
Updated and systemd 245.4-4ubuntu3.7 was installed. Rebooted and the system
booted and worked OK.
However the installed version of Ubuntu 20.04 use Kernel: 5.8.0-54-generic
x86_64.
Bluetooth works fine.

Den ons 2 juni 2021 kl 01:15 skrev Brian Murray <1921...@bugs.launchpad.net
>:

> Hello Per-Inge, or anyone else affected,
>
> Accepted systemd into focal-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.7 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: systemd (Ubuntu Focal)
>Status: In Progress => Fix Committed
>
> ** Tags added: verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1921696
>
> Title:
>   Failed to start Load/Save RF Kill Switch Status
>
> Status in systemd:
>   Fix Released
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in systemd source package in Focal:
>   Fix Committed
> Status in systemd source package in Groovy:
>   Fix Committed
>
> Bug description:
>   [impact]
>
>   systemd-rfkill fails when running under kernel 5.10 or later due to
>   change in the kernel/userspace api
>
>   [test case]
>
>   on a system with kernel 5.10 or later, check systemd-rfkill status or
>   journal output, see comment 3 for specific failure text
>
>   [regression]
>
>   any regression would almost certainly cause problems with the systemd-
>   rfkill service and/or systemd-rfkill binary
>
>   [scope]
>
>   this is needed for focal
>
>   this was fixed upstream in commit
>   a71c09685021cbcecb7566a00342421f635cc002 which was backported to h in
>   version 247.3-3ubuntu3.
>
>   since this only occurs with kernel 5.10 or later, no releases earlier
>   than f are affected because they will never receive kernel 5.10.
>
>   since the HWE kernel in f will be updated to 5.10 once 21.04 is
>   released, this is needed for f. Since a user could upgrade to the 5.10
>   HWE kernel in f, and then do-release-upgrade to g before it EOL, this
>   is also needed in g.
>
>   [original description]
>
>
>   When I boot the system I get these lög messages
>   - Failed to start Load/Save RF Kill Switch Statu
>   - A start job for unit systemd-rfkill.service has failed
>   and with sender systemd-rfkil
>   Read event structure of invalid size
>
>   Also happens on an Ubuntu system on the same computer.
>
>   System details
>
>   p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
>   System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon
> 4.8.6 Distro: Ubuntu 21.04 (Hirsute Hippo)
>   Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:
> 
>  Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev
> X.0x serial:  UEFI: American Megatrends v: 1804
>  date: 02/02/2021
>   CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP
> L2 cache: 3 MiB
>  Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1:
> 2509 2: 2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798
>  8: 2239 9: 2238 10: 2233 11: 2236 12: 2234
>   Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX
> 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu
>  v: kernel
>  Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati
> unloaded: fbdev,modesetting,radeon,vesa
>  resolution: 2560x1440~60Hz
>  OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0
&g

[Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

[Per Olav Kroka]

I just want to confirm that this is a problem.  I have had it for a
while and not found another workaround (until now) than restarting the
machine.

If this is NOT a bug then something "close by" is a bug.

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

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

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

[Bug 1929326] Re: Bluetooth WH-1000XM3 headphones disconnects and reconnects

[Per Larsson]

** Attachment added: "Output from 'sudo journalctl --since="-10 minutes"'"
   
https://bugs.launchpad.net/ubuntu/+bug/1929326/+attachment/5499594/+files/log-output.txt

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

Title:
  Bluetooth WH-1000XM3 headphones disconnects and reconnects

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

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

[Bug 1929326] [NEW] Bluetooth WH-1000XM3 headphones disconnects and reconnects

[Per Larsson]

Public bug reported:

>From time to time, my Sony WH-1000XM3 Bluetooth connected headphones
automatically disconnect, and then a couple of seconds later reconnects.
This started happening after updating Ubuntu from 20.10 to 21.04. This
never happened even once when using Ubuntu 20.10, and the headphones are
not used or paired to any other device. The only device that has had any
changes to it is the computer which is now running Ubuntu 21.04.

It is currently using a custom kernel from https://kernel.ubuntu.com
/~kernel-ppa/mainline/ in an attempt to see if that would mitigate the
problem. It did not. The issue started to happen when the Ubuntu 21.04
system was running its default kernel.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
Uname: Linux 5.12.4-051204-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  per2734 F pulseaudio
 /dev/snd/controlC2:  per2734 F pulseaudio
 /dev/snd/controlC0:  per2734 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun May 23 12:58:22 2021
InstallationDate: Installed on 2018-11-26 (908 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: WH-1000XM3
Symptom_PulseAudioLog:
 maj 23 11:33:04 perdator systemd[1473]: pulseaudio.service: Succeeded.
 maj 23 11:33:14 perdator systemd[1473]: pulseaudio.socket: Succeeded.
 maj 23 12:35:05 perdator dbus-daemon[1151]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" 
(uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
 maj 23 12:54:15 perdator dbus-daemon[1151]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.79" (uid=1000 pid=2734 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.5" 
(uid=0 pid=1147 comm="/usr/lib/bluetooth/bluetoothd ")
Symptom_Type: Sound works for a while, then breaks
Title: [WH-1000XM3, playback] fails after a while
UpgradeStatus: Upgraded to hirsute on 2021-05-10 (13 days ago)
dmi.bios.date: 03/11/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5843
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X470-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5843:bd03/11/2021:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX470-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  Bluetooth WH-1000XM3 headphones disconnects and reconnects

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

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

Re: [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

[Per-Inge]

Don't get the crash any longer.

Den tors 22 apr. 2021 kl 16:41 skrev Launchpad Bug Tracker <
1820...@bugs.launchpad.net>:

> This bug was fixed in the package nautilus - 1:3.38.2-1ubuntu2
>
> ---
> nautilus (1:3.38.2-1ubuntu2) hirsute; urgency=medium
>
>   * d/p/19_unity_open_location_xid:
> - Do not update opened locations on bus connection.
>   Nautilus may connect to the bus when the application is already about
>   shut down, however at that point its implementation is destroyed but
>   Gio doesn't handle this gracefully as per GNOME/GLib!2056.
>   To prevent this, we can safely reduce the delta of the distro-patch
> by
>   avoiding updating the opened locations on bus acquired, as we
> already do
>   it in all the cases a window actually changes its state. (LP:
> #1820859)
>
>  -- Marco Trevisan (Treviño)   Wed, 21 Apr 2021
> 07:03:29 +0200
>
> ** Changed in: nautilus (Ubuntu Hirsute)
>Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1820859
>
> Title:
>   nautilus --version segfaults in
>   g_application_impl_get_dbus_object_path
>
> Status in nautilus package in Ubuntu:
>   Fix Released
> Status in nautilus source package in Hirsute:
>   Fix Released
>
> Bug description:
>   * Impact
>
>   nautilus hits a segfault when called with the version argument, which
>   was annoying but became problematic in hirsute since the desktop icons
>   ng calls that command to check if nautilus is available
>
>   * Test case
>
>   $ nautilus --version
>   shouldn't segfault
>
>   * Regression potential
>
>   The change is in a patch which was added to expose open locations to
>   Unity for the benefit of the launcher and which is also used by the
>   dashtodock one now. Check that the launcher correctly indicates which
>   windows are active, especially when dealing with external devices.
>
>   --
>
>
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding nautilus.  This problem was most recently seen with package
> version 1:3.31.90-1ubuntu2, the problem page at
> https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions
>


-- 
Skickat från min Sony Xperia eller Ubuntu

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

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

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

[Bug 1925464] [NEW] Cannot open /boot/efi

[Per-Inge]

Public bug reported:

Get this error message when trying to open /boot/efi
"gdbus error freedesktop policykit1 error failed unix process subject does not 
have uuid set"

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nautilus 1:3.38.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 22 12:24:31 2021
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'355'
 b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
 b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2021-04-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 evince40.1-1
 file-roller   3.38.1-1
 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1
 nautilus-share0.7.3-2ubuntu3

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


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

** Attachment added: "error message"
   
https://bugs.launchpad.net/bugs/1925464/+attachment/5490958/+files/Screenshot%20from%202021-04-22%2012-29-55.png

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

Title:
  Cannot open /boot/efi

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

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

[Bug 1921696] Re: Failed to start Load/Save RF Kill Switch Status

[Per-Inge]

Didn't get the log message about rfkill after boot this morning.
After update today I have systemd 247.3-3ubuntu3 installed.

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

Title:
  Failed to start Load/Save RF Kill Switch Status

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

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

[Bug 1922234] [NEW] Grub doesn't update kernel version

[Per-Inge]

Public bug reported:

You have a dual boot with two Ubuntu versions installed, e.g lts version and 
development version.  The kernel in the development version is updated. At 
reboot the development version will boot with the old kernel.
To boot with the new kernel you first have to boot with the Ubuntu version at 
the top position in the grub menu and run sudo update-grub.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: grub-efi-amd64-bin 2.04-1ubuntu44
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  1 14:07:53 2021
InstallationDate: Installed on 2021-02-11 (48 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210211)
SourcePackage: grub2-unsigned
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-unsigned (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute 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/1922234

Title:
  Grub doesn't update kernel version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1922234/+subscriptions

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

[Bug 1921696] [NEW] Failed to start Load/Save RF Kill Switch Status

[Per-Inge]

Public bug reported:

When I boot the system I get these lög messages
- Failed to start Load/Save RF Kill Switch Statu
- A start job for unit systemd-rfkill.service has failed
and with sender systemd-rfkil
Read event structure of invalid size

Also happens on an Ubuntu system on the same computer.

System details

p-i@pi-tuf-b550m-wifi:~$ inxi -Fz
System:Kernel: 5.11.0-11-generic x86_64 bits: 64 Desktop: Cinnamon 4.8.6 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
   Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1804 
   date: 02/02/2021 
CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3 MiB 
   Speed: 2509 MHz min/max: 2200/4791 MHz Core speeds (MHz): 1: 2509 2: 
2237 3: 2858 4: 2236 5: 2235 6: 2238 7: 2798 
   8: 2239 9: 2238 10: 2233 11: 2236 12: 2234 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
   v: kernel 
   Display: x11 server: X.Org 1.20.10 driver: loaded: amdgpu,ati 
unloaded: fbdev,modesetting,radeon,vesa 
   resolution: 2560x1440~60Hz 
   OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.40.0 
5.11.0-11-generic LLVM 11.0.1) v: 4.6 Mesa 21.0.1 
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
   Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
   Device-3: Logitech Webcam C250 type: USB driver: 
snd-usb-audio,uvcvideo 
   Sound Server: ALSA v: k5.11.0-11-generic 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
   IF: wlp6s0 state: down mac:  
   Device-2: Realtek RTL8125 2.5GbE driver: r8169 
   IF: enp7s0 state: up speed: 1000 Mbps duplex: full mac:  
   IF-ID-1: vmnet1 state: unknown speed: N/A duplex: N/A mac:  
   IF-ID-2: vmnet8 state: unknown speed: N/A duplex: N/A mac:  
Bluetooth: Device-1: Intel AX200 Bluetooth type: USB driver: btusb 
   Report: ID: hci0 state: up running pscan bt-v: 3.0 address:  
Drives:Local Storage: total: 1.36 TiB used: 97.88 GiB (7.0%) 
   ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP600 size: 465.76 
GiB 
   ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 
GiB 
   ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 
GiB 
Partition: ID-1: / size: 456.96 GiB used: 97.84 GiB (21.4%) fs: ext4 dev: 
/dev/nvme0n1p2 
   ID-2: /boot/efi size: 511 MiB used: 33.3 MiB (6.5%) fs: vfat dev: 
/dev/nvme0n1p1 
Swap:  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: 
/swapfile 
Sensors:   System Temperatures: cpu: 35.9 C mobo: 39.0 C gpu: amdgpu temp: 40.0 
C 
   Fan Speeds (RPM): fan-1: 698 fan-2: 937 fan-3: 711 fan-7: 931 gpu: 
amdgpu fan: 0 
Info:  Processes: 372 Uptime: 13m Memory: 15.54 GiB used: 1.88 GiB (12.1%) 
Shell: Bash inxi: 3.3.01 
p-i@pi-tuf-b550m-wifi:~$

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: systemd 247.3-3ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
Uname: Linux 5.11.0-11-generic x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: X-Cinnamon
Date: Mon Mar 29 10:12:21 2021
InstallationDate: Installed on 2021-02-05 (51 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203)
MachineType: ASUS System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic 
root=UUID=d37b6e75-43a0-4e56-85c1-4a6ef8e1ffc9 ro acpi_enforce_resources=lax 
quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: 
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1804
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B550M-PLUS (WI-FI)
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 

[Bug 1913384] Re: Request header parsing fails in some cases with Tomcat 9.0.31

[Per Lundberg]

Here are some more details about this, from the Tomcat 9.0 changelog:
https://ci.apache.org/projects/tomcat/tomcat9/docs/changelog.html.
Tomcat 9.0.33 introduces the fix:

> 64210: Correct a regression in the improvements to HTTP header
validation that caused requests to be incorrectly treated as invalid if
a CRLF sequence was split between TCP packets. Improve validation of
request lines, including for HTTP/0.9 requests. (markt)

The exact upstream commit which has the fix is available here:
https://github.com/apache/tomcat/commit/27a0c116e02ba9cd66873ded0e64b8c0fec2bc19

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

Title:
  Request header parsing fails in some cases with Tomcat 9.0.31

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

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

[Bug 1910220] Re: Characters from dead keys shown in plan view in password field on login screen

[Per Larsson]

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


** Attachment added: "Partially hidden password"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1910220/+attachment/5462183/+files/Ubuntu%2064-bit-2021-02-10-09-16-02.png

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

Title:
  Characters from dead keys shown in plan view in password field on
  login screen

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

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

[Bug 1910220] Re: Characters from dead keys shown in plan view in password field on login screen

[Per Larsson]

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

If this bug was a duplicate of or related to
https://bugs.launchpad.net/bugs/1772791 I would expect the whole
password to be visible. Please see newly uploaded screenshot. Only the
accent from the dead key is visible, while the other three letters in
the password are obscured.

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

Title:
  Characters from dead keys shown in plan view in password field on
  login screen

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

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

[Bug 1910220] Re: Characters from dead keys shown in plan view in password field on login screen

[Per Larsson]

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

I don't believe this is a duplicate of
https://bugs.launchpad.net/bugs/1772791 as this is specifically about
using dead keys when typing in a password. At no time does the entire
password display in clear text. Only the accents of dead keys are shown,
but as the intended letter is then pressed, the completed letter with
accent is hidden.

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

Title:
  Characters from dead keys shown in plan view in password field on
  login screen

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

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

[Bug 1906294] Re: systemd-journal hang after chromium is closed

[Per-Inge]

Has been fixed after updates. Probably one of these
Start-Date: 2020-12-01  19:43:08
Commandline: aptdaemon role='role-commit-packages' sender=':1.241'
Upgrade: xserver-common:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xorg-core:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xorg-legacy:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), 
xserver-xephyr:amd64 (2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1), xwayland:amd64 
(2:1.20.9-2ubuntu1, 2:1.20.9-2ubuntu1.1)
End-Date: 2020-12-01  19:43:10

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

Title:
  systemd-journal hang after chromium is closed

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

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

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

[Per-Inge]

I installed all the updates in proposed (main repository) and now have
libfprint-2-2 1:1.90.3tod1-0ubuntu3 installed
This fixed the problem on my computer

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

Title:
  Mouse stop moving after few seconds. restart at click

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

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

[Bug 1906294] [NEW] systemd-journal hang after chromium is closed

[Per-Inge]

Public bug reported:

CPU usage after close of Chromium is 98,7% by systemd-jounal after these
updates

Start-Date: 2020-11-30  18:39:16
Commandline: packagekit role='update-packages'
Upgrade: gir1.2-mutter-7:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), snapd:amd64 
(2.47.1+20.10.1, 2.48+20.10), libmutter-7-0:amd64 (3.38.1-1ubuntu1, 
3.38.1-2ubuntu1), mutter-common:amd64 (3.38.1-1ubuntu1, 3.38.1-2ubuntu1), 
gir1.2-snapd-1:amd64 (1.57-0ubuntu4, 1.58-0ubuntu0.20.10.0), 
libsnapd-glib1:amd64 (1.57-0ubuntu4, 1.58-0ubuntu0.20.10.0)
End-Date: 2020-11-30  18:39:25

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Uname: Linux 5.10.0-051000rc3-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 30 19:20:00 2020
InstallationDate: Installed on 2020-11-14 (16 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Snap: chromium 87.0.4280.66 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy snap

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

Title:
  systemd-journal hang after chromium is closed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1906294/+subscriptions

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

[Bug 1905946] Re: Mouse stop moving after few seconds. restart at click

[Per-Inge]

Same problem mouse is Steeleries Rival 110
My configuration is
p-i@pi-TUF-Gaming-B550M:~$ inxi -Fz
System:Kernel: 5.8.0-25-generic x86_64 bits: 64 Desktop: GNOME 3.38.1 
Distro: Ubuntu 21.04 (Hirsute Hippo) 
Machine:   Type: Desktop System: ASUS product: N/A v: N/A serial:  
   Mobo: ASUSTeK model: TUF GAMING B550M-PLUS (WI-FI) v: Rev X.0x 
serial:  UEFI: American Megatrends v: 1212 
   date: 11/04/2020 
CPU:   Info: 6-Core model: AMD Ryzen 5 5600X bits: 64 type: MT MCP L2 
cache: 3072 KiB 
   Speed: 2196 MHz min/max: 2200/3700 MHz Core speeds (MHz): 1: 2198 2: 
2198 3: 2199 4: 2200 5: 2199 6: 2194 7: 2198 
   8: 2201 9: 2193 10: 2195 11: 2194 12: 2192 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] driver: amdgpu 
   v: kernel 
   Display: x11 server: X.Org 1.20.9 driver: amdgpu,ati unloaded: 
fbdev,modesetting,radeon,vesa 
   resolution: 2560x1440~60Hz 
   OpenGL: renderer: AMD Radeon RX 5700 (NAVI10 DRM 3.38.0 
5.8.0-25-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.2 
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 HDMI Audio 
driver: snd_hda_intel 
   Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio 
driver: snd_hda_intel 
   Sound Server: ALSA v: k5.8.0-25-generic 
Network:   Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi 
   IF: wlp6s0 state: up mac:  
   Device-2: Realtek RTL8125 2.5GbE driver: N/A 
Drives:Local Storage: total: 1.36 TiB used: 24.03 GiB (1.7%) 
   ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 
465.76 GiB 
   ID-2: /dev/nvme1n1 vendor: Kingston model: SA2000M8500G size: 465.76 
GiB 
   ID-3: /dev/sda vendor: Samsung model: SSD 860 EVO 500GB size: 465.76 
GiB 
Partition: ID-1: / size: 456.96 GiB used: 24.00 GiB (5.3%) fs: ext4 dev: 
/dev/sda2 
Swap:  ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: 
/swapfile 
Sensors:   System Temperatures: cpu: 0.0 C mobo: N/A gpu: amdgpu temp: 46.0 C 
   Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 
Info:  Processes: 362 Uptime: 2m Memory: 15.54 GiB used: 2.20 GiB (14.2%) 
Shell: Bash inxi: 3.1.09 
p-i@pi-TUF-Gaming-B550M:~$

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

Title:
  Mouse stop moving after few seconds. restart at click

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

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

[Bug 1904382] Re: Always crash when opened

[Per-Inge]

Fixed in this update
Start-Date: 2020-11-22  09:54:35
Commandline: apt upgrade
Requested-By: p-i (1000)
Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 
(1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), 
mscompress:amd64 (0.4-7, 0.4-8), libcurl4:amd64 (7.68.0-1ubuntu4, 
7.72.0-1ubuntu1), libk5crypto3:amd64 (1.17-10, 1.17-10ubuntu1), 
ubuntu-drivers-common:amd64 (1:0.8.6.1, 1:0.8.6.2), libkrb5support0:amd64 
(1.17-10, 1.17-10ubuntu1), python3-dbus:amd64 (1.2.16-3, 1.2.16-4), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu4, 7.72.0-1ubuntu1)
End-Date: 2020-11-22  09:54:37

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

Title:
  Always crash when opened

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

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

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

[Per-Inge]

Fixed in this update

Start-Date: 2020-11-22  09:54:35
Commandline: apt upgrade
Requested-By: p-i (1000)
Upgrade: libc-ares2:amd64 (1.16.1-1ubuntu1, 1.17.1-1), libkrb5-3:amd64 
(1.17-10, 1.17-10ubuntu1), libgssapi-krb5-2:amd64 (1.17-10, 1.17-10ubuntu1), 
mscompress:amd64 (0.4-7, 0.4-8), libcurl4:amd64 (7.68.0-1ubuntu4, 
7.72.0-1ubuntu1), libk5crypto3:amd64 (1.17-10, 1.17-10ubuntu1), 
ubuntu-drivers-common:amd64 (1:0.8.6.1, 1:0.8.6.2), libkrb5support0:amd64 
(1.17-10, 1.17-10ubuntu1), python3-dbus:amd64 (1.2.16-3, 1.2.16-4), 
libcurl3-gnutls:amd64 (7.68.0-1ubuntu4, 7.72.0-1ubuntu1)
End-Date: 2020-11-22  09:54:37

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

Title:
  update-manager crashed with dbus.exceptions.DBusException in update():
  org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
  with unknown return code 1

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

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

[Bug 1904878] Re: update-manager crashed with dbus.exceptions.DBusException in update(): org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

[Per-Inge]

** Information type changed from Private to Public

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

Title:
  update-manager crashed with dbus.exceptions.DBusException in update():
  org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited
  with unknown return code 1

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

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

[Bug 1904866] Re: Software updater fails to update with errors

[Per-Inge]

I got the bug on Ubuntu with the ubuntu-desktop

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

Title:
  Software updater fails to update with errors

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

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

Re: [Bug 1904382] Re: Always crash when opened

[Per-Inge]

I think the bug is reported in
https://bugs.launchpad.net/bugs/1904217
When I tried to report the crash I got the message that it already is
reported, but I don't have permission to open the bug.

Den mån 16 nov. 2020 kl 10:56 skrev Julian Andres Klode <
1904...@bugs.launchpad.net>:

> Thanks for your bug report. Unfortunately, you have not included any
> error messages like the stacktrace from such a crash, and the bug cannot
> be analyzed further without them.
>
> ** Changed in: update-manager (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1904382
>
> Title:
>   Always crash when opened
>
> Status in update-manager package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Crash when opened on a new hirsute installation.
>   sudo apt update and sudo apt upgrade work OK
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.04
>   Package: update-manager 1:20.10.1
>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>   Uname: Linux 5.8.0-25-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu51
>   Aptdaemon:
>
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Nov 16 09:16:05 2020
>   GsettingsChanges:
>b'com.ubuntu.update-manager' b'launch-count' b'4'
>b'com.ubuntu.update-manager' b'launch-time' b'int64 1605513900'
>   InstallationDate: Installed on 2020-11-15 (0 days ago)
>   InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201115)
>   PackageArchitecture: all
>   SourcePackage: update-manager
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1904382/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  Always crash when opened

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

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

[Bug 1904382] [NEW] Always crash when opened

[Per-Inge]

Public bug reported:

Crash when opened on a new hirsute installation.
sudo apt update and sudo apt upgrade work OK

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: update-manager 1:20.10.1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu51
Aptdaemon:
 
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 16 09:16:05 2020
GsettingsChanges:
 b'com.ubuntu.update-manager' b'launch-count' b'4'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1605513900'
InstallationDate: Installed on 2020-11-15 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201115)
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  Always crash when opened

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

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

[Bug 1902545] [NEW] software-properties-gtk error

[Per Bovbjerg]

Public bug reported:

ERROR:dbus.proxies:Introspect error on :1.225:/: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message 
bus without replying
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.225 was not provided by any .service files

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

Title:
  software-properties-gtk error

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

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

[Bug 1901541] [NEW] update to 20.04 fails

[Per Axelson]

Public bug reported:

trying to update to 20.04. Removed all ppas and still it fails.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 26 13:42:49 2020
InstallationDate: Installed on 2020-01-16 (283 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-10-26 (0 days ago)
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2020-10-23T23:24:13.380310

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

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

Title:
  update to 20.04 fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901541/+subscriptions

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

Re: [Bug 1900998] Re: ubiquity graphic problems

[Per-Inge]

Installed the 20201022 ISO.
This worked better and the 2:nd time the installation worked without
graphic issues
The 1:st time I got a system hang, when I used the mouse to scroll down to
find the keyboard layout. Had to do a hard reset of the computer.

Den tors 22 okt. 2020 kl 15:38 skrev Per-Inge Hallin <
peringe.hal...@gmail.com>:

> A screenshot looks OK. But this time I got a gnome-shell crash and I
> uploaded this. Probably it's a gnome-shell problem and not ubiquity.
>
> Den tors 22 okt. 2020 kl 14:01 skrev Jean-Baptiste Lallement <
> 1900...@bugs.launchpad.net>:
>
>> Thanks for your report. Can you please attach a screenshot of the issue?
>>
>> ** Changed in: ubiquity (Ubuntu)
>>Status: New => Incomplete
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1900998
>>
>> Title:
>>   ubiquity graphic problems
>>
>> Status in ubiquity package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   USB booted OK, graphic problem started when selecting keyboard and
>> continued during the installation with unreadable text and slide show with
>> graphic problems.
>>   Hard to select keyboard, had to guess the right keyboard was selected.
>>   Installation is OK with Nvidia driver.
>>   UEFI install
>>   GPU: Nvidia GEFORCE GTX 660
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 20.10
>>   Package: ubiquity (not installed)
>>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>>   Uname: Linux 5.8.0-25-generic x86_64
>>   NonfreeKernelModules: nvidia_modeset nvidia
>>   ApportVersion: 2.20.11-0ubuntu50
>>   Architecture: amd64
>>   CasperMD5CheckResult: skip
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Thu Oct 22 12:41:51 2020
>>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
>> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>>   InstallationDate: Installed on 2020-10-22 (0 days ago)
>>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64
>> (20201021.2)
>>   SourcePackage: ubiquity
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>>
>> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900998/+subscriptions
>>
>
>
> --
> Skickat från min nya mailadress
>


-- 
Skickat från min nya mailadress

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

Title:
  ubiquity graphic problems

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

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

Re: [Bug 1900998] Re: ubiquity graphic problems

[Per-Inge]

A screenshot looks OK. But this time I got a gnome-shell crash and I
uploaded this. Probably it's a gnome-shell problem and not ubiquity.

Den tors 22 okt. 2020 kl 14:01 skrev Jean-Baptiste Lallement <
1900...@bugs.launchpad.net>:

> Thanks for your report. Can you please attach a screenshot of the issue?
>
> ** Changed in: ubiquity (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1900998
>
> Title:
>   ubiquity graphic problems
>
> Status in ubiquity package in Ubuntu:
>   Incomplete
>
> Bug description:
>   USB booted OK, graphic problem started when selecting keyboard and
> continued during the installation with unreadable text and slide show with
> graphic problems.
>   Hard to select keyboard, had to guess the right keyboard was selected.
>   Installation is OK with Nvidia driver.
>   UEFI install
>   GPU: Nvidia GEFORCE GTX 660
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.10
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
>   Uname: Linux 5.8.0-25-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu50
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Thu Oct 22 12:41:51 2020
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2020-10-22 (0 days ago)
>   InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64
> (20201021.2)
>   SourcePackage: ubiquity
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900998/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ubiquity graphic problems

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

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

[Bug 1900998] [NEW] ubiquity graphic problems

[Per-Inge]

Public bug reported:

USB booted OK, graphic problem started when selecting keyboard and continued 
during the installation with unreadable text and slide show with graphic 
problems.
Hard to select keyboard, had to guess the right keyboard was selected.
Installation is OK with Nvidia driver.
UEFI install
GPU: Nvidia GEFORCE GTX 660

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 22 12:41:51 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2020-10-22 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201021.2)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy ubiquity-20.10.13

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

Title:
  ubiquity graphic problems

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

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

[Bug 1880749] Re: python3 virtualenvs include (broken) bundled pip deps

[Per Lundberg]

For the record: This is still broken in Ubuntu 20.04 (Focal Fossa). It
breaks Ansible being able to support 20.04 in their official PPA.
Tracking ticket on the Ansible side:
https://github.com/ansible/ansible/issues/69203

It would be awesome if someone with the time and energy would do the
work suggested by Kai to get this fix into a Focal Fossa update as well,
so we can get these packages working there. Otherwise, people on Focal
Fossa are bound to run the repo-provided Ansible packages (i.e. some
older version).

** Bug watch added: github.com/ansible/ansible/issues #69203
   https://github.com/ansible/ansible/issues/69203

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

Title:
  python3 virtualenvs include (broken) bundled pip deps

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

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

[Bug 1890124] Re: I can't click on the bottom ~25 % of the screen

[Per Johansson]

Hi,

I haven't configured anything about the on-screen keyboard so it should
be the default one, whichever that is. I don't ever use it, to be
honest, but it does appear if I touch a text field on the screen. Ah,
now after I've used it the cursor work on the bottom part of the screen
again.

I've confirmed there's no extensions in the extensions app except the
built in ones.

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890124/+attachment/5398227/+files/Sk%C3%A4rmbild%20fr%C3%A5n%202020-08-03%2012-00-27.png

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

Title:
  I can't click on the bottom ~25 % of the screen

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

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

[Bug 1890124] [NEW] I can't click on the bottom ~25 % of the screen

[Per Johansson]

Public bug reported:

Whenever I move the cursor to the bottom ~25 % of the screen I can't use
it to click. Sometimes but not alwyas there's a busy cursor displayed.

The on-screen keyboard popped up before and I think maybe it covered
roughly the same area. It disappeared when I typed my login password on
the lock screen using the physical keyboard. Still, maybe it could be
related?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
Uname: Linux 5.7.4-050704-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Åtkomst nekas: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  3 11:25:21 2020
DistUpgraded: 2020-04-29 11:55:55,099 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 620 [1028:07e6]
InstallationDate: Installed on 2018-05-05 (820 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9370
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.7.4-050704-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
btusb.enable_autosuspend=n vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-29 (95 days ago)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
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.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  I can't click on the bottom ~25 % of the screen

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

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

Re: [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist(

[Per-Inge]

I don't have problems with suspend any longer. I think this bug is
fixed.

However I'm not using the standard kernel.  I'm using Kernel:
5.7.7-050707-generic x86_64.
I had a problem with Chrome freezing the computer and this kernel fixed
that problem.

Den tis 14 juli 2020 kl 16:01 skrev Martin Wimpress <
1868...@bugs.launchpad.net>:

> ** Changed in: gnome-shell (Ubuntu Focal)
>  Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> ** Changed in: gnome-shell (Ubuntu)
>  Assignee: (unassigned) => Daniel van Vugt (vanvugt)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868660
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
>   from st_texture_cache_load_gicon() from st_icon_update() from
>   _g_closure_invoke_va() from g_signal_emit_valist()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem
> regarding gnome-shell.  This problem was most recently seen with package
> version 3.35.91-1ubuntu2, the problem page at
> https://errors.ubuntu.com/problem/f48b96bcfbbd221faf772da51dae29be310cbd9c
> contains more details, including versions of packages affected, stacktrace
> or traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software
> developer, you can request it at http://forms.canonical.com/reports/.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868660/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

[Bug 1885414] Re: on flavours ubiquity: bootloader failed on /dev/vda

[Per-Inge]

Made an USB boot disk with mkusb and tested the Groovy Ubuntu Desktop
amd64 version 20200709.

Worked with MBR/BIOS mode on a desktop computer with an AMD Bulldozer CPU and 
Nvidia 1660 GPU. There were however some peculiar things
- Graphical artifacts during the installation. Perhaps "Safe graphics mode" is 
needed.
- Had to power off after the installation to boot the computer
- At boot you get the message: BootOrder not found. Initializing default. 
Creating boot entry "Boot002" with label "ubuntu" for file 
\EFI\ubuntu\shimx64.efi

Worked as expected on a newer computer with Ryzen CPU and Radeon GPU.

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

Title:
  on flavours ubiquity: bootloader failed on /dev/vda

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

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

[Bug 1885414] Re: ubiquity: bootloader failed on /dev/vda

[Per-Inge]

Tested installation in VirtualBox of Ubuntu desktop amd64 version
20200707.1 in both MBR and EFI mode. Both worked OK.

Tested to install from USB in MBR mode on a computer with Nvidia GPU.
Doesn't work. get an error message about /DEV/SR0 No media found

Tested on another computer in EFI mode. Doesn't work. Error message
"Unable to find a medium container a live file system"

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

Title:
  ubiquity: bootloader failed on /dev/vda

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

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

[Bug 1879559] Re: net/bpfilter: remove superfluous testing message

[Per Allansson]

I disagree on the "low" priority of this one as it 1) fills up logs and
2) causes support questions (and thus wasting everyone's time).

So, please backport this one ASAP to the hwe kernels.

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

Title:
   net/bpfilter: remove superfluous testing message

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

[Per-Inge]

p-i@asus-b450-f:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.36.3-1ubuntu1~20.04.2
  Candidate: 3.36.3-1ubuntu1~20.04.2
  Version table:
 *** 3.36.3-1ubuntu1~20.04.2 500
500 http://se.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
100 /var/lib/dpkg/status
 3.36.2-1ubuntu1~20.04.1 500
500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
 3.36.1-5ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages
p-i@asus-b450-f:~

Den fre 19 juni 2020 kl 16:05 skrev Marco Trevisan (Treviño) <
1877...@bugs.launchpad.net>:

> Please, ensure the version with the command I gave to you
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

[Per-Inge]

No, this is noy groovy. I have downloaded Focal Daily from
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds some days ago and
updates regularly and I think the developer option is set.
After an update today the Gnome version is " Desktop: Gnome 3.36.3". I have
made a couple of suspends and there is no crash..

Den fre 19 juni 2020 kl 12:30 skrev Marco Trevisan (Treviño) <
1877...@bugs.launchpad.net>:

> > I'm now using the development version of 20.04.1. Will this fix be
> included?
>
> What do you mean by that? Are you using groovy?
>
> However, to check, just look what version of gnome-shell you're running via
>  - apt-cache policy gnome-shell
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal

[Per-Inge]

I'm now using the development version of 20.04.1. Will this fix be
included?

Den fre 19 juni 2020 kl 07:55 skrev Timo Aaltonen <
1877...@bugs.launchpad.net>:

> Hello Per-Inge, or anyone else affected,
>
> Accepted gnome-shell into focal-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/gnome-
> shell/3.36.3-1ubuntu1~20.04.2 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: gnome-shell (Ubuntu Focal)
>Status: Fix Released => Fix Committed
>
> ** Tags added: verification-needed verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1877760
>
> Title:
>   gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
>   g_str_has_prefix() from _st_theme_node_ensure_background() from
>   st_theme_node_paint_equal
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   GNOME shell crashes on extensions loading / updates
>
>   [ Test case ]
>- No clear test case, normally may happen during screen
> locking/unlocking
>- But crashes should be monitored at
>
> https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3
>
>   [ Regression potential ]
>
>   Stylesheet memory could be leaked
>
>   ---
>
>   Started the computer from suspend. Started Gmail from Dash to Panel.
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 18:30:48 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu
> (%rdi),%ymm1
>PC (0x7fe9fdcc3e41) ok
>source "(%rdi)" (0xf0250) not located in a known VMA region (needed
> readable region)!
>destination "%ymm1" ok
>   SegvReason: reading unknown VMA
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101
>g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in __strncmp_avx2() from
  g_str_has_prefix() from _st_theme_node_ensure_background() from
  st_theme_node_paint_equal

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

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

[Bug 1856708] Re: Clipboard usability issues

[Per Bergstrand]

I'm on Ubuntu 20.04 and it affects me. Definately occured for me on
19.10 as well. For example when running Notepad++ I very often have to
click ctrl+c more than once, in order to get it to the buffer available
for pasting. Applies to ctrl+x as well.

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

Title:
  Clipboard usability issues

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

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

[Bug 1880447] [NEW] Crash (segmentaion fault) when opening pcbnew

[Per Ekelund]

Public bug reported:

After upgrading to Ubuntu 20.04 Kicads pcbnew can not be started.

It crashes with "segmentation fault" as the only information.

No problem before 20.04 upgrade.

Please advise and let me know if i can debug somehow.

Thanks

** Affects: kicad (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/1880447

Title:
  Crash (segmentaion fault) when opening pcbnew

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

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

Re: [Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

[Per-Inge]

Started Groovy Gorilla today and update. Suspend don't crash gnome-shell.
Perhaps "gnome-shell-extension-desktop-icons:amd64 (20.04.0-1, 20.04.0-2)"
fixed the problem.

Den ons 20 maj 2020 kl 19:30 skrev Per-Inge
<1877...@bugs.launchpad.net>:

> Used apport-cli to report and that worked. Marked the report as bug
> 184.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/184
>
> Title:
>   gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
>   when using dash-to-panel
>
> Status in GNOME Shell:
>   Unknown
> Status in Gnome Shell Extension Dash To Panel:
>   Fix Released
> Status in gnome-shell package in Ubuntu:
>   Fix Committed
>
> Bug description:
>   Seems to be reproducible
>   Suspend the computer
>   Start the computer from suspend
>   Start chrome gmail.
>   Has happened two times
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 20.10
>   Package: gnome-shell 3.36.2-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
>   Uname: Linux 5.4.0-28-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu33
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May  9 20:00:47 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-04-16 (23 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64
> (20200415.2)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1
>   SegvAnalysis:
>Segfault happened at: 0x7fe1b40c4252
> <_st_theme_node_ensure_background+226>: mov(%rax),%r12
>PC (0x7fe1b40c4252) ok
>source "(%rax)" (0x) not located in a known VMA region (needed
> readable region)!
>destination "%r12" ok
>   SegvReason: reading NULL VMA
>   Signal: 11
>   SourcePackage: gnome-shell
>   StacktraceTop:
>_st_theme_node_ensure_background () from /usr/lib/gnome-shell/
> libst-1.0.so
>st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>st_widget_style_changed () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>   Title: gnome-shell crashed with SIGSEGV in
> _st_theme_node_ensure_background()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  when using dash-to-panel

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

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

[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() when using dash-to-panel

[Per-Inge]

Used apport-cli to report and that worked. Marked the report as bug
184.

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

Title:
  gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
  when using dash-to-panel

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

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

Re: [Bug 1879043] Re: gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

[Per-Inge]

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

OK,
when I send the crash report launchpad isn't opened. Might be because the
crash file _usr_bin_gnome.shell.1000.crash is 45 MB, the
file  _usr_bin_gnome.shell.1000.upload is 0 bytes and
the _usr_bin_gnome.shell.1000.uploaded is only 37 bytes.

Den mån 18 maj 2020 kl 08:55 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:

> *** This bug is a duplicate of bug 184 ***
> https://bugs.launchpad.net/bugs/184
>
> Without more information we will assume this is bug 184.
>
> In future please follow these steps to report crashes:
>
>
> https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
>
> ** This bug has been marked a duplicate of bug 184
>gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background()
> when using dash-to-panel
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1879043
>
> Title:
>   gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()
>
> Status in gnome-shell package in Ubuntu:
>   New
>
> Bug description:
>   It might be bug 184.
>   This is a new installation. During the installation After each change I
> made Suspend and restarted the computer and checked if gnome-shell had
> crashed.
>   Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab,
> Applications Menu, OpenWeather and Dash to Panel without crash.
>   The last thing I did before the crash was to "install" Gmail and Google
> Calender and put all my favorite applications in the panel. Left the
> computer to suspend, after 15 minutes, and restarted the computer.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
>   Uname: Linux 5.4.0-31-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat May 16 11:11:09 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-05-16 (0 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64
> (20200423)
>   RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

[Per-Inge]

I reinstalled and got a crash after suspend. It might be bug 184, but I
made a new one.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879043

Den fre 15 maj 2020 kl 22:41 skrev Marco Trevisan (Treviño) :

> No error reported for the SRU or groovy version for this crash at
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
> ** Tags removed: verification-needed verification-needed-focal
> ** Tags added: verification-done verification-done-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
  from _st_set_text_from_style()

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

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

[Bug 1879043] [NEW] gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

[Per-Inge]

Public bug reported:

It might be bug 184.
This is a new installation. During the installation After each change I made 
Suspend and restarted the computer and checked if gnome-shell had crashed.
Installed: Printer, Flatpaks, Sensory Perceptions, AlternateTab, Applications 
Menu, OpenWeather and Dash to Panel without crash.
The last thing I did before the crash was to "install" Gmail and Google 
Calender and put all my favorite applications in the panel. Left the computer 
to suspend, after 15 minutes, and restarted the computer.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat May 16 11:11:09 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal package-from-proposed

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

Title:
  gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()

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

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

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

[Per-Inge]

I don't know if this is related. It seems I always get a crash either when I 
start suspend or when I return from suspend. When I send the crash report 
launchpad don't open. The crash is in gnome-shell and the crash message is 
"gnome-shell crashed with SIGSEGV in_st_theme_node_ensure_background()".
It might be related to my installation and I will reinstall Focal later today.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

[Per-Inge]

I installed the gnome related components from proposed, but this isn't on a
standard installation I'm using the oibaf ppa (4.6 Mesa 20.2.0-devel
(git-d510974 2020-05-06 focal-oibaf-ppa) and kernel 5.6.7-050607-generic
x86_64. After the update the Gnome desktop is Gnome 3.36.2.
This problem doesn't happen often, but I will use this configuration for
some time. Alternatively I also use a system on other hardware with Groovy
Gorilla. This system don't have any kernel or graphic driver changes.

Den tis 12 maj 2020 kl 22:21 skrev Brian Murray :

> Hello Per-Inge, or anyone else affected,
>
> Accepted gnome-shell into focal-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/gnome-
> shell/3.36.2-1ubuntu1~20.04.1 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> focal to verification-done-focal. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-focal. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: gnome-shell (Ubuntu Focal)
>Status: New => Fix Committed
>
> ** Tags added: verification-needed verification-needed-focal
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   Fix Committed
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
  from _st_set_text_from_style()

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

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

Re: [Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features() from _st_set_text_from_style()

[Per-Inge]

I don't have a standard installation of Ubuntu 20.04 any longer. It's now
updated with kernel 5.6.7-050607-generic x86_64 and I'm also using
the oibaf-ppa.
I tried clicking multiple times in appindicators  in the system tray, but I
didn't get any error.
I run Fedora 32 on this computer too and I think I got this error also on
Fedora 32 before it was upgraded to gnome-shell 3.36.2.
I have these extensions installed: AlternateTab, Dash to Panel, OpenWeather
and Sensory Perception


Den tors 7 maj 2020 kl 18:41 skrev Marco Trevisan (Treviño) :

> ** Description changed:
>
> + [ Impact ]
> +
> + gnome-shell crashes in st_theme_node_get_font_features()
> +
> + [ Test case ]
> +
> + No single reproducer, but try clicking multiple times in appindicators
> + in the system tray
> +
> + [ Regression potential ]
> +
> + Extensions are not correctly styled
> +
> + ---
> +
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
> - ProblemType: Crash
> - DistroRelease: Ubuntu 20.04
> + ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
> - Signal: 11
> - SourcePackage: gnome-shell
> + Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> ** Changed in: gnome-shell (Ubuntu)
>  Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
>
> ** Also affects: gnome-shell (Ubuntu Focal)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1868440
>
> Title:
>   gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
>   from _st_set_text_from_style()
>
> Status in GNOME Shell:
>   Unknown
> Status in gnome-shell package in Ubuntu:
>   Fix Released
> Status in gnome-shell source package in Focal:
>   New
>
> Bug description:
>   [ Impact ]
>
>   gnome-shell crashes in st_theme_node_get_font_features()
>
>   [ Test case ]
>
>   No single reproducer, but try clicking multiple times in appindicators
>   in the system tray
>
>   [ Regression potential ]
>
>   Extensions are not correctly styled
>
>   ---
>
>
> https://errors.ubuntu.com/problem/7235aacf0ac9572c674e49ffcc32ddb01d46a0f0
>
>   ---
>
>   This happened when I closed Chrome and moved the curser to "Power
>   Off/Log Out, Settings .."
>
>   ProblemType: CrashDistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.35.91-1ubuntu2
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Mar 22 11:22:08 2020
>   DisplayManager: gdm3
>   ExecutablePath: /usr/bin/gnome-shell
>   InstallationDate: Installed on 2020-03-15 (6 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200315)
>   ProcCmdline: /usr/bin/gnome-shell
>   RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
>   Signal: 11SourcePackage: gnome-shell
>   StacktraceTop:
>st_theme_node_get_font_features () from /usr/lib/gnome-shell/
> libst-1.0.so
>_st_set_text_from_style () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /usr/lib/gnome-shell/libst-1.0.so
>?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: gnome-shell crashed with SIGSEGV in
> st_theme_node_get_font_features()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1868440/+subscriptions
>


-- 
Skickat från min nya mailadress

-- 
You received 

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

[Per-Inge]

No, I'm not using gTile. To Lock the screen and log in also works OK. My
gnome-shell crashes don't happen that often and I haven't found a way to
reproduce the crash.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

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

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

[Bug 1835660] Re: initramfs unpacking failed

[Per-Inge]

I added the fix in comment #33 on two computers and this fixed the
initramfs problem.

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

Title:
  initramfs unpacking failed

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

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

[Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist()

[Per-Inge]

Thought this was fixed with gnome 3.36, but I got it when I 1:st closed
Gmail and then Chrome.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style()
  from st_texture_cache_load_gicon() from st_icon_update() from
  _g_closure_invoke_va() from g_signal_emit_valist()

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

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

[Bug 1868440] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

[Per-Inge]

Happened again, but now it refers to icon instead of font.

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

Title:
  gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

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

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

[Bug 1863839] [NEW] package systemd 242-7ubuntu3.7 failed to install/upgrade: package systemd is already installed and configured

[Per jørgensen]

Public bug reported:

??

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: systemd 242-7ubuntu3.7
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu28.1
Architecture: amd64
CrashReports:
 640:0:124:339804:2020-02-18 17:41:57.197012662 +0100:2020-02-18 
17:41:58.197012662 +0100:/var/crash/systemd.0.crash
 640:0:124:339806:2020-02-18 17:41:58.189012917 +0100:2020-02-18 
17:41:57.917021388 +0100:/var/crash/mount.0.crash
Date: Tue Feb 18 17:41:58 2020
DpkgTerminalLog:
 dpkg: error processing package mount (--configure):
  package mount is already installed and configured
 dpkg: error processing package systemd (--configure):
  package systemd is already installed and configured
ErrorMessage: package systemd is already installed and configured
InstallationDate: Installed on 2020-02-17 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=dd4941a4-3783-4690-a72c-f17108ee5787 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: dpkg
SystemdDelta:
 [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
Title: package systemd 242-7ubuntu3.7 failed to install/upgrade: package 
systemd is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: already-installed amd64 apport-package eoan

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

Title:
  package systemd 242-7ubuntu3.7 failed to install/upgrade: package
  systemd is already installed and configured

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

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

Re: [Bug 1862792] Re: gnome-shell always crash after boot

[Per-Inge]

This is the result:

Error reports sent from this system
Occurred Received Problem Type Program
2020-02-11 19:02 2020-02-11 18:02 UTC Crash gnome-shell
2020-02-11 06:02 2020-02-11 05:02 UTC Crash gnome-shell
2020-02-10 11:02 2020-02-10 11:02 UTC Crash gnome-shell
2020-02-09 12:02 2020-02-09 12:02 UTC Crash gnome-shell
2020-02-08 09:02 2020-02-08 08:02 UTC Crash gnome-shell
2020-02-03 17:02 2020-02-03 16:02 UTC Crash /usr/lib/xorg/Xorg
2020-02-03 07:02 2020-02-03 07:02 UTC Crash /usr/lib/xorg/Xorg
2020-01-24 15:01 2020-01-24 14:01 UTC Crash google-chrome-stable
2020-01-17 21:01 2020-01-17 20:01 UTC Crash gnome-shell
2020-01-13 18:01 2020-01-13 17:01 UTC Crash cups-browsed
2019-12-30 21:12 2019-12-30 20:12 UTC Crash google-chrome-stable
2019-12-27 19:12 2019-12-27 18:12 UTC Crash google-chrome-stable
2019-12-27 12:12 2019-12-27 13:12 UTC Crash cups-browsed

These are the links:
https://errors.ubuntu.com/oops/31013d32-4cfd-11ea-a96b-fa163e983629
https://errors.ubuntu.com/oops/8269e776-4c91-11ea-a07a-fa163e6cac46
https://errors.ubuntu.com/oops/e4e4e6ec-4bfa-11ea-a95c-fa163e983629
https://errors.ubuntu.com/oops/5f9cd9b2-4b3b-11ea-a957-fa163e983629
https://errors.ubuntu.com/oops/650b32dc-4a4e-11ea-a953-fa163e983629
https://errors.ubuntu.com/oops/234b0822-46a3-11ea-aa47-fa163e6cac46
https://errors.ubuntu.com/oops/b2bebda8-4655-11ea-b902-fa163e102db1
https://errors.ubuntu.com/oops/65f83450-3eb8-11ea-a7c8-fa163ee63de6
https://errors.ubuntu.com/oops/a46d4394-3966-11ea-b219-fa163e983629
https://errors.ubuntu.com/oops/cb2e2fc2-3626-11ea-b89d-fa163e102db1
https://errors.ubuntu.com/oops/e2494484-2b44-11ea-a75f-fa163ee63de6
https://errors.ubuntu.com/oops/b45882ec-28d8-11ea-b84d-fa163e102db1
https://errors.ubuntu.com/oops/70a7627c-28b0-11ea-b1c1-fa163e983629

Den ons 12 feb. 2020 kl 03:20 skrev Daniel van Vugt <
daniel.van.v...@canonical.com>:

> It sounds like the main issue is that Xwayland has crashed first:
>
> [   31.095070] pi-asus-b450f-gaming gnome-shell[1400]: Connection to
> xwayland lost
>
> Please follow the steps in comment #2 to help us diagnose the problem
> further.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1862792
>
> Title:
>   gnome-shell always crash after boot
>
> Status in gnome-shell package in Ubuntu:
>   Incomplete
>
> Bug description:
>   gnome-shell always crash after boot with an UnreportableReason. This is
> in a Wayland session.
>   There are no stability issues after boot.
>
>   I get this information in the terminal after the command ubuntu-bug
>
>   p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
>   p-i@pi-asus-b450f-gaming:~$
> [8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID
> data: manufacturer id
>   [8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)]
> InitializeSandbox() called with multiple threads in process gpu-process.
>
> [8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)]
> GetVSyncParametersIfAvailable() failed for 1 times!
>
>   ERROR:gl goes from 1 to 19.
>
>   In Settings the Display is named Microstep 27"
>   The problem might be hardware related:
>   Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
>   GPU: AMD Navi 10 Radeon RX 5700
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: gnome-shell 3.34.3-1ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
>   Uname: Linux 5.4.0-12-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu16
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Feb 11 16:43:08 2020
>   DisplayManager: gdm3
>   InstallationDate: Installed on 2020-02-08 (3 days ago)
>   InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64
> (20200207.2)
>   RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862792/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  gnome-shell always crash after boot

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

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

[Bug 1862792] [NEW] gnome-shell always crash after boot

[Per-Inge]

Public bug reported:

gnome-shell always crash after boot with an UnreportableReason. This is in a 
Wayland session. 
There are no stability issues after boot. 

I get this information in the terminal after the command ubuntu-bug

p-i@pi-asus-b450f-gaming:~$ ubuntu-bug gnome-shell
p-i@pi-asus-b450f-gaming:~$ 
[8196:8196:0211/164342.764494:ERROR:edid_parser.cc(102)] Too short EDID data: 
manufacturer id
[8232:8232:0211/164342.881085:ERROR:sandbox_linux.cc(374)] InitializeSandbox() 
called with multiple threads in process gpu-process.
[8232:8232:0211/164344.007722:ERROR:gl_surface_presentation_helper.cc(259)] 
GetVSyncParametersIfAvailable() failed for 1 times!

ERROR:gl goes from 1 to 19.

In Settings the Display is named Microstep 27"
The problem might be hardware related:
Mobo: ASUSTeK model: ROG STRIX B450-F GAMING
GPU: AMD Navi 10 Radeon RX 5700

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 16:43:08 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-02-08 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200207.2)
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Title:
  gnome-shell always crash after boot

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

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

[Bug 1835660] Re: initramfs unpacking failed

[Per-Inge]

I get different behavior depending on how I boot the computer using the BIOS 
boot menu
- When I select sda with Ubuntu 20.04, I don't get the error message
- When I select sdc with Fedora 31 and select Ubuntu from Fedora's boot menu I 
get the 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/1835660

Title:
  initramfs unpacking failed

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

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

[Bug 1835660] Re: initramfs unpacking failed

[Per-Inge]

Added Fedora 31 and made a triple boot system with Ubuntu 20.04, Windows 10 and 
Fedora 31.
Fedora stored the boot record in /dev/sdc1 and I had to change boot disk to sdc 
in BIOS.
Fedora provides a boot menu with
Fedora
Ubuntu
Windows
When I start Ubuntu via the Fedora boot menu I get this 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/1835660

Title:
  initramfs unpacking failed

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

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

[Bug 1848771] Re: Reboot after resume from suspend (deep)

[Per-Inge]

I don't know if this is related but it fixed my problem with wake up from 
suspend.
This is on a desktop with an Asus Rog Strix B450-F Gaming motherboard and Focal 
Fossa.

I have changed these settings in BIOS
- Used DOCP settings on the memory
- USB power delivery in SoftOff is set to Disable
- PSS support is set to enable
- Serial Port is set to OFF
In AMD CBS
- IOMMU is set to Disabled
- Global C-state control is set to enable
- Power Supply Idle Control is set to Low Current Idle

I think the most important setting is to disable IOMMU. Instead I have
added "iommu=soft" in GRUB_CMDLINE_LINUX="" in /etc/default/grub

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

Title:
  Reboot after resume from suspend (deep)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions

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

[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise

[Per-Inge]

On computers with HDA or SDA drives it is possible to disconnect all drives 
except the installation drive to install grub on the wanted drive.
This is however not a practical solution with NVme drives.
As I want to use the development version of Ubuntu early this is normally the 
last installation and will provide the used grub. To have to use grub of the 
development version gives a high risk to crash the whole computer.
I suppose this also is the case when you want to use IOS, Fedora or Windows as 
your "master" version in a computer and clearly separate the different 
installations.

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

Title:
  installer uses first EFI system partition found even when directed
  otherwise

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

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

[Bug 1849426] Re: Daily Limit Exceeded error for Google calendar

[Per Hertz]

Seems like a Mee2 thing... :-D

/Per

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

Title:
  Daily Limit Exceeded error for Google calendar

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

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

[Bug 1846318] [NEW] Placement set to Left

[Per-Inge]

Public bug reported:

When Placement in Windows Titlebars is set to Left, gnome-tweaks opens in a too 
small window and the menu to select view isn't shown.
Test case:
Set placement to Left
Open gnome-tweaks
Enlarge the window and the menu is shown.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-tweaks 3.34.0-2
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  2 11:53:07 2019
InstallationDate: Installed on 2019-08-02 (60 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
PackageArchitecture: all
SourcePackage: gnome-tweaks
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Placement set to Left

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

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

[Bug 1845248] Re: Security fixes and bugs from latest stable release requested

[Per Christian Henden]

** Information type changed from Private Security to Public Security

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-16239

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

Title:
  Security fixes and bugs from latest stable release requested

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

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

Re: [Bug 1842022] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

[Per-Inge]

I haven't seen this bug for some time and the test case: log in, start
Gnome Gmail open a mail and click a link that opens Chrome works fine.
This is on ibus 1.5.19-4ubuntu2.

Den tis 17 sep. 2019 kl 21:50 skrev Gunnar Hjalmarsson <
1842...@bugs.launchpad.net>:

> IBus has just been updated in eoan. Can those of you who were hit by
> crashes please upgrade to ibus 1.5.21-1~exp2ubuntu1 and let us know if
> you notice any difference.
>
> ** Information type changed from Private to Public
>
> ** Changed in: ibus (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1842022
>
> Title:
>   ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Didn't do anything special. Logged out and checked if "Ubuntu" or
>   Ubuntu on Wayland" was set and "Ubuntu" was set.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.10
>   Package: ibus 1.5.19-4ubuntu2
>   ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
>   Uname: Linux 5.2.0-15-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Aug 30 08:47:18 2019
>   ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
>   InstallationDate: Installed on 2019-08-02 (27 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
>   ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
>   SegvAnalysis:
>Segfault happened at: 0x7fd6131738ce <__vfprintf_internal+30>:
>  mov%rsi,-0x4b8(%rbp)
>PC (0x7fd6131738ce) ok
>source "%rsi" ok
>destination "-0x4b8(%rbp)" (0x7ffdb5e52bf8) not located in a known VMA
> region (needed writable region)!
>Stack memory exhausted (SP below stack segment)
>   SegvReason: writing unknown VMA
>   Signal: 11
>   SourcePackage: ibus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
>ibus_bus_get_engines_by_names () from
> /lib/x86_64-linux-gnu/libibus-1.0.so.5
>?? ()
>?? ()
>g_cclosure_marshal_VOID__STRINGv () from
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: ibus-ui-gtk3 crashed with SIGSEGV in
> ibus_bus_get_engines_by_names()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1842022/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

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

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

Re: [Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Per-Inge]

Test case
Start Text Editor, Minimize and right click Text Editor in the Dock works
fine.

Den mån 16 sep. 2019 kl 17:50 skrev Launchpad Bug Tracker <
1843...@bugs.launchpad.net>:

> This bug was fixed in the package gnome-shell-extension-ubuntu-dock -
> 66ubuntu19.10.2
>
> ---
> gnome-shell-extension-ubuntu-dock (66ubuntu19.10.2) eoan; urgency=medium
>
>   [ Marco Trevisan (Treviño) ]
>   * windowPreview: Use the window actor as Clone source (LP: #1843520)
>   * appIcons: Don't warn if variable is undefined
>   * appIcons: Enable scroll handler if enabled on construction
>   * docking: Don't warn if variable is undefined
>   * ubuntu-gschema.override: Enable fixed transparency with opacity at 70%
>
>  -- Marco Trevisan (Treviño)   Mon, 16 Sep 2019
> 14:28:09 +0200
>
> ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
>Status: In Progress => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1843520
>
> Title:
>   ubuntu-dock right-click menu appears at the top-left corner of the
>   desktop (which in some cases is the wrong monitor) and is permanent
>
> Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
>   Fix Released
>
> Bug description:
>   Very recently the ubuntu-dock has started displaying some right-click
>   menus for pinned apps on the wrong monitor. It doesn't happen for all
>   the apps, but when it does, the menu is permanent but you can't click
>   on it and you have to restart gnome-shell with ALT-F2 'r' (which now
>   always kills some apps like firefox).
>
>   See attached screenshot where the menu for gnome-tweaks has appeared
>   at the top left of the top monitor.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell-extension-ubuntu-dock 66ubuntu19.10.1
>   Uname: Linux 5.3.0-050300rc8-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep 11 11:42:07 2019
>   InstallationDate: Installed on 2019-07-01 (71 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
>   PackageArchitecture: all
>   SourcePackage: gnome-shell-extension-ubuntu-dock
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1843520/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1799081] Re: Unable to cut+paste using PCManFM in Ubuntu 18.04 LTS

[Per Stenebo]

This describes my problem too (since some time).
Cut and past don't work in PCManFM 1.2.5, but works on the very same file in 
the default file manager Filer 3.26.4. 
That should rule out other stuff I think.

lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

Same result in standard "Ubuntu" session as in "GNOME Flashback (Metacity)" 
(gnome-session-flashback).
/Per

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

Title:
  Unable to cut+paste using PCManFM in Ubuntu 18.04 LTS

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

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

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Per-Inge]

One more problem.
After Log Out and Log In, Windows Titlebars are move from Left to Right. It is 
not possible to change them back to Left in Tweaks.

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1843520] Re: ubuntu-dock right-click menu appears at the top-left corner of the desktop (which in some cases is the wrong monitor) and is permanent

[Per-Inge]

This also happens in this usecase.
Open an application for example text editor
Minimize the application
Right click the application in Ubuntu Dock

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

Title:
  ubuntu-dock right-click menu appears at the top-left corner of the
  desktop (which in some cases is the wrong monitor) and is permanent

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

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

[Bug 1768177] Re: "Missing host" for 1&1 sftp access. Address is correct and ssh connects but sshfs does not

[Per Stenebo]

On a clean Ubuntu 18.04.2 I needed to add remote path after host (:/) to
get rid of the problem, like "sshfs remotehost:/ ~/my/mountpoint".

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

Title:
  "Missing host" for 1&1 sftp access. Address is correct and ssh
  connects but sshfs does not

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1768177/+subscriptions

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

[Bug 1834957] [NEW] Automatic generated printer in CUPS

[Per-Inge]

Public bug reported:

The automatic generated printer don't work. It is possible to use Settings and 
add the printer.
It is possible to delete the faulty printer in Setting, but every time the 
printer is turned on the faulty printer is generated again.
It is also possible to use Settings to block the printer, but after login the 
printer is activated again.
There is also notifications about the printout until the printout is canceled.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.10-6ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
Uname: Linux 5.0.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  1 19:23:17 2019
InstallationDate: Installed on 2019-07-01 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190701)
Lpstat: device for Brother_HL_3140CW_series: 
implicitclass://Brother_HL_3140CW_series/
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Brother_HL_3140CW_series.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Brother_HL_3140CW_series.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-17-generic 
root=UUID=27f650c7-e62f-48f9-acce-c3c8e92f109e ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug eoan

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

Title:
  Automatic generated printer in CUPS

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

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

[Bug 1809936] Re: Installing GNOME shell extensions

[Per-Inge]

In a new installation of EOAN it's not possible to install gnome extensions in 
Chromium.
You get this error message
"Although GNOME Shell integration extension is running, native host connector 
is not detected." Refer documentation for instructions about installing 
connector."
The method advised in the instruction "GNOME Shell integration for Chrome 
Installation Guide"
$ sudo apt-get install chrome-gnome-shell
isn't working.

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

Title:
  Installing GNOME shell extensions

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

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

Re: [Bug 1821435] [NEW] nautilus crashed with SIGABRT in g_assertion_message()

[Per-Inge]

I set the developer option and updated. Got the nautilus update among other
updates.
Copied a file from the server to Documents and starred the file. Worked OK
and got no crash.
Copied another file from the server to Documents and starred it. Got no
crash, but the file didn't show up in Starred.
Restarted Nautilus, but this didn't help.
Logged out and logged in again. Open Documents and starred the file again.
This time the file showed up in Starred.

Did the same in Eoan with the same result.


Den lör 23 mars 2019 kl 08:15 skrev Per-Inge :

> Private bug reported:
>
> Copied a file from a server to ~/Documents and used the Star function.
> Got this crash two times with different files.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 19.04
> Package: nautilus 1:3.32.0-0ubuntu1
> ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
> Uname: Linux 5.0.0-8-generic x86_64
> ApportVersion: 2.20.10-0ubuntu23
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Sat Mar 23 07:53:09 2019
> ExecutablePath: /usr/bin/nautilus
> InstallationDate: Installed on 2018-11-24 (118 days ago)
> InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
> ProcCmdline: /usr/bin/nautilus --gapplication-service
> Signal: 6
> SourcePackage: nautilus
> StacktraceTop:
>  ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>  g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>  nautilus_window_slot_get_location ()
>  ?? ()
>  g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
> separator:
>
> usr_lib_nautilus:
>
> ** Affects: nautilus (Ubuntu)
>  Importance: Medium
>  Status: New
>
>
> ** Tags: amd64 apport-crash disco third-party-packages
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821435
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in nautilus package in Ubuntu:
>   New
>
> Bug description:
>   Copied a file from a server to ~/Documents and used the Star function.
>   Got this crash two times with different files.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.04
>   Package: nautilus 1:3.32.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
>   Uname: Linux 5.0.0-8-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu23
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 23 07:53:09 2019
>   ExecutablePath: /usr/bin/nautilus
>   InstallationDate: Installed on 2018-11-24 (118 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>nautilus_window_slot_get_location ()
>?? ()
>g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1821435/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

Re: [Bug 1821435] Re: nautilus crashed with SIGABRT in g_assertion_message()

[Per-Inge]

Will test om thursday

Den mån 20 maj 2019 16:30Łukasz Zemczak <1821...@bugs.launchpad.net>
skrev:

> Hello Per-Inge, or anyone else affected,
>
> Accepted nautilus into disco-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/nautilus/1:3.32.1-0ubuntu0.19.04.0
> in a few hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-disco to verification-done-disco. If it does not fix
> the bug for you, please add a comment stating that, and change the tag
> to verification-failed-disco. In either case, without details of your
> testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> ** Changed in: nautilus (Ubuntu Disco)
>Status: New => Fix Committed
>
> ** Tags added: verification-needed verification-needed-disco
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821435
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in Nautilus:
>   Fix Released
> Status in nautilus package in Ubuntu:
>   Fix Released
> Status in nautilus source package in Disco:
>   Fix Committed
>
> Bug description:
>   Copied a file from a server to ~/Documents and used the Star function.
>   Got this crash two times with different files.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 19.04
>   Package: nautilus 1:3.32.0-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
>   Uname: Linux 5.0.0-8-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu23
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 23 07:53:09 2019
>   ExecutablePath: /usr/bin/nautilus
>   InstallationDate: Installed on 2018-11-24 (118 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181124)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>nautilus_window_slot_get_location ()
>?? ()
>g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nautilus/+bug/1821435/+subscriptions
>

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

There's no image that contain the latest image as far as I know.
You can always install an older image like 18.04.1 and then upgrade it.
http://old-releases.ubuntu.com/releases/bionic/

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

Guess so.
Your screenshot shows kernal 4.15.0.45 which is affected by this bug.

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1824572] [NEW] package libpam-runtime 1.1.8-3.2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Per-Erik Feltenmark]

Public bug reported:

Automatic update to Ubuntu 18.0.4 crash, I don't know why

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-runtime 1.1.8-3.2ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Apr 11 22:32:57 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2019-04-11 (1 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: pam
Title: package libpam-runtime 1.1.8-3.2ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: Upgraded to xenial on 2019-04-12 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpam-runtime 1.1.8-3.2ubuntu2.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

I have also installed linux-image-4.15.0-48-generic/bionic-proposed and
it's working fine for me as well.

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1631514] Re: snap doesnt work. error: cannot communicate with server

[Per]

I experienced that problem with a fresh installation of Ubuntu Core for
RasbperryPI 3 using the official instructions:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3

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

Title:
  snap doesnt work. error: cannot communicate with server

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

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

[Bug 1723760] Re: No restart after installation

[Per-Inge]

I haven't seen this when I have followed the 18.10 and 19.04
development.

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

Title:
  No restart after installation

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

https://people.canonical.com/~khfeng/lp1814069-2/ is working for me. I haven't 
done any extensive testing but the server can boot and has network access.
Attaching dmesg output from successful boot if that's relevant

BR Per

** Attachment added: "dmesg_4.15.0-47.50"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5246012/+files/dmesg_4.15.0-47.50

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

Attached is the dmesg output from a modprobe using the ordinary kernel
4.15.0-46

** Attachment added: "dmesg_4.15.0-46.49"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5245801/+files/dmesg_4.15.0-46.49

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

Here's a log from a boot using your kernal at 
https://people.canonical.com/~khfeng/lp1814069/
Kernel parameters are as you requested and a modprobe hv_netvsc after boot.

I'm not sure exactly how to retrieve dmesg properly nowadays but I used
journalctl -k -b -2 to retrieve the kernel messages for the boot we're
interested in. If you need more detailed info give me a hint on how to
retrieve it.

** Attachment added: "kernel messages from modprobe in 4.15.0-46"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814069/+attachment/5245537/+files/dmesg

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

[Per Bengtsson]

I tried that kernel but it didn't seem to make any difference.
Version 4.15.0-46 from the repository was already installed so I had to 
uninstall that one first.

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

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

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

[Bug 1242367] Re: gnome-control-center user-accounts don't load, only hangs

[Per Vapp]

I have new hardware and cannot test it.

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

Title:
  gnome-control-center user-accounts don't load, only hangs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1242367/+subscriptions

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

[Bug 1814393] Re: "make: write error: stdout" on parallel builds

[Per Gregers Bilse]

I can confirm this.  I noticed after the upgrade from 4.15.0-43-generic,
but at first wasn't sure if I had messed up my build; I downgraded to 43
and forgot about it until the system upgraded again yesterday.  I'm now
on 45, and my build fails as before, an excerpt:

/bin/sh: line 0: echo: write error: Resource temporarily unavailable
mv ../../bcmdrivers/broadcom/char/pktflow/bcm963138/fcache.o_tmp 
../../bcmdrivers/broadcom/char/pktflow/bcm963138/fcache.o
/bin/sh: line 0: echo: write error: Resource temporarily unavailable
scripts/Makefile.build:258: recipe for target 
'/home/bilse/bcm_50203/bcmdrivers/broadcom/char/adsl/bcm963138/BcmAdslCore.o' 
failed
make[4]: *** 
[/home/bilse/bcm_50203/bcmdrivers/broadcom/char/adsl/bcm963138/BcmAdslCore.o] 
Error 1
make[4]: *** Waiting for unfinished jobs
[...]
make[4]: write error: stdout
scripts/Makefile.build:423: recipe for target 
'../../bcmdrivers/broadcom/char/pktflow/bcm963138' failed
make[3]: *** [../../bcmdrivers/broadcom/char/pktflow/bcm963138] Error 1
scripts/Makefile.build:423: recipe for target 
'../../bcmdrivers/broadcom/char/adsl/bcm963138' failed
make[3]: *** [../../bcmdrivers/broadcom/char/adsl/bcm963138] Error 2
make[3]: write error: stdout
Makefile:1201: recipe for target '../../bcmdrivers' failed
make[2]: *** [../../bcmdrivers] Error 1
make[2]: *** wait: No child processes. Stop.
make[2]: write error: stdout
Makefile:476: recipe for target 'inner_kernelbuild' failed
make[1]: *** [inner_kernelbuild] Error 1
make[1]: Leaving directory '/home/bilse/bcm_50203'
Makefile:473: recipe for target 'kernelbuild' failed
make: *** [kernelbuild] Error 2
bilse@ub40:~/bcm_50203$ uname -a
Linux ub40 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 29 18:03:48 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux
bilse@ub40:~/bcm_50203$

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

Title:
  "make: write error: stdout" on parallel builds

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

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

[Bug 1815577] [NEW] Incorrect decoding of PDF v1.7 document

[Per Olav Kroka]

Public bug reported:

The file at 
("The Norwegian Directorate for Civil Protection") presents garbled
text.  Libre Office seems to decode the text correctly.  I guess this is
a font issue (incorrect font) as if copied and pasted the text comes out
correctly:

"Dokumentasjon av det elektriske anlegget
Erklæring om samsvar i henhold til forskrift om elektriske lavspenningsanlegg"

Version: GNOME Document Viewer 3.28.4

** Affects: evince-hwp (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot from evince showing the referenced document"
   
https://bugs.launchpad.net/bugs/1815577/+attachment/5237948/+files/Screenshot%20from%202019-02-12%2011-25-26.png

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

Title:
  Incorrect decoding of PDF v1.7 document

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince-hwp/+bug/1815577/+subscriptions

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

Re: [Bug 1793249] Re: nautilus crashed with SIGABRT in g_assertion_message()

[Per-Inge]

I don't get that crash any longer.
I'm using Nautilus 3.26.4.

Den tis 15 jan. 2019 kl 18:35 skrev Sebastien Bacher
:

> The error tracker has a few report for that issue on
> https://errors.ubuntu.com/problem/82ca773a06c225419be734599e500c5f4b2100ac
>
> ** Information type changed from Private to Public
>
> ** Changed in: nautilus (Ubuntu)
>Importance: Medium => Low
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1793249
>
> Title:
>   nautilus crashed with SIGABRT in g_assertion_message()
>
> Status in nautilus package in Ubuntu:
>   Confirmed
>
> Bug description:
>   This is a second crash when I searched for it87. Nautilus crashed after
> typing "i".
>   Related to bug report 1793248. Before I rebooted.
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 18.10
>   Package: nautilus 1:3.26.4-0ubuntu3
>   ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
>   Uname: Linux 4.18.0-7-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu11
>   Architecture: amd64
>   CrashCounter: 1
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Sep 19 06:49:11 2018
>   ExecutablePath: /usr/bin/nautilus
>   GsettingsChanges:
>b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'"
>b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
>b'org.gnome.nautilus.window-state' b'sidebar-width' b'222'
>b'org.gnome.nautilus.window-state' b'geometry' b"'1108x849+1308+138'"
>b'org.gnome.nautilus.list-view' b'default-column-order' b"['name',
> 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where',
> 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']"
>   InstallationDate: Installed on 2018-08-09 (40 days ago)
>   InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64
> (20180809)
>   ProcCmdline: /usr/bin/nautilus --gapplication-service
>   Signal: 6
>   SourcePackage: nautilus
>   StacktraceTop:
>?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>?? ()
>?? ()
>?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>   Title: nautilus crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   usr_lib_nautilus:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1793249/+subscriptions
>


-- 
Skickat från min nya mailadress

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

Title:
  nautilus crashed with SIGABRT in g_assertion_message()

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

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

[Bug 1666570] Re: Post install script has error in RegEx

[Per Lundberg]

One way to work around this until the package gets fixed in xenial is to
escape the % sign in the JAVA_OPTS string:

JAVA_OPTS="${JAVA_OPTS} -Xloggc:/var/log/tomcat7/gc-\%t.log"

This has been tested and seems to make both the postinst script work, as
well as make the JVM include the timestamp in the GC log file at
runtime.

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

Title:
  Post install script has error in RegEx

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

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

[Bug 1666570] Re: Post install script has error in RegEx

[Per Lundberg]

Note: as implied by Mathew Hodson, the tomcat7 package for Xenial has
_not_ yet been updated (because the package failed to build.)

(We started seeing this bug appearing on some servers after upgrading to
tomcat7, so I can personally verify that it's still present with
7.0.68-1ubuntu0.4.)

It would be great if the tomcat7 package could be fixed, because right
now it's uninstallable under certain scenarios.

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

Title:
  Post install script has error in RegEx

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

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

Re: [Bug 1804951] Re: An Icon called kmines is still in the program menu after uninstalling the game

[Per Ole Tetli]

Hi,

I use the standard Gnome shell


Per Ole

> 25. nov. 2018 kl. 17:41 skrev Adolfo Jayme :
> 
> What DE do you use?
> 
> ** Changed in: kmines (Ubuntu)
>   Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1804951
> 
> Title:
>  An Icon called kmines is still in the program menu after uninstalling
>  the game
> 
> Status in kmines package in Ubuntu:
>  Incomplete
> 
> Bug description:
>  I have uninstalled kmines but an icon with that name is still there.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 18.04
>  Package: kmines (not installed)
>  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>  Uname: Linux 4.15.0-39-generic x86_64
>  ApportVersion: 2.20.9-0ubuntu7.5
>  Architecture: amd64
>  CurrentDesktop: ubuntu:GNOME
>  Date: Sat Nov 24 17:23:26 2018
>  InstallationDate: Installed on 2018-11-10 (13 days ago)
>  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
> (20180725)
>  SourcePackage: kmines
>  UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/kmines/+bug/1804951/+subscriptions
>

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

Title:
  An Icon called kmines is still in the program menu after uninstalling
  the game

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

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