EasyUbuntu

Synaptic Errors (18151 & 18219

Asked by Jack Climpson

I'm new to Linux and Easyubuntu.
Running Breezy Badger and have installed 'bleeding edge' package, successfully I think.

When I run the script, I get the following (I left the non-error' bits in, just in case they are relevent to the synaptic error messages.

Screen reads below:

jack@ubuntu:~/easyubuntu/trunk$ sudo python easyubuntu.py
['/usr/sbin/synaptic', '--hide-main-window', '--non-interactive', '-o=dir::etc=/ home/jack/easyubuntu/trunk/conf', '-o=dir::etc::sourcelist=sources.list']
In update ['/usr/sbin/synaptic', '--hide-main-window', '--non-interactive', '-o= dir::etc=/home/jack/easyubuntu/trunk/conf', '-o=dir::etc::sourcelist=sources.lis t', '--update-at-startup']

(synaptic:18151): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(synaptic:18151): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
In Install ['/usr/sbin/synaptic', '--hide-main-window', '--non-interactive', '-o =dir::etc=/home/jack/easyubuntu/trunk/conf', '-o=dir::etc::sourcelist=sources.li st', '--set-selections']

(synaptic:18219): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

(synaptic:18219): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion `gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed

Where do I go from here?

Jack

Question information

Language:
English Edit question
Status:
Solved
For:
EasyUbuntu Edit question
Assignee:
No assignee Edit question
Solved by:
KarlGoetz
Solved:
Last query:
Last reply:
Revision history for this message
KarlGoetz (kgoetz) said : 		#1

Hi mate.
Did EasyUbuntu run ok anyway? or did it fail to install packages? These look like the standard output of synaptic when run from a terminal. If EasyUbuntu failed to run, then the problem is slightly more serious.
thanks
kk

Revision history for this message
Jack Climpson (j-t-c) said : 		#2

Hard to tell. The terminal window had a mix of failed synaptic messages mixed with apparent successful actions, but the window never came to a clean close(i.e returned to the prompt) and it gave no indication of activity so I couldn't tell wheteher it was doing something or nothing. After about 30 mins I decided it was doing nothing and terminated the window.

Anyway, I gave up on it, removed it from the sytem and switched to Automatix, which worked as expected, so I will take the ticket off the list for active support.

Thanks for your help.

Jack

Revision history for this message
KarlGoetz (kgoetz) said : 		#3

Jack Climpson wrote:

> Comment:
> Hard to tell. The terminal window had a mix of failed synaptic messages mixed with apparent successful actions, but the window never came to a clean close(i.e returned to the prompt) and it gave no indication of activity so I couldn't tell wheteher it was doing something or nothing. After about 30 mins I decided it was doing nothing and terminated the window.
>
If you have usability problems, i suggest filing a bug on them, so we
know what we need to try and fix.

> Anyway, I gave up on it, removed it from the sytem and switched to Automatix, which worked as expected, so I will take the ticket off the list for active support.
>
> Thanks for your help.

No worries.

>
> Jack
>
Karl