[plasma-pa] [Bug 402664] New: Default sound device set not working

2018-12-28 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=402664

Bug ID: 402664
   Summary: Default sound device set not working
   Product: plasma-pa
   Version: 5.14.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: anvar...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
I have two sound devices on my PC (Analog and HDMI), and I usually have enabled
the option "Add virtual device for simultaneous output", and normally I use the
Analog HD Audio output as default sound device, but now when I set the Analog
output as default and restart the session, the default sound device always back
to Simultaneous virtual device.

STEPS TO REPRODUCE
1. Enable option "Add virtual device for simultaneous output" in Volume Sound
Preferences.
2. Set Analog output (or another instead of Simultaneous virtual device) as
default.
3. Restart the session.

OBSERVED RESULT
The default sound device always back to Simultaneous virtual device.

EXPECTED RESULT
The default sound device should be the one I set.

SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: KDE Neon 5.14.4
(available in About System)
KDE Plasma Version: 5.14.4
KDE Frameworks Version: 5.53.0
Qt Version: 5.11.2

ADDITIONAL INFORMATION
I have tried this in Kubuntu 18.04 and this problem is not present.

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

[dolphin] [Bug 395723] New: The median line width of icons view mode is the same as the small width

2018-06-21 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=395723

Bug ID: 395723
   Summary: The median line width of icons view mode is the same
as the small width
   Product: dolphin
   Version: 18.04.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Created attachment 113501
  --> https://bugs.kde.org/attachment.cgi?id=113501&action=edit
Width Text Screenshots of Dolphin Icons View

I am using KDE Neon User Edition, and I've noticed that in some of the latest
updates (I do not know if Plasma, or KDE Apps, or Frameworks...), that the
median width of the text in the icons view mode of Dolphin is exactly the same
as the small width, you can select any of them and the width does not change.
Seeing this I tried the big width, but the difference in width size here is
huge.

I know that the bug is at some point in the latest updates, because on my
laptop I use Kubuntu 18.04 and this problem is not present: there is a
difference between the medium and small text widths, and the median is seen as
it has been since the beginning in the icons view.

In the attached file I show you three screenshots where you can see the width
size difference between median, small and big text width.

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

[Discover] [Bug 383413] Discover crashes in Transaction::isActive() during or after updating

2017-11-08 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=383413

--- Comment #6 from VaryHeavy  ---
(In reply to Nate Graham from comment #5)
> All instances of this crash happened in Discover 5.8.x and Qt 5.7.1 or 5.6.1.
> 
> Is anyone able to reproduce this crash using a newer version of Discover or
> Qt?

In KDE Neon, with Qt 5.9.1 and Discover 5.11, this bug is not present, but in
KDE Neon LTS is a recurrent problem since some of the last updates.

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

[Discover] [Bug 386477] New: Plasma Discover crashes after installing updates

2017-11-02 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=386477

Bug ID: 386477
   Summary: Plasma Discover crashes after installing updates
   Product: Discover
   Version: 5.8.8
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.8.8)

Qt Version: 5.7.1
Frameworks Version: 5.39.0
Operating System: Linux 4.4.0-98-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

I am installing updates by Plasma Discover, and when it finishes, automatically
it crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Descubrir (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3ff236e900 (LWP 3153))]

Thread 8 (Thread 0x7f3fb147d700 (LWP 3175)):
#0  idleTimerSourceCheck (source=) at
kernel/qeventdispatcher_glib.cpp:224
#1  0x7f3fea3e8dc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3fea3e9330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3fea3e949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f3fef89275b in QEventDispatcherGlib::processEvents
(this=0x7f3fa8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f3fef83d0ba in QEventLoop::exec (this=this@entry=0x7f3fb147ccc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f3fef66cf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f3fef671b48 in QThreadPrivate::start (arg=0x195f940) at
thread/qthread_unix.cpp:368
#8  0x7f3fec5a76ba in start_thread (arg=0x7f3fb147d700) at
pthread_create.c:333
#9  0x7f3feec753dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f3fb3fff700 (LWP 3174)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f3fef6729fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1bbb410) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x1bb3948,
mutex=mutex@entry=0x1bb3940, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f3ff1c9f47d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x1bb3938) at scenegraph/qsgthreadedrenderloop.cpp:242
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x1bb38c0) at
scenegraph/qsgthreadedrenderloop.cpp:690
#5  0x7f3ff1c9fd55 in QSGRenderThread::run (this=0x1bb38c0) at
scenegraph/qsgthreadedrenderloop.cpp:719
#6  0x7f3fef671b48 in QThreadPrivate::start (arg=0x1bb38c0) at
thread/qthread_unix.cpp:368
#7  0x7f3fec5a76ba in start_thread (arg=0x7f3fb3fff700) at
pthread_create.c:333
#8  0x7f3feec753dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f3fbad72700 (LWP 3171)):
#0  0x7f3fea3e8e68 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3fea3e9330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3fea3e949c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f3fef89275b in QEventDispatcherGlib::processEvents
(this=0x7f3fb40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3fef83d0ba in QEventLoop::exec (this=this@entry=0x7f3fbad71cc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f3fef66cf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f3fef671b48 in QThreadPrivate::start (arg=0x2c920c0) at
thread/qthread_unix.cpp:368
#7  0x7f3fec5a76ba in start_thread (arg=0x7f3fbad72700) at
pthread_create.c:333
#8  0x7f3feec753dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f3fcf1bb700 (LWP 3158)):
#0  0x7f3fea42da94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f3fea3e94a6 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f3fef89275b in QEventDispatcherGlib::processEvents
(this=0x7f3fbc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#3  0x7f3fef83d0ba in QEventLoop::exec (this=this@entry=0x7f3fcf1bacc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#4  0x7f3fef66cf64 in QThread::exec (this=) at
thread/qthread.cpp:507
#5  0x7f3fef671b48 in QThreadPrivate::start (arg=0x7f3fc4003650) at
thread/qthread_unix.cpp:368
#6  0x7f3fec5a76ba in start_thread (arg=0x7f3fcf1bb700) at
pthread_create.c:333
#7  0x7f3feec753dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f3fcf9bc700 (LWP 3157)):
#0  0x7f3feec6524d in rea

[neon] [Bug 365228] partitionmanager crash when open, pmlibpartedbackendplugin error.

2017-10-17 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=365228

--- Comment #3 from VaryHeavy  ---
(In reply to VaryHeavy from comment #2)
> I am experiencing this error both in KDE Neon 5.11 and KDE Neon 5.8 LTS,
> when I try to open Partitionmanager, an error message appears saying that it
> can't load the "pmlibpartedbackendplugin". What package contains the
> pmlibpartedbackendplugin? It is impossible to open Partitionmanager right
> now.

I respond to myself: As Jonathan Ridell said, it depends of kpmcore package.
After install kpmcore, Partitionmanager can be opened correctly. For some
reason, on some of the last occasions I ran "apt autoremove", it uninstalled
the kpmcore package, and it is not the first time that it happens, it has
happened to me with other packages when running "apt autoremove".

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

[neon] [Bug 365228] partitionmanager crash when open, pmlibpartedbackendplugin error.

2017-10-17 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=365228

--- Comment #2 from VaryHeavy  ---
I am experiencing this error both in KDE Neon 5.11 and KDE Neon 5.8 LTS, when I
try to open Partitionmanager, an error message appears saying that it can't
load the "pmlibpartedbackendplugin". What package contains the
pmlibpartedbackendplugin? It is impossible to open Partitionmanager right now.

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

[neon] [Bug 365228] partitionmanager crash when open, pmlibpartedbackendplugin error.

2017-10-17 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=365228

VaryHeavy  changed:

   What|Removed |Added

 CC||anvar...@gmail.com

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

[kwin] [Bug 380493] New: KWin crashes when title of a window changes

2017-06-02 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=380493

Bug ID: 380493
   Summary: KWin crashes when title of a window changes
   Product: kwin
   Version: 5.8.7
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.7)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.4.0-79-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

I am writing a text note in Kate, and when I saved the note (and window title
changed), KWin crashed.
In addition, I had some other applications opened, like Firefox, Dolphin,
Telegram Desktop or Avidemux.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8675559900 (LWP 1809))]

Thread 8 (Thread 0x7f8654b8c700 (LWP 21752)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f8672d1c9fb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1d8e5e0) at
thread/qwaitcondition_unix.cpp:143
#2  QWaitCondition::wait (this=this@entry=0x228d988,
mutex=mutex@entry=0x228d980, time=time@entry=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7f866e3b547d in QSGRenderThreadEventQueue::takeEvent (wait=true,
this=0x228d978) at scenegraph/qsgthreadedrenderloop.cpp:242
#4  QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x228d900) at
scenegraph/qsgthreadedrenderloop.cpp:690
#5  0x7f866e3b5d55 in QSGRenderThread::run (this=0x228d900) at
scenegraph/qsgthreadedrenderloop.cpp:719
#6  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x228d900) at
thread/qthread_unix.cpp:368
#7  0x7f866ed8c6ba in start_thread (arg=0x7f8654b8c700) at
pthread_create.c:333
#8  0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f86569d0700 (LWP 21751)):
#0  0x7f867504fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8672f37aaa in poll (__timeout=, __nfds=1,
__fds=0x7f8648012898) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f8648012898) at
kernel/qcore_unix.cpp:83
#3  qt_safe_poll (fds=0x7f8648012898, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:102
#4  0x7f8672f39392 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f8672ee70ba in QEventLoop::exec (this=this@entry=0x7f86569cfca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8672d16f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f866dee9bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x226cdf0) at
thread/qthread_unix.cpp:368
#9  0x7f866ed8c6ba in start_thread (arg=0x7f86569d0700) at
pthread_create.c:333
#10 0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f86456ad700 (LWP 1992)):
#0  0x7f867504fb5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f8672f37aaa in poll (__timeout=, __nfds=1,
__fds=0x7f863c000a58) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f863c000a58) at
kernel/qcore_unix.cpp:83
#3  qt_safe_poll (fds=0x7f863c000a58, nfds=1, timeout_ts=timeout_ts@entry=0x0)
at kernel/qcore_unix.cpp:102
#4  0x7f8672f39392 in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500
#5  0x7f8672ee70ba in QEventLoop::exec (this=this@entry=0x7f86456acca0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f8672d16f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f866dee9bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f8672d1bb48 in QThreadPrivate::start (arg=0x17a23b0) at
thread/qthread_unix.cpp:368
#9  0x7f866ed8c6ba in start_thread (arg=0x7f86456ad700) at
pthread_create.c:333
#10 0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f863bfff700 (LWP 1920)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f86720b36f4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f86720b3739 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f866ed8c6ba in start_thread (arg=0x7f863bfff700) at
pthread_create.c:333
#4  0x7f867505b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f8655c21700 (LWP 1906)):

[print-manager] [Bug 377124] Print-manager does not save modifications in settings

2017-03-02 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=377124

--- Comment #1 from VaryHeavy  ---
I have realized that when I modify any option, and next I click on "Apply",
changes are not saved. But if I click on "Accept/OK", without clicking on
"Apply", changes are saved.

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

[print-manager] [Bug 377124] Print-manager does not save modifications in settings

2017-03-02 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=377124

VaryHeavy  changed:

   What|Removed |Added

Version|unspecified |0.3.0

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

[print-manager] [Bug 377124] New: Print-manager does not save modifications in settings

2017-03-02 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=377124

Bug ID: 377124
   Summary: Print-manager does not save modifications in settings
   Product: print-manager
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: anvar...@gmail.com
  Target Milestone: ---

This occurs to the KDE Print-manager version included in Ubuntu Xenial
packages. I have tried on KDE Neon 5.8 LTS user edition.

When I modify any settings in the Print-manager, like "Output Mode" or "Print
Quality", and apply the changes, this changes are not saved. When I reopen the
configuration settings, all are in default options.

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

[systemsettings] [Bug 377077] New: Systemsettings5 sometimes crashes when I make modifications in some settings

2017-03-01 Thread VaryHeavy
https://bugs.kde.org/show_bug.cgi?id=377077

Bug ID: 377077
   Summary: Systemsettings5 sometimes crashes when I make
modifications in some settings
   Product: systemsettings
   Version: 5.8.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: anvar...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.4.0-65-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

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

- Modify GTK appearance settings.
- Modify window decoration.
- Modify workspace theming.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Preferencias del sistema (systemsettings5), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1f9fe3a8c0 (LWP 2079))]

Thread 6 (Thread 0x7f1f5e879700 (LWP 2089)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f5e878d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x1be8a20) at
thread/qthread_unix.cpp:368
#7  0x7f1f9977a6ba in start_thread (arg=0x7f1f5e879700) at
pthread_create.c:333
#8  0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f1f6cfd2700 (LWP 2086)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f640008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f6cfd1d00,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x1cd3960) at
thread/qthread_unix.cpp:368
#7  0x7f1f9977a6ba in start_thread (arg=0x7f1f6cfd2700) at
pthread_create.c:333
#8  0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f1f6f7fe700 (LWP 2085)):
#0  0x7f1f976e8a94 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f1f976a3f2a in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a43f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f6f7fdce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f1f9b5c0bf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x18f44b0) at
thread/qthread_unix.cpp:368
#9  0x7f1f9977a6ba in start_thread (arg=0x7f1f6f7fe700) at
pthread_create.c:333
#10 0x7f1f9c57582d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f1f868ca700 (LWP 2081)):
#0  0x7f1f9c569b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1f976a438c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1f976a449c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1f9ce8975b in QEventDispatcherGlib::processEvents
(this=0x7f1f88c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f1f9ce340ba in QEventLoop::exec (this=this@entry=0x7f1f868c9cd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f1f9cc63f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#6  0x7f1f9ff8d735 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f1f9cc68b48 in QThreadPrivate::start (arg=0x7f1fa0001d60) at
thread/qthread_unix.cpp:368
#8  0x7f1f9977a6ba in start_thread (arg=0x7f1f868ca700) at
pthread_create.c:333
#9  0x7f1f9c57582d in clone () at
..

[gwenview] [Bug 362199] KIPI plugins do not work in Gwenview

2016-06-17 Thread VaryHeavy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362199

VaryHeavy  changed:

   What|Removed |Added

 CC||varyhe...@gmail.com

--- Comment #1 from VaryHeavy  ---
I confirm this problem. The only option that appears in all plugins submenus is
"KXML Hello World...", even though last kipi-plugins package from Ubuntu
universe repositories is installed.

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


[systemsettings] [Bug 362861] KFontInst crashes after installing fonts

2016-06-08 Thread VaryHeavy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362861

VaryHeavy  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Kubuntu Packages

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


[kamoso] [Bug 364123] New: Video stutters after a few seconds of recording

2016-06-08 Thread VaryHeavy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364123

Bug ID: 364123
   Summary: Video stutters after a few seconds of recording
   Product: kamoso
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: afies...@kde.org
  Reporter: varyhe...@gmail.com

When you turn Kamoso to video mode and begin recording, after a few seconds of
recording, the video starts to stutter, appreciating jumps in sound and image.

I experienced this same behaviour in OpenSUSE Leap 42.1 and Kubuntu 16.04. I
don't remember what Kamoso version ran in OpenSUSE, but in Kubuntu (which I use
currently), the Kamoso version is 3.0.0, from universe repositories, so I have
put 'unspecified' in the field 'Version', because the only option I had,
besides 'unspecified', was the 2.0.2.

Reproducible: Always

Steps to Reproduce:
1. Open Kamoso.
2. Turn to video mode.
3. Start recording and waits 15-25 seconds.

Actual Results:  
Video starts to stutter, appreciating jumps in sound and image.

Expected Results:  
Video recording should be stable in sound and image at all times.

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


[systemsettings] [Bug 362861] New: KFontInst crashes after installing fonts

2016-05-09 Thread VaryHeavy via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362861

Bug ID: 362861
   Summary: KFontInst crashes after installing fonts
   Product: systemsettings
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: kcm_fontinst
  Assignee: unassigned-b...@kde.org
  Reporter: varyhe...@gmail.com

Application: kfontinst (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-22-generic x86_64
Distribution: Ubuntu 16.04 LTS

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

I was installing some tipographic fonts (double click on the font-type file)
and then, suddenly, the installer crashed. I was doing it this way instead of
using the fonts manager systemsettings5 because it hangs when I try to install
any font from it.

Note that font installer stands in the little window that says "Installing",
and it never closes automatically as in KDE 4, forcing me to close the window
manually.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Instalador de tipos de letra de KDE (kfontinst), signal:
Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7f27cc48f064 in KNotification::flags (this=this@entry=0x1f636d0) at
../../src/knotification.cpp:233
#7  0x7f27cc4acee7 in NotifyByAudio::onAudioFinished (this=0x1e6b4a0) at
../../src/notifybyaudio.cpp:140
#8  0x7f27cc4b35b5 in NotifyByAudio::qt_static_metacall
(_o=_o@entry=0x1e6b4a0, _c=_c@entry=QMetaObject::InvokeMetaMethod,
_id=_id@entry=0, _a=_a@entry=0x7ffc364d4a40) at moc_notifybyaudio.cpp:83
#9  0x7f27ce249fca in QMetaObject::activate (sender=0x221c970,
signalOffset=, local_signal_index=,
argv=) at kernel/qobject.cpp:3713
#10 0x7f27c60b36ad in ?? () from
/usr/lib/x86_64-linux-gnu/libphonon4qt5.so.4
#11 0x7f27ce24aea1 in QObject::event (this=0x221c970, e=) at
kernel/qobject.cpp:1239
#12 0x7f27ced6105c in QApplicationPrivate::notify_helper
(this=this@entry=0x1c3af00, receiver=receiver@entry=0x221c970,
e=e@entry=0x229b940) at kernel/qapplication.cpp:3716
#13 0x7f27ced66516 in QApplication::notify (this=0x7ffc364d5330,
receiver=0x221c970, e=0x229b940) at kernel/qapplication.cpp:3499
#14 0x7f27ce21b62b in QCoreApplication::notifyInternal
(this=0x7ffc364d5330, receiver=0x221c970, event=event@entry=0x229b940) at
kernel/qcoreapplication.cpp:965
#15 0x7f27ce21da26 in QCoreApplication::sendEvent (event=0x229b940,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x1c34700) at
kernel/qcoreapplication.cpp:1593
#17 0x7f27ce21df08 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1451
#18 0x7f27ce271673 in postEventSourceDispatch (s=0x1c71fd0) at
kernel/qeventdispatcher_glib.cpp:271
#19 0x7f27c8848127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f27c8848380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7f27c884842c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7f27ce271a7f in QEventDispatcherGlib::processEvents (this=0x1c70090,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#23 0x7f27ce218dea in QEventLoop::exec (this=this@entry=0x7ffc364d5000,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#24 0x7f27cef5bc7d in QDialog::exec (this=0x1e6bc40) at
dialogs/qdialog.cpp:541
#25 0x00411645 in KFI::CJobRunner::exec(KFI::CJobRunner::ECommand,
QList const&, bool) ()
#26 0x004162de in KFI::CInstaller::install(QSet const&) ()
#27 0x0040c4b3 in main ()

Possible duplicates by query: bug 361474, bug 360449, bug 357826, bug 357668,
bug 354518.

Reported using DrKonqi

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