Διαφορα προβλήματα με Debian

[miza]

Έχω διαφορα προβλήματα με το debian testing και για να μην ανοίγω πολλά thread ειπα να τα γράψω μαζεμένα.

 

Όταν ανοίγω το Network μου βγάζει αυτό εδώ:

 

 

Όταν πατάω gksu gedit:

 

An error occurred while loading or saving configuration information for Text Editor. Some of your configuration settings may not work properly.

Details

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/'>http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

 

Ένα τελευταίο, προσπαθώ να περάσω το python-wxgtk2.8 έχω κατεβάσει το deb για amd64 debian testing που έχω, το έχω βάλει στο local apt που έχω και προσπαθώ να το περάσω και μου βγάζει αυτό :

 

 

The following packages have unmet dependencies:

python-wxgtk2.8: Depends: python (< 2.5) but 2.5.4-2 is to be installed

E: Broken packages

 

 

Παρακαλώ τα φώτα σας

 

edit:

Όταν ανοίγω το pc αφού φορτώσει το linux και πάει να μπει στο γραφικό περιβάλλον,αργεί να το φορτώσει και μετά μου βγάζει αυτό το μήνυμα:

 

 

Αυτό λύθηκε σβήνοντας αυτούς τους φακέλους: .gnome .gnome2 .gnome2_private .gconf .gconfd

[jim_p]

1) Το κανει και σε μενα. Μαλλον ειναι post-installation bug του gnome-network-admin. Σε ρωταει για τη διανομη σου γιατι, αναλογα με τη διανομη, αλλαζει το αρχειο αποθηκευσης ρυθμισεων δικτυου στο οποιο το προγραμμα εχει αμεση προσβαση. Στο debian πχ ειναι /etc/network/interfaces ενω στο arch ειναι /etc/rc.conf. Το "κακο" ειναι οτι επρεπε με καποιο τροπο, κατοπιν εγκαταστασης, να εχει ειδοποιηθει το αναλογο αρχειο ρυθμισεων οτι δουλευει σε debian.

 

Οποτε εκει επιλεγεις Debian Linux > testing/unstable.

 

Αλλα την επομενη φορα που θα το τρεξεις, παλι θα σε ρωτησει

 

2) Αυτο μαλλον ειναι bug του gedit. Αν σε ανακουφιζει, σου λεω οτι το κανει και σε εμενα, και στα 2 pc με testing και gnome. Με "gksu leafpad" παντως δεν εχω κανενα προβλημα.

 

3) Γιατι δεν το βαζεις με το apt? Δεν φαινεται να λειπει καποιο dependency απο εδω

Αν δεις οτι ουτε παλι στο βαζει, δοκιμασε να αλλαξεις server στο sources.list. Βαλε πχ τον 2ο γερμανικο που θεωρειται primary.

 

deb ftp://ftp2.de.debian.org/debian/ testing main contrib non-free

[miza]

Εβαλα στο sources.list αυτό που μου είπες αλλα το ίδιο μου λέει πάλι και είναι και λογικό μιας και εγώ το ίδιο πακέτο είχα βάλει στο local apt μου.

Καμια άλλη λύση στο τι μπορώ να κάνω για αυτό;

Πια είναι τα αρνητικά αν το περάσω με dpkg?

Γενικά δεν έχω καταλάβει τα αρνητικά του dpkg και πως κάνω uninstall κάτι που έχω κάνει install με dpkg.

A και κάτι άλλο, πως μπορώ να περάσω τα public keys που μου λείπουν;

Υπάρχει κάποια στάνταρ λογικη για το public key όταν δεν το έχεις για να το περάσεις;

Δεν το έχω καταλάβει καθόλου αυτό . Αν και δουλεύει μια χαρά μου σπάει τα νεύρα κάθε φορα να μου βγάζει στο τέλος apt-get update τα errors.

[jim_p]

Αναλογα με το (μη-default) repo, πρεπει να κατεβασεις και το αναλογο κλειδι και να το περασεις με το apt-key add. Πχ για το repo της opera

>wget http://deb.opera.com/[b]archive.key
[/b]
apt-key add [b]arhive.key[/b]

Αν ολα πανε καλα, που θα πανε γιατι δεν ειναι καμια τρομερη διαδικασια, θα σου βγαλει στην επομενη γραμμη του τερματικο ΟΚ.

 

Οταν λες local apt, πως το εννοεις? Ενας φακελος με .deb αρχεια ΔΕΝ εινια τοπικο repo. Ειναι απλα ενας φακελος με αρχεια.

Ενα τοπικο repo εχει τη δομη ενος κανονικου online repo μονο που βρισκεται στον σκληρο σου και δηλωνεται ετσι στο sources.list

(πχ απο το δικο μου τοπικο repo στο laptop)

>[b]deb file:[/b]/home/modis/localrepo/ testing main 

 

Μεσα στον φακελο ~/localrepo/dists/testing/main/binary-i386/ υπαρχει η λιστα των πακετων που ειναι στο repo, η Packages.gz και στο φακελο ~/localrepo/pool/main/τα πακετα σε .deb (τα εχω χυμα γιατι ειναι πολυ λιγα).

 

Με αυτο τον τροπο, οταν βρισκω ενα .deb αρχειο online, πχ το wbar, το πεταω σε εκεινο το φακελο, εκτελω ενα σκριπτακι για να ανανεωσει την λιστα των πακετων Packages.gz, apt-get update, apt-get install wbar, μου βαζει και τις εξαρτησεις και τελος.

 

Γενικα, οτι πακετο υπαρχει σε online repo, και γενικα σε repo, το βαζεις με το apt για να επιλυει αυτο τις εξαρτησεις που χρειαζονται και να μην μπλεκεις με dpkg κλπ. Ο μονος λογος να βαλεις κατι με dpkg ειναι το ιδιο το προγραμμα να εχει ολες τις εξαρτησεις του στο ιδιο .deb που παρεχει, πχ nerolinux. Τοτε ναι, dpkg.

 

Για να βγαλεις κατι περασμενο με dpkg ειτε κανεις

>apt-get autoremove paketo

μιας και το apt ειναι ενημερο οτι το paketo εχει εγκατασταθει και θα βγαλει και τις εξαρτησεις του, ή

>dpkg -r paketo

που θα βγαλει μονο το πακετο και τιποτε αλλο.

 

Μιας και το ειδα τωρα, οταν πηγες να κατεβασεις το python-wxgtk2.8 απο εδω, λεει πανω πανω σε κοκκινο πλαισιο

 

If you are running Debian, it is strongly suggested to use a package manager like aptitude or synaptic to download and install packages, instead of doing so manually via this website.

 

You should be able to use any of the listed mirrors by adding a line to your /etc/apt/sources.list like this:

 

deb http://ftp.de.debian.org/debian squeeze main

 

Replacing ftp.de.debian.org/debian with the mirror in question.

[miza]

Έχω κανονικά apt local, έχω στο sources.list μου αυτό

deb file:///root/debs ./

και περνάω εκεί τα deb, και μετά κάνω apt-get install και τα βλέπει κανονικά.

 

Νταξή με τα public key όλα ok τα βρήκα όλα.

 

Με το python-wxgtk2.8 τζίφος, άλλαξα και στο sources.list και έβαλα αυτό:

deb http://ftp.de.debian.org/debian squeeze main

δοκίμασα και από synaptic,όλα μου βγάζαν το ίδιο μήνυμα.

Παλιότερα το είχα περάσει με dpkg αλλα μετά στο apt-get upgrade μου έλεγε "python-wxgtk2.8 kept back" κάτι τέτοιο. Το playonlinux θέλω να περάσω βασικά και δεν μπορώ γιατί δεν μπορεί να περαστεί το πακέτο python-wxgtk2.8.Απλά θέλω να δω μπας και καταφέρω να το περάσω με apt, αν δεν βρω άκρη θα δοκιμάσω dpkg.

[jim_p]

Εχεις ενημερωμενη την λιστα των πακετων στο τοπικο repo?

 

Αν το apt στο βγαζει να ειναι held-back, περασε το με apt-get dist-upgrade. Πιο brutal τροπος, αλλα αυτος ειναι.

Για να μην περαστει ενα πακετο held-back ουτε με dist-upgrade παει να πει οτι υπαρχει παρα πολυ σοβαρος λογος που ειναι held-back.

 

Eπισης, οσα πακετα μπαινουν σαν held-back, μπορει να μπαινουν εκει ειτε γιατι χρειαζεται να εγκαταστησει το apt νεα πακετα που πριν δεν υπηρχαν, ειτε γιατι χρειαζεται να αφαιρεσει καποια που ειναι ηδη εγκατεστημενα αν πχ εγινε συγχωνευση πακετων.

[miza]

Ναι,αφού προσθέσω κάποιο πακέτο, πάντα τρέχω την εντολή

dpkg-scanpackages /root/debs| gzip > /root/debs/Packages.gz

 

Θα το ψάξω λίγο ακόμα google αν και ως τώρα δεν βρίσκω και πολλά πράγματα.E νταξή δεν θα έρθει και η συντέλεια του κόσμου άμα το περάσω με dpkg, ζαλίστηκα να ψάχνω για αυτό το κολοπακετο.

[poscaman]

εχω το ιδιο προβλημα με το τελευταιο σου.εσβησα τους φακελους, τιποτα. δοκιμασα και με καινουριο χρηστη κανενα προβλημα.

στην πορεια ανακαλυψα οτι το προβλημα ειναι αλλο. οταν ο χρηστης ΔΕΝ ειναι στο group audio, τοτε φορτωνει κανονικα,κανενα προβλημα, ΑΛΛΑ ΔΕΝ ΕΧΩ ΗΧΟ (λογικο....)

 

απο την αλλη, αν προσθεσω το χρηστη στο audio group, εχω το ιδιο προβλημα που περιγραφεται στο edit του πρωτου ποστ.

εχω φτασει σε dead end, πειτε καμμια ιδεα!

 

ευχαριστω, και συγγνωμη για την "σφηνα"

[miza]

Και εγώ σήμερα διαπίστωσα ότι έχω ακόμα πρόβλημα ,όχι ακριβώς το ίδιο. Όταν μπαίνω στο linux, μου λείπουν τα εικονίδια τις πάνω μπάρας(Application,places,system, ότι έχει η πάνω μπάρα λείπει).

Επιπλέον από τότε που έσβησα τους φακέλους .gnome,.gnome2 και τους άλλους που γράφω στο πρώτο post στο keybord shortcuts λείπουν επιλογές όπως shortcut για terminal που το χρησιμοποιούσα και με βόλευε πολύ και δεν εννοώ ότι έχει να του βάλεις shortcut και δεν του έχω βάλει δεν το έχει καν.

Τι μπορώ να κάνω για το πρώτο πρόβλημα, να σβήσω πάλι τους φακέλους; Αλλα δεν είναι δουλειά και αυτή να σβήνω κάθε τρις και λίγο τους φακέλους .gnome κτλ.

Και για το δεύτερο υπάρχει κάποιος τρόπος να το επαναφέρω όπως ήταν με όλες τις επιλογές για shortcuts γιατί τώρα λείπουν πολλές;

[SV8XXX]

miza,Τα ίδια... και με εμένα στα 1) και 2)προσπαθώντας να βρω λύση και εγώ διέγραψα τους ίδιους φακέλους αλλά πρώτα κράτησα αντίγραφα,έτσι ξαναέφερα τις συντομεύσεις.

Δυστυχώς και εγώ δεν βρήκα άκρη όμως κατέληξα στο συμπέρασμα ότι κάτι γίνεται με το dbus .Ίσος κάνω και λάθος.

Τελικά έφερα πίσω ένα backup του συστήματος 3μηνο ,στο sources.list όπου testing έβαλα lenny και όλα καλά μετά από 240 περίπου ενημερώσεις.

Ομολογώ πως "σπάστηκα μ αυτή τη παπαριά"αν και είμαι υπέρμαχος του Debian.

[miza]

Φημολογείται ότι όταν μπαίνει νέα έκδοση stable στο debian το testing και το sid παραγίνονται unstable για κάποιο καιρό, αλλα δεν ξέρω κατά ποσο ισχύει. Ίσος κάποιος debian με χρονια πήρα στο debian να ξέρει αν ισχύει η είναι φήμη.

Άμα δεν την παλέψω ίσος μπω και εγώ σε lenny η θα παο σε καμια άλλη έκδοση, αν και με το debian sid μέχρι πριν λίγο καιρό ήμουνα απόλυτα ευχαριστημένος και τώρα μου βγάζει το λάδι το testing. Για το sidux τι άποψη έχετε?

[poscaman]

εχω το ιδιο προβλημα με το τελευταιο σου.εσβησα τους φακελους, τιποτα. δοκιμασα και με καινουριο χρηστη κανενα προβλημα.

στην πορεια ανακαλυψα οτι το προβλημα ειναι αλλο. οταν ο χρηστης ΔΕΝ ειναι στο group audio, τοτε φορτωνει κανονικα,κανενα προβλημα, ΑΛΛΑ ΔΕΝ ΕΧΩ ΗΧΟ (λογικο....)

 

απο την αλλη, αν προσθεσω το χρηστη στο audio group, εχω το ιδιο προβλημα που περιγραφεται στο edit του πρωτου ποστ.

εχω φτασει σε dead end, πειτε καμμια ιδεα!

 

ευχαριστω, και συγγνωμη για την "σφηνα"

 

το προβλημα λυθηκε μονο του μετα την σημερινη αναβαθμιση, αρκετων πακετων του gnome.

[miza]

Πλακα κανεις? Τώρα το λες? Άλλαξα διανομή γιατί μου έσπασε τα νεύρα και είπα να ξανακάνω μια προσπάθεια με τη fedora αλλα αυτή μου έσπασε περισσότερο τα νεύρα και έφτασα στο συμπέρασμα ότι είμαι εθισμένος με debian. Mονο στην ιδέα άλλης διανομής τρομάζω!!! Τώρα κατεβάζω το stable για να το έχω γενικά και για να μείνω λίγο καιρό stable να ησυχάσει το κεφάλι μου, να αρχίσει να ξαναγίνεται κυριλέ και το testing. Ίσος ήδη είναι κυριλέ αλλα με κούρασε πολύ η κατάσταση τις τελευταίες μέρες και θέλω να είμαι σίγουρος.

[jim_p]

Τωρα που ξαναβλεπω με πιο ηρεμο μυαλο την ολη κατασταση με το gnome στο debian, και μετα απο τα οσα update εχουν γινει, ειμαι σιγουρος οτι την εχω ξαναζησει.

 

Περυσι, περιπου τον ιδιο καιρο, υπηρχαν τα ιδια προβληματα ακριβως με την μεταβαση απο το gnome 2.18 στο 2.20 (δεν ειμαι σιγουρος για τις εκδοσεις), τα οποια εξαλειφθηκαν με τα updates. Εκεινο τον καιρο το νου μου τον ειχα στο pro και στο virtualization και δεν εδωσα σημασια. Σημερα παμε για 2.24 ολοταχως!

 

Δυστυχως, θελει υπομονη γιατι η διανομη ειναι ρεουσα, και τετοια περιστατικα μπορει να συμβουν

 

Θεωρω δε οτι ειναι καλυτερο για λιγες μερες να πας σε kde, που ειναι καιρο τωρα στην 3.5.10, παρα σε αλλη διανομη!

 

----- edit

Αληθεια, απο ποιον server κανετε update?

Εχω στο (πολυπαθες) laptop τον 1ο γερμανικο

http://ftp.de.debian.org/debian/

 

και στο desktop τον 2ο γερμανικο

http://ftp2.de.debian.org/debian/

 

Υποτιθεται οτι και οι 2 ειναι primary, αρα παιρνουν τα updates νωριτερα απο τους secondary, που ειναι πχ οι ελληνικοι.

Παρολα αυτα εχει τυχει μερικα update, πχ σημερα iceweasel 3.0.7 στο testing, να το εχει στον 1ο γερμανικο μονο!

[poscaman]

Από το ntua συνηθως κατεβαζω, αν και εχω και ftp.us.debian.org

 

και μιας και συζηταμε, ιδου το sources.list μου

 

apt-pinning

 

>#Testing
deb http://security.debian.org/ testing/updates main contrib
deb-src http://security.debian.org/ testing/updates main contrib
deb http://ftp.ntua.gr/pub/linux/debian testing main contrib non-free
deb http://ftp.gr.debian.org/debian/ testing main contrib non-free
deb http://ftp.us.debian.org/debian/ testing main contrib non-free
deb-src http://ftp.us.debian.org/debian/ testing main contrib non-free



#Unstable
deb http://ftp.ntua.gr/pub/linux/debian unstable main contrib non-free
deb http://ftp.gr.debian.org/debian/ unstable main contrib non-free
deb http://ftp.us.debian.org/debian/ unstable main contrib non-free