package gij 4:4.4.1-1ubuntu2 failed to install/upgrade: ne peut pas acc?der ? l'archive: Aucun fichier ou dossier de ce type

Bug #481622 reported by François
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

None

ProblemType: Package
Architecture: i386
Date: Sun Nov 8 23:29:51 2009
DistroRelease: Ubuntu 9.10
ErrorMessage: ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type
Package: gij 4:4.4.1-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: gcc-defaults
Title: package gij 4:4.4.1-1ubuntu2 failed to install/upgrade: ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type
Uname: Linux 2.6.31-15-generic i686
XsessionErrors:
 (nautilus:27823): Liboobs-WARNING **: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
 (nautilus:27823): Liboobs-CRITICAL **: run_message: assertion `oobs_session_get_connected (priv->session)' failed
 (nautilus:27823): Liboobs-CRITICAL **: run_message: assertion `oobs_session_get_connected (priv->session)' failed
 (gnome-panel:27782): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 24

Revision history for this message
François (contribos) wrote :
Revision history for this message
Matthias Klose (doko) wrote :

not a gcc error:

dpkg : erreur de traitement de /var/cache/apt/archives/gij_4%3a4.4.1-1ubuntu2_i386.deb (--unpack) :
 ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type
dpkg : erreur de traitement de /var/cache/apt/archives/gcj-jre-headless_4%3a4.4.1-1ubuntu2_i386.deb (--unpack) :
 ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type

affects: gcc-defaults (Ubuntu) → ubuntu
Revision history for this message
Sergio Barjola (sbarjola) wrote :

Are you still having this issue ? If so, can you run from a terminal 'sudo apt-get clean' and 'sudo apt-get update'. Thanks in advance!

affects: ubuntu → update-manager (Ubuntu)
Changed in update-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Sergio Barjola (sbarjola) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Sergio Barjola (sbarjola) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. Thanks again!

Changed in update-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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