[systemsettings] [Bug 457506] Charge limit doesn't save settings

2022-08-04 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=457506

Camilo Bohórquez  changed:

   What|Removed |Added

 CC||camib...@gmail.com

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

[systemsettings] [Bug 457506] New: Charge limit doesn't save settings

2022-08-04 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=457506

Bug ID: 457506
   Summary: Charge limit doesn't save settings
   Product: systemsettings
   Version: 5.24.4
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_powerdevil
  Assignee: plasma-b...@kde.org
  Reporter: camib...@gmail.com
CC: k...@privat.broulik.de
  Target Milestone: ---

Created attachment 151125
  --> https://bugs.kde.org/attachment.cgi?id=151125=edit
Desktop recording with steps to reproduce

I try to save settings for battery charge limits, but this settings doesn't
saved, once apply button is clicked.

STEPS TO REPRODUCE (See the desktop recording attached)

1. Set 'stop charging' percentage at 85%
2. Ser 'start charging' percentage at 15%
3. Click Apply and enter my password as sudo (No root password).

OBSERVED RESULT

Battery charge limit remains as:

- Stop Charging: 50%
- Start Charging: Always charge when plugged in

EXPECTED RESULT

Remain desired settings saved.


SOFTWARE/OS VERSIONS

Linux: 5.15.0-43-lowlatency (64 bit)
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

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

[kaddressbook] [Bug 449523] New: KAddressbook - No Google Contacts appear.

2022-02-02 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=449523

Bug ID: 449523
   Summary: KAddressbook - No Google Contacts appear.
   Product: kaddressbook
   Version: 5.13.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: camib...@gmail.com
CC: to...@kde.org
  Target Milestone: ---

Hi there:

I've added two Google accounts to KAddressbook, but I can't view my contacts
list.

In Akonadi console, I can view the two Google Contacts agents, but the contacts
still unavailable on KAddressbook.

Any ideas ???

STEPS TO REPRODUCE

1.  Add Google Contacts to KAddressbook
2.  Login to Google Account and authorize KDE-Pim / Akonadi

OBSERVED RESULT

Can't view contacts lists.

EXPECTED RESULT

View, add, edit, and remove Google contacts.

Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-97-lowlatency
OS Type: 64-bit
Processors: 2 × Intel® Core™2 Duo CPU T5250 @ 1.50GHz
Memory: 2.9 GiB of RAM

ADDITIONAL INFORMATION

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

[kaddressbook] [Bug 359178] Kaddressbook does not download new contacts from Google Contacts

2022-02-02 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=359178

Camilo Bohórquez  changed:

   What|Removed |Added

 CC||camib...@gmail.com

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

[kontact] [Bug 404543] Kontact Crashes When Adding AdBlock Subscription to Akregator

2019-04-07 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=404543

--- Comment #3 from Camilo Bohórquez  ---
Created attachment 119289
  --> https://bugs.kde.org/attachment.cgi?id=119289=edit
New crash information added by DrKonqi

akregator (5.10.3) using Qt 5.12.2

- What I was doing when the application crashed:

I try to add a AdBlock subscription to my KDE PIM Suite.

- Custom settings of the application:

-- Backtrace (Reduced):
#6  0x7f981836c41a in AdBlock::AdBlockSettingWidget::save
(this=0x5568878f96e0) at
/usr/src/debug/kdepim-addons-18.12.3-1.1.x86_64/plugins/webengineurlinterceptor/adblock/lib/widgets/adblocksettingwidget.cpp:285
#7  0x7f981836836d in
AdBlock::AdblockPluginUrlInterceptorConfigureWidget::saveSettings
(this=0x55688788ed40) at
/usr/src/debug/kdepim-addons-18.12.3-1.1.x86_64/plugins/webengineurlinterceptor/adblock/lib/widgets/adblockpluginurlinterceptorconfigurewidget.cpp:48
#8  0x7f983308168d in PimCommon::ConfigurePluginDialog::slotAccepted
(this=0x556880ade1e0) at
/usr/src/debug/pimcommon-18.12.3-1.1.x86_64/src/pimcommon/configureplugins/configureplugindialog.cpp:86
#9  0x7f9831ba1343 in QtPrivate::QSlotObjectBase::call (a=0x7ffd2989aa70,
r=0x556880ade1e0, this=0x5568879dd360) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394
[...]
#11 0x7f98326f37c0 in QDialogButtonBoxPrivate::_q_handleButtonClicked
(this=) at widgets/qdialogbuttonbox.cpp:864

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

[kontact] [Bug 404543] Kontact Crashes When Adding AdBlock Subscription to Akregator

2019-04-07 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=404543

Camilo Bohórquez  changed:

   What|Removed |Added

 CC||camib...@gmail.com

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

[digikam] [Bug 376366] New: Not show nothing...

2017-02-11 Thread Camilo Bohórquez
https://bugs.kde.org/show_bug.cgi?id=376366

Bug ID: 376366
   Summary: Not show nothing...
   Product: digikam
   Version: 5.4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: showfoto
  Assignee: digikam-de...@kde.org
  Reporter: camib...@gmail.com
  Target Milestone: ---

Created attachment 103982
  --> https://bugs.kde.org/attachment.cgi?id=103982=edit
Showfoto main window

In this version at the LXQt desktop, the app not show nothing at open the JPEG
files in any resolution.

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

[plasmashell] [Bug 367616] New: Frequently KDE Plasma general crash...

2016-08-20 Thread Camilo Bohórquez via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367616

Bug ID: 367616
   Summary: Frequently KDE Plasma general crash...
   Product: plasmashell
   Version: 5.7.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: camib...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.7.3)

Qt Version: 5.6.1
Frameworks Version: 5.24.0
Operating System: Linux 4.7.0-2-default x86_64
Distribution: "openSUSE Tumbleweed (20160812) (x86_64)"

-- Information about the crash:
- Unusual behavior I noticed:

also ksmserver & kwin ocassionaly crash

The crash can be reproduced sometimes.

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

Thread 10 (Thread 0x7f4a2e789700 (LWP 3476)):
#0  0x7f4afb7a50a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4afb760f50 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4afb7613e2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4a2f7f85f6 in  () at /usr/lib64/libgio-2.0.so.0
#4  0x7f4afb787335 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7f4a2ef8a700 (LWP 3475)):
#0  0x7f4aff0d6a1d in poll () at /lib64/libc.so.6
#1  0x7f4afb761056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4afb76116c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4afb7611b1 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f4afb787335 in  () at /usr/lib64/libglib-2.0.so.0
#5  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#6  0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7f4a3cf7e700 (LWP 3286)):
#0  0x7f4afb7a50a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4afb760a7c in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4afb760ff4 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4afb76116c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4affa01aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4aff9a976a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4aff7cf3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4aff7d42d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7f4a4d02f700 (LWP 2955)):
#0  0x7f4afb7a50c4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f4afb76059c in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f4afb760f7b in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f4afb76116c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f4affa01aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f4aff9a976a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f4aff7cf3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f4b03708606 in  () at /usr/lib64/libQt5Quick.so.5
#8  0x7f4aff7d42d8 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#10 0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 6 (Thread 0x7f4adbfff700 (LWP 2842)):
#0  0x7f4afe8df09f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7f4b0517efc4 in  () at /usr/lib64/libQt5Script.so.5
#2  0x7f4b0517f009 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#4  0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7f4ae6001700 (LWP 2820)):
#0  0x7f4aff0d6a1d in poll () at /lib64/libc.so.6
#1  0x7f4afb761056 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f4afb76116c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f4affa01aeb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f4aff9a976a in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f4aff7cf3b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f4b02b791e5 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7f4aff7d42d8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f4afe8d9474 in start_thread () at /lib64/libpthread.so.0
#9  0x7f4aff0df3ed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7f4ae79d3700 (LWP 2778)):
#0  0x7f4aff0eba82 in __libc_disable_asynccancel () at /lib64/libc.so.6
#1  0x7f4aff0d6a29 in poll () at /lib64/libc.so.6
#2 

[digikam] [Bug 367611] Time gap on renaming at download...

2016-08-20 Thread Camilo Bohórquez via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367611

--- Comment #1 from Camilo Bohórquez <camib...@gmail.com> ---
Correction: The time difference is, My Time Zone (UTC -05:00) minus 5 hours.

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

[digikam] [Bug 367611] Time gap on renaming at download...

2016-08-20 Thread Camilo Bohórquez via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367611

Camilo Bohórquez <camib...@gmail.com> changed:

   What|Removed |Added

 CC||camib...@gmail.com

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

[digikam] [Bug 367611] New: Time gap on renaming at download...

2016-08-20 Thread Camilo Bohórquez via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=367611

Bug ID: 367611
   Summary: Time gap on renaming at download...
   Product: digikam
   Version: 5.1.0
  Platform: openSUSE RPMs
   URL: https://drive.google.com/drive/folders/0B-p9Wx8eR_XmUF
dHNW5YR1JvZGs?usp=sharing
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: Import-Rename
  Assignee: digikam-de...@kde.org
  Reporter: camib...@gmail.com

When I set my system for UTC Hardware clock as YaST time settings suggest (See
YaST screenshot), digiKam at importing process rename my pictures & videos with
a time difference about my real time zone (See the digikam importing
screenshot). The photograph properties show a real creation date from my
camera, but digiKam show and rename my pictures in this case with the UTC time
zone.

The problem only solves temporarily, when I uncheck the UTC hardware clock
option in YaST. But I like mantain enabled this option and without this bug at
impoort and renaming in digiKam.

Thanks in advance, for solve this problem.

Reproducible: Always

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