*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
screenreader was disabled in my system.
but i used gnome-orca and this program comes with a screenreader too.
i deinstalled orca and sysnaptic started again.
--
You received this bug notification because
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
I just tried the fix in #37, and it worked for me as well. I also run
Mint 12, and had this problem with GNOME 3 as well as Cinnamon, but not
Mate. Thanx Mauro (jasmines)!
--
You received this bug
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
The problem is that synaptic currently does not start up when at-spi2 is
enabled. Of course, if you disable at-spi2 as described in #37, the
problem does not happen anymore. But this is not a fix; it simply
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
hi together,
I can also confirm this bug for LinuxMint 12. As I wanted to sue
synaptic for looking something up a few minutes ago, it also crashed
with this abouve mentioned error:
what():
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
Mauro (jasmines)'s fix in #37 worked for me. None of the others did.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
I can confirm this bug for oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
Try:
gsettings set org.gnome.desktop.interface toolkit-accessibility false
It worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 607605 ***
https://bugs.launchpad.net/bugs/607605
** This bug has been marked a duplicate of bug 607605
Synaptic crashes when using orca or Accerciser
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I just have switched dropdown on screen setup from 'ambiance' to
'adwaita'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in __kernel_vsyscall()
To
Confirmation of the comment in #13 : Switching the screen reader on and
back off solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT
When I went to the Language Support in the common Settings dialog it
asked me to install the missing language support packages. After
installation Synaptic started successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am affected, too, in exactly the same way as Jay Ó Broin.
Orca is off; This bug appeared after testing it. I would like not to
perform an os reinstall.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Wait a minute - after removing and purging the orca packages. The bug
still persisted.
But then I remembered the accessibility settings -- screen reader was
set on though itself, as I mentioned, had been removed.
After switching to off my dear synaptic is working properly again ...
:-))
--
You
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in
In my case, error in vector::_M_range_check was caused by user profile.
New clear user has synaptic working. I resolve bug by restoring backup
copy of my /home folder
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After a week consulting LinuxQuestions.org, Ubuntu forums, Ubuntu launchpad
...etc.
finally I find the bug is alive and nobody works fixing it. What a pity.
My outputs:
eu@eu-Vostro-330:~$ gksu synaptic
what(): vector::_M_range_check
instance of 'std::out_of_range'
eu@eu-Vostro-330:~$
In my specific case, reinstalling the latest Ubuntu fixed my bug, but I
wouldn't mark this as fixed since I basically started from zero.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
I also got 0.75.2ubuntu8 installed and I tried switching screen-reader
and screen-keyboard on and off again. The result stays the same:
Synaptic is starting up and showing for about a tenth of a second just
to terminate again.
--
You received this bug notification because you are a member of
BTW dmesg tells me:
[ 1056.663423] synaptic[3747]: segfault at dae4b2a8 ip b68e5410 sp bfc76b8c
error 5 in libc-2.13.so[b68a2000+176000]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
OK I got it working but only when switching to a Theme different from
ambience. I got the idea from
https://bbs.archlinux.org/viewtopic.php?id=118331 which describes a
similar error in that libc-2.13.so
Actually I like the ambience theme and would love to switch back to
it. Only Synaptic then
So I played a bit more and unfortunately simply switching the theme away from
ambiance is not enough since although synaptic started at first it crashed
later on when applying changes and could not be started again even after
changing the themes again.
Here is a serious of the error synaptic
OK I think I could figure what is kind of causing the segfault at least
for me. It's the language environment I'm using.
Steps to reproduce:
~$ export LANG=nb_NO.UTF-8
~$ sudo gdb synaptic
(gdb) run
Starting program: /usr/sbin/synaptic
[Thread debugging using libthread_db enabled]
Program
Dietmar, you've just moved my #874078 over to this bug, and not changed
anything else. I think that's a mistake.
My bug was originally assigned to #839219. I discovered that my bug was
only being triggered by accessibility. I commented this on #839219, as
recommended, and I _modified the bug
Alan, sorry you are right. I thought that that was the same problem. I
just reverted the duplication note of #839219 again (btw I never did
anything to #874078 which doesn't even exist) so that that bug can be
handled by itself.
I hope that clears things up again.
--
You received this bug
Yep, that addresses my concern, thanks! Btw, #874078 does exist, but
I've just noticed that it was marked private :-).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed
So we have the final release without a working proper gui package
manager (I don't count software center as such) :( Any development on
this segfault issue at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Dietmar, actually, it's fixed for me in the latest set of updates:
synaptic:
Installed: 0.75.2ubuntu8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT
Re Dietmar, actually, it's fixed for me in the latest set of upgrades:
synaptic:
Installed: 0.75.2ubuntu8
On Fri, Oct 14, 2011 at 2:45 AM, Dietmar Winkler
807...@bugs.launchpad.netwrote:
So we have the final release without a working proper gui package
manager (I don't count software
*bump*
With only a few days to go before release, I'm still getting problems on
my installation which is completely up to date. When the official
release comes out I'll try for a fresh install though and see how that
works.
--
You received this bug notification because you are a member of
*bump*
it seems crazy to me that this bug has been open for almost three months
with 12 duplicates and being classified as a HIGH priority bug doesn't
have anybody assigned to fix this. obviously the software-center covers
most of the features necessary for average users, but the fact that the
Same problem, synaptic crashes on start. Screen reader and On-screen
keyboard are both off, although I was testing Orca last week.
Update manager starts fine for me though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Strange; My screen reader and on screen keyboard was also off, but I
have just on and off again, and I've just tried synaptic, it's work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
I had this crash after activating Orca... see also bug 839087.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in __kernel_vsyscall()
To manage
Hi, I reported bug 818382 which might be a duplicate of this but the
SIGABRT is slightly different.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in
Could you disable accessibility and tell if this crash occurs again ?
Launch 'gnome-control-center'
Open 'Universal Access'
and set 'Screen Reader' to 'OFF'
Thanks in advance.
** Changed in: synaptic (Ubuntu)
Importance: Medium = High
** Changed in: synaptic (Ubuntu)
Status:
Just checked and screen reader is off now. Crash hasn't happened again.
On 30 July 2011 10:51, Jean-Baptiste Lallement jean-
bapti...@ubuntu.comwrote:
Could you disable accessibility and tell if this crash occurs again ?
Launch 'gnome-control-center'
Open 'Universal Access'
and set 'Screen
Yes, after turning off the screen reader, Synaptic works without
crashing. Thanks!
** Changed in: synaptic (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My system has changed dramatically sine the bug report.
Python 2.6 or 2.7 kept back
And fix broken then Everything that depended on was removed
( didn't realize python was so pervasive in the distro and windowing like
gnome and KDE ...
Anyways, I've not seen synaptic crash again
But worry
I meant to say on screen keyboard, not screen reader.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in __kernel_vsyscall()
To manage notifications about
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807771
Title:
synaptic crashed with SIGABRT in __kernel_vsyscall()
To manage notifications about this bug go to:
40 matches
Mail list logo
