I upgraded to 20.09 beta today, and on login, network-manager-applet crashes:
sept. 30 22:24:22 nlaptop systemd[1703]: Started Network manager applet.
sept. 30 22:24:30 nlaptop .nm-applet-wrap[1745]: Failed to connect to proxy
sept. 30 22:24:30 nlaptop .nm-applet-wrap[1745]: Failed to show notification: Erreur lors de l鈥檃ppel de StartServiceByName pour org.freedesktop.Notifications聽: Unit xfce4-notifyd.service not found.
sept. 30 22:24:36 nlaptop .nm-applet-wrap[1745]: GdkWindow 0xe00002 unexpectedly destroyed
sept. 30 22:24:36 nlaptop .nm-applet-wrap[1745]: ../gobject/gsignal.c:2735: instance '0x6bf4c0' has no handler with id '724'
sept. 30 22:24:36 nlaptop .nm-applet-wrap[1745]: The program 'nm-applet' received an X Window System error.
This probably reflects a bug in the program.
The error was 'RenderBadPicture (invalid Picture parameter)'.
(Details: serial 287 error_code 143 request_code 139 (RENDER) minor_code 7)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the GDK_SYNCHRONIZE environment
variable to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
sept. 30 22:24:37 nlaptop systemd[1703]: nm-applet.service: Main process exited, code=dumped, status=5/TRAP
sept. 30 22:24:37 nlaptop systemd[1703]: nm-applet.service: Failed with result 'core-dump'.
sept. 30 22:24:37 nlaptop systemd-coredump[2021]: Process 1745 (.nm-applet-wrap) of user 1000 dumped core.
```
````
This did no use happen on 20.03.
I saw this with ibus once, but it does not reproduce reliably, and maybe it's something else.
Note that the bug is twofold: first nm crashes, but the unit does not have Restart=always. Restarting the unit by hand works perfectly.
programs.nm-applet.enable = true
Login to your x session. This happened to me in a xfce+i3 session, not sure if it's relevant.
"x86_64-linux"Linux 5.8.11, NixOS, 20.09beta514.a9226f2b3a5 (Nightingale)yesyesnix-env (Nix) 2.3.7"nixos-20.09beta514.a9226f2b3a5, nixos-hardware, nixos-unstable-21.03pre244669.5aba0fe9766""home-manager-20.09""home-manager-20.03"/nix/var/nix/profiles/per-user/root/channels/nixoscc nm applet module maintainers @jtojnar @worldofpeace
I also see this with i3 and nm-applet. I use nixos-unstable. And the same is reported by parcellite application:
Oct 16 08:18:05 steelpick .parcellite-wra[1652]: GdkWindow 0x120001c unexpectedly destroyed
Oct 16 08:18:05 steelpick xsession[1652]: The program 'parcellite' received an X Window System error.
Oct 16 08:18:05 steelpick xsession[1652]: This probably reflects a bug in the program.
Oct 16 08:18:05 steelpick xsession[1652]: The error was 'RenderBadPicture (invalid Picture parameter)'.
Oct 16 08:18:05 steelpick xsession[1652]: (Details: serial 299 error_code 143 request_code 139 minor_code 7)
Oct 16 08:18:05 steelpick xsession[1652]: (Note to programmers: normally, X errors are reported asynchronously;
Oct 16 08:18:05 steelpick xsession[1652]: that is, you will receive the error a while after causing it.
Oct 16 08:18:05 steelpick xsession[1652]: To debug your program, run it with the --sync command line
Oct 16 08:18:05 steelpick xsession[1652]: option to change this behavior. You can then get a meaningful
Oct 16 08:18:05 steelpick xsession[1652]: backtrace from your debugger if you break on the gdk_x_error() function.)
If needed, I can try to get the backtrace.
I can trigger this crash not only on login, but also by restarting i3 window manager or by changing xrandr configuration. In my case, the login crash was caused by calling xrandr from i3 config.
Indeed changing the resolution in xfce parameters crashes nm-applet.
This was fixed in i3 upstream by https://github.com/i3/i3/pull/4163 or https://github.com/i3/i3/pull/4147. I no longer have the issue with i3 4.18.3.
This requires a backport to 20.09 as far as I can tell
Most helpful comment
This requires a backport to 20.09 as far as I can tell