[kdeconnect] [Bug 368089] New: Ringing Phone stops

[Victor Tran via KDE Bugzilla]

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

Bug ID: 368089
   Summary: Ringing Phone stops
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Android 5.x
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: victor.tr...@live.com

Ok, there are a few prerequisites.
- The user must have a custom ringtone.
- There are possibly more that I don't know about.

When the ringtone is a user defined ringtone, after one iteration, KDE Connect
stops playing the ringtone.

I tested with a custom ringtone, and it didn't loop. When I reverted back to
the default 'Over the Horizon' (which sounds pretty good!) the sound looped.

I had this problem when I was coding this thing called theLink for Android, I
fixed this issue by creating an object of type MediaPlayer, setting the Data
Source to the URI of the default ringtone, setting the Looping property to true
and starting it. When the activity was destroyed, I would stop the media
player.

   MediaPlayer mp = new MediaPlayer();
mp.setAudioStreamType(AudioManager.STREAM_MUSIC);
mp.setDataSource(getApplicationContext(),
RingtoneManager.getDefaultUri(RingtoneManager.TYPE_RINGTONE));
mp.setLooping(true);
mp.prepare();
mp.start();

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

[kdeconnect] [Bug 358549] HTML is not escaped in notifications

[Victor Tran via KDE Bugzilla]

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

Victor Tran  changed:

   What|Removed |Added

 CC||victor.tr...@live.com

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

[systemsettings] [Bug 366113] New: systemsettings crashes testing touchpad settings

[Victor Tran via KDE Bugzilla]

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

Bug ID: 366113
   Summary: systemsettings crashes testing touchpad settings
   Product: systemsettings
   Version: 5.7.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: victor.tr...@live.com

Application: systemsettings5 (5.7.2)

Qt Version: 5.7.0
Frameworks Version: 5.24.0
Operating System: Linux 4.6.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
In System Settings, under Input Devices > Touchpad, in the testing area, there
is a folder that you can drag to test touchpad dragging. If you drag it onto
itself, then try to start dragging it again, systemsettings crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6da7099800 (LWP 31892))]

Thread 8 (Thread 0x7f6d777fe700 (LWP 31978)):
#0  0x7f6d9ee9e458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f6da34b3b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f6da34af274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f6da34b2d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 7 (Thread 0x7f6d77fff700 (LWP 31977)):
#0  0x7f6d9ee9e458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f6da34b3b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f6da34af274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f6da34b2d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 6 (Thread 0x7f6d7cc25700 (LWP 31976)):
#0  0x7f6d9ee9e458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f6da34b3b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f6da34af274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f6da34b2d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 5 (Thread 0x7f6d7d426700 (LWP 31975)):
#0  0x7f6d9ee9e458 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/usr/lib/libpthread.so.0
#1  0x7f6da34b3b66 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib/libQt5Core.so.5
#2  0x7f6da34af274 in ?? () from /usr/lib/libQt5Core.so.5
#3  0x7f6da34b2d78 in ?? () from /usr/lib/libQt5Core.so.5
#4  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#5  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f6d7ee4c700 (LWP 31974)):
#0  0x7f6da2db872d in read () from /usr/lib/libc.so.6
#1  0x7f6d9d1dcc80 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f6d9d199ab4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f6d9d199f74 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f6d9d19a362 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#5  0x7f6d7f936726 in ?? () from /usr/lib/libgio-2.0.so.0
#6  0x7f6d9d1c02b5 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f6d7f64d700 (LWP 31973)):
#0  0x7f6da2db872d in read () from /usr/lib/libc.so.6
#1  0x7f6d9d1dcc80 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f6d9d199ab4 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f6d9d199f74 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f6d9d19a0ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f6d9d19a131 in ?? () from /usr/lib/libglib-2.0.so.0
#6  0x7f6d9d1c02b5 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x7f6d9ee98484 in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f6da2dc56dd in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f6d8b059700 (LWP 31899)):
#0  0x7f6da2dbc6cd in poll () from /usr/lib/libc.so.6
#1  0x7f6d9d199fd6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f6d9d19a0ec in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f6da36e159b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#4  0x7f6da368b0da in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#5  0x7f6da34ae0f3 in 

[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".

[Victor Tran via KDE Bugzilla]

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

Victor Tran  changed:

   What|Removed |Added

 CC||victor.tr...@live.com

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

[kscreenlocker] [Bug 353855] Media controls should be shown on lock screen.

[Victor Tran via KDE Bugzilla]

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

--- Comment #2 from Victor Tran  ---
Oh, by the way, when I say "when KDE detects that music is playing", I mean
"when MPRIS says that music is playing" :)

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

[Breeze] [Bug 358818] New: Breeze Dark battery icon outline is a bad colour

[Victor Tran via KDE Bugzilla]

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

Bug ID: 358818
   Summary: Breeze Dark battery icon outline is a bad colour
   Product: Breeze
   Version: 5.5.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Icons
  Assignee: uri_herr...@nitrux.in
  Reporter: victor.tr...@live.com
CC: kain...@gmail.com

The Breeze Dark battery icons used in the battery widget in Plasma have a dark
outline, which makes it hard to see how much battery there really is.

Reproducible: Always

Steps to Reproduce:
Make sure you are on a portable!

1. Set the desktop theme to "Breeze Dark"
2. Set the icon theme to "Breeze Dark"
3. Look at the battery symbol in the system tray/battery monitor widget

Actual Results:  
The outline of the battery is a dark colour

Expected Results:  
The outline of the battery should be a light colour rather than a dark colour.

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

[Breeze] [Bug 358818] Breeze Dark battery icon outline is a bad colour

[Victor Tran via KDE Bugzilla]

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

--- Comment #1 from Victor Tran  ---
Created attachment 96938
  --> https://bugs.kde.org/attachment.cgi?id=96938=edit
System Tray Screenshot

On the left is Klipper and on the right is Amarok. In the middle is the Battery
monitor. You can't see the outline of the battery, which makes it a bit hard to
see how much battery there really is.

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

[Breeze] [Bug 358818] Breeze Dark battery icon outline is a bad colour

[Victor Tran via KDE Bugzilla]

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

--- Comment #2 from Victor Tran  ---
Created attachment 96939
  --> https://bugs.kde.org/attachment.cgi?id=96939=edit
Breeze Light System Tray Screenshot

This is the same system tray in Breeze Light. You can see the outline around
the battery, which makes it a lot easier to see how much power there is left.

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