Re: [gentoo-amd64] Ugly desktop
On 1/27/06, Jonathan Schaeffer <[EMAIL PROTECTED]> wrote: > I use XFCE and since some weeks, I have a realy ugly taskbar. I don't > know if it's an xFCE bug or a library version that does not realy suits > ... Has someone experiences the same as this [...] I seem to recall that an issue with pango caused that when using gtk+-2.8.x. What I am thinking of, though, was fixed shortly after 2.8.0's release (by .1 or so, I think), so I'm not sure if it's the same thing that you have, though the problem looked identical to yours. Maybe checking out pango could be a start, though. Sorry I can't help more. -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] BUG: soft lockup detected on CPU#0!
On Saturday 28 January 2006 00:57, Aggelos wrote: > Machine holds for a few seconds at the: > Probing IDE interface ide1... > (just before it reports the BUG:) > and then continues on, booting normaly. > Is this a bug? > I include complete dmesg, lspci and .config. > Aggelos. > I would send the stuff to lkml and be ready to answer some questions and try some stuff ;) -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] BUG: soft lockup detected on CPU#0!
Machine holds for a few seconds at the: Probing IDE interface ide1... (just before it reports the BUG:) and then continues on, booting normaly. Is this a bug? I include complete dmesg, lspci and .config. Aggelos. http://www.freemail.gr - δωρεάν υπηρεσία ηλεκτρονικού ταχυδρομείου. http://www.freemail.gr - free email service for the Greek-speaking.Bootdata ok (command line is ro root=/dev/sda5 vga=791) Linux version 2.6.15-27Jan06-r1 ([EMAIL PROTECTED]) (gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)) #1 SMP Fri Jan 27 21:08:26 EET 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 3fff (usable) BIOS-e820: 3fff - 3fff3000 (ACPI NVS) BIOS-e820: 3fff3000 - 4000 (ACPI data) BIOS-e820: fec0 - 0001 (reserved) ACPI: RSDP (v000 VIAK8T) @ 0x000f7420 ACPI: RSDT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff3000 ACPI: FADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff3040 ACPI: BOOT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff7d40 ACPI: MADT (v001 VIAK8T AWRDACPI 0x42302e31 AWRD 0x) @ 0x3fff7d80 ACPI: DSDT (v001 VIAK8T AWRDACPI 0x1000 MSFT 0x010e) @ 0x Scanning NUMA topology in Northbridge 24 Number of nodes 1 Node 0 MemBase Limit 3fff Using 63 for the hash shift. Using node hash shift of 63 Bootmem setup node 0 -3fff On node 0 totalpages: 257045 DMA zone: 2540 pages, LIFO batch:0 DMA32 zone: 254505 pages, LIFO batch:31 Normal zone: 0 pages, LIFO batch:0 HighMem zone: 0 pages, LIFO batch:0 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] disabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 3, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to physical flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 5000 (gap: 4000:bec0) Checking aperture... CPU 0: aperture @ e000 size 128 MB SMP: Allowing 2 CPUs, 1 hotplug CPUs Built 1 zonelists Kernel command line: ro root=/dev/sda5 vga=791 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 3.579545 MHz PM timer. time.c: Detected 1838.880 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Memory: 1026396k/1048512k available (3159k kernel code, 21728k reserved, 1462k data, 244k init) Calibrating delay using timer specific routine.. 3686.27 BogoMIPS (lpj=7372554) Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 512K (64 bytes/line) CPU 0(1) -> Node 0 -> Core 0 mtrr: v2.0 (20020519) Using local APIC timer interrupts. Detected 12.770 MHz APIC timer. Brought up 1 CPUs time.c: Using PIT/TSC based timekeeping. testing NMI watchdog ... OK. NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20050902 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) Boot video device is :01:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12) *5 ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 7 10 11 *12) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 6 7 *10 11 12) ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 6 7 10 11 12) *0, disabled. ACPI: PCI Interrupt Link [ALKA] (IRQs 20) *11 ACPI: PCI Interrupt Link [ALKB] (IRQs *21) ACPI: PCI Interrupt Link [ALKC] (IRQs *22) ACPI: PCI Interrupt Link [ALKD] (IRQs *23), disabled. SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=routeirq". If it h
Re: [gentoo-amd64] Re: Ugly desktop
2006/1/28, Duncan <[EMAIL PROTECTED]>: > Jonathan Schaeffer posted <[EMAIL PROTECTED]>, excerpted below, > on Fri, 27 Jan 2006 21:30:02 +0100: > > > I see the taskbar issue, but couldn't see the Qt issue. Of course, I'm a > KDE user, not an XFCE user, so maybe that's it. I think it's just about the QT style. "Plastique" would have been cuter. Still, qtconfig it useless. > In any case, I don't > have any suggestions altho I can certainly see how you'd be frustrated > with the taskbar as it is. Someone else may be of help, as there are > several XFCE users here I believe, but pointing you to the desktop > group/list is the best I can do with it. That's pretty well. Thanks. Jonathan -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Re: Ugly desktop
Jonathan Schaeffer posted <[EMAIL PROTECTED]>, excerpted below, on Fri, 27 Jan 2006 21:30:02 +0100: > This might not be the best list to post this question. Anyway, If no one can help you fix it here, maybe try the gentoo-desktop list. That's where I usually see this sort of question (and it usually yields a fix, too =8^). > I use XFCE and since some weeks, I have a realy ugly taskbar. I don't > know if it's an xFCE bug or a library version that does not realy suits > ... Has someone experiences the same as this : > > http://skizo.rutabaga.free.fr/ugly_desktop.png > > By the way, my Qt apps are not cute at all (see screen shot). I tried a > qtconfig but it was helpless. > > At work I use XFCE too and I don't see this awfull texts in the taskbar. > And Qt apps are nicer. I see the taskbar issue, but couldn't see the Qt issue. Of course, I'm a KDE user, not an XFCE user, so maybe that's it. In any case, I don't have any suggestions altho I can certainly see how you'd be frustrated with the taskbar as it is. Someone else may be of help, as there are several XFCE users here I believe, but pointing you to the desktop group/list is the best I can do with it. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] Ugly desktop
On Fri, Jan 27, 2006 at 09:30:02PM +0100, Jonathan Schaeffer wrote: > I use XFCE and since some weeks, I have a realy ugly taskbar. I don't > know if it's an xFCE bug or a library version that does not realy suits > ... Has someone experiences the same as this : > > http://skizo.rutabaga.free.fr/ugly_desktop.png Me too -- Koef. -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] Ugly desktop
Hi * This might not be the best list to post this question. Anyway, I use XFCE and since some weeks, I have a realy ugly taskbar. I don't know if it's an xFCE bug or a library version that does not realy suits ... Has someone experiences the same as this : http://skizo.rutabaga.free.fr/ugly_desktop.png By the way, my Qt apps are not cute at all (see screen shot). I tried a qtconfig but it was helpless. At work I use XFCE too and I don't see this awfull texts in the taskbar. And Qt apps are nicer. Has anybody some idea ? Jonathan begin:vcard fn:Jonathan Schaeffer n:Schaeffer;Jonathan email;internet:[EMAIL PROTECTED] x-mozilla-html:FALSE version:2.1 end:vcard signature.asc Description: OpenPGP digital signature
Re: [gentoo-amd64] problem with gcc-4.0.2-r3
i already found out what was problem i had switched gcc profile to x86_64-pc-linux-gnu-3.4.4-hardened and i forget about it even that i was doing it once but thanks anyway On 1/27/06, Richard Fish <[EMAIL PROTECTED]> wrote: > On 1/26/06, Martin Ostrica <[EMAIL PROTECTED]> wrote: > > Hi i need for developing gcc-4 so i tried to emerge it i was following > > guide > > > > http://gentoo-wiki.com/HOWTO_gcc4 > > > > after successful emerging of all needed ebuild i was compiling gcc but > > i got this error > > > > > > > > cc1: warning: ssp stub: stack protector is not supported > > cc1: warning: ssp stub: stack protector is not supported > > Output of emerge --info please. > > -- > gentoo-amd64@gentoo.org mailing list > > -- gentoo-amd64@gentoo.org mailing list
Re: [gentoo-amd64] ailed to connect to socket /var/run/dbus/system_bus_socket k3b
I don't know if this can be of any help to you, but recently dbus was upgraded from version 0.50-r2 to version 0.60-r3. Check your version and do an revdep-rebuild if you recently upgraded. Another thing. Is dbus running (you can check by doing a /etc/init.d/dbus status)? If not try to run it (/etc/init.d/dbus start) and you should add it to you default runlevel (rc-update add dbus default). Regards -- Nuno Araujo <[EMAIL PROTECTED]> > Hello, > I found using k3b it fails at writing ~50% of an image. So I looked in > a terminal and found 'ailed to connect to > socket /var/run/dbus/system_bus_socket: no file'. So I tried as su > andalso received 'k3b: ERROR: (K3bDevice::Device) Unable to do > inquiry.'. I found > http://k3b.plainblack.com/message-board/error-k3bdevicedevice-unable-to-do-inquiry > I followed this through. But, still have the same probs. I upgraded to > the > kernel-genkernel-x86_64-2.6.14-gentoo-r5 kernel and I have the same > problem. Can anyone help? > Gavin. > -- > Dr Gavin Seddon > School of Pharmacy and Pharmaceutical Sciences > University of Manchester > Oxford Road, Manchester > M13 9PL, U.K. > > -- > gentoo-amd64@gentoo.org mailing list > > -- gentoo-amd64@gentoo.org mailing list
[gentoo-amd64] ailed to connect to socket /var/run/dbus/system_bus_socket k3b
Hello, I found using k3b it fails at writing ~50% of an image. So I looked in a terminal and found 'ailed to connect to socket /var/run/dbus/system_bus_socket: no file'. So I tried as su andalso received 'k3b: ERROR: (K3bDevice::Device) Unable to do inquiry.'. I found http://k3b.plainblack.com/message-board/error-k3bdevicedevice-unable-to-do-inquiry I followed this through. But, still have the same probs. I upgraded to the kernel-genkernel-x86_64-2.6.14-gentoo-r5 kernel and I have the same problem. Can anyone help? Gavin. -- Dr Gavin Seddon School of Pharmacy and Pharmaceutical Sciences University of Manchester Oxford Road, Manchester M13 9PL, U.K. -- gentoo-amd64@gentoo.org mailing list