Notices


Reply
Thread Tools
Posts: 4 | Thanked: 0 times | Joined on Aug 2010
#161
Hi, every time i launch the application as soon as i choose new or open it crash. If i launch it from terminal the following message is show:

ERROR:dbus-gproxy.c:2269:dbus_g_proxy_marshal_args_to_message : code should not be reached
Aborted.

I am using latest version 1.6 from extras-(testing/devel) on N900 software PR 1.2.

Could someone help me ? Thanks.
 
thp's Avatar
Posts: 1,391 | Thanked: 4,272 times | Joined on Sep 2007 @ Vienna, Austria
#162
Originally Posted by mello73 View Post
Hi, every time i launch the application as soon as i choose new or open it crash. If i launch it from terminal the following message is show:

ERROR:dbus-gproxy.c:2269:dbus_g_proxy_marshal_args_to_message : code should not be reached
Aborted.
Make sure that you run it as user "user" in the terminal, not as root. Does it work then? Please paste the output of the following command:

Code:
gconftool -R /apps/maepad
Also, it will usually show the "lastdocument" key there - please try renaming the file - it contains all your MaePad data (if any) - and if it starts working afterwards, please send it to me (via PM), so I can investigate.
 
Posts: 4 | Thanked: 0 times | Joined on Aug 2010
#163
Originally Posted by thp View Post
Make sure that you run it as user "user" in the terminal, not as root. Does it work then? Please paste the output of the following command:
Code:
gconftool -R /apps/maepad
i am already running the program as "user"

in gconf there is no entry (i think the program crash even before creating it)

Originally Posted by thp View Post
Also, it will usually show the "lastdocument" key there - please try renaming the file - it contains all your MaePad data (if any) - and if it starts working afterwards, please send it to me (via PM), so I can investigate.
This is the first time i am installing maepad so there is no "lastdocument".

Thanks

Last edited by mello73; 2010-08-23 at 18:48.
 
Posts: 561 | Thanked: 75 times | Joined on Jan 2010 @ Spain
#164
I have exactly the same problem and is a facility without previous documents
 
Posts: 25 | Thanked: 9 times | Joined on Sep 2010
#165
I also got the problem with the dbus error above using the latest version. Any ideas to why? First install of the program so i don't have any previos configs or the like
 
thp's Avatar
Posts: 1,391 | Thanked: 4,272 times | Joined on Sep 2007 @ Vienna, Austria
#166
Ok. So the problem seems to be cases where some file or gconf entry has not been created yet. That should be enough to help me get started on fixing the issue =)
 
thp's Avatar
Posts: 1,391 | Thanked: 4,272 times | Joined on Sep 2007 @ Vienna, Austria
#167
I've now tried removing the gconf entry for MaePad, so that it thinks its a fresh install, however, I was not able to reproduce this bug. I still get the "Welcome to MaePad" dialog where I can choose to create a new file (and then saving it, etc.. works fine).

You can remove the gconf entry with this command:

Code:
gconftool-2 -u /apps/maepad/general/lastdocument
 
Posts: 25 | Thanked: 9 times | Joined on Sep 2010
#168
Originally Posted by thp View Post
I've now tried removing the gconf entry for MaePad, so that it thinks its a fresh install, however, I was not able to reproduce this bug. I still get the "Welcome to MaePad" dialog where I can choose to create a new file (and then saving it, etc.. works fine).

You can remove the gconf entry with this command:

Code:
gconftool-2 -u /apps/maepad/general/lastdocument
Hello! Sorry for the late response, i though that i would get an email when someone wrote a response in the thread. I did try to remove the settings but I still get the same error..

$ maepad
Init: 0x46567270
**
ERROR:dbus-gproxy.c:2269:dbus_g_proxy_marshal_args_to_message : code should not be reached
Aborted

Do you want me to try something else?

Thanks!
 
thp's Avatar
Posts: 1,391 | Thanked: 4,272 times | Joined on Sep 2007 @ Vienna, Austria
#169
I've implemented live search (filter down the list of memos with the keyboard) yesterday, but it kind of conflicts (obviously) with the keyboard shortcuts (like "o", "w", jkl, ...) in the main view, so I'm not sure what would be the best way to add this:
  • Get rid of keyboard shortcuts on the main page / move them to arrows+return where possible
  • Have live search be started with "/" only, which makes searching a bit more difficult, but does not conflict with the other bindings

I found that I accidentally hit "o" or "w" in the main view, because I got so used to it, and I figured that other users might, too - what do you think? Would having live search be more important than the keyboard shortcuts? Would "/" be okay or should it be "normal" live search (as soon as you type something)?
 
Posts: 48 | Thanked: 9 times | Joined on Jan 2010
#170
I suggest, that you stick with the current key bindings (h,j,k,l, etc) and have "/", or something else, as the search key

Remember that you intended you make it feel like vi. Making it non-modal will surprise users, unless that is your intention.
 

The Following User Says Thank You to ebzzry For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 14:33.