Thanks for the quick response
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Invalid
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "journal_print_crash.txt"
http://launchpadlibrarian.net/18892853/journal_print_crash.txt
--
Kontact crashes on printing Journal-Entries
https://bugs.launchpad.net/bugs/277293
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I was able to reproduce this crash in an updated intrepid using the
steps provided in the original report. Backtrace attached
** Changed in: kdepim (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
--
Kontact crashes on printing Journal-Entries
https://bugs.launchpad.net/b
Thanks for reporting this bug.
Is this bug reproducible every time you try to delete a message this
way? If so could you please install the package kdepim-dbg then induce
the crash again. This should provide a more useful backtrace than the
automatically generated one to help diagnose the problem.
Thanks for reporting this bug.
Is this crash reproducible?
Does it happen every time you subscribe to a group for any group?
If you are able to reproduce the crash please install the package kdepim-dbg
then induce the crash. This should provide a more useful backtrace to help
diagnose the proble
Thanks for reporting this bug.
Does this bug still occur with all current updates installed?
Is it reproducible, i.e. does it happen on every start up?
Thanks
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
akregator crashed with SIGSEGV
https://bugs.launchpad.net/bugs/27887
Thanks for reporting this bug.
Does this bug still occur for you with a fully updated current system
Is this crash reproducible or did it only happen once?
What type of mail accounts do you use imap, pop, disconnected imap, mbox other?
thanks
** Changed in: kdepim (Ubuntu)
Status: New =>
Thanks for reporting this bug.
What type of mail accounts do you use, imap, pop, mbox, other? If you
use more than one type does this crash only occur with a particular
type?
Thanks
** Visibility changed to: Public
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
kontact cra
Thanks for reporting this bug.
Could you give us some idea what you were doing immediately prior to the
crash. For example did it occur when you first started the application
or just after a reboot. We need to try to figure out the steps to
reproduce the crash to be able to fix it. Most importantl
Thanks for reporting this bug. Does this bug still occur for you?
I was unable to reproduce it on my system running intrepid with all
current updates. If this crash still occurs reproducibly please install
the package kdepim-dbg then induce the crash. This should give us a more
useful backtrace to
** Visibility changed to: Public
--
Crashed when tried to open akregator using the kontact environment
https://bugs.launchpad.net/bugs/281262
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.
Thanks for reporting this bug
Does this crash occur reproducibly?
If so could you please install the package kdepim-dbg then induce the crash.
This will help us to get a more useful backtrace so that we can find the cause
of the problem
** Visibility changed to: Public
** Changed in: kdepim (Ub
Thanks for reporting this bug. To find the source of the problem we need more
information.
Most importantly, is the crash reproducible or did it only happen once?
What were you doing immediately before the crash? For example did it occur when
you first booted the machine or when you first starte
Thanks for reporting this bug. If you are still able to reliably induce
this crash please install the package kdepim-dbg then induce the crash.
This package contains the debugging symbols for kdepim. This should give
us a more informative backtrace.
thanks
** Changed in: kdepim (Ubuntu)
St
** Visibility changed to: Public
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282151
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
https://lists.ubuntu.com/ma
Thanks for reporting this bug. I have made this bug private that means
only members of the ubuntu bugcontrol and development teams can view it.
If you attach your core file we can review it for sensitive data. If
there is none we can make the bug public. If there is sensitive data it
can be kept pr
Thanks for reporting this bug. To find the source of this problem we need some
more information.
Most importantly, is this crash reproducible?
Could you give us some more specific steps to induce the crash? For example did
it occur when you clicked on a single article, when you tried to fetch a
** Visibility changed to: Public
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/282658
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/m
If the crash has only happened once it isn't really a reproducible bug.
I'll close this bug but feel free to re-open it if the crash happens
again.
Thanks for your feedback
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Invalid
--
akregator crashed with SIGSEGV
https://bugs.launchp
Thanks for reporting this bug. At the time the crash occurred did leave
akregator running when you shutdown prior to seeing this crash report?
We have seen some reports recently of akregator showing a crash report
on start up when it was left running at shutdown. I'm just trying to
figure out if t
Thanks for reporting this bug. Prior to the crash did you leave
akregator open when you shut down?
We have seen a number of crashes recently with Kontact or components of
kdepim when they are left running on shutdown/reboot. I'm just wondering
if this is related or if this is something different.
Thanks for reporting this bug. Does it crash every time you try to check
mail?
If so could you please install the package kdepim-dbg and induce the
crash. This contains the debugging symbols for kontact. Hopefully it
will give us a more detailed backtrace so we can find the cause of the
problem
*
I've managed to reproduce this on my machine. A full reboot isn't
required. Log out and log back in is sufficient to induce the crash.
Backtrace attached.
Steps to reproduce:
1. Start Kontact
2. Leave Kontact window open and log out
3. Log back in.
4. KDE crash handler appears
My system is Kubunt
*** This bug is a duplicate of bug 287633 ***
https://bugs.launchpad.net/bugs/287633
** This bug has been marked a duplicate of bug 287633
kontact crashed with SIGSEGV
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/285016
You received this bug notification because you are
bug 285016 reports the same bug on i386 so it isn't limited to amd64
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287633
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.ub
** Visibility changed to: Public
--
kontact crashed with SIGSEGV when clicking sent-items
https://bugs.launchpad.net/bugs/285171
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
ht
** Attachment added: "backtrace.txt"
http://launchpadlibrarian.net/1715/backtrace.txt
--
kontact crashed with SIGSEGV when clicking on image
https://bugs.launchpad.net/bugs/286379
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
I can confirm this bug. Reproduced based on the steps in the original
report. Backtrace to follow. The only difference is that I am on i386,
the original report is amd64
** Visibility changed to: Public
** Changed in: kdepim (Ubuntu)
Importance: Undecided => Low
Status: New => Confirmed
Thanks for reporting this bug. Could you clarify the steps you took to induce
the crash.
When you say you tried to open -Settings-, I assume you mean the settings menu
of Kontact/Kmail, correct?
I'm not sure what you mean by another opened kmail. Do you mean a second
instance of the KMail progr
Confirming based on duplication by 2 different users
** Visibility changed to: Public
** Changed in: kdepim (Ubuntu)
Status: New => Confirmed
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287030
You received this bug notification because you are a member of Ubuntu
Bugs,
** Visibility changed to: Public
--
kmail crashed with SIGSEGV when using -Settings-
https://bugs.launchpad.net/bugs/287250
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
https:/
Thanks for reporting this bug. To find the cause of this bug we need some
further information.
Is this crash reproducible, i.e. if you repeat the actions you took does it
crash everytime?
Also, you said you logged out. Did the crash report appear before you logged
out or on the following reboot?
*** This bug is a duplicate of bug 287633 ***
https://bugs.launchpad.net/bugs/287633
** This bug has been marked a duplicate of bug 287633
kontact crashed with SIGSEGV
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287558
You received this bug notification because you are
Confirming based on duplication. There seem to be multiple bug reports
all reporting the same thing. All the ones I've found so far are on
amd64
** Changed in: kdepim (Ubuntu)
Status: New => Confirmed
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287633
You received this
*** This bug is a duplicate of bug 287633 ***
https://bugs.launchpad.net/bugs/287633
** This bug has been marked a duplicate of bug 287633
kontact crashed with SIGSEGV
--
kontact crashed with SIGSEGV on startup
https://bugs.launchpad.net/bugs/287700
You received this bug notification beca
*** This bug is a duplicate of bug 287633 ***
https://bugs.launchpad.net/bugs/287633
Further investigation shows this is a duplicate of bug 287633
** This bug has been marked a duplicate of bug 287633
kontact crashed with SIGSEGV
--
kontact crashed with SIGSEGV on system startup
https://
*** This bug is a duplicate of bug 287633 ***
https://bugs.launchpad.net/bugs/287633
** Visibility changed to: Public
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287558
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Visibility changed to: Public
--
kontact crashed with SIGSEGV
https://bugs.launchpad.net/bugs/287633
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/m
Thanks for reporting this bug. We need some further information to find the
cause of this bug.
Did you have Kontact open when you closed your previous session?
Is the crash reproducible?
This sounds similar to bug 288085 but it's hard to be sure yet.
** Changed in: kdepim (Ubuntu)
Status:
** Visibility changed to: Public
--
kontact crashed with SIGSEGV on startup
https://bugs.launchpad.net/bugs/287700
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
https://lists.ub
Thanks for reporting this bug. We need a bit more information to find the
source of this problem.
Does this crash happen reproducibly every time you try to add a button to the
toolbar?
Does it crash for any button you add or only a specific button?
I tried to reproduce the crash here but was un
Thanks for taking the time to report this bug. Is this crash
reproducible, i.e. if you always leave kontact open when you shutdown
does it always crash when you start up again or has it only happened
once?
** Visibility changed to: Public
** Changed in: kdepim (Ubuntu)
Status: New => Incom
I can confirm this behaviour as described running up to date Kubuntu
Intrepid. Individually configured feeds use the chosen archive settings.
Feeds set to use default settings seem to ignore the default archive
settings. This is a clean install and the only feeds I have configured
are the default s
Further investigation suggests that this bug is already known upstream
https://bugs.kde.org/show_bug.cgi?id=167749
--
Delete articles older than X days for default archive settings not remembered
https://bugs.launchpad.net/bugs/286596
You received this bug notification because you are a member of
This bug us marked Kubuntu 8.10 beta. I just tried to reproduce this bug
on a fully up to date 8.10 install and was unable to do so. I added 10
new contacts consecutively without inducing a crash. Do you still
observe this crash with an up to date system?
Qt: 4.4.3
KDE: 4.1.2 (KDE 4.1.2)
Kontact:
** Visibility changed to: Public
--
knotes crashed with SIGSEGV in _start()
https://bugs.launchpad.net/bugs/284527
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
https://lists.ub
** Visibility changed to: Public
--
akregator crashed with SIGSEGV
https://bugs.launchpad.net/bugs/278871
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
https://lists.ubuntu.com/
** Visibility changed to: Public
--
akregator crashed with SIGSEGV in QCoreApplication::postEvent()
https://bugs.launchpad.net/bugs/282736
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.ubu
Thanks for following up.
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Triaged
--
marking a recurring kontact to-do as complete causes application crash
https://bugs.launchpad.net/bugs/177566
You received this bug notification because you are a member of Kubuntu
Bugs, which is subs
Thanks for the feedback Gary. We're now too close to Intrepid final
release to get this fixed before release. Hopefully we can do something
about it soon after release.
** Changed in: system-config-printer-kde (Ubuntu)
Importance: Undecided => Low
Status: Incomplete => Triaged
--
syste
You're never alone :) It just sometimes takes us longer to respond than
we'd like :) If the crash can't be reproduced I'll close the bug. If the
crash does recur feel free to reopen it.
** Changed in: system-config-printer-kde (Ubuntu)
Status: Incomplete => Invalid
--
system-config-printe
I can also confirm this bug. Upgrade test from Hardy KDE4 remix to
intrepid. This was a VM which had only the default Hardy KDE4 package
set installed. I launched the upgrade with the command kdesudo
'adept_manager --dist-upgrade-devel'
Once the upgrade completed I restarted and tried to log in. I
** Changed in: system-config-printer-kde (Ubuntu)
Importance: Undecided => Wishlist
--
system-config-printer-kde - take out of add/remove
https://bugs.launchpad.net/bugs/278372
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Could you please answer a few questions to clarify the steps that induce this
crash.
Are you saying that if a document is printing and you try to print a test page
then this crash occurs?
Does it happen for any document or is it only if you try to print a test page
immediately followed by a sec
Thanks for reporting this bug. Could you please let us know the exact
steps you took to induce this crash i.e. what application were you
trying to print from etc. Also, what type of printer do you have and how
is it connected to your PC?
The traceback in the crash report implies that the failure o
Does this problem still occur for you? If so could you let us know what
version of Kubuntu/KDE you are currently running?
Could you also let us know what version of system-config-printer-kde you
currently have. You can get this from the output of the command sudo
apt-cache policy system-config-pri
Removed the duplicate against bug 210395. The two are probably related but the
tracebacks are slightly different. This bug has:
Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer-kde.py", line
3011, in on_btnNPApply_clicked
self.show_IPP_Error(
** Visibility changed to: Public
--
Trying to install Epson CX11NF network printer.
https://bugs.launchpad.net/bugs/210395
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
https:/
Thanks for the feedback Jason. I've added this to the wishlist of
features to be added in a future version.
** Changed in: system-config-printer-kde (Ubuntu)
Importance: Undecided => Wishlist
Status: Incomplete => Triaged
--
[kde4] Can't configure advanced printer options
https://bugs.
** Changed in: system-config-printer (Ubuntu)
Importance: Undecided => Wishlist
--
Detect and install Brother printers
https://bugs.launchpad.net/bugs/234822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Thanks for reporting this bug. To the find the source of the problem we
need some further information. If the bug still occurs could you let us
know what version of KDE you are running.
Could you also paste the output of the command sudo apt-cache policy
system-config-printer-kde so we can see wha
Just to clarify so we can try to address the problem. Are you saying the
options you want are present in the GUI but are disabled or are you
saying that these features are absent all together?
thanks
** Changed in: system-config-printer-kde (Ubuntu)
Status: New => Incomplete
--
[kde4] Ca
Re-assigning the package to system-config-printer. The -kde package is
just the front end. The work is done by system-config-printer
** Changed in: system-config-printer (Ubuntu)
Sourcepackagename: system-config-printer-kde => system-config-printer
--
Detect and install Brother printers
https://
*** This bug is a duplicate of bug 206459 ***
https://bugs.launchpad.net/bugs/206459
** This bug has been marked a duplicate of bug 206459
print status doesn't update automatically
--
Document Print Status applet doesn't refresh status
https://bugs.launchpad.net/bugs/246878
You received t
Does this problem still occur?
If so could you tell us what version of KDE you are currently running?
You mention that you have checked the logfile. If you can still reproduce the
problem could you please attach the log to this report so we can try to trace
the problem.
Thanks
** Changed in: sy
Hi,
Sorry for the slow follow up on this. To track down the source of the
problem we need some more information.
This report comes from before the Hardy final release. Do you still
experience this problem in the final release? If so what version of KDE
are you currently running?
** Changed in: s
*** This bug is a duplicate of bug 206459 ***
https://bugs.launchpad.net/bugs/206459
** This bug has been marked a duplicate of bug 206459
print status doesn't update automatically
--
kprinter job list is not updated
https://bugs.launchpad.net/bugs/226627
You received this bug notificatio
Hi,
This should be fixed in later versions of system-config-printer-kde. If
this crash still occurs please let us know.
** Changed in: system-config-printer-kde (Ubuntu)
Status: New => Fix Released
--
system-config-printer-kde.py crashed with IOError in parse()
https://bugs.launchpad.net
As noted in the previous comment this crash hasn't recurred in some time
and there has been no further follow up. Closing Bug. If anyone can
reproduce this feel free to re-open
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Invalid
--
KMail crashes when moving mail in imap folder
ht
This bug is now fixed in an up to date intrepid as of 16/10/2008.
Clicking the edit button brings up the edit event dialogue as decribed
in the upstream report
** Changed in: kdepim (Ubuntu)
Status: Triaged => Fix Released
--
edit button on Korganizer reminder dialog box does not respond
On Fri, Sep 26, 2008 at 12:28 AM, Sergei Ivanov
<[EMAIL PROTECTED]>wrote:
> On Wednesday 24 September 2008, Richard Birnie wrote:
> > Do you still observe this bug in more recent versions of kmail?
>
> Yes I still observe it in hardy.
>
> > I just tried to re
eekend I
> will try to see if I can reproduce the crash with the newest version
> of KMail.
>
> Cheers
>
> On Wed, Sep 24, 2008 at 9:46 PM, Richard Birnie <[EMAIL PROTECTED]>
> wrote:
> > Just updating old bugs. Does this crash still occur with newer versions
>
It sounds like we have a pretty good diagnosis of the problem. Does
anyone still experience this bug in hardy or intrepid or has it been
fixed?
thanks,
Richard
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
kontact hangs on start, uses almost all CPU
https://bugs.launchpad.n
*** This bug is a duplicate of bug 267315 ***
https://bugs.launchpad.net/bugs/267315
Thanks for reporting this bug. This issue is currently being tracked in
bug 267315 and has been reported upstream at
http://bugs.kde.org/show_bug.cgi?id=140041
** This bug has been marked a duplicate of bug 2
thanks for the quick response. In the absence further information I'll
close this report. If similar problems emerge in KDE4 then feel free to
file a new report
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Invalid
--
[gutsy] kmail often crashes during drag'n'drop operations from/t
** Bug watch added: KDE Bug Tracking System #171618
http://bugs.kde.org/show_bug.cgi?id=171618
** Also affects: kdepim via
http://bugs.kde.org/show_bug.cgi?id=171618
Importance: Unknown
Status: Unknown
--
edit button on Korganizer reminder dialog box does not respond
https://bugs
Do you still observe this in Hardy final release. I tried to reproduce
this in Intrepid alpha 6 and found that I was able to drag events or to-
do items around at will and the views updated immediately. This at least
suggests that the bug only exists on KDE3 unless anyone else can confirm
on kde4.
OK having finally got my reminder to trigger under intrepid I can now confirm
that this bug does still exist. As originally reported the edit button doesn't
seem to do anything. I'll forward this upsteam.
kontact --version
Qt: 4.4.2
KDE: 4.1.1
Kontact: 1.3
** Changed in: kdepim (Ubuntu)
S
Does this crash still occur with more recent versions of kmail? If so could you
please provide us with the following information:
what version of kubuntu do you currently use?
What version of kmail currently displays the crash?
If you are able to induce the crash at will could you please install
Does this bug still occur? If so what is the most recent version of
Kubuntu/Korganiser that has the bug?
In particular have you had a chance to see if the bug still occurs in
KDE4?
Sorry for all the questions, just following up on old bugs and seeing
which ones still need attention.
** Changed i
Hi,
Just following up on some old bugs. Do you still observe this problem in newer
versions of kpilot? If so could you let us know:
What version of Kubuntu you currently use?
What version of KDE/kpilot shows the crash?
If the application crashes consistently try starting kpilot from the command
Just following up on some old kdepim bugs. Do you still observe this behaviour?
If so could you let us know the following:
What version of kubuntu are you running?
What version of KDE/kdepim shows this behaviour?
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
Offline to onli
I'm no sure what would cause this. Do you still see this bug with newer
versions of kmail? If so what version and I'll try to reproduce it
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
kmail settings for default account keeps removing default e-mail address
https://bugs.laun
** This bug is no longer a duplicate of bug 156044
kmail settings for default account keeps removing default e-mail address
--
TVTime can not change video source on 7.10
https://bugs.launchpad.net/bugs/156045
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for reporting this bug. Does this problem still occur? If so
could you let us know what version of kubuntu you use as well as what
version of KDE/Korganiser
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
--
korganizer gets confused with timezones
https://bugs.launchpad.ne
Does this crash still occur for you in newer versions of kontact? I
tried to reproduce this behaviour on intrepid with kontact 1.3 and it
doesn't seem to crash from me. If you are still seeing this crash could
you tell us in what version of Kontact/KDE.
If the crash does occur could you try to pro
Does this bug still occur for you?
I just tried to replicate this in Intrepid without success. I sent a
mail with 'disposition notification' selected and clicked on it in my
outbox. Kmail displayed the content of the mail but did not ask for the
read receipt
** Changed in: kdepim (Ubuntu)
This is not a bug so much as a missing feature. This is not something we
can fix at distribution level. If this is still a problem for you raise
it with upstream and report at bugs.kde.org
** Changed in: kdepim (Ubuntu)
Status: New => Invalid
--
sign / encrypt by default are hard to disab
Do you still observe this bug in more recent versions of kmail?
I just tried to reproduce this in both hardy and intrepid both with kde4 and
kmail 1.10.1 using these steps
In Kmail, go to Settings -> Composer -> Charset, try to add "ibm866" to the
list.
In both cases the entry was added to the
Just updating old bugs. Does this crash still occur with newer versions of
kmail? If so could you please let us know:
what version of kubuntu you currently use?
What is the most recent version of KDE/Kmail that shows this crash?
In particular have you observed this crash in KDE4
** Changed in: kd
Thanks for reporting this bug. To find what caused the problem could you
provide the following information:
What version of Kubuntu are you using?
What is the most recent version of KDE/Kmail that shows the crash?
If you can reproduce the crash at will can you install the package
kdepim-dbg and i
This could be a bit difficult to reproduce. It sounds like a config file
got overwritten by the newer package. I notice that this report comes
from before the Hardy release. Have you upgraded to hardy by any chance
and did the same problem occur?
** Changed in: kdepim (Ubuntu)
Status: New =
I'm just following up on some kdepim bugs. Does this problem still occur? If so
could you provide the following information:
What version of kubuntu are you currently using?
What is the most recent version of KDE/Kmail that shows this problem?
Does the problem still exist in KDE4
Sorry for all th
Thanks for reporting this bug. Does this crash still occur? If so could you
please provide the following information for the most recent version of the
crash.
What version of Kubuntu are you currently running?
What version of KDE/Kmail?
If you can reliably induce the crash could you please insta
Thanks for following up on this. Two people have tried to reproduce this
crash based on your test case on both hardy and intrepid systems.
Neither can reproduce it.
If you are able to reproduce this crash then the best course of the
action would be to install the kdepim-dbg package and get a good
Thanks for following up and providing data. I've imported your
feeds.opml into akregator and I'll leave it idling for a while then see
if I can cause the crash.
I'm afraid I wouldn't recognise a corrupt archive but someone else might
be able to use that.
--
akregator crashed with SIGSEGV in Akre
Thanks for following up. If gnome and ubuntu are better suited to your
needs that's fine. I did try to reproduce this based on your description
but without success. In the absence of further information I'll close
the report
** Changed in: kdepim (Ubuntu)
Status: New => Invalid
--
KMail c
Thanks for following this up Michael. I think we can close this now. If
the problem emerges again in KDE4 we'll deal with it then
** Changed in: kdepim (Ubuntu)
Status: Incomplete => Fix Released
--
Kmail configuration changes not applied until application restarted
https://bugs.launchpad
Agreed, that doesn't sound like intended behaviour. It's certainly inconsistent
with other config dialogs if it is.
Does this bug still affect you under hardy?
Is it only the KDE3 version of Kmail or does it also occur under KDE4?
** Changed in: kdepim (Ubuntu)
Status: New => Incomplete
sorry, typo, that should be kdepim-kde4-dbg for kde4 on hardy
--
crash with gmane nntp server and kvm.devel newsgroup
https://bugs.launchpad.net/bugs/209403
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in ubuntu.
--
kubuntu-bugs mail
201 - 300 of 1088 matches
Mail list logo