[Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)

2022-11-09 Thread Roel Van de Paar
Are you using Compton? If so, please see
https://askubuntu.com/a/1439993/682596 and
https://gitlab.xfce.org/xfce/xfwm4/-/issues/676

Basically, Compton could be at fault for creating these key delays. As
soon as I start Compton manually in a similar fashion as the OS startup,
the problem appears. I am not using double keyboards.

** Bug watch added: gitlab.xfce.org/xfce/xfwm4/-/issues #676
   https://gitlab.xfce.org/xfce/xfwm4/-/issues/676

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

Title:
  Desktop briefly becomes unresponsive when receiving a keypress from a
  different device/mapping than the last keypress (in Xorg)

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


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

[Bug 1943488] Re: when typeing too fast in the search line searching stops to work

2022-11-09 Thread Jeff Fortin Tam
If this is related to the bug I had filed upstream (linked above), then
this should be fixed in Nautilus 43.1 or later.

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1731
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/1731
   Importance: Unknown
   Status: Unknown

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

Title:
  when typeing too fast in the search line searching stops to work

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


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

[Bug 1990563] Re: Some maximized/fullscreen windows appear on both monitors

2022-11-09 Thread Andrea
43.1 seems to exist at https://gitlab.gnome.org/GNOME/mutter/-/tags

Does anybody have a package to see if it actually fixes it?

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

Title:
  Some maximized/fullscreen windows appear on both monitors

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


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

[Bug 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-11-09 Thread Jefferson Ascaneo
Same issue with evince 42.3-0ubuntu2, apparmor 3.0.4-2ubuntu2.1,
cinnamon 5.2.7-4 on Ubuntu 22.04.1 (jammy).

I believe the apparmor workaround below is better, since it works on any
version:

Inside '/etc/apparmor.d/usr.bin.evince', add following line after the
line containing 'thunar':

  /usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx ->
sanitized_helper, # Print Dialog

Alternatively, run the command below (one line):

$ sudo sed -i 's|.*/usr/bin/thunar Cx -> sanitized_helper,.*|&\n
/usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx ->
sanitized_helper, # Print Dialog|' /etc/apparmor.d/usr.bin.evince

The workaround above solves the issue for me.

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

Title:
  evince does not print (apparmor, pxgsettings)

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


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

[Bug 1983794] Re: Evolution not deleting autosave files

2022-11-09 Thread Esben Høg
To try to get rid of this problem with Evolution I uninstalled
libcanberra-gtk-3-0 as m...@papersolve.com suggested, and after that I
can only log in to my Ubuntu 22.04 in terminal mode! I have reinstalled
libcanberra-gtk-3-0 but it doesn't help. I am stuck in terminal at
start-up !!

(I realize now that I should never have uninstalled libcanberra-gtk-3-0)

How do I get the GUI back ??

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

Title:
  Evolution not deleting autosave files

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


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

[Bug 1996068] Re: i915 crash at boot time (probably to activate vga console)

2022-11-09 Thread Germán Poo-Caamaño
** Package changed: mutter (Ubuntu) => linux (Ubuntu)

** Attachment added: "Output of dmidecoe"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996068/+attachment/5630050/+files/dmi.txt

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

Title:
  i915 crash at boot time (probably to activate vga console)

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


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

[Bug 1996068] [NEW] i915 crash at boot time (probably to activate vga console)

2022-11-09 Thread Germán Poo-Caamaño
Public bug reported:

This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen.


Nov  5 09:46:42 shusaku kernel: [2.209937] [ cut here 
]
Nov  5 09:46:42 shusaku kernel: [2.209938] i915 :00:02.0: Block 42 
min_size is zero
Nov  5 09:46:42 shusaku kernel: [2.209953] WARNING: CPU: 2 PID: 254 at 
drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915]
Nov  5 09:46:42 shusaku kernel: [2.210068] Modules linked in: fjes(+) 
i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core 
drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul 
ghash_c
lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci 
nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss 
thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid 
video pin
ctrl_tigerlake
Nov  5 09:46:42 shusaku kernel: [2.210087] CPU: 2 PID: 254 Comm: 
systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu
Nov  5 09:46:42 shusaku kernel: [2.210089] Hardware name: LENOVO 
21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022
Nov  5 09:46:42 shusaku kernel: [2.210091] RIP: 
0010:init_bdb_block+0x29a/0x460 [i915]
Nov  5 09:46:42 shusaku kernel: [2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 
f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 
89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6 
48 c7 c7
Nov  5 09:46:42 shusaku kernel: [2.210168] RSP: 0018:abb9c0953888 
EFLAGS: 00010246
Nov  5 09:46:42 shusaku kernel: [2.210170] RAX:  RBX: 
8ca1a1108000 RCX: 
Nov  5 09:46:42 shusaku kernel: [2.210171] RDX:  RSI: 
 RDI: 
Nov  5 09:46:42 shusaku kernel: [2.210172] RBP: abb9c09538d8 R08: 
 R09: 
Nov  5 09:46:42 shusaku kernel: [2.210173] R10:  R11: 
 R12: 002a
Nov  5 09:46:42 shusaku kernel: [2.210174] R13:  R14: 
8ca1826ad170 R15: 8ca1a1109328
Nov  5 09:46:42 shusaku kernel: [2.210175] FS:  7f21d34178c0() 
GS:8ca8bf48() knlGS:
Nov  5 09:46:42 shusaku kernel: [2.210176] CS:  0010 DS:  ES:  CR0: 
80050033
Nov  5 09:46:42 shusaku kernel: [2.210177] CR2: 55a99a0511d8 CR3: 
00011d202003 CR4: 00770ee0
Nov  5 09:46:42 shusaku kernel: [2.210179] PKRU: 5554
Nov  5 09:46:42 shusaku kernel: [2.210179] Call Trace:
Nov  5 09:46:42 shusaku kernel: [2.210181]  
Nov  5 09:46:42 shusaku kernel: [2.210183]  intel_bios_init+0x171/0x7c0 
[i915]
Nov  5 09:46:42 shusaku kernel: [2.210312]  ? 
drm_vblank_worker_init+0x68/0x80 [drm]
Nov  5 09:46:42 shusaku kernel: [2.210391]  
intel_modeset_init_noirq+0x3b/0x250 [i915]
Nov  5 09:46:42 shusaku kernel: [2.210594]  i915_driver_probe+0x1ae/0x490 
[i915]
Nov  5 09:46:42 shusaku kernel: [2.210765]  ? 
drm_privacy_screen_get+0x16d/0x190 [drm]
Nov  5 09:46:42 shusaku kernel: [2.210833]  ? acpi_dev_found+0x64/0x80
Nov  5 09:46:42 shusaku kernel: [2.210842]  i915_pci_probe+0x56/0x150 [i915]
Nov  5 09:46:42 shusaku kernel: [2.210935]  local_pci_probe+0x44/0x90
Nov  5 09:46:42 shusaku kernel: [2.210939]  pci_call_probe+0x55/0x190
Nov  5 09:46:42 shusaku kernel: [2.210940]  pci_device_probe+0x84/0x120
Nov  5 09:46:42 shusaku kernel: [2.210941]  really_probe+0x1dc/0x3b0
Nov  5 09:46:42 shusaku kernel: [2.210945]  
__driver_probe_device+0x12c/0x1b0
Nov  5 09:46:42 shusaku kernel: [2.210946]  driver_probe_device+0x24/0xd0
Nov  5 09:46:42 shusaku kernel: [2.210948]  __driver_attach+0xe0/0x210
Nov  5 09:46:42 shusaku kernel: [2.210949]  ? 
__device_attach_driver+0x130/0x130
Nov  5 09:46:42 shusaku kernel: [2.210951]  bus_for_each_dev+0x8d/0xe0
Nov  5 09:46:42 shusaku kernel: [2.210952]  driver_attach+0x1e/0x30
Nov  5 09:46:42 shusaku kernel: [2.210953]  bus_add_driver+0x187/0x230
Nov  5 09:46:42 shusaku kernel: [2.210955]  driver_register+0x8f/0x100
Nov  5 09:46:42 shusaku kernel: [2.210956]  __pci_register_driver+0x62/0x70
Nov  5 09:46:42 shusaku kernel: [2.210958]  
i915_pci_register_driver+0x23/0x30 [i915]
Nov  5 09:46:42 shusaku kernel: [2.210993]  i915_init+0x3b/0xf2 [i915]
Nov  5 09:46:42 shusaku kernel: [2.211045]  ? 0xc098b000
Nov  5 09:46:42 shusaku kernel: [2.211046]  do_one_initcall+0x5b/0x240
Nov  5 09:46:42 shusaku kernel: [2.211049]  do_init_module+0x50/0x210
Nov  5 09:46:42 shusaku kernel: [2.211051]  load_module+0xb7d/0xcd0
Nov  5 09:46:42 shusaku kernel: [2.211053]  __do_sys_finit_module+0xc4/0x140
Nov  5 09:46:42 shusaku kernel: [2.211054]  ? 
__do_sys_finit_module+0xc4/0x140
Nov  5 09:46:42 shusaku kernel: [2.211056]  __x64_sys_finit_module+0x18/0x30
Nov  5 09:46:42 shusaku 

[Bug 1983794] Re: Evolution not deleting autosave files

2022-11-09 Thread m...@papersolve.com
Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)

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

Title:
  Evolution not deleting autosave files

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


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

[Bug 1996053] [NEW] No GUI after upgrade from 22.04.1 to 22.10

2022-11-09 Thread Heinrich Bjerregaard
Public bug reported:

I am running Ubuntu 22.04.1 on a VM under TrueNas.
After upgrade to 22.10 I just ends up with a black screen, however, everything 
else like mail, dns, dhcp and apache2 works well.

I am using x11vnc and in the 'journalctl -b' it seems that a display
cannot be achieved.

In the boot menu I have
*Ubuntu, with Linux version 5.19.0-23-generic
 Ubuntu, with Linux version 5.15.0-52-generic

However, if I am booting 5.15.0-52 everything is OK.
-
lsb_release -rd
Description:Ubuntu 22.10
Release:22.10
-
cat /proc/version_signature
Ubuntu 5.19.0-23.24-generic 5.19.7

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

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

Title:
  No GUI after upgrade from 22.04.1 to 22.10

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


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

[Bug 1987631] Re: Screencast only records one second

2022-11-09 Thread Bin Li
On 22.10, our customer could not reproduce this issue.

I picked the patch in pipewire, the screencast becomes stable, the fail
rate is lower than before, although it would skip frames for seconds. I
will let our customer do more test.

https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/1ea1d525

https://people.canonical.com/~binli/pipewire/

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

Title:
  Screencast only records one second

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


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

[Bug 1987631] Re: Screencast only records one second

2022-11-09 Thread Bin Li
** Tags added: oem-priority originate-from-1994117 sutton

** Changed in: oem-priority
 Assignee: (unassigned) => Bin Li (binli)

** Changed in: oem-priority
   Importance: Undecided => High

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Screencast only records one second

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


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