scim-bridge was rewritten from scratch and has moved to the scim
package. Please reopen a ticket there if you still experience this
problem. You can reference this bug if what you see is similar
** Changed in: scim-bridge (Ubuntu)
Status: Confirmed = Won't Fix
--
You received this bug
for all those who think that upstream is alive and kicking I have some
recommended reading:
http://bugs.debian.org/591467
http://bugs.debian.org/591468
** Bug watch added: Debian Bug tracker #591467
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591467
** Bug watch added: Debian Bug
resubscribing sponsors on advice from Daniel Holbach
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package scim-bridge - 0.4.16-2ubuntu4
---
scim-bridge (0.4.16-2ubuntu4) maverick; urgency=low
* add some information to the README about crashes induced apparently by
incompatible data structures in old config files. (LP: #338217)
-- Rolf Leggewie
Rolf Leggewie, sorry for assuming that upstream is still alive (due to
the upstream releases). Stating that you are part of upstream would have
given your comment more weight.
** Changed in: scim-bridge (Ubuntu)
Status: Fix Released = Confirmed
--
scim-bridge crashed with SIGSEGV in
** Branch linked: lp:ubuntu/scim-bridge
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: scim-bridge (Ubuntu)
Milestone: ubuntu-10.04.1 = None
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Guys, do as you please. You're not doing Ubuntu a favor by withholding
this documentation, that's for sure. Having it documented is better
than the current situation. Who knows, it's quite well possible this
problem was introduced by one of Ubuntu's ill-guided patches in the
past. FWIW, I
** Tags added: patch
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I see no sign that upstream is dead. Therefore I agree with Daniel.
Please forward the bug report with an example ~/.scim directory tarball
to upstream to get a real fix for this bug. Then come back and
resubscribe ubuntu-sponsors.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() -
** Tags removed: regression-potential verification-done
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This should be forwarded to the upstream developers with a tarball of
the ~/.scim directory that exposes the behaviour. Writing this into the
documentation is not enough to fix this bug.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
** Tags added: regression-potential verification-done
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Daniel, before I comment on #24, let me ask you whether you think the
currently proposed patch is a step in the right direction or not.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug
why is the sponsors team once more sitting on their behinds fiddling
thumbs and doing nothing?
** Changed in: scim-bridge (Ubuntu)
Milestone: None = ubuntu-10.04.1
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
Excuse the maybe ignorant question, but why is it assumed to be just
the way it is if a package chokes on its own config data after an
update? Certainly it should be expected to handle such a conflict in
some graceful way?
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by
Mario, the first time this bug was reported is over two years ago.
Upstream is more or less dead. Ubuntu has moved to ibus.
This is a serious problem, but with an easy enough fix. Feel free to
send a patch if you disagree with the proposed solution. I wish we
could come up with a proper patch.
Oh, I was not aware of the situation as you described it. I understand
now, thanks.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload() - fixed by rm -Rf
~/.scim/
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which
Unfortunately, there is apparently nothing that can be done from the
packaging side. As such, I'm resolving this into a question so that
others can find the explanation how to deal with the issue.
SBKch, please mark it as solved soon.
** Changed in: scim-bridge (Ubuntu)
Status:
I'm resetting this back to a bug for now. My apologies. I skimmed over
Arne's comment 13 too quickly that there is still work left to be done
to properly understand all the issues here.
** Changed in: scim-bridge (Ubuntu)
Status: Invalid = Confirmed
--
scim-bridge crashed with SIGSEGV
hggdh confirmed in #ubuntu-bugs today that the stack traces match. Will
mark as dupe.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the two bugs are now finally merged. It's still unclear how to proceed
from here since there is currently no known fix that does not involve
user intervention.
** Summary changed:
- scim-bridge crashed with SIGSEGV in scim::Module::unload()
+ scim-bridge crashed with SIGSEGV in
Maybe a call to postinst could be added that backs up ~/.scim for all
users, removes that directory and sends a mail to root about this being
done, together with a link to this ticket for further information.
Sounds generally like a good way forward, but I somehow seem to recall
that postinst
Fumbling around user directories from postinst is not a good idea. I
have added some information in the README instead now. That's the best
way to deal with this bug.
See attached patch
** Patch added: LP338217.debdiff
http://launchpadlibrarian.net/39501373/LP338217.debdiff
--
If removing the ~/.scim/ directory resolves this issue, I guess we
cannot fix this bug. It seems to me that it is a configuration conflict
between older versions and the current one. The user needs to do this
step manually anyways as packages are not supposed to delete data in the
users' home
Arne, you asked for this information. What does it mean as far as
fixing this bug is concerned?
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
removing the ~/.scim/ directory, then re-installing the packages
mentioned seems to have remedied the error.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We're seeing a lot of dupes reported for this ticket so it seems that
quite a number of users are affected. Alas, neither Arne nor I seem to
run into this.
Can those affected please report whether the problem remains even after
you remove (or move away) ~/.scim/ and reinstall the scim and scim-
I'm not getting any crash reports in Debian. I wonder if this isn't
again a regression introduced by one of the Ubuntu patches? If so, it
must be one that's been applied for quite a while.
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You
This still happens with 1.4.9-1ubuntu1 as confirmed by rxy in bug 419592
rxy, can you reproduce the problem on every login or does it only happen
sometimes? As Arne said in comment 7, does the problem go away when you
remove (or move away) ~/.scim/ and reinstall scim and scim-bridge?
--
** Tags added: karmic
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
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
Bug still there after all upgrades/updates
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is this bug reproduceable or only after the first login? I'm asking,
because I don't see this crash on my system.
** Changed in: scim-bridge (Ubuntu)
Status: New = Incomplete
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received
Is this the same bug as
https://bugs.edge.launchpad.net/ubuntu/+source/scim-bridge/+bug/199592 ?
Can you please try to remove ~/.scim/ and optionally reinstall the scim and
scim-bridge packages?
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
just upgraded. had been working
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
StacktraceTop:scim::Module::unload (this=0x53454741) at scim_module.cpp:258
~Module (this=0x53454741) at scim_module.cpp:132
ScimBridgeAgentImpl::finalize_scim (this=0x98ca2b8)
ScimBridgeAgentImpl::finalize (this=0x98ca2b8)
~ScimBridgeAgentImpl (this=0x98ca2b8)
** Attachment removed: CoreDump.gz
** Changed in: scim-bridge (Ubuntu)
Sourcepackagename: None = scim-bridge
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Visibility changed to: Public
--
scim-bridge crashed with SIGSEGV in scim::Module::unload()
https://bugs.launchpad.net/bugs/338217
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
38 matches
Mail list logo
