chromium-browser or opera from twm
 

Hello,
I would like to start opera browser or chromium-browser from twm.
How to do it? I start twm with startx and twm command in ~/.xinitrc
then I run xterm and try to run opera, chromium-browser without success.
When I start firefox fisrst - then I can run opera and chromium-browser without problems.
How to properly setup X session to get opera running without problems.

thanks for any help

Do you have this line in your /etc/fstab?

Also, what version of Slackware are you running?

I have something like:
tmpfs /dev/shm tmpfs nosuid,nodev,noexec 0 0
tmpfs /tmp tmpfs nosuid,nodev 0 0

I run Slackware64-current.
I noticed, that when I start some gui apps - then I can run opera and chromium-browser without problems:
- thunderbird
- kmail
- firefox
- /usr/lib64/xfce4/notifyd/xfce4-notifyd (I use it as warkaround of this problem, I put it in .xinitrc just before opera or chromium-browser)
Another problem is wrong size for opera window running from .xinitrc directly. It is not really fullscreen but about half size. When I touch maximize on its windows decorations then nothing is changing.
What I wish to have is just web browser running in fullscreen mode without any window manager.
For now I am fine with old opera browser version before chromium based one and old slackware version, but I am looking for similar setup in slackware64_current
environment.

I don't have opera but I just tried launching chromium-browser in twm and it works fine. It sounds like maybe you are not understanding how windows are sized in twm? If the browser is "half size" then you can click and drag the resize button in the top right to make it larger.

AFAIK twm can't launch a browser in fullscreen like this. If you want a simpler solution for this then you could forgo using twm and startx and just use xinit instead:

I just tried that straight from the command line after logging in and it fires up the browser in fullscreen directly. Just no window decorations since its not running in a window manager.

I use twm to reproduce the problem and find the solution how to fix it.
When I start chromium with xinit /usr/bin/chromium, then I don't get it working. (chromium fails to start).
The only way to start chromium is to run thunderbird once before it. then I can kill each program started by thunderbird (gvfsd, at-spi2-registryd, xfce4-notifyd,
at-spi-bus-launcher and others) and run chromium without problem. I think that I missed something in xorg setup that cuse the problems.
Another problem is with firefox. It runs with xinit /usr/bin/firefox - but standard menu of firefox is useless - it doesn't work.
When I run chromium or opera from xterm in fluxbox or twm - then it runs in fullscreen mode. Bat the first step that I have to do is to run something else before the browser (nm-applet, volumeicon, cbatticon).

Can you show your .xinitrc? I can start Firefox with

in my `.xinitrc`, and opera with

no problem. And I can start twm, launch an xterm and type `firefox` or `opera` to start it, menus and everything work fine.

Running directly `xinit /usr/bin/opera` doesn't read your `.twmrc`, so it just shows an X window with opera, no titlebars, menus, or anything.

Yeah it starts the application without the window manager so there's no window sizing to be done. Also the browsers don't use the -geometry options from xinit, you have to read the command line options for whichever browser you want to use to set the window size in their preferred way if using this method. E.g. xinit /usr/bin/firefox -width 1920 -height 1080 makes firefox launch in fullscreen for me since that's the resolution I use.

It's also not ideal to use xinit directly since not all features are going to be supported without a window manager. For example the drop down menus in firefox don't work properly with this method, although chromium does work for me. I put that info there since the OP wanted to run a graphical browser without a window manager and thats how that works.

I'm not sure why the OP is having issues getting these browsers to start and without any error messages there's not much else to suggest.