github-starred/firejail
2
0
Fork 0
mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00
Code Issues 531 Projects Packages Wiki Activity Actions 6

[GH-ISSUE #3379] thunderbird: keyboard does not work: Unable to connect to ibus #2124

New issue
Open
opened 2026-05-05 08:48:10 -06:00 by gitea-mirror · 27 comments
gitea-mirror commented 2026-05-05 08:48:10 -06:00
Owner
Copy link

Originally created by @fabianhick on GitHub (Apr 24, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3379

Hey,
after upgrading my installation to Ubuntu 20.04 I ran into the following issues:

Describe the bug
When running Thunderbird on Ubuntu 20.04 with firejail the keyboard input is broken.

Behavior change on disabling firejail
The keyboard input works as intended

To Reproduce
Steps to reproduce the behavior:

  1. Start Thunderbird: firejail --private thunderbird
  2. Try to enter something into the input fields
  3. See error in terminal:
(thunderbird:17): IBUS-WARNING **: 02:56:35.752: Unable to connect to ibus: Could not connect: Connection refused
(thunderbird:17): IBUS-WARNING **: 02:56:39.831: Events queue growing too big, will start to drop.
(thunderbird:17): IBUS-WARNING **: 02:56:39.877: Events queue growing too big, will start to drop.
(thunderbird:17): IBUS-WARNING **: 02:56:39.905: Events queue growing too big, will start to drop.

Expected behavior
Being able to input information with the keyboard.

Desktop (please complete the following information):

  • Ubuntu 20.04 LTS (focal)
firejail version 0.9.62

Compile time support:
	- AppArmor support is enabled
	- AppImage support is enabled
	- chroot support is enabled
	- file and directory whitelisting support is enabled
	- file transfer support is enabled
	- firetunnel support is enabled
	- networking support is enabled
	- overlayfs support is enabled
	- private-home support is enabled
	- seccomp-bpf support is enabled
	- user namespace support is enabled
	- X11 sandboxing support is enabled

Additional context
This issues also appears in gedit.

Originally created by @fabianhick on GitHub (Apr 24, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3379 Hey, after upgrading my installation to Ubuntu 20.04 I ran into the following issues: **Describe the bug** When running Thunderbird on Ubuntu 20.04 with firejail the keyboard input is broken. **Behavior change on disabling firejail** The keyboard input works as intended **To Reproduce** Steps to reproduce the behavior: 1. Start Thunderbird: `firejail --private thunderbird` 2. Try to enter something into the input fields 3. See error in terminal: ``` (thunderbird:17): IBUS-WARNING **: 02:56:35.752: Unable to connect to ibus: Could not connect: Connection refused (thunderbird:17): IBUS-WARNING **: 02:56:39.831: Events queue growing too big, will start to drop. (thunderbird:17): IBUS-WARNING **: 02:56:39.877: Events queue growing too big, will start to drop. (thunderbird:17): IBUS-WARNING **: 02:56:39.905: Events queue growing too big, will start to drop. ``` **Expected behavior** Being able to input information with the keyboard. **Desktop (please complete the following information):** - Ubuntu 20.04 LTS (focal) ``` firejail version 0.9.62 Compile time support: - AppArmor support is enabled - AppImage support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - firetunnel support is enabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled ``` **Additional context** This issues also appears in gedit. </details>
gitea-mirror commented 2026-05-05 08:48:12 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Apr 24, 2020):

Can you try firejail --ignore=nodbus thunderbird.

<!-- gh-comment-id:618857250 --> @rusty-snake commented on GitHub (Apr 24, 2020): Can you try `firejail --ignore=nodbus thunderbird`.
gitea-mirror commented 2026-05-05 08:48:12 -06:00
Author
Owner
Copy link

@fabianhick commented on GitHub (Apr 24, 2020):

@rusty-snake, I did try your command and the issue still persists.

<!-- gh-comment-id:618944765 --> @fabianhick commented on GitHub (Apr 24, 2020): @rusty-snake, I did try your command and the issue still persists.
gitea-mirror commented 2026-05-05 08:48:13 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 1, 2020):

I cannot reproduce this in a ubu-focal test VM with firejail-git.

<!-- gh-comment-id:622359790 --> @rusty-snake commented on GitHub (May 1, 2020): I cannot reproduce this in a ubu-focal test VM with firejail-git.
gitea-mirror commented 2026-05-05 08:48:14 -06:00
Author
Owner
Copy link

@JKjakay commented on GitHub (May 1, 2020):

I have the same problem. However, I do not use --private but instead just run:
firejail thunderbird

The firejailed TB works as usual, but does not accept keyboard input. The ibus warning shows up in the console - to be exact, one time for every keypress, I think.

<!-- gh-comment-id:622508072 --> @JKjakay commented on GitHub (May 1, 2020): I have the same problem. However, I do not use --private but instead just run: firejail thunderbird The firejailed TB works as usual, but does not accept keyboard input. The ibus warning shows up in the console - to be exact, one time for every keypress, I think.
gitea-mirror commented 2026-05-05 08:48:14 -06:00
Author
Owner
Copy link

@fabianhick commented on GitHub (May 1, 2020):

It doesn't work for me both with and without --private.
I can confirm @JKjakay's description of the issue in regards to keypresses.

<!-- gh-comment-id:622550159 --> @fabianhick commented on GitHub (May 1, 2020): It doesn't work for me both with and without `--private`. I can confirm @JKjakay's description of the issue in regards to keypresses.
gitea-mirror commented 2026-05-05 08:48:14 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 1, 2020):

Can you try with firejail --ignore=private-tmp --ignore=tracelog --ignore="shell none" --ignore=protocol --ignore=nogroups --ignore=noroot --ignore=machine-id. If this works, remove ignores till it breaks again.

<!-- gh-comment-id:622553676 --> @rusty-snake commented on GitHub (May 1, 2020): Can you try with `firejail --ignore=private-tmp --ignore=tracelog --ignore="shell none" --ignore=protocol --ignore=nogroups --ignore=noroot --ignore=machine-id`. If this works, remove ignores till it breaks again.
gitea-mirror commented 2026-05-05 08:48:15 -06:00
Author
Owner
Copy link

@fabianhick commented on GitHub (May 1, 2020):

Thanks for the new command, @rusty-snake.
Unfortunately the issue still persists:

(thunderbird:10): IBUS-WARNING **: 23:06:29.152: Unable to connect to ibus: Could not connect: Connection refused
<!-- gh-comment-id:622568714 --> @fabianhick commented on GitHub (May 1, 2020): Thanks for the new command, @rusty-snake. Unfortunately the issue still persists: ``` (thunderbird:10): IBUS-WARNING **: 23:06:29.152: Unable to connect to ibus: Could not connect: Connection refused ```
gitea-mirror commented 2026-05-05 08:48:15 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 2, 2020):

Then you will need to comment every thing in thunderbird.profile and uncomment line for line to find the problematic line. (You can also uncomment a block of line and only go line for line in the block with the problematic line).

<!-- gh-comment-id:622770800 --> @rusty-snake commented on GitHub (May 2, 2020): Then you will need to comment every thing in thunderbird.profile and uncomment line for line to find the problematic line. (You can also uncomment a block of line and only go line for line in the block with the problematic line).
gitea-mirror commented 2026-05-05 08:48:16 -06:00
Author
Owner
Copy link

@fabianhick commented on GitHub (May 2, 2020):

I did just try it out and commenting the line containing ignore nodbus in thunderbird.profile seems to solve the issue.
The initial error message (Unable to connect to ibus) still appears, but the Events queue isn't growing too big anymore and keyboard input is working again.

<!-- gh-comment-id:622930742 --> @fabianhick commented on GitHub (May 2, 2020): I did just try it out and commenting the line containing `ignore nodbus` in `thunderbird.profile` seems to solve the issue. The initial error message (Unable to connect to ibus) still appears, but the Events queue isn't growing too big anymore and keyboard input is working again.
gitea-mirror commented 2026-05-05 08:48:16 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 2, 2020):

So calling firejail (--private) --nodbus thunderbird works?

<!-- gh-comment-id:622931284 --> @rusty-snake commented on GitHub (May 2, 2020): So calling `firejail (--private) --nodbus thunderbird` works?
gitea-mirror commented 2026-05-05 08:48:16 -06:00
Author
Owner
Copy link

@fabianhick commented on GitHub (May 2, 2020):

Yes indeed, @rusty-snake.
But I also just noticed that the thunderbird.profile on GitHub is different to mine from the Ubuntu Focal package...

<!-- gh-comment-id:622931538 --> @fabianhick commented on GitHub (May 2, 2020): Yes indeed, @rusty-snake. But I also just noticed that the `thunderbird.profile` on GitHub is different to mine from the Ubuntu Focal package...
gitea-mirror commented 2026-05-05 08:48:17 -06:00
Author
Owner
Copy link

@JKjakay commented on GitHub (May 2, 2020):

Starting TB with

firejail --nodbus thunderbird

works for me, too

<!-- gh-comment-id:622938957 --> @JKjakay commented on GitHub (May 2, 2020): Starting TB with `firejail --nodbus thunderbird` works for me, too
gitea-mirror commented 2026-05-05 08:48:17 -06:00
Author
Owner
Copy link

@paddyredbeard commented on GitHub (May 2, 2020):

FWIW - I was having exactly the same issue with Chromium browser on a fresh upgrade to Pop!_OS 20.04 (based on Ubuntu 20.04). Per @JKjakay's comment, firejail --nodbus chromium resolves this for me.

<!-- gh-comment-id:622966621 --> @paddyredbeard commented on GitHub (May 2, 2020): FWIW - I was having exactly the same issue with Chromium browser on a fresh upgrade to Pop!_OS 20.04 (based on Ubuntu 20.04). Per @JKjakay's comment, `firejail --nodbus chromium` resolves this for me.
gitea-mirror commented 2026-05-05 08:48:18 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (May 10, 2020):

I had this issue with several applications (Thunderbird, Firefox, Vivaldi, Brave, Text-Editor).
Using the --nodbus parameter helped (unless it's explicitely blocked like for Firefox, see issue https://github.com/netblue30/firejail/issues/3408). Alternatively changing the profile files also helped (commenting out all dbus related lines in the main profile file)

Running it on Ubuntu 18.04

<!-- gh-comment-id:626369944 --> @ghost commented on GitHub (May 10, 2020): I had this issue with several applications (Thunderbird, Firefox, Vivaldi, Brave, Text-Editor). Using the --nodbus parameter helped (unless it's explicitely blocked like for Firefox, see issue https://github.com/netblue30/firejail/issues/3408). Alternatively changing the profile files also helped (commenting out all dbus related lines in the main profile file) Running it on Ubuntu 18.04
gitea-mirror commented 2026-05-05 08:48:18 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 10, 2020):

Unfortunately we still do not know what the real reason is, or how it can be fixed. Blocking D-Bus breaks dconf and other things. It will not work with all programs.

<!-- gh-comment-id:626370688 --> @rusty-snake commented on GitHub (May 10, 2020): Unfortunately we still do not know what the real reason is, or how it can be fixed. Blocking D-Bus breaks dconf and other things. It will not work with all programs.
gitea-mirror commented 2026-05-05 08:48:19 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 22, 2020):

@buggitheclown @paddyredbeard @JKjakay @fabianhick can you try this: https://github.com/netblue30/firejail/issues/116#issuecomment-632394043

<!-- gh-comment-id:632635027 --> @rusty-snake commented on GitHub (May 22, 2020): @buggitheclown @paddyredbeard @JKjakay @fabianhick can you try this: https://github.com/netblue30/firejail/issues/116#issuecomment-632394043
gitea-mirror commented 2026-05-05 08:48:19 -06:00
Author
Owner
Copy link

@paddyredbeard commented on GitHub (May 22, 2020):

@rusty-snake GTK_IM_MODULE=xim firejail chromium works for me.

<!-- gh-comment-id:632694704 --> @paddyredbeard commented on GitHub (May 22, 2020): @rusty-snake `GTK_IM_MODULE=xim firejail chromium` works for me.
gitea-mirror commented 2026-05-05 08:48:19 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 22, 2020):

ok, I'm now able to reproduce it. Ubuntu 20.04 (minimal) VM with firejail-git.

$ LC_ALL=C firejail --env=GTK_IM_MODULE=ibus --noprofile gedit
Parent pid 3034, child pid 3035
Child process initialized in 41.73 ms

(gedit:2): IBUS-WARNING **: 18:01:11.426: Unable to connect to ibus: Could not connect: Connection refused

(gedit:2): IBUS-WARNING **: 18:01:14.737: Events queue growing too big, will start to drop.

(gedit:2): IBUS-WARNING **: 18:01:14.746: Events queue growing too big, will start to drop.

(gedit:2): IBUS-WARNING **: 18:01:14.770: Events queue growing too big, will start to drop.

(gedit:2): IBUS-WARNING **: 18:01:14.815: Events queue growing too big, will start to drop.

Parent is shutting down, bye...

Thats are bad news, because it is broken even with --noprofile.

Knowed work arounds:

  • nodbus/dbus-user none or net none, both don't work for all programs
  • env GTK_IM_MODULE=xim and env QT_IM_MODULE=xim
<!-- gh-comment-id:632778490 --> @rusty-snake commented on GitHub (May 22, 2020): ok, I'm now able to reproduce it. Ubuntu 20.04 (minimal) VM with firejail-git. ``` $ LC_ALL=C firejail --env=GTK_IM_MODULE=ibus --noprofile gedit Parent pid 3034, child pid 3035 Child process initialized in 41.73 ms (gedit:2): IBUS-WARNING **: 18:01:11.426: Unable to connect to ibus: Could not connect: Connection refused (gedit:2): IBUS-WARNING **: 18:01:14.737: Events queue growing too big, will start to drop. (gedit:2): IBUS-WARNING **: 18:01:14.746: Events queue growing too big, will start to drop. (gedit:2): IBUS-WARNING **: 18:01:14.770: Events queue growing too big, will start to drop. (gedit:2): IBUS-WARNING **: 18:01:14.815: Events queue growing too big, will start to drop. Parent is shutting down, bye... ``` Thats are bad news, because it is broken even with `--noprofile`. Knowed work arounds: - `nodbus`/`dbus-user none` or `net none`, both don't work for all programs - `env GTK_IM_MODULE=xim` and `env QT_IM_MODULE=xim`
gitea-mirror commented 2026-05-05 08:48:20 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 22, 2020):

Problematic strace line (strace -f):
connect(14, {sa_family=AF_UNIX, sun_path=@"/home/ubuntu01/.cache/ibus/dbus-AyGV49uw"}, 41) = -1 ECONNREFUSED (Connection refused)

Looks like ibus is rejecting the connection. Maybe because of the PID-namespace?

<!-- gh-comment-id:632779468 --> @rusty-snake commented on GitHub (May 22, 2020): Problematic strace line (strace -f): `connect(14, {sa_family=AF_UNIX, sun_path=@"/home/ubuntu01/.cache/ibus/dbus-AyGV49uw"}, 41) = -1 ECONNREFUSED (Connection refused)` Looks like ibus is rejecting the connection. Maybe because of the PID-namespace?
gitea-mirror commented 2026-05-05 08:48:20 -06:00
Author
Owner
Copy link

@ghost commented on GitHub (May 23, 2020):

@rusty-snake

That workaround you linked doesn't work for me. I tried creating the signal-desktop file in my home directory and using the console command like @paddyredbeard
So far using --noprofile --nodbus worked with all programs that had the issue for me.
EDIT: I changed my user name so don't be surprised why a new name showed up in the convo

<!-- gh-comment-id:632990419 --> @ghost commented on GitHub (May 23, 2020): @rusty-snake That workaround you linked doesn't work for me. I tried creating the signal-desktop file in my home directory and using the console command like @paddyredbeard So far using --noprofile --nodbus worked with all programs that had the issue for me. EDIT: I changed my user name so don't be surprised why a new name showed up in the convo
gitea-mirror commented 2026-05-05 08:48:21 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (May 23, 2020):

electron doesn't use gtk, maybe QT_IM_MODULE=xim works.

<!-- gh-comment-id:632998471 --> @rusty-snake commented on GitHub (May 23, 2020): electron doesn't use gtk, maybe `QT_IM_MODULE=xim` works.
gitea-mirror commented 2026-05-05 08:48:21 -06:00
Author
Owner
Copy link

@wellcomez commented on GitHub (Oct 17, 2022):

@rusty-snake for my case, I think this caused by multi ibus configuration file under ~/.config/ibus/bus/ and one of them contains wrong socket address.

<!-- gh-comment-id:1280950026 --> @wellcomez commented on GitHub (Oct 17, 2022): @rusty-snake for my case, I think this caused by multi ibus configuration file under ~/.config/ibus/bus/ and one of them contains wrong socket address.
gitea-mirror commented 2026-05-05 08:48:21 -06:00
Author
Owner
Copy link

@rusty-snake commented on GitHub (Oct 17, 2022):

What do you mean with "wrong address"?

<!-- gh-comment-id:1281034104 --> @rusty-snake commented on GitHub (Oct 17, 2022): What do you mean with "wrong address"?
gitea-mirror commented 2026-05-05 08:48:22 -06:00
Author
Owner
Copy link

@wellcomez commented on GitHub (Oct 20, 2022):

What do you mean with "wrong address"?
wrong means it doesn't exis in.

<!-- gh-comment-id:1285096122 --> @wellcomez commented on GitHub (Oct 20, 2022): > What do you mean with "wrong address"? wrong means it doesn't exis in.
gitea-mirror commented 2026-05-05 08:48:22 -06:00
Author
Owner
Copy link

@wellcomez commented on GitHub (Nov 16, 2022):

What do you mean with "wrong address"?

  • i found there are several ibus_addres_file under .config/ibus/bus. One of them will be chosen by firejail and used as ibus_address.
    Maybe it looks right because its filename is confirmed with naming rule, but really it doesn't point to living unix socket.
    After i remove all these files ,keyboard works. After reboot again, new ibus_address file appears, then try gedit again, it also works.
  • Another finding:
    I use ss i can find ibus_address used by system is different with ibus_address which is set to sandbox by firejail.
<!-- gh-comment-id:1316225215 --> @wellcomez commented on GitHub (Nov 16, 2022): > What do you mean with "wrong address"? - i found there are several ibus_addres_file under .config/ibus/bus. One of them will be chosen by firejail and used as ibus_address. Maybe it looks right because its filename is confirmed with naming rule, but really it doesn't point to living unix socket. After i remove all these files ,keyboard works. After reboot again, new ibus_address file appears, then try gedit again, it also works. - Another finding: I use ss i can find ibus_address used by system is different with ibus_address which is set to sandbox by firejail.
gitea-mirror commented 2026-05-05 08:48:23 -06:00
Author
Owner
Copy link

@vaindru commented on GitHub (Jan 8, 2024):

* i found there are several ibus_addres_file under .config/ibus/bus. One of them will be chosen by firejail and used as ibus_address.
  Maybe it looks right because  its filename is confirmed with naming rule, but really it doesn't point to living unix socket.
  **After i remove all these files ,keyboard  works**. After reboot again, new ibus_address file appears, then try gedit again, it also works.

* Another finding:
  I use ss i can find ibus_address used by system is different with ibus_address which is set to sandbox by firejail.

This saved me! Firefox didn't recognize keyboard input and also a friend had another editor software with same problem and it helped too. Thanks!:)

<!-- gh-comment-id:1880938440 --> @vaindru commented on GitHub (Jan 8, 2024): > * i found there are several ibus_addres_file under .config/ibus/bus. One of them will be chosen by firejail and used as ibus_address. > Maybe it looks right because its filename is confirmed with naming rule, but really it doesn't point to living unix socket. > **After i remove all these files ,keyboard works**. After reboot again, new ibus_address file appears, then try gedit again, it also works. > > * Another finding: > I use ss i can find ibus_address used by system is different with ibus_address which is set to sandbox by firejail. This saved me! Firefox didn't recognize keyboard input and also a friend had another editor software with same problem and it helped too. Thanks!:)
gitea-mirror commented 2026-05-05 08:48:23 -06:00
Author
Owner
Copy link

@wazaberry commented on GitHub (Aug 4, 2024):

Thanks a lot Welcomez... deleting .config/ibus/bus did the trick and the keyboard now works in Firefox :)

<!-- gh-comment-id:2267595585 --> @wazaberry commented on GitHub (Aug 4, 2024): Thanks a lot Welcomez... deleting .config/ibus/bus did the trick and the keyboard now works in Firefox :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
serialize_remounts_v2
landlock_v4
landlock
release-0.9.64
release-0.9.62
gitlab_ci
LTSbase
fred_ctests
docs
0.9.80
0.9.80-rc1
0.9.78
0.9.76
0.9.76-rc4
0.9.76-rc3
0.9.76-rc2
0.9.76-rc1
0.9.74
landlock-split
0.9.72
0.9.72rc1
0.9.70
0.9.68
0.9.68rc1
0.9.66
0.9.66rc1
0.9.64.4
0.9.64.2
0.9.64
0.9.64rc1
0.9.62.4
0.9.62.2
0.9.62
0.9.56.2-LTS
0.9.60
0.9.60-rc1
0.9.58.2
0.9.58
0.9.58-rc1
0.9.56-LTS-release
0.9.56-LTS
0.9.56
0.9.56-rc1
0.9.54
0.9.54-rc2
0.9.54-rc1
0.9.52
0.9.38.12
0.9.50
0.9.50-rc1
0.9.48
0.9.46
0.9.46-rc1
0.9.44.10
0.9.44.8
0.9.44.6
0.9.38.10
0.9.44.4
0.9.38.8
0.9.44.2
0.9.44
0.9.44-rc1
0.9.38.4
0.9.42
0.9.42-rc2
0.9.38.2
0.9.42-rc1
disable-globalcfg
0.9.40
0.9.40-rc1
0.9.38
0.9.38-rc1
0.9.36
0.9.36-rc1
0.9.34
0.9.34-rc1
0.9.32
0.9.32-rc1
0.9.30
0.9.30-rc1
Labels
Clear labels   
LTS merge

   
LTS merge

   
bug

   
bug

   
converted-to-discussion

   
doc-todo

   
documentation

   
duplicate

   
enhancement

   
file-transfer

   
firecfg

   
firejail-in-firejail

   
firetools

   
graphics

   
help wanted

   
information_old

   
installation

   
invalid

   
modif

   
moved

   
needinfo

   
networking

   
notabug

   
notourbug

   
old-version

   
overlayfs

   
packaging

   
profile-request

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question_old

   
removal

   
runtime-permissions

   
sandbox-ipc

   
security

   
stale

   
wiki

   
wiki

   
wontfix

   
wordpress

   
workaround
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2124
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?