[Bug 173643] New: Cannot position notes on multiple monitors, existing position corrupted

2008-10-26 Thread Raman Gupta
http://bugs.kde.org/show_bug.cgi?id=173643

   Summary: Cannot position notes on multiple monitors, existing
position corrupted
   Product: knotes
   Version: 3.5
  Platform: Fedora RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: [EMAIL PROTECTED]


Version:(using KDE 3.5.10)
OS:Linux
Installed from:Fedora RPMs

I have a dual-screen setup. There are two problems related to knotes with this
setup:

1) Notes do not keep position across monitors. If there are notes positioned on
both monitors, after a hide/show all notes appear on one of the two monitors.
Notes that were on the other monitor appear on the edge of the current monitor
closest to the monitor on which the note was positioned.

2) After a hide/show knotes moves all of my notes to the monitor which has the
focus [1]. If that monitor is not the one on which the notes were previously
positioned, then all the notes lose their x position and move to the edge of
the monitor.

[1] Sometimes focus is not sufficient -- selecting some text in the focused
window seems to more reliably force the notes to appear on that monitor.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[knotes] [Bug 338531] New: Unable to migrate notes, Failed to create resource: Agent instance creation timed out.

2014-08-24 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=338531

Bug ID: 338531
   Summary: Unable to migrate notes, Failed to create resource:
Agent instance creation timed out.
   Product: knotes
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rocketra...@gmail.com
CC: myr...@kde.org

I am unable to migrate my old knotes into Knotes KDE version 4.13.3. I have
reviewed and tried all the debugging information in #333640, and it still
doesn't work. The migration log is:

[Sun Aug 24 14:53:40 2014] Info   : Starting migration...
[Sun Aug 24 14:53:40 2014] Info   : Beginning KNotes migration...
[Sun Aug 24 14:53:40 2014] Info   : Creating instance of type
akonadi_akonotes_resource
[Sun Aug 24 14:53:50 2014] ERROR  : Migration failed: Failed to create
resource: Agent instance creation timed out.
[Sun Aug 24 14:53:50 2014] Info   : KNotes migration finished
[Sun Aug 24 14:53:50 2014] Info   : Migration finished.

The old kresources does exist and points to a valid notes.ics:

cat .kde/share/config/kresources/notes/stdrc 
[General]
ResourceKeys=4AAtTLzChG
Standard=4AAtTLzChG

[Resource_4AAtTLzChG]
NotesURL[$e]=file://$HOME/.kde/share/apps/knotes/notes.ics
ResourceIdentifier=4AAtTLzChG
ResourceIsActive=true
ResourceIsReadOnly=false
ResourceName=Notes
ResourceType=file

# ls -l $HOME/.kde/share/apps/knotes/notes.ics
-rw-rw-r--. 1 raman raman 2918 Mar 13 23:50
/home/raman/.kde/share/apps/knotes/notes.ics

I have tried akonadictl fsck and akonadictl restart. Here is the output of
akonadictl status:

# akonadictl status
Akonadi Control: running
Akonadi Server: running
search paths:  (/home/raman/.kde/lib64/kde4/plugins/,
/usr/lib64/kde4/plugins/, /usr/lib64/qt4/plugins,
/usr/lib64/kde4/plugins, /usr/bin, /home/raman/.kde/lib64/kde4/,
/usr/lib64/kde4/) 
Akonadi Server Search Support: available (Remote Search, Akonadi Baloo Search
Plugin)
Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent,
akonadi_baloo_indexer, akonadi_birthdays_resource, akonadi_contacts_resource,
akonadi_davgroupware_resource, akonadi_facebook_resource,
akonadi_folderarchive_agent, akonadi_googlecalendar_resource,
akonadi_googlecontacts_resource, akonadi_ical_resource,
akonadi_icaldir_resource, akonadi_imap_resource, akonadi_invitations_agent,
akonadi_kabc_resource, akonadi_kalarm_dir_resource, akonadi_kalarm_resource,
akonadi_kcal_resource, akonadi_kdeaccounts_resource,
akonadi_kolabproxy_resource, akonadi_localbookmarks_resource,
akonadi_maildir_resource, akonadi_maildispatcher_agent,
akonadi_mailfilter_agent, akonadi_mailtransport_dummy_resource,
akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource,
akonadi_nepomuk_feeder, akonadi_newmailnotifier_agent, akonadi_nntp_resource,
akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource,
akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_vcard_resource,
akonadi_vcarddir_resource

I have erased all the akonadi_akonotes_resource_* using akonadiconsole and
tried again, and still get the same error every time. I have no idea what the
problem is.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[knotes] [Bug 338531] Unable to migrate notes, Failed to create resource: Agent instance creation timed out.

2014-08-24 Thread Raman Gupta
https://bugs.kde.org/show_bug.cgi?id=338531

Raman Gupta rocketra...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Raman Gupta rocketra...@gmail.com ---
Resetting akonadi using the instructions here solved the problem:

http://docs.kde.org/stable/en/kdepim/kmail/clean-start-after-a-failed-migration.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[libkgapi] [Bug 318405] Broken timezones handling

2015-12-16 Thread Raman Gupta via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=318405

--- Comment #11 from Raman Gupta <rocketra...@gmail.com> ---
It seems to be working correctly on KDE Korganizer 4.14.10 with libkgapi 2.2.0
(tested on Fedora 23). My test cases are all ok. Can others with the same issue
confirm?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs