Crash when attempting to print note (Ubuntu 22.04, deb package)

Rando_User · May 27, 2022, 9:26pm

[ X ] I have checked the troubleshooting

Bug report

Linux app crashes when attempting to print any note.

Terminal output:

[bugsnag] Loaded!
  app:info Initializing inkdrop app.. +0ms
  app:info Arguments: /usr/lib/inkdrop/inkdrop +3ms
  app:info Starting inkdrop app.. +97ms
  app:info axios default config: { proxy: false, httpAgent: undefined, httpsAgent: undefined } +41ms
  app:info Starting a session +104ms
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[1225358:0527/130248.154167:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
Crashing due to FD ownership violation:
#0 0x565460471b03 <unknown>
#1 0x56546051ab5c <unknown>
#2 0x56546051ab21 <unknown>
#3 0x7f976dca4ef3 <unknown>
Trace/breakpoint trap

Environment

Platform: Ubuntu
Platform version: 22.04 LTS (GNOME 42)
App Version: 5.5.1

How to reproduce

Install Inkdrop from DEB package on Ubuntu 22.04 LTS.
Try to print a note with Ctrl+Shift+P.
App window darkens, (GNOME “Force Quit”/“Wait” dialog may appear) then app crashes.

craftzdog · May 29, 2022, 1:44am

Hi Rando,

Thanks for the report.
Looks like a bug in Electron 16:

github.com/microsoft/vscode

Linux CI: Crashing due to FD ownership violation

opened 10:16AM - 14 Feb 22 UTC

closed 12:50PM - 14 Feb 22 UTC

bpasero

linux engineering electron-16-update

Lately in Linux CI I see a lot of these errors appearing, I think ever since we …updated to E16 https://dev.azure.com/monacotools/Monaco/_build/results?buildId=155814&view=logs&j=963754b8-394e-5caf-de5d-2790b068caec&t=a5663145-e9fb-5b6a-6210-7b66b21662a2&l=15786 ``` [0214/091827.609331:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0214/091827.610195:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2) [0214/091827.610226:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2) [4153:0214/091827.719417:ERROR:bus.cc(393)] Failed to connect to the bus: /usr/bin/dbus-launch terminated abnormally with the following error: Crashing due to FD ownership violation: #0 0x55a004e3b463 <unknown> #1 0x55a004ee238c <unknown> #2 0x55a004ee2351 <unknown> #3 0x7f8e74a5a395 <unknown> #4 0x55a004ee542b <unknown> #5 0x24c21e8d984b8800 <unknown> #6 0x7ffc3e614f98 <unknown> #7 0x7ffc3e615530 <unknown> #8 0x55a005bb85c6 <unknown> #9 0x55a005bb8c2b <unknown> #10 0x55a002830eee <unknown> #11 0x55a002822c13 <unknown> #12 0x55a0026e6460 <unknown> #13 0x55a003e5a735 <unknown> #14 0x185200080eb8 <unknown> #15 0x18520000c761 <unknown> #16 0x18520009eb8d <unknown> #17 0x18520000c761 <unknown> #18 0x18520000c761 <unknown> #19 0x18520000c761 <unknown> #20 0x1852002d28af <unknown> #21 0x1852002e6c4e <unknown> #22 0x18520000a75c <unknown> #23 0x18520000a487 <unknown> #24 0x55a003f17b28 <unknown> #25 0x55a003f16f8a <unknown> #26 0x55a003e0fa2e <unknown> #27 0x55a00846a192 <unknown> ```

Will be planning to upgrade to the latest version in the future as it involves significant breaking changes.

craftzdog · June 1, 2022, 7:58am

I’ve tried to reproduce it on Ubuntu 22.04 but it didn’t crash. My environment:

❯ uname -a
Linux ubuntu 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

So, looks like it’s not an Electron’s bug. It could be an environment-dependent issue.
I can see it failed to initialize a sandbox in your error log.
Can you please try running Inkdrop with --disable-gpu-sandbox option?

Rando_User · June 2, 2022, 6:00am

Still crashes.

[bugsnag] Loaded!
  app:info Initializing inkdrop app.. +0ms
  app:info Arguments: /usr/lib/inkdrop/inkdrop +3ms
  app:info Arguments: --disable-gpu-sandbox +0ms
  app:info Starting inkdrop app.. +103ms
  app:info axios default config: { proxy: false, httpAgent: undefined, httpsAgent: undefined } +52ms
  app:info Starting a session +108ms
Crashing due to FD ownership violation:
#0 0x5604ac7eab03 <unknown>
#1 0x5604ac893b5c <unknown>
#2 0x5604ac893b21 <unknown>
#3 0x7f050d575ef3 <unknown>
Trace/breakpoint trap

Joplin (AppImage) also seems to be using Electron and has a similar crash when I attempt to print. It doesn’t recognize the “–disable-gpu-sandbox” flag, so I ran without it:

xdg-settings: invalid application name
Try 'xdg-settings --help' for more information.
mesa: for the --simplifycfg-sink-common option: may only occur zero or one times!
mesa: for the --global-isel-abort option: may only occur zero or one times!
mesa: for the --amdgpu-atomic-optimizations option: may only occur zero or one times!
[3192602:0601/215615.190912:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
(node:3192561) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(Use `@joplinapp-desktop --trace-warnings ...` to show where the warning was created)
(node:3192561) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
(node:3192561) electron: The default of nativeWindowOpen is deprecated and will be changing from false to true in Electron 15.  See https://github.com/electron/electron/issues/28511 for more information.
Crashing due to FD ownership violation:
#0 0x55f45fc54f83 <unknown>
#1 0x55f45fcfbfbc <unknown>
#2 0x55f45fcfbf81 close
#3 0x7f25b7cfbef3 <unknown>

craftzdog · June 3, 2022, 6:05am

Thanks for the report.
Yeah, it might be a bug in Electron but not resolved yet because it randomly happens:

github.com/electron/electron

[Bug]: `window.print()` without printers causes the main process to crash

opened 03:50PM - 27 Sep 21 UTC

andsmedeiros

platform/linux bug

14-x-y

### Preflight Checklist - [x] I have read the [Contributing Guidelines](https:/…/github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project. - [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to. - [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success. ### Electron Version 14.0.1 ### What operating system are you using? Ubuntu ### Operating System Version 5.11.0-37-generic #41-Ubuntu SMP Mon Sep 20 16:39:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux ### What arch are you using? x64 ### Last Known Working Electron version 13.4.0 ### Expected Behavior Calling `window.print()` should open the print window, even if there are no printers installed in the system. ### Actual Behavior Calling `window.print()` from the renderer process crashes the main process. ### Testcase Gist URL https://gist.github.com/85a5466567215173419a17982e79becb ### Additional Information When the process crashes, the terminal prints: ```Crashing due to FD ownership violation: #0 0x5616b9f1e143 <unknown> #1 0x5616b9fc517c <unknown> #2 0x5616b9fc5141 close #3 0x7f4c4568817b <unknown> Failed to get crash dump id. Report Id: --2021-09-27 12: Failed to get crash dump id. Report Id: --2021-09-27 12: PATH/TO/PROJECT/node_modules/electron/dist/electron exited with signal SIGILL ``` When calling `BrowserWindow.print()`, the console prints: `[22590:0927/121740.971531:ERROR:print_backend_cups.cc(218)] CUPS: Error getting default printer: No destinations added.` and the print callback *is* called with `[ false, 'no valid printers available' ]` for args. The main process does not crash, but the print window never opens (I have filed a similar issue back at v10.x: https://github.com/electron/electron/issues/25498) On v13.4.0, a similar error message is printed, but the process does not crashes (or does, but recovers immediately somehow): ``` Crashing due to FD ownership violation: #0 0x564e03bc1143 <unknown> #1 0x564e03c6817c <unknown> #2 0x564e03c68141 close #3 0x7f20e79ea17b <unknown> Electron exited with signal SIGTRAP. Saving files to temp directory... Saved files to /tmp/tmp-18241-0f2HhywGTnpu Electron v13.4.0 started. ``` Also, the print window is correctly displayed, containing only the 'Print to File' option.