Ipdl protocol error handler returned error code

Bugzilla Categories (Thunderbird :: General, defect) Tracking (Not tracked) Tracking Status thunderbird_esr91 thunderbird_esr102 thunderbird109 thunderbird110 thunderbird111 People (Reporter: riegler.b, Unassigned) References Details wanted-thunderbird sec-bounty sec-bounty-hof in-qa-testsuite Crash Data Security (public) User Story Description User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Steps to reproduce: on platform GNU/Linux Ubuntu 20.04 LTS install of […]

Содержание

  1. Bugzilla
  2. Categories
  3. (Thunderbird :: General, defect)
  4. Tracking
  5. (Not tracked)
  6. People
  7. (Reporter: riegler.b, Unassigned)
  8. References
  9. Details
  10. Crash Data
  11. Security
  12. (public)
  13. User Story
  14. Description
  15. Updated
  16. Updated
  17. Comment 1
  18. Selenium does not set firefox profile — python #6592
  19. Comments
  20. Bugzilla
  21. Categories
  22. (Firefox :: Untriaged, defect)
  23. Tracking
  24. People
  25. (Reporter: ishikawa, Unassigned)
  26. References
  27. Details
  28. Crash Data
  29. Security
  30. (public)
  31. User Story
  32. Description
  33. Bugzilla
  34. Categories
  35. (Thunderbird :: General, defect)
  36. Tracking
  37. (Not tracked)
  38. People
  39. (Reporter: sm1179844, Unassigned)
  40. References
  41. Details
  42. Crash Data
  43. Security
  44. (public)
  45. User Story
  46. Description

Bugzilla

Categories

(Thunderbird :: General, defect)

Tracking

(Not tracked)

Tracking Status
thunderbird_esr91
thunderbird_esr102
thunderbird109
thunderbird110
thunderbird111

People

(Reporter: riegler.b, Unassigned)

References

Details

Crash Data

Security

(public)

User Story

Description

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

on platform GNU/Linux Ubuntu 20.04 LTS install of thunderbird 91.0.1 into
$HOME/thunderbird/
start CLI: $HOME/thunderbird/thunderbird &

thunderbird 91.0.1 is working and doing my normal email work.

during working there are in the start shell (bash) repeated messages:
IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

in a run-time product there should not be any debugging messages,
therefore I consider this a real bug. It is with the latest version 91.0.1

Updated

Updated

after update to 91.1.0 same messages remain.

$ tb
IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Источник

Selenium does not set firefox profile — python #6592

System
windows:10
Selenium:3.14
Python:3.7
Gecodriver:0.23

Expection:
Open the firefox with test profile

Issue:
Open the firefox with default profile
Create a temp profile folder to temp folder

Has anyone have any idea !

Thanks in Advance

The text was updated successfully, but these errors were encountered:

the configuration option below works for assigning profile to geckodriver but this time it refuses connection

Expection:
Opens the firefox and remote control

Happining:
Opens the firefox and fires connection error

Thanks in Advance

in this last example, options should be an instance of selenium.webdriver.firefox.options.Options() .. where are you creating it?

Sorry about code,i missed a line there.It is like this actually .

1541767559696 mozrunner::runner INFO Running command: «C:UsersAppDataLocalMozilla Firefoxfirefox.exe» «-marionette» «-profile» «C:UsersAppDataRoamingMozillaFirefoxProfilesdnm8f0kz.default-1541758576709» «-foreground» «-no-remote» IPDL protocol error: Handler returned error code!

. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was
deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was
deserialized, but the handler returned false (indicating failure)

Источник

Bugzilla

Categories

(Firefox :: Untriaged, defect)

Tracking

a11y-review
Webcompat Priority
Performance Impact
Tracking Status
relnote-firefox
firefox-esr102
firefox109
firefox110
firefox111

People

(Reporter: ishikawa, Unassigned)

References

Details

Crash Data

Security

(public)

User Story

Description

I am not sure if my problem is Debian GNU/Linux specific or not, but here it goes to share my experience under linux.

firefox-esr 68.2.0.ESR startup error under Debian GNU/Linux

My debian kernel version is:
$ uname -a
Linux ip030 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-09-26) x86_64 GNU/Linux

I am using a testing package of Debian. So, that may be one of the reasons of ill-behavior.

I could use the installed Firefox ESR version (not sure which it was) a few days ago.

(1) I upgraded my Debian GNU/Linux packages, and firefox seemed to
updated itself some days ago or yesterday, I am not sure when.

When I tried to run Firefox for the first time after these events by
invoking it from the application menu maybe for the first time in a
few days, Firefox was not usable because any tab including the startup
tab(s) that I wanted to create crashed, and firefox displayed the
error message and offered to close the tab or restore the tab.

Since the tab(s) crashed immediately after startup, if I closed the
tab, Firefox terminated.
If I tried to restore the tabs, this again resulted in the same tab
crashing dialog screen page. There was no way out.

(2) Another bug I noticed is incorrect link in the help dialog.

I get Page not found error when I clicked on the «What’s New» link:

HELP -> About Firefox -> What’s New link

I get Page not Found error.

If I delete the «/und» part manually and hit return in the URL bar,
I think the correct page s being accessed.
(I am not sure if the incorrect URL is Debian-specific or originated
in the mozilla binary.)

In then accessed page I see clearly the following message. So it IS
the release note.

Firefox ESR
Release Notes

Release Notes tell you what’s new in Firefox. As always, we welcome
your feedback. You can also file a bug in Bugzilla or see the system
requirements of this release.

68.2.0
Firefox ESR

October 22, 2019
Version 68.2.0, first offered to ESR channel users on October 22, 2019

Observed ERROR messages:
While the error in (1) was observed, I saw something like the following (quoted/pasted at the end of this comment) in the startup console where I typed /usr/bin/firefox-esr

I found a solution by accident. I have no idea if this works for everybody.

I tried to restart Firefox after disabling plugin, i.e., safe-mode from the firefox tool menu.
This operation failed again and no window was created.
Usually Firefox restart after disabling plugins. But I saw no such
window and there does not seem to be any live firefox process anymore.

ps axg | grep firefox

did not show firefox process.

So, after this, I ran firefox-esr again by typing the command line
this time. To my relief, this time no «tab(s) crashed» error screen
appeared, and I can access google search, for example eventually.
Something, maybe some profile or whatever, was changed for the better
(?) is my best guess.

Just thought to share my experience.

Note; Some error messages that appeared on the command tty window where I
typed firefox-esr to start Firefox.

Error messages during the time when I observed the error (1) above:

$ firefox-esr
IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

[Parent 6980, Gecko_IOThread] WARNING: pipe error (104): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 6980, Gecko_IOThread] WARNING: pipe error (103): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Child 7483, Chrome_ChildThread] WARNING: pipe error (3): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358

###. [Child][MessageChannel] Error: (msgtype=0x530005,name=PHttpChannel::Msg_Cancel) Closed channel: cannot send/recv

[Parent 6980, Gecko_IOThread] WARNING: pipe error (114): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358

###. [Parent][MessageChannel] Error: (msgtype=0x1E008F,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv

###. [Child][MessageChannel] Error: (msgtype=0x35011D,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv

[Parent 6980, Gecko_IOThread] WARNING: pipe error (65): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 6980, Gecko_IOThread] WARNING: pipe error (187): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
ishikawa@ip030:/NREF-COMM-CENTRAL/mozilla$ firefox-esr
[Parent 7708, Gecko_IOThread] WARNING: pipe error (109): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 7708, Gecko_IOThread] WARNING: pipe error (51): Connection reset by peer: file /build/firefox-esr-7jzoEE/firefox-esr-68.2.0esr/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358

###. [Parent][MessageChannel] Error: (msgtype=0x1E008F,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv

###. [Child][MessageChannel] Error: (msgtype=0x35011D,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv

(I have no idea if there was any virtual memory issue or something, but if so, firefox would print out memory error message.)

Источник

Bugzilla

Categories

(Thunderbird :: General, defect)

Tracking

(Not tracked)

Tracking Status
thunderbird_esr91
thunderbird_esr102
thunderbird109
thunderbird110
thunderbird111

People

(Reporter: sm1179844, Unassigned)

References

Details

Crash Data

Security

(public)

User Story

Description

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

when run in console, it gives this

[calBackendLoader] Using Thunderbird’s libical backend
[LDAPModuleLoader] Using LDAPDirectory.jsm
[MsgSendModuleLoader] Using MessageSend.jsm
[SmtpModuleLoader] Using SmtpService.jsm
console.warn: «[l10nregistry] Attempting to synchronously load filen resource:///chrome/en-US/locale/en-US/calendar/messenger/otr/otrUI.ftl while it’s being loaded asynchronously.»
console.debug: «Trying to load /usr/lib64/thunderbird/libotr.so»
console.debug: «Trying to load libotr.so from system’s standard library locations»
console.debug: «Successfully loaded OTR library libotr.so from system’s standard library locations»
console.debug: «Successfully loaded OpenPGP library librnp.so version 0.15.2+git20210806.dd923a4e.MZLA from /usr/lib64/thunderbird/librnp.so»
console.debug: «Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)»
console.warn: services.settings: thunderbird/hijack-blocklists has signature disabled
IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###. [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Источник

Adblock
detector

Источник


Closed

Bug 1727509


Opened 2 years ago
Closed 1 year ago

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

on platform GNU/Linux Ubuntu 20.04 LTS install of thunderbird 91.0.1 into
$HOME/thunderbird/
start CLI: $HOME/thunderbird/thunderbird &

thunderbird 91.0.1 is working and doing my normal email work.

Actual results:

during working there are in the start shell (bash) repeated messages:
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Expected results:

in a run-time product there should not be any debugging messages,
therefore I consider this a real bug. It is with the latest version 91.0.1

after update to 91.1.0 same messages remain.

bernie@prod:~$ tb
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Also happens on Linux Mint 20.2 Cinnamon.

Component: Untriaged → General

Status: UNCONFIRMED → RESOLVED

Closed: 1 year ago

Resolution: — → DUPLICATE

Источник

Thunderbird 91.3.1

If I start Thunderbird from the terminal, and then select any email message to read, I see the following error…

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Google doesn’t give any real clue about what an «IPDL protocol error» is.

To troubleshoot, I logged into a separate Ubuntu account where Thunderbird had never been used. I started Thunderbird from the terminal and created a mail account using one of my Google gmail accounts. Read any message, and got the same problem. So it’s not an account-specific problem.

Partial log from terminal…

~$ thunderbird
[calBackendLoader] Using Thunderbird's libical backend
[LDAPModuleLoader] Using LDAPDirectory.jsm
[MsgSendModuleLoader] Using MessageSend.jsm
[SmtpModuleLoader] Using SmtpService.jsm
console.debug: WebExtensions: 
  Compact Headers loaded
1642775310275   tbsortfolders.folderPane    DEBUG   Init
1642775310275   tbsortfolders.folderPane    DEBUG   Add observer
console.debug: "Trying to load /usr/lib/thunderbird/libotr.so"
console.debug: "Trying to load libotr.so from system's standard library locations"
console.debug: "Trying to load libotr.so.5 from system's standard library locations"
console.debug: "Successfully loaded OTR library libotr.so.5 from system's standard library locations"
console.debug: "Successfully loaded OpenPGP library librnp.so version 0.15.2+git20210806.dd923a4e.MZLA from /usr/lib/thunderbird/librnp.so"
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 unprotected)"
console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 from system's standard library locations"
console.debug: "gpgme version: 1.14.0-unknown"

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Any ideas what this error is about?

Источник

So I keep getting this before it stops losing focus.

[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3
[GFX1-]: (gfxWindowsPlatform) scheduled device update.
[GFX1-]: LayerManager::EndTransaction skip RenderLayer().
[GFX1-]: GFX: D3D11 skip BeginFrame with device-removed.
[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3
[GFX1-]: (gfxWindowsPlatform) scheduled device update.
[GFX1-]: LayerManager::EndTransaction skip RenderLayer().
[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3
[GFX1-]: (gfxWindowsPlatform) scheduled device update.
[GFX1-]: LayerManager::EndTransaction skip RenderLayer().
[GFX1-]: (gfxWindowsPlatform) Detected device reset: 3
[GFX1-]: (gfxWindowsPlatform) scheduled device update.
[GFX1-]: LayerManager::EndTransaction skip RenderLayer().
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer
 Processing error: message was deserialized, but the handler returned false (ind
icating failure)
Источник

#1 2019-03-27 00:58:42

merilius
Member
Registered: 2012-06-15
Posts: 33

[SOLVED] cannot add firefox extensions under Plasma

I have a strange problem with firefox. When I want to add an extension a popup from the address bar appears with options to either add or to cancel adding an extension.
Whatever I click it does nothing. The popup remains, the extension is not installed and the only way to close this popup is to close the tab or refresh the page. (Cancelling does not work either)
Strangely this does not happen under Gnome or LxQt+compiz! I don’t get it.
I tried disabling various desktop effects, but it did not help.

Edit: I tried LxQt + kwin and managed to reproduce it under LxQt this way! So it is some kind of kwin problem… Or firefox…

http://serwer.sucha.eu/~balwierz/tmp/fi … orking.png

EDIT, SOLVED:
It is the mouse cursor focus policy. I had it set all the way to the right (focus strictly follows cursor, like in the old X11 days). Set it to anything lower than this to resolve the issue.
Apparently these firefox popup windows (extension adding, notification questions) are not typical windows and are not dealt with by kwin well when focusPolicy == 3.

Last edited by merilius (2019-03-29 13:47:40)

#3 2019-03-27 12:42:02

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,652

Re: [SOLVED] cannot add firefox extensions under Plasma

please start firefox from terminal in one of the problem cases, try to add an extension and close firefox.
post the terminal output.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

#4 2019-03-27 12:47:14

merilius
Member
Registered: 2012-06-15
Posts: 33

Re: [SOLVED] cannot add firefox extensions under Plasma

Console output from firefox. All messages appeared at closing time.

[Parent 22724, Gecko_IOThread] WARNING: pipe error (48): Connection reset by peer: file /build/firefox/src/mozilla-unified/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)

[Parent 22724, Gecko_IOThread] WARNING: pipe error (114): Connection reset by peer: file /build/firefox/src/mozilla-unified/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 357

Last edited by merilius (2019-03-27 12:48:38)

#5 2019-03-27 12:54:47

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 10,652

Re: [SOLVED] cannot add firefox extensions under Plasma

These look relevant
https://stackoverflow.com/questions/506 … e#50703960

https://bugzilla.mozilla.org/show_bug.cgi?id=1410187

especially comment 11 & 12 from the mozilla bug report.

Does disabling compositing temporarily help ?

post lspci -k please

Last edited by Lone_Wolf (2019-03-27 13:01:46)

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

#6 2019-03-27 13:26:33

merilius
Member
Registered: 2012-06-15
Posts: 33

Re: [SOLVED] cannot add firefox extensions under Plasma

The second link is about firefox for windows, no extension popup mentioned, youtube links are dead.
The first one claims that the issue is fixed in nightly. It isn’t for me

This is what I get from nightly:

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PLayerTransaction::Msg_ReleaseLayer Processing error: message was deserialized, but the handler returned false (indicating failure)
###!!! [Parent][MessageChannel] Error: (msgtype=0x1F0088,name=PBrowser::Msg_Destroy) Closed channel: cannot send/recv
###!!! [Child][MessageChannel] Error: (msgtype=0x360114,name=PContent::Msg_DetachBrowsingContext) Closed channel: cannot send/recv

I disabled compositing by unchecking  system settings -> compositor settings and desktop effect -> enable compositor on startup
and by logging out and back in.
It did not help.

$ lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
	Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
	Kernel driver in use: skl_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
	Kernel driver in use: pcieport
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
	Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
	Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family MEI Controller
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
	Subsystem: ASUSTeK Computer Inc. Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
	Kernel driver in use: ahci
	Kernel modules: ahci
00:1b.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 (rev f1)
	Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
	Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller (rev 31)
	Subsystem: ASUSTeK Computer Inc. Z170 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
	Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
	Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family HD Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
	Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family SMBus
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
	Subsystem: ASUSTeK Computer Inc. Ethernet Connection (2) I219-V
	Kernel driver in use: e1000e
	Kernel modules: e1000e
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070]
	Kernel driver in use: nvidia
	Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 High Definition Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
	Subsystem: ASUSTeK Computer Inc. ASM1142 USB 3.1 Host Controller
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

Last edited by merilius (2019-03-27 13:27:15)

#7 2019-03-28 10:37:36

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 18,300

Re: [SOLVED] cannot add firefox extensions under Plasma

Worksforme, what’s your output for 

qdbus org.kde.KWin /KWin supportInformation

maybe you have some overeager focus catching enabled.

#8 2019-03-28 13:17:57

merilius
Member
Registered: 2012-06-15
Posts: 33

Re: [SOLVED] cannot add firefox extensions under Plasma

On a different computer with integrated Intel GPU it works for me as well.

$ qdbus org.kde.KWin /KWin supportInformation
KWin Support Information:
The following information should be used when requesting support on e.g. https://forum.kde.org.
It provides information about the currently running instance, which options are used,
what OpenGL driver and which effects are running.
Please post the information provided underneath this introductory text to a paste bin service
like http://paste.kde.org instead of pasting into support threads.

==========================

Version
=======
KWin version: 5.15.3
Qt Version: 5.13.0
Qt compile version: 5.13.0
XCB compile version: 1.13.1

Operation Mode: X11 only

Build Options
=============
KWIN_BUILD_DECORATIONS: yes
KWIN_BUILD_TABBOX: yes
KWIN_BUILD_ACTIVITIES: yes
HAVE_DRM: yes
HAVE_GBM: yes
HAVE_X11_XCB: yes
HAVE_EPOXY_GLX: yes
HAVE_WAYLAND_EGL: yes

X11
===
Vendor: The X.Org Foundation
Vendor Release: 12004000
Protocol Version/Revision: 11/0
SHAPE: yes; Version: 0x11
RANDR: yes; Version: 0x14
DAMAGE: yes; Version: 0x11
Composite: yes; Version: 0x4
RENDER: yes; Version: 0xb
XFIXES: yes; Version: 0x50
SYNC: yes; Version: 0x31
GLX: yes; Version: 0x0

Decoration
==========
Plugin: org.kde.breeze
Theme: 
Blur: 0
onAllDesktopsAvailable: true
alphaChannelSupported: true
closeOnDoubleClickOnMenu: false
decorationButtonsLeft: 0, 2
decorationButtonsRight: 8, 9, 6, 3, 4, 5
borderSize: 4
gridUnit: 18
font: Noto Sans,11,-1,5,50,0,0,0,0,0,Regular
smallSpacing: 4
largeSpacing: 18

Platform
==========
Name: KWin::X11StandalonePlatform

Options
=======
focusPolicy: 3
nextFocusPrefersMouse: false
clickRaise: true
autoRaise: false
autoRaiseInterval: 750
delayFocusInterval: 0
shadeHover: true
shadeHoverInterval: 250
separateScreenFocus: false
placement: 6
focusPolicyIsReasonable: false
borderSnapZone: 10
windowSnapZone: 10
centerSnapZone: 0
snapOnlyWhenOverlapping: false
rollOverDesktops: true
focusStealingPreventionLevel: 0
legacyFullscreenSupport: false
operationTitlebarDblClick: 5000
operationMaxButtonLeftClick: 5000
operationMaxButtonMiddleClick: 5015
operationMaxButtonRightClick: 5014
commandActiveTitlebar1: 0
commandActiveTitlebar2: 30
commandActiveTitlebar3: 2
commandInactiveTitlebar1: 4
commandInactiveTitlebar2: 30
commandInactiveTitlebar3: 2
commandWindow1: 7
commandWindow2: 8
commandWindow3: 8
commandWindowWheel: 31
commandAll1: 10
commandAll2: 3
commandAll3: 14
keyCmdAllModKey: 16777251
showGeometryTip: false
condensedTitle: false
electricBorderMaximize: true
electricBorderTiling: true
electricBorderCornerRatio: 0.25
borderlessMaximizedWindows: false
killPingTimeout: 5000
hideUtilityWindowsForInactive: true
inactiveTabsSkipTaskbar: false
autogroupSimilarWindows: false
autogroupInForeground: true
compositingMode: 1
useCompositing: true
compositingInitialized: true
hiddenPreviews: 1
glSmoothScale: 2
xrenderSmoothScale: false
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 0
glPlatformInterface: 1
windowsBlockCompositing: true

Screen Edges
============
desktopSwitching: false
desktopSwitchingMovingClients: false
cursorPushBackDistance: 1x1
timeThreshold: 150
reActivateThreshold: 350
actionTopLeft: 0
actionTop: 0
actionTopRight: 0
actionRight: 0
actionBottomRight: 0
actionBottom: 0
actionBottomLeft: 0
actionLeft: 0

Screens
=======
Multi-Head: no
Active screen follows mouse:  yes
Number of Screens: 1

Screen 0:
---------
Name: DP-2
Geometry: 0,0,3840x2160
Scale: 1
Refresh Rate: 59.9966


Compositing
===========
Compositing is active
Compositing Type: OpenGL
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 1070/PCIe/SSE2
OpenGL version string: 3.1.0 NVIDIA 418.56
OpenGL platform interface: GLX
OpenGL shading language version string: 1.40 NVIDIA via Cg compiler
Driver: NVIDIA
Driver version: 418.56
GPU class: Unknown
OpenGL version: 3.1
GLSL version: 1.40
X server version: 1.20.4
Linux kernel version: 5.0.4
Direct rendering: Requires strict binding: no
GLSL shaders:  yes
Texture NPOT support:  yes
Virtual Machine:  no
OpenGL 2 Shaders are used
Painting blocks for vertical retrace:  no

Loaded Effects:
---------------
zoom
kwin4_effect_fadingpopups
kwin4_effect_frozenapp
kwin4_effect_logout
kwin4_effect_windowaperture
kwin4_effect_translucency
kwin4_effect_morphingpopups
kwin4_effect_maximize
kwin4_effect_login
kwin4_effect_fade
kwin4_effect_dialogparent
slidingpopups
screenshot
magiclamp
desktopgrid
cubeslide
cube
colorpicker
sheet
wobblywindows
presentwindows
highlightwindow
blur
contrast
startupfeedback
screenedge
kscreen

Currently Active Effects:
-------------------------
blur
contrast

Effect Settings:
----------------
zoom:
zoomFactor: 1.2
mousePointer: 0
mouseTracking: 0
enableFocusTracking: false
followFocus: true
focusDelay: 350
moveFactor: 20
targetZoom: 1

kwin4_effect_fadingpopups:
isActiveFullScreenEffect: false

kwin4_effect_frozenapp:
isActiveFullScreenEffect: false

kwin4_effect_logout:
isActiveFullScreenEffect: false

kwin4_effect_windowaperture:
isActiveFullScreenEffect: false

kwin4_effect_translucency:
isActiveFullScreenEffect: false

kwin4_effect_morphingpopups:
isActiveFullScreenEffect: false

kwin4_effect_maximize:
isActiveFullScreenEffect: false

kwin4_effect_login:
isActiveFullScreenEffect: false

kwin4_effect_fade:
isActiveFullScreenEffect: false

kwin4_effect_dialogparent:
isActiveFullScreenEffect: false

slidingpopups:
slideInDuration: 75
slideOutDuration: 125

screenshot:

magiclamp:

desktopgrid:
zoomDuration: 150
border: 10
desktopNameAlignment: 0
layoutMode: 0
customLayoutRows: 2
usePresentWindows: true

cubeslide:
rotationDuration: 250
dontSlidePanels: true
dontSlideStickyWindows: false
usePagerLayout: true
useWindowMoving: false

cube:
cubeOpacity: 0.800000011920929
opacityDesktopOnly: false
displayDesktopName: true
reflection: true
rotationDuration: 250
backgroundColor: #000000
capColor: #eff0f1
paintCaps: true
closeOnMouseRelease: false
zPosition: 100
useForTabBox: false
invertKeys: false
invertMouse: false
capDeformationFactor: 0
useZOrdering: false
texturedCaps: true

colorpicker:

sheet:
duration: 150

wobblywindows:
stiffness: 0.1
drag: 0.85
moveFactor: 0.1
xTesselation: 20
yTesselation: 20
minVelocity: 0
maxVelocity: 1000
stopVelocity: 0.5
minAcceleration: 0
maxAcceleration: 1000
stopAcceleration: 0.5
moveEffectEnabled: true
openEffectEnabled: false
closeEffectEnabled: false
moveWobble: true
resizeWobble: true

presentwindows:
layoutMode: 0
showCaptions: true
showIcons: true
doNotCloseWindows: false
ignoreMinimized: false
accuracy: 20
fillGaps: true
fadeDuration: 75
showPanel: false
leftButtonWindow: 1
rightButtonWindow: 2
middleButtonWindow: 0
leftButtonDesktop: 2
middleButtonDesktop: 0
rightButtonDesktop: 0

highlightwindow:

blur:

contrast:

startupfeedback:
type: 1

screenedge:

kscreen:

Last edited by merilius (2019-03-28 13:18:57)

#9 2019-03-28 19:28:44

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 18,300

Re: [SOLVED] cannot add firefox extensions under Plasma

My focus policy is 0 your focusPolicy  is 3 which is the far right and highly discouraged setting in KWin’s settings kcm, and likely the cause for your issue. set that to something reasonable (one that doesn’t pop up bold warning messages wink ) in kcmshell5 kwinoptions

Last edited by V1del (2019-03-28 19:30:26)

#10 2019-03-29 01:50:30

merilius
Member
Registered: 2012-06-15
Posts: 33

Re: [SOLVED] cannot add firefox extensions under Plasma

Yes, That was it. Thank you!
works for focusPolicy <= 2

Источник
  • Печать

Страницы: [1]   Вниз

Тема: Поломались ассоциации файлов в Thunderbird  (Прочитано 1379 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн
kenar

В Thunderbird поломалась ассоциация с необходимыми программами для открытия вложенных файлов после обновления системы через Aptitude. Thunderbird предлагает только самого себя для открытия либо System Handler (по умолчанию).

Помогите, пожалуйста, починить.

Пользователь добавил сообщение 14 Октября 2021, 20:58:56:

Запустил в терминале.
При открытии письма выдает:

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)


А при попытке открыть pdf вложение в данном письме:

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

/run/user/1000/doc/d95c6ae8/evince: error while loading shared libraries: libevview3.so.3: cannot open shared object file: No such file or directory

« Последнее редактирование: 14 Октября 2021, 20:58:56 от kenar »

Оффлайн
vbuzunova

Добрый день.

Вижу аналогичные ошибки

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)

Заметила, что возникают при создании нового письма и его отправке. Также иконка Thunderbird показывает, будто открыто множество окон, хотя по факту открыто только одно активное окно. Количество «точек», обозначающих количество открытых окон в приложении,  растет каждый раз при создании нового письма.

Также, если закрыть Thunderbird, то обратно открыть его из меню или панели быстрого доступа невозможно. Открыть можно только через терминал.

Кто-то уже сталкивался с таким?

Проблема возникла после обновления Ubuntu с версии 20.04 до 21.10. 

Версия Thunderbird — 91.1.2

Спасибо.

shamanhuev

после обновления Ubuntu с версии 20.04 до 21.10. 

За один шаг ? Самая безумная затея , обновляться со стабильной версии на тестовую.

  • Печать

Страницы: [1]   Вверх

Источник

Понравилась статья? Поделить с друзьями:
  • Ipc internal error
  • Ipc error with error code 1007
  • Ipc error warp
  • Ipad ошибка 2015
  • Ipad отключен подключитесь к itunes как исправить