Hi Kévin and everyone who commented in the bug, thank you for your
report and the comments. Sorry for the long reaction time. As far as I
see it refers to a version of KMail that still uses Nepomuk and is
unmaintained. Thus closing. If you still have issues with sending mail,
please open a new bug
Hi Philip, thank for your report and sorry for taking so long to answer
it.
It is about a version of KMail which uses Nepomuk and is unmaintained. Thus
closing. If you still see performance issues please open new reports. But
please follow the following guide lines to avoid unnecessary work for
(In reply to Chris Wilson from comment #226)
(In reply to Martin Steigerwald from comment #225)
Chris, you referred me to this bug as I reported
Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x, Kicking stuck
semaphore on render ring
I skimmed through it and it appears that
Chris, you referred me to this bug as I reported
Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x, Kicking stuck
semaphore on render ring
I skimmed through it and it appears that there are some patches to test?
But I am not sure which ones these are. Can you or someone else
enlighten me?
(In reply to Chris Wilson from comment #226)
(In reply to Martin Steigerwald from comment #225)
Chris, you referred me to this bug as I reported
Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x, Kicking stuck
semaphore on render ring
I skimmed through it and it appears that
Chris, you referred me to this bug as I reported
Bug 90835 - [4.1-rc6] gpu hang: ecode 6:-1:0x, Kicking stuck
semaphore on render ring
I skimmed through it and it appears that there are some patches to test?
But I am not sure which ones these are. Can you or someone else
enlighten me?
** Branch linked: lp:~vcs-imports/exe1/0
--
mono-jay includes no parser skeleton(s)
https://bugs.launchpad.net/bugs/179215
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Daniel Philipps, developer of Tux3 filesystem, wants to make sure that renames
come after file being written even when delayed writing of metadata is
introduced to it:
http://mailman.tux3.org/pipermail/tux3/2009-March/000829.html
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You
For the application side of things I filed a bug report for KDE:
https://bugs.kde.org/show_bug.cgi?id=187172
--
Ext4 data loss
https://bugs.launchpad.net/bugs/317781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
