Ubuntu
linux package

Unable to shutdown the system from gnome

Asked by Joseph Maillardet

I was unable to shutdown my system from gnome. If I try, I finish on tty8 and it's impossible to login in any other tty[1-6]... The only way is to press ctrl+alt+suppr to get reboot and halt from grub.

But, in other way, if I disconnect to back on GDM and hask him to shutdown the system, all is going ok, the system shutdown properly !...

I don't know where and what log can be helpfull, hask me anything.

+ Jokx.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu linux Edit question
Assignee:
No assignee Edit question
Solved by:
Joseph Maillardet
Solved:
Last query:
Last reply:

This question was originally filed as bug #226964.

Revision history for this message
Richard Seguin (sectech) said : 		#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at [WWW] https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see [WWW] https://help.ubuntu.com/community/ReportingBugs .

Revision history for this message
Joseph Maillardet (jokx) said : 		#2

This is not a question ! I know how to shutdown my system thanks !! 0_o

I said that if I go on System > Logout... > Shutdown .... gnome go off, and I see tty8 but the system not shutdown ... so I need to ctrl+alt+suppr.

But, if I hask a shutdown in GDM rather than Gnome, the system shutdown properly.

Using Dell XPS M1330.

Revision history for this message
Jan Evert van Grootheest (j-e-van-grootheest) said : 		#3

Hi Joseph,

The last couple of lines from syslog would be interesting.
In case you've never heard of that, try the System menu > Administration > System log. Then select syslog on the left.
Now scroll all the way to the bottom and, using the timestamps, figure out which lines are about the shutdown. I would expect quite a few are about daemons and such shutting down.
Perhaps you could copy the last 20 or so.

Revision history for this message
Joseph Maillardet (jokx) said : 		#4

Hi,

Update : Ok from last update the system is able to shutdown from gnome, but after 20~30 second of time where I just see the tty8 on the screen, no splash, no log ...

Here is a extraction of syslog during the process.

*** Here I click on "shutdown" ***
May 12 09:18:44 sputnik init: tty4 main process (5764) killed by TERM signal
May 12 09:18:44 sputnik init: tty5 main process (5765) killed by TERM signal
May 12 09:18:44 sputnik init: tty2 main process (5767) killed by TERM signal
May 12 09:18:44 sputnik init: tty1 main process (7033) killed by TERM signal
May 12 09:18:44 sputnik init: tty3 main process (5769) killed by TERM signal
May 12 09:18:44 sputnik init: tty6 main process (5771) killed by TERM signal
May 12 09:18:44 sputnik gdm[6845]: WARNING: Le démon principal a obtenu le signal anormal SIGABRT. Arrêt !
May 12 09:19:14 sputnik avahi-daemon[6255]: Got SIGTERM, quitting.
May 12 09:19:14 sputnik avahi-daemon[6255]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.186.
May 12 09:19:15 sputnik mysqld[6350]: 080512 9:19:15 [Note] /usr/sbin/mysqld: Normal shutdown
May 12 09:19:15 sputnik mysqld[6350]:
May 12 09:19:15 sputnik mysqld[6350]: 080512 9:19:15 InnoDB: Starting shutdown...
May 12 09:19:16 sputnik mysqld[6350]: 080512 9:19:16 InnoDB: Shutdown completed; log sequence number 0 43655
May 12 09:19:16 sputnik mysqld[6350]: 080512 9:19:16 [Note] /usr/sbin/mysqld: Shutdown complete
May 12 09:19:16 sputnik mysqld[6350]:
May 12 09:19:16 sputnik mysqld_safe[8542]: ended
May 12 09:19:18 sputnik kernel: [ 500.386583] ip6_tables: (C) 2000-2006 Netfilter Core Team
May 12 09:19:19 sputnik exiting on signal 15
*** Here I press the power button ***
May 12 09:20:15 sputnik syslogd 1.5.0#1ubuntu1: restart.
May 12 09:20:15 sputnik kernel: Inspecting /boot/System.map-2.6.24-17-generic
May 12 09:20:15 sputnik kernel: Loaded 27880 symbols from /boot/System.map-2.6.24-17-generic.
May 12 09:20:15 sputnik kernel: Symbols match kernel version 2.6.24.
May 12 09:20:15 sputnik kernel: Loaded 19607 symbols from 98 modules.
May 12 09:20:15 sputnik kernel: [ 0.000000] Initializing cgroup subsys cpuset
May 12 09:20:15 sputnik kernel: [ 0.000000] Initializing cgroup subsys cpu
May 12 09:20:15 sputnik kernel: [ 0.000000] Linux version 2.6.24-17-generic (buildd@palmer) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Thu May 1 14:31:33 UTC 2008 (Ubuntu 2.6.24-17.31-generic)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-provided physical RAM map:
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 000000007f692400 (usable)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 000000007f692400 - 0000000080000000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000f8000000 - 00000000fc000000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000fed18000 - 00000000fed1c000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000fed20000 - 00000000fed90000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000feda0000 - 00000000feda6000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved)
May 12 09:20:15 sputnik kernel: [ 0.000000] 1142MB HIGHMEM available.
May 12 09:20:15 sputnik kernel: [ 0.000000] 896MB LOWMEM available.
May 12 09:20:15 sputnik kernel: [ 0.000000] Entering add_active_range(0, 0, 521874) 0 entries of 256 used
May 12 09:20:15 sputnik kernel: [ 0.000000] Zone PFN ranges:
May 12 09:20:15 sputnik kernel: [ 0.000000] DMA 0 -> 4096
May 12 09:20:15 sputnik kernel: [ 0.000000] Normal 4096 -> 229376
May 12 09:20:15 sputnik kernel: [ 0.000000] HighMem 229376 -> 521874
May 12 09:20:15 sputnik kernel: [ 0.000000] Movable zone start PFN for each node
May 12 09:20:15 sputnik kernel: [ 0.000000] early_node_map[1] active PFN ranges
May 12 09:20:15 sputnik kernel: [ 0.000000] 0: 0 -> 521874
May 12 09:20:15 sputnik kernel: [ 0.000000] On node 0 totalpages: 521874
May 12 09:20:15 sputnik kernel: [ 0.000000] DMA zone: 32 pages used for memmap
May 12 09:20:15 sputnik kernel: [ 0.000000] DMA zone: 0 pages reserved
May 12 09:20:15 sputnik kernel: [ 0.000000] DMA zone: 4064 pages, LIFO batch:0
May 12 09:20:15 sputnik kernel: [ 0.000000] Normal zone: 1760 pages used for memmap
May 12 09:20:15 sputnik kernel: [ 0.000000] Normal zone: 223520 pages, LIFO batch:31
May 12 09:20:15 sputnik kernel: [ 0.000000] HighMem zone: 2285 pages used for memmap
May 12 09:20:15 sputnik kernel: [ 0.000000] HighMem zone: 290213 pages, LIFO batch:31
May 12 09:20:15 sputnik kernel: [ 0.000000] Movable zone: 0 pages used for memmap
May 12 09:20:15 sputnik kernel: [ 0.000000] DMI 2.4 present.
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: RSDP signature @ 0xC00FBBF0 checksum 0
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: RSDP 000FBBF0, 0024 (r2 DELL )
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: XSDT 7F693E00, 005C (r1 DELL M08 27D70903 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: FACP 7F693C9C, 00F4 (r4 DELL M08 27D70903 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: DSDT 7F694400, 5739 (r2 INT430 SYSFexxx 1001 INTL 20050624)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: FACS 7F6A2C00, 0040
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: HPET 7F693F00, 0038 (r1 DELL M08 1 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: APIC 7F694000, 0068 (r1 DELL M08 27D70903 ASL 47)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: MCFG 7F693FC0, 003E (r16 DELL M08 27D70903 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: SLIC 7F69409C, 0176 (r1 DELL M08 27D70903 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: BOOT 7F693BC0, 0028 (r1 DELL M08 27D70903 ASL 61)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: SSDT 7F6925BC, 04CC (r1 PmRef CpuPm 3000 INTL 20050624)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: PM-Timer IO Port: 0x1008
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: Local APIC address 0xfee00000
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
May 12 09:20:15 sputnik kernel: [ 0.000000] Processor #0 6:15 APIC version 20
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
May 12 09:20:15 sputnik kernel: [ 0.000000] Processor #1 6:15 APIC version 20
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
May 12 09:20:15 sputnik kernel: [ 0.000000] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: IRQ0 used by override.
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: IRQ2 used by override.
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: IRQ9 used by override.
May 12 09:20:15 sputnik kernel: [ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs
May 12 09:20:15 sputnik kernel: [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
May 12 09:20:15 sputnik kernel: [ 0.000000] Using ACPI (MADT) for SMP configuration information
May 12 09:20:15 sputnik kernel: [ 0.000000] Allocating PCI resources starting at 88000000 (gap: 80000000:78000000)
May 12 09:20:15 sputnik kernel: [ 0.000000] swsusp: Registered nosave memory region: 000000000009f000 - 00000000000a0000
May 12 09:20:15 sputnik kernel: [ 0.000000] swsusp: Registered nosave memory region: 00000000000a0000 - 0000000000100000
May 12 09:20:15 sputnik kernel: [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 517797
May 12 09:20:15 sputnik kernel: [ 0.000000] Kernel command line: root=UUID=d979cfdc-ab7d-42d0-b6da-342538cc80cd ro quiet splash
May 12 09:20:15 sputnik kernel: [ 0.000000] mapped APIC to ffffb000 (fee00000)
May 12 09:20:15 sputnik kernel: [ 0.000000] mapped IOAPIC to ffffa000 (fec00000)
May 12 09:20:15 sputnik kernel: [ 0.000000] Enabling fast FPU save and restore... done.
May 12 09:20:15 sputnik kernel: [ 0.000000] Enabling unmasked SIMD FPU exception support... done.
May 12 09:20:15 sputnik kernel: [ 0.000000] Initializing CPU#0
May 12 09:20:15 sputnik kernel: [ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
May 12 09:20:15 sputnik kernel: [ 0.000000] Detected 1995.112 MHz processor.
May 12 09:20:15 sputnik kernel: [ 5.510128] Console: colour VGA+ 80x25
...

Thanks for all, J.

Revision history for this message
Jan Evert van Grootheest (j-e-van-grootheest) said : 		#5

Jospeh,

May 12 09:18:44 sputnik gdm[6845]: WARNING: Le démon principal a obtenu le signal anormal SIGABRT. Arrêt !
May 12 09:19:14 sputnik avahi-daemon[6255]: Got SIGTERM, quitting.

Apparently your gdm is misbehaving; there's a 30 second pause here. I understand that gdm receives SIGABRT? That seems to indicate that gdm somehow crashes or exits in an unexpected manner and that may cause the shutdown process to last longer.

Did you make any changes to the gdm configuration? Most people don't, so I'll assume not.
Given that gdm received an ABRT signal, that would indicate a problem of gdm itself (usually gdm problems are only symptoms of xserver problems).

Would you please check /var/log/gdm/:0.log.1 (the .1 is the previous one, .2 is before that one, etc). If you could do a diff of the current and the last one (diff -u "/var/log/gdm/:0.log" "/var/log/gdm/:0.log.1"). That gets us only the differences.
And the errors from the xserver log, just to be sure. (grep "(EE)" /var/log/Xorg.0.log.old)

We'll take it from there...

Revision history for this message
Joseph Maillardet (jokx) said : 		#6

ok, today I restart my computer after daily upgrade and discover that the problem have disappear :)

I don't know if what you ask me is always necessary so I do it :

* First, I have not modify the GDM config.
* result of diff -u "/var/log/gdm/:0.log" "/var/log/gdm/:0.log.1" :

--- /var/log/gdm/:0.log 2008-05-15 10:42:09.000000000 +0200
+++ /var/log/gdm/:0.log.1 2008-05-15 10:01:48.000000000 +0200
@@ -20,7 +20,7 @@
 Markers: (--) probed, (**) from config file, (==) default setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
-(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 15 10:36:16 2008
+(==) Log file: "/var/log/Xorg.0.log", Time: Thu May 15 10:00:55 2008
 (==) Using config file: "/etc/X11/xorg.conf"
 (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
 (II) Module "ddc" already built-in
@@ -38,53 +38,3 @@
 > Ignoring extra symbols
 Errors from xkbcomp are not fatal to the X server
 SetClientVersion: 0 9
-The XKEYBOARD keymap compiler (xkbcomp) reports:
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Warning: Duplicate shape name ""
-> Using last definition
-> Error: Section defined without a name
-> Definition ignored
-> Error: Section defined without a name
-> Definition ignored
-> Error: Section defined without a name
-> Definition ignored
-> Error: Section defined without a name
-> Definition ignored
-> Warning: Multiple doodads named ""
-> Using first definition
-> Warning: Multiple doodads named ""
-> Using first definition
-> Warning: Multiple doodads named ""
-> Using first definition
-> Warning: Multiple doodads named ""
-> Using first definition
-> Warning: Multiple doodads named ""
-> Using first definition
-> Warning: Multiple doodads named ""
-> Using first definition
-Errors from xkbcomp are not fatal to the X server

* Result of grep "(EE)" /var/log/Xorg.0.log.old :

 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.

So no error here :)

Thanks for the correction that appear to be made. J.