[Touch-packages] [Bug 2004533] Re: Gtk-WARNING ... drawing failure for widget ... invalid value (typically too big)

2023-02-12 Thread Daniel van Vugt
It doesn't really help. I was just searching the code for an explanation
of the message.

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

Title:
  Gtk-WARNING ... drawing failure for widget ... invalid value
  (typically too big)

Status in GTK+:
  Unknown
Status in cairo package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  A tiny sample of of my logs starting with the subject of this thread:
  gnome-shell[15376]: Can't update stage views actor [:0x564e0cfc0900] is on 
because it needs an allocation.
  others
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:18.003: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.986: infinite 
surface size not supported
  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 19:23:17.970: drawing 
failure for widget 'GtkImage': invalid value (typically too big) for the size 
of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17 gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkBox': invalid value (typically too 
big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkFixed': invalid value (typically 
too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkEventBox': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  Feb  1 19:23:17  gnome-shell[15376]: DING: (gjs:23748): Gtk-WARNING **: 
19:23:17.970: drawing failure for widget 'GtkApplicationWindow': invalid value 
(typically too big) for the size of the input (surface, pattern, etc.)
  st_widget_get_theme_node called on the widget [0x564e28a187d0 StBoxLayout 
("…")] which is not in the stage.
  gnome-shell[15376]: Window manager warning: Buggy client sent a 
_NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a4
  Feb  1 19:02:01 gnome-control-c[19519]: Finalizing AdwPreferencesPage 
0x556a2f5a5b70, but it still has children left:
  Feb  1 19:02:01 gnome-control-c[19519]:- GtkCenterBox 0x556a2f5b2300
  Feb  1 19:02:03 gnome-shell[15376]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00018

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  1 23:40:47 2023
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'disable-user-extensions' b'true'
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
  InstallationDate: Installed on 2021-01-17 (745 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2023-01-05 (27 days ago)

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


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


[Touch-packages] [Bug 2007035] Re: audio output defaults to hdmi

2023-02-12 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => pulseaudio (Ubuntu)

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

Title:
  audio output defaults to hdmi

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  appears to be similar to #1847570, however a workaround proposed does
  not help

  at the beginning of each playback, the sound output is directed to
  hdmi. In order to change to a wireless USB headset, the sink must be
  selected after the beginning of the playback. Selecting the sink
  before start of playback does not help.

  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  pulseaudio:
Installed: 1:15.99.1+dfsg1-1ubuntu2
Candidate: 1:15.99.1+dfsg1-1ubuntu2
Version table:
   *** 1:15.99.1+dfsg1-1ubuntu2 500
  500 http://lt.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:15.99.1+dfsg1-1ubuntu1 500
  500 http://lt.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  pactl list sinks short
  1 alsa_output.pci-_00_1f.3.hdmi-stereomodule-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED
  2 alsa_output.usb-EPOS_EPOS_BTD_800_A000871203803238-00.iec958-stereo 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  valdas 2136 F pulseaudio
   /dev/snd/controlC2:  valdas 2136 F pulseaudio
   /dev/snd/controlC1:  valdas 2136 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 12 20:38:40 2023
  InstallationDate: Installed on 2021-12-18 (421 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to jammy on 2022-10-31 (103 days ago)
  dmi.bios.date: 05/03/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F8
  dmi.board.asset.tag: Default string
  dmi.board.name: GB-BSi5-1135G7
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF8:bd05/03/2021:br5.19:svnGIGABYTE:pnGB-BSi5-1135G7:pvr1.x:rvnGIGABYTE:rnGB-BSi5-1135G7:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
  dmi.product.family: BRIX-00
  dmi.product.name: GB-BSi5-1135G7
  dmi.product.sku: 01
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2023-02-12T20:20:06.748040

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


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


[Touch-packages] [Bug 2007035] [NEW] audio output defaults to hdmi

2023-02-12 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

appears to be similar to #1847570, however a workaround proposed does
not help

at the beginning of each playback, the sound output is directed to hdmi.
In order to change to a wireless USB headset, the sink must be selected
after the beginning of the playback. Selecting the sink before start of
playback does not help.

Description:Ubuntu 22.04.1 LTS
Release:22.04

pulseaudio:
  Installed: 1:15.99.1+dfsg1-1ubuntu2
  Candidate: 1:15.99.1+dfsg1-1ubuntu2
  Version table:
 *** 1:15.99.1+dfsg1-1ubuntu2 500
500 http://lt.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:15.99.1+dfsg1-1ubuntu1 500
500 http://lt.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

pactl list sinks short
1   alsa_output.pci-_00_1f.3.hdmi-stereomodule-alsa-card.c  
s16le 2ch 44100Hz   SUSPENDED
2   alsa_output.usb-EPOS_EPOS_BTD_800_A000871203803238-00.iec958-stereo 
module-alsa-card.c  s16le 2ch 48000Hz   SUSPENDED

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  valdas 2136 F pulseaudio
 /dev/snd/controlC2:  valdas 2136 F pulseaudio
 /dev/snd/controlC1:  valdas 2136 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 12 20:38:40 2023
InstallationDate: Installed on 2021-12-18 (421 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to jammy on 2022-10-31 (103 days ago)
dmi.bios.date: 05/03/2021
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F8
dmi.board.asset.tag: Default string
dmi.board.name: GB-BSi5-1135G7
dmi.board.vendor: GIGABYTE
dmi.board.version: 1.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF8:bd05/03/2021:br5.19:svnGIGABYTE:pnGB-BSi5-1135G7:pvr1.x:rvnGIGABYTE:rnGB-BSi5-1135G7:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:sku01:
dmi.product.family: BRIX-00
dmi.product.name: GB-BSi5-1135G7
dmi.product.sku: 01
dmi.product.version: 1.x
dmi.sys.vendor: GIGABYTE
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2023-02-12T20:20:06.748040

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


** Tags: amd64 apport-bug jammy
-- 
audio output defaults to hdmi
https://bugs.launchpad.net/bugs/2007035
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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


[Touch-packages] [Bug 2007004] Re: Bluetooth Mouse goes into connect/disconnect loop when Wifi disconnected

2023-02-12 Thread Michael P
changed package from bluez to linux and updated text

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

** Description changed:

  Ubuntu 22.04.01 /  ASUS E410MA Laptop / Logitech MX Anywhere 2S mouse.
- Fully updated via apt.
  
- Everything worked OK until sometime around early January 2023 (it may
- have started earlier, but I only noticed it the first time I moved to a
- location without WiFi).
+ This problem occurs with the rtw88_8821ce driver
+ Workaround was to blacklist rtw88_8821ce and install rtl8821ce
  
- Since then, everything works OK as long as I am connected to WiFi. The
- moment I disconnect from a WiFi network, or disable WiFi altogether, the
- mouse begins to rapidly disconnect/connect in a loop about 3-4 times a
- second. If I boot up somewhere where I have no WiFi signal, same thing
- happens.
  
- If I boot with an older 22.04.01 live USB  - no problem
- If I boot with a recent 22.10 live USB - same problem
+   root@ithaca:~ # uname -a
+   Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64
+   GNU/Linux
  
-   root@ithaca:~ # uname -a  
-   Linux ithaca 5.15.0-60-generic #66-Ubuntu SMP Fri Jan 20 14:29:49 UTC 2023 
x86_64 x86_64 x86_64 
-   GNU/Linux
- 
-   root@ithaca:~ # inxi -EMN
-   Machine:
- Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
-   v: 1.0 serial: 
- Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
-   UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
-   Network:
- Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
-   driver: rtw_8821ce
-   Bluetooth:
- Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
- Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1
+   root@ithaca:~ # inxi -EMN
+   Machine:
+ Type: Laptop System: ASUSTeK product: VivoBook_ASUS Laptop E410MA_E410MA
+   v: 1.0 serial: 
+ Mobo: ASUSTeK model: E410MA v: 1.0 serial: XXX
+   UEFI: American Megatrends v: E410MA.302 date: 09/11/2020
+   Network:
+ Device-1: Realtek RTL8821CE 802.11ac PCIe Wireless Network Adapter
+   driver: rtw_8821ce
+   Bluetooth:
+ Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb
+ Report: hciconfig ID: hci0 state: up address: 20:4E:XX:XX:XX:XX bt-v: 2.1
  
  Output of running bluetoothctl while this happens:
  
-   root@ithaca:/var/log # bluetoothctl
-   Agent registered
- (At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
-  then about 10 seconds elapse, then the below messages start)
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
- (This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
-   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
-   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
-   [MX Anywhere 2S]# 
-   [MX Anywhere 2S]# 
+   root@ithaca:/var/log # bluetoothctl
+   Agent registered
+ (At this point I disconnect WiFI. Mouse starts acting up immediately, 
responding erratically,
+  then about 10 seconds elapse, then the below messages start)
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+ (This goes on and on about 3 times a second until I reconnect Wifi using 
the touchpad)
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: no
+   [CHG] Device E4:3B:XX:XX:XX:XX Connected: yes
+   [CHG] Device E4:3B:XX:XX:XX:XX ServicesResolved: yes
+   [MX Anywhere 2S]#
+   [MX Anywhere 2S]#
  
  kern.log messages while this happens:
  < I disconnect from Wifi>
-   Feb 11 20:46:15 ithaca kernel: [ 3385.920613] wlo1: deauthenticating from 
de:5d:xx:xx:xx:xx by 
-   local choice (Reason: 3=DEAUTH_LEAVING)
-   Feb 11 20:46:15 ithaca kernel: [ 3386.027110] rtw_8821ce :02:00.0: sta 
de:5d:xx:xx:xx:xx 
-   with macid 0 left
-   Feb 11 20:46:33 ithaca kernel: [ 3403.244131] input: MX Anywhere 2S 
Keyboard as /devices/virtual/misc/uhid/0005:046D:B01A.0019/input/input87
-   Feb 11 20:46:33 ithaca kernel: [ 3403.248887] input: MX Anywhere 2S Mouse 
as