Fejl efter langsom opstart (LØST)

[ljdaltoften]

Hej
Efter at have op dateret ubuntu 7.10 til 8.04 kommer f'lgende fejl melding
opstod en fejl under kørsel af indstillingsserveren til Gnome.

Nogle ting, så som temaer, lyde eller baggrundsindstillinger virker muligvis ikke korrekt.

Den sidste fejlbesked var:

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.

Gnome vil stadig forsøge at starte indstillingsserveren næste gang du logger på.

[Stra]

Hej

Sker nogen få gange. Hvorfor ved jeg ikke.

Log af og og på igen så skulle det være på plads. alternativ arbejd videre (det kan man som regel, men compiz virker måske ikke o.l.) og når du starer PCeren næste gang er det ok.

Måske én ved, hvordan man via terminalen kan genstarte Gnome uden log ud?

Stra

[ljdaltoften]

Hej
Problemet er ikke gnome, den starter fint nok op efter lang tid, det er mere at den tager over
10-15 min at starte maskinen op, før jeg opgraderede til 8,04 tog det kun 2 min. Jeg har søgt på google, og alle steder efter nogen der evt. havde prøvet det, men uden det store held, håber at der er et kvikt hovede her inde som kan hjælpe mig, ellers skal jeg den lange geninstallation´s vej.

[PKO]

Hej,

Kunne du ikke lige kigge lidt i dine logs. Der kan du måske finde lidt information.

Indtil videre har du jo ikke givet os meget vi kan bruge til at finde ud af dit problem.

Jeg har tidligere opdateret til 8.04 fra 7.10 uden problemer.

Det er dog altid en god ide, at have den version du opdaterer fra fuldt opdateret, inden du tager en opdatering til en ny version.

Hvordan er dit system partitioneret?

[ljdaltoften]

Hej
Da jeg i sin tid indstalerede ubuntu 7,10, lavede den selv partitionerne, det har jeg ikke forstand på. Hvor finder jeg de logs. som jeg skal kigge på. Evt paste dem her ind.
Når jeg læser fejl meldingen, ser det ud som at den ikke kan komme på nettet for at sende en eller anden fejl log. men jeg ved ikke om jeg tolker det rigtigt.
Lidt flere oplysninger det er en bærbar dell latitude d600, med en ATI Radeon RV250 [Mobility FireGL 9000] grafik del. 1024 ram. og 40gb hdd.
Hvis der er mere i skal vide for at hjælpe, så spørg endeligt så vil jeg svare så godt jeg kan.

[ljdaltoften]

Hej
Jeg har haft en til at hjælpe, han mente at i måske kan bruge det her fra user.log :

Sep 25 01:29:46 laptop dhcdbd: Started up.
Sep 25 01:29:50 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
Sep 25 06:33:22 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Sep 25 08:17:30 laptop dhcdbd: Started up.
Sep 25 08:21:38 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason
Sep 25 08:34:28 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.domain_name
Sep 25 08:34:28 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_domain
Sep 25 08:34:28 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_servers
Sep 25 08:34:28 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.interface_mtu
Sep 25 09:08:51 laptop gnome-power-manager: (john) GNOME interaktiv udlogning. Årsag: Tænd/sluk-knappen er blevet trykket.


Her er noget fra deamon.log :

Sep 25 22:50:50 laptop NetworkManager: <info> starting...
Sep 25 22:50:51 laptop avahi-daemon[6685]: Found user 'avahi' (UID 106) and group 'avahi' (GID 114).
Sep 25 22:50:51 laptop avahi-daemon[6685]: Successfully dropped root privileges.
Sep 25 22:50:51 laptop avahi-daemon[6685]: avahi-daemon 0.6.22 starting up.
Sep 25 22:50:51 laptop avahi-daemon[6685]: Successfully called chroot().
Sep 25 22:50:51 laptop avahi-daemon[6685]: Successfully dropped remaining capabilities.
Sep 25 22:50:51 laptop avahi-daemon[6685]: No service file found in /etc/avahi/services.
Sep 25 22:50:51 laptop avahi-daemon[6685]: Network interface enumeration completed.
Sep 25 22:50:51 laptop avahi-daemon[6685]: Registering HINFO record with values 'I686'/'LINUX'.
Sep 25 22:50:51 laptop avahi-daemon[6685]: Server startup complete. Host name is laptop.local. Local service cookie is 2033568257.
Sep 25 22:50:51 laptop atieventsd[6725]: ATI External Events Daemon started...
Sep 25 22:50:51 laptop atieventsd[6725]: Event daemon control socket created
Sep 25 22:50:51 laptop atieventsd[6725]: acpid connection established
Sep 25 22:50:55 laptop NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/dell_wlan_switch
Sep 25 22:50:55 laptop NetworkManager: <info> ath0: Device is fully-supported using driver 'ath_pci'.
Sep 25 22:50:55 laptop NetworkManager: <info> ath0: driver does not support SSID scans (scan_capa 0x00).
Sep 25 22:50:55 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Sep 25 22:50:55 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Sep 25 22:50:55 laptop NetworkManager: <info> Now managing wireless (802.11) device 'ath0'.
Sep 25 22:50:55 laptop NetworkManager: <info> Deactivating device ath0.
Sep 25 22:50:55 laptop NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'.
Sep 25 22:50:55 laptop NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start
Sep 25 22:50:55 laptop NetworkManager: <info> nm_device_init(): device's worker thread started, continuing.
Sep 25 22:50:55 laptop NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
Sep 25 22:50:55 laptop NetworkManager: <info> Deactivating device eth0.
Sep 25 22:50:55 laptop NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link.
Sep 25 22:50:55 laptop NetworkManager: <debug> [1222375855.540859] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_model_RW/DVD_GCC_4243N').
Sep 25 22:50:55 laptop NetworkManager: <info> Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not supported
Sep 25 22:50:55 laptop NetworkManager: <info> Wireless now enabled by radio killswitch
Sep 25 22:50:57 laptop NetworkManager: <debug> [1222375857.874576] nm_hal_device_added(): New device added (hal udi is '/org/freedesktop/Hal/devices/pci_1002_4c66_drm_r200_card0').
Sep 25 22:51:19 laptop avahi-daemon[6685]: Registering new address record for fe80::212:79ff:fe3e:94b5 on ath0.*.
Sep 25 22:54:57 laptop NetworkManager: <info> Updating allowed wireless network lists.
Sep 25 22:54:57 laptop NetworkManager: <info> SWITCH: no current connection, found better connection 'ath0'.
Sep 25 22:54:57 laptop NetworkManager: <info> Will activate connection 'ath0/Hoejer'.
Sep 25 22:54:57 laptop NetworkManager: <info> Device ath0 activation scheduled...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) started...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0/wireless): access point 'Hoejer' is encrypted, but NO valid key exists. New key needed.
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) New wireless user key requested for network '******'.
Sep 25 22:54:57 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) New wireless user key for network '*******' received.
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
Sep 25 22:55:26 laptop NetworkManager: <info> Activation (ath0/wireless): access point '********' is encrypted, and a key exists. No new key needed.
Sep 25 22:55:28 laptop NetworkManager: <info> retry to connect to global supplicant socket (try=1)
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD ath0^I^Imadwifi^I/var/run/wpa_supplicant0^I'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was '0'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 486f656a6572'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 psk <key>'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Sep 25 22:55:28 laptop NetworkManager: <info> SUP: response was 'OK'
Sep 25 22:55:28 laptop NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
Sep 25 22:55:33 laptop NetworkManager: <info> Supplicant state changed: 1
Sep 25 22:55:33 laptop NetworkManager: <info> Activation (ath0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point '******'.
Sep 25 22:55:33 laptop NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep 25 22:55:33 laptop NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) started...
Sep 25 22:55:34 laptop NetworkManager: <info> Activation (ath0) Beginning DHCP transaction.
Sep 25 22:55:34 laptop NetworkManager: <info> Activation (ath0) Stage 3 of 5 (IP Configure Start) complete.
Sep 25 22:55:34 laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface ath0
Sep 25 22:55:34 laptop dhclient: wifi0: unknown hardware address type 801
Sep 25 22:55:35 laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface ath0
Sep 25 22:55:35 laptop dhclient: wifi0: unknown hardware address type 801
Sep 25 22:55:36 laptop NetworkManager: <info> Old device 'ath0' activating, won't change.
Sep 25 22:55:38 laptop dhclient: DHCPREQUEST of 192.168.15.102 on ath0 to 255.255.255.255 port 67
Sep 25 22:55:38 laptop dhclient: DHCPACK of 192.168.15.102 from 192.168.15.1
Sep 25 22:55:38 laptop avahi-daemon[6685]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.15.102.
Sep 25 22:55:38 laptop avahi-daemon[6685]: New relevant interface ath0.IPv4 for mDNS.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Registering new address record for 192.168.15.102 on ath0.IPv4.
Sep 25 22:55:38 laptop NetworkManager: <info> DHCP daemon state is now 4 (reboot) for interface ath0
Sep 25 22:55:38 laptop NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) scheduled...
Sep 25 22:55:38 laptop NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) started...
Sep 25 22:55:38 laptop NetworkManager: <info> Retrieved the following IP4 configuration from the DHCP daemon:
Sep 25 22:55:38 laptop NetworkManager: <info> address 192.168.15.102
Sep 25 22:55:38 laptop NetworkManager: <info> netmask 255.255.255.0
Sep 25 22:55:38 laptop NetworkManager: <info> broadcast 192.168.15.255
Sep 25 22:55:38 laptop NetworkManager: <info> gateway 192.168.15.1
Sep 25 22:55:38 laptop NetworkManager: <info> nameserver 192.168.15.1
Sep 25 22:55:38 laptop NetworkManager: <info> hostname 'laptop'
Sep 25 22:55:38 laptop NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) scheduled...
Sep 25 22:55:38 laptop NetworkManager: <info> Activation (ath0) Stage 4 of 5 (IP Configure Get) complete.
Sep 25 22:55:38 laptop NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) started...
Sep 25 22:55:38 laptop dhclient: bound to 192.168.15.102 -- renewal in 34626 seconds.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Withdrawing address record for 192.168.15.102 on ath0.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Leaving mDNS multicast group on interface ath0.IPv4 with address 192.168.15.102.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Interface ath0.IPv4 no longer relevant for mDNS.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Withdrawing address record for fe80::212:79ff:fe3e:94b5 on ath0.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Joining mDNS multicast group on interface ath0.IPv4 with address 192.168.15.102.
Sep 25 22:55:38 laptop avahi-daemon[6685]: New relevant interface ath0.IPv4 for mDNS.
Sep 25 22:55:38 laptop avahi-daemon[6685]: Registering new address record for 192.168.15.102 on ath0.IPv4.
Sep 25 22:55:39 laptop NetworkManager: <info> Clearing nscd hosts cache.
Sep 25 22:55:39 laptop NetworkManager: <WARN> nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))
Sep 25 22:55:39 laptop NetworkManager: <info> Activation (ath0) successful, device activated.
Sep 25 22:55:39 laptop NetworkManager: <info> Activation (ath0) Finish handler scheduled.
Sep 25 22:55:39 laptop NetworkManager: <info> Activation (ath0) Stage 5 of 5 (IP Configure Commit) complete.
Sep 25 22:55:40 laptop ntpdate[13477]: adjust time server 91.189.94.4 offset 0.103548 sec
Sep 25 22:55:40 laptop avahi-daemon[6685]: Registering new address record for fe80::212:79ff:fe3e:94b5 on ath0.*.
Sep 25 23:20:28 laptop console-kit-daemon[7160]: WARNING: Unable to activate console: No such device or address
Sep 25 23:20:28 laptop init: tty4 main process (6068) killed by TERM signal
Sep 25 23:20:28 laptop init: tty5 main process (6069) killed by TERM signal

Måske kan i se nogen fejl, jeg kan ikke.

[PKO]

Hej,

Den ser ud til at lede efter noget for netkort som ikke er der.

Kode: Vælg alt

Sep 25 01:29:50 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Sep 25 01:29:55 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
Sep 25 06:33:22 laptop dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.reason

Hvordan er det trådløse blevet installeret?

Kunne du poste resultat af denne kommando i terminal

Kode: Vælg alt

lspci

[ljdaltoften]

Hej
Da jeg opgraderede virkede det som før, fra starten ville netkortet ikke virke men så skiftede jeg kortet til Atheros AR 5212 den virkede da jeg startede op ogindtastede koder og bruger navn.
Her kommer det du skulle bruge : 00:00.0 Host bridge: Intel Corporation 82855PM Processor to I/O Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 82855PM Processor to AGP Controller (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 01)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5705M Gigabit Ethernet (rev 01)
02:01.0 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)
02:01.1 CardBus bridge: O2 Micro, Inc. OZ711EC1 SmartCardBus Controller (rev 20)
02:03.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)

[PKO]

Hej,

Jeg mener det er blvevet installeret forkert netværk. Den bruger en masse tid på at løse denne konfilkt.

Har du ikke en henvisning til den guide, du har brugt til installering af dit trådløse netkort.

[ljdaltoften]

Hej
Kortet er instaleret under hardware drivers som:
arheros Hardware Access (HAL)
Software modem
Support for Atheros 802.11 Wireless LAN cards

Der er sat flueben i dem alle 3

[PKO]

Jeg er ikke sikker,

men prøv at fjerne

arheros Hardware Access (HAL)
Software modem

genstart og test.

Kunne du også give resultat af

Kode: Vælg alt

lsusb

[ljdaltoften]

Hej igen
Har forsogt men samme problem. Her er lidt at se paa >
john@laptop:~$ lsusb
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 413c:8000 Dell Computer Corp.
Bus 001 Device 001: ID 0000:0000

Hvorfor kan jeg ikke skrive ;'[ de danske bogstaver det plejer jeg at kunne.

[ljdaltoften]

hej
genstart af firefox så virker æøå igen.

[PKO]

Hej,

Hvis jeg var dig med alle disse problemer som fremkommer, ville jeg lave en ny installation. Det bliver hurtigere og bedre end vi forsøger at fejlfinde mere.

Du skal tage backup at din hjemmemappe.

Her er en god guide for korrekt installation med egen partition for dine data http://wiki.ubuntu-dk.org/GuidesHowtos/ ... stallation

[ljdaltoften]

Hej
Det var nok det jeg frygtede, jeg lever nok med det til den nye ubuntu kommer.
Du får mange tak for din hjælp, det er rart at der er nogen der vil prøve at hjælpe, nogen gange er det bare ikke nemt.