[plasmashell] [Bug 469906] Plasma hangs some time after switching between activities

2023-06-02 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=469906

--- Comment #1 from Enmk  ---
Update: Happened today again and since the window frames were missing too (only
content is visible) I thorught that this might be related to KWin.

So there is a simple fix from second tty (switching by Ctrl+Alt+F2):
```
$ killall kwin # -- that says something like "not found kwin"
$ DISPLAY=:0 kwin --replace & # restarts KWin and everything is back to normal
```

It would be nice if KWin wouldn't crash, but a backup mechanism of restarting
KWin if it is absent/not healthy would solve my workflow in 99% of cases.

Can someone please draft a script that would do something like that as a
short-term solution?

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

[plasmashell] [Bug 469906] New: Plasma hangs some time after switching between activities

2023-05-17 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=469906

Bug ID: 469906
   Summary: Plasma hangs some time after switching between
activities
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: v.nem...@gmail.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
***
After a while (I notice that this happens after switching to another activity),
I am unable to switch between applications with keyboard nor with clicking on
"Icons only task manager". Activity switching kind of works (icons in task
manager change), but actual active window doesn't change too.

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


STEPS TO REPRODUCE
1. Happens randomly, I assume, after switching to another activity.

OBSERVED RESULT
Can't switch between applications with neither keyboard nor mouse.

If I check `dmesg`, there is nothing suspiciuos, `journalctl --since today
--user --unit=plasma-plasmashell` gives this at:
```
May 17 18:29:03 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:03 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:03 enmk-xps9570 plasmashell[3961]: qml: PlasmaExtras.ScrollArea is
deprecated. Use PlasmaComponents3.ScrollView instead.
May 17 18:29:03 enmk-xps9570 plasmashell[3961]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:185:
TypeError: Value is null and could not be converted to an object
May 17 18:29:18 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:18 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:18 enmk-xps9570 plasmashell[3961]: qml: PlasmaExtras.ScrollArea is
deprecated. Use PlasmaComponents3.ScrollView instead.
May 17 18:29:19 enmk-xps9570 plasmashell[3961]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:185:
TypeError: Value is null and could not be converted to an object
May 17 18:29:21 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:21 enmk-xps9570 plasmashell[3961]: SwitcherBackend: FAILED to get
the thumbnail "Unknown error code 0\n\nPlease send a full bug report at
https://bugs.kde.org.; ("Undocumented Error", "Undocumented
ErrorUnknown error code 0\n>
May 17 18:29:21 enmk-xps9570 plasmashell[3961]: qml: PlasmaExtras.ScrollArea is
deprecated. Use PlasmaComponents3.ScrollView instead.
May 17 18:29:22 enmk-xps9570 plasmashell[3961]:
file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Desktop.qml:185:
TypeError: Value is null and could not be converted to an object
```
If I try to restart plasma with `kquitapp5 plasmashell || killall plasmashell
&& kstart5 plasmashell` from `krunner` or terminal, it seems to be restarting
incorrectly: keyboard input is not working at all, window decorations are
missing.
Had to restart OS to fix it.

EXPECTED RESULT
Can switch between applications within activity / switch between activities. OR
restarting plasma fixes the issue.

SOFTWARE/OS VERSIONS
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: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9570

ADDITIONAL INFORMATION
Started to happen only recently, was working fine before system update. Single
built-in single-monitor setup. Maybe related to low available RAM on machine
(used by other process excessively), no swap.

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

[plasmashell] [Bug 463114] System monitor sensor - Disk usage widget forgets sensors

2022-12-16 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=463114

--- Comment #2 from Enmk  ---
The issue happened many times throughout the year, usually once per week.
System is updated regularly, and the issue appeared on previous Neon versions
and survived (several) dist-upgrades.

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

[plasmashell] [Bug 463114] System monitor sensor - Disk usage widget forgets sensors

2022-12-16 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=463114

--- Comment #1 from Enmk  ---
Created attachment 154624
  --> https://bugs.kde.org/attachment.cgi?id=154624=edit
Widget sensors configuration

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

[plasmashell] [Bug 463114] New: System monitor sensor - Disk usage widget forgets sensors

2022-12-16 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=463114

Bug ID: 463114
   Summary: System monitor sensor - Disk usage widget forgets
sensors
Classification: Plasma
   Product: plasmashell
   Version: 5.26.4
  Platform: Neon
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: plasma-b...@kde.org
  Reporter: v.nem...@gmail.com
CC: ahiems...@heimr.nl, notm...@gmail.com
  Target Milestone: 1.0

Created attachment 154623
  --> https://bugs.kde.org/attachment.cgi?id=154623=edit
Widget apperance configuration

SUMMARY
***
I have multiple filesystems mounted (at startup), each filesystem is added as a
(percentage used) horizontal bar to "System monitor sensor" widget to a
desktop.
>From time to time I notice that some of the bars disappear from the widget and
I have to re-add those manually. Corresponding FSs seem to be working just
fine, so the problem clearly is in the widget.

***


OBSERVED RESULT
Bars corresponding to some FS disappear from widget, usually leaving 3 of 5
bras

EXPECTED RESULT
Widget doesn't forget sensors

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Manufacturer: Dell Inc.
Product Name: XPS 15 9570

ADDITIONAL INFORMATION
One note that all FS on my laptop are LUKS with an encryption:
```
$ cat /etc/fstab 
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
#  
UUID=56E5-5939/boot/efi  vfat   
defaults,noatime 0 2
/dev/mapper/luks-<> /  ext4defaults,noatime,discard 0 1
tmpfs /tmp   tmpfs  
defaults,noatime,mode=1777 0 0

/dev/mapper/luks-<>   /home/enmk ext4   discard 
0 0 
/dev/mapper/luks-<>   /home/enmk/work/altinity   ext4   discard 
    0 0 
/dev/mapper/luks-<>   /home/enmk/work/pets   ext4   discard 
0 0 
UUID=<>   none   swap   sw  
0 0 
/dev/sda5   /mnt/ntfs  
   ntfs   noatime,noauto,nodiratime,ro,users   0 0

$ cat /etc/crypttab 
# /etc/crypttab: mappings for encrypted partitions.
#
# Each mapped device will be created in /dev/mapper, so your /etc/fstab
# should use the /dev/mapper/ paths for encrypted devices.
#
# See crypttab(5) for the supported syntax.
#
# NOTE: You need not list your root (/) partition here, but it must be set up
#   beforehand by the initramfs (/etc/mkinitcpio.conf). The same applies
#   to encrypted swap, which should be set up with mkinitcpio-openswap
#   for resume support.
#
#  
luks-<> UUID=<> /crypto_keyfile.bin luks,discard

# home folder
luks-<> UUID=<> /etc/luks-keys/disk_secret_key
luks,discard,tries=1
# pets disk
luks-<> UUID=<> /etc/luks-keys/disk_secret_key
luks,discard,tries=1
# altinity disk
luks-<> UUID=<> /etc/luks-keys/disk_secret_key
luks,discard,tries=1
```

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

[kdiff3] [Bug 456946] New: kdiff3 can't read files from bash <()

2022-07-20 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=456946

Bug ID: 456946
   Summary: kdiff3 can't read files from bash <()
   Product: kdiff3
   Version: 1.9.5
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: reeves...@gmail.com
  Reporter: v.nem...@gmail.com
  Target Milestone: ---

SUMMARY
***

***


STEPS TO REPRODUCE
1. kdiff3 <(echo hello) <(echo world) 

OBSERVED RESULT
kdiff3 shows error popup multiple times and doesn't display any diff

$ kdiff3 <(echo hello) <(echo world)
org.kde.kdiff3: "Loading A: /dev/fd/63"
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
org.kde.kdiff3: "Loading B: /dev/fd/62"
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
kf.kio.core: couldn't create slave: "Unknown protocol 'pipe'."
org.kde.kdiff3.fileAccess: slotStatResult: pJob->error() =  173
org.kde.kdiff3: "Diff: A <-> B"
org.kde.kdiff3: "Linediff: A <-> B"
org.kde.kdiff3: Enter: calcDiff3LineListUsingAB
org.kde.kdiff3: Leave: calcDiff3LineListUsingAB

EXPECTED RESULT
kdiff3 is able to read from file substitution and display a diff

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.24
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.13.0-48-generic (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

ADDITIONAL INFORMATION
$ kdiff3 --version
kdiff3 1.9.5 (64 bit)

$ sha256sum `which kdiff3`
397555cae80ca330a2ae30f0c30b28e0109e955e59e260cd606980e88bcf8477 
/usr/bin/kdiff3

$ apt show kdiff3
Package: kdiff3
Version: 1.9.5-0xneon+20.04+focal+release+build14
Priority: optional
Section: kde
Maintainer: Neon CI 
Installed-Size: 5,264 kB
Depends: libc6 (>= 2.14), libkf5configcore5, libkf5configwidgets5,
libkf5coreaddons5, libkf5crash5, libkf5i18n5, libkf5kiocore5,
libkf5kiowidgets5, libkf5parts5, libkf5widgetsaddons5, libkf5xmlgui5,
libqt5core5a (>= 5.15.2+p20.04+tunstable+git20220305.0110), libqt5gui5 (>=
5.15.2+p20.04+tunstable+git20220305.0110), libqt5printsupport5 (>=
5.15.2+p20.04+tunstable+git20220305.0110), libqt5widgets5 (>=
5.15.2+p20.04+tunstable+git20220305.0110), libstdc++6 (>= 5)
Recommends: kdiff3-doc
Breaks: kdiff3-qt (<< 1.0)
Replaces: kdiff3-qt (<< 1.0)
Homepage: https://kde.org/applications/development/kdiff3
Download-Size: 863 kB
APT-Manual-Installed: yes

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

[kate] [Bug 188764] Ambiguous shortcuts in all actions when starting Kate with split views

2021-02-11 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=188764

Enmk  changed:

   What|Removed |Added

   Platform|Ubuntu Packages |Neon Packages
 CC||v.nem...@gmail.com
Version|unspecified |20.12.1
 Status|RESOLVED|REOPENED
 Resolution|FIXED   |---

--- Comment #30 from Enmk  ---
This bug recently reappeared for me while editing a markdown document with a
live preview. 

Occasionally either Ctrl+F, Ctrl+S, or Ctrl+C stop working, which is a huge
inconvenience. Nothing suspicious in the settings, i.e., no keybindings
dublicates.

Kate
Version 20.12.1

KMarkdownWebViewPart
Version 0.5.6

Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.15.2
Kernel Version: 5.4.0-65-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31,0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

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

[neon] [Bug 428212] QtCreator's clang backend isn't shipped with its packages.

2020-12-02 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=428212

Enmk  changed:

   What|Removed |Added

 CC||v.nem...@gmail.com

--- Comment #1 from Enmk  ---
Same thing is happening to me too:

Operating System: KDE neon 5.20
KDE Plasma Version: 5.20.4
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
Kernel Version: 5.4.0-54-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31,0 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630

$ apt show qtcreator
Package: qtcreator
Version: 4.13.0-1+20.04+focal+build26
Priority: optional
Section: devel
Maintainer: Neon CI 
Installed-Size: 79,2 MB
Depends: libqt5sql5-sqlite, qml-module-qtqml-models2,
qml-module-qtquick-controls (>= 5.5.0~), qml-module-qtquick2 (>= 5.5.0~),
qtchooser, qtcreator-data (= 4.13.0-1+20.04+focal+build26), libc6 (>= 2.29),
libdw1 (>= 0.158), libelf1 (>= 0.142), libgcc-s1 (>= 3.4), libllvm10 (>=
1:9~svn298832-1~), libqt5concurrent5 (>= 5.15.0+dfsg), libqt5core5a (>=
5.15.0+dfsg), libqt5designer5, libqt5designercomponents5, libqt5gui5 (>=
5.15.0+dfsg), libqt5help5, libqt5network5 (>= 5.15.0+dfsg), libqt5printsupport5
(>= 5.15.0+dfsg), libqt5qml5 (>= 5.15.0), libqt5quick5 (>= 5.15.0),
libqt5quickwidgets5 (>= 5.15.0), libqt5serialport5, libqt5sql5 (>=
5.15.0+dfsg), libqt5widgets5 (>= 5.15.0+dfsg), libqt5xml5 (>= 5.15.0+dfsg),
libstdc++6 (>= 7), libyaml-cpp0.6 (>= 0.6.2)
Recommends: clang-tidy, gdb, make, qmlscene, qt5-doc, qt5-qmltooling-plugins,
qtbase5-dev-tools, qtcreator-doc, qtdeclarative5-dev-tools, qttools5-dev-tools,
qttranslations5-l10n, qtxmlpatterns5-dev-tools, xterm | x-terminal-emulator
Suggests: clazy (>= 1.5), cmake, g++, git, meson, subversion, valgrind
Breaks: qtcreator-data (<< 4.5.2-2~)
Replaces: qtcreator-data (<< 4.5.2-2~)
Homepage: https://doc.qt.io/qt-5/topics-app-development.html
Download-Size: 20,3 MB
APT-Manual-Installed: yes
APT-Sources: http://archive.neon.kde.org/user focal/main amd64 Packages
Description: integrated development environment (IDE) for Qt

$ which qtcreator
/usr/bin/qtcreator

$ qtcreator -version

Qt Creator 4.13.0 based on Qt 5.15.1

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

[neon] [Bug 418692] Qt Creator from distro packages lacks features present in binary version from qt.io

2020-03-25 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=418692

--- Comment #4 from Enmk  ---
Well, something disturbing happened recently: I wasn't able to update Qt
Creator on Mac, since "My license for this platform expired" (not exact words,
but something like that). And to "Extend" that license, I had to log in with
corporate email (which I did not). I imagine something like that may happen
soon with Linux version too.

That means one day you might be unable to install Qt Creator from qt.io on
Linux, and the (broken) package in distribution is going to be the only free
(in many senses) source.

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

[neon] [Bug 418692] Qt Creator from distro packages lacks features present in binary version from qt.io

2020-03-14 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=418692

--- Comment #2 from Enmk  ---
Hi! There is no problem with using binaries qt.io, and I ended using it anyway.

EXCEPT:
* qt.io binaries is not default source of applications for KDE Neon (while apt
is)
* it requires qt.io login
* it bypasses the package manager

Also what is the point of having qt creator in repos if it doesn’t works as
expected?

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

[neon] [Bug 418692] New: Qt Creator from distro packages lacks features present in binary version from qt.io

2020-03-10 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=418692

Bug ID: 418692
   Summary: Qt Creator from distro packages lacks features present
in binary version from qt.io
   Product: neon
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Packages User Edition
  Assignee: neon-b...@kde.org
  Reporter: v.nem...@gmail.com
CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org
  Target Milestone: ---

SUMMARY

I have installed qt creator with apt a long time ago, and after update few very
important features are gone/not working properly:
* Run in terminal
* Clang code model

STEPS TO REPRODUCE (Run in terminal)
1. apt install qtcreator
2. launch qtcreator
3. create a simple hello world C/C++ application
4. Navigate to "build and run"/Run, select "Run in terminal option"
5. choose build/Run from application menu.

OBSERVED RESULT
Application pane is opened with text:
"Starting /home/enmk/proj/test/build-test-Clang_8-Debug/main ..."
No terminal window is opened anywhere on desktop, program is not launched.

EXPECTED RESULT
New teminal window with program output appears.



STEPS TO REPRODUCE (clang code model)
1. apt install qtcreator
2. qtcreator
3. create a simple hello world C/C++ application
4. choose Tools/Options from application menu, choose C++/Code model tab

OBSERVED RESULT
Part of dialog is greyed out, and the label says "The Clang code model is
disabled because the corresponding plugin is not loaded".
There is no Clang Code Model plugin in the list of plugins.

EXPECTED RESULT
Dialog shows "The Clang code model is ebabled because the corresponding plugin
is loaded"
Clang Code Model plugin is present in the list of plugins and works fine.




SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.18
KDE Plasma Version: 5.18.2
KDE Frameworks Version: 5.67.0
Qt Version: 5.14.1
Kernel Version: 5.3.0-40-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz
Memory: 31.0 GiB of RAM


ADDITIONAL INFORMATION
Same issues are not reproducible on same version of Qt Creator installed from
qt.io with online installer.

Please find more information in qt.io bugtracker:
https://bugreports.qt.io/browse/QTCREATORBUG-23705
https://bugreports.qt.io/browse/QTCREATORBUG-23704

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

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=411130

--- Comment #2 from Enmk  ---
Backtrace of doing the same in '100%' zoom mode:


Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff1480c8200 (LWP 444))]

Thread 7 (Thread 0x7ff112ffd700 (LWP 498)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff112ffcbe0, expected=0, futex_word=0x56105d01db94) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff112ffcca0, mutex=0x56105d01db40,
cond=0x56105d01db68) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105d01db68, mutex=0x56105d01db40,
abstime=0x7ff112ffcca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105d01db40, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105d01db40) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105b73dce0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105b73dcd0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105b73dcd0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff112ffd700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7ff113fff700 (LWP 497)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff113ffebe0, expected=0, futex_word=0x56105b079d14) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff113ffeca0, mutex=0x56105b079cc0,
cond=0x56105b079ce8) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105b079ce8, mutex=0x56105b079cc0,
abstime=0x7ff113ffeca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105b079cc0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105b079cc0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105b777ec0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105b777eb0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105b777eb0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff113fff700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7ff1137fe700 (LWP 496)):
#0  0x7ff140ad4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7ff1137fdbe0, expected=0, futex_word=0x56105c175734) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  __pthread_cond_wait_common (abstime=0x7ff1137fdca0, mutex=0x56105c1756e0,
cond=0x56105c175708) at pthread_cond_wait.c:533
#2  __pthread_cond_timedwait (cond=0x56105c175708, mutex=0x56105c1756e0,
abstime=0x7ff1137fdca0) at pthread_cond_wait.c:667
#3  0x7ff14443ed36 in QWaitConditionPrivate::wait_relative
(this=0x56105c1756e0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x56105c1756e0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=, mutex=0x56105c166e60,
deadline=...) at thread/qwaitcondition_unix.cpp:225
#6  0x7ff14443f096 in QWaitCondition::wait (this=this@entry=0x56105c1d11e0,
mutex=mutex@entry=0x56105c166e60, time=) at
thread/qwaitcondition_unix.cpp:209
#7  0x7ff14443c740 in QThreadPoolThread::run (this=0x56105c1d11d0) at
thread/qthreadpool.cpp:139
#8  0x7ff144437c72 in QThreadPrivate::start (arg=0x56105c1d11d0) at
thread/qthread_unix.cpp:361
#9  0x7ff140ace6db in start_thread (arg=0x7ff1137fe700) at
pthread_create.c:463
#10 0x7ff143d3788f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7ff11baed700 (LWP 449)):
#0  0x7ff140ad49f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x561059d53b98) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x561059d53b48,
cond=0x561059d53b70) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x561059d53b70, mutex=0x561059d53b48) at
pthread_cond_wait.c:655
#3  0x7ff11c6d00aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7ff11c6cfdd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7ff140ace6db in start_thread (arg=0x7f

[okular] [Bug 411130] Searching CHM files crashes Okular

2019-08-21 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=411130

--- Comment #1 from Enmk  ---
Well, actually I've opened a subsection of the 'The Python standard
library'/'Builting types'/'set and frozenset', but any other page may cause a
crash too. It is not always reproducible from the first try, click around the
'Contents'.

It also looks like that setting '100%' zoom mode rather than 'Fit width',
reduces chances of crashing.

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

[okular] [Bug 411130] New: Searching CHM files crashes Okular

2019-08-21 Thread Enmk 
https://bugs.kde.org/show_bug.cgi?id=411130

Bug ID: 411130
   Summary: Searching CHM files crashes Okular
   Product: okular
   Version: 1.8.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: v.nem...@gmail.com
  Target Milestone: ---

Application: okular (1.8.0)

Qt Version: 5.12.3
Frameworks Version: 5.61.0
Operating System: Linux 5.0.0-25-generic x86_64
Distribution: KDE neon User Edition 5.16

-- Information about the crash:
- What I was doing when the application crashed:
* Downloaded a Python 2.7.16 docs in CHM format from
https://www.python.org/ftp/python/2.7.16/python2716.chm
* Opened the said chm with Okular
* Typed 'set' in search bar
* Navigated search results to a 'Standard library' page
* Clicked the page to open

The crash can be reproduced every time.

-- Backtrace:
Application: Okular (okular), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fea4d576200 (LWP 30784))]

Thread 4 (Thread 0x7fea20ea4700 (LWP 30789)):
#0  0x7fea45f829f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55b0ab5234b8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55b0ab523468,
cond=0x55b0ab523490) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55b0ab523490, mutex=0x55b0ab523468) at
pthread_cond_wait.c:655
#3  0x7fea21a870aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4  0x7fea21a86dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#5  0x7fea45f7c6db in start_thread (arg=0x7fea20ea4700) at
pthread_create.c:463
#6  0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fea32af2700 (LWP 30788)):
#0  _dl_update_slotinfo (req_modid=2) at ../elf/dl-tls.c:651
#1  0x7fea4d3aa87c in update_get_addr (ti=0x7fea49f6d670) at
../elf/dl-tls.c:799
#2  0x7fea4d3b0a28 in __tls_get_addr () at
../sysdeps/x86_64/tls_get_addr.S:55
#3  0x7fea498e4c26 in get_thread_data () at thread/qthread_unix.cpp:184
#4  QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at
thread/qthread_unix.cpp:239
#5  0x7fea49b1bcaa in postEventSourcePrepare (s=0x7fea2c004ba0,
timeout=0x7fea32af1ba4) at kernel/qeventdispatcher_glib.cpp:252
#6  0x7fea43c49b28 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fea43c4a4fb in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fea43c4a6dc in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fea49b1bdcb in QEventDispatcherGlib::processEvents
(this=0x7fea2c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#10 0x7fea49abd03a in QEventLoop::exec (this=this@entry=0x7fea32af1d70,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#11 0x7fea498e44ca in QThread::exec (this=) at
thread/qthread.cpp:531
#12 0x7fea49f8a015 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#13 0x7fea498e5c72 in QThreadPrivate::start (arg=0x7fea4a201d80) at
thread/qthread_unix.cpp:361
#14 0x7fea45f7c6db in start_thread (arg=0x7fea32af2700) at
pthread_create.c:463
#15 0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fea3b7b8700 (LWP 30787)):
#0  0x7fea491d8bf9 in __GI___poll (fds=0x7fea3b7b7ca8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fea469fe747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7fea46a0036a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7fea3e59f578 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x7fea498e5c72 in QThreadPrivate::start (arg=0x55b0ab27d110) at
thread/qthread_unix.cpp:361
#5  0x7fea45f7c6db in start_thread (arg=0x7fea3b7b8700) at
pthread_create.c:463
#6  0x7fea491e588f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fea4d576200 (LWP 30784)):
[KCrash Handler]
#6  QWidget::window (this=0x55b0ad940680) at kernel/qwidget.cpp:4330
#7  0x7fea4ab86e4c in QWidgetPrivate::sharedPainter (this=0x55b0ac7c56f0)
at
../../include/QtWidgets/5.12.3/QtWidgets/private/../../../../../src/widgets/kernel/qwidget_p.h:985
#8  QWidget::render (this=this@entry=0x55b0ad940680,
painter=painter@entry=0x7ffdd5addcc0, targetOffset=..., sourceRegion=...,
renderFlags=renderFlags@entry=...) at kernel/qwidget.cpp:5185
#9  0x7fea4ab8795b in QWidget::render (this=this@entry=0x55b0ad940680,
target=target@entry=0x55b0acaace40, targetOffset=..., sourceRegion=...,
renderFlags=..., renderFlags@entry=...) at kernel/qwidget.cpp:5126
#10 0x7fea1b92ae42 in copyWidget (r=..., p=p@entry=0x7ffdd5ade348,