[kaddressbook] [Bug 371195] Edit Contact Name is missing Display Name field

2022-10-27 Thread Kai Holthaus
https://bugs.kde.org/show_bug.cgi?id=371195

Kai Holthaus  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #3 from Kai Holthaus  ---
Sorry for the multiple reporting. I was wrong - I found the field. Setting
status to resolved.

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

[kaddressbook] [Bug 371195] Edit Contact Name is missing Display Name field

2022-10-27 Thread Kai Holthaus
https://bugs.kde.org/show_bug.cgi?id=371195

Kai Holthaus  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #2 from Kai Holthaus  ---
Hi -

Currently using Kontact 5.19.3 - I do not see a DisplayName field in the
Contact edit dialog.

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

[kontact] [Bug 384310] Kontact crashes every time when started

2017-09-28 Thread Kai Holthaus
https://bugs.kde.org/show_bug.cgi?id=384310

--- Comment #3 from Kai Holthaus  ---
I have a hard time imagining the HTML email bug to be a duplicate, because I
don't use any preview panes. Meaning, Kontact crashes without trying to
interpret HTML.
Kontact works fine on my laptop when I use the internal display. It crashes
when any external display is connected.

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

[kontact] [Bug 384310] Kontact crashes every time when started

2017-09-08 Thread Kai Holthaus
https://bugs.kde.org/show_bug.cgi?id=384310

--- Comment #1 from Kai Holthaus  ---
Additional info:
Crash happens when Laptop (Lenovo Thinkpad X220) is docked and connected to two
external displays (via displayport and vga).
Crash does not happen when laptop is undocked and internal display ist used.

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

[kontact] [Bug 384310] New: Kontact crashes every time when started

2017-09-03 Thread Kai Holthaus
https://bugs.kde.org/show_bug.cgi?id=384310

Bug ID: 384310
   Summary: Kontact crashes every time when started
   Product: kontact
   Version: 5.2.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kai_holth...@hotmail.com
  Target Milestone: ---

Application: kontact (5.2.3)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.10.0-33-generic x86_64
Distribution: Ubuntu 17.04

-- Information about the crash:
- What I was doing when the application crashed:
Starting Kontact. Kontact windows is displayed, and then immediately Kontact
crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9f8f1df000 (LWP 4400))]

Thread 18 (Thread 0x7f9ed9687700 (LWP 4430)):
#0  0x7f9f850c98b9 in pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225
#1  0x7f9f8c7d0a26 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9f8c7cc252 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9f850c36da in start_thread (arg=0x7f9ed9687700) at
pthread_create.c:456
#5  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 17 (Thread 0x7f9ed9e88700 (LWP 4429)):
#0  0x7f9f8333aef0 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4b70 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ed9e88700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f9ef910f700 (LWP 4422)):
#0  0x7f9f8333aef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4f81 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f5514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ef910f700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f9ef9910700 (LWP 4420)):
#0  0x7f9f8333aef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4a60 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9f8c99cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9f8c7caf83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9f8c7cfc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9f850c36da in start_thread (arg=0x7f9ef9910700) at
pthread_create.c:456
#9  0x7f9f8bec5d7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 14 (Thread 0x7f9efa111700 (LWP 4418)):
#0  0x7f9f832f2557 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9f832f4ec4 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9f832f5514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9f832f568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f9f8c9f30bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Co

[kaddressbook] [Bug 371195] Edit Contact Name is missing Display Name field

2016-10-18 Thread Kai Holthaus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371195

Kai Holthaus  changed:

   What|Removed |Added

 CC||kai_holth...@hotmail.com

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


[kaddressbook] [Bug 371195] New: Edit Contact Name is missing Display Name field

2016-10-18 Thread Kai Holthaus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371195

Bug ID: 371195
   Summary: Edit Contact Name is missing Display Name field
   Product: kaddressbook
   Version: 5.2.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: kai_holth...@hotmail.com
CC: to...@kde.org

The edit contact form used to have the "Display Name" field, which is used to
specify how a contact should be displayed (e.g. "first last" or "last, first").
That field is no longer available in the edit name form.

Reproducible: Always

Steps to Reproduce:
1. Create new contact or open an existing one to edit
2.Enter / update name, click on "..." button for edit name dialog

Actual Results:  
Display Name field is not present - neither in the overall contact edit dialog,
nor in the edit name dialog.

Expected Results:  
Display Name field should be possible to edit.

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