[kde] [Bug 504040] New: Issue: Contact Editing Non-functional + Google Account Duplication in KAddressBook

bugzilla_noreply at kde.org bugzilla_noreply at kde.org
Sun May 11 06:10:27 BST 2025


https://bugs.kde.org/show_bug.cgi?id=504040

            Bug ID: 504040
           Summary: Issue: Contact Editing Non-functional + Google Account
                    Duplication in KAddressBook
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: jshand2013 at gmail.com
  Target Milestone: ---

# šŸž Issue: Contact Editing Non-functional + Google Account Duplication in
KAddressBook

## A. āŒ Cannot Edit Selected Contact

### Summary
In the current KAddressBook source build, selecting a contact and attempting to
edit it results in **no UI response** — the expected contact editor dialog does
not appear.

### Technical Findings
- The codebase has **no definition or invocation** of `editContact()` or
equivalent methods in `MainWidget`, `MainWindow`, or related classes.
- No `QAction`, signal/slot, or context menu appears to be triggering any
editing behavior.
- There is **no reference to `ContactEditor`, `ItemEditJob`, or
`Akonadi::ItemEditJob`** within the available source.
- This suggests the **editing logic is either missing, disabled, or not
integrated** in this version of the source.

### Possible Causes
- The editor module (e.g., `ContactEditor` or similar) may be excluded or
missing from the build.
- UI logic may be incomplete or lacks connections to an editing interface.
- Contacts may be treated as read-only due to resource backend issues (e.g.,
LDAP, DAV, or remote Google).

### Recommendations
- Reintroduce or reconnect contact editing logic (`ContactEditor`, etc.) in the
UI.
- Ensure address books are not flagged read-only unless explicitly configured
that way.
- Audit UI interaction triggers (buttons, menu items) to verify they're bound
to editing actions.

---

## B. šŸŒ€ Google Account Appears Duplicated in KAddressBook

### Summary
When adding a Google account via either KAddressBook or KOrganizer, **duplicate
address book entries appear** in KAddressBook.

### Behavior
- If a Google account is added from the Calendar (KOrganizer), it appears
correctly.
- If the same account is then added from KAddressBook (or vice versa), it
creates **a new, redundant Google address book resource**.
- The same Google contacts are then displayed multiple times, however seems
that default is all ticked and displaying correctly and the duplicate has no
ticks.  have not tried to verify multiple duplicate contacts

### Technical Observations
- Google account integration uses the `akonadi_google_resource`.
- There appears to be **no deduplication mechanism** to check if an
account/resource already exists before creating a new one.
- The problem seems related to the **account setup workflow being duplicated**
between KOrganizer and KAddressBook, each triggering independent Akonadi
resource creation.

### Recommendations
- Introduce a resource check before adding a new Google Groupware resource.
- Consolidate Google account setup logic across KDE PIM apps.
- If a Google resource is already registered with Akonadi, reuse or link to it
instead of creating a new instance.

---

Operating System: openSUSE Tumbleweed 20250508
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.5-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 Ɨ IntelĀ® Coreā„¢ 7 150U
Memory: 15.3 GiB of RAM
Graphics Processor: IntelĀ® Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 16 5640

Please advise if these issues are known, or if there is an intended workflow to
avoid duplication and restore editing functionality.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list