[plasmashell] [Bug 484090] plasmashell dies when creating virtual screens with xrandr

[eduard]

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

--- Comment #2 from eduard  ---
(In reply to fanzhuyifan from comment #1)
> In general using xrandr to manually manipulate the monitor config is not
> formally supported in Plasma.

I don't expect plasma to manage background of newly created virtual screens.
Nor any other "unsuported" feature. Just it to not crash as it did not crash
few weeks ago.
Converting a laptop into a full 3 monitors computer simply putting some glasses
on is incredible convenient, and right now, wayland's virtual screens do not
work well enough for it.

Just asking that, as I understand, there is a code that count screens and if
they don't match it fails. It should consider the possibility that xrandr has
been used and not fail. I think.

Anyway, for anybody that gets here only to find that the case has been closed
"because it is not supported": I have a workaround. Install liquidshell, a
plasmashell substitution.
Not as preatty or powerful, but at least it works with xrandr and you can call
it after enabling xrandr virtual desktops.

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

[plasmashell] [Bug 484090] New: plasmashell dies when creating virtual screens with xrandr

[eduard]

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

Bug ID: 484090
   Summary: plasmashell dies when creating virtual screens with
xrandr
Classification: Plasma
   Product: plasmashell
   Version: 6.0.2
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: "Manage Desktop and Panels" window
  Assignee: plasma-b...@kde.org
  Reporter: edua...@bredax.com
  Target Milestone: 1.0

SUMMARY
***
In order to use the computer with Meta Quest googles, I have a script that
creates a couple of virtual screens (xrandr) and then calls the App that lets
you remotely connect with the computer.
This week, this process hangs plasmashell as it seems uncapable to start if the
number of phisical screens differ from the total one.

plasmashell
ASSERT: "allScreens.count() == m_sizeSortedScreens.count()" in file
./shell/screenpool.cpp, line 337
KCrash: Application 'plasmashell' crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 4792
KCrash: Arguments: /usr/bin/plasmashell 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi
qt.qml.typeresolution.cycle: Cyclic dependency detected between
"qrc:/qt/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and
"qrc:/qt/qml/org/kde/desktop/MenuItem.qml"
qrc:/ui/MainPage.qml:64:13: QML MainPageButton: Binding loop detected for
property "icon.height"
qrc:/ui/MainPage.qml:48:13: QML MainPageButton: Binding loop detected for
property "icon.height"
29  ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
QSocketNotifier: Invalid socket 5 and type 'Read', disabling...

***


STEPS TO REPRODUCE
1.  Open KDE with X11
2.  Use xrandr to create a virtual screen.

#!/bin/sh
xrandr --addmode HDMI-1 2560x1600 
xrandr --addmode HDMI-2 2560x1600
xrandr --output HDMI-1 --pos 0x0 --mode 2560x1600  --right-of eDP-1
xrandr --output HDMI-2 --pos 0x0 --mode 2560x1600  --left-of eDP-1 



3. plasmashell crashes and does not run again until I kill the virtual screens
with
 xrandr --output HDMI-1 --off
xrandr --output HDMI-2 --off


OBSERVED RESULT

plasmashell dies and cannot be restarted

EXPECTED RESULT

plasmashell shouldn't die.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 
Operating System: KDE neon 6.0
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.5.0-26-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 23.2 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LG Electronics
Product Name: 17Z990-V.AA75B
System Version: 0.1


ADDITIONAL INFORMATION

It sure works in KDE 5.27 and I would bet it worked in KDE 6.0.0 or 6.0.1

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

[kdeconnect] [Bug 481885] Bluetooth keyboard accents/tilde/(two keystrokes) symbols do not route correctly.

[eduard]

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

eduard  changed:

   What|Removed |Added

 CC||edua...@bredax.com

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

[kdeconnect] [Bug 481885] New: Bluetooth keyboard accents/tilde/(two keystrokes) symbols do not route correctly.

[eduard]

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

Bug ID: 481885
   Summary: Bluetooth keyboard accents/tilde/(two keystrokes)
symbols do not route correctly.
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: edua...@bredax.com
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY

I am trying to attach a bluetooth keyboard my mobile phone in order to route it
to my computer and use it as a local keyboard in the computer.
kdeconnect works great for that with simple characters, but fails when sending
double keystrokes characters such as à,é...
Instead of an à, the server side receives `a, instead of an é, it receives 'e
and so forth.


STEPS TO REPRODUCE
1. Configure an international bluetooth keyboard in android.
2. Set it up so it has the correct layout in android.
3. Start kdeconnect in Android and route keyboard/mouse to a server.
4. Try to type accentuated vowels... à, é, í...
OBSERVED RESULT
You receive every keystroke individually: `a 'e 'i

EXPECTED RESULT
You should only receive keys once selection has been made (à, é, í)
OR
You should receive "open keystrokes" as in kde where you get a temporary
`(underscored) that gets substituted by the correct accentuated vowel once you
press it. 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 23.10
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 473932] New: Application Dashboard do not remember what is its proper monitor.

[eduard]

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

Bug ID: 473932
   Summary: Application Dashboard do not remember what is its
proper monitor.
Classification: Plasma
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: plasma-b...@kde.org
  Reporter: edua...@bredax.com
CC: mikel5...@gmail.com, noaha...@gmail.com
  Target Milestone: 1.0

SUMMARY
In a multiple display's setup, application launcher do not remember the display
it is set in after powering down and up one of the monitors.


STEPS TO REPRODUCE
1. Create a setup with three monitors. Assign the launcher to the center
display.
2. Open few windows and put them around the screen ( not needed surely, just to
make the point that they do remember where they are).
3. Power off the first and the third monitor.
4. Power on the monitors again.
5. Launch the  Application Dashboard.

OBSERVED RESULT

Application Launchboard wakes up in the first monitor.

EXPECTED RESULT

Application Launchboard should wake up in the center monitor, which is the one
where the launcher sits.
IMPORTANT: Just to be clear... prior to powering down and up the monitors, the
launchboard correctly wakes up in the middle monitor, where the launcher is
located.


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-27-generic (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4070/PCIe/SSE2

ADDITIONAL INFORMATION
Windows do magically remember where they were sited once I power up those
monitors. Great job! Maybe that is the clue to solve it. Yet I would guess that
simply asking everytime what monitor has the launcher sited should solve the
problem.

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

[kstars] [Bug 460558] New: I can't solve any object because the telescope coordinates are fixed and never change

[Eduard]

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

Bug ID: 460558
   Summary: I can't solve any object because the telescope
coordinates are fixed and never change
Classification: Applications
   Product: kstars
   Version: 3.6.1
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: valldor...@gmail.com
  Target Milestone: ---

Created attachment 152915
  --> https://bugs.kde.org/attachment.cgi?id=152915=edit
Image of the Solver Control screen showing the immovable numbers 23 and 180.

Hello

I'm working with Kstars V 3.6.1 stable in Linux mint and an LX200

The problem I have is when I want to use the Solver Control because when I look
for a star and I center it in the telescope and in kstars, the same numbers
always appear in telescope coordinates 23:56:00 and 180:00:00. And they are
always fixed.

I have connected first the telescope and then kstars, then the other way around
and I have changed the star. And I've tried all the combinations.

But the numbers I have written are fixed and do not change. They never change
when changing celestial objects. For this reason it is not possible to solve
any object 

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT

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

[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open when using an NVIDIA GPU on Wayland

[Eduard]

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

--- Comment #60 from Eduard  ---
On  my system QSG_RENDER_LOOP is set to "basic" anyway.
>From the info on https://nobaraproject.org/ I learned today that this value is
set by default if you are using NVIDIA's proprietary driver:
"QSG_RENDER_LOOP=”basic” set for nvidia cards — fixes nouveau Wayland freezes.
The nvidia proprietary driver sets this anyway after installation. This fixes
the issue of KDE Wayland often times freezing on first login before nvidia
proprietary drivers are installed."

In other words: This fix is ONLY effective if you use Nouveau. If you
experience the issues with the proprietary driver like me, something else is
wrong that you probably cannot fix by yourself.

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

[frameworks-plasma] [Bug 455575] Panel widget popups sometimes do not open

[Eduard]

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

Eduard  changed:

   What|Removed |Added

 CC||jongedu...@hotmail.com

--- Comment #30 from Eduard  ---
Hi! I'ld also like to add my 2 cents here. Same situation: NVIDIA & Wayland.
Symptom: Application Launcher not opening most of the time.
Waiting a while before opening it again appears to help very often, and
repeatedly clicking on it - clearly - not.

General note:

I would REALLY wish that I was able to say that I love to use nothing else than
KDE Plasma for all it's AMAZING features and beauty, but the reality is that I
am experiencing to many bugs with it every time I use it.

And of course, I can fall back to Xorg. But on Xorg it's so slow that I
consider it unusable, especially with things like Application Launcher.

Wayland is definitely the way to go!, it's the future.
But sadly, as very much opposed to my Wayland experience with GNOME (same
machine and both on Arch Linux - so the versions of the software are very new),
the large number of bugs makes it very hard to use.

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

[Powerdevil] [Bug 454161] Brightness stuck at 30%

[eduard]

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

eduard  changed:

   What|Removed |Added

 CC||edua...@bredax.com

--- Comment #17 from eduard  ---
Same workaround for KUbuntu :

sudo apt install powerdevil=4:5.24.4-0ubuntu1 powerdevil-data=4:5.24.4-0ubuntu1
libpowerdevilcore2=4:5.24.4-0ubuntu1 libpowerdevilui5=4:5.24.4-0ubuntu1

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

[kstars] [Bug 449221] New: Current traking is poor. Two weeks ago it was perfect

[Eduard]

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

Bug ID: 449221
   Summary: Current traking is poor. Two weeks ago it was perfect
   Product: kstars
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: mutla...@ikarustech.com
  Reporter: valldor...@gmail.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION
A week ago I had a traking of 0.35.
But on Monday the 24th I have reinstalled Linux on my computer and also Kstars.
And now I have a tracking of 1.40 / 1.90 and I can't reduce it in any way.

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

[kwin] [Bug 446478] Plasma desktop unusable due to stuttering with compositing enabled on VRR display with gsync enabled

[Eduard]

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

--- Comment #2 from Eduard  ---
I forgot to mention: There's nothing obvious in the logs for kernel, X,
krunner, kwin, xsession, etc. But one of the symptoms becomes visible once
gsync is enabled: You start seeing entries like

(EE) event3  - DELL Dell USB Entry Keyboard: client bug: event processing
lagging behind by 31ms, your system is too slow

for mouse and keyboard despite <5% cpu utilization per core.

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

[kwin] [Bug 446478] Plasma desktop unusable due to stuttering with compositing enabled on VRR display with gsync enabled

[Eduard Bachmakov]

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

--- Comment #1 from Eduard Bachmakov  ---
Created attachment 144214
  --> https://bugs.kde.org/attachment.cgi?id=144214=edit
perf at 145Hz for 10s on kwin_x11 when gsync-disabled

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

[kwin] [Bug 446478] New: Plasma desktop unusable due to stuttering with compositing enabled on VRR display with gsync enabled

[Eduard Bachmakov]

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

Bug ID: 446478
   Summary: Plasma desktop unusable due to stuttering with
compositing enabled on VRR display with gsync enabled
   Product: kwin
   Version: 5.23.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: e.bachma...@gmail.com
  Target Milestone: ---

Created attachment 144213
  --> https://bugs.kde.org/attachment.cgi?id=144213=edit
perf at 145Hz for 10s on kwin_x11 when gsync-enabled

SUMMARY
On my single-monitor x11 setup, enabling (a.k.a. "not disabling") gsync in the
nvidia-settings causes everything to stutter. This is new since my distro
upgrade (see versions below). Happens both logged-in and when sddm is running.

It gives the impression that "processing speed" is coupled with the refresh
rate. For example, with an empty desktop/no visual movement, triggering krunner
takes multiple seconds ... every time. When I trigger it while quickly dragging
a window (thus raising the VRR) it happens ~instantly. (It's almost as if it
takes a fixed number of frames to show it.)

When disabling gsync or compositing, fps is at a locked 144 and no problems
occur.

This bug sounds somewhat overlapping with #445330 but they explicitly say "x11
is fine" and don't mention VRR.

STEPS TO REPRODUCE
1. Have plasma5 desktop running on X11
2. Open nvidia-settings
3. Toggle "Allow G-SYNC/G-SYNC Compatible" from off to on

OBSERVED RESULT
1. FPS counter (built into the display itself) unlocks from 144 to a variable
number roughly proportional to amount of movement on screen, as low as 1 FPS.
2. During "low FPS times" everything stutters, there are large delays (e.g.
krunner or kickoff)

EXPECTED RESULT
1. either locked max fps (windows does this) 
2. or instant fps scaling without any delays (phones do that I believe)

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.3 (prev: 5.21.5)
KDE Frameworks Version: 5.87.0 (prev: 5.81.0)
Qt Version: 5.15.3 (prev: 5.15.2)

ADDITIONAL INFORMATION
Kernel: 5.15.4 (prev: same)
Distro: NixOS 21.11.333896.a640d8394f3 (prev: 21.05)
Nvidia driver: 495.44 (prev: 470.63.01)

I was curious as to how kwin is handling this internally so peeked at it a bit,
see attachments. [gsync-on variant seems to eat quite a bit more cycles and
spend a lot of time within destructors?]

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

[dolphin] [Bug 439196] New: Binding CTRL-J in readline's inputrc breaks Dolphin's sendCdToTerminal functionality

[Eduard Bachmakov]

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

Bug ID: 439196
   Summary: Binding CTRL-J in readline's inputrc breaks Dolphin's
sendCdToTerminal functionality
   Product: dolphin
   Version: 21.04.2
  Platform: Gentoo Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: panels: terminal
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: e.bachma...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 139679
  --> https://bugs.kde.org/attachment.cgi?id=139679=edit
Annotated demo of issue.

SUMMARY
cd's are no longer run for you but rather appear as literals your line editor.

STEPS TO REPRODUCE
0. Have bash as your shell
1. Add 'Control-j: menu-complete' to your .inputrc (or unbind via "...: nop")
2. Open dolphin
3. Open terminal component via F4 shortcut
4. Observe results

OBSERVED RESULT
Current directory does NOT change. The ' cd $target' string now in current
input buffer/line editor.

See annotated screenshot.

Note that pressing "Enter" still works just as expected.

EXPECTED RESULT
Changed directory.

SOFTWARE/OS VERSIONS
KDE Frameworks Version: 5.83.0
Qt Version: Qt 5.15.2 (built against 5.15.2)

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

[krita] [Bug 424105] New: Krita 4.3 error after exit

[Eduard]

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

Bug ID: 424105
   Summary: Krita 4.3 error after exit
   Product: krita
   Version: 4.3.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: krita-bugs-n...@kde.org
  Reporter: scal...@gmail.com
  Target Milestone: ---

Application: krita (4.3.0)

Qt Version: 5.14.2
Frameworks Version: 5.71.0
Operating System: Linux 5.6.13-153.current x86_64
Windowing system: X11
Distribution: Solus 4.1 Fortitude

-- Information about the crash:
- What I was doing when the application crashed:
After I finished work on Krita everytime Dr Konqi report about Segmentation
fault   

- Custom settings of the application:

All setting in Krita by default, except - i disable all vector optimizations (i
have AMD CPU)

The crash can be reproduced every time.

-- Backtrace:
Application: Krita (krita), signal: Segmentation fault

[KCrash Handler]
#4  0x7f3d1d4ddd06 in ?? () from /usr/lib/libQt5Widgets.so.5
#5  0x7f3d1d4ece0a in ?? () from /usr/lib/libQt5Widgets.so.5
#6  0x7f3d1d4ece30 in ?? () from /usr/lib/libQt5Widgets.so.5
#7  0x7f3d1d4eced5 in ?? () from /usr/lib/libQt5Widgets.so.5
#8  0x7f3d1d4e2467 in ?? () from /usr/lib/libQt5Widgets.so.5
#9  0x7f3d1d4d23d8 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#10 0x7f3d1d4d28a9 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f3d1c9c3e7e in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#12 0x7f3d1d4d26b6 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f3d1d5a664d in ?? () from /usr/lib/libQt5Widgets.so.5
#14 0x7f3d1c9c3e7e in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#15 0x7f3d1d4d26b6 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#16 0x7f3d1d5a8d04 in ?? () from /usr/lib/libQt5Widgets.so.5
#17 0x7f3d1c9c3e7e in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#18 0x7f3d1d4d26b6 in QWidget::~QWidget() () from
/usr/lib/libQt5Widgets.so.5
#19 0x7f3c88d0cdd9 in ?? () from
/usr/lib/python3.7/site-packages/PyQt5/QtWidgets.so
#20 0x7f3c89733ac1 in ?? () from
/usr/lib/python3.7/site-packages/PyQt5/QtCore.so
#21 0x7f3c898386f8 in ?? () from
/usr/lib/python3.7/site-packages/PyQt5/sip.so
#22 0x7f3c8973376c in ?? () from
/usr/lib/python3.7/site-packages/PyQt5/QtCore.so
#23 0x7f3c89cba70b in PyCFunction_Call () from
/usr/lib/libpython3.7m.so.1.0
#24 0x7f3c89dee14a in ?? () from /usr/lib/libpython3.7m.so.1.0
#25 0x7f3c89dcabb3 in Py_FinalizeEx () from /usr/lib/libpython3.7m.so.1.0
#26 0x7f3c89f797d1 in ?? () from /usr/lib64/kritaplugins/kritapykrita.so
#27 0x7f3c89f7995c in ?? () from /usr/lib64/kritaplugins/kritapykrita.so
#28 0x7f3c89f76bf7 in ?? () from /usr/lib64/kritaplugins/kritapykrita.so
#29 0x7f3d1c9c3e7e in QObjectPrivate::deleteChildren() () from
/usr/lib/libQt5Core.so.5
#30 0x7f3d1c9cd4f6 in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#31 0x7f3d1c99ca0a in QCoreApplication::~QCoreApplication() () from
/usr/lib/libQt5Core.so.5
#32 0x7f3d1d494dc4 in QApplication::~QApplication() () from
/usr/lib/libQt5Widgets.so.5
#33 0x7f3d1f00c40f in QtSingleApplication::~QtSingleApplication() () from
/usr/lib/libkritaui.so.19
#34 0x0040737b in main ()
[Inferior 1 (process 5199) detached]

Possible duplicates by query: bug 422974, bug 420612, bug 419140, bug 418530,
bug 417465.

Reported using DrKonqi

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

[LabPlot2] [Bug 395357] Changing of the x- and y- axis-scales from linear to log, ln or any other doesn't work in appropriate way.

[Eduard]

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

Eduard  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Eduard  ---
Solution was found. Plot and axis settings need to be changed together to
obtain appropriate plot representation.

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

[LabPlot2] [Bug 395357] New: Changing of the x- and y- axis-scales from linear to log, ln or any other doesn't work in appropriate way.

[Eduard]

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

Bug ID: 395357
   Summary: Changing of the x- and y- axis-scales from linear to
log, ln or any other doesn't work in appropriate way.
   Product: LabPlot2
   Version: 2.4.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: alexander.se...@web.de
  Reporter: e.maievs...@gmail.com
  Target Milestone: ---

Changing of axis-scales doesn't affect on the curve shape and dots position. 
Ticks and grids  dissapear after the axis-scale changing to log,ln or any other
scale.

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

[LabPlot2] [Bug 395357] Changing of the x- and y- axis-scales from linear to log, ln or any other doesn't work in appropriate way.

[Eduard]

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

Eduard  changed:

   What|Removed |Added

 CC||e.maievs...@gmail.com

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

[LabPlot2] [Bug 395352] problem with importing of csv/ascii data-files with mixed text/numeric columns

[Eduard]

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

Eduard  changed:

   What|Removed |Added

 CC||e.maievs...@gmail.com

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

[LabPlot2] [Bug 395352] New: problem with importing of csv/ascii data-files with mixed text/numeric columns

[Eduard]

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

Bug ID: 395352
   Summary: problem with importing of csv/ascii data-files with
mixed text/numeric columns
   Product: LabPlot2
   Version: 2.4.0
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: backend
  Assignee: alexander.se...@web.de
  Reporter: e.maievs...@gmail.com
  Target Milestone: ---

Data type of every column is automatically assigned as "Numeric". The algorithm
implemented for importing of ascii/csv data files leads to inappropriate data
representation in resulting spreadsheet.

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

[kio] [Bug 393047] SFTP transfers handled by kio_sftp are much slower than those handled by scp

[eduard]

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

--- Comment #2 from eduard <edua...@bredax.com> ---
I did open the bug. Is there anything that can be done with buffer sizes or is
it a totally unrelated problem as I guess?

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

[kio] [Bug 393047] SFTP transfers handled by kio_sftp are much slower than those handled by scp

[eduard]

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

eduard <edua...@bredax.com> changed:

   What|Removed |Added

 CC||edua...@bredax.com

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

[kio] [Bug 393047] New: SFTP transfers handled by kio_sftp are much slower than those handled by scp

[eduard]

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

Bug ID: 393047
   Summary: SFTP transfers handled by kio_sftp are much slower
than those handled by scp
   Product: kio
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: sftp
  Assignee: a...@cryptomilk.org
  Reporter: edua...@bredax.com
  Target Milestone: ---

Description of problem:
On a 100Mbps network, I can transfer files with an average throughput of 11.1
MB/s with sftp get command in Konsole. Transferring the exact files using
Dolphin and kio_sftp gives an average throughput of only 1.2 MB/s.

Version-Release number of selected component (if applicable):
unknown

How reproducible:
Always

Steps to Reproduce:
0.a. Setup a gigabit network with at least two machines and a multiGB file to
download on one side.
0.b. Set up ssh access on machine 2
1. On machine1 open Dolphin
2. Click on the "address" bar. The bar becomes editable
3. enter "sftp://@:/home/"
4. Enter password when prompted for one
5. After directory loads, "copy"(Ctrl-C) a large local, and "paste" (Ctrl-V) it
in the Dolphin window. This starts the transfer.
6. Use the "Network Management" widget to observe transfer speed
7. Try to copy the same or a similar file with scp:
 $ scp large.file @:/home//
8 Observe the transfer speed either by watching scp output, or using the
"Network Management" widget.

Actual results:
kio_sftp: about 1.2 MiB/s average throughput
scp: about 11.1 MiB/s average throughput

Expected results:
Same throughput using both scp and kio_sftp, and same cpu usage.

Additional info:
I transferred one contiguous 65 GiB file. Speeds remain constant in both
escenarios. Dolphin scenario almost 2 days downloading some 215GB.

I read someplace in bugs.kde.org a similar problem solved by increassing some
buffer size for samba kio slave.

I copied this bug description from
https://bugzilla.redhat.com/show_bug.cgi?id=985113 replacing statistics with my
own data.

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

[kdemultimedia] [Bug 376204] no package libqt5multimedia-dev

[Eduard Kalinowski]

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

Eduard Kalinowski <eduard_kalinow...@yahoo.de> changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

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

[kdemultimedia] [Bug 376204] no package libqt5multimedia-dev

[Eduard Kalinowski]

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

--- Comment #1 from Eduard Kalinowski <eduard_kalinow...@yahoo.de> ---
sorry, mistake in package names:
right is qtmultimetia5-dev

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

[kdemultimedia] [Bug 376204] New: no package libqt5multimedia-dev

[Eduard Kalinowski]

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

Bug ID: 376204
   Summary: no package libqt5multimedia-dev
   Product: kdemultimedia
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kde-multime...@kde.org
  Reporter: eduard_kalinow...@yahoo.de
  Target Milestone: ---

it's not possible to find the header files for multimedia qt5

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

[korganizer] [Bug 361419] Unaccepted Google calendar events not shown

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

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

[kmail2] [Bug 368498] Kmail does not open links with target="_blank"

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

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

[kmail2] [Bug 368498] New: Kmail does not open links with target="_blank"

[Eduard Valiauka via KDE Bugzilla]

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

Bug ID: 368498
   Summary: Kmail does not open links with target="_blank"
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: nsbm.abb...@gmail.com

If a html message contains an anchor with target="_blank", clicking such link
does not do anything. Links without target work fine

Reproducible: Always




Sample message that show the issue:

>From a@b.c Fri Sep 09 12:59:16 2016
Delivered-To: d@w.d
Content-Type: text/html; charset=UTF-8





http://google.com;>I'm working
http://google.com; target="_blank">I'm not



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

[dolphin] [Bug 366215] New: Dolphin crashes when right clicking properties on SOME text files

[Eduard Voicu via KDE Bugzilla]

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

Bug ID: 366215
   Summary: Dolphin crashes when right clicking properties on SOME
text files
   Product: dolphin
   Version: 4.14.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: edithera...@yahoo.com

Application: dolphin (4.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.5 (jessie)

-- Information about the crash:
- What I was doing when the application crashed:
I tryied to to open properties of tarball README file.

- Unusual behavior I noticed:
Also, kate crashes when trying to open the file

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc3f641a800 (LWP 15502))]

Thread 4 (Thread 0x7fc3d88b7700 (LWP 15507)):
#0  0x7fc3ec7fe304 in g_mutex_unlock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fc3ec7b9ed9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc3ec7b9ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc3f1bfdd37 in QEventDispatcherGlib::processEvents
(this=0x7fc3d40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc3f1bcd271 in QEventLoop::processEvents
(this=this@entry=0x7fc3d88b6d80, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc3f1bcd5d5 in QEventLoop::exec (this=this@entry=0x7fc3d88b6d80,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc3f1ac1e99 in QThread::exec (this=this@entry=0x27fe080) at
thread/qthread.cpp:538
#7  0x7fc3f1badac3 in QInotifyFileSystemWatcherEngine::run (this=0x27fe080)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fc3f1ac470f in QThreadPrivate::start (arg=0x27fe080) at
thread/qthread_unix.cpp:349
#9  0x7fc3ecca80a4 in start_thread (arg=0x7fc3d88b7700) at
pthread_create.c:309
#10 0x7fc3f5d0087d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7fc3d3fff700 (LWP 15508)):
#0  0x7fc3f5cf3e0d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc3ec7fce50 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc3ec7b996c in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc3ec7b9e83 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fc3ec7b9ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fc3f1bfdd37 in QEventDispatcherGlib::processEvents
(this=0x7fc3cc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fc3f1bcd271 in QEventLoop::processEvents
(this=this@entry=0x7fc3d3ffedd0, flags=...) at kernel/qeventloop.cpp:149
#7  0x7fc3f1bcd5d5 in QEventLoop::exec (this=this@entry=0x7fc3d3ffedd0,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7fc3f1ac1e99 in QThread::exec (this=) at
thread/qthread.cpp:538
#9  0x7fc3f1ac470f in QThreadPrivate::start (arg=0x268ac90) at
thread/qthread_unix.cpp:349
#10 0x7fc3ecca80a4 in start_thread (arg=0x7fc3d3fff700) at
pthread_create.c:309
#11 0x7fc3f5d0087d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fc3d1f8e700 (LWP 15524)):
#0  0x7fc3f5cf7d3d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fc3ec7b9ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fc3ec7b9ffc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fc3f1bfdd37 in QEventDispatcherGlib::processEvents
(this=0x7fc3bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fc3f1bcd271 in QEventLoop::processEvents
(this=this@entry=0x7fc3d1f8dd80, flags=...) at kernel/qeventloop.cpp:149
#5  0x7fc3f1bcd5d5 in QEventLoop::exec (this=this@entry=0x7fc3d1f8dd80,
flags=...) at kernel/qeventloop.cpp:204
#6  0x7fc3f1ac1e99 in QThread::exec (this=this@entry=0x2cae790) at
thread/qthread.cpp:538
#7  0x7fc3f1badac3 in QInotifyFileSystemWatcherEngine::run (this=0x2cae790)
at io/qfilesystemwatcher_inotify.cpp:265
#8  0x7fc3f1ac470f in QThreadPrivate::start (arg=0x2cae790) at
thread/qthread_unix.cpp:349
#9  0x7fc3ecca80a4 in start_thread (arg=0x7fc3d1f8e700) at
pthread_create.c:309
#10 0x7fc3f5d0087d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fc3f641a800 (LWP 15502)):
[KCrash Handler]
#6  d_func (this=0x0) at ../../kdecore/sycoca/ksycocaentry.h:154
#7  KSycocaEntry::name (this=0x0) at ../../kdecore/sycoca/ksycocaentry.cpp:159
#8  0x7fc3f3c117ff in KDEPrivate::KFilePropsPlugin::KFilePropsPlugin
(this=0x2ed7df0, _props=0x0) at ../../kio/kfile/kpropertiesdialog.cpp:744

[kate] [Bug 366214] New: Kate crashes on SOME text files

[Eduard Voicu via KDE Bugzilla]

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

Bug ID: 366214
   Summary: Kate crashes on SOME text files
   Product: kate
   Version: 3.14.2
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: edithera...@yahoo.com

Application: kate (3.14.2)
KDE Platform Version: 4.14.2
Qt Version: 4.8.6
Operating System: Linux 3.16.0-4-amd64 x86_64
Distribution: Debian GNU/Linux 8.5 (jessie)

-- Information about the crash:
- What I was doing when the application crashed:
Trying to open README file from tarballs. Kate crashes. File opens in non-kde
dependant progrms, like libreoffice for instance.

- Unusual behavior I noticed:
Dolphin also crashes when right click-> properties on the file

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f659f2d7780 (LWP 17154))]

Thread 2 (Thread 0x7f658a317700 (LWP 17155)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f658b97edea in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f658b97ee19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f659c1880a4 in start_thread (arg=0x7f658a317700) at
pthread_create.c:309
#4  0x7f659ec4887d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f659f2d7780 (LWP 17154)):
[KCrash Handler]
#6  d_func (this=0x0) at ../../kdecore/sycoca/ksycocaentry.h:154
#7  KSycocaEntry::name (this=0x0) at ../../kdecore/sycoca/ksycocaentry.cpp:159
#8  0x7f658bf9a7d2 in TextLoader (proberType=, filename=...,
this=0x7ffc36694b80) at ../../part/buffer/katetextloader.h:72
#9  Kate::TextBuffer::load (this=0x19f5590, filename=...,
encodingErrors=@0x19f5658: false, tooLongLinesWrapped=@0x19f5659: false,
enforceTextCodec=false) at ../../part/buffer/katetextbuffer.cpp:529
#10 0x7f658c01349e in KateBuffer::openFile (this=0x19f5590, m_file=...,
enforceTextCodec=enforceTextCodec@entry=false) at
../../part/document/katebuffer.cpp:214
#11 0x7f658c008b3f in KateDocument::openFile (this=0x19f4d00) at
../../part/document/katedocument.cpp:1970
#12 0x7f6598fd673a in KParts::ReadOnlyPartPrivate::openLocalFile
(this=this@entry=0x19f4f80) at ../../kparts/part.cpp:591
#13 0x7f6598fd8b76 in KParts::ReadOnlyPart::openUrl
(this=this@entry=0x19f4d00, url=...) at ../../kparts/part.cpp:555
#14 0x7f658bff3dde in KateDocument::openUrl (this=0x19f4d00, url=...) at
../../part/document/katedocument.cpp:2332
#15 0x7f659d72f047 in KateDocManager::openUrl (this=this@entry=0x1878790,
url=..., encoding=..., isTempFile=isTempFile@entry=false, docInfo=...) at
../../../kate/app/katedocmanager.cpp:253
#16 0x7f659d72f4ec in KateDocManager::openUrls (this=0x1878790, urls=...,
encoding=..., isTempFile=isTempFile@entry=false, docInfo=...) at
../../../kate/app/katedocmanager.cpp:228
#17 0x7f659d73e971 in KateViewManager::openUrls (this=0x1aa4060, urls=...,
encoding=..., isTempFile=isTempFile@entry=false, docInfo=...) at
../../../kate/app/kateviewmanager.cpp:337
#18 0x7f659d726f29 in KateApp::startupKate (this=0x7ffc36695660) at
../../../kate/app/kateapp.cpp:225
#19 0x7f659d727e35 in KateApp::initKate (this=this@entry=0x7ffc36695660) at
../../../kate/app/kateapp.cpp:135
#20 0x7f659d728230 in KateApp::KateApp (this=0x7ffc36695660,
args=) at ../../../kate/app/kateapp.cpp:72
#21 0x7f659ef157fc in kdemain (argc=912870240, argv=0x0) at
../../../kate/app/katemain.cpp:377
#22 0x7f659eb81b45 in __libc_start_main (main=0x4006d0 ,
argc=3, argv=0x7ffc366957e8, init=, fini=,
rtld_fini=, stack_end=0x7ffc366957d8) at libc-start.c:287
#23 0x004006fe in _start ()

Possible duplicates by query: bug 348406, bug 344826, bug 342286, bug 341680.

Reported using DrKonqi

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

[digikam] [Bug 363650] I18N_ARGUMENT_MISSING in export dialog image type selection widget

[Eduard Sukharev via KDE Bugzilla]

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

Eduard Sukharev <krap...@mail.ru> changed:

   What|Removed |Added

URL||https://drive.google.com/fi
   ||le/d/0B3OhO8aM9nsXMDNtQy1Ua
   ||3JTMnM/view?usp=sharing
   Priority|NOR |LO
   Severity|minor   |normal
 CC||krap...@mail.ru

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

[digikam] [Bug 363650] New: I18N_ARGUMENT_MISSING in export dialog image type selection widget

[Eduard Sukharev via KDE Bugzilla]

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

Bug ID: 363650
   Summary: I18N_ARGUMENT_MISSING in export dialog image type
selection widget
   Product: digikam
   Version: 5.0.0
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: Export
  Assignee: digikam-de...@kde.org
  Reporter: krap...@mail.ru

Export dialog shows I18N_ARGUMENT_MISSING for each file format and it's human
readable name in image type selection widget

Reproducible: Always

Steps to Reproduce:
1. Select any image in digiKam
2. Open Image editor for it (right click -> Open... or F4)
3. Select File menu -> Export... (Ctrl + Shift + E)
4. Observe image type selection widget

Actual Results:  
All items are of the following format:

PNG(I18N_ARGUMENT_MISSING) Image (*.png(I18N_ARGUMENT_MISSING))

Expected Results:  
Probably something like

PNG Image (*.png)

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

[kmail2] [Bug 363586] New: Kmail2 handles mailto: incorrectly. urlencoded does not work

[eduard via KDE Bugzilla]

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

Bug ID: 363586
   Summary: Kmail2 handles mailto: incorrectly. urlencoded does
not work
   Product: kmail2
   Version: unspecified
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: edua...@bredax.com

I used to create emails with attached files using mailto: and kmail, but latter
versions did stop working properly.

The standard way to work is to urlencode the mailto link so kmail decodes it
and creates the message.
Now kmail2 does not accept the urlencoded link. TO, CC fields get mixed up. And
if you send the code urldecoded then line breaks are not printed correctly.

Example:

What should work
mailto:SOMEONE%20%3Csomeonesmail%40email.com%3E?cc=someotherm...@othermail.com,YETANOTHER20%3Cyetanothermail%40yetanothermail.com%3Esubject=a%20subject%20here%202016body=Dear%20Al%C3%ADcia%2C%0A%0ABlahAdjuntem%20factura%20n%C3%BAm%203043%20de%20Bredax.%0A%0ASalutacions%2C%0Aattachment=/somefile.pdf;
link should work and
/>Urlencoded Correct email
mailto:SOMEONE
?cc=someotherm...@othermail.com,YETANOTHERsubject=a
subject here 2016body=Dear Alícia,
BlahAdjuntem factura núm 3043 de Bredax.

Salutacions,
attachment=/somefile.pdf"
/>Urldecoded incorrect mail

The second one is the one that kind of works, yet line breaks are not
interpreted correctly.

Reproducible: Always

Steps to Reproduce:
1. Test the links I send you
2. You'll see the first does not compose correcly and the second do not have
line breaks.


Actual Results:  
2. You'll see the first does not compose correcly and the second do not have
line breaks.


Expected Results:  
The first link should generate correct email with TO, 2 CC fields, body
attachment and properly formated body.

I am using firefox from last Ubuntu 16.04

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

[kdevelop] [Bug 362413] New: crash after loading

[Eduard Kalinowski via KDE Bugzilla]

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

Bug ID: 362413
   Summary: crash after loading
   Product: kdevelop
   Version: 4.7.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Language Support: CPP
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: eduard_kalinow...@yahoo.de

after loading of project, crash. current kubuntu 16.04

gdb -ex=run --args kdevelop
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11 
Copyright (C) 2016 Free Software Foundation, Inc.   
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>   
This is free software: you are free to change and redistribute it.  
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"  
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".  
Type "show configuration" for configuration details.
For bug reporting instructions, please see: 
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.   
For help, type "help".  
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdevelop...(no debugging symbols found)...done.
Starting program: /usr/bin/kdevelop 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffda9cd700 (LWP 8867)]
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder
Verzeichnis nicht gefunden
[New Thread 0x7fff5959c700 (LWP 8868)]
QFileSystemWatcher: failed to add paths: /home/eduard-x/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
kdevelop(8863)/kdevplatform (language) {anonymous}::shouldClear: version-hint
not found, seems to be an old version 
kdevelop(8863)/kdevplatform (language)
KDevelop::ItemRepositoryRegistryPrivate::open: "The data-repository at
/home/eduard-x/.cache/kdevduchain/kdevelop-{d183ff20-f248-43f0-9458-eafc95c24ee8}
has to be cleared." 
[New Thread 0x7fff53fff700 (LWP 8869)]
[New Thread 0x7fff49507700 (LWP 8870)]
[New Thread 0x7fff48d06700 (LWP 8871)]
[New Thread 0x7fff39323700 (LWP 8877)]
qrc:/qml/main.qml:23:1: QML Loader: Bei der für die Eigenschaft
âÂÂsourceâ angegebenen Bindung wurde eine Endlosschleife festgestellt
qrc:/qml/main.qml:23:1: QML Loader: Bei der für die Eigenschaft
âÂÂsourceâ angegebenen Bindung wurde eine Endlosschleife festgestellt
kdevelop(8863) KDevNinjaBuilderPlugin::KDevNinjaBuilderPlugin: Ninja plugin
installed but ninja is not installed. 
kdevelop(8863)/kdevplatform (shell)
KDevelop::PluginController::loadPluginInternal: "Das Modul
„Ninja-Projekterstellung“ kann nicht korrekt geladen werden und wird
deaktiviert.
Ursache: ." 
kdevelop(8863) KDevNinjaBuilderPlugin::KDevNinjaBuilderPlugin: Ninja plugin
installed but ninja is not installed. 
kdevelop(8863)/kdevplatform (shell)
KDevelop::PluginController::loadPluginInternal: "Das Modul
„Ninja-Projekterstellung“ kann nicht korrekt geladen werden und wird
deaktiviert.
Ursache: ." 
[New Thread 0x7fff2716f700 (LWP 8889)]
[New Thread 0x7fff2696e700 (LWP 8890)]
[New Thread 0x7fff2616d700 (LWP 8892)]
[Thread 0x7fff2716f700 (LWP 8889) exited]
[Thread 0x7fff2696e700 (LWP 8890) exited]
kdevelop(8863)/kdevplatform (shell)
KDevelop::SessionControllerPrivate::performRecovery: Starting recovery from 
"/home/eduard-x/.kde/share/apps/kdevelop/sessions/{d183ff20-f248-43f0-9458-eafc95c24ee8}/recovery/current"
 
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x5c00013
[New Thread 0x7fff2696e700 (LWP 8939)]
[New Thread 0x7fff2716f700 (LWP 8941)]
[New Thread 0x7fff32305700 (LWP 8950)]
kdevelop(8863)/kdevplatform (shell) KDevelop::RunController::registerJob:
non-killable job CMakeImportJob(0x91fd70) registered - this might lead to
crashes on shutdown. 
[New Thread 0x7fff31b04700 (LWP 8951)]
kdevelop(8863)/kdevelop (cpp support) Cpp::instantiateDeclarationAndContext:
Resolved bad base-class "__or_< is_arithmetic< _Tp >, is_void< _Tp >,
is_null_pointer< _Tp > >::type" "__or_< is_arithmetic< _Tp >, is_void< _Tp >,
is_null_pointer< _Tp > >::type" 
kdevelop(8863)/kdevelop (cpp supp

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

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

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

[Akonadi] [Bug 334569] KOrganizer not syncing properly with modified repeated events in google calendar

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

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

[plasmashell] [Bug 356764] left mouse click on taskbar is randomly not detected

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

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

[krunner] [Bug 344328] krunner is not visible when using multiple monitors

[Eduard Valiauka via KDE Bugzilla]

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

Eduard Valiauka <nsbm.abb...@gmail.com> changed:

   What|Removed |Added

 CC||nsbm.abb...@gmail.com

--- Comment #13 from Eduard Valiauka <nsbm.abb...@gmail.com> ---
My setup: laptop + external monitor. Primary display is the external monitor.

In 9 system startups out of 10 krunner is not centred (displayed on the left
half of the primary display). Restarting krunner helps.

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

[digikam] [Bug 355256] Failed to load image if file path contains non-ascii characters

[Eduard Sukharev via KDE Bugzilla]

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

--- Comment #3 from Eduard Sukharev <krap...@mail.ru> ---
(In reply to caulier.gilles from comment #2)
> The error reported under windows come from the libexiv2 interface used by
> digiKam. Code relevant is given below :
> 
> bool MetaEngine::load(const QString& filePath) const
> {
> ...
> Exiv2::Image::AutoPtr image;
> 
> image= Exiv2::ImageFactory::open((const
> char*)(QFile::encodeName(filePath)).constData());
> 
> image->readMetadata();
> ...
> }
> 
> We pass file path to Exiv2 using QString (UTF8). Exiv2 use char* data which
> is converted by QFile::encodeName() function.
> 
> Following this thread :
> 
> http://subsurface.hohndel.narkive.com/sM5jj4ot/file-encodename-and-utf8-as-
> the-default-encoding-under-qt5
> 
> With Qt5 the encoding problem must be fixed under Windows
> 
> Gilles Caulier

Good to know it should be fixed in Qt5 release. Should we close this report as
won't fix or resolved? Or should this rather be fixed even in Qt4 release
series?

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