[Bug 193223] Re: package python-apt 0.7.4ubuntu4 failed to install/upgrade: subprocess pre-installation script returned error exit status 1

2008-02-19 Thread fork
0.7.4ubuntu5 also -- package python-apt 0.7.4ubuntu4 failed to install/upgrade: subprocess pre-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/193223 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.

[Bug 182222] Re: package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-12 Thread fork
*** This bug is a duplicate of bug 182130 *** https://bugs.launchpad.net/bugs/182130 I confirm it. 2.6.24-3-generic ubuntu hardy -- package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation script returned error exit status 1

[Bug 182130] Re: package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-12 Thread fork
save the attachment to /usr/share/cli- common/policies.d/libflickrnet2.1.5-cil/ ** Attachment added: policy.2.1.FlickrNet.dll http://launchpadlibrarian.net/11307378/policy.2.1.FlickrNet.dll -- package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation

[Bug 182130] Re: package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation script returned error exit status 1

2008-01-12 Thread fork
Mike Durham: sudo cp policy.2.1.FlickrNet.dll /usr/share/cli- common/policies.d/libflickrnet2.1.5-cil/ -- package libflickrnet2.1.5-cil 25277-5 failed to install/upgrade: subprocess post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/182130 You received this

[Bug 182390] gmailfs mountpoint not readable after connection

2008-01-12 Thread fork
Public bug reported: Binary package hint: gmailfs my gmailfs.log says: 01/12/08 21:23:47 INFO Mountpoint: /home/fork/gmail 01/12/08 21:23:47 INFO Named mount options: {'username': '*', 'password': '', 'fsname': '**'} 01/12/08 21:23:47 INFO waiting for /home

[Bug 182390] Re: gmailfs mountpoint not readable after connection

2008-01-12 Thread fork
** Description changed: Binary package hint: gmailfs my gmailfs.log says: 01/12/08 21:23:47 INFO Mountpoint: /home/fork/gmail 01/12/08 21:23:47 INFO Named mount options: {'username': '*', 'password': '', 'fsname': '**'} 01/12/08 21:23:47 INFO

[Bug 182390] Re: gmailfs mountpoint not readable after connection

2008-01-15 Thread fork
It seems linux gmailfs is different from windows GDrive so I couldn't see windows GDrive files. gmailfs works for me now. Bug should be deleted. -- gmailfs mountpoint not readable after connection https://bugs.launchpad.net/bugs/182390 You received this bug notification because you are a member

[Bug 1465189] Re: Nautilus crashes when opening Dropbox

2015-06-15 Thread Fork
** Package changed: nautilus (Ubuntu) = nautilus-dropbox (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465189 Title: Nautilus crashes when opening Dropbox To manage notifications about

[Bug 1465189] Re: Nautilus crashes when opening Dropbox

2015-06-18 Thread Fork
** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1465189 Title: Nautilus crashes when opening Dropbox To manage notifications about this bug go to:

[Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

2016-06-04 Thread Fork
Great thing it's working for macias now! The issue persists for me and others. Please reopen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566302 Title: Ubuntu 16.04: Suspend freezes the system

[Bug 1633826] Re: nautilus desktop crashes when called with --no-desktop

2016-11-02 Thread Fork
Hm, weird. There was no message this time when the desktop disappeared. I have included the output of the nautilus startup. ** Description changed: When calling nautilus with the --no-desktop flag in Ubuntu 16.10 while it is already running, the existing desktop stops responding. All icons

[Bug 1633826] Re: nautilus desktop crashes when called with --no-desktop

2016-11-04 Thread Fork
This issue actually appears to be a regression: https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1453655 I'm reluctant to mark the bug as duplicate, though, since the other issue is version-specific and marked as closed. -- You received this bug notification because you are a

[Bug 1633826] Re: nautilus desktop crashes when called with --no-desktop

2016-11-02 Thread Fork
Note that nautilus in its entirety does not crash. nautilus windows will function normally. However, the desktop becomes nonfunctional (all icons disappear and the desktop does not respond to the mouse). ** Attachment added: "Backtrace"

[Bug 1633826] Re: nautilus desktop crashes when called with --no-desktop

2016-11-02 Thread Fork
Updated. Which log? The command line output is in the description, the backtrace is in comment #4. nautilus doesn't appear to write to /var/log. ** Description changed: - When calling nautilus with the --no-desktop flag in Ubuntu 16.10, the - existing desktop crashes with the following error: +

[Bug 1633826] [NEW] nautilus desktop crashes when called with --no-desktop

2016-10-16 Thread Fork
Public bug reported: When calling nautilus with the --no-desktop flag in Ubuntu 16.10, the existing desktop crashes with the following error: (nautilus:3723): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:3723):

[Bug 1874250] Re: do-release-upgrade fails 19.10->20.04 AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'

2020-04-24 Thread Fork
*** This bug is a duplicate of bug 1848829 *** https://bugs.launchpad.net/bugs/1848829 This seems to typically stem from a pip-installed version of distro-info shadowing the apt version, like in the issue David S linked. I'm not sure this can be prevented by the updater. If you're here