[muon] [Bug 369301] Muon doesn't find packages after installing a package

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

   Severity|normal  |major

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

[plasmashell] [Bug 371487] Plasma crashes when changing tray icon settings

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 101702
  --> https://bugs.kde.org/attachment.cgi?id=101702=edit
Crash backtrace

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

[plasmashell] [Bug 371487] New: Plasma crashes when changing tray icon settings

[Lastique via KDE Bugzilla]

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

Bug ID: 371487
   Summary: Plasma crashes when changing tray icon settings
   Product: plasmashell
   Version: 5.7.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: andy...@mail.ru

Plasma shell process crashes when I change which icons in the system tray (the
notification area) are shown or hidden.

Reproducible: Always

Steps to Reproduce:
1. Right click on the system tray, pick System Tray Settings.
2. Go to the Entries page.
3. Select an entry and change its visibility (e.g. from Auto to Shown).
4. Select another entry and try changing its visibility.

Actual Results:  
The second time the drop-down list becomes white, the text in the list is not
visible. When I click outside the list to close it, plasma crashes.

Expected Results:  
Visibility selection should work, plasma should not crash.

Kubuntu 16.10, x86_64. Intel Haswell GPU drivers.

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

[konsole] [Bug 362416] Switching between tabs is slow

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

   Severity|normal  |major

--- Comment #3 from Lastique  ---
I stopped using Konsole and switched to Terminator because of this problem. The
delay is just unbearable with my normal work.

After some usage I can say that Terminator also seem to render console contents
faster. I used to think that the delay is related to ssh connection speed (I
often used Konsole for remote connections via ssh) but Terminator does seem to
work much faster in the very same conditions.

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

[muon] [Bug 369301] Muon doesn't find packages after installing a package

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
(In reply to Tony from comment #1)
> I used to have a similar issue (before i ditch it and went full terminal...)
> and it was related to muon building a search index.  Let it do its think,
> close and open it again, that's what worked for me.

The search doesn't start to work even if you wait until it finishes rebuilding
the index. Only restart helps.

But it would still be a bug even if it started working after rebuilding the
index had completed. Somehow other package managers don't have this problem.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

--- Comment #8 from Lastique  ---
(In reply to Christophe Giboudeaux from comment #7)
> file_db_data should only contain directories nowadays. run 'akonadictl fsck'
> and check if you still have files inside.

Thanks, 'akonadictl fsck' removed the files from file_db_data. It didn't fix
syncing though.

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

[kmail2] [Bug 316888] Folder retrieval options are not preserved across reboot

[Lastique via KDE Bugzilla]

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

--- Comment #5 from Lastique  ---
(In reply to Laurent Montel from comment #4)
> Git commit 9376f6317bc0c0ee60e45f3474280499771b33f4 by Montel Laurent.
> Committed on 25/09/2016 at 05:40.
> Pushed by mlaurent into branch 'master'.
> 
> increase maximum minutes for "Retrieve message bodies on demand" option
> 
> M  +60   -39   src/widgets/cachepolicypage.ui
> 
> http://commits.kde.org/akonadi/9376f6317bc0c0ee60e45f3474280499771b33f4

Thank you for the fix. Do I understand correctly that the new limit is 
minutes, just under 7 days? If so, I think it is still too short. Could the
limit be removed at all? Or at least be raised to a month or so?

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

--- Comment #6 from Lastique  ---
Could the problem be related to the amount of messages in the email account? My
~/.local/share/akonadi/file_db_data contains 112871 files plus 100 directories
with more files inside. Reading the file_db_data directory takes a noticeable
amount of time.

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

[kmail2] [Bug 316888] Folder retrieval options are not preserved across reboot

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #3 from Lastique  ---
In Kubuntu 16.04, Kmail 5.1.3, the retrieval options are saved, but I can't
enter more than 99 minutes into the "Retrieve message bodies on demand" option.
I consider this a bug because I want to keep recent messages (e.g. up to a few
weeks old) locally for faster access, and 1.5 hour upper limit is just
impractical.

Also, opening the folder properties seems to block on the IMAP resource, since
because of https://bugs.kde.org/show_bug.cgi?id=364802 I'm almost not able to
open folder properties on one of my IMAP accounts - the dialog window either
appears with a long delay or does not appear at all.

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

[kmail2] [Bug 317117] Cannot assign Shift+Ins to "Paste Without Formatting" in composer

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

Version|4.10.1  |5.1.3
   Platform|Ubuntu Packages |Kubuntu Packages

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

[kmail2] [Bug 336596] Message list navigation not working when composer is open

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
Version|4.13.1  |5.1.3
 Status|NEEDSINFO   |UNCONFIRMED
   Platform|unspecified |Kubuntu Packages

--- Comment #2 from Lastique  ---
(In reply to Denis Kurz from comment #1)
> This bug has only been reported for versions before 4.14, which have been
> unsupported for at least two years now. Can anyone tell if this bug still
> present?
> 
> If noone confirms this bug for a Framework-based version of kmail2 (version
> 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in
> about three months.

I can still reproduce this bug in Kubuntu 16.04 x86_64, Kmail 5.1.3.

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

[kmail2] [Bug 317117] Cannot assign Shift+Ins to "Paste Without Formatting" in composer

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |CONFIRMED

--- Comment #3 from Lastique  ---
Kmail 5.1.3 in Kubuntu 16.04 behaves differently than the one I reported the
problem against. But the problem still persists.

The original problem was that pasting links from Chrome in the composer would
invoke a menu and there was no way around it (the keyboard shortcut did not
avoid the menu).

Currently, the menu does not appear whether you do a regular paste or paste
without formatting. However, you can see that the shortcut still cannot be
reassigned. Here's the updated repro:

1. Open kmail composer (e.g. by creating a new mail). Go to Settings->Configure
shortcuts.
2. Select "Paste Without Formatting" primary or alternate shortcut and change
it to Shift+Ins. Confirm if it asks whether it should reassign the shortcut
from "Paste".
3. Open Chrome or Chromium and open any web page. Copy the URL in the address
bar (Ctrl+Ins). Note: the browser is essential, won't work with Firefox.
4. Go back to the email composer.
5. Ensure you have Rich Text editing mode enabled.
6. Paste the URL into the message body by pressing Shift+Ins. Also try pasting
by selecting Edit->Paste and Edit->Paste Without Formatting in the menu for
comparison.

What you will see that Paste puts the URL formatted as an URL (e.g. blue
underlined) and Paste Without Formatting puts it as plain text. Shift+Ins,
despite being reassigned, acts equivalently to Paste.

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

[muon] [Bug 369301] New: Muon doesn't find packages after installing a package

[Lastique via KDE Bugzilla]

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

Bug ID: 369301
   Summary: Muon doesn't find packages after installing a package
   Product: muon
   Version: 5.6
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: andy...@mail.ru
CC: silh...@gmail.com

After installing/updating a package in Muon, searching for other packages does
not produce any results.

Reproducible: Always

Steps to Reproduce:
1. Start Muon package manager.
2. In the search field, type some package name that you know exists in the
repository (e.g. kmail). Note that the package is found and displayed in the
list below.
3. Now select and install some package that was previously not installed.
Upgrading packages by pressing "Full Upgrade" also works.
4. After the installation completes, type the same package name from bullet 2
in the search field again.

Actual Results:  
The second time the package is not found. In fact the package list is always
empty as if no packages ever found through the search field.

Expected Results:  
The search should continue to work.

Kubuntu 16.04, x86_64.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

   Severity|normal  |grave

--- Comment #5 from Lastique  ---
I stopped using kmail because of this bug. Please, fix it.

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

[frameworks-kwallet] [Bug 368126] KWallet can't open a gpg-encrypted wallet

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 100890
  --> https://bugs.kde.org/attachment.cgi?id=100890=edit
KWallet error message

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

[frameworks-kwallet] [Bug 368126] New: KWallet can't open a gpg-encrypted wallet

[Lastique via KDE Bugzilla]

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

Bug ID: 368126
   Summary: KWallet can't open a gpg-encrypted wallet
   Product: frameworks-kwallet
   Version: 5.18.0
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: andy...@mail.ru
CC: kdelibs-b...@kde.org

A newly created wallet with GPG backend cannot be opened.

Reproducible: Always

Steps to Reproduce:
1. Start Wallet Manager.
2. Create a new wallet (File->New), select GPG backend and an RSA-4096 GPG key.
3. When you select the key, an error appears (see the attach). No matter how
many times you press Retry, the same error appears.
4. When you press Cancel, the error disappears, the new wallet is in the list
in the Manager.
5. When you try to open the wallet, the same error appears. Occasionally the
error does not appear and the wallet opens, but that is a rare case.
6. The same error appears when you execute `kwallet-query -l ` in
the command line.


Actual Results:  
An error appears, the wallet is inaccessible.

Expected Results:  
The wallet should work.

The GPG key uses RSA 4096-bit key with no passphrase.

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

[krunner] [Bug 365373] New: Krunner crashed when running konsole

[Lastique via KDE Bugzilla]

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

Bug ID: 365373
   Summary: Krunner crashed when running konsole
   Product: krunner
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@privat.broulik.de
  Reporter: andy...@mail.ru

Application: krunner (5.5.5)

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

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

I pressed Alt+F2 and typed "konsole". Krunner crashed after I pressed Enter.

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

Thread 20 (Thread 0x7f6d08ff9700 (LWP 17310)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6d493d6aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1bfd670) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x16b3f00,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f6d25d6c50b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x18cbcb0, th=) at ../../src/weaver.cpp:594
#4  0x7f6d25d6d2bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x18cbcb0,
th=th@entry=0x7f6d14003a00, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554
#5  0x7f6d25d714e8 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:66
#6  0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#7  0x7f6d25d71542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:73
#8  0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#9  0x7f6d25d71542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:73
#10 0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#11 0x7f6d25d71542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:73
#12 0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#13 0x7f6d25d71542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:73
#14 0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#15 0x7f6d25d71542 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6d14003a00, wasBusy=) at
../../src/workinghardstate.cpp:73
#16 0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6d14003a00, wasBusy=) at ../../src/weaver.cpp:568
#17 0x7f6d25d6f353 in ThreadWeaver::Thread::run (this=0x7f6d14003a00) at
../../src/thread.cpp:103
#18 0x7f6d493d584e in QThreadPrivate::start (arg=0x7f6d14003a00) at
thread/qthread_unix.cpp:331
#19 0x7f6d46f2f6fa in start_thread (arg=0x7f6d08ff9700) at
pthread_create.c:333
#20 0x7f6d48cebb5d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 19 (Thread 0x7f6d097fa700 (LWP 17309)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f6d493d6aeb in QWaitConditionPrivate::wait
(time=18446744073709551615, this=0x1bfd670) at
thread/qwaitcondition_unix.cpp:136
#2  QWaitCondition::wait (this=, mutex=0x16b3f00,
time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208
#3  0x7f6d25d6c50b in
ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked
(this=this@entry=0x18cbcb0, th=) at ../../src/weaver.cpp:594
#4  0x7f6d25d6d2bf in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x18cbcb0,
th=th@entry=0x7f6cd4002b90, threadWasBusy=threadWasBusy@entry=false,
suspendIfInactive=suspendIfInactive@entry=false,
justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554
#5  0x7f6d25d714e8 in ThreadWeaver::WorkingHardState::applyForWork
(this=0x1fec960, th=0x7f6cd4002b90, wasBusy=) at
../../src/workinghardstate.cpp:66
#6  0x7f6d25d6c46d in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f6cd4002b90, wasBusy=) at ../../src/weaver.cpp:568
#7  

[dolphin] [Bug 365216] Dolphin fails to copy a particular directory

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99936
  --> https://bugs.kde.org/attachment.cgi?id=99936=edit
Dolphin error.

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

[dolphin] [Bug 365216] New: Dolphin fails to copy a particular directory

[Lastique via KDE Bugzilla]

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

Bug ID: 365216
   Summary: Dolphin fails to copy a particular directory
   Product: dolphin
   Version: 15.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: andy...@mail.ru

I have this directory tree under /mnt/e/Videos:

Homeland
└── Homeland 4 - LostFilm.TV [1080p]
├── Homeland.S04E01.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E02.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E03.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E04.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E05.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E06.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E07.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E08.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E09.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E10.1080p.rus.LostFilm.TV.mkv
├── Homeland.S04E11.1080p.rus.LostFilm.TV.mkv
└── Homeland.S04E12.1080p.rus.LostFilm.TV.mkv

When trying to copy this tree to a different location (another partition),
Dolphin fails with an error (see attached screenshot). Dolphin is running in
two panel mode. I'm copying the Homeland directory by dragging it from the
right panel to the left one. This error does not appear when I copy different
directories, including from the same /mnt/e/Videos directory. I can copy
Homeland without errors to the intended target directory without errors in
Midnight Commander.

/mnt/e/Videos is on an XFS partition. Target filesystems don't seem to matter
(I tried ntfs-3g and ext4).

Reproducible: Always

Steps to Reproduce:
1. Drag Homeland directory to a different location.


Actual Results:  
An error appears (see the attached screenshot).

Expected Results:  
No error should appear.

Kubuntu 16.04, x86_64.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

--- Comment #4 from Lastique  ---
(In reply to Michael Mikowski from comment #3)
> I also ran into this problem today, but it might just be a problem with
> Google Imap because now works.

Thunderbird worked fine with the same account while Kmail did not. If this is a
problem related to GMail then I guess some workaround is present in Thunderbird
and missing in Akonadi.

> Can you try auto-detecting the server under
> Settings ->  Configure Kmail -> Accounts -> Receiving -> Modify (selected
> account) -> Advanced ->  Auto Detect (under Connection Settings)? Does it
> now work?

No, it's the same. Even after I restart the IMAP resource and press Check Mail,
it starts syncing and eventually hangs on one of the folders.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
The problem is on Kubuntu 16.04, x86_64.

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

[Akonadi] [Bug 364802] Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

Version|5.1.3   |15.12
  Component|general |IMAP resource
 CC||kdepim-b...@kde.org,
   ||vkra...@kde.org
Product|kmail2  |Akonadi

--- Comment #1 from Lastique  ---
Also when that happens I can see that the email account is hanging "syncing"
some of the folders at 97% and not changing.

I have another IMAP account, also hosted on GMail, and the problem does not
appear with it. It has much less messages in it though.

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

[plasmashell] [Bug 364832] Calendar widget displayed as icon on the desktop

[Lastique via KDE Bugzilla]

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

--- Comment #5 from Lastique  ---
(In reply to Kai Uwe Broulik from comment #4)
> Press and hold, then use the applet handle to resize.

That helped, thanks.

Why is it so unintuitive? I remember the applet handle appeared automatically
before. I would have never guessed I have to hold the mouse for it to appear.

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

[plasmashell] [Bug 364832] Calendar widget displayed as icon on the desktop

[Lastique via KDE Bugzilla]

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

--- Comment #3 from Lastique  ---
(In reply to Kai Uwe Broulik from comment #2)
> Does it help if you make it larger? It should show the full grid when large
> enough.

I can't make it larger, I can only move it. The mouse cursor doesn't change to
the "resize arrows" when I move it over any edge or corner of the widget.

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

[plasmashell] [Bug 364832] Calendar widget displayed as icon on the desktop

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99736
  --> https://bugs.kde.org/attachment.cgi?id=99736=edit
The Calendar widget on the desktop, displayed as icon

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

[plasmashell] [Bug 364832] New: Calendar widget displayed as icon on the desktop

[Lastique via KDE Bugzilla]

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

Bug ID: 364832
   Summary: Calendar widget displayed as icon on the desktop
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Calendar
  Assignee: mklape...@kde.org
  Reporter: andy...@mail.ru
CC: plasma-b...@kde.org

When I add the Calendar widget on the desktop, the widget is displayed as an
icon instead of the calendar.

Reproducible: Always

Steps to Reproduce:
1. Right click on the desktop, click Add Widgets.
2. Select the Calendar widget and drag it on the desktop.


Actual Results:  
The widget is displayed as an icon instead of the actual calendar.

Expected Results:  
The actual calendar should be displayed.

Kubuntu 16.04, x86_64. Nvidia drivers 367.27.

The widget worked initially on this system. At some point I was re-configuring
widgets on the desktop, removed the calendar and added again. That's when the
widget broke. Now I'm having this problem and see no way to fix it. Removing
~/.config/plasma-org.kde.plasma.desktop-appletsrc and re-configuring the
desktop doesn't help - the widget still doesn't work.

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

[kmail2] [Bug 364802] New: Kmail stops syncing with an IMAP account

[Lastique via KDE Bugzilla]

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

Bug ID: 364802
   Summary: Kmail stops syncing with an IMAP account
   Product: kmail2
   Version: 5.1.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: andy...@mail.ru

Sometimes Kmail stops syncing with one of my IMAP accounts (Gmail). It doesn't
download new messages, even if I press the Check Mail button. No errors are
displayed. I know there are messages since I can see them in web interface and
Thunderbird.

Killing akonadi_imap_resource helps sometimes, but not always.


Reproducible: Sometimes

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

[kmail2] [Bug 364800] Unicode subject displayed incorrectly sometimes

[Lastique via KDE Bugzilla]

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

--- Comment #3 from Lastique  ---
Created attachment 99719
  --> https://bugs.kde.org/attachment.cgi?id=99719=edit
The problematic Subject header

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

[kmail2] [Bug 364800] Unicode subject displayed incorrectly sometimes

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
Created attachment 99718
  --> https://bugs.kde.org/attachment.cgi?id=99718=edit
Thunderbird displays subject correctly

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

[kmail2] [Bug 364800] Unicode subject displayed incorrectly sometimes

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99717
  --> https://bugs.kde.org/attachment.cgi?id=99717=edit
Kmail displays subject incorrectly

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

[kmail2] [Bug 364800] New: Unicode subject displayed incorrectly sometimes

[Lastique via KDE Bugzilla]

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

Bug ID: 364800
   Summary: Unicode subject displayed incorrectly sometimes
   Product: kmail2
   Version: 5.1.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: andy...@mail.ru

For some emails with national characters in Subject the subject is displayed
incorrectly in the kmail message list. I attached the Subject header from such
an email and also screenshots of kmail and Thunderbird displaying it.
Thunderbird displays it correctly.

Reproducible: Always

Steps to Reproduce:
1. You just have to receive a message similarly formatted.

Actual Results:  
The subject in kmail contains unrecognized characters.

Expected Results:  
The subject should not contain unknown characters.

Kubuntu 16.04, x86_64.

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

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99643
  --> https://bugs.kde.org/attachment.cgi?id=99643=edit
Crash log

Thread 1 (Thread 0x7f72a10ee900 (LWP 1970)):
[KCrash Handler]
#6  0x7f72a0af2418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#7  0x7f72a0af401a in __GI_abort () at abort.c:89
#8  0x7f729c3abff1 in qt_message_fatal (context=..., message=) at global/qlogging.cpp:1578
#9  QMessageLogger::fatal (this=, msg=) at
global/qlogging.cpp:781
#10 0x7f729f426af1 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#11 0x7f729f42f332 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7f729f42f733 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7f729c8ea2e5 in QWindow::event (this=0x1b5a710, ev=)
at kernel/qwindow.cpp:2060
#14 0x7f729f462871 in QQuickWindow::event(QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#15 0x7f729ce9205c in QApplicationPrivate::notify_helper
(this=this@entry=0x1b15d00, receiver=receiver@entry=0x1b5a710,
e=e@entry=0x7fff647898e0) at kernel/qapplication.cpp:3716
#16 0x7f729ce97516 in QApplication::notify (this=0x1b17220,
receiver=0x1b5a710, e=0x7fff647898e0) at kernel/qapplication.cpp:3499
#17 0x7f729c59f62b in QCoreApplication::notifyInternal (this=0x1b17220,
receiver=receiver@entry=0x1b5a710, event=event@entry=0x7fff647898e0) at
kernel/qcoreapplication.cpp:965
#18 0x7f729c8e24ec in QCoreApplication::sendSpontaneousEvent
(event=0x7fff647898e0, receiver=0x1b5a710) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:227
#19 QGuiApplicationPrivate::processExposeEvent (e=0x2008ed0) at
kernel/qguiapplication.cpp:2663
#20 0x7f729c8e325d in QGuiApplicationPrivate::processWindowSystemEvent
(e=e@entry=0x2008ed0) at kernel/qguiapplication.cpp:1658
#21 0x7f729c8c6f38 in QWindowSystemInterface::sendWindowSystemEvents
(flags=...) at kernel/qwindowsysteminterface.cpp:625
#22 0x7f728e5dbf10 in userEventSourceDispatch (source=) at
eventdispatchers/qeventdispatcher_glib.cpp:70
#23 0x7f7296686127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#24 0x7f7296686380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f729668642c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f729c5f5a7f in QEventDispatcherGlib::processEvents (this=0x1b67590,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#27 0x7f729c59cdea in QEventLoop::exec (this=this@entry=0x7fff64789bb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#28 0x7f72a0ea25c9 in KSMShutdownDlg::exec (this=this@entry=0x1b5a710) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdowndlg.cpp:293
#29 0x7f72a0ea2698 in KSMShutdownDlg::confirmShutdown
(maysd=maysd@entry=true, choose=choose@entry=true, sdtype=@0x7fff64789cdc:
KWorkSpace::ShutdownTypeReboot, bootOption=..., theme=...) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdowndlg.cpp:308
#30 0x7f72a0eb1326 in KSMServer::shutdown (this=0x1ba2190,
confirm=, sdtype=KWorkSpace::ShutdownTypeReboot,
sdmode=KWorkSpace::ShutdownModeInteractive) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/shutdown.cpp:164
#31 0x7f72a0470ad9 in _SmsProcessMessage () from
/usr/lib/x86_64-linux-gnu/libSM.so.6
#32 0x7f72a0261071 in IceProcessMessages () from
/usr/lib/x86_64-linux-gnu/libICE.so.6
#33 0x7f72a0e9a012 in KSMServer::processData (this=0x1ba2190) at
/build/plasma-workspace-kxRFE_/plasma-workspace-5.5.5.2/ksmserver/server.cpp:790
#34 0x7f729c5cde4f in QtPrivate::QSlotObjectBase::call (a=0x7fff64789fe0,
r=0x1ba2190, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#35 QMetaObject::activate (sender=sender@entry=0x1c44d80,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff64789fe0) at kernel/qobject.cpp:3698

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

[ksmserver] [Bug 364593] New: Crash on logout after Nvidia driver update

[Lastique via KDE Bugzilla]

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

Bug ID: 364593
   Summary: Crash on logout after Nvidia driver update
   Product: ksmserver
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ui
  Assignee: l.lu...@kde.org
  Reporter: andy...@mail.ru

Whenever I update Nvidia drivers (as a package update, via Muon or apt-get),
invoking the logout/reboot/shutdown dialog results in ksmserver crash. Often it
is seen that the dialog is not drawn when the crash happens (i.e. the desktop
fades out, according to the logout effect, but the panel with the
logout/reboot/shutdown selection does not appear).

Reproducible: Always

Steps to Reproduce:
1. In KDE, update nvidia drivers to a different version. For example, you can
switch from nvidia-364 to nvidia-367 package or back.
2. Invoke the logout/reboot/shutdown dialog. For example, by pressing the
"Leave" button on the panel (the Lock/Logout widget).


Actual Results:  
ksmserver crashes, the logout dialog does not appear.

Expected Results:  
The crash should not happen.

Kubuntu 16.04 x86_64. Nvidia drivers 367.27.

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

[Powerdevil] [Bug 364592] Controller input does not prevent screen from turning off

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
I'll add that in my case Dualshock 4 is connected via Bluetooth.

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

[Powerdevil] [Bug 364592] New: Controller input does not prevent screen from turning off

[Lastique via KDE Bugzilla]

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

Bug ID: 364592
   Summary: Controller input does not prevent screen from turning
off
   Product: Powerdevil
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: andy...@mail.ru

Controller (Dualshock 4 gamepad) input does not prevent screen energy saving.
As a result the display turns off while one is playing a game with a
controller. 

Reproducible: Always

Steps to Reproduce:
1. Configure a timeout for turning off the screen in the System Settings ->
Power Management.
2. Start a game with a controller support. I use The Talos Principle.
3. Play the game with the gamepad for a while.

Actual Results:  
The screen turns off mid-game after the timeout.

Expected Results:  
Controller input should count as input and prevent the screen from turning off.

Kubuntu 16.04 x86_64, Nvidia drivers 367.27.

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

[ksysguard] [Bug 364325] New: Crash on closing

[Lastique via KDE Bugzilla]

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

Bug ID: 364325
   Summary: Crash on closing
   Product: ksysguard
   Version: 5.5.5
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: andy...@mail.ru

Application: ksysguard (5.5.5)

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

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

System Monitor crashed when I closed its window by pressing X button on the
window decoration.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  0x7fef877dc3e6 in QLabelPrivate::clearContents
(this=this@entry=0x1cd7a80) at widgets/qlabel.cpp:1274
#7  0x7fef877dcf1c in QLabel::setText (this=0x1dd6a60, text=...) at
widgets/qlabel.cpp:282
#8  0x7fef8afdd1a9 in TopLevel::answerReceived (this=0x1dc92b0,
id=, answerList=...) at
/build/ksysguard-2wYzme/ksysguard-5.5.5/gui/ksysguard.cpp:447
#9  0x7fef8a276cc1 in KSGRD::SensorAgent::processAnswer(char const*, int)
() from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#10 0x7fef8a27e5b0 in ?? () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#11 0x7fef86dd2e4f in QtPrivate::QSlotObjectBase::call (a=0x7ffe3ef70cc0,
r=0x1ece3e0, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#12 QMetaObject::activate (sender=sender@entry=0x1e90500,
signalOffset=, local_signal_index=local_signal_index@entry=5,
argv=argv@entry=0x0) at kernel/qobject.cpp:3698
#13 0x7fef86dd37d7 in QMetaObject::activate (sender=sender@entry=0x1e90500,
m=m@entry=0x7fef86fe9400 ,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#14 0x7fef86cd1e03 in QProcess::readyReadStandardOutput
(this=this@entry=0x1e90500) at .moc/moc_qprocess.cpp:266
#15 0x7fef86cda362 in QProcessPrivate::tryReadFromChannel (this=0x1ef0420,
channel=0x1ef0550) at io/qprocess.cpp:966
#16 0x7fef86cda7e0 in QProcessPrivate::_q_canReadStandardOutput
(this=) at io/qprocess.cpp:977
#17 QProcess::qt_static_metacall (_o=, _c=,
_id=, _a=0x7ffe3ef70ec0) at .moc/moc_qprocess.cpp:133
#18 0x7fef86dd2fca in QMetaObject::activate (sender=sender@entry=0x1ead550,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7ffe3ef70ec0) at kernel/qobject.cpp:3713
#19 0x7fef86dd37d7 in QMetaObject::activate (sender=sender@entry=0x1ead550,
m=m@entry=0x7fef86fed780 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe3ef70ec0)
at kernel/qobject.cpp:3578
#20 0x7fef86e5251e in QSocketNotifier::activated
(this=this@entry=0x1ead550, _t1=12) at .moc/moc_qsocketnotifier.cpp:134
#21 0x7fef86ddf47b in QSocketNotifier::event (this=0x1ead550, e=) at kernel/qsocketnotifier.cpp:260
#22 0x7fef8769705c in QApplicationPrivate::notify_helper
(this=this@entry=0x1cd7fc0, receiver=receiver@entry=0x1ead550,
e=e@entry=0x7ffe3ef71130) at kernel/qapplication.cpp:3716
#23 0x7fef8769c516 in QApplication::notify (this=0x7ffe3ef71450,
receiver=0x1ead550, e=0x7ffe3ef71130) at kernel/qapplication.cpp:3499
#24 0x7fef86da462b in QCoreApplication::notifyInternal
(this=0x7ffe3ef71450, receiver=0x1ead550, event=event@entry=0x7ffe3ef71130) at
kernel/qcoreapplication.cpp:965
#25 0x7fef86dfaf45 in QCoreApplication::sendEvent (event=0x7ffe3ef71130,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#26 socketNotifierSourceDispatch (source=0x1d14b30) at
kernel/qeventdispatcher_glib.cpp:101
#27 0x7fef7f8fa127 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fef7f8fa380 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fef7f8fa42c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fef86dfaa7f in QEventDispatcherGlib::processEvents (this=0x1d1cf90,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x7fef86da1dea in QEventLoop::exec (this=this@entry=0x7ffe3ef71340,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x7fef86da9e8c in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#33 0x7fef870ddc3c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1542
#34 0x7fef87693495 in QApplication::exec () at kernel/qapplication.cpp:2976
#35 0x7fef8afdead9 in kdemain (argc=1, argv=) at
/build/ksysguard-2wYzme/ksysguard-5.5.5/gui/ksysguard.cpp:596
#36 0x7fef8abbe830 in __libc_start_main (main=0x400710 ,
argc=1, argv=0x7ffe3ef71598, init=, fini=,
rtld_fini=, stack_end=0x7ffe3ef71588) at ../csu/libc-start.c:291
#37 0x00400749 in _start ()

Possible duplicates by 

[plasmashell] [Bug 363817] Memory status widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99318
  --> https://bugs.kde.org/attachment.cgi?id=99318=edit
Memory status widget on a panel

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

[plasmashell] [Bug 363817] New: Memory status widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

Bug ID: 363817
   Summary: Memory status widget unreadable when placed on panel
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: andy...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Memory status widget becomes unreadable is placed on a horizontal panel because
the memory type overlaps with the consumption readings. The widget has no
settings, so there is no way to remove the memory type or adjust font settings
or anything.

Reproducible: Always

Steps to Reproduce:
1. Add a memory status widget to a horizontal panel.

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

[plasmashell] [Bug 363816] Network monitor widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99317
  --> https://bugs.kde.org/attachment.cgi?id=99317=edit
Network monitor on a panel

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

[plasmashell] [Bug 363816] New: Network monitor widget unreadable when placed on panel

[Lastique via KDE Bugzilla]

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

Bug ID: 363816
   Summary: Network monitor widget unreadable when placed on panel
   Product: plasmashell
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: andy...@mail.ru
CC: bhus...@gmail.com, plasma-b...@kde.org

Network monitor widget becomes unreadable is placed on a horizontal panel
because the network interface name overlaps with the bandwidth readings. The
widget has no settings, so there is no way to remove the interface name or
adjust font settings or anything.


Reproducible: Always

Steps to Reproduce:
1. Add a network monitor widget to a horizontal panel.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

  Attachment #99313|0   |1
is obsolete||

--- Comment #22 from Lastique  ---
Created attachment 99316
  --> https://bugs.kde.org/attachment.cgi?id=99316=edit
Screencast showing opacity changes when opening windows

Sorry, I mixed up two of by bugs.

Here's a screencast of opacity changes when blur is enabled. Pay attention to
the panels.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

  Attachment #99314|0   |1
is obsolete||

--- Comment #13 from Lastique  ---
Created attachment 99315
  --> https://bugs.kde.org/attachment.cgi?id=99315=edit
Screencast showing undrawn decorations

Sorry, I mixed up two of by bugs.

(In reply to Lastique from comment #11)
> I put KWIN_USE_BUFFER_AGE=0 to /etc/environment a few days ago and so far I
> haven't seen any flickering textures. I can't be 100% sure this fixes the
> problem but it does make things better.
> 
> Note: My vsync mode is "Automatic".

And there you go. A few minutes later after I wrote the message I re-enabled
the Blur effect and got un-drawn window decorations. No flickering though. Also
I noticed that the decorations are affected by the nearby windows. See the
attached screencast.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #12 from Lastique  ---
Created attachment 99314
  --> https://bugs.kde.org/attachment.cgi?id=99314=edit
Screencast showing opacity changes when opening windows

Here's a screencast of opacity changes when blur is enabled. Pay attention to
the panels.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #21 from Lastique  ---
Created attachment 99313
  --> https://bugs.kde.org/attachment.cgi?id=99313=edit
Screencast showing undrawn decorations

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #20 from Lastique  ---
(In reply to Lastique from comment #19)
> 
> I tried disabling blur and indeed opacity changes have disappeared.

And there you go. A few minutes later after I wrote the message I re-enabled
the Blur effect and got un-drawn window decorations. No flickering though. Also
I noticed that the decorations are affected by the nearby windows. See the
screencast.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #11 from Lastique  ---
I put KWIN_USE_BUFFER_AGE=0 to /etc/environment a few days ago and so far I
haven't seen any flickering textures. I can't be 100% sure this fixes the
problem but it does make things better.

Note: My vsync mode is "Automatic".

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #19 from Lastique  ---
(In reply to Thomas Lübking from comment #18)
> Meh - blur (next to contrast) is by it's nature still a major contender to
> be the culprit.
> => If you can reproduce it with disabled blur, it might be helpful to see a
> video of what's actually going one.

I tried disabling blur and indeed opacity changes have disappeared.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #17 from Lastique  ---
(In reply to Thomas Lübking from comment #16)
> "kcmshell5 kwineffects", filter for "blur", configure the effect and disable
> the blur cache (only checkbox)
> Still reproducible?

That option is already disabled.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #15 from Lastique  ---
Created attachment 99191
  --> https://bugs.kde.org/attachment.cgi?id=99191=edit
KWin log

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #14 from Lastique  ---
(In reply to Thomas Lübking from comment #13)
> No. Explanation:

Thanks for the explanation, makes sense. I thought I was going crazy. :)

> Does the panel opacity change still happen?

I didn't manage to reproduce the "very transparent panels" case since I started
to collect the log. But I can still see the panels becoming more opaque at
times.

This is typically easier to reproduce right after a reboot. For example, on a
freshly booted system I start QtCreator 4.0.0 and can see the lower panel
blinking to more opaque and back twice as QtCreator starts. Another case is
clicking on the Networks icon in the system tray (the panel blinks once).
Another case is opening System Settings -> Desktop Behavior -> Desktop Effects
(the panel blinks once). Performing the same actions the second time does not
cause panel blinks, at least not if done soon after the first time.

I saved the kwin output while I was experimenting (attached). I did not notice
any particular messages appearing when the panel blinks.

I can add that the glowing effect/shadow around the window decorations are not
affected when the above blinks happen. These effects are not shown when
compositing is disabled, so the problem is indeed not caused by compositing
restart.

> (The hanging GL call might be a rather unrelated issue - notably if not
> reproducible.)

No hangs on 364.19 so far. Although I haven't reproduced the "very transparent
panels" either, which is when kwin hung.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #11 from Lastique  ---
Created attachment 99182
  --> https://bugs.kde.org/attachment.cgi?id=99182=edit
An example of a panel without contrast effect

I've attached a screenshot without the contrast effect.

Curiously, I got used to this effect fixing the panels so much that I didn't
disable it for years. Now, when I tried to disable it and surprisingly, after a
few seconds the panels "fixed" themselves, as if the effect have been
re-enabled. The effect is clearly disabled in the settings but the panels look
as if it's on. This happens every time when I disable the effect - the panels
go dark for a second or two and then back to light again. Is it possible that
the effect is somehow force-enabled somewhere?

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #12 from Lastique  ---
(In reply to Thomas Lübking from comment #10)
> 
> Let me guess: disabling the blur effect will "fix" this (by selecting the
> more opaque plasma panel theme)?

Nope, the behavior is the same as I described in the #11. Except, well, the
desktop background is not blurred behind panels.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #9 from Lastique  ---
(In reply to Thomas Lübking from comment #8)
> 
> I'd suggest to simply disable it. *shrug*

I would but without it the panels are nearly unusable with a dark desktop
background. Fonts are barely readable because the panel is too dark.

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

[kmix] [Bug 347503] Volume meter is black regardless of desktop theme

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
The problem is fixed in Kubuntu 16.04.

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

[kmail2] [Bug 354727] Kmail has default icon in the task manager

[Lastique via KDE Bugzilla]

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

--- Comment #6 from Lastique  ---
The problem is fixed in Kubuntu 16.04.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #7 from Lastique  ---
> Did you have those restarts on the stable driver as well?

Yes, the panels did reset* on 364.19 too, but kwin did not hang. The hang only
happened once, on 367.18, but I haven't been using it for long (I updated the
driver yesterday and reverted back to 364.19 now).

* By 'reset' I mean I can see their opacity change suddenly. Either they
temporarily become opaque or very transparent, as if the Contrast effect is
disabled. Shortly after they restore their normal display.

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

[konsole] [Bug 362416] Switching between tabs is slow

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
Another way to see the slow interface update is to try minimizing and restoring
Konsole window. When the window is restored, you can see part of the underlying
desktop for about 500 ms before the Konsole window contents appear.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #4 from Lastique  ---
Created attachment 99178
  --> https://bugs.kde.org/attachment.cgi?id=99178=edit
KWin support info

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #5 from Lastique  ---
(In reply to Thomas Lübking from comment #4)
> https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Disable_framebuffer
> 
> Ubuntu should be using /etc/default/grub as well ( just they've no useful
> documentations ;-P )

Thanks. I got rid of the warning now.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #3 from Lastique  ---
> I'd suggest trying a stable driver (367.18 is a beta version) to see whether 
> the same issues occur there as well.

364.19 is the stable one, it happened with it too. I updated trying if the new
version fixed anything.

> maybe dmesg holds valuable information (cc., ensure there's no NVRM warning 
> about using unsupported framebuffer consoles)

dmesg has this warning:

[4.137728] NVRM: Your system is not currently configured to drive a VGA
console
[4.137730] NVRM: on the primary VGA device. The NVIDIA Linux graphics
driver
[4.137731] NVRM: requires the use of a text-mode VGA console. Use of other
console
[4.137732] NVRM: drivers including, but not limited to, vesafb, may result
in
[4.137732] NVRM: corruption and stability problems, and is not supported.

I'm not sure how to fix this. I didn't configure any console drivers.

> If kwin restarts *completely* (to recover from a crash), please ensure to 
> have drkonqi installed and provide the segfault/abort backtrace ("developer 
> information" tab)

The KDE crash handler doesn't start when this happens; I don't think kwin
process crashes.

> it would be good to see the initial error which caused the restart (start 
> "kwin_x11 --replace &" from konsole and trigger it)

Ok, I will try this. But since I don't have a repro, this may take a while.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #2 from Lastique  ---
I forgot to mention that I tried switching from Automatic refresh to Full
screen repaints, it didn't help.

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

[kwin] [Bug 363500] Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99174
  --> https://bugs.kde.org/attachment.cgi?id=99174=edit
Undrawn decorations screenshot

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

[kwin] [Bug 363500] New: Flickering and incompletely drawn textures

[Lastique via KDE Bugzilla]

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

Bug ID: 363500
   Summary: Flickering and incompletely drawn textures
   Product: kwin
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: andy...@mail.ru

Sometimes I can see flickering or incompletely drawn textures around the
desktop. For example, I once saw part of the Firefox window, which was opened
on one monitor, flicker on the other monitor (which had no open windows, i.e.
it flickered on the desktop). Another time window decorations were either
flickering or not drawn at all for different applications. I took a screenshot
of this case (attached). When I moved the mouse over the decoration, it starts
to flicker more frequently, and if I move mouse over the decoration buttons,
they are drawn in squares, with the rest of the decoration not drawn.

Reproducible: Sometimes

Steps to Reproduce:
I don't know a reliable way to reproduce this.



Kubuntu 16.04, x86_64. Nvidia driver 367.18. The flicker also happened with
364.19. OpenGL interface: GLX, rendering backend: OpenGL 3.1. Desktop theme:
Breeze, window decorations: org.kde.oxygen.

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

[kwin] [Bug 363499] kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
Created attachment 99173
  --> https://bugs.kde.org/attachment.cgi?id=99173=edit
A backtrace of the looping kwin

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

[kwin] [Bug 363499] New: kwin occasionally restarts compositing and hangs

[Lastique via KDE Bugzilla]

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

Bug ID: 363499
   Summary: kwin occasionally restarts compositing and hangs
   Product: kwin
   Version: 5.5.5
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: andy...@mail.ru

Occasionally, I can see compositing being restarted at random actions, like
opening or closing application windows. This can be seen as flickering
semi-transparent panels on the desktop, as if the "Background contrast" effect
has been disabled and re-enabled. One time kwin hung while doing this and stuck
in an infinite loop, desktop unresponsive. I saved a few backtraces while it
was hanging. They were the same, so I attached only one. strace only shows
"clock_gettime(CLOCK_MONOTONIC, {90155, 71576276}) = 0" call in a loop (the
numbers change).


Reproducible: Sometimes

Steps to Reproduce:
I don't know a reliable way to reproduce this.



Kubuntu 16.04, x86_64. Nvidia driver 367.18. The restarts also happened with
364.19. OpenGL interface: GLX, rendering backend: OpenGL 3.1. Desktop theme:
Breeze, window decorations: org.kde.oxygen.

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

[konsole] [Bug 362416] Switching between tabs is slow

[Lastique via KDE Bugzilla]

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

--- Comment #1 from Lastique  ---
I should add that the console input is not delayed - the keypresses are
immediately shown in the console. Browsing the main menu and tabs in Konsole
settings are also not affected.

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

[konsole] [Bug 362416] New: Switching between tabs is slow

[Lastique via KDE Bugzilla]

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

Bug ID: 362416
   Summary: Switching between tabs is slow
   Product: konsole
   Version: 15.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: tabbar
  Assignee: konsole-de...@kde.org
  Reporter: andy...@mail.ru

Switching between multiple tabs in Konsole happens with a noticeable delay.


Reproducible: Always

Steps to Reproduce:
1. Open Konsole with a few tabs.
2. Try switching between the tabs by pressing Shift+Left/Shift+Right or with
mouse.
3. See how fast the actual switching happens.

Actual Results:  
In my case there is noticeable delay between the key is pressed and the tab is
actually switched (I guess about 200-500 ms).

Expected Results:  
The tab should switch immediately.

Kubuntu 16.04 x86_64, Nvidia drivers 364.19. I don't have this problem with
Yakuake on the same machine. Other applications (KDE or not) with tabs also
don't exhibit delays when switching tabs.

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

[plasmashell] [Bug 354731] Black or incorrect textures in different places of UI

[Lastique via KDE Bugzilla]

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

--- Comment #16 from Lastique  ---
Still happens to me in Kubuntu 16.04 with Plasma 5.5.5. Will this ever be
fixed? This is a show stopper bug for me.

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

[plasmashell] [Bug 354731] Black or incorrect textures in different places of UI

[Lastique via KDE Bugzilla]

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

Lastique  changed:

   What|Removed |Added

 Status|NEEDSINFO   |UNCONFIRMED
 Resolution|WAITINGFORINFO  |---

--- Comment #14 from Lastique  ---
(In reply to David Edmundson from comment #13)
> >That variable is already set.
> 
> By whom?

By me. I've added it to /etc/environment to fix crashes in different KDE apps,
such as System Settings. See https://bugs.kde.org/show_bug.cgi?id=344651 for
example.

> Can you try unsetting it then?

It doesn't change anything, the texture corruption was present even before I
added this variable.

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

[muon] [Bug 358659] New: Muon package manager does not close

[Lastique via KDE Bugzilla]

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

Bug ID: 358659
   Summary: Muon package manager does not close
   Product: muon
   Version: 5.4.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: muon
  Assignee: echidna...@kubuntu.org
  Reporter: andy...@mail.ru
CC: aleix...@kde.org, sit...@kde.org

The main package manager window does not close. Neither Alt+F4 nor the X button
in the window decoration close the application - it seem to simply ignore these
events. It does close if I select File->Quit. It also closes if I send SIGINT
to the process. No other applications on the machine exhibit this problem.

Reproducible: Always

Steps to Reproduce:
1. Start Muon package manager.
2. Try to close it by pressing Alt+F4 or the close window button in the window
decoration.


Actual Results:  
The application doesn't close.

Expected Results:  
The application should close.

The problem started to happen after a recent update. KDE is installed from
kubuntu-backports.

Kubuntu 15.10, x86_64.

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

[ksysguard] [Bug 358660] New: KSystemGuard crashed on closing

[Lastique via KDE Bugzilla]

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

Bug ID: 358660
   Summary: KSystemGuard crashed on closing
   Product: ksysguard
   Version: 5.5.3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: andy...@mail.ru

Application: ksysguard (5.5.3)

Qt Version: 5.5.1
Operating System: Linux 4.2.0-25-generic x86_64
Distribution: Ubuntu 15.10

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

KSystemGuard application crashed when I closed it. The crash doesn't happen
every time, though.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  operator== (s1=..., s2=...) at tools/qstring.cpp:2553
#7  0x7fd766c0cbd7 in QLabel::setText (this=0x754550, text=...) at
widgets/qlabel.cpp:276
#8  0x7fd76a410239 in TopLevel::answerReceived (this=0x744020,
id=, answerList=...) at ../../gui/ksysguard.cpp:447
#9  0x7fd7696a8d11 in KSGRD::SensorAgent::processAnswer(char const*, int)
() from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#10 0x7fd7696b0620 in ?? () from /usr/lib/x86_64-linux-gnu/libksgrd.so.7
#11 0x7fd766200777 in QtPrivate::QSlotObjectBase::call (a=0x7fff4c3349e0,
r=0x841390, this=) at
../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124
#12 QMetaObject::activate (sender=sender@entry=0x83bc60,
signalOffset=, local_signal_index=local_signal_index@entry=5,
argv=argv@entry=0x0) at kernel/qobject.cpp:3698
#13 0x7fd7662010e7 in QMetaObject::activate (sender=sender@entry=0x83bc60,
m=m@entry=0x7fd766417360 ,
local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x0) at
kernel/qobject.cpp:3578
#14 0x7fd7660ff1b3 in QProcess::readyReadStandardOutput
(this=this@entry=0x83bc60) at .moc/moc_qprocess.cpp:266
#15 0x7fd766107822 in QProcessPrivate::tryReadFromChannel (this=0x85f9f0,
channel=0x85fb20) at io/qprocess.cpp:966
#16 0x7fd766107ca0 in QProcessPrivate::_q_canReadStandardOutput
(this=) at io/qprocess.cpp:977
#17 QProcess::qt_static_metacall (_o=, _c=,
_id=, _a=0x7fff4c334be0) at .moc/moc_qprocess.cpp:133
#18 0x7fd7662008ea in QMetaObject::activate (sender=sender@entry=0x7e3eb0,
signalOffset=, local_signal_index=local_signal_index@entry=0,
argv=argv@entry=0x7fff4c334be0) at kernel/qobject.cpp:3713
#19 0x7fd7662010e7 in QMetaObject::activate (sender=sender@entry=0x7e3eb0,
m=m@entry=0x7fd76641b6e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff4c334be0)
at kernel/qobject.cpp:3578
#20 0x7fd7662801fe in QSocketNotifier::activated (this=this@entry=0x7e3eb0,
_t1=12) at .moc/moc_qsocketnotifier.cpp:134
#21 0x7fd76620cd9b in QSocketNotifier::event (this=0x7e3eb0, e=) at kernel/qsocketnotifier.cpp:260
#22 0x7fd766ac69dc in QApplicationPrivate::notify_helper
(this=this@entry=0x6639e0, receiver=receiver@entry=0x7e3eb0,
e=e@entry=0x7fff4c334e50) at kernel/qapplication.cpp:3716
#23 0x7fd766acbea6 in QApplication::notify (this=0x7fff4c335170,
receiver=0x7e3eb0, e=0x7fff4c334e50) at kernel/qapplication.cpp:3499
#24 0x7fd7661d1d7b in QCoreApplication::notifyInternal
(this=0x7fff4c335170, receiver=0x7e3eb0, event=event@entry=0x7fff4c334e50) at
kernel/qcoreapplication.cpp:965
#25 0x7fd7662289bd in QCoreApplication::sendEvent (event=0x7fff4c334e50,
receiver=) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:224
#26 socketNotifierSourceDispatch (source=0x698d90) at
kernel/qeventdispatcher_glib.cpp:101
#27 0x7fd75ed14ff7 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7fd75ed15250 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#29 0x7fd75ed152fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#30 0x7fd7662284ef in QEventDispatcherGlib::processEvents (this=0x698ee0,
flags=...) at kernel/qeventdispatcher_glib.cpp:418
#31 0x7fd7661cf50a in QEventLoop::exec (this=this@entry=0x7fff4c335060,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#32 0x7fd7661d75ec in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1229
#33 0x7fd76650bd1c in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1530
#34 0x7fd766ac2e15 in QApplication::exec () at kernel/qapplication.cpp:2976
#35 0x7fd76a411b5d in kdemain (argc=1, argv=) at
../../gui/ksysguard.cpp:594
#36 0x7fd769ff0a40 in __libc_start_main (main=0x400730 ,
argc=1, argv=0x7fff4c3352b8, init=, fini=,
rtld_fini=, stack_end=0x7fff4c3352a8) at libc-start.c:289
#37 0x00400769 in _start ()

Possible duplicates by query: bug 348751, bug 347662.

Reported using DrKonqi

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

[ktorrent] [Bug 356559] New: Downloading to ntfs-3g partition blocks UI

[Lastique via KDE Bugzilla]

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

Bug ID: 356559
   Summary: Downloading to ntfs-3g partition blocks UI
   Product: ktorrent
   Version: 4.3.1
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: andy...@mail.ru

When downloading large torrents to an ntfs-3g partition ktorrent UI
periodically blocks for a long time (tens of seconds). Keyboard and mouse
events are buffered until UI unblocks for a few seconds and after that it
blocks again. This happens while the torrent is being downloaded; UI becomes
responsive again when the torrent finishes downloading. The UI is not blocked
when seeding torrents from an ntfs-3g partition.

Reproducible: Always

Steps to Reproduce:
1. Add a large torrent (30 Gb or more) to ktorrent and choose an ntfs-3g
partition as the target. Make sure it starts downloading (i.e. ktorrent is
receiving data).
2. Try interacting with ktorrent UI. E.g. click on different torrents in the
download list, open contextual menu, click on the File/Edit/View... menu, etc.


Actual Results:  
At certain points UI blocks, without CPU load. HDD seems not loaded as well.
While UI is blocked, network transfers are not happening (network receive and
send meters drop to 0).

Expected Results:  
The UI should remain responsive at all times. Preferably, network transfers
should also remain active. At least some torrents may be on different
filesystems and not blocked by write operations.

I have saved and attached a backtrace of ktorrent while it is blocked.

Kubuntu 15.10, x86_64.

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