[Desktop-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes

[Juerg Haefliger]

17.04 is EOL. Please open a new bug report if you still encounter the
same issue.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Intel Wireless 7260 often crashes

Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS 
enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses 
Intel 7260 wifi, rev. bb:
  01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently,
  everything (kernel, firmware, etc.) is stock. Issue has persisted
  across multiple installations.

  Bug: Wifi/Bluetooth crashes and refuses to come back up, even after
  multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.)

  When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, 
upon boot, it is not uncommon for the wireless to stop working within two 
minutes of login time. Curiously, the GUI usually still shows being 
"connected", though trying to change anything with the wifi shows otherwise. 
Other times, upon system resume when wireless was previously working, the GUI 
will show "device not ready" and refuse to continue. Dmesg shows the following:
  [  423.814823] Bluetooth: hci0 command 0x1403 tx timeout
  [  424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  424.173067] iwlwifi :01:00.0: Scan failed! ret -5
  [  425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd
  [  425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: 
enqueue_hcmd failed: -5
  [  425.194593] iwlwifi :01:00.0: Scan failed! ret -5

  Solution: Rebooting doesn't fix the problem. Perhaps a different
  firmware version will work better? Configuration settings? etc.?
  Unknown.

  Thanks ahead of time for the help. Let me know if there's anything you
  need/commands I should run/solutions I can attempt.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bmueller   1669 F pulseaudio
  CurrentDesktop: MATE
  Date: Wed Apr 19 10:34:11 2017
  InstallationDate: Installed on 2017-04-13 (6 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp.
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Gnawty
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago)
  dmi.bios.date: 08/16/2015
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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


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

[Desktop-packages] [Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI

[Juerg Haefliger]

** No longer affects: tracker-miners (Ubuntu Noble)

** No longer affects: tracker-miners (Ubuntu Oracular)

** Changed in: tracker-miners (Ubuntu)
   Status: New => Invalid

** Changed in: linux-raspi (Ubuntu Noble)
   Status: New => Confirmed

** Changed in: linux-raspi (Ubuntu Oracular)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/2066885

Title:
  On Pi desktop, numerous reports of lack of landlock supported ABI

Status in linux-raspi package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid
Status in linux-raspi source package in Noble:
  Confirmed
Status in linux-raspi source package in Oracular:
  Confirmed

Bug description:
  [Impact]

  On the Ubuntu noble desktop for Raspberry Pi, the system journal has
  numerous of the following entries:

  May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock 
supported ABI: Operation not supported
  May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data 
since Landlock could not be enabled. Update your kernel to fix this warning.

  These appear to be written every time a file in my home directory is
  modified. The kernel is the stock noble kernel from linux-raspi,
  6.8.0-1004-raspi.

  [Test Case]

  Ubuntu desktop image with tracker-miner should produce any log entries
  like the ones above.

  $ sudo dmesg | grep landl
  [0.002208] LSM: initializing 
lsm=lockdown,capability,landlock,yama,apparmor,ima,evm
  [0.002531] landlock: Up and running.

  
  [Where Problems Could Occur]

  Kernel issues (crashes, stack traces) at boot and/or when userspace
  invokes the LSM ABI.

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


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

[Desktop-packages] [Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI

[Juerg Haefliger]

** Changed in: linux-raspi (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/2066885

Title:
  On Pi desktop, numerous reports of lack of landlock supported ABI

Status in linux-raspi package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  New
Status in linux-raspi source package in Noble:
  New
Status in tracker-miners source package in Noble:
  New
Status in linux-raspi source package in Oracular:
  New
Status in tracker-miners source package in Oracular:
  New

Bug description:
  [Impact]

  On the Ubuntu noble desktop for Raspberry Pi, the system journal has
  numerous of the following entries:

  May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock 
supported ABI: Operation not supported
  May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data 
since Landlock could not be enabled. Update your kernel to fix this warning.

  These appear to be written every time a file in my home directory is
  modified. The kernel is the stock noble kernel from linux-raspi,
  6.8.0-1004-raspi.

  [Test Case]

  Ubuntu desktop image with tracker-miner should produce any log entries
  like the ones above.

  $ sudo dmesg | grep landl
  [0.002208] LSM: initializing 
lsm=lockdown,capability,landlock,yama,apparmor,ima,evm
  [0.002531] landlock: Up and running.

  
  [Where Problems Could Occur]

  Kernel issues (crashes, stack traces) at boot and/or when userspace
  invokes the LSM ABI.

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


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

[Desktop-packages] [Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI

[Juerg Haefliger]

** Description changed:

+ [Impact]
+ 
  On the Ubuntu noble desktop for Raspberry Pi, the system journal has
  numerous of the following entries:
  
  May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock 
supported ABI: Operation not supported
  May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data 
since Landlock could not be enabled. Update your kernel to fix this warning.
  
  These appear to be written every time a file in my home directory is
  modified. The kernel is the stock noble kernel from linux-raspi,
  6.8.0-1004-raspi.
+ 
+ [Test Case]
+ 
+ Ubuntu desktop image with tracker-miner should produce any log entries
+ like the ones above.
+ 
+ [Where Problems Could Occur]
+ 
+ Kernel issues (crashes, stack traces) at boot and/or when userspace
+ invokes the LSM ABI.

** Also affects: tracker-miners (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

** Also affects: tracker-miners (Ubuntu Oracular)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/2066885

Title:
  On Pi desktop, numerous reports of lack of landlock supported ABI

Status in linux-raspi package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  New
Status in linux-raspi source package in Noble:
  New
Status in tracker-miners source package in Noble:
  New
Status in linux-raspi source package in Oracular:
  New
Status in tracker-miners source package in Oracular:
  New

Bug description:
  [Impact]

  On the Ubuntu noble desktop for Raspberry Pi, the system journal has
  numerous of the following entries:

  May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock 
supported ABI: Operation not supported
  May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data 
since Landlock could not be enabled. Update your kernel to fix this warning.

  These appear to be written every time a file in my home directory is
  modified. The kernel is the stock noble kernel from linux-raspi,
  6.8.0-1004-raspi.

  [Test Case]

  Ubuntu desktop image with tracker-miner should produce any log entries
  like the ones above.

  [Where Problems Could Occur]

  Kernel issues (crashes, stack traces) at boot and/or when userspace
  invokes the LSM ABI.

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


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

[Desktop-packages] [Bug 1454450] Re: Bluetooth mouse laggy and erratic

[Juerg Haefliger]

I'm closing this bug due to old age. Please open a new bug if you think
the issue still exists.

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1454450

Title:
  Bluetooth mouse laggy and erratic

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios
  A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves
  erratically (laggy, jumpy). The problem happens after a few (sometimes
  one) suspend and resume. I am attaching below some info on my system.
  Thank you.

  cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep 
-i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth
  Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac 
Wireless Network Adapter [14e4:43b1] (rev 03)
   Subsystem: Dell Device [1028:0019]
   Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8001 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0c45:670c Microdia
  Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
  Bus 001 Device 002: ID 0a5c:216f Broadcom Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [2.174367] Bluetooth: Core ver 2.20
  [2.174669] Bluetooth: HCI device and connection manager initialized
  [2.174792] Bluetooth: HCI socket layer initialized
  [2.174795] Bluetooth: L2CAP socket layer initialized
  [2.175449] Bluetooth: SCO socket layer initialized
  [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [3.542421] Bluetooth: BNEP filters: protocol multicast
  [3.542425] Bluetooth: BNEP socket layer initialized
  [3.551641] Bluetooth: RFCOMM TTY layer initialized
  [3.551649] Bluetooth: RFCOMM socket layer initialized
  [3.551654] Bluetooth: RFCOMM ver 1.11
  [   26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
  [   26.569287] Bluetooth: HIDP socket layer initialized
  [   26.576971] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15
  [   26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [   72.448281] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16
  [   72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 2994.842547] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17
  [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 
lmp_ver=06 lmp_subver=220e
  [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 
lmp_ver=06 lmp_subver=220e
  [ 3811.777260] input: Dell Travel Mouse WM524 as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20
  [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID 
v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c
  [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option 
usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr 
binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal 
dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul 
dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel 
hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc 
glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd 
v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms 
intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic 
cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress 
snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit
  [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth]
  [ 5579.876261]  [] hci_dev_do_open+0xe1/0xa90 [bluetooth]
  [ 5579.876266]  [] hci_power_on+0x40/0x200 [bluetooth]
  [

[Desktop-packages] [Bug 1768001] Re: En Thinkpad T430 con controlador BCM20702A0

[Juerg Haefliger]

I'm closing this bug due to old age. Please open a new bug if you think
the issue still exists.

** Changed in: linux-firmware (Ubuntu)
   Status: Triaged => Expired

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1768001

Title:
  En Thinkpad T430 con controlador BCM20702A0

Status in bluez package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Expired

Bug description:
  loa dispositivos se intentan conectar y se conectan/desconectan
  continuamente. Se hace inutilizable el bluetooth.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 13:26:49 2018
  InstallationDate: Installed on 2018-04-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349I62
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b9f1f5f8-77c7-404e-92e8-a58f7bd5fa9e ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB4WW (2.74 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349I62
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB4WW(2.74):bd09/25/2017:svnLENOVO:pn2349I62:pvrThinkPadT430:rvnLENOVO:rn2349I62:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349I62
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:E5:43:C5:85:87  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1196 acl:0 sco:0 events:88 errors:0
TX bytes:4095 acl:0 sco:0 commands:86 errors:0

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


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

[Desktop-packages] [Bug 2021956] Re: crash cups-proxyd

[Juerg Haefliger]

Remove the snap. Printing works fine here with deb 2.4.7-1.2ubuntu7.2.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2021956

Title:
  crash cups-proxyd

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu IOT Desktop 22.04 LTS

  # cat /etc/os-release
  PRETTY_NAME="Ubuntu 22.04.2 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04.2 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  UBUNTU_CODENAME=jammy

  Kernel Version: 5.15.0-1028-intel-iotg

  # journalctl --no-hostname -b --no-pager | grep cups-proxyd
  mai 31 11:51:22 cups.cupsd[949]: + PROXY_DAEMON=cups-proxyd
  mai 31 11:51:22 cups.cupsd[3032]: exec cups-proxyd 
/var/snap/cups/common/run/cups.sock /run/cups/cups.sock -l --logdir 
/var/snap/cups/872/var/log
  mai 31 11:51:23 audit[3032]: SECCOMP auid=4294967295 uid=0 gid=0 
ses=4294967295 subj=snap.cups.cupsd pid=3032 comm="cups-proxyd" 
exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 
ip=0x7fb050c2973d code=0x5
  mai 31 11:51:23 kernel: audit: type=1326 audit(1685523083.773:85): 
auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=3032 
comm="cups-proxyd" exe="/snap/cups/872/sbin/cups-proxyd" sig=0 arch=c03e 
syscall=314 compat=0 ip=0x7fb050c2973d code=0x5
  mai 31 11:51:24 kernel: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e 
sp 7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000]

  
  Error: cups-proxyd[3032]: segfault at 18 ip 558e95990d6e sp 
7ffe2436a230 error 4 in cups-proxyd[558e9598d000+7000]


  Snap list:
  # snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  chromium   113.0.5672.1262477   latest/stable
canonical✓ -
  core20 20230503  1891   latest/stable
canonical✓ base
  core22 20230503  634latest/stable
canonical✓ base
  cups   2.4.2-5   872latest/stable
openprinting✓  -
  firefox111.0-2   2432   latest/stable/…  mozilla✓ 
  -
  gnome-3-38-20040+git.6f39565 140latest/stable/…  
canonical✓ -
  gnome-42-2204  0+git.587e965 102latest/stable
canonical✓ -
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-71-g709398e  959latest/stable/…  
canonical✓ -
  snapd  2.59.219122  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.9   83 latest/stable/…  
canonical✓ -

  
  Reproduced: At every boot OS

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


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Juerg Haefliger]

** Changed in: libcamera (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037642

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Won't Fix
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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


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

[Desktop-packages] [Bug 2038669] Re: Add Raspberry Pi 5 support

[Juerg Haefliger]

** Also affects: libcamera (Ubuntu Noble)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/2038669

Title:
  Add Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Confirmed
Status in libcamera source package in Mantic:
  Won't Fix
Status in libcamera source package in Noble:
  New

Bug description:
  placeholder

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


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

[Desktop-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop

[Juerg Haefliger]

We should drop it from the seed since we're not building ARM ISOs
anymore.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2062667

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

This should go into a raspi specific package/config.


** Also affects: ubuntu-raspi-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-raspi (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in SDDM:
  New
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-raspi-settings package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

And:

#!/bin/bash

# Glamor should not run on platforms prior to Pi 4.

if ! raspi-config nonint gpu_has_mmu ; then
if ! [ -e /usr/share/X11/xorg.conf.d/20-noglamor.conf ] ; then
cat > /usr/share/X11/xorg.conf.d/20-noglamor.conf << EOF
Section "Device"
Identifier "kms"
Driver "modesetting"
Option "AccelMethod" "msdri3"
Option "UseGammaLUT" "off"
EndSection
EOF
fi
else
if [ -e /usr/share/X11/xorg.conf.d/20-noglamor.conf ] ; then
rm /usr/share/X11/xorg.conf.d/20-noglamor.conf
fi
fi

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in SDDM:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

OK, it's an X config. It runs this script:

#!/bin/bash

# Choose an appropriate "Primary GPU" for Xorg
# This should normally be vc4 (not v3d) but when some
# other display is enabled on Pi5, it should match that.

IDENTIFIER=vc4
MATCHDRIVER=vc4

if raspi-config nonint is_pifive; then
  if ls /dev/dri/by-path/ | grep -q '\(vec\|dsi\|dpi\)-card' ; then
IDENTIFIER=rp1
MATCHDRIVER='rp1-vec|rp1-dsi|rp1-dpi'
  fi
fi

sed -e "s/XXX/${IDENTIFIER}/" << EOF | sed -e "s/YYY/${MATCHDRIVER}/" > 
/etc/X11/xorg.conf.d/99-v3d.conf.tmp
Section "OutputClass"
  Identifier "XXX"
  MatchDriver "YYY"
  Driver "modesetting"
  Option "PrimaryGPU" "true"
EndSection
EOF

mv -f /etc/X11/xorg.conf.d/99-v3d.conf.tmp
/etc/X11/xorg.conf.d/99-v3d.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in SDDM:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

gldriver_test:

Description: Various graphics-related config services
 Installs systemd services to manage various aspects of configuration
 of video drivers on Raspberry Pi.

http://archive.raspberrypi.org/debian/pool/main/g/gldriver-test/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in SDDM:
  New
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

Ok. Thanks for the clarification regarding X support. In that case we
need to understand what gldriver_test is doing that fixes things.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2044718] Re: mantic on raspberry5: x and/or lightdm problems

[Juerg Haefliger]

If this is an X specific package then I'd say adding it to Ubuntu won't
fly. X is dead and Wayland is the future. But I've been proven to be
wrong in the past :-)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2044718

Title:
  mantic on raspberry5: x and/or lightdm problems

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  New

Bug description:
  running mantic on raspberry5, graphical sessions doesn't start unless on 
gdm3; while performing installation, Ubuntu Budgie graphical session goes on 
without problems but at reboot DE doesn't start.
  Tried installing "classical" ubuntu and DE came on w/o problems; installed 
budgie-desktop and lightdm side by side and budgie didn't start; installed sddm 
with same results. Only gdm3 works
  See attached logs collection

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


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Juerg Haefliger]

** No longer affects: libcamera (Ubuntu Noble)

** No longer affects: linux-meta-raspi (Ubuntu Noble)

** No longer affects: linux-raspi (Ubuntu Noble)

** No longer affects: mesa (Ubuntu Noble)

** No longer affects: pipewire (Ubuntu Noble)

** No longer affects: rpi-eeprom (Ubuntu Noble)

** No longer affects: ubuntu-settings (Ubuntu Noble)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/2037642

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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


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

[Desktop-packages] [Bug 2041219] Re: GUI Freezes Randomly

[Juerg Haefliger]

Not seeing any kernel issues in the log but gnome-shell stack traces:

Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x557967942990), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x557967942990), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context 0x5579631c7180 ==
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #0   7ffdfcf6b3f0 b   
resource:///org/gnome/shell/ui/workspacesView.js:639 (61fcff5c1a0 @ 33)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #1   7ffdfcf6b540 b   
resource:///org/gnome/shell/ui/workspacesView.js:686 (61fcff5c240 @ 488)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #2   7ffdfcf6cfe0 b   
resource:///org/gnome/shell/ui/workspace.js:855 (61fcff08510 @ 370)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #3   7ffdfcf6d700 b   
resource:///org/gnome/shell/ui/workspace.js:806 (61fcff08470 @ 17)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #4   5579632ca070 i   
resource:///org/gnome/shell/ui/workspacesView.js:1016 (61fcff5cc40 @ 124)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #5   5579632c9fe0 i   
resource:///org/gnome/shell/ui/overviewControls.js:715 (2744d0ebcd80 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #6   5579632c9f58 i   
resource:///org/gnome/shell/ui/layout.js:347 (133181930510 @ 22)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #7   5579632c9ec8 i   
resource:///org/gnome/shell/ui/overview.js:641 (2744d0ebabf0 @ 175)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #8   5579632c9e48 i   
resource:///org/gnome/shell/ui/overview.js:624 (2744d0ebaba0 @ 12)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #9   5579632c9dc8 i   
resource:///org/gnome/shell/ui/overviewControls.js:757 (2744d0ebcf60 @ 55)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #10   7ffdfcf73460 b   
resource:///org/gnome/shell/ui/environment.js:151 (1331819cc4c0 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #11   7ffdfcf73520 b   
resource:///org/gnome/shell/ui/environment.js:317 (1331819cc9c0 @ 14)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context 0x5579631c7180 ==
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #0   7ffdfcf6b540 b   
resource:///org/gnome/shell/ui/workspacesView.js:688 (61fcff5c240 @ 505)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #1   7ffdfcf6cfe0 b   
resource:///org/gnome/shell/ui/workspace.js:855 (61fcff08510 @ 370)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #2   7ffdfcf6d700 b   
resource:///org/gnome/shell/ui/workspace.js:806 (61fcff08470 @ 17)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #3   5579632ca070 i   
resource:///org/gnome/shell/ui/workspacesView.js:1016 (61fcff5cc40 @ 124)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #4   5579632c9fe0 i   
resource:///org/gnome/shell/ui/overviewControls.js:715 (2744d0ebcd80 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #5   5579632c9f58 i   
resource:///org/gnome/shell/ui/layout.js:347 (133181930510 @ 22)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #6   5579632c9ec8 i   
resource:///org/gnome/shell/ui/overview.js:641 (2744d0ebabf0 @ 175)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #7   5579632c9e48 i   
resource:///org/gnome/shell/ui/overview.js:624 (2744d0ebaba0 @ 12)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #8   5579632c9dc8 i   
resource:///org/gnome/shell/ui/overviewControls.js:757 (2744d0ebcf60 @ 55)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #9   7ffdfcf73460 b   
resource:///org/gnome/shell/ui/environment.js:151 (1331819cc4c0 @ 39)
Oct 26 10:32:44 darian-W94-95-97JU gnome-shell[2648]: #10   7ffdfcf73520 b   
resource:///org/gnome/shell/ui/environment.js:317 (1331819cc9c0 @ 14)
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: Object St.Button 
(0x5579632bdff0), has been already disposed — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: Object St.Label 
(0x557968471c40), has been already disposed — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
Oct 26 10:32:45 darian-W94-95-97JU gnome-shell[2648]: == Stack trace for 
context 0x5579631c718

[Desktop-packages] [Bug 2041496] [NEW] btmgmt --index broken in Mantic

[Juerg Haefliger]

Public bug reported:

On Mantic:

$ btmgmt --index 1 info
Unable to open 1: No such file or directory (2)
Index list with 1 item
hci0:   Primary controller
 addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
 supported settings: powered connectable fast-connectable discoverable bondable 
link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
 current settings: powered ssp br/edr le secure-conn
 name rpi-5b-rev1d0-f88b
 short name
hci0:   Configuration options
 supported options: public-address
 missing options:

Note the error 'Unable to open...' above.

The machine has only a single hci so index 1 is invalid. The correct
result should be:

$ btmgmt --index 1 info
Reading hci1 info failed with status 0x11 (Invalid Index)

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

** Description changed:

  On Mantic:
  
- btmgmt --index 1 info
+ $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
-   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
-   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration 
-   current settings: powered ssp br/edr le secure-conn 
-   name rpi-5b-rev1d0-f88b
-   short name 
+  addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
+  supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
+  current settings: powered ssp br/edr le secure-conn
+  name rpi-5b-rev1d0-f88b
+  short name
  hci0: Configuration options
-   supported options: public-address 
-   missing options: 
- 
+  supported options: public-address
+  missing options:
  
  Note the error 'Unable to open...'
  
  The machine has only a single hci so index 1 is invalid. The correct
  result should be:
  
  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

** Description changed:

  On Mantic:
  
  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:
  
- Note the error 'Unable to open...'
+ Note the error 'Unable to open...' above.
  
  The machine has only a single hci so index 1 is invalid. The correct
  result should be:
  
  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2041496

Title:
  btmgmt --index broken in Mantic

Status in bluez package in Ubuntu:
  New

Bug description:
  On Mantic:

  $ btmgmt --index 1 info
  Unable to open 1: No such file or directory (2)
  Index list with 1 item
  hci0: Primary controller
   addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
   supported settings: powered connectable fast-connectable discoverable 
bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy 
configuration static-addr phy-configuration
   current settings: powered ssp br/edr le secure-conn
   name rpi-5b-rev1d0-f88b
   short name
  hci0: Configuration options
   supported options: public-address
   missing options:

  Note the error 'Unable to open...' above.

  The machine has only a single hci so index 1 is invalid. The correct
  result should be:

  $ btmgmt --index 1 info
  Reading hci1 info failed with status 0x11 (Invalid Index)

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


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

[Desktop-packages] [Bug 2039358] Re: Audio via bluetooth gets intermitent when a browser is started

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 2038539
   bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC)

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

Title:
  Audio via bluetooth gets intermitent when a browser is started

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  listening to a fresh boot of mantic install .. sound works properly
  and bluetooh headphones/speaker connection is flawless.. starting a
  browser .. audio becomes choppy via bluetooth .. laptop speaker suffer
  no degradation.. occurs with kernels above 6.5.0-5  see bug 2038539
  also.. (reported from a 6.5.0-5 kernel instance

  This report was added so a report from a 6.5.0-9 kernel instance is
  made

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  derk   1707 F wireplumber
   /dev/snd/controlC1:  derk   1707 F wireplumber
   /dev/snd/seq:derk   1704 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Oct 14 10:39:35 2023
  InstallationDate: Installed on 2023-10-04 (10 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
  dmi.product.family: IdeaPad Slim 5 16ABR8
  dmi.product.name: 82XG
  dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
  dmi.product.version: IdeaPad Slim 5 16ABR8
  dmi.sys.vendor: LENOVO

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


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

[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

FWIW, this works correctly with a 6.2 lunar kernel and mantic userspace.

** Attachment added: "udev-6-2-3b+.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708655/+files/udev-6-2-3b+.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038964

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

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


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

[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

udev debug log from a 3B+

** Attachment added: "udev-3b+.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708640/+files/udev-3b+.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038964

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

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


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

[Desktop-packages] [Bug 2038964] Re: raspi ethernet rename is racy

[Juerg Haefliger]

udev debug log from a 3B

** Attachment added: "udev-3b.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708641/+files/udev-3b.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2038964

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

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


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

[Desktop-packages] [Bug 2038669] [NEW] Add Raspberry Pi 5 support

[Juerg Haefliger]

Public bug reported:

placeholder

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

** Affects: libcamera (Ubuntu Mantic)
 Importance: Undecided
 Status: New

** Also affects: libcamera (Ubuntu Mantic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcamera in Ubuntu.
https://bugs.launchpad.net/bugs/2038669

Title:
  Add Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  New
Status in libcamera source package in Mantic:
  New

Bug description:
  placeholder

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


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Juerg Haefliger]

** Changed in: linux-meta-raspi (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: linux-raspi (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2037642

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Juerg Haefliger]

Debdiff with squash of
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450

Briefly tested on Pi 5, 4 and 400. Desktop comes up and glx and vulkan
are accelerated.

** Patch added: "mesa_23.2.1-1ubuntu2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037642/+attachment/5705304/+files/mesa_23.2.1-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2037642

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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


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

[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support

[Juerg Haefliger]

** Changed in: libcamera (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-meta-raspi (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-raspi (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: pipewire (Ubuntu)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2037642

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

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


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

[Desktop-packages] [Bug 2037635] [NEW] Add support for Pi 5

[Juerg Haefliger]

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

Public bug reported:

Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa.

Upstream MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450

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

** Affects: mesa (Ubuntu Mantic)
 Importance: Undecided
 Status: New

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

** Description changed:

- Placeholder
+ Backport support for new bcm2712 HW (used on Pi 5) to Mantic mesa.
+ Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450

** Description changed:

- Backport support for new bcm2712 HW (used on Pi 5) to Mantic mesa.
- Upstream MR: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450
+ Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa.
+ 
+ Upstream MR:
+ https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450

** This bug has been marked a duplicate of bug 2037642
   [FFe] Raspberry Pi 5 support

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037635

Title:
  Add support for Pi 5

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Mantic:
  New

Bug description:
  Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa.

  Upstream MR:
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450

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


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

[Desktop-packages] [Bug 2037425] [NEW] ubuntu-server pulls in ZFS userspace

[Juerg Haefliger]

Public bug reported:

ubuntu-server in Mantic pulls in zfs userspace packages and systemd
services are automatically enabled, which means zfs kernel modules are
automatically loaded at boot, for everybody. On Raspberry Pi, this
results in +5MB of additional memory consumption which is not
acceptable, especially not on 512MB devices.

Culprit:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35

** Affects: ubuntu-meta (Ubuntu)
 Importance: Critical
 Status: New

** Affects: ubuntu-meta (Ubuntu Mantic)
 Importance: Critical
 Status: New


** Tags: rls-mm-incoming

** Also affects: ubuntu-meta (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu Mantic)
   Importance: Undecided => Critical

** Description changed:

  ubuntu-server in Mantic pulls in zfs userspace packages and systemd
  services are automatically enabled, which means zfs kernel modules are
- automatically loaded at boot, for everybody. On Raspberry Pi, that
+ automatically loaded at boot, for everybody. On Raspberry Pi, this
  results in +5MB of additional memory consumption which is not
  acceptable, especially not on 512MB devices.
  
  Culprit:
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2037425

Title:
  ubuntu-server pulls in ZFS userspace

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Mantic:
  New

Bug description:
  ubuntu-server in Mantic pulls in zfs userspace packages and systemd
  services are automatically enabled, which means zfs kernel modules are
  automatically loaded at boot, for everybody. On Raspberry Pi, this
  results in +5MB of additional memory consumption which is not
  acceptable, especially not on 512MB devices.

  Culprit:
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35

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


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

[Desktop-packages] [Bug 2017097] Re: [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

[Juerg Haefliger]

How do you determine shell fps?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2017097

Title:
  [raspi] GNOME Shell runs at 30 FPS unless the CPU is being stressed

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

Bug description:
  On a Raspberry Pi 400, GNOME Shell runs at 30 FPS unless the CPU is
  being stressed in which case it becomes a smooth 60 FPS. Seems like a
  frequency scaling issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.2.0-1004.5-raspi 6.2.6
  Uname: Linux 6.2.0-1004-raspi aarch64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 20 15:13:51 2023
  ImageMediaBuild: 20230417
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2015182] Re: Add support for Adreno a690

[Juerg Haefliger]

Test packages: https://launchpad.net/~juergh/+archive/ubuntu/mesa

** Description changed:

- The Lenovo X13s ARM laptop contains an Ardeno a690 GPU. Please add Mesa
+ The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa
  support for this GPU. This landed in upstream Mesa here:
  
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2015182

Title:
  Add support for Adreno a690

Status in mesa package in Ubuntu:
  New

Bug description:
  The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add
  Mesa support for this GPU. This landed in upstream Mesa here:

  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573

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


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

[Desktop-packages] [Bug 2015182] Re: Add support for Adreno a690

[Juerg Haefliger]

** Attachment added: "mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+attachment/5660728/+files/mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2015182

Title:
  Add support for Adreno a690

Status in mesa package in Ubuntu:
  New

Bug description:
  The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add
  Mesa support for this GPU. This landed in upstream Mesa here:

  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573

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


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

[Desktop-packages] [Bug 2015182] [NEW] Add support for Adreno a690

[Juerg Haefliger]

Public bug reported:

The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa
support for this GPU. This landed in upstream Mesa here:

https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2015182

Title:
  Add support for Adreno a690

Status in mesa package in Ubuntu:
  New

Bug description:
  The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add
  Mesa support for this GPU. This landed in upstream Mesa here:

  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573

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


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

[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

[Juerg Haefliger]

Also works with this monitor: https://www.edid.tv/edid/2266/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1998716

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux-raspi/+bug/1998716/+subscriptions


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

[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

[Juerg Haefliger]

FWIW, works for me as well with 5.19.0-1015-raspi. Fades to black, cuts
signal, monitor turns off and stays off.

My monitor: https://www.edid.tv/edid/1091/

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1998716

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

Status in linux-raspi package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux-raspi/+bug/1998716/+subscriptions


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

[Desktop-packages] [Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor

[Juerg Haefliger]

** Tags added: kern-5128

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1998716

Title:
  [raspi] Ubuntu 22.10 does not turn off monitor

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

Bug description:
  I am using Ubuntu Desktop 22.10 on Raspberry Pi 4, and noticed a
  strange behaviour of the screen saver.

  In settings -> energy -> power saving options I selected Screen Blank
  after 5 minutes. After 5 minutes of inactivity, the screen goes blank,
  the monitor says No Signal and turns off, but a few seconds after it
  turns on again, showing a completely black screen.

  The desired behaviour here is that Ubuntu sends no signal to the
  monitor, so the monitor goes into low-consumption mode. But this is
  not happening, the monitor is on and showing a black screen.

  I wonder how to solve this problem, especially given the current
  energy situation in Europe.

  This bug is related to the Ubuntu 22.04 LTS and 22.10 version.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-1009.16-raspi 5.19.7
  Uname: Linux 5.19.0-1009-raspi aarch64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  4 21:31:27 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  ImageMediaBuild: 20221018.1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  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/linux-raspi/+bug/1998716/+subscriptions


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

[Desktop-packages] [Bug 1971712] Re: Add support for Intel DG2

[Juerg Haefliger]

** Tags added: kern-4615

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971712

Title:
  Add support for Intel DG2

Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in linux-oem-6.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Jammy:
  In Progress
Status in linux-oem-5.17 source package in Jammy:
  Won't Fix
Status in linux-oem-6.0 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

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


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

[Desktop-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.

[Juerg Haefliger]

** Changed in: linux-raspi (Ubuntu Jammy)
   Status: New => Invalid

** Changed in: linux-raspi (Ubuntu Kinetic)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1977764

Title:
  kernel modules "zstd" and "z3fold" missing.

Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  New
Status in linux-raspi source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  New
Status in linux-raspi source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  New

Bug description:
  The modules "zstd" and "z3fold" are missing despite being configured
  for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot
  display that state they do not exist and so instead use compressor
  "lzo" and pool "zbud".

  Ubuntu version is 22.04 LTS flashed from the official image.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8
  ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30
  Uname: Linux 5.15.0-1008-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  6 17:29:00 2022
  ImageMediaBuild: 20220419
  SourcePackage: linux-raspi
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Juerg Haefliger]

Ah never mind I looked at the amd64 image manifest, not raspi :-(

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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

[Desktop-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

[Juerg Haefliger]

Did you disable it in user-data?

cloud-initramfs-growroot is no longer installed per the manifest
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-amd64.manifest

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1947311/+subscriptions


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

Hirsute is EOL so closing this bug. Please open a new one if the problem
still persists with one of the supported series.

** Changed in: linux-firmware (Ubuntu Hirsute)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Won't Fix

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

If you want this fixed in Ubuntu I need to know what series are
affected. Hirsute goes EOL at the end of the month. Are Impish and/or
Jammy working or affected as well?

** Changed in: linux-firmware (Ubuntu Hirsute)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Incomplete

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

@antonio-petricca, What series? What kernel?

I can produce a hirsute linux-firmware package with the reverted sdma
firmware but need someone to verify it on hirsute with the hirsute
kernel. Any takers? Or have you all moved on to impish?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

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

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

** No longer affects: mesa (Ubuntu Hirsute)

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux-firmware (Ubuntu Hirsute)
   Status: New => Confirmed

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux-firmware (Ubuntu Hirsute)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in linux-firmware source package in Hirsute:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

@antonio-petricca, sorry but 5.15.2 is not a supported Ubuntu kernel and
especially not on Bionic with (old) Bionic firmware.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Juerg Haefliger]

Hi. I'm picking up this ticket from Seth. Reading through the history it
seems it's still an open issue? My understanding is that upstream
'fixed' this by reverting fw blobs in version 20210818. I can produce a
linux-firmware test package for hirsute 20.04 with these reverts if
necessary. Just let me know.


** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1928393

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  New
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

[Desktop-packages] [Bug 1909884] Re: tracker-extract crashes with SIGSYS when adding pdf to filesystem

[Juerg Haefliger]

Closing due to inactivity.

** Changed in: linux-raspi (Ubuntu)
   Status: New => Invalid

** Changed in: tracker-miners (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/1909884

Title:
  tracker-extract crashes with SIGSYS when adding pdf to filesystem

Status in linux-raspi package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid

Bug description:
  Almost daily, _usr_libexec_tracker-extract.1000.crash shows up in
  /var/crash.

  I'm using Raspberry Pi 4B 8GB with Ubuntu 20.10 Desktop and lxqt as
  Desktop.

  uname -a:
  Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 
2020 aarch64 aarch64 aarch64 GNU/Linux

  I saw in a previous backtrace that a pdf was the problem. So i
  downloaded some pdf with firefox to /home/username/Documents. In my
  case it was https://www.who.int/ceh/capacity/sanitation_hygiene.pdf

  After doing that, a crash-report was dumped by apport to /var/crash.

  A backtrace and full backtrace is in the attachment.

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


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

[Desktop-packages] [Bug 1940910] [NEW] gnome-terminal doesn't honor --geometry

[Juerg Haefliger]

Public bug reported:

On hirsute + X11 (I haven't tested wayland) gnome-terminal no longer
honors the position as provided with --geometry COLSxROWS+X+Y. The size
still works but not the positioning.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1940910

Title:
  gnome-terminal doesn't honor --geometry

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  On hirsute + X11 (I haven't tested wayland) gnome-terminal no longer
  honors the position as provided with --geometry COLSxROWS+X+Y. The
  size still works but not the positioning.

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


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

[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt

[Juerg Haefliger]

No response to my question in #34 from April of last year so setting
'linux (Ubuntu)' to 'Invalid'.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1865379

Title:
  Raspberry Pi 4 fails to wake at login prompt

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

Bug description:
  Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
  Eoan) fails to wake from sleep when no user is logged in and the
  screen is sitting at the gdm login prompt.

  This has happened on two different systems.  One system uses the
  official RPi 7 inch touchscreen via (LCD DSI Display Connector).  The
  other system has a 10 inch non-touchscreen from SunFounder via (Micro
  HDMI).

  Nothing wakes the Pi: Keyboard, mouse, or touchscreen.

  After a user logs in and the screen locks on sleep the system wakes
  just fine with a lock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  Date: Sun Mar  1 20:03:12 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8086:0808 Intel Corp. 
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  Tags:  focal uec-images ubuntu reproducible
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-01-12 (72 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  version.compiz: compiz N/A
  v

[Desktop-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4

[Juerg Haefliger]

** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)

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

** Also affects: pi-bluetooth (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1901272

Title:
  Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on
  Raspberry Pi 4

Status in bluez package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in pi-bluetooth package in Ubuntu:
  Confirmed
Status in bluez source package in Groovy:
  New
Status in linux-raspi source package in Groovy:
  New
Status in pi-bluetooth source package in Groovy:
  New

Bug description:
  Raspberry pi 4 4Gb ram
  Ubuntu desktop 20.10 64 bit
  After reboot no Bluetooth devices connect, scanning Bluetooth devices works, 
results with same device name (duplicated and with not set up status).
  Sometimes after several reboots it works.
  If I use power off and cycle power then it works fine each time.

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

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

[Desktop-packages] [Bug 1899125] [NEW] Font scaling factor is lost after loging out

[Juerg Haefliger]

Public bug reported:

I have a font scaling factor set in gnome-tweaks. If I logout and back
in the fonts are no longer scaled even though gnome-tweaks still shows
the scaling factor.

This problem showed up after a Focal update a couple of weeks ago.

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

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

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1899125

Title:
  Font scaling factor is lost after loging out

Status in gnome-shell package in Ubuntu:
  New
Status in gnome-shell source package in Focal:
  New

Bug description:
  I have a font scaling factor set in gnome-tweaks. If I logout and back
  in the fonts are no longer scaled even though gnome-tweaks still shows
  the scaling factor.

  This problem showed up after a Focal update a couple of weeks ago.

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

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

[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt

[Juerg Haefliger]

I've noticed that the kernel you're running is quite old. Are you still
able to reproduce this issue with a current image from
http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/current/?

Also, how did you install xfce? Can you please detail the steps so we
can try to reproduce the issue? Lastly, when your display goes off, does
it turn off (go into standby) or is it just blanked?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1865379

Title:
  Raspberry Pi 4 fails to wake at login prompt

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

Bug description:
  Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
  Eoan) fails to wake from sleep when no user is logged in and the
  screen is sitting at the gdm login prompt.

  This has happened on two different systems.  One system uses the
  official RPi 7 inch touchscreen via (LCD DSI Display Connector).  The
  other system has a 10 inch non-touchscreen from SunFounder via (Micro
  HDMI).

  Nothing wakes the Pi: Keyboard, mouse, or touchscreen.

  After a user logs in and the screen locks on sleep the system wakes
  just fine with a lock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  Date: Sun Mar  1 20:03:12 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8086:0808 Intel Corp. 
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  ProcVersionSi

[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt

[Juerg Haefliger]

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1865379

Title:
  Raspberry Pi 4 fails to wake at login prompt

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  New
Status in xorg-server source package in Focal:
  New

Bug description:
  Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
  Eoan) fails to wake from sleep when no user is logged in and the
  screen is sitting at the gdm login prompt.

  This has happened on two different systems.  One system uses the
  official RPi 7 inch touchscreen via (LCD DSI Display Connector).  The
  other system has a 10 inch non-touchscreen from SunFounder via (Micro
  HDMI).

  Nothing wakes the Pi: Keyboard, mouse, or touchscreen.

  After a user logs in and the screen locks on sleep the system wakes
  just fine with a lock screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  Date: Sun Mar  1 20:03:12 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  CurrentDesktop: XFCE
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  Package: gnome-shell 3.35.91-1ubuntu2
  PackageArchitecture: armhf
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
  Tags: focal uec-images third-party-packages
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: armhf
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8086:0808 Intel Corp. 
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
  Tags:  focal uec-images ubuntu reproducible
  Uname: Linux 5.4.0-1001-raspi2 armv7l
  UpgradeStatus: Upgraded to focal on 2020-01-12 (72 days ago)
  UserGroups: adm audio cdro

[Desktop-packages] [Bug 1732357] [NEW] g_strsplit: assertion 'string != NULL' failed

[Juerg Haefliger]

Public bug reported:

Tons of the following in the log on 17.10:

Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 
'member_name != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 
'member_name != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 
'member_name != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: assertion 
'member_name != NULL' failed

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1732357

Title:
  g_strsplit: assertion 'string != NULL' failed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  Tons of the following in the log on 17.10:

  Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: 
assertion 'member_name != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: 
assertion 'member_name != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: 
assertion 'member_name != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strsplit: assertion 'string != 
NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: g_strv_length: assertion 
'str_array != NULL' failed
  Nov 15 07:49:08 gollum gnome-software[3355]: json_object_has_member: 
assertion 'member_name != NULL' failed

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

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

[Desktop-packages] [Bug 1732358] [NEW] failed to rescan

[Juerg Haefliger]

Public bug reported:

On every boot of 17.10:

Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-background-panel.desktop file: cannot process 
file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-bluetooth-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-color-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-control-center.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-datetime-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-default-apps-panel.desktop file: cannot process 
file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-display-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-info-overview-panel.desktop file: cannot process 
file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-info-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-keyboard-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-mouse-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-network-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-notifications-panel.desktop file: cannot process 
file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-online-accounts-panel.desktop file: cannot 
process file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-power-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-printers-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-privacy-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-region-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-removable-media-panel.desktop file: cannot 
process file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-search-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-sharing-panel.desktop file: cannot process file 
of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-sound-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-ubuntu-panel.desktop file: cannot process file of 
type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-universal-access-panel.desktop file: cannot 
process file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-user-accounts-panel.desktop file: cannot process 
file of type application/x-desktop
Nov 10 07:50:53 gollum gnome-software[2669]: failed to rescan: Failed to parse 
/usr/share/applications/gnome-wacom-panel.desktop file: cannot process file of 
type application/x-deskt

[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

[Juerg Haefliger]

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

Hmm... Why do you think this is a duplicate of #1720159? My stack trace
looks different.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
  globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
  add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
  if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
  self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
  self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
  mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
  linelist = s.strip().split("\n")
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 08:05:45 2017
  InstallationDate: Installed on 2017-05-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

[Juerg Haefliger]

** Also affects: duplicity
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in Duplicity:
  New
Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
  globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
  add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
  if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
  self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
  self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
  mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
  linelist = s.strip().split("\n")
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 08:05:45 2017
  InstallationDate: Installed on 2017-05-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text() from ffi_call_unix64() [dash-to-panel specific?]

[Juerg Haefliger]

I worked with Marco on Friday and he submitted a PR for dash-to-panel
which fixes my crashes. See https://github.com/jderose9/dash-to-
panel/issues/261.


** Bug watch added: github.com/jderose9/dash-to-panel/issues #261
   https://github.com/jderose9/dash-to-panel/issues/261

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text() from ffi_call_unix64() [dash-to-panel specific?]

Status in GNOME Shell:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text()

[Juerg Haefliger]

I kind of suspected that it was dash-to-panel. But a misbehaving
extension shouldn't bring gnome-shell down.

Oct 17 13:54:52 gollum org.gnome.Shell.desktop[30048]: == Stack trace for 
context 0x5567bdf59170 ==
Oct 17 13:54:52 gollum org.gnome.Shell.desktop[30048]: #0 0x5567be390fb0 i   
/home/juergh/.local/share/gnome-shell/extensions/dash-to-pa...@jderose9.github.com/windowPreview.js:506
 (0x7f58d905d918 @ 36)
Oct 17 13:54:52 gollum org.gnome.Shell.desktop[30048]: #1 0x7fff501a1ef0 I   
self-hosted:917 (0x7f59284ee4d8 @ 394)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text()

Status in GNOME Shell:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  error report:
  https://errors.ubuntu.com/problem/1c95cc2653ab00054b5d1764e41d974328a5f49d

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text()

[Juerg Haefliger]

Hmm...

$ sudo gdb -p 6478
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 6478
[New LWP 6482]
[New LWP 6485]
[New LWP 6487]
[New LWP 6491]
[New LWP 6492]
[New LWP 6493]
[New LWP 6494]
[New LWP 6495]
[New LWP 6496]
[New LWP 6497]
[New LWP 6498]
[New LWP 6499]
[New LWP 6500]
[New LWP 6501]
[New LWP 6502]
[New LWP 6503]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f717427f831 in __GI___poll (fds=0x558ad4f04000, nfds=16, timeout=11693) 
at ../sysdeps/unix/sysv/linux/poll.c:29
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb) c
Continuing.

Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
0x7f71765cde0d in g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(gdb) call gjs_dumpstack()
$1 = -776839760
(gdb)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text()

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

[Juerg Haefliger]

Happened again the day after cleaning the cache.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
  globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
  add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
  if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
  self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
  self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
  mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
  linelist = s.strip().split("\n")
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 08:05:45 2017
  InstallationDate: Installed on 2017-05-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722454] Re: Duplicity fails with MemoryError

[Juerg Haefliger]

Workaround is to purge the cache ~/.cache/deja-dup.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  do_backup(action)
File "/usr/bin/duplicity", line 1416, in do_backup
  globals.archive_dir).set_values()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
  self.get_backup_chains(partials + backend_filename_list)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
  add_to_sets(f)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
  if set.add_filename(filename):
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
  self.set_manifest(filename)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
  self.set_files_changed()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
  mf = self.get_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
  return self.get_local_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
  return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
  vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
  linelist = s.strip().split("\n")
  MemoryError

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: duplicity 0.7.12-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Oct 10 08:05:45 2017
  InstallationDate: Installed on 2017-05-25 (137 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: duplicity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1722454] [NEW] Duplicity fails with MemoryError

[Juerg Haefliger]

Public bug reported:

Running the following command:

/usr/bin/python /usr/bin/duplicity collection-status
--exclude=/mnt/jabba/juergh/backup/gollum --include=/home/juergh/.cache
/deja-dup/metadata --exclude=/home/juergh/.uk-pkg
--exclude=/home/juergh/Music --exclude=/home/juergh/debug
--exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
--exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
--exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
--exclude=/home/juergh/tmp --exclude=/home/juergh/git
--exclude=/home/juergh/Downloads
--exclude=/home/juergh/.local/share/Trash --exclude=/home/juergh/.cache
/deja-dup/tmp --exclude=/home/juergh/.thumbnails
--exclude=/home/juergh/.cache/deja-dup --exclude=/home/juergh/.cache
--include=/home/juergh --exclude=/sys --exclude=/run --exclude=/proc
--exclude=/var/tmp --exclude=/tmp --exclude=** --gio
file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
--gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-dup
--tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

results in:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1546, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1540, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1391, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1416, in do_backup
globals.archive_dir).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, 
in set_values
self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 836, 
in get_backup_chains
add_to_sets(f)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 824, 
in add_to_sets
if set.add_filename(filename):
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, 
in add_filename
self.set_manifest(filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 148, 
in set_manifest
self.set_files_changed()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 128, 
in set_files_changed
mf = self.get_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 250, 
in get_manifest
return self.get_local_manifest()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 224, 
in get_local_manifest
return manifest.Manifest().from_string(manifest_buffer)
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 215, in 
from_string
vi = VolumeInfo().from_string(match.group(1))
  File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 383, in 
from_string
linelist = s.strip().split("\n")
MemoryError

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: duplicity 0.7.12-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Oct 10 08:05:45 2017
InstallationDate: Installed on 2017-05-25 (137 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1722454

Title:
  Duplicity fails with MemoryError

Status in duplicity package in Ubuntu:
  New

Bug description:
  Running the following command:

  /usr/bin/python /usr/bin/duplicity collection-status
  --exclude=/mnt/jabba/juergh/backup/gollum
  --include=/home/juergh/.cache/deja-dup/metadata --exclude=/home/juergh
  /.uk-pkg --exclude=/home/juergh/Music --exclude=/home/juergh/debug
  --exclude=/home/juergh/canonical/cve-matrix/cve-matrix/cve-tracker
  --exclude=/home/juergh/canonical/cve-matrix/cve-autotriage
  --exclude=/home/juergh/Desktop --exclude=/home/juergh/.cache
  --exclude=/home/juergh/tmp --exclude=/home/juergh/git
  --exclude=/home/juergh/Downloads
  --exclude=/home/juergh/.local/share/Trash
  --exclude=/home/juergh/.cache/deja-dup/tmp
  --exclude=/home/juergh/.thumbnails --exclude=/home/juergh/.cache/deja-
  dup --exclude=/home/juergh/.cache --include=/home/juergh
  --exclude=/sys --exclude=/run --exclude=/proc --exclude=/var/tmp
  --exclude=/tmp --exclude=** --gio
  file:///mnt/jabba/juergh/backup/gollum --no-encryption --verbosity=9
  --gpg-options=--no-use-agent --archive-dir=/home/juergh/.cache/deja-
  dup --tempdir=/home/juergh/.cache/deja-dup/tmp --log-fd=19

  results in:

  Traceback (most recent call last):
File "/usr/bin/duplicity", line 1546, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 1540, in with_tempdir
  fn()
File "/usr/bin/duplicity", line 1391, in main
  d

[Desktop-packages] [Bug 1714989] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from st_label_set_text()

[Juerg Haefliger]

This also happens quite frequently on Artful.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1714989

Title:
  gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from
  st_label_set_text()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Saw some reports with the same title but they're all for previous
  versions.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  4 16:52:13 2017
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2017-04-21 (135 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fd97c8e7e5d :
movzbl 0x16(%rax),%edx
   PC (0x7fd97c8e7e5d) ok
   source "0x16(%rax)" (0xeb1e) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_type_check_instance_cast () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /usr/lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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