Bug 266291 - QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance()
Summary: QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLi...
Status: RESOLVED DUPLICATE of bug 147094
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-14 13:22 UTC by George R. Goffe
Modified: 2011-08-01 17:14 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description George R. Goffe 2011-02-14 13:22:51 UTC
Version:           unspecified (using KDE 4.5.5) 
OS:                Linux

Starting Konsole gives this message: QMetaObject::invokeMethod: No such method Konsole::Application::loadCommandLineOptionsForNewInstance()

Konsole also appears to ignore such requests as geometry including size and location requests via "--geometry 100x100+0+0"


Reproducible: Always

Steps to Reproduce:
konsole --geometry 100x100+0+0

Actual Results:  
Konsole appears to be almost full screen height and width.

Expected Results:  
konsole widget of size 100x100 located at +0+0

I would try to use the help facility but that seems to be rather useless. Typing in the "search" part of the help widget, the search button remains greyed out.

--geometry from "konsole --help-kde" does not appear in the help.
Comment 1 Jekyll Wu 2011-08-01 17:14:18 UTC
The message about loadCommandLineOptionsForNewInstance() looks very weird. That name does not exist either in the code for kDE-4.5.5, nor in the commit history of konsole(AFAIK).

As for the --geometry option, that seems a known bug. See bug #147094 and #165355.

You need to use 'konsole --nofork --geometry ...' to make it really work. See comment #22, #23 of bug #155603.

*** This bug has been marked as a duplicate of bug 147094 ***