SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
For some odd reason $opera -fullscreen wont work. Opera just opens up in "normal" mode.
Using F11 from within Opera works like a charm, so the basic fullscreen functionality seems to be working fine. It's just the CLI command that wont stick.
I have a Kubuntu and an OpenSuse box, and it works fine on those two. When issuing the $opera -fullscreen command, Opera opens up in fullscreen, as intended.
My Slackware 12 install is a complete install. Only thing I've done is changing the kernel from huge to generic.
Anybody else experiencing this issue? Is it a know problem with Slackware/Opera/the slackbuilds.org script, or is it perhaps just me being my usual unlucky self?
I hope someone can shed some light on this. I desperately need my -fullscreen option!
Works fine on my machine, same slackbuild. The slackbuild shouldn't be a much of factor anyway, as it just repackages the opera shared QT build as a Slackware package. IMHO, It is more likely to be an oddity of your X or window manager settings.
Works fine on my machine, same slackbuild. The slackbuild shouldn't be a much of factor anyway, as it just repackages the opera shared QT build as a Slackware package. IMHO, It is more likely to be an oddity of your X or window manager settings.
Ok, seeing as it works with F11 from within Opera, I can probably rule out issues with X right?
That leaves problems with window manager settings.
What could possibly have gone wrong? It's a clean Slackware 12 install, with no manual tweaking done to anything, except installing of software (nVidia driver, Krusader, Opera, Kompare and htop) and switching from huge to generic kernel.
Hmm, that's not entirely true come to think of it: I also changed my mouse settings in xorg.conf.
But besides that, nothing been done to the system. KDE is in pristine condition.
Any suggestions as to how I might be able to fix this very weird issue?
make an exception for kwin: right-click on the title bar -> advanced -> special application settings. there should be a "fullscreen" checkbox somewhere
make an exception for kwin: right-click on the title bar -> advanced -> special application settings. there should be a "fullscreen" checkbox somewhere
This wont do, as the fullscreen I'm looking for has nothing to do with KDE, and everything to do with Opera removing all of its toolbars (navigation, bookmarks and so on) from view.
I agree, it is wierd. I've checked with XFCE, KDE and fluxbox and Opera starts fine fullscreen with all of them in my case. Is this a new install of Opera or an upgrade? My Opera 9.22 was upgraded from 9.21, also packaged using a slackbuilds.org script.
PS: the only difference between the slackbuilds for the two was values for the VERSION and DATESTRING variables and the values in the opera.info files.
I agree, it is wierd. I've checked with XFCE, KDE and fluxbox and Opera starts fine fullscreen with all of them in my case. Is this a new install of Opera or an upgrade? My Opera 9.22 was upgraded from 9.21, also packaged using a slackbuilds.org script.
PS: the only difference between the slackbuilds for the two was values for the VERSION and DATESTRING variables and the values in the opera.info files.
This is a new install.
I guess I'll just have to wait for someone patching either Opera or Slackware, and hope it fixes this weird issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.