After upgrading from 7.04 to 7.10 glom crshes

Bug #161935 reported by mune
8
Affects Status Importance Assigned to Milestone
glom (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: glom

I happily worked on glom with Ubuntu 7.04 until when i upgraded to 7.10M; since then it crashes when it starts and on console it says:
[code]$ glom
glom: error while loading shared libraries: libgnomecanvasmm-2.6.so.1: cannot open shared object file: No such file or directory[/code]

Some info about my system
[code]$ uname -a
Linux lello 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
[/code]

Revision history for this message
Murray Cumming (murrayc) wrote :

Maybe the glom package should depend on libgnomecanvasmm-2.6-1c2a, though Glom really shouldn't need it. Maybe a later version of glom 1.6.x would fix that problem.

I am also surprised that I can't reproduce this here, though I also don't have libgnomecanvasmm-2.6-1c2a installed.

Revision history for this message
Murray Cumming (murrayc) wrote :

Glom 1.6.4 certainly doesn't depend on libgnomecanvas, and has other essential fixes. It really should be packaged.

Changed in glom:
status: New → Fix Committed
Revision history for this message
mune (mune) wrote : Re: [Bug 161935] Re: After upgrading from 7.04 to 7.10 glom crshes

On lun, 2007-11-26 at 08:39 +0000, Murray Cumming wrote:
> Glom 1.6.4 certainly doesn't depend on libgnomecanvas, and has other
> essential fixes. It really should be packaged.

The distro (ubuntu 7.10) installs glom
~$ glom --version
1.4.4

I don't know how but now it is *started working again*: now I have the
problem that I have modified the DB with MS Access in win via pgsqlODBC
and glom crash on a table: I don't see any solutions, as the old db
backup makes glom working with all the tables, but the php application
complains (maybe I did a modification to that table with phpPgSQL).
--
Fede
________________________________________________________________________
       mune (at) fsfe.org Ing. Federico Munerotto
   home http://www.mune-web.eu
Public key http://www.mune-web.eu/personal/misc/pk/pk.html
Signoraggio http://www.mune-web.eu/personal/misc/signoraggio/
________________________________________________________________________
      posta firmata digitalmente | mail digitally signed
______________________________________|_________________________________
There's nothing like a restart.

Revision history for this message
Murray Cumming (murrayc) wrote :

> The distro (ubuntu 7.10) installs glom
> ~$ glom --version
> 1.4.4

No, Ubuntu 7.10 (Gutsy) definitely has 1.6.0. I don't know why you seem to have 1.4.4. Maybe you are not really using 7.10, or an upgrade failed somehow. Or maybe you installed Glom separately somehow. "which glom" should tell you if you are running from /usr/bin

> now I have the problem that I have modified the DB with MS Access in win via pgsqlODBC
> and glom crash on a table: I don't see any solutions, as the old db
> backup makes glom working with all the tables, but the php application
> complains (maybe I did a modification to that table with phpPgSQL).

One bug per bug report, please. But Glom cannot deal with structural changes that you make outside of Glom. It should be able to deal with simple changes to data (such as adding a row). If that's all you've done then I would like to see a backtrace with the latest version.

Revision history for this message
mune (mune) wrote :

On lun, 2007-11-26 at 11:07 +0000, Murray Cumming wrote:
> > The distro (ubuntu 7.10) installs glom
> > ~$ glom --version
> > 1.4.4
>
> No, Ubuntu 7.10 (Gutsy) definitely has 1.6.0. I don't know why you
> seem
> to have 1.4.4. Maybe you are not really using 7.10, or an upgrade
> failed
> somehow. Or maybe you installed Glom separately somehow. "which glom"
> should tell you if you are running from /usr/bin

mune@lello:~$ which glom
/usr/local/bin/glom
mune@lello:~$ which /usr/bin/glom
/usr/bin/glom
mune@lello:~$ /usr/bin/glom --version
1.6.0

You was right, sorry
--
Fede
________________________________________________________________________
       mune (at) fsfe.org Ing. Federico Munerotto
   home http://www.mune-web.eu
Public key http://www.mune-web.eu/personal/misc/pk/pk.html
Signoraggio http://www.mune-web.eu/personal/misc/signoraggio/
________________________________________________________________________
      posta firmata digitalmente | mail digitally signed
______________________________________|_________________________________
Just to have it is enough.
Let me put it this way: today is going to be a learning experience.

Revision history for this message
mune (mune) wrote :

On lun, 2007-11-26 at 17:13 +0000, mune wrote:
> [...]
> mune@lello:~$ which glom
> /usr/local/bin/glom
> mune@lello:~$ which /usr/bin/glom
> /usr/bin/glom
> mune@lello:~$ /usr/bin/glom --version
> 1.6.0
>
> You was right, sorry

But it still doesn't work.

To be safe I removed the packages libgda3-postgres and glom.
Then I reinstalled both.

Weird enough I receive a "not enough memory" error.

mune@lello:~$ sudo apt-get install libgda3-postgres
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso
Reading state information... Fatto
I seguenti pacchetti NUOVI (NEW) saranno installati:
  libgda3-postgres
0 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prendere 0B/44,9kB di archivi.
Dopo l'estrazione, verranno occupati 164kB di spazio su disco.
(Lettura del database ... 198944 file e directory attualmente
installati.)
Spacchetto libgda3-postgres
(da .../libgda3-postgres_3.0.1-1build2_amd64.deb) ...
dpkg: errore
processando /var/cache/apt/archives/libgda3-postgres_3.0.1-1build2_amd64.deb (--unpack):
 fork fallita: Cannot allocate memory
dpkg: errore durante la pulizia:
 fork fallita: Cannot allocate memory
Sono occorsi degli errori processando:
 /var/cache/apt/archives/libgda3-postgres_3.0.1-1build2_amd64.deb
L'operazione è stata bloccata perché si sono verificati troppi errori.
E: Sub-process /usr/bin/dpkg returned an error code (1)

I don't understand way, maybe it can help this output

mune@lello:~$ cat /proc/meminfo
MemTotal: 1028408 kB
MemFree: 9204 kB
Buffers: 2904 kB
Cached: 197632 kB
SwapCached: 0 kB
Active: 694832 kB
Inactive: 216484 kB
SwapTotal: 8024 kB
SwapFree: 0 kB
Dirty: 1276 kB
Writeback: 0 kB
AnonPages: 710792 kB
Mapped: 34652 kB
Slab: 43724 kB
SReclaimable: 11456 kB
SUnreclaim: 32268 kB
PageTables: 26504 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 522228 kB
Committed_AS: 1764520 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 20564 kB
VmallocChunk: 34359717683 kB

--
Fede
________________________________________________________________________
       mune (at) fsfe.org Ing. Federico Munerotto
   home http://www.mune-web.eu
Public key http://www.mune-web.eu/personal/misc/pk/pk.html
Signoraggio http://www.mune-web.eu/personal/misc/signoraggio/
________________________________________________________________________
      posta firmata digitalmente | mail digitally signed
______________________________________|_________________________________
Just to have it is enough.
Let me put it this way: today is going to be a learning experience.

Revision history for this message
mune (mune) wrote :
Download full text (3.2 KiB)

On lun, 2007-11-26 at 20:56 +0000, mune wrote:
> On lun, 2007-11-26 at 17:13 +0000, mune wrote:
> > [...]
> > mune@lello:~$ which glom
> > /usr/local/bin/glom
> > mune@lello:~$ which /usr/bin/glom
> > /usr/bin/glom
> > mune@lello:~$ /usr/bin/glom --version
> > 1.6.0
> >
> > You was right, sorry
>
> But it still doesn't work.
>
> To be safe I removed the packages libgda3-postgres and glom.
> Then I reinstalled both.
>
> Weird enough I receive a "not enough memory" error.
>
> mune@lello:~$ sudo apt-get install libgda3-postgres
> Lettura della lista dei pacchetti in corso... Fatto
> Generazione dell'albero delle dipendenze in corso
> Reading state information... Fatto
> I seguenti pacchetti NUOVI (NEW) saranno installati:
> libgda3-postgres
> 0 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
> È necessario prendere 0B/44,9kB di archivi.
> Dopo l'estrazione, verranno occupati 164kB di spazio su disco.
> (Lettura del database ... 198944 file e directory attualmente
> installati.)
> Spacchetto libgda3-postgres
> (da .../libgda3-postgres_3.0.1-1build2_amd64.deb) ...
> dpkg: errore
> processando /var/cache/apt/archives/libgda3-postgres_3.0.1-1build2_amd64.deb (--unpack):
> fork fallita: Cannot allocate memory
> dpkg: errore durante la pulizia:
> fork fallita: Cannot allocate memory
> Sono occorsi degli errori processando:
> /var/cache/apt/archives/libgda3-postgres_3.0.1-1build2_amd64.deb
> L'operazione è stata bloccata perché si sono verificati troppi errori.
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I don't understand way, maybe it can help this output
>
> mune@lello:~$ cat /proc/meminfo
> MemTotal: 1028408 kB
> MemFree: 9204 kB
> Buffers: 2904 kB
> Cached: 197632 kB
> SwapCached: 0 kB
> Active: 694832 kB
> Inactive: 216484 kB
> SwapTotal: 8024 kB
> SwapFree: 0 kB
> Dirty: 1276 kB
> Writeback: 0 kB
> AnonPages: 710792 kB
> Mapped: 34652 kB
> Slab: 43724 kB
> SReclaimable: 11456 kB
> SUnreclaim: 32268 kB
> PageTables: 26504 kB
> NFS_Unstable: 0 kB
> Bounce: 0 kB
> CommitLimit: 522228 kB
> Committed_AS: 1764520 kB
> VmallocTotal: 34359738367 kB
> VmallocUsed: 20564 kB
> VmallocChunk: 34359717683 kB

I restarted my box and installed
glom and libgda3-postgres
(there should has been a memory overload problem)

But when I launch glom I get:
mune@lello:~$ glom
glom: symbol lookup error: glom: undefined symbol:
_ZN4Glom14ConnectionPool51check_postgres_gda_client_is_available_with_warningEv

--
Fede
________________________________________________________________________
       mune (at) fsfe.org Ing. Federico Munerotto
   home http://www.mune-web.eu
Public key http://www.mune-web.eu/personal/misc/pk/pk.html
Signoraggio http://www.mune-web.eu/personal/misc/signoraggio/
________________________________________________________________________
      posta firmata digitalmente | mail digitally signed
______________________________________|_________________________________
People are beginning to notice you...

Read more...

Revision history for this message
Murray Cumming (murrayc) wrote :

> mune@lello:~$ sudo apt-get install libgda3-postgres
[snip]
> fork fallita: Cannot allocate memory

Sorry, but I think something is seriously wrong with your Ubuntu installation, and I'm not expert enough about apt-get to help fix it. I don't think it's a Glom error.

Revision history for this message
mune (mune) wrote :

On mar, 2007-11-27 at 09:03 +0000, Murray Cumming wrote:
> > mune@lello:~$ sudo apt-get install libgda3-postgres
> [snip]
> > fork fallita: Cannot allocate memory
>
> Sorry, but I think something is seriously wrong with your Ubuntu
> installation, and I'm not expert enough about apt-get to help fix it. I
> don't think it's a Glom error.

Don't worry that issue is solved: I overloaded system, I've been able to
reinstall the packages, but I get
mune@lello:~$ glom
glom: symbol lookup error: glom: undefined symbol:
_ZN4Glom14ConnectionPool51check_postgres_gda_client_is_available_with_warningEv

--
Fede
________________________________________________________________________
       mune (at) fsfe.org Ing. Federico Munerotto
   home http://www.mune-web.eu
Public key http://www.mune-web.eu/personal/misc/pk/pk.html
Signoraggio http://www.mune-web.eu/personal/misc/signoraggio/
________________________________________________________________________
      posta firmata digitalmente | mail digitally signed
______________________________________|_________________________________
You are not dead yet. But watch for further reports.

Revision history for this message
Murray Cumming (murrayc) wrote :

Closing because I don't think this is a Glom problem and there's not much I can do about it.

Changed in glom:
status: Fix Committed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.