[bugs.kde.org] [Bug 372502] New: Delete my account

2016-11-15 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=372502

Bug ID: 372502
   Summary: Delete my account
   Product: bugs.kde.org
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: sysad...@kde.org
  Reporter: molecularbiophys...@yahoo.com
CC: she...@kde.org
  Target Milestone: ---

Please delete my account 

many thanks!

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

[Akonadi] [Bug 424579] New: Incorrect parsing/interpretation of a path to Local Folder (creates file: in $HOME)

2020-07-23 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=424579

Bug ID: 424579
   Summary: Incorrect parsing/interpretation of a path to Local
Folder (creates file: in $HOME)
   Product: Akonadi
   Version: 5.13.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Maildir Resource
  Assignee: kdepim-b...@kde.org
  Reporter: vo...@rambler.ru
  Target Milestone: ---

SUMMARY
After changing a path to the Local Folder a prefix 'file:' gets added to a
filepath, so a new location of Local Folder becomes
/home/serge/file:/home/serge/.local/share/akonadi_maildir_resource_0.
Restarting akonadi does not help. Moreover, it is noted that 'file:' gets
created under the directory akonadi starts from. Going to the data in the DB
shows exactly that value. One might expect that it should contain 'file://'
with two slashes instead of one. I do not know whether this happened before but
such a behaviour was noticed for 19.12.3.


STEPS TO REPRODUCE
1. Start kmail
2. Copy a directory where Local Folder is located to a new location
3. Change settings for Local Folder to that new location


OBSERVED RESULT
Wrong location for Local Folder


EXPECTED RESULT
The location should correspond to the one specified in settings

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.13.3
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.12.9

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 424579] Incorrect parsing/interpretation of a path to Local Folder (creates file: in $HOME)

2020-07-24 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=424579

--- Comment #1 from Sergei  ---
It seems the things starts from ConfigWidget::save() in
https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/maildir/configwidget.cpp
but I do not have time to dig in more details.

A workaround for that 'file:' thing is by just deleting Local Folder through
akonadiconsole and kmail will create a new one.

Has to be fixed anyway...

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

[kdevelop] [Bug 283438] Crash, after close KDevelop (using NXClient)

2020-12-17 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=283438

Sergei  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kdevelop] [Bug 283438] Crash, after close KDevelop (using NXClient)

2018-09-23 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=283438

Sergei  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|BACKTRACE   |---

--- Comment #4 from Sergei  ---
(In reply to Aleix Pol from comment #1)
> It would be interesting if you could provide a backtrace with debug
> information. There's not much we can do with this backtrace.

Hi Alex, 

 see all threads are waiting except thread 9. Please, take a look if
QEventDispatcherGlib::~QEventDispatcherGlib could cause the abort. It may be
fixed long time ago this.

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

[kdelibs] [Bug 382395] New: unable to open cmake project under bash@ubuntu@windows

2017-07-16 Thread Sergei
https://bugs.kde.org/show_bug.cgi?id=382395

Bug ID: 382395
   Summary: unable to open cmake project under bash@ubuntu@windows
   Product: kdelibs
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: knotify
  Assignee: ogoff...@kde.org
  Reporter: sergeikrivo...@gmail.com
  Target Milestone: ---

Application: knotify4 (4.14.16)
KDE Platform Version: 4.14.16
Qt Version: 4.8.7
Operating System: Linux 4.4.0-43-Microsoft x86_64
Distribution: Ubuntu 16.04.2 LTS

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

- Custom settings of the application:
launched under bash@ubuntu@windows
 I used xming X server for windows

The crash can be reproduced every time.

-- Backtrace:
Application: KNotify (knotify4), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8a5f0c0900 (LWP 112))]

Thread 3 (Thread 0x7f8a4d8f0700 (LWP 123)):
#0  __pthread_mutex_unlock_full (mutex=0x12bb870, decr=) at
pthread_mutex_unlock.c:250
#1  0x7f8a61e8f32e in pa_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#2  0x7f8a666e2853 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f8a666d3e11 in pa_mainloop_poll () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f8a666d44ae in pa_mainloop_iterate () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f8a666d4560 in pa_mainloop_run () from
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f8a666e27a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f8a61e90078 in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#8  0x7f8a644876ba in start_thread (arg=0x7f8a4d8f0700) at
pthread_create.c:333
#9  0x7f8a66a073dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f8a571c0700 (LWP 115)):
#0  0x7f8a6721ab35 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#1  0x7f8a63f89dc1 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f8a63f8a330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f8a63f8a49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f8a6721b2ce in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x7f8a671e918f in
QEventLoop::processEvents(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x7f8a671e94f5 in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x7f8a670d8549 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x7f8a671c9223 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x7f8a670dae3c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x7f8a644876ba in start_thread (arg=0x7f8a571c0700) at
pthread_create.c:333
#11 0x7f8a66a073dd in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f8a5f0c0900 (LWP 112)):
[KCrash Handler]
#6  0x7f8a66935428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f8a6693702a in __GI_abort () at abort.c:89
#8  0x7f8a61e8f3cd in pa_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-8.0.so
#9  0x7f8a4d90a0b7 in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpulse.so
#10 0x7f8a4f6b619b in gst_audio_ring_buffer_open_device () from
/usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
#11 0x7f8a4f6d5db9 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0
#12 0x7f8a4d90d802 in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpulse.so
#13 0x7f8a54df91ce in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#14 0x7f8a54df9947 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#15 0x7f8a4dd82ee4 in ?? () from
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstautodetect.so
#16 0x7f8a54df91ce in gst_element_change_state () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#17 0x7f8a54df9947 in ?? () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
#18 0x7f8a550ed016 in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_gstreamer.so
#19 0x7f8a550ee62b in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_gstreamer.so
#20 0x7f8a550e5888 in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_gstreamer.so
#21 0x7f8a550ea35b in ?? () from
/usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_gstreamer.so
#22 0x7f8a695afa42 in ?? () from /usr/lib/x86_64-linux-gnu/libphonon.so.4
#23 0x7f8a695a30bf in ?? () from /usr/lib/x86_64-linux-gnu/libphonon.so.4
#24 0x7f8a695a060f in ?

[kate] [Bug 372129] New: Kate opens at the center of 2 monitors

2016-11-05 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=372129

Bug ID: 372129
   Summary: Kate opens at the center of 2 monitors
   Product: kate
   Version: 16.08
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: sergeidani...@gmail.com
  Target Milestone: ---

Created attachment 102062
  --> https://bugs.kde.org/attachment.cgi?id=102062&action=edit
Kate when I open it

1. Setup 2 monitors with a main screen as a left monitor.
2. Open kate
-> instead of opening on the main screen kate opens in the center of 2
monitors.
See attached screenshot and video: https://goo.gl/photos/pgCg7e7LB1BuKQNR6

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

[kate] [Bug 372129] Kate opens at the center of 2 monitors

2016-11-05 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=372129

--- Comment #1 from Sergei Danilov  ---
KDE Frameworks 5.27.0
Qt 5.6.2 (built against 5.6.1)
plasma version: 5.8.2

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

[plasmashell] [Bug 462725] [NVIDIA, X11] When HDMI monitor is plugged in at boot, icons are missing throughout Plasma (but not apps, and not when the HDMI monitor is plugged in later)

2023-02-01 Thread Aspidov Sergei
https://bugs.kde.org/show_bug.cgi?id=462725

Aspidov Sergei  changed:

   What|Removed |Added

 CC||aspido...@gmail.com

--- Comment #28 from Aspidov Sergei  ---
I encountered this error as early as last year in November 2022~
This error was on Manjaro Linux Stable  \  Arch Linux 
This error appears only on laptops with nvidia + intel graphics in Plasma x11
sesion any actual kernel 

I Use:
video-hybrid-intel-nvidia-prime 
nvidia-utils 525.60.11-2
kscreen and libkscreen to 5.25.1<=
KDE Plasma 5.26.4
KDE FW 5.101.0
QT 5.15.7
Kernel 5.15.85-1 Manjaro
X11

Same trouble
https://forum.manjaro.org/t/panel-icons-disappears-after-hovering/132997/4
https://forum.manjaro.org/t/all-desktop-and-menu-icons-missing/125832
https://forum.manjaro.org/t/icons-missing-wrong-fonts-unresponsive-plasma-after-update/127958
https://forum.manjaro.org/t/system-hangs-out-freezes-on-external-monitor-after-last-update/129926/20
https://bbs.archlinux.org/viewtopic.php?id=280535

Temporary solution: 
1. Disconnect the external monitor which is connected via type C or set the
same refresh rate main and external monitor
2. Downgrade kscreen and libkscreen to 5.25.5<= and ignore updatre
3. When your log on in plasma, try to upload new desktop wallper, after refresh
all to be normal ( after logout, need do it again )
4. Install optimums manager and use only intel or nvidia driver.

5. Not all situation - GRUB_CMDLINE_LINUX_DEFAULT dd this parameter ibt=off

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

[plasmashell] [Bug 462725] [NVIDIA, X11] When HDMI monitor is plugged in at boot, icons are missing throughout Plasma (but not apps, and not when the HDMI monitor is plugged in later)

2023-02-02 Thread Aspidov Sergei
https://bugs.kde.org/show_bug.cgi?id=462725

--- Comment #29 from Aspidov Sergei  ---
This problem only occurs on 
1. Laptop
2. On which an external display is connected
3. In KDE only x11 
4. With intel + nvidia hybrid GPU\driver installed 
5. kscreen and libkscreen =>5.25.90
6. Primary and secondary monitor refresh rates do not match. 

Fix way:
1. Go to system settings \display and monitor \ set same Refresh rate to all
monitor
2. Downgrade kscreen and libkscreen to 5.25.5<= and ignore update
3. install optimus-manager and switch gpu to nvidia \ intel only
4. When your log on in plasma, try to upload new desktop wallper, after refresh
all to be normal ( after logout, need do it again ) YES  WHY

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

[KScreen] [Bug 462725] [NVIDIA, X11] When HDMI monitor is plugged in at boot, icons are missing throughout Plasma (but not apps, and not when the HDMI monitor is plugged in later)

2023-02-02 Thread Aspidov Sergei
https://bugs.kde.org/show_bug.cgi?id=462725

Aspidov Sergei  changed:

   What|Removed |Added

  Component|general |common
Version|5.26.4  |5.25.90
   Platform|Fedora RPMs |Compiled Sources
Product|plasmashell |KScreen
   Target Milestone|1.0 |---

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

[KScreen] [Bug 462725] [NVIDIA, X11] When external monitor is plugged in at boot and have different frame rate icons and fronts are missing Plasma

2023-02-02 Thread Aspidov Sergei
https://bugs.kde.org/show_bug.cgi?id=462725

Aspidov Sergei  changed:

   What|Removed |Added

Summary|[NVIDIA, X11] When HDMI |[NVIDIA, X11] When external
   |monitor is plugged in at|monitor is plugged in at
   |boot, icons are missing |boot and have different
   |throughout Plasma (but not  |frame rate  icons and
   |apps, and not when the HDMI |fronts are missing Plasma
   |monitor is plugged in   |
   |later)  |

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

[kcalc] [Bug 488728] Input error when entering hexadecimal number

2024-06-19 Thread Deriabin Sergei
https://bugs.kde.org/show_bug.cgi?id=488728

--- Comment #2 from Deriabin Sergei  ---
(In reply to popov895 from comment #1)
> *** Bug 485319 has been marked as a duplicate of this bug. ***
Some more test cases for version  24.05.1:
ab -- Input error
AB -- AB
00AB -- 0
00ab -- Input error
0x00AB -- AB
0x00ab -- Input error

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

[kcalc] [Bug 485319] New: Incorrect decoding of zero-prefixed hexadecimals

2024-04-10 Thread Deriabin Sergei
https://bugs.kde.org/show_bug.cgi?id=485319

Bug ID: 485319
   Summary: Incorrect decoding of zero-prefixed hexadecimals
Classification: Applications
   Product: kcalc
   Version: 24.02.1
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ete...@alum.rit.edu
  Reporter: sadsader...@gmail.com
  Target Milestone: ---

STEPS TO REPRODUCE
1. Settings->Numeral System mode
2. Copy zero-prefixed hexadecimal number  00ab into clipboard
3. paste to KCalc

OBSERVED RESULT
nan

EXPECTED RESULT
ab

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

[kcalc] [Bug 485319] Incorrect decoding of zero-prefixed hexadecimals

2024-04-10 Thread Deriabin Sergei
https://bugs.kde.org/show_bug.cgi?id=485319

Deriabin Sergei  changed:

   What|Removed |Added

 CC||sadsader...@gmail.com

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

[systemsettings] [Bug 455431] Spare layout not working on Wayland

2023-09-14 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=455431

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@pm.me

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

[Akonadi] [Bug 424231] Logging in to a enterprise managed EWS server "needs" MS intune

2021-01-21 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=424231

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

--- Comment #9 from Sergei Gureev  ---
I ran into this issue, but instead of intune it asks to install Community
Portal, which is the same thing under a new name, I presume.

"Troubleshooting details" from the page that is displayed after the auth form:

App name: Akonadi EWS
App id: 452b289a-7894-41d7-9cd4-d5275739fa27
Device identifier: Not available
Device platform: Android
Device state: Unregistered

> steal the device certificate & key from a Windows system

Krzysztof, can you please provide more detailed instructions on how to do that?
Where they are stored and what "Key password" should be used?

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

[Akonadi] [Bug 424231] Logging in to a enterprise managed EWS server "needs" MS intune

2021-01-21 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=424231

--- Comment #10 from Sergei Gureev  ---
This works fine in Thunderbird plugin which uses "Thunderbird ActiveSync" user
agent:
https://github.com/jobisoft/EAS-4-TbSync/blob/1f14adba113c3a674b34c5e5f8191f4200d63182/content/provider.js#L42

Can we also use it in ewsoauth?
https://invent.kde.org/pim/kdepim-runtime/-/blob/5c7278c9b201a46cde29cf407e5630ea1b854376/resources/ews/ewsclient/auth/ewsoauth.cpp#L36

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

[okular] [Bug 423490] New: File open error when path or filename contains a number sign

2020-06-25 Thread Sergei K
https://bugs.kde.org/show_bug.cgi?id=423490

Bug ID: 423490
   Summary: File open error when path or filename contains a
number sign
   Product: okular
   Version: 1.10.1
  Platform: MS Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: skz...@outlook.com
  Target Milestone: ---

SUMMARY
When I try to open file which contains a number sign (#) in path or filename
there is an error

STEPS TO REPRODUCE
1. Add # to file or folder name
2. Try to open file for view in Okular

OBSERVED RESULT
Popup window with Error - Could not open file:///D:/folder/pre.

EXPECTED RESULT
Document opened to view

SOFTWARE/OS VERSIONS
Windows: 8.1 x64
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 5.14.1

ADDITIONAL INFORMATION

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

[okular] [Bug 418758] Okular will not open file if "#" is in the filename or file path when "Open with" method is used.

2020-06-27 Thread Sergei K
https://bugs.kde.org/show_bug.cgi?id=418758

Sergei K  changed:

   What|Removed |Added

 CC||skz...@outlook.com

--- Comment #6 from Sergei K  ---
I also have similar problem that reported in bug 423490. Appears only if you
click on a document in Explorer or use "Open with". From cli doesn't work the
same way. Opening from the Okular menu works correctly.

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

[ark] [Bug 434457] New: [BUG] Incorrect decryption of file names in encrypted archives

2021-03-15 Thread Sergei Rezchikov
https://bugs.kde.org/show_bug.cgi?id=434457

Bug ID: 434457
   Summary: [BUG] Incorrect decryption of file names in encrypted
archives
   Product: ark
   Version: 20.12.2
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Keywords: accessibility, usability
  Severity: major
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: rezchi...@protonmail.com
CC: aa...@kde.org, rthoms...@gmail.com
  Target Milestone: ---

Created attachment 136701
  --> https://bugs.kde.org/attachment.cgi?id=136701&action=edit
Screenshot

Hello!

I found a very unpleasant bug in the program. When I trying to open an
encrypted archive (password-encrypted), Ark incorrectly decrypts file names for
viewing.
When decompressing this error also stays, even if I enter the password.

Take a look at the screenshot. I will say that the real encoding of these file
names is UTF-8, it should be Cyrillic.

OS: Manjaro KDE.
Ark v20.12.2

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

[yakuake] [Bug 415762] Exiting the session in a Yakuake tab sometimes crash Yakuake

2020-04-24 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=415762

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

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

[ring-kde] [Bug 396185] New: Compilation failed with gcc 8.1

2018-07-05 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

Bug ID: 396185
   Summary: Compilation failed with gcc 8.1
   Product: ring-kde
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elv1...@gmail.com
  Reporter: bem...@gmail.com
  Target Milestone: ---

I can't compile ring-kde with gcc-8.1.1. The errors are:

src/qmlwidgets/treeview2.cpp: In member function ‘bool
VisualTreeItem::error()’:
src/qmlwidgets/treeview2.cpp:1414:1: error: control reaches end of non-void
function [-Werror=return-type]

src/qmlwidgets/treeview2.cpp: In member function ‘bool
TreeTraversalItems::error()’:
src/qmlwidgets/treeview2.cpp:1445:1: error: control reaches end of non-void
function [-Werror=return-type]

src/qmlwidgets/treeview2.cpp: In member function ‘bool
TreeView2Private::error()’:
src/qmlwidgets/treeview2.cpp:1630:1: error: control reaches end of non-void
function [-Werror=return-type]

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-09 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #2 from Sergei Gureev  ---
Thank you!
But it fails again:

[  4%] Building CXX object src/klib/CMakeFiles/libkring.dir/kcfg_settings.cpp.o
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:4:
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.h:12:18: error:
Declaring type ‘class ConfigurationSkeleton’ final would enable
devirtualization of 1 call [-Werror=suggest-final-types]
 class LIB_EXPORT ConfigurationSkeleton : public KConfigSkeleton
  ^
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:246:1:
error: Declaring virtual destructor of ‘class ConfigurationSkeleton’ final
would enable devirtualization of 1 call [-Werror=suggest-final-methods]
 ConfigurationSkeleton::~ConfigurationSkeleton()
 ^
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp: In
destructor ‘ConfigurationSkeleton::~ConfigurationSkeleton()’:
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:248:38:
error: potential null pointer dereference [-Werror=null-dereference]
   s_globalConfigurationSkeleton()->q = nullptr;
   ~~~^
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp: In static
member function ‘static ConfigurationSkeleton* ConfigurationSkeleton::self()’:
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:19:41:
error: potential null pointer dereference [-Werror=null-dereference]
   if (!s_globalConfigurationSkeleton()->q) {
~^
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:21:38:
error: potential null pointer dereference [-Werror=null-dereference]
 s_globalConfigurationSkeleton()->q->read();
 ~^
/tmp/yaytmp-1000/ring-kde-git/src/build/src/klib/kcfg_settings.cpp:24:43:
error: potential null pointer dereference [-Werror=null-dereference]
   return s_globalConfigurationSkeleton()->q;

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #4 from Sergei Gureev  ---
The error is still there =(

[ 15%] Building CXX object
src/qmlwidgets/CMakeFiles/libqmlwidgets.dir/treeview2.cpp.o
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/qmlwidgets/treeview2.cpp: In
member function ‘bool VisualTreeItem::error()’:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/qmlwidgets/treeview2.cpp:1423:1:
error: no return statement in function returning non-void [-Werror=return-type]
 }
 ^
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/qmlwidgets/treeview2.cpp: In
member function ‘bool TreeView2Private::error()’:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/qmlwidgets/treeview2.cpp:1645:1:
error: control reaches end of non-void function [-Werror=return-type]
 }

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #6 from Sergei Gureev  ---
We're moving further!

[ 68%] Building CXX object src/CMakeFiles/ring-kde.dir/ringapplication.cpp.o
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp: In member
function ‘void RingApplication::initCollections()’:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp:317:43:
error: too few arguments to function ‘void
HistoryImporter::importHistory(LocalHistoryCollection*,
std::function&)>)’
   HistoryImporter::importHistory(histo);
   ^

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #8 from Sergei Gureev  ---
Thank you. I've added -k option and the process continued to 100%.
Previous "68%" error seems to be the last one. No more errors here.

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #9 from Sergei Gureev  ---
Here'is the log:

[ 68%] Building CXX object src/CMakeFiles/ring-kde.dir/ringapplication.cpp.o
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp: In member
function ‘void RingApplication::initCollections()’:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp:317:43:
error: too few arguments to function ‘void
HistoryImporter::importHistory(LocalHistoryCollection*,
std::function&)>)’
   HistoryImporter::importHistory(histo);
   ^
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp:71:
/usr/include/libringqt/libcard/historyimporter.h:40:17: note: declared here
 void LIB_EXPORT importHistory(LocalHistoryCollection* col,
std::function&)> callback);
 ^
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp: In static
member function ‘static QQmlApplicationEngine* RingApplication::engine()’:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp:504:37:
warning: ‘void KDeclarative::KDeclarative::setupBindings()’ is deprecated
[-Wdeprecated-declarations]
   m_pDeclarative->setupBindings();
 ^
In file included from
/usr/include/KF5/KDeclarative/KDeclarative/KDeclarative:1,
 from
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/ringapplication.cpp:39:
/usr/include/KF5/KDeclarative/kdeclarative/kdeclarative.h:57:34: note: declared
here
 KDECLARATIVE_DEPRECATED void setupBindings();
  ^
make[2]: *** [src/CMakeFiles/ring-kde.dir/build.make:240:
src/CMakeFiles/ring-kde.dir/ringapplication.cpp.o] Error 1
[ 69%] Building CXX object src/CMakeFiles/ring-kde.dir/errormessage.cpp.o
[ 69%] Building CXX object src/CMakeFiles/ring-kde.dir/actioncollection.cpp.o
[ 70%] Building CXX object src/CMakeFiles/ring-kde.dir/implementation.cpp.o
[ 70%] Building CXX object
src/CMakeFiles/ring-kde.dir/model/extendedprotocolmodel.cpp.o
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/model/extendedprotocolmodel.cpp:18:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/model/extendedprotocolmodel.h:26:7:
warning: Declaring type ‘class ExtendedProtocolModel’ final would enable
devirtualization of 3 calls [-Wsuggest-final-types]
 class ExtendedProtocolModel : public QIdentityProxyModel
   ^
[ 71%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/autocompletiondelegate.cpp.o
[ 71%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/autocompletiondelegate2.cpp.o
[ 72%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/toolbardelegate.cpp.o
[ 72%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/accountinfodelegate.cpp.o
[ 73%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/kdepixmapmanipulation.cpp.o
[ 73%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/categorizeddelegate.cpp.o
[ 74%] Building CXX object
src/CMakeFiles/ring-kde.dir/delegates/righticondelegate.cpp.o
[ 74%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/simplerotateproxy.cpp.o
[ 75%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/deduplicateproxy.cpp.o
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/proxies/deduplicateproxy.cpp:18:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/proxies/deduplicateproxy.h:57:7:
warning: Declaring type ‘class DeduplicateProxy’ final would enable
devirtualization of 5 calls [-Wsuggest-final-types]
 class DeduplicateProxy : public QSortFilterProxyModel
   ^~~~
[ 75%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/filtertoplevelproxy.cpp.o
[ 76%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/roletransformationproxy.cpp.o
[ 76%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/flagsfilterproxy.cpp.o
[ 77%] Building CXX object
src/CMakeFiles/ring-kde.dir/proxies/pollingproxy.cpp.o
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/proxies/pollingproxy.cpp:18:
/tmp/yaytmp-1000/ring-kde-git/src/ring-kde/src/proxies/pollingproxy.h:35:7:
warning: Declaring type ‘class PollingProxy’ final would enable
devirtualization of 4 calls [-Wsuggest-final-types]
 class PollingProxy : public QIdentityProxyModel
   ^~~~
[ 77%] Building CXX object
src/CMakeFiles/ring-kde.dir/conf/accountserializationadapter.cpp.o
[ 78%] Building CXX object
src/CMakeFiles/ring-kde.dir/conf/configurationdialog.cpp.o
[ 78%] Building CXX object src/CMakeFiles/ring-kde.dir/conf/dlggeneral.cpp.o
[ 79%] Building CXX object src/CMakeFiles/ring-kde.dir/conf/dlgdisplay.cpp.o
[ 79%] Building CXX object src/CMakeFiles/ring-kde.dir/conf/dlgaudio.cpp.o
[ 80%] Building CXX object
src/CMakeFiles/ring-kde.dir/conf/dlgaddressbook.cpp.o
In file included from
/tmp/yaytmp-1000/ring-kde-git/src/build/src/ui_dlgaddressbookbase.h:24,

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

Sergei Gureev  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #11 from Sergei Gureev  ---
Thank you, everything is fine now!

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

[ring-kde] [Bug 396185] Compilation failed with gcc 8.1

2018-07-10 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=396185

--- Comment #13 from Sergei Gureev  ---
I don't see any other issues, just some warnings. Guess it's ready for release!

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

[plasmashell] [Bug 364766] Graphics distorted after suspend/resume with nvidia

2018-03-10 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=364766

Sergei Danilov  changed:

   What|Removed |Added

 CC||sergeidani...@gmail.com

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

[konsole] [Bug 391781] Add support for SIXEL in Konsole

2018-12-29 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=391781

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

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

[konsole] [Bug 401465] Tab title color is not reset to default when activating a tab with changed contents

2018-12-13 Thread Sergei Stolyarov
https://bugs.kde.org/show_bug.cgi?id=401465

Sergei Stolyarov  changed:

   What|Removed |Added

 CC||ser...@regolit.com

--- Comment #1 from Sergei Stolyarov  ---
The same behaviour when I use command line option --tabs-from-file: all tabs
except the last one keep highlighted state forever.

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

[plasma-nm] [Bug 484045] Please add support for Secret Service

2024-11-08 Thread Sergei Gureev
https://bugs.kde.org/show_bug.cgi?id=484045

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@pm.me

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

[KScreen] [Bug 501670] New: KDE randomly connects external display either using RGB or YCBCR420 colorspace

2025-03-17 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=501670

Bug ID: 501670
   Summary: KDE randomly connects external display either using
RGB or YCBCR420 colorspace
Classification: Plasma
   Product: KScreen
   Version: 6.3.0
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: common
  Assignee: kscreen-bugs-n...@kde.org
  Reporter: sergeidani...@gmail.com
  Target Milestone: ---

Created attachment 179523
  --> https://bugs.kde.org/attachment.cgi?id=179523&action=edit
YCBCR420 picture

I'm using LG C2 TV as monitor with KDE Plasma 6.3
My Lenovo X1 carbon Gen9 laptop allows using it with 4K@120HZ over type C with
cable matters typec->hdmi adapter. 

Half of time KDE connects to the monitor using RGB 8 bit , which is looking
totally fine. 
But another half connects with YCBCR420 8bit , which provides bad rainbow
effect and makes text unreadable.
The fact it there is no consistency makes me puzzled that that color space
selection is not really controlled.
I checked on Windows 11, it consistenly using RGB 8bit, so problem is specific
to Linux.

Problem is reproduced only with 4K@120HZ, 4K@60HZ Consistently using RGB.


Hardware:
Lenovo X1 carbon Gen9
cable matters typec->hdmi 4k 120Hz adapter
LG C2 42" as monitor
Software:
Debian 12 Testing
Kde Plasma 6.3 Wayland (But also was present with 5.27)
Qt 6.7.2
Kernel 6.12

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

[KScreen] [Bug 501670] KDE randomly connects external display either using RGB or YCBCR420 colorspace

2025-03-17 Thread Sergei Danilov
https://bugs.kde.org/show_bug.cgi?id=501670

--- Comment #1 from Sergei Danilov  ---
Created attachment 179524
  --> https://bugs.kde.org/attachment.cgi?id=179524&action=edit
RGB 8 bit picture

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

[frameworks-kservice] [Bug 442721] kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found

2023-03-21 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=442721

Sergei S. Rublёv  changed:

   What|Removed |Added

 CC||kde-b...@ssr.host.ru

--- Comment #19 from Sergei S. Rublёv  ---
I see this in terminal just after "xdg-open ~" command. KDE 5.27.3

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

[systemsettings] [Bug 445704] Crash installing themes

2021-11-21 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=445704

Sergei S. Rublёv  changed:

   What|Removed |Added

 CC||kde-b...@ssr.host.ru

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

[systemsettings] [Bug 445704] Crash installing themes

2021-11-21 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=445704

--- Comment #3 from Sergei S. Rublёv  ---
Created attachment 143795
  --> https://bugs.kde.org/attachment.cgi?id=143795&action=edit
New crash information added by DrKonqi

systemsettings5 (5.23.3) using Qt 5.15.2

- What I was doing when the application crashed:
Trying to remove a theme called "Sweet Mars". It was installed and become
unremovable. I tried to re-install it to try to remove. Crashes after
installation attempt every time.

-- Backtrace (Reduced):
#6  0x7f28266f95ed in QDir::fromNativeSeparators(QString const&) () at
io/qdir.cpp:930
#7  0x7f282670a979 in QFileInfoPrivate::QFileInfoPrivate (file=...,
this=0x5634dffab8e0) at /usr/include/c++/11/bits/atomic_base.h:338
#8  QFileInfo::QFileInfo (this=this@entry=0x7ffe325deea0, file=...) at
io/qfileinfo.cpp:347
#9  0x7f2811040404 in operator() (__closure=) at
/usr/src/debug/plasma-workspace-5.23.3-1.fc35.x86_64/kcms/lookandfeel/kcm.cpp:117
#10 KCMLookandFeel::knsEntryChanged (wrapper=,
this=0x5634dc73f660) at
/usr/src/debug/plasma-workspace-5.23.3-1.fc35.x86_64/kcms/lookandfeel/kcm.cpp:126

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

[plasmashell] [Bug 414085] New: Plasma crash after login and presing Win key

2019-11-12 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=414085

Bug ID: 414085
   Summary: Plasma crash after login and presing Win key
   Product: plasmashell
   Version: 5.17.2
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: kde-b...@ssr.host.ru
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.2)

Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-22-generic x86_64
Distribution: Ubuntu 19.10

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

Just booted after kernel update and pressed Windows key to get into menu

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fed8b19d800 (LWP 1844))]

Thread 14 (Thread 0x7fed4a7fc700 (LWP 5079)):
#0  0x7fed88f982c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ac0d3752b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7fed88f982c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ac0d375260, cond=0x55ac0d375288) at pthread_cond_wait.c:508
#2  0x7fed88f982c6 in __pthread_cond_wait (cond=0x55ac0d375288,
mutex=0x55ac0d375260) at pthread_cond_wait.c:638
#3  0x7fed89b2cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fed89b2cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed67cdcea0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fed67ce0c3e in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fed67cdc072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fed67cdeb83 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fed89b26cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fed88f91669 in start_thread (arg=) at
pthread_create.c:479
#11 0x7fed897a2323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7fed4affd700 (LWP 5078)):
#0  0x7fed88f982c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ac0d3752b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7fed88f982c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ac0d375260, cond=0x55ac0d375288) at pthread_cond_wait.c:508
#2  0x7fed88f982c6 in __pthread_cond_wait (cond=0x55ac0d375288,
mutex=0x55ac0d375260) at pthread_cond_wait.c:638
#3  0x7fed89b2cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fed89b2cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed67cdcea0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fed67ce0c3e in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fed67cdc072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fed67cdeb83 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7fed89b26cc2 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fed88f91669 in start_thread (arg=) at
pthread_create.c:479
#11 0x7fed897a2323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7fed4b7fe700 (LWP 5077)):
#0  0x7fed88f982c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ac0d3752b0) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1  0x7fed88f982c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x55ac0d375260, cond=0x55ac0d375288) at pthread_cond_wait.c:508
#2  0x7fed88f982c6 in __pthread_cond_wait (cond=0x55ac0d375288,
mutex=0x55ac0d375260) at pthread_cond_wait.c:638
#3  0x7fed89b2cdef in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fed89b2cee1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fed67cdcea0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fed67ce0c3e in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fed67cdc072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver

[Discover] [Bug 380425] New: Discover app crash on update attempt

2017-06-01 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=380425

Bug ID: 380425
   Summary: Discover app crash on update attempt
   Product: Discover
   Version: 5.9.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: kde-b...@ssr.host.ru
  Target Milestone: ---

Application: plasma-discover (5.9.4)

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

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

Just tried to update OS via taskbar. Systray → Updates → "Updates available" →
clicked "Update", then got this crash (3 times in row). Crash Reporting
Assistant said the crash information is useful, that's why I'm sending it.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4586ec2440 (LWP 6712))]

Thread 34 (Thread 0x7f4514ff1700 (LWP 6747)):
#0  0x7f457d014a7d in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f457d01549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f457d01568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f458304bf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4582ff588a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4582e22fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4582e27c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f457f1b26da in start_thread (arg=0x7f4514ff1700) at
pthread_create.c:456
#8  0x7f458242317f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 33 (Thread 0x7f45157f2700 (LWP 6746)):
#0  0x7f457d05aed9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f457d015532 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f457d01568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f458304bf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4582ff588a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4582e22fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4582e27c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f457f1b26da in start_thread (arg=0x7f45157f2700) at
pthread_create.c:456
#8  0x7f458242317f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 32 (Thread 0x7f4515ff3700 (LWP 6745)):
#0  0x7f458241718d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f457d015576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f457d01568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f458304bf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f4582ff588a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4582e22fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4582e27c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f457f1b26da in start_thread (arg=0x7f4515ff3700) at
pthread_create.c:456
#8  0x7f458242317f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 31 (Thread 0x7f45167f4700 (LWP 6744)):
#0  0x7f4582412cad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f457d059b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f457d015042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f457d015514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f457d01568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f458304bf2b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4582ff588a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4582e22fe3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4582e27c98 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f457f1b26da in start_thread (arg=0x7f45167f4700) at
pthread_create.c:456
#10 0x7f458242317f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 30 (Thread 0x7f4516ff5700 (LWP 6743)):
#0  0x7f457d05aef4 in g_mutex_unlock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f457d014f81 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f457d01551

[systemsettings] [Bug 394693] New: Keyboard layout Preview doesn't show russian layout

2018-05-26 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=394693

Bug ID: 394693
   Summary: Keyboard layout Preview doesn't show russian layout
   Product: systemsettings
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_keyboard_layout
  Assignee: unassigned-b...@kde.org
  Reporter: kde-b...@ssr.host.ru
  Target Milestone: ---

Keyboard layout Preview doesn't show Russian layout. I have 2 layouts: en and
ru. If I choose ru and Preview, I see English and can't see Russian.

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

[systemsettings] [Bug 394693] Keyboard layout Preview doesn't show russian layout

2018-05-26 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=394693

--- Comment #1 from Sergei S. Rublёv  ---
In console, I see different messages, one of them "keyboard_preview: Symbols
Parsing failed"

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

[systemsettings] [Bug 394693] Keyboard layout Preview doesn't show russian layout

2018-05-27 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=394693

Sergei S. Rublёv  changed:

   What|Removed |Added

Version|unspecified |5.12.5

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

[systemsettings] [Bug 384596] New: Crash on resetting Themes

2017-09-11 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=384596

Bug ID: 384596
   Summary: Crash on resetting Themes
   Product: systemsettings
   Version: 5.9.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: kde-b...@ssr.host.ru
  Target Milestone: ---

Application: systemsettings5 (5.9.5)

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: Was setting Workspace Theme to
all defaults in KDE. Turning "Use Desktiop Layout from theme" setting on causes
crash when applying.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc8fd9ec8c0 (LWP 1923))]

Thread 9 (Thread 0x7fc8b6bfa700 (LWP 2031)):
#0  0x7fc8f973fd8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc8f3825576 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc8f382568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc8fa0630bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc8fa00cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc8f9e3af83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc8f815ddf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fc8f9e3fc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc8f59c26da in start_thread (arg=0x7fc8b6bfa700) at
pthread_create.c:456
#9  0x7fc8f974bd7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7fc8b5bf9700 (LWP 2030)):
#0  0x7fc8f386aed9 in g_mutex_lock () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc8f3824a79 in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc8f382549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc8f382568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc8fa0630bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc8fa00cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc8f9e3af83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc8f815ddf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7fc8f9e3fc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fc8f59c26da in start_thread (arg=0x7fc8b5bf9700) at
pthread_create.c:456
#10 0x7fc8f974bd7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fc8afdf2700 (LWP 2029)):
#0  0x7fc8f973b8ad in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fc8f3869b30 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc8f3825042 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc8f3825514 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc8f382568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc8fa0630bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc8fa00cbea in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fc8f9e3af83 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fc8f815ddf5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7fc8f9e3fc38 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fc8f59c26da in start_thread (arg=0x7fc8afdf2700) at
pthread_create.c:456
#11 0x7fc8f974bd7f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fc8bcf22700 (LWP 1951)):
#0  0x7ffeec795a0c in clock_gettime ()
#1  0x7fc8f975a506 in __GI___clock_gettime (clock_id=1, tp=0x7fc8bcf21a40)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7fc8f9ee4c41 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7fc8fa060d39 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fc8fa0612e5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fc8fa06268e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fc8f3824a6d in g_main_context_prepare () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fc8f382549b in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fc8f382568c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fc8fa0630bb in
QEventDispatcherGlib::processEvents(QFlags) ()

[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget with QSG_RENDER_LOOP=basic

2024-12-03 Thread Sergei S . Rublёv
https://bugs.kde.org/show_bug.cgi?id=368838

Sergei S. Rublёv  changed:

   What|Removed |Added

 CC||kde-b...@ssr.host.ru

--- Comment #132 from Sergei S. Rublёv  ---
I am having this in 6.11.10-300.fc41.x86_64, Plasma 6.2.4, Wayland, Nvidia
565.57.01

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

[kopete] [Bug 365984] New: kopete does not ignore incoming messages formatting

2016-07-22 Thread Sergei via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365984

Bug ID: 365984
   Summary: kopete does not ignore incoming messages formatting
   Product: kopete
   Version: 1.6.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Chat Window
  Assignee: kopete-bugs-n...@kde.org
  Reporter: spirit...@gmail.com

I have enabled option "Ignore peer's formatting", but kopete still shows
formatted incoming messages - another font size and color.

kopete-1.6.60, kde-4.13.3 (latest packages from default kubuntu-14.04
repositories)


Reproducible: Always

Steps to Reproduce:
1. Enable "Ignore peer's formatting" (Settings -> Chat window -> Colors & Fonts
tab)
2. Ask someone to send you a formatted message


Actual Results:  
I see formatted message

Expected Results:  
Message with size/font/color/... configured in kopete settings.

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


[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-03-08 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

--- Comment #2 from Sergei Gureev  ---
Hi, Laurent!

I've send you an email with problem mail in attach. Please review it.
Thanks!

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


[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-03-10 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

--- Comment #4 from Sergei Gureev  ---
I hope so.

In which release will your changes be included?

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


[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-03-15 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

--- Comment #5 from Sergei Gureev  ---
I've updated to 15.12.3 and the bug is still here

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


[KScreen] [Bug 356505] New: Wrong output change detection

2015-12-11 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356505

Bug ID: 356505
   Summary: Wrong output change detection
   Product: KScreen
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kded
  Assignee: dvra...@kde.org
  Reporter: bem...@gmail.com

Steps to reproduce:
1. Open 'journalctl -f' in konsole
2. Open dolphin, RMB anywhere -> New -> Folder
3. When "New folder" dialog window appears I got following errors in logs:
http://pastebin.com/G1EVC39f

Reproducible: Always

Also, I've got heavy freezes on any file operations in dolphin, such as create
folder, move file, etc.
I think this bug is the cause of this misbehavior.

System info:
# hwinfo --short
http://pastebin.com/1k2bzq5f

# uname -a
Linux archer 4.2.5-1-zen #1 ZEN SMP PREEMPT Tue Oct 27 10:09:21 UTC 2015 x86_64
GNU/Linux

# xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x47 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
4 outputs: 4 associated providers: 0 name:Intel

# pacman -Q plasma-desktop 
plasma-desktop 5.5.0-3

Intel microcode is installed

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


[KScreen] [Bug 356505] Wrong output change detection

2015-12-30 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356505

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

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


[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-04-26 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

Sergei Gureev  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

--- Comment #11 from Sergei Gureev  ---
Bug seems to be fixed in kmail 16.04

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


[klipper] [Bug 343519] Klipper systray widget is not closed automatically once a user has selected an item

2016-01-24 Thread Sergei Stolyarov via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=343519

Sergei Stolyarov  changed:

   What|Removed |Added

 CC||ser...@regolit.com

--- Comment #11 from Sergei Stolyarov  ---
There should option like “Close menu on item select”. And, probably, another
option: target, where clicked item contents should be placed (clipboard or
selection).

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

[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-03-27 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

Sergei Gureev  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|UNCONFIRMED

--- Comment #9 from Sergei Gureev  ---
I've updated kmail and kdepim to 15.12.3 and the bug still persists

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


[konqueror] [Bug 359224] New: Linux mint 17.3 kongueror 4.14.13

2016-02-10 Thread sergei slabun via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359224

Bug ID: 359224
   Summary: Linux mint 17.3 kongueror 4.14.13
   Product: konqueror
   Version: Git
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: konq-e
  Assignee: kon...@kde.org
  Reporter: slabu...@mail.ru

Created attachment 97131
  --> https://bugs.kde.org/attachment.cgi?id=97131&action=edit
фото панели настроек

в настройках отсутствует раздел МОДУЛИ И ПЛАГИНЫ нет воспроизвидения видео.

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

[kmail2] [Bug 359813] New: images inserted in mail with CID are not displayed

2016-02-26 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

Bug ID: 359813
   Summary: images inserted in mail with CID are not displayed
   Product: kmail2
   Version: 5.1
  Platform: Archlinux Packages
   URL: http://snag.gy/nfCac.jpg
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: bem...@gmail.com

I've got KMail connected to both Gmail and Exchange servers.
When I receive mail with build-in images, they are displayed as attachments and
in message's body there is only an empty frame.
If launch kmail in console, I can see following errors every time I open
message with such image:
couldn't create slave: "Unable to create io-slave:\nklauncher said: Unknown
protocol «cid».\n"

If I open such message in message editor, images are displayed correctly.

I'm used to face this bug also on OpenSuse, and now I'm getting it on
ArchLinux.

Reproducible: Always

Steps to Reproduce:
1. Get e-mail with attached (build-in) image
2. Select this e-mail in message list
3. Look into message view section.

Actual Results:  
Images are missing, there are only empty frames for them

Expected Results:  
Images are displayed correctly

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

[kmail2] [Bug 359813] images inserted in mail with CID are not displayed

2016-02-26 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359813

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

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


[KScreen] [Bug 356505] Wrong output change detection

2016-02-29 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356505

Sergei Gureev  changed:

   What|Removed |Added

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

--- Comment #1 from Sergei Gureev  ---
Cannot reproduce it anymore

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


[frameworks-kio] [Bug 355390] Localized Dolphin crashes when I try to create new folder

2016-02-29 Thread Sergei Gureev via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=355390

Sergei Gureev  changed:

   What|Removed |Added

 CC||bem...@gmail.com

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


[kipiplugins] [Bug 356673] New: MediaWiki export doesn't work

2015-12-14 Thread Sergei S . Rublёv via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356673

Bug ID: 356673
   Summary: MediaWiki export doesn't work
   Product: kipiplugins
   Version: 4.14.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: MediaWiki
  Assignee: kde-imag...@kde.org
  Reporter: kde-b...@ssr.host.ru

I cannot upload any file to Wikimedia Commons with KIPI "Export to MediaWiki"
plugin.

In the past, this worked. From some time, this stopped working. Relatively long
ago, several months. I tried this in several Linux installations, the same
everywhere — this time in latest Fedora with latest updates.

I pick a file, successfully login to Commons in the plugin, fill out forms.
When I click "Upload", it starts "uploading", but eternally sticks at 0%, never
upload. I have to interrupt this, and DigiKam status bar then sticks at
"Aborting" (with 0%).

Reproducible: Always

Steps to Reproduce:
1. Pick a file, start the plugin, login to Commons
2. Fill out basical forms (maybe not all) 
3. Press upload button

Actual Results:  
No upload

Expected Results:  
Upload to Commons

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