[plasmashell] [Bug 490880] Unnecessarily large widget size on a vertical taskbar

2024-07-27 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=490880

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
Created attachment 172027
  --> https://bugs.kde.org/attachment.cgi?id=172027=edit
Normal size

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

[plasmashell] [Bug 490880] New: Unnecessarily large widget size on a vertical taskbar

2024-07-27 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=490880

Bug ID: 490880
   Summary: Unnecessarily large widget size on a vertical taskbar
Classification: Plasma
   Product: plasmashell
   Version: 6.1.3
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Activity Switcher
  Assignee: plasma-b...@kde.org
  Reporter: tonal.proms...@gmail.com
CC: ivan.cu...@kde.org
  Target Milestone: 1.0

Created attachment 172026
  --> https://bugs.kde.org/attachment.cgi?id=172026=edit
big widget

SUMMARY
Unnecessarily large widget size on a vertical taskbar
But menu widget - normal size

OBSERVED RESULT
Very large widget size

EXPECTED RESULT
Normal widget size

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.4.0 
Qt Version: 6.7.0

ADDITIONAL INFORMATION

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

[neon] [Bug 463947] Wrong dependencies make it impossible to update/install packages

2024-07-16 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=463947

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[plasmashell] [Bug 489107] Icons-and-Text Task Manager does not allow you to split the group into parts on a vertical panel

2024-06-24 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=489107

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
Created attachment 170911
  --> https://bugs.kde.org/attachment.cgi?id=170911=edit
Screencast

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

[plasmashell] [Bug 489107] New: Icons-and-Text Task Manager does not allow you to split the group into parts on a vertical panel

2024-06-24 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=489107

Bug ID: 489107
   Summary: Icons-and-Text Task Manager does not allow you to
split the group into parts on a vertical panel
Classification: Plasma
   Product: plasmashell
   Version: 6.1.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: tonal.proms...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

SUMMARY
Previously, it was possible to split a group into parts by moving the button
not in the group inside the group.

STEPS TO REPRODUCE
1. Open many Chrome windows
2. Open Dolphin window
3. Move the Dolphin button to the middle of the Crome group.

OBSERVED RESULT
Group not break

EXPECTED RESULT
Group break


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

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 489106] Icons-and-Text Task Manager Sorting within a group does not work on a vertical panel

2024-06-24 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=489106

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
Created attachment 170910
  --> https://bugs.kde.org/attachment.cgi?id=170910=edit
Screencast

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

[plasmashell] [Bug 489106] New: Icons-and-Text Task Manager Sorting within a group does not work on a vertical panel

2024-06-24 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=489106

Bug ID: 489106
   Summary: Icons-and-Text Task Manager Sorting within a group
does not work on a vertical panel
Classification: Plasma
   Product: plasmashell
   Version: 6.1.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: tonal.proms...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

SUMMARY

Previously, it was possible to manually change the order of buttons in a group
by simply moving the selected button to the desired position in the group. It's
not working right now.

STEPS TO REPRODUCE
1. Select the button in the group by holding down the left mouse button
2.  Drag and drop to the selected place inside the group

OBSERVED RESULT
Nothing happens

EXPECTED RESULT
The order of the buttons changes to the selected one

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0 
Qt Version: 6.7.0

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 488733] New: does not show window titles when the panel is positioned vertically

2024-06-19 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=488733

Bug ID: 488733
   Summary: does not show window titles when the panel is
positioned vertically
Classification: Plasma
   Product: plasmashell
   Version: 6.1.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: tonal.proms...@gmail.com
CC: qydwhotm...@gmail.com
  Target Milestone: 1.0

Created attachment 170636
  --> https://bugs.kde.org/attachment.cgi?id=170636=edit
Taskbar

SUMMARY
Previously, both icons and part of the title were shown on the taskbar, now
only icons.
Is it possible to display the title text as before?

OBSERVED RESULT
Icons only on button

EXPECTED RESULT
Icon and text n button 

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 6.1.0
KDE Frameworks Version: 6.3.0 
Qt Version: 6.7.0

ADDITIONAL INFORMATION

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

[neon] [Bug 487374] Missing icons

2024-05-23 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=487374

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[Discover] [Bug 478672] New: Crash Discover

2023-12-17 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=478672

Bug ID: 478672
   Summary: Crash Discover
Classification: Applications
   Product: Discover
   Version: 5.27.10
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: tonal.proms...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.27.10)

Qt Version: 5.15.11
Frameworks Version: 5.113.0
Operating System: Linux 6.2.0-39-generic x86_64
Windowing System: X11
Distribution: KDE neon 5.27
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
I start Diskiver from icon in taskbar - and reseive crash

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Центр программ Discover (plasma-discover), signal: Segmentation
fault

[KCrash Handler]
#4  std::__atomic_base::operator++() (this=0x90) at
/usr/include/c++/11/bits/atomic_base.h:384
#5  QAtomicOps::ref(std::atomic&) (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:283
#6  QBasicAtomicInteger::ref() (this=0x90) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:118
#7  QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*)
(obj=0x55777882c910) at tools/qsharedpointer.cpp:1398
#8  0x7f0b649a639a in QV4::QObjectWrapper::create(QV4::ExecutionEngine*,
QObject*) () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7f0b649a80a0 in
QV4::QObjectWrapper::wrap_slowPath(QV4::ExecutionEngine*, QObject*) () at
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#10 0x7f0b64928068 in QV4::ExecutionEngine::metaTypeToJS(int, void const*)
() at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#11 0x7f0b649279e8 in QV4::ExecutionEngine::fromVariant(QVariant const&) ()
at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#12 0x7f0b649a85c8 in  () at /lib/x86_64-linux-gnu/libQt5Qml.so.5
#13 0x7f0b3c01a776 in  ()
#14 0x in  ()
[Inferior 1 (process 132690) detached]

The reporter indicates this bug may be a duplicate of or related to bug 366264.

Reported using DrKonqi

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

[frameworks-kauth] [Bug 471013] New: polkit-kde-agent-1 not react on KAuth action timeout

2023-06-14 Thread Alexandr Tsygsnov
https://bugs.kde.org/show_bug.cgi?id=471013

Bug ID: 471013
   Summary: polkit-kde-agent-1 not react on KAuth action timeout
Classification: Frameworks and Libraries
   Product: frameworks-kauth
   Version: 5.106.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: seti...@gmail.com
  Target Milestone: ---

SUMMARY
Polikit autintification dialog not react on action timeout. Executed dialog has
stand by, prevents other dialogs from appearing.

STEPS TO REPRODUCE
1. Run any programm using polkit actions (run kate for example);
2. Execute polkit action, for example:
2.1. Open system file (/etc/hosts, for example);
2.2. Modification and save file;
3. Wait on polikit autintification dialog, time usialy 25 seconds.

OBSERVED RESULT
Application show on polkit action error message, polkit autintification dialog
has stand by. Dialog no longer associated with the application.

EXPECTED RESULT
Application send on polkit action error message, polkit autintification dialog
has bin closed.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.9

ADDITIONAL INFORMATION
It seems this is an old story, it is strange that did not find information on
this "feature".

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

[Akonadi] [Bug 402680] akonadiserver do not start

2023-04-28 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=402680

--- Comment #9 from Alexandr Zamaraev (aka Tonal)  ---
see also https://bugs.kde.org/show_bug.cgi?id=411093

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

[Akonadi] [Bug 402680] akonadiserver do not start

2023-04-28 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=402680

--- Comment #8 from Alexandr Zamaraev (aka Tonal)  ---
(In reply to Christophe Marin from comment #7)
> the rules are in the apparmor/mysqld_akonadi file
I found 3 files:
```
/etc/apparmor.d$ ls *akonadi*
mariadbd_akonadi  mysqld_akonadi  usr.bin.akonadiserver
```

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

[Akonadi] [Bug 402680] akonadiserver do not start

2023-04-25 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=402680

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #5 from Alexandr Zamaraev (aka Tonal)  ---
$ akonadictl --version
akonadictl 5.23.0 (23.04.0)

$ akonadictl start
org.kde.pim.akonadictl: Starting Akonadi Server...
org.kde.pim.akonadictl:done.
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Starting up the Akonadi Server...
org.kde.pim.akonadiserver: Running DB initializer
tonal@hius2:~/lang/projects/promsoft/epool$ org.kde.pim.akonadiserver: DB
initializer done
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: Unable to connect to dbus service:  "An AppArmor
policy prevents this sender from sending this message to this recipient;
type=\"method_call\", sender=\":1.145\" (uid=1000 pid=413638
comm=\"/usr/bin/akonadiserver \" label=\"/usr/bin/akonadiserver (enforce)\")
interface=\"org.freedesktop.DBus\" member=\"RequestName\" error
name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.DBus\"
(bus)"
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadiserver' exited
normally...

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 5.19.0-41-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 31.2 ГиБ of RAM
Graphics Processor: NVIDIA GeForce 940MX/PCIe/SSE2
Manufacturer: Acer
Product Name: TravelMate P259-MG
System Version: V1.51

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

[neon] [Bug 456968] KDE Wallet Manager window is blank

2023-02-16 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=456968

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[neon] [Bug 399982] Crash Qt Designer after install Scintilla designer plugin

2022-12-01 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=399982

--- Comment #2 from Alexandr Zamaraev (aka Tonal)  ---
I could not reproduce this problem.

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

[plasmashell] [Bug 422111] Battery applet not showing up in tray.

2021-06-24 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=422111

--- Comment #50 from Alexandr Paliy  ---
Sorry for double-posting, I'll add some info.
When I say "icon is missing", ofc I mean that normally it would be shown (for
example, now I have like 70% of battery, and in tray settings it is set to be
always shown - but it is not, and it's also missing from "expanded" tray ("show
hidden icons")).

I've tried to set "Always show all entries" in systray's properties - I can see
everything except for battery :)

I don't know if that's still actual, but:
> David Edmundson 2020-06-29 14:40:55 UTC
> Can I see the output of:
> qdbus org.freedesktop.DBus /org/freedesktop/DBus 
> org.freedesktop.DBus.ListNames

Here it is:
https://gist.github.com/alexandrpaliy/06012b961bdb463ec3f488260ddba469

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

[plasmashell] [Bug 422111] Battery applet not showing up in tray.

2021-06-24 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=422111

Alexandr Paliy  changed:

   What|Removed |Added

 CC||alexandrpa...@gmail.com

--- Comment #49 from Alexandr Paliy  ---
Operating System: Gentoo Linux
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.10.45-gentoo (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

Happens to me too, but it's not consistently gone. Sometimes icon is present,
sometimes it's not. I did not make any "deep" tests, but it feels like icon is
missing after system went to sleep and woke up. After reboot icon [usually] is
present again.

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

[systemsettings] [Bug 438877] Does not start the application by shortcut

2021-06-18 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=438877

Alexandr  changed:

   What|Removed |Added

Summary|Does not start the  |Does not start the
   |application by hotkey   |application by shortcut

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

[systemsettings] [Bug 438877] New: Does not start the application by hotkey

2021-06-18 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=438877

Bug ID: 438877
   Summary: Does not start the application by hotkey
   Product: systemsettings
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_keys
  Assignee: plasma-b...@kde.org
  Reporter: alex.slugg...@yandex.com
CC: k...@david-redondo.de
  Target Milestone: ---

Does not start the application by hotkey

When appointing a hot key to start the application, if the .desktop-file
application is in /usr/share/applications, contains letters in the upper case
(as, for example, FBReader.desktop or org.qbittorrent.qBittorrent.desktop) -
the hot key will not work, because in kglobalshortcutsrc the names of these
files are added in the lower case and possibly due to the sensitivity to the
register does not start.

After renaming desktop files in the /usr/share/applications directory and bring
their names to the lower case (fbreader.desktop and
org.qbittorrent.qbittorrent.desktop), everything starts working. 


Linux/KDE Plasma: openSUSE Tumbleweed
(available in About System)
KDE Plasma Version: 5.81.0
KDE Frameworks Version: 5.81.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

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

[systemsettings] [Bug 434967] New: nftables support

2021-03-26 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=434967

Bug ID: 434967
   Summary: nftables support
   Product: systemsettings
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_firewall
  Assignee: plasma-b...@kde.org
  Reporter: be...@yandex.ru
CC: tcanabr...@kde.org
  Target Milestone: ---

Hello, I know firewalld can run on top of nftables, but personally I'd rather
manage nftables without firewalld. Thanks.

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

[plasmashell] [Bug 430390] Panel has black edge when compositor is disabled

2020-12-26 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=430390

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[plasmashell] [Bug 430591] New: Plasma crash on Wayland after install updates

2020-12-19 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=430591

Bug ID: 430591
   Summary: Plasma crash on Wayland after install updates
   Product: plasmashell
   Version: 5.20.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sasha01...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.20.4)

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.4.0-58-generic x86_64
Windowing system: Wayland
Distribution: KDE neon User Edition 5.20

-- Information about the crash:
- What I was doing when the application crashed:
I am installed latest updates and reboot

- Unusual behavior I noticed:
After logon: briefly saw desktop iconswithout panels, theneverything turned
black.

- Custom settings of the application:
- Time: show seconds
- Thame - default
Icons: Home, Trash, one SH file.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[New LWP 1367]
[New LWP 1490]
[New LWP 1495]
[New LWP 1496]
[New LWP 1497]
[New LWP 1498]
[New LWP 1537]
[New LWP 1540]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f4d1393baff in __GI___poll (fds=0x7ffd6adf0ba8, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f4d0fb9d3c0 (LWP 1339))]

Thread 9 (Thread 0x7f4ceaffd700 (LWP 1540)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x7f4d08019224) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f4d080191d0,
cond=0x7f4d080191f8) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x7f4d080191f8, mutex=0x7f4d080191d0) at
pthread_cond_wait.c:638
#3  0x7f4d13cced1b in QWaitConditionPrivate::wait (deadline=...,
this=0x7f4d080191d0) at thread/qwaitcondition_unix.cpp:146
#4  QWaitCondition::wait (this=, mutex=0x7f4d0800ec50,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#5  0x7f4d15a68814 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f4d15a68c89 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f4d13cc8bac in QThreadPrivate::start (arg=0x7f4d0800ebb0) at
thread/qthread_unix.cpp:329
#8  0x7f4d12d2d609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f4d13948293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f4ceb7fe700 (LWP 1537)):
#0  0x7f4d162b4aaa in _dl_update_slotinfo (req_modid=1) at
../elf/dl-tls.c:625
#1  0x7f4d162b4cac in update_get_addr (ti=0x7f4d1414a588) at
../elf/dl-tls.c:799
#2  0x7f4d162bad4c in __tls_get_addr () at
../sysdeps/x86_64/tls_get_addr.S:55
#3  0x7f4d13cc807a in get_thread_data () at thread/qthread_unix.cpp:207
#4  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:207
#5  0x7f4d13f08e8e in postEventSourcePrepare (s=0x7f4cdc010cb0,
timeout=0x7f4ceb7fdad4) at kernel/qeventdispatcher_glib.cpp:253
#6  0x7f4d1226c72f in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f4d1226d0db in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f4d1226d2e3 in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f4d13f08fbb in QEventDispatcherGlib::processEvents
(this=0x7f4cdc00e920, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#10 0x7f4d13ead1ab in QEventLoop::exec (this=this@entry=0x7f4ceb7fdca0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#11 0x7f4d13cc7a12 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#12 0x7f4d159a338a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f4d13cc8bac in QThreadPrivate::start (arg=0x5619bfa9d220) at
thread/qthread_unix.cpp:329
#14 0x7f4d12d2d609 in start_thread (arg=) at
pthread_create.c:477
#15 0x7f4d13948293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f4cebfff700 (LWP 1498)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5619bf4ed968) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5619bf4ed918,
cond=0x5619bf4ed940) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5619bf4ed940, mutex=0x5619bf4ed918) at
pthread_cond_wait.c:638
#3  0x7f4d04a4e62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#4  0x7f4d04a4e23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
#5  0x7f4d12d2d609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f4d13948293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f4cfa969700 (LWP 1497)):
#0  

[kio-extras] [Bug 345047] fish:// kioslave doesn't work if target doesn't have perl installed

2020-10-19 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=345047

--- Comment #2 from Alexandr Akulich  ---
The issue is reproducible with postmarketOS.
I proposed the fix at
https://invent.kde.org/network/kio-extras/-/merge_requests/44

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

[kio-extras] [Bug 345047] fish:// kioslave doesn't work if target doesn't have perl installed

2020-10-19 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=345047

Alexandr Akulich  changed:

   What|Removed |Added

 CC||akulichalexan...@gmail.com
 Status|REPORTED|CONFIRMED
   Assignee|trou...@garni.ch|akulichalexan...@gmail.com
 Ever confirmed|0   |1

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

[Falkon] [Bug 424655] Falkon crashed on start

2020-07-25 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=424655

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
Aftre computer restart all work.

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

[Falkon] [Bug 424655] New: Falkon crashed on start

2020-07-25 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=424655

Bug ID: 424655
   Summary: Falkon crashed on start
   Product: Falkon
   Version: 3.1.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: tonal.proms...@gmail.com
  Target Milestone: ---

Application: falkon (3.1.0)

Qt Version: 5.14.2
Frameworks Version: 5.72.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
- What I was doing when the application crashed:
A start Falkon.
Falkon crashed

Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.14.2
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 31.2 ГиБ of RAM

The crash can be reproduced every time.

-- Backtrace:
Application: Falkon (falkon), signal: Aborted

[KCrash Handler]
#4  0x7f232e064f47 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:51
#5  0x7f232e0668b1 in __GI_abort () at abort.c:79
#6  0x55a61eb85b48 in msgHandler(QtMsgType, QMessageLogContext const&,
QString const&) (type=, context=..., msg=...) at
./src/main/main.cpp:116
#7  0x7f232e8485d0 in qt_message_print (message=..., context=...,
msgType=QtFatalMsg) at global/qlogging.cpp:1843
#8  0x7f232e8485d0 in qt_message(QtMsgType, const QMessageLogContext &,
const char *, typedef __va_list_tag __va_list_tag *)
(msgType=msgType@entry=QtFatalMsg, context=..., msg=msg@entry=0x7f232d71ab6f
"%s", ap=ap@entry=0x7ffd77095f90) at global/qlogging.cpp:378
#9  0x7f232e82e672 in QMessageLogger::fatal(char const*, ...) const
(this=this@entry=0x7ffd770960a0, msg=msg@entry=0x7f232d71ab6f "%s") at
global/qlogging.cpp:890
#10 0x7f232d716cc0 in
QQuickWidgetPrivate::handleContextCreationFailure(QSurfaceFormat const&, bool)
(this=this@entry=0x55a61f66a630, format=..., isEs=isEs@entry=false) at
qquickwidget.cpp:869
#11 0x7f232d717020 in QQuickWidgetPrivate::createContext()
(this=this@entry=0x55a61f66a630) at qquickwidget.cpp:902
#12 0x7f232d71917e in QQuickWidget::resizeEvent(QResizeEvent*)
(this=0x55a61f867d70, e=) at qquickwidget.cpp:1244
#13 0x7f232de12919 in
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::resizeEvent(QResizeEvent*)
() at /usr/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#14 0x7f232f0b7bde in QWidget::event(QEvent*)
(this=this@entry=0x55a61f867d70, event=event@entry=0x7ffd77096670) at
kernel/qwidget.cpp:8823
#15 0x7f232d719ecb in QQuickWidget::event(QEvent*) (this=0x55a61f867d70,
e=0x7ffd77096670) at qquickwidget.cpp:1551
#16 0x7f232de12c40 in
QtWebEngineCore::RenderWidgetHostViewQtDelegateWidget::event(QEvent*) () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineWidgets.so.5
#17 0x7f232f0769ac in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=this@entry=0x55a61f0fdb00, receiver=receiver@entry=0x55a61f867d70,
e=e@entry=0x7ffd77096670) at kernel/qapplication.cpp:3685
#18 0x7f232f07dbb0 in QApplication::notify(QObject*, QEvent*)
(this=0x7ffd77097860, receiver=0x55a61f867d70, e=0x7ffd77096670) at
kernel/qapplication.cpp:3431
#19 0x7f232ea424a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x55a61f867d70, event=0x7ffd77096670) at
kernel/qcoreapplication.cpp:1075
#20 0x7f232ea4267e in QCoreApplication::sendEvent(QObject*, QEvent*)
(receiver=receiver@entry=0x55a61f867d70, event=event@entry=0x7ffd77096670) at
kernel/qcoreapplication.cpp:1470
#21 0x7f232f0aff76 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool,
bool) (this=this@entry=0x55a61f66a630, recursive=recursive@entry=false,
disableUpdates=, disableUpdates@entry=false) at
kernel/qwidget.cpp:7727
#22 0x7f232f0b4303 in QWidgetPrivate::show_helper()
(this=this@entry=0x55a61f66a630) at kernel/qwidget.cpp:7778
#23 0x7f232f0b7453 in QWidgetPrivate::setVisible(bool)
(this=0x55a61f66a630, visible=) at kernel/qwidget.cpp:8127
#24 0x7f23260200bd in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#25 0x7f2326023b1e in
QtWebEngineCore::WebContentsAdapter::load(QWebEngineHttpRequest const&) () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#26 0x7f232fa2a9af in WebView::loadRequest(LoadRequest const&)
(this=0x55a61f6be370, this@entry=0x7ffd770967b0, req=...) at
./src/lib/webengine/webview.cpp:1267
#27 0x7f232fa2ab2f in WebView::load(LoadRequest const&)
(this=0x7ffd770967b0, request=...) at ./src/lib/webengine/webview.cpp:211
#28 0x7f232f9ea125 in TabWidget::addView(LoadRequest const&, QString
const&, QFlags const&, bool, int, bool)
(this=this@entry=0x55a61f461940, req=..., title=..., openFlags=...,

[krunner] [Bug 424179] Crash KRunner while typed

2020-07-14 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=424179

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

Summary|Crash KRuhher while typed   |Crash KRunner while typed

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

[krunner] [Bug 424179] Crash KRuhher while typed

2020-07-14 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=424179

--- Comment #3 from Alexandr Zamaraev (aka Tonal)  ---
(In reply to Alexander Lohnau from comment #1)
> The plugin should be called "Instant Messaging", does disabling it fix the
> crash?
> 
> This is not reproducible on KDE Neon Unstable, but I will look into it!

Yes! Worked!

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

[krunner] [Bug 424179] New: Crash KRuhher while typed

2020-07-13 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=424179

Bug ID: 424179
   Summary: Crash KRuhher while typed
   Product: krunner
   Version: 5.19.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: tonal.proms...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: krunner (5.19.3)

Qt Version: 5.14.2
Frameworks Version: 5.72.0
Operating System: Linux 5.3.0-62-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
- What I was doing when the application crashed:
Launched KRunner, started typing. This started with the latest updates of neon
stable. Unfortunately it's fully reproducable.

The crash can be reproduced every time.

-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault

[KCrash Handler]
#4  0x in ?? ()
#5  0x7f350fbed0f4 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/krunner_ktp_contacts.so
#6  0x7f3542cf44b9 in doActivate (sender=0x56302b538ae0,
signal_index=3, argv=0x7ffda714e690) at kernel/qobject.cpp:3882
#7  0x7f3542ceef92 in QMetaObject::activate
(sender=sender@entry=0x56302b538ae0, m=m@entry=0x7f351bffe6a0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at
kernel/qobject.cpp:3930
#8  0x7f351bdd4ce0 in Plasma::AbstractRunner::prepare
(this=this@entry=0x56302b538ae0) at
./obj-x86_64-linux-gnu/src/KF5Runner_autogen/include/moc_abstractrunner.cpp:225
#9  0x7f351bdf3aa8 in Plasma::RunnerManagerPrivate::loadInstalledRunner
(this=this@entry=0x56302ada5bc0, pluginMetaData=...) at
./src/runnermanager.cpp:401
#10 0x7f351bdf4f9b in Plasma::RunnerManagerPrivate::loadRunners
(this=0x56302ada5bc0) at ./src/runnermanager.cpp:270
#11 0x7f351bdf162d in Plasma::RunnerManager::launchQuery
(this=0x56302adf3700, untrimmedTerm=..., runnerName=...) at
./src/runnermanager.cpp:913
#12 0x7f351bdf17a7 in Plasma::RunnerManager::launchQuery (this=, term=...) at ./src/runnermanager.cpp:883
#13 0x7f35202c296d in Milou::RunnerResultsModel::setQueryString
(this=0x56302b07da50, queryString=...) at ./lib/runnerresultsmodel.cpp:194
#14 0x7f35202bf32d in Milou::ResultsModel::setQueryString (this=, queryString=...) at ./lib/resultsmodel.cpp:370
#15 0x7f35202ccc6a in Milou::ResultsModel::qt_static_metacall
(_o=, _c=, _id=, _a=) at
./obj-x86_64-linux-gnu/lib/milou_autogen/EWIEGA46WW/moc_resultsmodel.cpp:228
#16 0x7f3545ab8d1f in QQmlPropertyData::writeProperty (flags=...,
value=0x7ffda714ea98, target=, this=) at
../../include/QtQml/5.14.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertydata_p.h:286
#17 GenericBinding<10>::doStore (flags=..., pd=,
value=..., this=0x56302b0696f0) at qml/qqmlbinding.cpp:334
#18 GenericBinding<10>::write (this=0x56302b0696f0, result=...,
isUndefined=, flags=...) at qml/qqmlbinding.cpp:315
#19 0x7f3545ab944a in QQmlNonbindingBinding::doUpdate (this=0x56302b0696f0,
watcher=..., flags=..., scope=...) at qml/qqmlbinding.cpp:250
#20 0x7f3545ab6032 in QQmlBinding::update (this=0x56302b0696f0, flags=...)
at qml/qqmlbinding.cpp:186
#21 0x7f3545a8f322 in QQmlNotifier::emitNotify (endpoint=,
a=a@entry=0x0) at qml/qqmlnotifier.cpp:104
#22 0x7f3545a3d119 in QQmlData::signalEmitted (object=0x56302adacbd0,
index=, a=0x0) at qml/qqmlengine.cpp:858
#23 0x7f3542cf4314 in doActivate (sender=0x56302adacbd0,
signal_index=32, argv=0x0) at kernel/qobject.cpp:3762
#24 0x7f3545a38851 in QQmlVMEMetaObject::metaCall (this=0x56302adea5d0,
o=, c=, _id=, a=)
at qml/qqmlvmemetaobject.cpp:782
#25 0x7f354598085d in QV4::QObjectWrapper::setProperty
(engine=engine@entry=0x56302ae82dd0, object=object@entry=0x56302adacbd0,
property=0x7f351c205758, value=...) at jsruntime/qv4qobjectwrapper.cpp:542
#26 0x7f3545980b4e in QV4::QObjectWrapper::setQmlProperty
(engine=0x56302ae82dd0, qmlContext=, object=0x56302adacbd0,
name=, revisionMode=QV4::QObjectWrapper::IgnoreRevision,
value=...) at jsruntime/qv4qobjectwrapper.cpp:435
#27 0x7f3545980c9b in QV4::QObjectWrapper::virtualPut (m=0x7f35224ab560,
id=..., value=..., receiver=0x7f35224ab560) at
jsruntime/qv4qobjectwrapper.cpp:721
#28 0x7f35459468a9 in QV4::Object::put (receiver=0x7f35224ab560, v=...,
id=..., this=0x7f35224ab560) at jsruntime/qv4object_p.h:324
#29 QV4::Object::virtualResolveLookupSetter (object=0x7f35224ab560,
engine=0x56302ae82dd0, lookup=0x56302b1259c0, value=...) at
jsruntime/qv4object.cpp:804
#30 0x7f354578 in QV4::Moth::VME::interpret (frame=0x7ffda7150b40,
engine=0x56302ae82dd0, code=0x7f3521c96eff ".FM|") at
jsruntime/qv4vme_moth.cpp:653
#31 0x7f354599e686 in QV4::Moth::VME::exec
(frame=frame@entry=0x7ffda7150b40, engine=engine@entry=0x56302ae82dd0) at
jsruntime/qv4vme_moth.cpp:463
#32 

[systemsettings] [Bug 422014] New: error

2020-05-24 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=422014

Bug ID: 422014
   Summary: error
   Product: systemsettings
   Version: 5.8.8
  Platform: Mint (Ubuntu based)
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: axelf174...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.8)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.10.0-38-generic x86_64
Distribution: Linux Mint 18.3 Sylvia

-- Information about the crash:
- What I was doing when the application crashed:
I clicked on the "workspace design" application. Each time you clicked, an
error

The crash can be reproduced every time.

-- Backtrace:
Application: Параметры системы (systemsettings5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6fc21d1900 (LWP 18590))]

Thread 4 (Thread 0x7f6f9b681700 (LWP 18596)):
#0  0x7f6fbe87d74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fbb55f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6fbb55f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6fbf1a537b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6fbf14dffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fbef769e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6fbd8d06b5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7f6fbef7b808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6fbba806ba in start_thread (arg=0x7f6f9b681700) at
pthread_create.c:333
#9  0x7f6fbe88941d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f6fa6ffb700 (LWP 18594)):
#0  0x7f6fbe87d74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fbb55f38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f6fbb55f49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f6fbf1a537b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f6fbf14dffa in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fbef769e4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f6fc2326515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x7f6fbef7b808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f6fbba806ba in start_thread (arg=0x7f6fa6ffb700) at
pthread_create.c:333
#9  0x7f6fbe88941d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f6faf8c4700 (LWP 18592)):
#0  0x7f6fbe87d74d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f6fbc2f6c62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f6fbc2f88d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f6fb244cd29 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f6fbef7b808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f6fbba806ba in start_thread (arg=0x7f6faf8c4700) at
pthread_create.c:333
#6  0x7f6fbe88941d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f6fc21d1900 (LWP 18590)):
[KCrash Handler]
#6  0x7f6fbe7b7428 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f6fbe7b902a in __GI_abort () at abort.c:89
#8  0x7f6fbef62f41 in QMessageLogger::fatal(char const*, ...) const () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f6fc2304457 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#10 0x7f6fc23047aa in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#11 0x7f6fc2305695 in QQuickWidget::resizeEvent(QResizeEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5QuickWidgets.so.5
#12 0x7f6fc06c62ee in QWidget::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x7f6fc0680afc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x7f6fc0686036 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x7f6fbf1502a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x7f6fc06beca2 in QWidgetPrivate::sendPendingMoveAndResizeEvents(bool,
bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#17 0x7f6fc06c2a43 in QWidgetPrivate::show_helper() () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#18 0x7f6fc06c587d in QWidget::setVisible(bool) () from

[Akonadi] [Bug 402680] akonadiserver do not start

2020-03-27 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=402680

--- Comment #2 from Alexandr Zamaraev (aka Tonal)  ---
see also https://bugs.kde.org/show_bug.cgi?id=411093

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

[kdeconnect] [Bug 405207] KDE connect daemon always crashes

2020-03-23 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=405207

Alexandr  changed:

   What|Removed |Added

 CC||skater2...@mail.ru

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

[kwin] [Bug 416203] New: KWin crashed after google chrome user was switched

2020-01-13 Thread Alexandr Myshanskiy
https://bugs.kde.org/show_bug.cgi?id=416203

Bug ID: 416203
   Summary: KWin crashed after google chrome user was switched
   Product: kwin
   Version: 5.17.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: myshanskii.al...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.17.4)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 5.4.8-200.fc31.x86_64 x86_64
Distribution: Fedora 31 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
I opened Google Chrome and switched active users. After that, the interface was
hung and did not respond to mouse and keyboard clicks.
I switched to tty2 and killed plasma-desktop processes restarted the desktop
interface.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f784b539940 (LWP 1474))]

Thread 7 (Thread 0x7f77a1a03700 (LWP 2970)):
#0  0x7f7852530e33 in __libc_enable_asynccancel () from /lib64/libc.so.6
#1  0x7f78525a0b44 in ppoll () from /lib64/libc.so.6
#2  0x7f78510e6d29 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#3  0x7f78510e7f71 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f785109424b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f7850ee4c75 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f7850ee5dc6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f785044e4e2 in start_thread () from /lib64/libpthread.so.0
#8  0x7f78525ab693 in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f78375ef700 (LWP 1988)):
#0  0x7ffd709f6933 in clock_gettime ()
#1  0x7f78525726ab in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6
#2  0x7f78510ea0a5 in qt_gettime() () from /lib64/libQt5Core.so.5
#3  0x7f78510e8bed in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#4  0x7f78510e8ff9 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#5  0x7f78510e8164 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f785109424b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f7850ee4c75 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f784fb7f399 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#9  0x7f7850ee5dc6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 0x7f785044e4e2 in start_thread () from /lib64/libpthread.so.0
#11 0x7f78525ab693 in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f7835dad700 (LWP 1592)):
#0  0x7f7850454d45 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f78509d374a in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f78509d376f in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f785044e4e2 in start_thread () from /lib64/libpthread.so.0
#4  0x7f78525ab693 in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f7836dee700 (LWP 1586)):
#0  0x7f78525a0b66 in ppoll () from /lib64/libc.so.6
#1  0x7f78510e6d29 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#2  0x7f78510e7f71 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7f785109424b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7f7850ee4c75 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7f784fb7f399 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#6  0x7f7850ee5dc6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f785044e4e2 in start_thread () from /lib64/libpthread.so.0
#8  0x7f78525ab693 in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f783d585700 (LWP 1558)):
#0  0x7ffd709f6933 in clock_gettime ()
#1  0x7f78525726ab in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6
#2  0x7f78510ea0a5 in qt_gettime() () from /lib64/libQt5Core.so.5
#3  0x7f78510e8bed in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#4  0x7f78510e8ff9 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#5  0x7f78510e8164 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#6  0x7f785109424b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#7  0x7f7850ee4c75 in QThread::exec() () from /lib64/libQt5Core.so.5
#8  0x7f784f4d7f6a in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#9  0x7f7850ee5dc6 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#10 

[neon] [Bug 399346] Can not start Akonadi

2019-12-10 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=399346

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[neon] [Bug 411093] Unable to start Akonadi: Could not open required defaults file

2019-12-10 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=411093

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[plasmashell] [Bug 414920] New: Plasma freeze and crash while searching

2019-12-07 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=414920

Bug ID: 414920
   Summary: Plasma freeze and crash while searching
   Product: plasmashell
   Version: 5.17.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sasha01...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.4)

Qt Version: 5.13.2
Frameworks Version: 5.64.0
Operating System: Linux 5.0.0-37-generic x86_64
Distribution: KDE neon User Edition 5.17

-- Information about the crash:
- What I was doing when the application crashed:
1) I minimized the VmWare Workstation Pro 15.5 virtual machine from full screen
mode
2) Opened the widget "Application Launch Menu"
3) Started typing “muon” (But only “mu” was entered)
After that, the environment freezes.
To restore performance, I deployed and rolled back the VM.
The second time the search works.

- Unusual behavior I noticed:
You cannot enter anything else into the search or use the application launcher
menu or taskbar in any way.
It helped me move the mouse to the upper left corner to view open windows.

- Custom settings of the application:
Locale ru-RU_UTF-8
Modern application launcher menu
Time: show seconds
Taskbar (with icons and window names)
Calculator witget on panel

Touchscreen connected and not used on this test

The crash can be reproduced sometimes.

-- Backtrace (Reduced):
#7  0x7fe5bfbb3af0 in QQmlPropertyCache::callJSFactoryMethod
(args=0x7ffcf656ab90, object=0x562cc13f1900, this=0x7fe58c008bf0) at
../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/qml/qqmlpropertycache_p.h:875
#8  QV4::QObjectWrapper::create (engine=,
engine@entry=0x562cbe04b2b0, object=object@entry=0x562cc13f1900) at
jsruntime/qv4qobjectwrapper.cpp:691
#9  0x7fe5bfbb5e49 in QV4::QObjectWrapper::wrap_slowPath
(engine=0x562cbe04b2b0, object=0x562cc13f1900) at
jsruntime/qv4qobjectwrapper.cpp:623
#10 0x7fe5bfb941cb in QV4::QObjectWrapper::wrap
(engine=engine@entry=0x562cbe04b2b0, object=) at
../../include/QtQml/5.13.2/QtQml/private/../../../../../src/qml/jsruntime/qv4qobjectwrapper_p.h:224
#11 0x7fe5bfc3204c in QV4::ExecutionEngine::fromVariant
(this=this@entry=0x562cbe04b2b0, variant=...) at jsruntime/qv4engine.cpp:1524


The reporter indicates this bug may be a duplicate of or related to bug 413170.

Possible duplicates by query: bug 413170, bug 371268, bug 361513, bug 357590,
bug 356719.

Reported using DrKonqi

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

[plasmashell] [Bug 414920] Plasma freeze and crash while searching

2019-12-07 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=414920

--- Comment #1 from Alexandr  ---
Created attachment 124356
  --> https://bugs.kde.org/attachment.cgi?id=124356=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[telepathy] [Bug 406676] ktp-call-ui depends on unmaintained qt-gstreamer

2019-07-06 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=406676

--- Comment #2 from Alexandr Akulich  ---
Created attachment 121357
  --> https://bugs.kde.org/attachment.cgi?id=121357=edit
Patch for qt-gstreamer

Hi folks. I just found out this issue.
Recently I became a KDE Telepathy maintainer and though I'm not active here
(I'm busy with the underlying stuff), I'm kindly asking you to keep the project
in your repos for a bit longer.

The compilation error is caused by commit
https://gitlab.freedesktop.org/gstreamer/gstreamer/commit/b27ee943c2a44a5437a5343d21a9d2be918a1279

This commit introduces a brute C-style cast that prevents a compiler from
proper C++ casting. The workaround is trivial:

src/QGst/caps.cpp:57

 void Caps::append(const CapsPtr & caps2)
 {
-gst_caps_append(object(), gst_caps_copy(caps2));
+const GstCaps * caps2ptr = caps2;
+gst_caps_append(object(), gst_caps_copy(caps2ptr));
 }

I'll try to reach the last qt-gstreamer maintainer to upstream the fix.

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

[konsole] [Bug 407076] Shortcuts for profiles triggering the wrong action

2019-06-02 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=407076

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=408217

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

[konsole] [Bug 408217] Konsole switch profile from gui only change termial theme but not excute the customed command

2019-06-02 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=408217

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

   See Also||https://bugs.kde.org/show_b
   ||ug.cgi?id=407076

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

[konsole] [Bug 407076] Shortcuts for profiles triggering the wrong action

2019-06-02 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=407076

--- Comment #2 from Alexandr Zamaraev (aka Tonal)  ---
see also https://bugs.kde.org/show_bug.cgi?id=408217

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

[konsole] [Bug 408217] Konsole switch profile from gui only change termial theme but not excute the customed command

2019-06-02 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=408217

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
see also https://bugs.kde.org/show_bug.cgi?id=407076

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

[konsole] [Bug 407076] Shortcuts for profiles triggering the wrong action

2019-06-02 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=407076

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[okular] [Bug 283477] Missing language specific characters when filling in forms

2019-05-23 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=283477

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

--- Comment #16 from Alexandr Zamaraev (aka Tonal)  
---
see https://gitlab.freedesktop.org/poppler/poppler/issues/463
and https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1288182

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

[okular] [Bug 401067] Fillable form fields in Okular may show up as "undefined"

2019-05-23 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=401067

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
see https://gitlab.freedesktop.org/poppler/poppler/issues/463
and https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1288182

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

[okular] [Bug 403632] Cannot handle some fields in PDF forms.

2019-05-23 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=403632

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

--- Comment #3 from Alexandr Zamaraev (aka Tonal)  ---
see https://gitlab.freedesktop.org/poppler/poppler/issues/463
and https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1288182

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

[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block

2019-04-29 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=407060

--- Comment #1 from Alexandr Zamaraev (aka Tonal)  ---
Comment spec: https://yaml.org/spec/1.2/spec.html#id2780069

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

[frameworks-syntax-highlighting] [Bug 407060] New: incorrect YAML highlighted some text block

2019-04-29 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=407060

Bug ID: 407060
   Summary: incorrect YAML highlighted some text block
   Product: frameworks-syntax-highlighting
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: syntax
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: tonal.proms...@gmail.com
  Target Milestone: ---

SUMMARY
Incorrect highlighted text as comment
Break highlighting in double quote inside text block

STEPS TO REPRODUCE
1. Paste this fragment to Kate:

7:
  domain: example.org
  reg_list:
  - reg: ?#XPath //div[@class="product_item cf"][@id] ))(?sx)
  id="product(?P[^"]+)"
  .+?]+>(?P[^<]+)
  .+?>(?:(?P[^<]+)|\s*)
  .+?(?:new|usual)Price">(?:(?P[\d\s,.]*\d)(?:)?|]*>по\s+ запросу)
  - reg: ?#XPath //div[@class="product_item cf"][not(@id)] ))(?sx)
  \s*]+>(?P[^<]+)
  .+?
  .+?(?:(?P[^<]+)|\s*)
 
.+?(?:new|usual)Price">\s*(?:(?P[\d\s,.]+\d)\s*rur)">|]+>\s*по\s+
запросу)
  - reg: ?#XPath //div[@class="second_column left"]
))"name"\scontent="(?P[^<]+)">[\s\S]+?Артикул:\s(?P[^<]+)[\s\S]+?Price">(?P[\d\s,.]+)[\s\S]+?id="spinner(?P[^"]+)"


OBSERVED RESULT
Incorrect highlighted comment after '?'
Break highlighting in double quote inside text block

EXPECTED RESULT
3 key "reg". Values - text block without comments.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.15
KDE Plasma Version: 5.15.4
KDE Frameworks Version: 5.57.0
Qt Version: 5.12.0
Kernel Version: 4.15.0-48-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz
Memory: 19,5 ГиБ

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

[dolphin] [Bug 407019] New: Dolphin crashed while copying files from PC to phone

2019-04-28 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=407019

Bug ID: 407019
   Summary: Dolphin crashed while copying files from PC to phone
   Product: dolphin
   Version: 17.12.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: wumianzh...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (17.12.3)

Qt Version: 5.9.5
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-47-generic x86_64
Distribution: Ubuntu 18.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was copying files of different types (mp3 and png) to internal storage of
phone connected with USB, crash happened after some time of programm doing
nothing. Have not retried yet. As side effect dolphin does not seem to detect
folder into which files were copied.

-- 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 0x7f233e68f6c0 (LWP 27197))]

Thread 5 (Thread 0x7f230f98b700 (LWP 27202)):
#0  0x7f233df0dbf9 in __GI___poll (fds=0x7f23080049b0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f2330e69539 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f2330e6964c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f23381219bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f23380c6a1a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f2337ee523a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2337eea17d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f2332fda6db in start_thread (arg=0x7f230f98b700) at
pthread_create.c:463
#8  0x7f233df1a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7f2317fff700 (LWP 27201)):
#0  0x7f2332fe09f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55ff4dc7fdd8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f2332fe09f3 in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55ff4dc7fd88, cond=0x55ff4dc7fdb0) at pthread_cond_wait.c:502
#2  0x7f2332fe09f3 in __pthread_cond_wait (cond=0x55ff4dc7fdb0,
mutex=0x55ff4dc7fd88) at pthread_cond_wait.c:655
#3  0x7f231d881dcb in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7f231d881af7 in  () at /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7f2332fda6db in start_thread (arg=0x7f2317fff700) at
pthread_create.c:463
#6  0x7f233df1a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7f231700 (LWP 27200)):
#0  0x7ffe78fd9a40 in clock_gettime ()
#1  0x7f233df29ea6 in __GI___clock_gettime (clock_id=1, tp=0x7f231fffeae0)
at ../sysdeps/unix/clock_gettime.c:115
#2  0x7f23381212d1 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f233811fb09 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f23381200e5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f233812172e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f2330e68a98 in g_main_context_prepare () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f2330e6946b in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7f2330e6964c in g_main_context_iteration () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f23381219bb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f23380c6a1a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f2337ee523a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f233859ed45 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7f2337eea17d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f2332fda6db in start_thread (arg=0x7f231700) at
pthread_create.c:463
#15 0x7f233df1a88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7f2326e64700 (LWP 27199)):
#0  0x7f233df0dbf9 in __GI___poll (fds=0x7f2326e63ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f23307aa747 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f23307ac36a in xcb_wait_for_event () at
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f2329c112a9 in  () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7f2337eea17d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f2332fda6db in start_thread (arg=0x7f2326e64700) at
pthread_create.c:463
#6  0x7f233df1a88f in clone 

[Akonadi] [Bug 374636] akonadi does not start after restore

2019-03-14 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=374636

--- Comment #4 from Alexandr Zamaraev (aka Tonal)  ---
see also https://bugs.kde.org/show_bug.cgi?id=402680

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

[Akonadi] [Bug 374636] akonadi does not start after restore

2019-03-14 Thread Alexandr Zamaraev
https://bugs.kde.org/show_bug.cgi?id=374636

Alexandr Zamaraev (aka Tonal)  changed:

   What|Removed |Added

 CC||tonal.proms...@gmail.com

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

[telepathy] [Bug 399352] text-ui crashes on start

2019-03-04 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=399352

Alexandr Akulich  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 Status|REPORTED|NEEDSINFO
 CC||akulichalexan...@gmail.com

--- Comment #1 from Alexandr Akulich  ---
Hi Konstantin,

please provide the needed information, e.g. software versions, distro, and
video driver.

Personally, I have crashes and freezes on nouveau video driver because of the
used WebEngine view, but such issue is not related to KTp.

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

[telepathy] [Bug 404350] Choosing "offline" status does not disconnect accounts

2019-03-03 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=404350

Alexandr Akulich  changed:

   What|Removed |Added

   Version Fixed In||18.12.3

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

[telepathy] [Bug 384968] Only first 10 links in a message shown properly, additional links become copies of the 2nd link

2019-03-03 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=384968

Alexandr Akulich  changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||18.12.3
  Latest Commit||https://commits.kde.org/ktp
   ||-common-internals/5c77cc29d
   ||b5966a7ef227f20da8d54a264f2
   ||8746
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Alexandr Akulich  ---
Git commit 5c77cc29db5966a7ef227f20da8d54a264f28746 by Alexander Akulich.
Committed on 03/03/2019 at 22:45.
Pushed by akulichalexandr into branch 'Applications/18.12'.

Fix escape/url filter URL placeholder backward substitution

The placeholder ends with a decimal URL index. The substitution is an
incremental pass from zero index, so when the placeholder is substituted
back to URL the replacing code matches incomplete index and we got a
messed URLs.

(Replace of `#K#T#P1` messes up `#K#T#P10` and `#K#T#P11`)

Add a end marker to the placeholder scheme to never mess URL.
FIXED-IN: 18.12.3

Differential Revision: https://phabricator.kde.org/D19477

M  +1-1KTp/message-escape-filter.cpp

https://commits.kde.org/ktp-common-internals/5c77cc29db5966a7ef227f20da8d54a264f28746

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

[telepathy] [Bug 404350] Choosing "offline" status does not disconnect accounts

2019-03-03 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=404350

Alexandr Akulich  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED
  Latest Commit||https://commits.kde.org/ktp
   ||-contact-list/6dcdbdc872c2d
   ||8fb8e7838dcf5880c5b27b93c47

--- Comment #5 from Alexandr Akulich  ---
Git commit 6dcdbdc872c2d8fb8e7838dcf5880c5b27b93c47 by Alexander Akulich, on
behalf of Alexander Blinne.
Committed on 03/03/2019 at 22:43.
Pushed by akulichalexandr into branch 'Applications/18.12'.

Restore the "Offline" option in presence combobox

There is no valid reason to show the option but do nothing on activated.

Reviewed By: akulichalexander

M  +1-1global-presence-chooser.cpp

https://commits.kde.org/ktp-contact-list/6dcdbdc872c2d8fb8e7838dcf5880c5b27b93c47

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

[telepathy] [Bug 404350] Choosing "offline" status does not disconnect accounts

2019-03-02 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=404350

--- Comment #3 from Alexandr Akulich  ---
(In reply to Alexander Blinne from comment #0)
> Patch at https://phabricator.kde.org/differential/diff/51686/ fixes it most
> of the time, though in some cases (10-20% of times) it will go offline and
> go back online immediately afterwards. I can't find the reason for this
> right now...

I applied your patch and the Presence starts to work but it seems that there is
some race-condition so if I switch to online and quickly go back to offline
before a Connection Manager connected then it has some chance to report "I'm
connected" before it was told to stop trying.

Would you mind to submit the fix? This patch is a definitely the right thing to
do even if the issue still reproducible.

There is no other way to fix it and I'm hitting the issue on my own so I would
like to have your fix in 18.12.3 and we have literally one day to do that as
the release tag will be made at the Monday.
If you can't submit the patch today then I would like to commit it with you as
the author and me as a committer.

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

[telepathy] [Bug 404350] Choosing "offline" status does not disconnect accounts

2019-03-02 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=404350

Alexandr Akulich  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||akulichalexan...@gmail.com
 Status|REPORTED|CONFIRMED

--- Comment #1 from Alexandr Akulich  ---
Same here.
The patch looks good and the original code looks weird.
The return on ((index == count() - 3) introduced by
https://git.reviewboard.kde.org/r/130189/

What is the reason for the extra condition? (David, James?)

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

[telepathy] [Bug 373117] nothing is sent

2019-03-02 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=373117

Alexandr Akulich  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 CC||akulichalexan...@gmail.com
 Status|REPORTED|RESOLVED

--- Comment #1 from Alexandr Akulich  ---
The bug report has no details e.g. what is the connection manager in use.

It could be an issue on any level of Telepathy but most probably there was
something with your CM.
I'm closing it 'as is', feel free to add more info and reopen if needed.

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

[telepathy] [Bug 384968] Only first 10 links in a message shown properly, additional links become copies of the 2nd link

2019-03-02 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=384968

Alexandr Akulich  changed:

   What|Removed |Added

   Assignee|kde-telepathy-b...@kde.org  |akulichalexan...@gmail.com

--- Comment #2 from Alexandr Akulich  ---
https://phabricator.kde.org/D19477

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

[telepathy] [Bug 384968] Only first 10 links in a message shown properly, additional links become copies of the 2nd link

2019-03-01 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=384968

Alexandr Akulich  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||akulichalexan...@gmail.com

--- Comment #1 from Alexandr Akulich  ---
Still reproducible on 18.12.1 (with telepathy-morse/Telegram).

I'll try to fix it :)

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

[kmines] [Bug 399658] Touchscreen integration

2018-10-16 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=399658

Alexandr  changed:

   What|Removed |Added

 CC||sasha01...@gmail.com

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

[kmines] [Bug 399658] New: Touchscreen integration

2018-10-11 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=399658

Bug ID: 399658
   Summary: Touchscreen integration
   Product: kmines
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: dim...@gmail.com
  Reporter: sasha01...@gmail.com
CC: kde-games-b...@kde.org
  Target Milestone: ---

SUMMARY
Add the ability to mark mines using the touch screen

STEPS TO REPRODUCE
1. I'm launched the game by touchscreen.
2. I clicked (finger) on a random cell.
3. Then I made a long press of a finger on the place where there should be a
mine.
4. I expected the cell to check the box, but it exploded.

OBSERVED RESULT


EXPECTED RESULT
Kmines is not adapted for the touch screen. With the help of the touch screen,
you can only open the cells, change the level and reset the game. It is
impossible to mark mines!

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.12.6
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION
My touchscreen is DELLP2418HT
This screen works correctly with other applications (Chrome, Okular)

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

[frameworks-kcmutils] [Bug 349631] There is no possibility to configure my touchscreen

2018-10-11 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=349631

Alexandr  changed:

   What|Removed |Added

 CC||sasha01...@gmail.com

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

[dolphin] [Bug 394191] Dolphin crashes while attmptong to rename file

2018-09-28 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394191

Alexandr  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|LATER   |FIXED

--- Comment #8 from Alexandr  ---
Thank for response to community. Turned out this bug was fixed in Dolphin
17.12.3

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

[Falkon] [Bug 394692] New: Falkon 3.0.1 AppImage not working in Linux Mint 18.3

2018-05-26 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394692

Bug ID: 394692
   Summary: Falkon 3.0.1 AppImage not working in Linux Mint 18.3
   Product: Falkon
   Version: unspecified
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: now...@gmail.com
  Reporter: nevidlovs...@yandex.ru
  Target Milestone: ---

./Falkon-3.0.1.AppImage 

** (falkon:2260): WARNING **: Couldn't connect to accessibility bus: Failed to
connect to socket /tmp/dbus-7AlFLjs8LV: Connection refused
QApplication: invalid style override passed, ignoring it.
Could not find QtWebEngineProcess
[2260:2260:0526/143944.638280:FATAL:zygote_host_impl_linux.cc(182)] Check
failed: ReceiveFixedMessage(fds[0], kZygoteBootMessage,
sizeof(kZygoteBootMessage), _pid). 
#0 0x7f8ee06540a5 
#1 0x7f8ee0669eca 
#2 0x7f8edfcacfc3 
#3 0x7f8edfcabc3b 
#4 0x7f8edfcac219 
#5 0x7f8edf8ef93a 
#6 0x7f8edf8f4e76 
#7 0x7f8edf412600 
#8 0x7f8edf413b25 
#9 0x7f8edf3a7a61 QtWebEngineCore::BrowserContextAdapter::defaultContext()
#10 0x7f8ee535d218 QWebEngineProfile::defaultProfile()
#11 0x7f8ee569de78 MainApplication::MainApplication()
#12 0x0040358d main
#13 0x7f8eda21c830 __libc_start_main
#14 0x004038d5 

Received signal 6
#0 0x7f8ee06540a5 
#1 0x7f8edf395141 
#2 0x7f8ee065443d 
#3 0x7f8eda2314b0 
#4 0x7f8eda231428 gsignal
#5 0x7f8eda23302a abort
#6 0x7f8ee0653dc5 
#7 0x7f8ee066a1ed 
#8 0x7f8edfcacfc3 
#9 0x7f8edfcabc3b 
#10 0x7f8edfcac219 
#11 0x7f8edf8ef93a 
#12 0x7f8edf8f4e76 
#13 0x7f8edf412600 
#14 0x7f8edf413b25 
#15 0x7f8edf3a7a61 QtWebEngineCore::BrowserContextAdapter::defaultContext()
#16 0x7f8ee535d218 QWebEngineProfile::defaultProfile()
#17 0x7f8ee569de78 MainApplication::MainApplication()
#18 0x0040358d main
#19 0x7f8eda21c830 __libc_start_main
#20 0x004038d5 
  r8: 7ffe3eb34680  r9: 7f8ee5ca1900 r10: 0008 r11:
0206
 r12: 7ffe3eb34450 r13: 00aa r14: 7ffe3eb34680 r15:
7ffe3eb34df0
  di: 08d4  si: 08d4  bp: 7f8edae66140  bx:
7ffe3eb34bd0
  dx: 0006  ax:   cx: 7f8eda231428  sp:
7ffe3eb342e8
  ip: 7f8eda231428 efl: 0206 cgf: 002b0033 erf:

 trp:  msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.

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

[dolphin] [Bug 394191] Dolphin crashes while attmptong to rename file

2018-05-15 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394191

Alexandr <scad.lunc...@gmail.com> changed:

   What|Removed |Added

 Resolution|LATER   |WAITINGFORINFO

--- Comment #6 from Alexandr <scad.lunc...@gmail.com> ---
That's ok for me.
Thank you for replying to my issue.
Doesn't expected someone notice this report.

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

[dolphin] [Bug 394191] Dolphin crashes while attmptong to rename file

2018-05-15 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394191

--- Comment #4 from Alexandr <scad.lunc...@gmail.com> ---
(In reply to Julian Schraner from comment #3)
> Thanks for the quick response! Ubuntu 18.04 LTS has already been released
> (https://blog.ubuntu.com/2018/04/27/breeze-through-ubuntu-desktop-18-04-lts-
> bionic-beaver), so you should be able to upgrade without switching to a
> developer branch :)
Yes, I read this.

My system tuned to receive only lts updates, so it doesn't see new releases.
And this is logical behavior, because of:
"Upgrades from 16.04 LTS will not be enabled until a few days after 18.04.1's
release expected in late July."
https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes

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

[dolphin] [Bug 394191] Dolphin crashes while attmptong to rename file

2018-05-15 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394191

--- Comment #2 from Alexandr <scad.lunc...@gmail.com> ---
Julian Schraner, the problem is I am on LTS brunch of ubuntu and waiting for
18.04 will be released. I know I can update via dev brunch, but afraid problems
with compatibility with my hardware and apps which I'm using to work.

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

[dolphin] [Bug 394191] New: Dolphin crashes while attmptong to rename file

2018-05-13 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=394191

Bug ID: 394191
   Summary: Dolphin crashes while attmptong to rename file
   Product: dolphin
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: scad.lunc...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

Application: dolphin (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.13.0-41-generic x86_64
Distribution: Ubuntu 16.04.4 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Just opened folder, clicked RMB on file, and selected "rename". 
Dolphin crashing before showing edit field.

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 0x7f432bac4900 (LWP 24846))]

Thread 3 (Thread 0x7f4306931700 (LWP 24851)):
#0  0x7f432b4d174d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f43218cf38c in g_main_context_iterate (priority=2147483647, n_fds=1,
fds=0x7f4313c0, timeout=, context=0x7f4309b0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:4135
#2  0x7f43218cf38c in g_main_context_iterate
(context=context@entry=0x7f4309b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3835
#3  0x7f43218cf49c in g_main_context_iteration (context=0x7f4309b0,
may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#4  0x7f43261e837b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f4326190ffa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f4325fb99e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f4325fbe808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f432245b6ba in start_thread (arg=0x7f4306931700) at
pthread_create.c:333
#9  0x7f432b4dd41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f430f2ec700 (LWP 24849)):
#0  0x7f432b4cd27d in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f431d6f3073 in  () at
/usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#2  0x7f43219126f0 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7f430f2eba80, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#3  0x7f43219126f0 in g_wakeup_acknowledge (wakeup=0x7f43100015b0) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gwakeup.c:210
#4  0x7f43218cee74 in g_main_context_check
(context=context@entry=0x7f43080009b0, max_priority=2147483647,
fds=fds@entry=0x7f43080118e0, n_fds=n_fds@entry=1) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3632
#5  0x7f43218cf330 in g_main_context_iterate
(context=context@entry=0x7f43080009b0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at
/build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3837
#6  0x7f43218cf49c in g_main_context_iteration (context=0x7f43080009b0,
may_block=1) at /build/glib2.0-prJhLS/glib2.0-2.48.2/./glib/gmain.c:3901
#7  0x7f43261e837b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f4326190ffa in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f4325fb99e4 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7f432bbaf515 in  () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#11 0x7f4325fbe808 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f432245b6ba in start_thread (arg=0x7f430f2ec700) at
pthread_create.c:333
#13 0x7f432b4dd41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f432bac4900 (LWP 24846)):
[KCrash Handler]
#6  0x7f432ba85607 in _dl_relocate_object (reloc_addr_arg=0x7f42f9c90720,
reloc=0x7f42f9c8b000, l_addr=139925635133440) at
../sysdeps/x86_64/dl-machine.h:518
#7  0x7f432ba85607 in _dl_relocate_object (skip_ifunc=0, lazy=0,
nrelative=, relsize=40872, reladdr=,
map=0x2d19550) at do-rel.h:112
#8  0x7f432ba85607 in _dl_relocate_object (scope=,
reloc_mode=reloc_mode@entry=1, consider_profiling=,
consider_profiling@entry=0) at dl-reloc.c:258
#9  0x7f432ba8e851 in dl_open_worker (a=a@entry=0x7ffecbae3b70) at
dl-open.c:435
#10 0x7f432ba89564 in _dl_catch_error
(objname=objname@entry=0x7ffecbae3b60,
errstring=errstring@entry=0x7ffecbae3b68,
mallocedp=mallocedp@entry=0x7ffecbae3b5f, operate=operate@entry=0x7f432ba8e4d0
, args=args@entry=0x7ffecbae3b70) at dl-error.c:187
#11 0x7f432ba8dda9 in _dl_open (file=0x2d18c28

[valgrind] [Bug 393036] New: arm: unhandled instruction: 0xEBAD 0x1BC7 (sub.w fp, sp, r7, lsl #7)

2018-04-12 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=393036

Bug ID: 393036
   Summary: arm: unhandled instruction: 0xEBAD 0x1BC7 (sub.w fp,
sp, r7, lsl #7)
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: akulichalexan...@gmail.com
  Target Milestone: ---

Created attachment 111968
  --> https://bugs.kde.org/attachment.cgi?id=111968=edit
The fix in a format for git am

I've got this failure on profiling of a QR code detector on armv7hl. The code
is generated by gcc-4.8.3.

The attached patch fixes the problem (analysis starts to work fine after the
change applied).

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

[Plasma Vault] [Bug 386200] Import Vault

2018-01-16 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=386200

Alexandr <be...@yandex.ru> changed:

   What|Removed |Added

 CC||be...@yandex.ru

--- Comment #3 from Alexandr <be...@yandex.ru> ---
The same for me. Also I can't change path to encrypted folder (for eazy using
with cloud)

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

[telepathy] [Bug 386647] After resuming from standby & reconnect, ktp-text-ui chat window and chat-plasmoid open

2017-11-10 Thread Alexandr Akulich
https://bugs.kde.org/show_bug.cgi?id=386647

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||akulichalexan...@gmail.com
 Ever confirmed|0   |1

--- Comment #3 from Alexandr Akulich <akulichalexan...@gmail.com> ---
The Bustle log shows that there are requests to ChannelDispatcher to
EnsureChannel with a preferred handler = TpQtRaH Telepathy client. The first
request wakes up CM, but at the time of TextChannel appearance, there is no
TpQtRaH client anymore, so the ChannelDispatcher decides to raise a default
handler, namely — ktp-text-ui.

After a discussion, it turns out that the TpQtRaH clients registered by the
Chat Plasmoid and the C++ place of registration is TelepathyQt PendingChannel
[1].

I think of the following options:
1) Change TpQt API to let the Chat Plasmoid to specify the PendingChannel
handler service name as the name of the plasmoid.
2) Change TpQt or Chat Plasmoid to "ask the ChannelDispatcher to wake up a
ConnectionManager and then ask the ConnectionManager directly to restore the
channel". In this way, we'll use [2] with your=true to suppress an automatic
handler invocation. Right now we use [3] with preferredHandler = .
2) Disable the offline account PendingChannel-related code in the Chat
Plasmoid. I have no idea how it will affect the Plasmoid functionality, but
maybe it does not make much sense to ask ChannelDispatcher to set some account
presence (to online).

[1]
https://github.com/TelepathyIM/telepathy-qt/blob/master/TelepathyQt/pending-channel.cpp#L193
[2]
https://telepathy.freedesktop.org/spec/Channel_Dispatcher.html#Method:EnsureChannel
[3]
https://telepathy.freedesktop.org/spec/Connection_Interface_Requests.html#Method:EnsureChannel

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

[valgrind] [Bug 381819] amd64: unhandled instruction bextr (0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4) from BMI1

2017-10-08 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=381819

Alexandr <mexahota...@w1l.ru> changed:

   What|Removed |Added

 CC||mexahota...@w1l.ru

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

[tellico] [Bug 382680] 3.0.2 release build fails with cmake 3.9

2017-08-01 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=382680

Alexandr <s...@sss.chaoslab.ru> changed:

   What|Removed |Added

 CC||s...@sss.chaoslab.ru

--- Comment #2 from Alexandr <s...@sss.chaoslab.ru> ---
same problem.
can help with testing.

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

[tellico] [Bug 382572] crash after few seconds on start

2017-07-31 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=382572

Alexandr <s...@sss.chaoslab.ru> changed:

   What|Removed |Added

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

--- Comment #3 from Alexandr <s...@sss.chaoslab.ru> ---
working in 1ca506a511a217efcc70ec458886298474399875

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

[tellico] [Bug 382572] New: crash after few seconds on start

2017-07-21 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=382572

Bug ID: 382572
   Summary: crash after few seconds on start
   Product: tellico
   Version: HEAD
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ro...@periapsis.org
  Reporter: s...@sss.chaoslab.ru
  Target Milestone: ---

Created attachment 106783
  --> https://bugs.kde.org/attachment.cgi?id=106783=edit
backtrace

look at summary and attachment

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

[tellico] [Bug 379607] tellico crashes with segfault on start

2017-07-17 Thread Alexandr
https://bugs.kde.org/show_bug.cgi?id=379607

--- Comment #15 from Alexandr <s...@sss.chaoslab.ru> ---
maybe, so i should create separated ticket ?

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

[tellico] [Bug 379607] tellico crashes with segfault on start

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

Alexandr <s...@sss.chaoslab.ru> changed:

   What|Removed |Added

 CC||s...@sss.chaoslab.ru

--- Comment #13 from Alexandr <s...@sss.chaoslab.ru> ---
Created attachment 106673
  --> https://bugs.kde.org/attachment.cgi?id=106673=edit
gdb backtrace

same problem.
gdb backtrace in attachment.

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

[ksmserver] [Bug 379847] Plasma crash at startup

2017-06-27 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=379847

Alexandr Paliy <alexandrpa...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #3 from Alexandr Paliy <alexandrpa...@gmail.com> ---
Problem was related to GCC version during building different parts of the
system.
Gone after rebuilding the whole system with one compiler version.

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

[kdevelop] [Bug 380131] New: KDevelop Open Removed Session Bug

2017-05-23 Thread Alexandr Gulak
https://bugs.kde.org/show_bug.cgi?id=380131

Bug ID: 380131
   Summary: KDevelop Open Removed Session Bug
   Product: kdevelop
   Version: 5.1.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: khor...@openmailbox.org
  Target Milestone: ---

Application: kdevelop (5.1.0)

Qt Version: 5.8.0
Frameworks Version: 5.34.0
Operating System: Linux 4.11.2-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
KDevelop can open just everything which is remained in recent projects or
sessions menu. I have opened my old project, which main folder I have remained
- KDevelop shows window with empty tabs and then crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb754ed5840 (LWP 1194))]

Thread 9 (Thread 0x7fb7013f4700 (LWP 1228)):
#0  0x7fb74b6e6756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb7523c858b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb746a931d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb746a979d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb746a92263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb746a97a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb746a92263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb746a95249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb7523c76d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb74b6e02e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb751cda54f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7fb701bf5700 (LWP 1227)):
#0  0x7fb74b6e6756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb7523c858b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb746a931d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb746a979d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb746a92263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb746a95249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb7523c76d8 in  () at /usr/lib/libQt5Core.so.5
#7  0x7fb74b6e02e7 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7fb751cda54f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7fb70947e700 (LWP 1226)):
#0  0x7fb74b6e6756 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fb7523c858b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fb746a931d0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fb746a979d8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fb746a92263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fb746a97a32 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fb746a92263 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fb746a95249 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fb7523c76d8 in  () at /usr/lib/libQt5Core.so.5
#9  0x7fb74b6e02e7 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fb751cda54f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7fb709c7f700 (LWP 1206)):
#0  0x7ffda9758b00 in clock_gettime ()
#1  0x7fb751ce7826 in clock_gettime () at /usr/lib/libc.so.6
#2  0x7fb7525f6231 in  () at /usr/lib/libQt5Core.so.5
#3  0x7fb7525f49f9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/libQt5Core.so.5
#4  0x7fb7525f4fa5 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#5  0x7fb7525f666e in  () at /usr/lib/libQt5Core.so.5
#6  0x7fb749484e8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#7  0x7fb7494858db in  () at /usr/lib/libglib-2.0.so.0
#8  0x7fb749485acc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#9  0x7fb7525f709b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#10 0x7fb7525a08ca in
QEventLoop::exec(QFlags) () at

[ksmserver] [Bug 379847] Plasma crash at startup

2017-05-15 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=379847

--- Comment #2 from Alexandr Paliy <alexandrpa...@gmail.com> ---
Installed MATE today, it works fine. That means, there are no problems with
Xorg part, it's Qt or KDE who cause this.

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

[ksmserver] [Bug 379847] Plasma crash at startup

2017-05-15 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=379847

--- Comment #1 from Alexandr Paliy <alexandrpa...@gmail.com> ---
Created attachment 105556
  --> https://bugs.kde.org/attachment.cgi?id=105556=edit
Installed versions of qt libs and kde packages

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

[ksmserver] [Bug 379847] New: Plasma crash at startup

2017-05-15 Thread Alexandr Paliy
https://bugs.kde.org/show_bug.cgi?id=379847

Bug ID: 379847
   Summary: Plasma crash at startup
   Product: ksmserver
   Version: 5.9.5
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: l.lu...@kde.org
  Reporter: alexandrpa...@gmail.com
  Target Milestone: ---

Created attachment 10
  --> https://bugs.kde.org/attachment.cgi?id=10=edit
xterm output after plasma crash

Gentoo ~amd64. X server works fine and I can start it with "startx" from a
regular user. Then, I try to "startkde" from one of it's terminals. I see KDE
loading splash screen, but then it fades away and in terminal I see several
KCrash lines (attachment).

Then KDE crash reporter tool pops out, and here is info it provides:


Application: ksmserver (ksmserver), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fea8cfb2200 (LWP 2621))]

Thread 2 (Thread 0x7fea75e0c700 (LWP 2623)):
#0  0x7fea8ca8b1dd in poll () from /lib64/libc.so.6
#1  0x7fea813f071c in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fea813f082c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fea88629f3b in QEventDispatcherGlib::processEvents
(this=0x7fea680008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fea885d00e2 in QEventLoop::exec (this=this@entry=0x7fea75e0bd50,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7fea88416dae in QThread::exec (this=this@entry=0x7fea8d15bd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7fea8d0d7a25 in QDBusConnectionManager::run (this=0x7fea8d15bd80
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7fea8841c6cd in QThreadPrivate::start (arg=0x7fea8d15bd80 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7fea8310b3a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7fea8ca945af in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7fea8cfb2200 (LWP 2621)):
[KCrash Handler]
#5  std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x6175747269763d43) at
/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/include/g++-v6/bits/atomic_base.h:396
#6  QAtomicOps::load (_q_value=...) at
/usr/include/qt5/QtCore/qatomic_cxx11.h:227
#7  QBasicAtomicInteger::load (this=0x6175747269763d43) at
/usr/include/qt5/QtCore/qbasicatomic.h:99
#8  QtPrivate::RefCount::ref (this=0x6175747269763d43) at
/usr/include/qt5/QtCore/qrefcount.h:55
#9  QList::QList (this=this@entry=0x7ffc5354b570, l=...) at
/usr/include/qt5/QtCore/qlist.h:805
#10 0x7fea89c2c506 in QStringList::QStringList (this=0x7ffc5354b570) at
/usr/include/qt5/QtCore/qstringlist.h:100
#11 KProcess::program (this=) at
/var/tmp/portage/kde-frameworks/kcoreaddons-5.34.0/work/kcoreaddons-5.34.0/src/lib/io/kprocess.cpp:253
#12 0x7fea8cd64871 in KSMServer::::operator() (exitCode=9,
__closure=0x14ccc60) at
/var/tmp/portage/kde-plasma/plasma-workspace-5.9.5.1-r1/work/plasma-workspace-5.9.5.1/ksmserver/startup.cpp:691
#13 QtPrivate::FunctorCall, QtPrivate::List,
void, KSMServer::slotAutoStart():: >::call (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:135
#14 QtPrivate::Functor,
1>::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:192
#15 QtPrivate::QFunctorSlotObject, 1,
QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=1, this_=0x14ccc50, r=, a=, ret=) at /usr/include/qt5/QtCore/qobject_impl.h:169
#16 0x7fea885ff8f3 in QtPrivate::QSlotObjectBase::call (a=0x7ffc5354b740,
r=0x14c9c40, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101
#17 QMetaObject::activate (sender=sender@entry=0x14c9c40,
signalOffset=, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffc5354b740) at kernel/qobject.cpp:3723
#18 0x7fea885ffe37 in QMetaObject::activate (sender=sender@entry=0x14c9c40,
m=m@entry=0x7fea8882b1c0 ,
local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7ffc5354b740)
at kernel/qobject.cpp:3602
#19 0x7fea88516611 in QProcess::finished (this=this@entry=0x14c9c40,
_t1=) at .moc/moc_qprocess.cpp:326
#20 0x7fea8851d6bf in QProcessPrivate::_q_processDied
(this=this@entry=0x1517df0) at io/qprocess.cpp:1178
#21 0x7fea8856f704 in QProcessPrivate::waitForFinished
(this=this@entry=0x1517df0, msecs=msecs@entry=3) at
io/qprocess_unix.cpp:895
#22 0x7fea885172fb in QProcess::waitForFinished (this=this@entry=0x14c9c40,
msecs=msecs@entry=3) at io/qprocess.cpp:1922
#23 0x7fea88517a2c in 

[telepathy] [Bug 369527] applet should color through system colors

2016-10-08 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369527

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1
 CC||akulichalexan...@gmail.com

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


[krita] [Bug 369557] New: incorrect number of pixels

2016-09-30 Thread Alexandr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369557

Bug ID: 369557
   Summary: incorrect number of pixels
   Product: krita
   Version: unspecified
  Platform: Ubuntu Packages
   URL: https://www.youtube.com/watch?v=LadV-ORCGYw=yo
utu.be
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: ukro...@yandex.ru

OK!
When I select a certain area to count the number of pixels in the right panel
shows the wrong number. It's very strange. Please fix it!

Reproducible: Always

Steps to Reproduce:
1. Select area
2. Look at pane


Actual Results:  
incorrect number of pixels

Expected Results:  
the program should calculate the correct number of pixels

nope

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


[neon] [Bug 369089] Telegram/Morse not available

2016-09-20 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=369089

--- Comment #1 from Alexandr Akulich <akulichalexan...@gmail.com> ---
May be this is related:
https://bugs.launchpad.net/ubuntu/+source/ktp-contact-list/+bug/1512135

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


[telepathy] [Bug 368546] Add CMake option to disable otr-proxy

2016-09-10 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368546

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

   Keywords||junior-jobs

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


[telepathy] [Bug 368546] New: Add CMake option to disable otr-proxy

2016-09-10 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=368546

Bug ID: 368546
   Summary: Add CMake option to disable otr-proxy
   Product: telepathy
   Version: git-latest
  Platform: unspecified
OS: unspecified
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: common-internals
  Assignee: kde-telepathy-b...@kde.org
  Reporter: akulichalexan...@gmail.com

OTR-Proxy is a complex intermediate component of KTp, which is not really
optional in terms that if you have all dependencies, then it will be a part of
the build.
The problem that there is a bug in the component and you want to disable it,
then you have to break its dependency.


Reproducible: Always

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


[telepathy] [Bug 365990] Taskbar Entry does not work for messages in incoming chat

2016-09-08 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365990

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||akulichalexan...@gmail.com

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


[telepathy] [Bug 348929] Incoming and Outgoing message styles are swapped in history and scrollback.

2016-09-08 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348929

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

   Version Fixed In||16.12
 CC||akulichalexan...@gmail.com

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


[telepathy] [Bug 348929] Incoming and Outgoing message styles are swapped in history and scrollback.

2016-09-08 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=348929

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
  Latest Commit||http://commits.kde.org/tele
   ||pathy-text-ui/7e429544a6f55
   ||30365c22ca5f83b4fc4e97de658
 Resolution|--- |FIXED

--- Comment #1 from Alexandr Akulich <akulichalexan...@gmail.com> ---
Git commit 7e429544a6f5530365c22ca5f83b4fc4e97de658 by Alexandr Akulich, on
behalf of Mariusz Glebocki.
Committed on 08/09/2016 at 21:54.
Pushed by akulichalexandr into branch 'master'.

[lib] Fix message classes for history items

Reviewed-by: Alexandr Akulich <akulichalexan...@gmail.com>
REVIEW: 128841

M  +2-2lib/adium-theme-message-info.cpp

http://commits.kde.org/telepathy-text-ui/7e429544a6f5530365c22ca5f83b4fc4e97de658

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


[telepathy] [Bug 361459] empty ktp-text-ui crashes

2016-08-27 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361459

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 CC||akulichalexan...@gmail.com
 Resolution|--- |FIXED

--- Comment #2 from Alexandr Akulich <akulichalexan...@gmail.com> ---
IMO this is fixed by the referenced commit
https://quickgit.kde.org/?p=ktp-text-ui.git=commit=5015460c6fbd9696bf482e53e7cb94b64097db12
and then fixed again by commit in TelepathyQt:
https://cgit.freedesktop.org/telepathy/telepathy-qt/commit/?id=f496b0dbc0bc293b6a6714ddaa4d542aadc60c08

Feel free to reopen if the bug is still there after both fixes applied.

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


[telepathy] [Bug 364605] Spell check window does not open

2016-08-27 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364605

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 CC||akulichalexan...@gmail.com
 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #1 from Alexandr Akulich <akulichalexan...@gmail.com> ---
Hi Patrick,

"Check Spelling" is "inherited" from KTextEdit, which is a part of KTextWidgets
framework, so IMO this bugreport is not actually related to ktp-text-ui, but to
underlying libraries.  Furthermore, there is no any related change in the
application since its port to KF5 and the spell check works for me and
everybody I asked, so I'm sure that there is something bad with your
installation or setup. Please check your Sonnet and Aspell/Hunspell
installation and configuration, try to reproduce the issue with a different KDE
Application and if there is any problem, then send a bug report to your
distribution first.

We can reopen the bug later, if it would make sense.

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


[telepathy] [Bug 365609] No way to set the nick name in XMPP multi-user chat (MUC)

2016-08-26 Thread Alexandr Akulich via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365609

Alexandr Akulich <akulichalexan...@gmail.com> changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|UNCONFIRMED |CONFIRMED
 CC||akulichalexan...@gmail.com

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


[frameworks-baloo] [Bug 365164] New: Baloo crashes on search

2016-07-06 Thread Alexandr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365164

Bug ID: 365164
   Summary: Baloo crashes on search
   Product: frameworks-baloo
   Version: 5.18.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: pinak.ah...@gmail.com
  Reporter: kde.lrf...@sent.as

-- Information about the crash:


If I open the search bar (Alt+F2) and enter the search term "settings" I get a
notification that baloo has crashed. After this Alt+Space or Alt+F2 stops
working.
If I enter the same search term in the search bar by pressing Alt+F1 the plasma
would crash with the subsequent need to restart the computer.
The problem is reproduced every time, even after reboot and is present from the
moment of the installation of Kubuntu 16.04.

Application: baloo_file (5.18.0)

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

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation
fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1e167928c0 (LWP 1266))]

Thread 2 (Thread 0x7f1ccb5a2700 (LWP 1898)):
#0  0x7f1e14894e8d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f1e11a6539c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f1e11a654ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f1e154caa9b in QEventDispatcherGlib::processEvents
(this=0x7f1cc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f1e15471dea in QEventLoop::exec (this=this@entry=0x7f1ccb5a1bc0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x00420cd8 in Baloo::FileContentIndexer::run (this=0x189b770) at
../../../src/file/filecontentindexer.cpp:71
#6  0x7f1e15290343 in QThreadPoolThread::run (this=0x19b9c80) at
thread/qthreadpool.cpp:93
#7  0x7f1e1529384e in QThreadPrivate::start (arg=0x19b9c80) at
thread/qthread_unix.cpp:331
#8  0x7f1e13ef76fa in start_thread (arg=0x7f1ccb5a2700) at
pthread_create.c:333
#9  0x7f1e148a0b5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109
in
Thread 1 (Thread 0x7f1e167928c0 (LWP 1266)):
[KCrash Handler]
#6  0x7f1e12fd2cb7 in mdb_midl_xmerge () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#7  0x7f1e12fca76c in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#8  0x7f1e12fcaac9 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#9  0x7f1e12fcc704 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#10 0x7f1e12fd0857 in mdb_cursor_del () from
/usr/lib/x86_64-linux-gnu/liblmdb.so.0
#11 0x7f1e12fd1dc0 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0
#12 0x7f1e1595ed8e in Baloo::DocumentDB::del
(this=this@entry=0x7fff917eb520, docId=docId@entry=3414292841891843) at
../../../src/engine/documentdb.cpp:110
#13 0x7f1e15978f8b in Baloo::WriteTransaction::removeDocument
(this=0x1936790, id=id@entry=3414292841891843) at
../../../src/engine/writetransaction.cpp:128
#14 0x7f1e15971ff9 in Baloo::Transaction::removeDocument
(this=this@entry=0x7fff917eb660, id=id@entry=3414292841891843) at
../../../src/engine/transaction.cpp:235
#15 0x00429632 in Baloo::MetadataMover::removeMetadata
(this=this@entry=0x1889110, tr=tr@entry=0x7fff917eb660, url=...) at
../../../src/file/metadatamover.cpp:82
#16 0x0042a012 in Baloo::MetadataMover::moveFileMetadata
(this=0x1889110, from=..., to=...) at ../../../src/file/metadatamover.cpp:53
#17 0x7f1e154a2e4f in QtPrivate::QSlotObjectBase::call (a=0x7fff917eb7c0,
r=0x7fff917ebe80, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#18 QMetaObject::activate (sender=sender@entry=0x1951d80,
signalOffset=, local_signal_index=local_signal_index@entry=7,
argv=argv@entry=0x7fff917eb7c0) at kernel/qobject.cpp:3698
#19 0x7f1e154a37d7 in QMetaObject::activate (sender=sender@entry=0x1951d80,
m=m@entry=0x644cc0 ,
local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7fff917eb7c0)
at kernel/qobject.cpp:3578
#20 0x0042aaba in KInotify::moved (this=this@entry=0x1951d80, _t1=...,
_t2=...) at ./moc_kinotify.cpp:330
#21 0x0042cbff in KInotify::slotEvent (this=,
socket=) at ../../../src/file/kinotify.cpp:421
#22 0x7f1e154a2e4f in QtPrivate::QSlotObjectBase::call (a=0x7fff917eba50,
r=0x1951d80, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#23 QMetaObject::activate (sender=sender@entry=0x192f570,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff917eba50) at kernel/qobject.cpp:3698
#24 0x7f1e154a37d7 in QMetaObject::activate (sender=sender@entry=0x192f570,
m=m@entry=0x7f1e156bd780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff917eba50)
at kernel/qobject.cpp:3578
#25 

[frameworks-kservice] [Bug 353037] Dolphin freezes when trying to open a remote LibreOffice file

2016-02-17 Thread alexandr-makukhin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=353037

alexandr-makukhin <makukhin...@yandex.ru> changed:

   What|Removed |Added

 CC||makukhin...@yandex.ru

--- Comment #15 from alexandr-makukhin <makukhin...@yandex.ru> ---
Starting the LibreOffice result in an error.

KDEInit не может запустить «/usr/lib/x86_64-linux-gnu/libexec/kf5/kioexec»

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

[kde] [Bug 358305] New: acestream & viber

2016-01-21 Thread Alexandr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358305

Bug ID: 358305
   Summary: acestream & viber
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: vetra...@mail.ru

Application: kdeconnectd (0.1)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 3.16.0-59-generic x86_64
Distribution: Ubuntu 14.04.3 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Hi, Linux 14.04, the package is installed according to the instructions
http://forum.torrentstream.org/index.php?topic=2967.0 from the repository,
after installing Viber stops working (it starts and then
closes). Remove a package acestream-full restores
Viber.

The crash can be reproduced every time.

-- Backtrace:
Application: kdeconnect (kdeconnectd), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f4d7197f7c0 (LWP 2061))]

Thread 2 (Thread 0x7f4d5f538700 (LWP 2072)):
[KCrash Handler]
#6  0x7f4d69b7dc8e in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#7  0x7f4d69b770e2 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x7f4d69b775d2 in dbus_message_unref () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
#9  0x7f4d6e2df099 in q_dbus_message_unref (message=) at
qdbus_symbols_p.h:296
#10 ~QDBusArgumentPrivate (this=, __in_chrg=) at
qdbusargument.cpp:66
#11 QDBusArgument::~QDBusArgument (this=0xe8f310, __in_chrg=) at
qdbusargument.cpp:348
#12 0x7f4d6e2bbbce in qMetaTypeDeleteHelper (t=0xe941d0) at
../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134
#13 0x7f4d6fa78083 in clear (d=0xe08ca0) at kernel/qvariant.cpp:290
#14 0x7f4d6e2aae2c in node_destruct (this=, to=, from=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:431
#15 free (this=, data=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:757
#16 QList::~QList (this=0xe8f310, __in_chrg=) at
../../include/QtCore/../../src/corelib/tools/qlist.h:732
#17 0x7f4d6e2bf40f in QDBusMessage::~QDBusMessage (this=0xe8f310,
__in_chrg=) at qdbusmessage.cpp:537
#18 0x7f4d6e2bc1b6 in ~QDBusCallDeliveryEvent (this=0xe59bc0,
__in_chrg=) at qdbusintegrator_p.h:93
#19 QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent (this=0xe59bc0,
__in_chrg=) at qdbusintegrator_p.h:93
#20 0x7f4d6fa57b46 in QCoreApplicationPrivate::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xe3b770) at
kernel/qcoreapplication.cpp:1593
#21 0x7f4d6fa57fe3 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0) at
kernel/qcoreapplication.cpp:1470
#22 0x7f4d6fa81f83 in sendPostedEvents () at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#23 postEventSourceDispatch (s=0x7f4d58001350) at
kernel/qeventdispatcher_glib.cpp:287
#24 0x7f4d6c13fe04 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f4d6c140048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f4d6c1400ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f4d6fa817a1 in QEventDispatcherGlib::processEvents
(this=0x7f4d580008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#28 0x7f4d6fa530af in QEventLoop::processEvents
(this=this@entry=0x7f4d5f537e20, flags=...) at kernel/qeventloop.cpp:149
#29 0x7f4d6fa533a5 in QEventLoop::exec (this=this@entry=0x7f4d5f537e20,
flags=...) at kernel/qeventloop.cpp:204
#30 0x7f4d6f94fc5f in QThread::exec (this=) at
thread/qthread.cpp:537
#31 0x7f4d6f95232f in QThreadPrivate::start (arg=0xe58da0) at
thread/qthread_unix.cpp:349
#32 0x7f4d6c61f182 in start_thread (arg=0x7f4d5f538700) at
pthread_create.c:312
#33 0x7f4d6f30847d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f4d7197f7c0 (LWP 2061)):
#0  0x7f4d6f2f982d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f4d6c180c10 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f4d6c13fb14 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f4d6c13ff7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f4d6c1400ec in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f4d6fa817be in QEventDispatcherGlib::processEvents (this=0xca5920,
flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0x7f4d704e3be6 in QGuiEventDispatcherGlib::processEvents
(this=, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#7  0x7f4d6fa530af in QEventLoop::processEvents
(this=this@entry=0x7ffe4a266820, flags=...) at kernel/qeventloop.cpp:149
#8  0x7f4d6fa533a5 in QEventLoop::exec