At startup it outputs: "(synaptic:25142): Pango-WARNING **: Invalid
UTF-8 string passed to pango_layout_set_text()". Backtrace in Precise
version:
Program received signal SIGSEGV, Segmentation fault.
0xb7118b8e in vfprintf () from /lib/i386-linux-gnu/libc.so.6
(gdb) backtrace
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when accessibility is enabled, e.g. screen
See bug #952392 for a related problem in Precise.
** 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.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashe
Yes, using the work around others have found works for me too.
On Thu, 2012-03-08 at 11:13 +, Marius Kotsbak wrote:
> Maybe this is a duplicate of bug #787173? Does running:
>
> "sudo LANG=en_EN.utf8 synaptic"
>
> work for you?
>
--
You received this bug notification because you are a me
Maybe this is a duplicate of bug #787173? Does running:
"sudo LANG=en_EN.utf8 synaptic"
work for you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on st
@Phill: On Precise, it's not enough to enable the on-screen keyboard, as
I can run these two simultaneously without synaptic crashing. See my
screenshot.
To find out the version of synaptic you are running, please open a
terminal and run the command: apt-cache policy synaptic
** Attachment added:
Just for clarity, enabling the on-screen keyboard on it's own is enough
to cause this crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with
@Christopher (soft-kristal) - which Synaptic version did you confirm this? I
have tried using the latest with Screen reader enabled, and it did work as
expected.
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad
** Changed in: synaptic (Ubuntu)
Status: Confirmed => I
** 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.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [O
Could anyone reconfirm this with the latest updates applied on Precise? This
seems to be a duplicate of bug #607605, which states that in 0.75.5~exp2 and
later this issue is fixed, and the fix has been validated on 10th of February,
aka 6 days ago.
---
Ubuntu Bug Squad volunteer triager
http://w
ubuntu ~12.04
synaptic crashed Unity only, in fluxbox ok...
Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
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
thanks worked for me too :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when accessibility is enabled, e.g. sc
I had this problem and none of the advice here fixed it. I had
uninstalled onboard, one of the screen keyboard programs. I finally got
synaptic working by re-installing onboard and then disabling "Screen
Keyboard" in System Settings->Universal Access->Typing->Typing
Assistant. Weird.
--
You re
I am using oneiric on a tablet (novatech ntab). Disabling on-screen
keyboard is no workaround. Disabling orca alon does not help at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
s
Don't work 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/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when accessibility is enabled, e.g. screen reade
hey there. this seems to work
gsettings set org.gnome.desktop.interface toolkit-accessibility false
Is there any chance to release as a patch so that the not as savy people
and the newbies can also get the benefit?
>> It appears that it's related to accessibility settings. I was able to fix
>>
The trick do not work 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/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when accessibility is enabled, e.g.
the screen-reader on
the on-screen-keyboard on
will crash synaptic
both settings to off
synaptic works as expected.
BavarianPH,
Ubuntu Forever!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/83921
I confirm too, synaptic works again after this trick
>If I toggle the screen reader on & off again (System
Settings->Universal Access->Screen Reader), it stops crashing. If I
enable the >screenreader again, it starts crashing again.
--
You received this bug notification because you are a member
i can confirm
>If I toggle the screen reader on & off again (System Settings->Universal
>Access->Screen Reader), it stops crashing. If I enable the >screenreader
>again, it starts crashing again.
this help me too
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I have tried "pkill gnome-settings-daemon" but it does not work 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/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [O
What helped here was killing gnome-settings-daemon:
pkill gnome-settings-demon
and Snaptic starts as before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediatel
Pardon the typo. It should be:
pkill gnome-settings-daemon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when a
It affect me when screen reader is turned off.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on startup with SIGABRT in raise() [Only
when accessibility
** This bug is no longer a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839219
Title:
synaptic crashes immediately on
*** This bug is a duplicate of bug 807771 ***
https://bugs.launchpad.net/bugs/807771
** This bug has been marked a duplicate of bug 807771
synaptic crashed with SIGABRT in __kernel_vsyscall()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
26 matches
Mail list logo
