[systemsettings] [Bug 371551] New: System Pref crash

2016-10-23 Thread ANTONIO via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=371551

Bug ID: 371551
   Summary: System Pref crash
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: alopezsa...@gmail.com

Application: systemsettings (4.11.20)
KDE Platform Version: 4.14.9
Qt Version: 4.8.6
Operating System: Linux 3.16.7-42-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I open Multimedia in System Preferences, and all crash
Probably is due to have qt4 and qt5 at same time, but I can't pull off one of
this.

The crash can be reproduced every time.

-- Backtrace:
Application: Preferencias del sistema (systemsettings), signal: Segmentation
fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  __strcmp_sse2_unaligned () at
../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29
#7  0x7fb58cc55fee in qMetaTypeStaticType (length=22, typeName=0x42e6478
) at kernel/qmetatype.cpp:806
#8  QMetaType::registerNormalizedType (normalizedTypeName=...,
deleter=deleter@entry=0x7fb58d40c930
::Delete(void*)>, creator=creator@entry=0x7fb58d40cab0
::Create(void const*)>, destructor=destructor@entry=0x7fb58d40c890
::Destruct(void*)>, constructor=constructor@entry=0x7fb58d40c8a0
::Construct(void*, void const*)>, size=size@entry=16,
flags=flags@entry=..., metaObject=metaObject@entry=0x0) at
kernel/qmetatype.cpp:896
#9  0x7fb58d155f57 in qRegisterNormalizedMetaType
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, normalizedTypeName=...) at
../../src/corelib/kernel/qmetatype.h:1603
#10 qRegisterMetaType
(defined=QtPrivate::MetaTypeDefinedHelper::Defined, dummy=0x, typeName=0x7fb58d4e89de
"QPaintBufferCacheEntry") at ../../src/corelib/kernel/qmetatype.h:1628
#11 qt_metatype_id () at painting/qpaintbuffer.cpp:2081
#12 qt_metatype_id () at ../../src/corelib/kernel/qmetatype.h:1509
#13 qMetaTypeId () at
../../src/corelib/kernel/qmetatype.h:1649
#14 qRegisterMetaTypeStreamOperators () at
../../src/corelib/kernel/qmetatype.h:1698
#15 qRegisterPaintBufferMetaTypes () at painting/qpaintbuffer.cpp:2107
#16 qRegisterPaintBufferMetaTypes_ctor_class_ (this=) at
painting/qpaintbuffer.cpp:2111
#17 __static_initialization_and_destruction_0 (__priority=65535,
__initialize_p=1) at painting/qpaintbuffer.cpp:2111
#18 _GLOBAL__sub_I_qpaintbuffer.cpp(void) () at painting/qpaintbuffer.cpp:2207
#19 0x7fb5b9f9c8ea in call_init (l=, argc=argc@entry=1,
argv=argv@entry=0x7fff15ee8808, env=env@entry=0x19b0e30) at dl-init.c:78
#20 0x7fb5b9f9c9d3 in call_init (env=0x19b0e30, argv=0x7fff15ee8808,
argc=1, l=) at dl-init.c:36
#21 _dl_init (main_map=main_map@entry=0x21687e0, argc=1, argv=0x7fff15ee8808,
env=0x19b0e30) at dl-init.c:126
#22 0x7fb5b9fa0b08 in dl_open_worker (a=a@entry=0x7fff15ee5638) at
dl-open.c:566
#23 0x7fb5b9f9c7a4 in _dl_catch_error
(objname=objname@entry=0x7fff15ee5628,
errstring=errstring@entry=0x7fff15ee5630,
mallocedp=mallocedp@entry=0x7fff15ee5627, operate=operate@entry=0x7fb5b9fa0830
, args=args@entry=0x7fff15ee5638) at dl-error.c:187
#24 0x7fb5b9fa02fb in _dl_open (file=0x2168270
"/usr/lib64/vlc/plugins/gui/libqt4_plugin.so", mode=-2147483647,
caller_dlopen=, nsid=-2, argc=1, argv=0x7fff15ee8808,
env=0x19b0e30) at dl-open.c:650
#25 0x7fb5ae45402b in dlopen_doit (a=a@entry=0x7fff15ee5850) at dlopen.c:66
#26 0x7fb5b9f9c7a4 in _dl_catch_error (objname=0x1791310,
errstring=0x1791318, mallocedp=0x1791308, operate=0x7fb5ae453fd0 ,
args=0x7fff15ee5850) at dl-error.c:187
#27 0x7fb5ae4545dd in _dlerror_run (operate=operate@entry=0x7fb5ae453fd0
, args=args@entry=0x7fff15ee5850) at dlerror.c:163
#28 0x7fb5ae4540c1 in __dlopen (file=file@entry=0x2168270
"/usr/lib64/vlc/plugins/gui/libqt4_plugin.so", mode=) at
dlopen.c:87
#29 0x7fb58ee1cdcf in module_Load (p_this=p_this@entry=0x2087ad8,
path=path@entry=0x2168270 "/usr/lib64/vlc/plugins/gui/libqt4_plugin.so",
p_handle=p_handle@entry=0x7fff15ee58a0, lazy=) at
posix/plugin.c:60
#30 0x7fb58ee0236b in module_InitDynamic (obj=0x2087ad8, path=0x2168270
"/usr/lib64/vlc/plugins/gui/libqt4_plugin.so", fast=) at
modules/bank.c:586
#31 0x7fb58ee0264b in AllocatePluginFile (st=,
relpath=, abspath=, bank=) at
modules/bank.c:529
#32 AllocatePluginDir (bank=0x7fff15ee5b20, maxdepth=2363017224, 

[kile] [Bug 369049] New: Fixed Word Warp of commented lines

2016-09-19 Thread Antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369049

Bug ID: 369049
   Summary: Fixed Word Warp of commented lines
   Product: kile
   Version: 2.1.3
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: editor
  Assignee: michel.lud...@kdemail.net
  Reporter: antonio.mario.car...@gmail.com

If you edit a file with a long comment line, longer than for example 80
columns.
If you activate fixed word wrap, at 80 column. Then you edit the comment line
and for example just remove a word or just insert and remove a space, the
editor automatically wrap all the paragraph as expected but it do not preserve
the semantics of comment. i.e. only the first line have the % for latex
comment. It would be important to save the comment semantics for the entire
paragraph, i.e. if a long line start with % and you edit that line the word
wrapper must introduce other %, at least the first time that it would wrap.


Reproducible: Always

Steps to Reproduce:
1. Write a long line and comment it. Without fixed word warp activated
2. Activate Fixed Word Wrap.
3. Edit the line. The first preserve the % the others no.

-- 
You are receiving this mail because:
You are watching all bug changes.


[plasmashell] [Bug 361245] New: Problemas ao alternar entre redes wi-fi

2016-03-31 Thread Antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361245

Bug ID: 361245
   Summary: Problemas ao alternar entre redes wi-fi
   Product: plasmashell
   Version: 5.6.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: antonio.jr.sso...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.1)

Qt Version: 5.6.0
Frameworks Version: 5.20.0
Operating System: Linux 4.4.5-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed:

- Unusual behavior I noticed:

- Custom settings of the application:

-Desktop Environment crashed after network wi-fi changes, and this problem
always happend, but i don't know what to do.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdf26b47800 (LWP 1090))]

Thread 10 (Thread 0x7fdf0f9b0700 (LWP 1092)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf24fe2ae2 in ?? () from /usr/lib/libxcb.so.1
#2  0x7fdf24fe4757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7fdf112d2a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#4  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#5  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#6  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 9 (Thread 0x7fdf0dd84700 (LWP 1093)):
#0  0x7fdf1c466003 in ?? () from /usr/lib/libglib-2.0.so.0
#1  0x7fdf1c4684ab in g_main_context_prepare () from
/usr/lib/libglib-2.0.so.0
#2  0x7fdf1c468eab in ?? () from /usr/lib/libglib-2.0.so.0
#3  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#4  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#5  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#6  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#7  0x7fdf2168fa55 in ?? () from /usr/lib/libQt5DBus.so.5
#8  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#9  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#10 0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 8 (Thread 0x7fdf07fff700 (LWP 1109)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf1c468f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7fdef9a1e700 (LWP 1117)):
#0  0x7fdf1ffe4c3d in poll () from /usr/lib/libc.so.6
#1  0x7fdf1c468f7c in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7fdef3dc7700 (LWP 1124)):
#0  0x7fdf1c467f76 in g_main_context_acquire () from
/usr/lib/libglib-2.0.so.0
#1  0x7fdf1c468e35 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7fdf1c46908c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7fdf208fccab in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7fdf208a56fa in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7fdf206cefe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x7fdf23a71915 in ?? () from /usr/lib/libQt5Qml.so.5
#7  0x7fdf206d3de8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x7fdf1f7e7424 in start_thread () from /usr/lib/libpthread.so.0
#9  0x7fdf1ffedcbd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7fdef2581700 (LWP 1127)):
#0  0x7fdf1f7ed03f in pthread_cond_wait@@GLIBC_2.3.2 () from

[telepathy] [Bug 347219] files overlap with gnome account

2016-03-21 Thread antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=347219

antonio <216...@gmail.com> changed:

   What|Removed |Added

 CC||216...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 359505] Image deleted after applying tag

2016-02-20 Thread antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359505

antonio  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #4 from antonio  ---
I'm sorry I put wron status

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 359505] Image deleted after applying tag

2016-02-20 Thread antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359505

--- Comment #3 from antonio  ---
Hi Gill,
the problem isn't solved yet.
the requested entries of kdebugdialog, during wrong operation, are:
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::getIptcKeywords:
"/home/antonio/Immagini/img/IMG_0092.JPG"  ==> Read Iptc Keywords:  ()
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::setIptcKeywords:
"/home/antonio/Immagini/img/IMG_0092.JPG"  ==> New Iptc Keywords:  ("Isole
Eolie")
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::save: KExiv2::metadataWritingMode 0
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::save: Will write Metadata to file
"IMG_0092.JPG"
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations:
wroteComment:  true
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: wroteEXIF: 
true
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: wroteIPTC: 
true
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: wroteXMP: 
true
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::Private::saveOperations: File time
stamp restored
digikam(4608)/KEXIV2 KExiv2Iface::KExiv2::save: Metadata for file
"IMG_0092.JPG" written to file.
If I undersand well all operations are completed w/o errors!
Today I add a new ubuntu user and, surprise, digikam, on that user,  seems to
work like a charm.
I'll test for a wile just to bew sure that it isn't a false test.
Many thanks and best regards
Antonio

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 359505] Image deleted after applying tag

2016-02-17 Thread antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359505

--- Comment #2 from antonio  ---
Thank you Gilles.
Waiting your help I disabled writing metadata into image and I enable writing
them to sidecar file just to avoid unwanted effect. That work well.
Now, in order to follow your suggestion, I have restore the initial setting:
label into images, caption and titles and template (copyright etc)
Now I can reproduce the bug because now all it working, I don't know wy, Well!!
If problem appears again I'll put in action your suggestion.
Many thanks for you help
Best regards
Antonio

-- 
You are receiving this mail because:
You are watching all bug changes.


[digikam] [Bug 359505] New: Image deleted after applying tag

2016-02-17 Thread antonio via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359505

Bug ID: 359505
   Summary: Image deleted after applying tag
   Product: digikam
   Version: 4.14.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: Metadata
  Assignee: digikam-de...@kde.org
  Reporter: antoniodipo...@gmail.com

I'm experiencing a problem when I try to add/modify exif/iptc and other
metadata tags 
This is a very strange and dangerous isn'it?
My environment is:
Ubuntu 14.04 xamd64
Linux 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64
GNU/Linux
digikam 4:4.14.0-trusty~ppa1
Since digiKam use external libraries to manage metadata (Exiv2) I would like to
involve exiv2 people clicking on Exiv2 library bugs and wishes on your support
page  
but I can't do it because the link dev.robotbattle.com/bugs/my_view_page.php
dosen't work.

Could you help me to find this destructive problem?
If you need more info or more test tell me that.
Waiting your help I send you my best regards
Antonio

Reproducible: Always

Steps to Reproduce:
1.Open digikam and select an image
2.try to change anything metadata 
3.click on apply button

Actual Results:  
the selected file will be deleted

-- 
You are receiving this mail because:
You are watching all bug changes.