[bts-link] source package okular

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package okular # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #540600 (http://bugs.debian.org/540600) # Bug title: okular: fails to search from

[bts-link] source package kmplot

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package kmplot # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #683855 (http://bugs.debian.org/683855) # Bug title: incorrect extrema for second

[bts-link] source package kde-workspace

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package kde-workspace # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #684065 (http://bugs.debian.org/684065) # Bug title: plasma-widgets-workspace:

[bts-link] source package src:kdemultimedia

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package src:kdemultimedia # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #626908 (http://bugs.debian.org/626908) # Bug title: kdemultimedia:

[bts-link] source package kde-baseapps

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package kde-baseapps # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #683481 (http://bugs.debian.org/683481) # Bug title: dolphin: Folder names in

Bug#684513: okular: unable to search

2012-08-10 Thread Markus Schölzel
Package: okular Version: 4:4.8.4-2 Severity: important to reproduce: 1. open okular 2. Edit - Find... 3. Search for something okular: Installed: 4:4.8.4-2 Candidate: 4:4.8.4-2 Version table: *** 4:4.8.4-2 0 500 http://http.debian.net/debian/ sid/main amd64 Packages 500

Bug#684515: okular: unable to search

2012-08-10 Thread Markus Schölzel
Package: okular Version: 4:4.8.4-2 Severity: important reproduce: 1. Open a file in okular 2. Edit - Find 3. Search for something -- Markus Schölzel -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')

Processed: Re: Bug#684515: okular: unable to search

2012-08-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 684515 src:qt4-x11 Bug #684515 [okular] okular: unable to search Bug reassigned from package 'okular' to 'src:qt4-x11'. No longer marked as found in versions okular/4:4.8.4-2. Ignoring request to alter fixed versions of bug #684515 to the

[bts-link] source package kde-baseapps

2012-08-10 Thread bts-link-upstream
# # bts-link upstream status pull for source package kde-baseapps # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #683481 (http://bugs.debian.org/683481) # Bug title: dolphin: Folder names in

Bug#684515: okular: unable to search

2012-08-10 Thread Liang Guo
I confirm this bug, When searching something in okular, okular freeze, I can do nothing except restart okular On Saturday, August 11, 2012, Markus Schölzel wrote: Package: okular Version: 4:4.8.4-2 Severity: important reproduce: 1. Open a file in okular 2. Edit - Find 3. Search for

Re: [Nepomuk] Fwd: Re: kmail freeze when inserting something from addressbook into composer and then sending mail

2012-08-10 Thread David Faure
On Thursday 09 August 2012 22:06:16 Martin Steigerwald wrote: But maybe after I found out that sending SIGTERM to a process /usr/bin/nepomukservicestub nepomukqueryservice makes KMail continue sending the mail I thought I ask here whether this rings a bell and there might be some bugfix /

bug 675151: kmail vs akonadi?

2012-08-10 Thread Martin Albrecht
Hi, I tried - unsuccessfully - to get to the bottom of bug 675151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675151 I believe this to be a Debian bug and not a bug upstream is concerned about because upstream moved away from KMail 1 a while ago. As far as I can tell

Re: [Nepomuk] Fwd: Re: kmail freeze when inserting something from addressbook into composer and then sending mail

2012-08-10 Thread Martin Steigerwald
Am Freitag, 10. August 2012 schrieb David Faure: On Thursday 09 August 2012 22:06:16 Martin Steigerwald wrote: But maybe after I found out that sending SIGTERM to a process /usr/bin/nepomukservicestub nepomukqueryservice makes KMail continue sending the mail I thought I ask here whether

Re: [Nepomuk] Fwd: Re: kmail freeze when inserting something from addressbook into composer and then sending mail

2012-08-10 Thread David Faure
On Friday 10 August 2012 12:27:48 Martin Steigerwald wrote: Am Freitag, 10. August 2012 schrieb David Faure: On Thursday 09 August 2012 22:06:16 Martin Steigerwald wrote: But maybe after I found out that sending SIGTERM to a process /usr/bin/nepomukservicestub nepomukqueryservice makes

Re: bug 675151: kmail vs akonadi?

2012-08-10 Thread Diederik de Haas
On Friday 10 August 2012 12:19:50 Martin Albrecht wrote: As far as I can tell Akonadi::ContactSearchJob *job = new Akonadi::ContactSearchJob(); job-setQuery( Akonadi::ContactSearchJob::Email, email ); job-exec(); always comes back empty regardless of whether there's such an e-mail in

Re: Re: bug 675151: kmail vs akonadi?

2012-08-10 Thread Martin Albrecht
Hi, thanks for this. I am however not sure how exactly this thread relates except for talking about the same object? As far as I can tell the problem I am observing is due to Kmail being still the 1.13.x series in Debian. Or are pointing me to: Enable job tracking in akonadiconsole in

Re: bug 675151: kmail vs akonadi?

2012-08-10 Thread Diederik de Haas
On Friday 10 August 2012 20:02:52 Martin Albrecht wrote: I am however not sure how exactly this thread relates except for talking about the same object? I follow the nepomuk ML and I remembered the code snippet that you posted was also on that ML, so yeah, that was indeed the trigger for my