Tiny Core Extensions > TCE Bugs

[Solved] brave-browser: popup menus disappear when any menu item is left-clicked

(1/3) > >>

GNUser:
The behavior is observed when running brave-browser on TCL12 x86_64 or TCL11.1 x86_64 with Xorg (Xvesa doesn't work with my hardware, so I can't test it). Other tested browsers (e.g., firefox, chromium) do not have this problem. The same exact brave-browser binary running on a different OS (e.g., Devuan) on this same machine does not have this problem.

A quick and easy way to reproduce:
1. Load brave-browser.tcz
2. Start the browser and go to http://forum.tinycorelinux.net
3. Login to the forum
4. Hover over "My Messages" to activate the popup menu
5. Click on "Read your messages"
6. The menu disappears without taking you to messages section :-\

I've noticed the problem on multiple websites, so it is not a problem with the TCL forum site.

All the relevant software (Xorg, gtk3, the browser itself) is so complex that I'm at a loss how to even start troubleshooting this. Any ideas?

Rich:
Hi GNUser
I would suggest the first thing to try is start the browser from a terminal and see if any errors/warnings pop up.

GNUser:
Hi, Rich. Good idea. Here you go:

--- Code: ---$ brave-browser
[7145:7161:0503/213729.268753:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[7145:7145:0503/213729.623372:ERROR:browser_dm_token_storage_linux.cc(94)] Error: /etc/machine-id contains 0 characters (32 were expected).
[7145:7175:0503/213730.115130: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")
[7145:7175:0503/213730.115175: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")
[7145:7175:0503/213730.447046: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")
[7145:7175:0503/213730.447091: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")
[7145:7222:0503/213730.931778:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[7145:7222:0503/213730.931863:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[7145:7222:0503/213730.931977:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[7145:7222:0503/213730.932135:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[7145:7222:0503/213730.932199:ERROR:bus.cc(393)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

--- End code ---
These errors scroll by when first launching brave-browser. Once browser is running, no additional errors show up in the terminal. Also, no errors show up in the terminal when popup menus disappear.

BTW, launching chromium from the terminal shows the same errors and chromium doesn't have the problem I'm investigating, so I think the errors above are unrelated to my issue.

Juanito:
Quite a few apps seem to use dbus if the daemon is running and issue warning messages if it is not running.

I don't think running dbus will fix your problem, but you could give it a try.

Juanito:

--- Quote from: GNUser on May 03, 2021, 07:40:09 PM ---...running brave-browser on TCL12 x86_64 or TCL11.1 x86_64 with Xorg (Xvesa doesn't work with my hardware, so I can't test it)

--- End quote ---

Xvesa is 32-bit only

Navigation

[0] Message Index

[#] Next page