I'm not quite sure why this crash is reported against nautilus-dropbox
because the thread that had the problem does not seem to be running
nautilus-dropbox code? Reassigning to nautilus.
** Package changed: nautilus-dropbox (Ubuntu) = nautilus (Ubuntu)
--
You received this bug notification
This was a bug in glib that got fixed in the mean time.
** Changed in: nautilus-dropbox (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/932556
It's libglib2.0-0 2.31.20-0ubuntu2 which is supposed to not be affected
by LP#932627 ... so it must be something else. I don't know what though.
I'm also not convinced that nautilus-dropbox is faulty. The crash
happens in a function of libnautilus-extension1a. I'm thus adding
nautilus as affected
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/932627
Title:
nautilus crashes when opening any folder
Chris, thanks for tracking it down. Do you feel like reporting it
upstream? I don't see the bug yet on
https://bugzilla.gnome.org/buglist.cgi?product=glibbug_status=UNCONFIRMEDbug_status=NEWbug_status=ASSIGNEDbug_status=REOPENEDversion=2.31.x
I have added glib to the list of affected packages
The segmentation fault happens in the shared-mime-info package (in its
postinst script). It's not a bug in dpkg.
** Package changed: dpkg (Ubuntu) = shared-mime-info (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This looks like a too-lax dependency from glib against libc6. It's
pretty old I'm not sure there's anything useful to find here.
** Package changed: dpkg (Ubuntu) = glib2.0 (Ubuntu)
** Changed in: glib2.0 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification
This is a bug of libglib2.0-0 because its postrm purge removes it
unconditionnaly even if the package is still installed on another
architecture.
Cf the extract below of /var/lib/dpkg/info/libglib2.0-0:i386.postrm
if [ $1 = purge ] [ -d /usr/share/glib-2.0/schemas ]; then
# Purge the
Reassigning to python-gnomeapplet due to this error:
Removing python-gnomeapplet ...
Segmentation fault (core dumped)
dpkg: error processing python-gnomeapplet (--remove):
subprocess installed pre-removal script returned error exit status 139
** Package changed: dpkg (Ubuntu) =
The error is this one:
Preparing to replace libglib2.0-data 2.26.1-0ubuntu1 (using
.../libglib2.0-data_2.28.6-0ubuntu1_all.deb) ...
rm: cannot remove `/usr/share/doc/libglib2.0-data': Is a directory
dpkg: error processing
/var/cache/apt/archives/libglib2.0-data_2.28.6-0ubuntu1_all.deb
The real failure is this one:
Preparing to replace libpango1.0-dev 1.28.3-4~eugenesan~maverick1 (using
.../libpango1.0-dev_1.28.4-0ubuntu1_amd64.deb) ...
rm: cannot remove `/usr/share/doc/libpango1.0-dev': Is a directory
dpkg: error processing
Hum, I have been a bit too quick. You're upgrading from a third-party
package to an ubuntu package... so there might be something to do.
Reassigning to pango.
** Package changed: dpkg (Ubuntu) = pango1.0 (Ubuntu)
** Changed in: pango1.0 (Ubuntu)
Status: Invalid = New
--
You received
12 matches
Mail list logo
