Mint software manager and package manager do not start

[Peano58]

Hello everyone. i just performed a fresh install of LMDE 2014303 on my computer with mate and something weird is going on.
If I try to start either the software or the package manager from the menu, I get the request to insert the password as expected, but then the program doesn't start.

I tried to start the software manager from the terminal, but I get the following error:

Code: Select all

myusername@myusername-desktop ~ $ mintInstall
glibtop: Non-standard uts for running kernel:
release 3.11-2-486=3.11.0 gives version code 199424

I managed to start synaptic, and this is the code shown in terminal:

Code: Select all

myusername@myusername-desktop ~ $ sudo synaptic

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): GLib-GObject-CRITICAL **: g_object_set_data: assertion `G_IS_OBJECT (object)' failed

(synaptic:4432): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(synaptic:4432): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x9332d88 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93a5a68 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3010 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d30d8 is not mapped

(synaptic:4432): Gtk-WARNING **: GtkNotebook 0x9389048 is mapped but visible child GtkLabel 0x93d3330 is not mapped

Any suggestion is appreciated.

Here is the information about the system.

Code: Select all

CPU~Single core AMD Sempron 3000+ (-UP-) clocked at 2002.642 Mhz Kernel~3.11-2-486 i686 Up~40 min Mem~393.4/1009.0MB HDD~80.0GB(5.9% used) Procs~138 Client~Shell inxi~1.9.14

[py-thon]

Any suggestion is appreciated.

Two suggestions which turned up in Google:
There seems to be some bug with gksu ( https://github.com/linuxmint/mintinstall/issues/52 et al.) and problems with gtk3 (see http://forums.linuxmint.com/viewtopic.p ... &start=120 et al.).

[Peano58]

Hello py-thon,
thank you for the links. Indeed, mintInstall does work also on my system if launched via sudo -s session, as noticed by the author of the first page. My system is up to date, should I maybe try to do a downgrade of the bugged package?

By the way, I just noticed that even the update manager does not start.

[py-thon]

I would change theme first to ensure that's it is not one of the mentioned problems with themes. I once had weird behaviour after an UP because the theme I used as a base for my settings was no longer supported in some way.
Try to avoid downgrading if possible.

[Peano58]

Thank you for the piece of the advice, but It doesn't matter any more, because the computer broke. I guess it can happen after nine and half year of service. I will try to change the theme if I manage to take it back from the dead.