LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-24-2021, 08:20 AM   #1
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Question Firefox - Pipe Error Parent 13296...


Hey folks,

I've noticed with this fresh install (a week or so old) of Slack64 14.2 that I'm getting a page worth of the same error notice on the shutdown screen.

It looks like this:

Code:
Pipe ERROR - Parent 13296 /tmp/firefox-68.12.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc line 568
Is this just a normal error due to system shutdown or what? I've never seen it before in Slackware.

Everything is working fine, so I'm thinking this isn't a major event. Also, there's nothing even close to this in my /tmp directory.
 
Old 07-24-2021, 09:49 AM   #2
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Hmm... securitybreach, a fellow Admin over at Scot's Newsletter Forums - Bruno's All Things Linux, alerted me to this published bug from a couple years back:

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

It's still OPEN, so evidently still happening in v68.12.0 ESR. It doesn't seem like anything critical, but it is annoying to see the error splattered all down the screen when I telinit 0 my machine every night. Odd that it happens even though FF has already been terminated in the GUI.

Here's what it looks like when I run and shutdown FF from Terminal:

Code:
vtel57@ericsbane07~:$ firefox
[Parent 4187, Gecko_IOThread] WARNING: pipe error (42): Connection reset by peer: file /tmp/firefox-68.12.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
[Parent 4187, Gecko_IOThread] WARNING: pipe error (99): Connection reset by peer: file /tmp/firefox-68.12.0/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 358
Any thoughts?
 
Old 07-24-2021, 10:33 AM   #3
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 481

Rep: Reputation: 322Reputation: 322Reputation: 322Reputation: 322
Firefox can be pretty noisy on the root console, especially when shutting down. You'll go crazy if you try to track down everything it complains about. I would say, as long as it's closing down properly (i.e. not acting like it crashed next time you opened it), ignore its sputum.
 
1 members found this post helpful.
Old 07-24-2021, 10:39 AM   #4
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Yeah, I'm leaning toward this being nothing critical. It's Caturday. I have better things to do that chase bugs that are two or three years old in Firefox browser.

My cat Bootsie* is already busy contemplating her plans for the day.

*link is an Imgur.com image
 
Old 07-24-2021, 10:57 AM   #5
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 10,066

Rep: Reputation: Disabled
Poor cat, so bored doing nothing but lounging on a sofa, not even a mouse to chase... Does she really need white socks?
 
1 members found this post helpful.
Old 07-24-2021, 10:58 AM   #6
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 481

Rep: Reputation: 322Reputation: 322Reputation: 322Reputation: 322
A lot of those messages are just due to timing I think. This is what I get just opening it (to my google.ca homepage) and closing it. Under normal use at a bunch of sites, there'd probably be more complaints about javascript and stuff. If you have extensions, there could be even more noise.

Code:
[grogan@getstuffed:~]$ firefox
/usr/X11R7/share/libdrm/amdgpu.ids: Permission denied
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.

###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost

[grogan@getstuffed:~]$
This is a good build of Firefox 90.0.2 done on this system. The first one is because I didn't dump everything in /usr when I built this system (not Slackware) and its outside of the locations that the sandbox is allowed to access. I'm forcing webrender anyway so it doesn't matter. For the rest it's the left hand not doing what the right is doing... it's obviously finding my profile directory and it's not "sending or receiving" anything I want it to.
 
1 members found this post helpful.
Old 07-24-2021, 11:16 AM   #7
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Actually, @TheRealGrogan... I think I'll upgrade (using Ruario's script) to the newest FF. I was running it in 14.2 previously without any issues. Besides, 68 is getting kind of dated. I get tired of the "Your browser is old and out-of-date" warnings on some websites.

If the upgrade goes sideways, I can always revert relatively easily.
 
Old 07-24-2021, 11:41 AM   #8
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 481

Rep: Reputation: 322Reputation: 322Reputation: 322Reputation: 322
Don't forget to back up ~/.mozilla first if wanting to be able to go back though. Once the profile is converted, it's not just a matter of profiles.ini/installs.ini to go back to a different build channel.
 
1 members found this post helpful.
Old 07-24-2021, 12:18 PM   #9
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Absolutely, I have multiple backups of my Moz profiles.
 
Old 07-24-2021, 12:37 PM   #10
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
FF 90.0.2 useragent test...

Mozilla/5.0 (X11; Slackware x86_64; rv:90.0) Gecko/20100101 Firefox/90.0

Last edited by vtel57; 07-24-2021 at 12:40 PM.
 
Old 07-24-2021, 01:04 PM   #11
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
OK, no shutdown errors with FF 90.x. YAY!
 
Old 07-24-2021, 01:09 PM   #12
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 10,066

Rep: Reputation: Disabled
Quote:
Originally Posted by vtel57 View Post
Actually, @TheRealGrogan... I think I'll upgrade (using Ruario's script) to the newest FF. I was running it in 14.2 previously without any issues. Besides, 68 is getting kind of dated. I get tired of the "Your browser is old and out-of-date" warnings on some websites.

If the upgrade goes sideways, I can always revert relatively easily.
I provide repackaged ones using Ruario's script here. Do follow the instructions in the README if you want to try. Not tested in Slackware, but should work. I know I should upgrade Firefox 90, will do tonight.

Last edited by Didier Spaier; 07-24-2021 at 04:00 PM.
 
1 members found this post helpful.
Old 07-24-2021, 02:14 PM   #13
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
Ruario's script worked fine, Didier. Thank you!

I have a method:

- rename original .moz profiles, profile.ini, etc. and backup
- run Ruario's script
- installpkg
- start browser, sign into FF-Sync
- make a few manual tweaks to customize (enabling compact mode so tabs are smaller, for instance)
- copy over my "permissions.sqlite" from old profile (saves me from having to manually enter all my cookie/login exceptions)
- blacklist "mozilla-firefox" in /etc/slackpkg/blacklist so Slackpkg doesn't revert to 68 when I update

and that's pretty much it. FF-Sync takes care of most of the hard work.
 
Old 07-25-2021, 10:54 AM   #14
vtel57
Senior Member
 
Registered: Jul 2006
Location: USA
Distribution: Slackware64 - 14.2 w/ Xfce
Posts: 1,465

Original Poster
Rep: Reputation: 398Reputation: 398Reputation: 398Reputation: 398
...sigh...

Seems I just can't win with Firefox these days. When shutting down last night, I got these errors from Firefox...

Code:
(firefox:1596): Gtk-CRITICAL **: gtk_style_context_get_property: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed

(firefox:1596): GLib-GObject-CRITICAL **: g_value_unset: assertion 'G_IS_VALUE (value)' failed

(firefox:1596): Gtk-CRITICAL **: gtk_style_context_get_property: assertion 'GTK_IS_STYLE_CONTEXT (context)' failed
I'm pretty sure they're just theme-related baloney, so I'm going to ignore. All is working fine.
 
Old 07-25-2021, 02:54 PM   #15
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, LFS, Manjaro (for gaming)
Posts: 481

Rep: Reputation: 322Reputation: 322Reputation: 322Reputation: 322
I get baloney like that too, from a lot of GTK applications. Pretty much always, on any system. Those assertions aren't fatal, unlike how assertion failures would normally be treated, it behaves more like warnings. It can be caused by styling but it can also be discrepancies with software using older versions of APIs too and they have since removed or changed things. GTK is still compatible and the applications still work. Or, it might always have been incorrect usage and newer versions of GTK+ complain etc. depending on what the messages are.

It's not a problem because most people never see the root console, it's hidden behind splash screens and display session managers. However, Slackers are often old school users :-)

Firefox will be using old methods to support the likes of Ubuntu 16.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Create 5 processes from a common parent and ensure that the parent terminates after c pro_learner Linux - Newbie 1 03-06-2013 09:25 AM
File descriptors shared between child and parent causing parent to hang. bharadiaam Linux - Newbie 1 03-02-2009 01:01 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:02 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration