Menu

#1344 Linux. Triggers not working

KeePass_2.x
closed
nobody
5
2015-03-22
2015-02-03
No

Linux Mint Cinnamon 64bit
Keepass ver 2.25

When you have open the keepass2 and you try to set action triggers then an error occurs: The object was used after being dispoded.

1 Attachments

Related

Bugs: #1344

Discussion

  • Paul

    Paul - 2015-02-03

    Known problem in mono. See this thread for a work around.
    https://sourceforge.net/p/keepass/discussion/329221/thread/6bfc7514/

    cheers, Paul

     
    • John Pagourtzis

      John Pagourtzis - 2015-02-04

      Will it be fixed? In future releases or update?

      How and where to find in windows my trigger file so i can use it to my
      linux mint 17 machine? I am backing up my database file to my owncloud
      setup at home :) and i want to do the same with my linux.

      Thanks,

      John Pagourtzis
      On Feb 3, 2015 12:31 PM, "Paul" pail459@users.sf.net wrote:

      Known problem in mono. See this thread for a work around.
      https://sourceforge.net/p/keepass/discussion/329221/thread/6bfc7514/

      cheers, Paul

      Status: open
      Group: KeePass_2.x
      Labels: triggers linux mint 17
      Created: Tue Feb 03, 2015 08:55 AM UTC by John Pagourtzis
      Last Updated: Tue Feb 03, 2015 08:55 AM UTC
      Owner: nobody

      Linux Mint Cinnamon 64bit
      Keepass ver 2.25

      When you have open the keepass2 and you try to set action triggers then an
      error occurs: The object was used after being dispoded.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/keepass/bugs/1344/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Bugs: #1344

  • John Pagourtzis

    John Pagourtzis - 2015-02-04

    I believe its a very important feature that must be working. Backing up you password database is a serious thing :)

    Thanks anyways for the good job.

     

    Last edit: John Pagourtzis 2015-02-04
  • Paul

    Paul - 2015-02-04

    As it's a mono bug it's unlikely to be fixed in KeePass.

    If you have triggers in Windows, open the triggers window and click the Tools button. You can copy all or specific triggers to the clipboard.

    cheers, Paul

     
    • John Pagourtzis

      John Pagourtzis - 2015-02-05

      Copying the trigger will take all the events,actions etc... too?

      Thank you.

       

      Last edit: John Pagourtzis 2015-02-05
    • John Pagourtzis

      John Pagourtzis - 2015-02-05

      Copying extracts the trigger data in XML format. You then replace the <Triggers/> tag in your KeePass.config.xml with the <Triggers></Triggers> section from the copy. Restart KeePass and let us know how it goes, preferably in the thread linked above - bugs reports are not good for discussion.

      cheers, Paul

      Hello Paul.
      Ok i will try it as soon as possible and update here the results.

      Thank you.

       
  • Paul

    Paul - 2015-02-05

    Copying extracts the trigger data in XML format. You then replace the <Triggers/> tag in your KeePass.config.xml with the <Triggers></Triggers> section from the copy. Restart KeePass and let us know how it goes, preferably in the thread linked above - bugs reports are not good for discussion.

    cheers, Paul

     
    • John Pagourtzis

      John Pagourtzis - 2015-02-06

      My KeePass.config.xml doesnt contain <Triggers></Triggers>.

      Should i add them my self?
      Am i looking the proper xml (/usr/lib/keepass2)?

      Thank you.

      UPDATE.
      Found the xml (thanks Paul) and triggers working fine now.

      You can close the bug.
      Thank you.

       

      Last edit: John Pagourtzis 2015-02-09
  • Paul

    Paul - 2015-02-09

    Updating KeePass in Linux is just a matter of extracting the portable package over the top of the existing KeePass files, probably in /usr/YOU/lib/keePass.

    cheers, Paul

     
  • Dominik Reichl

    Dominik Reichl - 2015-03-22
    • status: open --> closed
     
  • Dominik Reichl

    Dominik Reichl - 2015-03-22

    This was caused by the following Mono bug:
    https://bugzilla.xamarin.com/show_bug.cgi?id=9653

    Apparently the Mono developers have fixed it in the beginning of 2015.

    Best regards,
    Dominik

     

Log in to post a comment.