Chrome quits when any key is pressed (Bionicpup64) solved

Amaponian · Post by **Amaponian** » Wed Dec 15, 2021 12:33 am

Note:
The fix is explained here:
viewtopic.php?p=48480#p48480

I can't use the last version of chrome (96.0.4664.93.1) for my frugal Bionicpup64.
It simply quits when I press any key.
I've been able to work copying text from geany and pasting it into the chrome browser.
I tested that in two different computers with same result.
Now I'm using the very old version 70.0.3538.77-1-x86_64 (the one in the quickpet.)

Can someone provide a fix for the current version
or a link for downloading a previous version that work and that is not so old?

Hope someone can help with this Puppy Linux bug.

Thank you!

My computer, where the problem ocurs:

Code: Select all

-Computer-
	Processor		: Intel(R) Celeron(R) CPU  N2805  @ 1.46GHz
	Memory			: 1918MB (549MB used)  --- chrome and palemoon loaded
	Machine Type		: Handheld
	Operating System	: Puppy Linux
	User Name		: root (root)
	Date/Time		: jue 16 dic 2021 13:39:02 -04
-Display-
	Resolution		: 1366x768 pixels
	OpenGL Renderer		: Mesa DRI Intel(R) Bay Trail 
	X11 Vendor		: The X.Org Foundation
-Audio Devices-
	Audio Adapter		: HDA-Intel - HDA Intel PCH
-Input Devices-
	Lid Switch
	Power Button
	Sleep Button
	Power Button
	AT Translated Set 2 keyboard
	cmpc_keys
	Video Bus
	PC Speaker
	HDA Digital PCBeep
	HDA Intel PCH Mic
	HDA Intel PCH Headphone
	HDA Intel PCH HDMI/DP,pcm:3
	USB HD Webcam: USB HD Webcam
	ImPS/2 Logitech Wheel Mouse
-Printers (CUPS)-
	CUPS-PDF			: <i>Default</i>
-SCSI Disks-
	Kingston DataTraveler 2.0


SYSTEM
-Version-
	Kernel				: Linux 4.19.23 (x86_64)
	Version				: #1 SMP Tue Feb 19 15:07:58 GMT 2019
	C Library			: GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
	Distribution			: Puppy Linux
-Current Session-
	Computer Name			: Amaponian
	User Name			: root (root)
	Language			: es_VE.UTF-8 (es_VE.UTF-8)
	Home Directory			: /root
-Misc-
	Uptime				: 56 minutes
	Load Average			: 0,31, 0,53, 0,52
	Available entropy in /dev/random: 3515 bits (healthy)

ozsouth · Post by **ozsouth** » Wed Dec 15, 2021 5:17 am

@Amaponian - you could try (at own risk) this .pet - is a couple of months old,
but ran in my bionic64. Uninstall any other chrome version before installing.
Will put an entry in the Internet menu.

https://archive.org/download/Puppy_Linu ... 1-spot.pet

Post by **mikewalsh** » Wed Dec 15, 2021 11:54 am

@Amaponian :-

You could always try the portable-Chrome I maintain here:-

viewtopic.php?t=146

All needed links are in the first post. What have you got to lose?

Ozsouth's package above is a more traditional Puppy package, if that's what you prefer or find easier to use.
The 'portables' are designed to work from outside the 'save'.

Both function perfectly, and work exactly the same. The choice, as always, is down to the individual.....

Mike.

8Geee · Post by **8Geee** » Wed Dec 15, 2021 9:54 pm

I'm wondering if glibc 2.27 is too old. New stuff likes 2.30+

Post by **mikewalsh** » Wed Dec 15, 2021 11:28 pm

@8Geee :-

8Geee wrote: ↑Wed Dec 15, 2021 9:54 pm
I'm wondering if glibc 2.27 is too old. New stuff likes 2.30+

Nah. I regularly run Chrome-portable across Puppies ranging from glibc 2.31 (Fossapup64) all the way back to glibc 2.20 (jrb's 'lite' spin on BK's Quirky64 'April' 7.0.1.

Google purposely recompile the "cutting-edge'" builds from the Chromium Project (which DO want the very newest of everything) against a very much older glibc and deps.....for the simple reason that it makes the browser available to the widest possible range of users. They know darned well that not everyone religiously upgrades to the very newest of everything the instant it hits the shelves; most folks, given the choice, and almost certainly running Redmond's nightmare of an OS, will put off updating as long as they possibly can.....

We geeks tend to be the sort of folks who like keeping everything up-to-date all the time. Nobody else can be bothered with all that, 'cos as far as they're concerned it's just a load of messing-about for the sake of messing-about...... Joe Public just doesn't think the same as thee or me.

Chrome runs fine for me in Bionic64, and is as stable as they come.

(*shrug*)

Mike.

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 4:57 am

mikewalsh wrote: ↑Wed Dec 15, 2021 11:54 am
@Amaponian :-

You could always try the portable-Chrome I maintain here:-

viewtopic.php?t=146

All needed links are in the first post. What have you got to lose?

Ozsouth's package above is a more traditional Puppy package, if that's what you prefer or find easier to use.
The 'portables' are designed to work from outside the 'save'.

Both function perfectly, and work exactly the same. The choice, as always, is down to the individual.....

Mike.

All day struggling with this without any success.
This is what I got:

ozsouth's gc64-94.0.4606.81-spot.pet
Versión 94.0.4606.81 (Build oficial) unknown (64 bits)
Error: Quits when any key is pressed

mikewalsh's Chrome Portable
Versión 96.0.4664.110 (Build oficial) unknown (64 bits)
Error: Quits when any key is pressed

Looks like there's a problem with my system, but consider this:

1. The previous version of chrome was working fine. I saw the annoying chrome message urging to update, then I updated and realized the fail on the chrome version 96.0.4664.93.1. I removed it and reinstalled the previous version and, again, it worked fine. Thank goodness I still had the .deb from chrome's site (but now the power suppy of that machine has a problem and I can't get the file).

2. I formatted a 2GB flashdrive, downloaded a new Bionicpup iso file, made a fresh install, downloaded and installed the Ozsouth's chrome package, getting the above error, again.

In every try I removed a chrome version before attempting to install another, always verifying the version in the About box.

It's a mind blowing problem.
It must be in this Puppy, or in these machines.
but I don't know how to spot it.

Thanks for the help.
Greetings from Venezuela.

Post by **mikewalsh** » Thu Dec 16, 2021 12:03 pm

@Amaponian :-

Hm. Very strange.....

I'm curious as to whether this is just Chrome itself, or whether it's the Chromium code-base in general. Is it only Chrome that exhibits this behaviour? You could try the current release of my Iron-portable:-

viewtopic.php?t=771

Iron is a brilliant Chrome 'clone'. Identical to Chrome in appearance, you can still sync with a Google a/c, use the same bookmarks, same extensions, etc. Or, there's the Ungoogled-Chromium 'portable':-

viewtopic.php?p=11080#p11080

This takes a bit more setting-up, since the Google-specific mechanisms aren't there, but full instructions on how to do so are in the thread, here:-

viewtopic.php?p=18966#p18966

Up to you, of course. If you decide to try either of these, let us know what the results are, please.

Mike.

dancytron · Post by **dancytron** » Thu Dec 16, 2021 12:39 pm

Have you tried running Chrome from the terminal to see if it gives an error before it crashes?

Try to use the exact same command as the "exec" line in the .desktop file.

Post by **mikewalsh** » Thu Dec 16, 2021 1:46 pm

dancytron wrote: ↑Thu Dec 16, 2021 12:39 pm
Have you tried running Chrome from the terminal to see if it gives an error before it crashes?

Try to use the exact same command as the "exec" line in the .desktop file.

Yes; that would of course be the most sensible course of action to begin with. If there's one thing you cannot accuse the Chromium browsers of, it's being scant with information in the terminal. If anything, they go to the other extreme, since these browsers are built to give a real-time, ongoing debug report all the time they're running.....

Mike.

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 4:04 pm

mikewalsh wrote: ↑Thu Dec 16, 2021 1:46 pm
dancytron wrote: ↑Thu Dec 16, 2021 12:39 pm
Have you tried running Chrome from the terminal to see if it gives an error before it crashes?

Try to use the exact same command as the "exec" line in the .desktop file.

Yes; that would of course be the most sensible course of action to begin with. If there's one thing you cannot accuse the Chromium browsers of, it's being scant with information in the terminal. If anything, they go to the other extreme, since these browsers are built to give a real-time, ongoing debug report all the time they're running.....

Mike.

Good idea!
Below is what I've got:

I'm doing this with the faulty last version of chrome.
(Versión 96.0.4664.110 (Build oficial) (64 bits))
pasting text from Geany.

I separated the two last lines
'cause they ocurred after I pressed the letter ñ inside chrome.

Code: Select all

root# google-chrome-stable
[26227:26261:1216/114125.158059:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26227:26261:1216/114125.158285:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26227:26261:1216/114125.456563:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26227:26261:1216/114125.456660:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26273:26273:1216/114125.618995:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[26227:26261:1216/114125.752946:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26227:26261:1216/114125.753023:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[26227:26383:1216/114126.241737:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[26227:26383:1216/114126.243159:ERROR:object_proxy.cc(642)] Failed to call methoroot# google-chrome-stable
[27020:27056:1216/114209.361773:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27020:27056:1216/114209.361997:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27020:27056:1216/114209.552588:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27020:27056:1216/114209.552682:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27068:27068:1216/114209.656343:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[27020:27056:1216/114209.810929:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27020:27056:1216/114209.811111:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[27020:27162:1216/114210.260191:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[27020:27162:1216/114210.262003:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[27020:27162:1216/114210.264712:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[27020:27020:1216/114210.306958:ERROR:gpu_process_host.cc(967)] GPU process exited unexpectedly: exit_code=11
[27180:27180:1216/114210.638649:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[27131:8:1216/114210.698857:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[27131:8:1216/114210.996488:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[27020:27020:1216/114211.000701:ERROR:gpu_process_host.cc(967)] GPU process exited unexpectedly: exit_code=11
[27215:27215:1216/114211.211819:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[27020:27020:1216/114211.295222:ERROR:gpu_process_host.cc(967)] GPU process exited unexpectedly: exit_code=11
[27227:27227:1216/114211.519298:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[27131:8:1216/114211.550985:ERROR:command_buffer_proxy_impl.cc(125)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

Segmentation fault
root#

Post by **rockedge** » Thu Dec 16, 2021 4:26 pm

Looks like actions looking for a system GPU are causing this crash. Perhaps disabling any GPU interactions will solve the problem.

Post by **bigpup** » Thu Dec 16, 2021 4:42 pm

Not sure if this will help, but it will make Bionicpup64 8.0 overall.

Quickpet>Info>Bionicpup updates
Reboot and save, so new changes are now being used.
This installs some bug fixes.

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 4:47 pm

bigpup wrote: ↑Thu Dec 16, 2021 4:42 pm
Not sure if this will help, but it will make Bionicpup64 8.0 overall.

Quickpet>Info>Bionicpup updates
Reboot and save, so new changes are now being used.
This installs some bug fixes.

Thanks, but that was done from the very beginning.

But the problem must be something very basic as, may be,
I have too little memory (2GB) for new versions of chrome.

Post by **bigpup** » Thu Dec 16, 2021 4:51 pm

Try this in Chrome:

Go to Settings -> System and disable Use hardware acceleration when available option.
You will need to restart Chrome for this to take effect.
The GPU process should be gone after this change.

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 5:25 pm

bigpup wrote: ↑Thu Dec 16, 2021 4:51 pm
Try this in Chrome:

Go to Settings -> System and disable Use hardware acceleration when available option.
You will need to restart Chrome for this to take effect.
The GPU process should be gone after this change.

Interesting...
Done.
Chrome still quits after a key is pressed.
These are now the errors in terminal:

Code: Select all

root# google-chrome-stable
[12133:12166:1216/132030.982698:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12133:12166:1216/132030.982914:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12133:12166:1216/132031.165713:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12133:12166:1216/132031.166671:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12192:12192:1216/132031.396282:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[12133:12166:1216/132031.447012:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12133:12166:1216/132031.447148:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[12133:12285:1216/132031.895727:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[12133:12285:1216/132031.897842:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[12133:12285:1216/132031.900484:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[12133:12161:1216/132034.757926:ERROR:chrome_browser_main_extra_parts_metrics.cc(226)] crbug.com/1216328: Checking Bluetooth availability started. Please report if there is no report that this ends.
[12133:12161:1216/132034.758301:ERROR:chrome_browser_main_extra_parts_metrics.cc(229)] crbug.com/1216328: Checking Bluetooth availability ended.
[12133:12161:1216/132034.759590:ERROR:chrome_browser_main_extra_parts_metrics.cc(232)] crbug.com/1216328: Checking default browser status started. Please report if there is no report that this ends.
[12133:12161:1216/132034.859000:ERROR:chrome_browser_main_extra_parts_metrics.cc(236)] crbug.com/1216328: Checking default browser status ended.
Segmentation fault
root#

williams2 · Post by **williams2** » Thu Dec 16, 2021 5:40 pm

Most of the errors are dbus errors.
What happens if you start chrome like this:

dbus-run-session google-chrome-stable

Does chrome need to run as user spot?

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 5:51 pm

My computer, where the problem ocurs:

Code: Select all

-Computer-
	Processor		: Intel(R) Celeron(R) CPU  N2805  @ 1.46GHz
	Memory			: 1918MB (549MB used)  --- chrome and palemoon loaded
	Machine Type		: Handheld
	Operating System	: Puppy Linux
	User Name		: root (root)
	Date/Time		: jue 16 dic 2021 13:39:02 -04
-Display-
	Resolution		: 1366x768 pixels
	OpenGL Renderer		: Mesa DRI Intel(R) Bay Trail 
	X11 Vendor		: The X.Org Foundation
-Audio Devices-
	Audio Adapter		: HDA-Intel - HDA Intel PCH
-Input Devices-
	Lid Switch
	Power Button
	Sleep Button
	Power Button
	AT Translated Set 2 keyboard
	cmpc_keys
	Video Bus
	PC Speaker
	HDA Digital PCBeep
	HDA Intel PCH Mic
	HDA Intel PCH Headphone
	HDA Intel PCH HDMI/DP,pcm:3
	USB HD Webcam: USB HD Webcam
	ImPS/2 Logitech Wheel Mouse
-Printers (CUPS)-
	CUPS-PDF			: <i>Default</i>
-SCSI Disks-
	Kingston DataTraveler 2.0


SYSTEM
-Version-
	Kernel				: Linux 4.19.23 (x86_64)
	Version				: #1 SMP Tue Feb 19 15:07:58 GMT 2019
	C Library			: GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27
	Distribution			: Puppy Linux
-Current Session-
	Computer Name			: Amaponian
	User Name			: root (root)
	Language			: es_VE.UTF-8 (es_VE.UTF-8)
	Home Directory			: /root
-Misc-
	Uptime				: 56 minutes
	Load Average			: 0,31, 0,53, 0,52
	Available entropy in /dev/random: 3515 bits (healthy)

Amaponian · Post by **Amaponian** » Thu Dec 16, 2021 6:01 pm

williams2 wrote: ↑Thu Dec 16, 2021 5:40 pm
Does chrome need to run as user spot?

I think not.
I've used recent versions without worrying about that.

williams2 wrote: ↑Thu Dec 16, 2021 5:40 pm
Most of the errors are dbus errors.
What happens if you start chrome like this:

dbus-run-session google-chrome-stable

Tested.
Chrome quits after a key is pressed.
Some changes in terminal.

Code: Select all

root# dbus-run-session google-chrome-stable
[31614:31660:1216/135328.085289:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31614:31660:1216/135328.088128:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31614:31660:1216/135328.285011:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31614:31660:1216/135328.296851:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31669:31669:1216/135328.480851:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[31614:31660:1216/135328.588009:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31614:31660:1216/135328.589516:ERROR:bus.cc(393)] Failed to connect to the bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
[31614:31767:1216/135329.008935:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[31614:31767:1216/135329.009631:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[31614:31767:1216/135329.010230:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
root#

Post by **rockedge** » Thu Dec 16, 2021 7:47 pm

does look like dbus is not running or is the wrong version(?)

Try in a terminal:

Code: Select all

dbus-launch

and if that doesn't go try:

Code: Select all

dbus-daemon

If something starts try running the Chrome again.

ndujoe2 · Post by **ndujoe2** » Thu Dec 16, 2021 8:02 pm

I had the same result when I updated my Google Chrome browser in Bionicpup64. I gave up and went to Opera. Any keypress and Chrome disappears.

dancytron · Post by **dancytron** » Thu Dec 16, 2021 8:13 pm

Go to chrome://settings/system (advanced settings--system from teh menu) and see if turning off "Enable Hardware Acceleration" helps.

The other thing to do is figure out exactly how you have your Mesa Driver set up with your hardware and if there is a better way to do it, which I'll leave to someone else.

Post by **mikewalsh** » Fri Dec 17, 2021 12:11 am

@Amaponian :-

Can you let us see exactly how the exec line of your wrapper script is set up? (This is the "google-chrome" - or "google-chrome-stable" - script inside the chrome directory that actually launches the browser).

I'm curious to see just how the '--switches' (if any) on the exec line have been phrased.

I did have a spell like this myself a couple of years ago, but I have to say that over the last year or two - with this current install of Bionic64 - update after update of Chrome has been as good as gold for me. Mind you, my Puppies are so highly modified, I couldn't even begin to say what might be making things behave themselves for me.

Mike.

Amaponian · Post by **Amaponian** » Fri Dec 17, 2021 1:37 am

mikewalsh wrote: ↑Fri Dec 17, 2021 12:11 am
@Amaponian :-

Can you let us see exactly how the exec line of your wrapper script is set up? (This is the "google-chrome" - or "google-chrome-stable" - script inside the chrome directory that actually launches the browser).

I'm curious to see just how the '--switches' (if any) on the exec line have been phrased.

I did have a spell like this myself a couple of years ago, but I have to say that over the last year or two - with this current install of Bionic64 - update after update of Chrome has been as good as gold for me. Mind you, my Puppies are so highly modified, I couldn't even begin to say what might be making things behave themselves for me.

Mike.

Below is the content of the file
google-chrome-stable
used to launch the app

Code: Select all

#!/bin/sh
   APP=/opt/google/chrome/google-chrome.bin
#script to run $APP as spot...
ARGS=""
[ "$1" ] && while [ "$1" ]; do ARGS="$ARGS \"$1\""; shift; done
if [ $(id -u) -eq 0 ]; then
 [ $XAUTHORITY ] && cp $XAUTHORITY /root/spot/.Xauthority 2>/dev/null
 touch /root/spot/.Xauthority
 #following line is mostly there to catch any root:root files that may have got copied in...
 find /root/spot \( -not -user spot -or -not -group spot \) -exec chown -h spot:spot {} \; &
 export XAUTHORITY=/root/spot/.Xauthority  
 export XDG_CONFIG_HOME=/root/spot/.config
 export XDG_CACHE_HOME=/root/spot/.cache
 export XDG_DATA_HOME=/root/spot/.local/share
 exec su spot -s /bin/sh -c "\"$APP\" $ARGS"
else #precaution
 exec "$APP" "$ARGS"
fi

Amaponian · Post by **Amaponian** » Fri Dec 17, 2021 1:50 am

dancytron wrote: ↑Thu Dec 16, 2021 8:13 pm
Go to chrome://settings/system (advanced settings--system from teh menu) and see if turning off "Enable Hardware Acceleration" helps.

Already tried that one, someone suggested it up there.
Chrome keeps halting when a key is pressed.

dancytron wrote: ↑Thu Dec 16, 2021 8:13 pm
The other thing to do is figure out exactly how you have your Mesa Driver set up with your hardware and if there is a better way to do it, which I'll leave to someone else.

Well, I don't know what 'Mesa' means here, but that's a Spanish name for a dinning table. Greetings from Venezuela.

BologneChe · Post by **BologneChe** » Fri Dec 17, 2021 10:57 am

Hi,

I also observed the same problem with Chromium 95. (under Bionicpup64 - from PPM)

Amaponian · Post by **Amaponian** » Fri Dec 17, 2021 12:04 pm

rockedge wrote: ↑Thu Dec 16, 2021 7:47 pm
does look like dbus is not running or is the wrong version(?)

Try in a terminal:
Code: Select all
dbus-launch
and if that doesn't go try:
Code: Select all
dbus-daemon
If something starts try running the Chrome again.

Sorry for the delay. I almost overlooked your comment.

I've just tested your suggestions.
Chrome keeps halting when a key is pressed.
This is what the terminal shows:

dbus-launch

Code: Select all

root# dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-GPBIBHTMrl,guid=4b1b88509416e0d3abcc4d1361bc7a16
DBUS_SESSION_BUS_PID=2387

root# google-chrome-stable
[2425:2459:1217/075259.711938:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2425:2459:1217/075259.712142:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2425:2459:1217/075259.873807:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2425:2459:1217/075259.873905:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2467:2467:1217/075300.137910:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[2425:2459:1217/075300.179729:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2425:2459:1217/075300.179808:ERROR:bus.cc(393)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2425:2587:1217/075300.695237:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2425:2587:1217/075300.696155:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[2425:2587:1217/075300.697018:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
Segmentation fault
root#

dbus-daemon

Code: Select all

root# dbus-daemon
No configuration file specified.
dbus-daemon [--version] [--session] [--system] [--config-file=FILE] [--print-address[=DESCRIPTOR]] [--print-pid[=DESCRIPTOR]] [--introspect] [--address=ADDRESS] [--nopidfile] [--nosyslog] [--syslog] [--syslog-only] [--nofork] [--fork] [--systemd-activation]
root#

dancytron · Post by **dancytron** » Fri Dec 17, 2021 12:07 pm

Amaponian wrote: ↑Fri Dec 17, 2021 1:50 am
dancytron wrote: ↑Thu Dec 16, 2021 8:13 pm
Go to chrome://settings/system (advanced settings--system from teh menu) and see if turning off "Enable Hardware Acceleration" helps.

Already tried that one, someone suggested it up there.
Chrome keeps halting when a key is pressed.

dancytron wrote: ↑Thu Dec 16, 2021 8:13 pm
The other thing to do is figure out exactly how you have your Mesa Driver set up with your hardware and if there is a better way to do it, which I'll leave to someone else.

Well, I don't know what 'Mesa' means here, but that's a Spanish name for a dinning table. Greetings from Venezuela.

Mesa is the name of the program that runs the accelerated graphics GPU stuff. (For general information purposes. The answer to your problem is NOT here. https://www.mesa3d.org )

Troubleshooting that is really not something I know how to do on Puppy anymore, someone more knowledgeable will be by.

Amaponian · Post by **Amaponian** » Fri Dec 17, 2021 12:12 pm

dancytron wrote: ↑Fri Dec 17, 2021 12:07 pm
Mesa is the name of the program that runs the accelerated graphics GPU stuff. (For general information purposes. The answer to your problem IS NOT here. https://www.mesa3d.org )

Troubleshooting that is really not something I know how to do on Puppy anymore, someone more knowledgeable will be by.

Thank you.

Amaponian · Post by **Amaponian** » Fri Dec 17, 2021 12:17 pm

ndujoe2 wrote: ↑Thu Dec 16, 2021 8:02 pm
I had the same result when I updated my Google Chrome browser in Bionicpup64. I gave up and went to Opera. Any keypress and Chrome disappears.

Thank you for the information.
It's useful to know that I'm not the only one affected.
I don't give up yet.

CelsoIII · Post by **CelsoIII** » Tue Dec 21, 2021 3:09 am

Same issue here on Bionic 64 after updating Chorme to google-chrome-stable_current_amd.deb
Chrome halts when any key is pressed.
Any help will be much appreciated.

Puppy Linux Discussion Forum

Chrome quits when any key is pressed (Bionicpup64) solved

Chrome quits when any key is pressed (Bionicpup64) solved

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: [ NOT SOLVED ] Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)

Re: Chrome 96.0.4664.93.1 quits when any key is pressed (Bionic 64 bits)