Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
On 12/4/2011, at 5:49am, Carlos Sura wrote: ... When I try to run LibreOffice as normal user, I can see the splash (of libreoffice) but nothing more... Cannot use any libreoffice application, it just don't work, fas as I can see is the libreoffice splash. No errors (as normal user), after the libreoffice splash it closes. Is this when you click on the libreoffice icon, or are you opening a terminal window and running `/path/to/bin/libreoffice`? The latter should (hopefully) output some error messages. Stroller.
Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
On 12 April 2011 00:00, Stroller strol...@stellar.eclipse.co.uk wrote: On 12/4/2011, at 5:49am, Carlos Sura wrote: ... When I try to run LibreOffice as normal user, I can see the splash (of libreoffice) but nothing more... Cannot use any libreoffice application, it just don't work, fas as I can see is the libreoffice splash. No errors (as normal user), after the libreoffice splash it closes. Is this when you click on the libreoffice icon, or are you opening a terminal window and running `/path/to/bin/libreoffice`? The latter should (hopefully) output some error messages. Stroller. This happens when I click on the libreoffice icon, and as a normal user in a terminal: libreoffice (no output) as root: *GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed: (connection-initialization_error == NULL)* By the way, as a normal user either root, it just show me the splash screen of libreoffice, but, when it finish loading the splash bar, nothing happens, it just closes... No outputs, no errors, nothing... It might be GLIB? (I've reciently updated) -- Carlos Sura.-
Re: [gentoo-user] Re: qemu-kvm black screen and infinite loop on startup
On Thu, Apr 7, 2011 at 1:19 AM, Michael Orlitzky mich...@orlitzky.comwrote: On 04/06/2011 07:45 AM, Kfir Lavi wrote: When I run qemu -no-kvm things work as expected under hardened kernel. Using regular kernel (none hardened) qemu works ok. So, the problem is running qemu under hardened kernel. If someone have some input, I'll be happy to hear it. I am a long-time user of qemu/kvm under hardened. It works off and on. I don't have any scientific advice for you, only this: if you ever find a combination of kernel/qemu that works, *don't change anything*. Well, thanks for this advice. hehe I booted a none hardened kernel, and qemu started to work again. So yes, the hardened kernel is to blame. I wonder why qemu have problem with hardened kernel? Maybe some of the hardened devs can pitch in Regards, Kfir
Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
On Mon, 11 Apr 2011 22:49:24 -0600, Carlos Sura wrote: When I try to run LibreOffice as normal user, I can see the splash (of libreoffice) but nothing more... Cannot use any libreoffice application, it just don't work, fas as I can see is the libreoffice splash. No errors (as normal user), after the libreoffice splash it closes. You are creating an extra error, that occurs before the point it was previously failing, when you ru it as root. This error is useless and basically translates to Don't run me as root in a user session. The error is there because there is no DBus session set up for root. The frist step is to try rebuilding LO. Revdep-rebuild may not have shown a problem, but since this occurred after a world update, that could still be the cause. -- Neil Bothwick The facts, although interesting, are irrelevant. signature.asc Description: PGP signature
Re: [gentoo-user] raid1 grub ext4
On Mon, 11 Apr 2011 21:09:17 -0500, Mark Shields wrote: If /boot is on a separate partition, you should be using find /grub/stage1 If the symlink is there for boot - /boot -- and it is by default -- both work. I've found GRUB's handling of symlinks to be variable at best. Try searching for the real file. -- Neil Bothwick A chicken is an egg's way of producing more eggs. signature.asc Description: PGP signature
Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
110412 Carlos Sura wrote: On 12 April 2011 00:00, Stroller strol...@stellar.eclipse.co.uk wrote: Is this when you click on the libreoffice icon, or are you opening terminal window and running `/path/to/bin/libreoffice`? The latter should (hopefully) output some error messages. I agree : make sure you start it from a command line in a user terminal -- just forget all about running it as root -- tell us if there are any error messages in the terminal, eg warning that it can't find a particular library file. But first, make sure you remerge LibreOffice: that often solves problems. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
[gentoo-user] Re: raid1 grub ext4
Stroller stroller at stellar.eclipse.co.uk writes: James, if I'm not wrong (legacy) sys-boot/grub-0.97-r10 does not have drivers for ext4. Not sure if there's a patch for it, or if grub2 can boot from ext4. Mick, that's what I was wondering. No evidence either way, that I could find so I decided to make everything ext4. There's no need for extents on such a small partition, nor journalling (because you write to /boot so rarely, the likelihood of a power failure when you're doing so is minuscule). Yea, sure, but that's not the point. I just wanted to use ext4 for everything. Not on this system, but often, my boot partition is very active, as I copy many kernels there for many different (arch)machines and different hardware (HD, SSD, CF, SD...) I try to make the many systems I admin as homogeneous as possible, hence the switch to ext4 for boot. James
[gentoo-user] Re: raid1 grub ext4
Neil Bothwick neil at digimed.co.uk writes: If /boot is on a separate partition, you should be using It is. find /grub/stage1 grub find /grub/stage1 Error 15: File not found grub find /boot/grub/stage1 Error 15: File not found If the symlink is there for boot - /boot -- and it is by default -- both work. # ls -alg snip lrwxrwxrwx 1 root 1 Apr 6 21:40 boot - . drwxr-xr-x 2 root1024 Apr 11 12:05 grub I've found GRUB's handling of symlinks to be variable at best. Try searching for the real file. Everything I try within grub indicated the filesystem is unknown. Maybe unmount the boot partition, reformat it to ext2 copy over the kernrel (run what mdadm commands again) remount and see if it works? Other ideas? James
Re: [gentoo-user] Re: raid1 grub ext4
On Tuesday 12 April 2011 15:10:52 James wrote: Stroller stroller at stellar.eclipse.co.uk writes: There's no need for extents on such a small partition, nor journalling (because you write to /boot so rarely, the likelihood of a power failure when you're doing so is minuscule). Yea, sure, but that's not the point. I just wanted to use ext4 for everything. Not on this system, but often, my boot partition is very active, as I copy many kernels there for many different (arch)machines and different hardware (HD, SSD, CF, SD...) I try to make the many systems I admin as homogeneous as possible, hence the switch to ext4 for boot. Nevertheless, if ext4 isn't working for you you should follow the advice you've been given and format /boot as ext2. All my boot partitions are ext2, regardless of which others are ext4 or reiserfs. -- Rgds Peter
Re: [gentoo-user] Re: raid1 grub ext4
Peter Humphrey wrote: On Tuesday 12 April 2011 15:10:52 James wrote: Strollerstrollerat stellar.eclipse.co.uk writes: There's no need for extents on such a small partition, nor journalling (because you write to /boot so rarely, the likelihood of a power failure when you're doing so is minuscule). Yea, sure, but that's not the point. I just wanted to use ext4 for everything. Not on this system, but often, my boot partition is very active, as I copy many kernels there for many different (arch)machines and different hardware (HD, SSD, CF, SD...) I try to make the many systems I admin as homogeneous as possible, hence the switch to ext4 for boot. Nevertheless, if ext4 isn't working for you you should follow the advice you've been given and format /boot as ext2. All my boot partitions are ext2, regardless of which others are ext4 or reiserfs. Same here. I use ext3 and reiserfs, depending on what it is, but /boot is always ext2. Why, it works well with grub and has for many many years and most likely will for many years to come as well. As for making things the same, that my not always be a good idea either. I put some things on reiserfs but some on ext3. It seams each file system has its strengths and weaknesses. I read that portage, with a lot of small files, does better on ext* file systems. So I put portage on that. Most everything else is on reiserfs. Just my $0.02 worth and that ain't much. Dale :-) :-)
Re: [gentoo-user] Re: raid1 grub ext4
On Tuesday 12 April 2011 09:57:26 Dale wrote: Peter Humphrey wrote: On Tuesday 12 April 2011 15:10:52 James wrote: Strollerstrollerat stellar.eclipse.co.uk writes: There's no need for extents on such a small partition, nor journalling (because you write to /boot so rarely, the likelihood of a power failure when you're doing so is minuscule). Yea, sure, but that's not the point. I just wanted to use ext4 for everything. Not on this system, but often, my boot partition is very active, as I copy many kernels there for many different (arch)machines and different hardware (HD, SSD, CF, SD...) I try to make the many systems I admin as homogeneous as possible, hence the switch to ext4 for boot. Nevertheless, if ext4 isn't working for you you should follow the advice you've been given and format /boot as ext2. All my boot partitions are ext2, regardless of which others are ext4 or reiserfs. Same here. I use ext3 and reiserfs, depending on what it is, but /boot is always ext2. Why, it works well with grub and has for many many years and most likely will for many years to come as well. As for making things the same, that my not always be a good idea either. I put some things on reiserfs but some on ext3. It seams each file system has its strengths and weaknesses. I read that portage, with a lot of small files, does better on ext* file systems. So I put portage on that. Most everything else is on reiserfs. Where did you read that portage, with lots of small files, is best on ext*? I was under the impression that reiserfs has better performance with lots of smaller files. -- Joost
Re: [gentoo-user] Re: raid1 grub ext4
On Tuesday 12 April 2011 15:57:26 Dale wrote: As for making things the same, that my not always be a good idea either. I might add a quotation from Ralph Waldo Emerson: a foolish preoccupation with consistency is the hobgoblin of small minds. -- Rgds Peter
[gentoo-user] Printing phpmyadmin output
Hello list, I've a weird one here. I'm rebuilding my local server on an Atom N270 box and I've reached the point of installing phpmyadmin on it to manage a MySQL database I'm developing. Three different browsers have no trouble displaying table structures, data, the database design and the data dictionary, but when it comes to printing anything from phpmyadmin they all refuse to believe that more than one page exists. They will print other multi-page sites but not this one. Can anyone throw any light on this? I've remerged apache, php and phpmyadmin with no effect. -- Rgds Peter
[gentoo-user] Re: raid1 grub ext4
James wireless at tampabay.rr.com writes: I've found GRUB's handling of symlinks to be variable at best. Try searching for the real file. All the files are in /boot/grub: (chroot) slam grub # ls defaultgrub.conf minix_stage1_5 stage2.old device.map grub.conf.bak reiserfs_stage1_5 stage2_eltorito e2fs_stage1_5 iso9660_stage1_5 splash.xpm.gz ufs2_stage1_5 fat_stage1_5 jfs_stage1_5 stage1 vstafs_stage1_5 ffs_stage1_5 menu.lst stage2 xfs_stage1_5 Everything I try within grub indicated the filesystem is unknown. This stumps me http://bugs.gentoo.org/show_bug.cgi?id=250829 Bug above looks like this grub support of ext4 was flushed out and fixed some time ago? Maybe unmount the boot partition, reformat it to ext2 copy over the kernrel (run what mdadm commands again) remount and see if it works? This is still my best idea, if nobody has any other ideas? James
[gentoo-user] Can a forced volume check be interrupted?
Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. If you know it's going to run, then you can do one of two things: 1) I believe there is an option to ignore it entirely 2) If you use Interactive mode then you can skip that step. Both of those, however, require that you know (or assume) its going to run fsck. Ben - Original Message From: Grant emailgr...@gmail.com To: Gentoo mailing list gentoo-user@lists.gentoo.org Sent: Tue, April 12, 2011 1:31:31 PM Subject: [gentoo-user] Can a forced volume check be interrupted? Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, Apr 12, 2011 at 10:50:56AM -0700, BRM wrote: Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman rocket surgeon / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o
Re: [gentoo-user] Can a forced volume check be interrupted?
Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? Exactly. I couldn't get it to stop with ^C or i or I. - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
- Original Message From: Grant emailgr...@gmail.com Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? Exactly. I couldn't get it to stop with ^C or i or I. No. You can't. Nor do you want to at that point. Once it has started it really should run until completion otherwise you really risk data corruption. If you want to stop it, you have to prevent it from starting in the first place. Ben
Re: [gentoo-user] Can a forced volume check be interrupted?
Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? Exactly. I couldn't get it to stop with ^C or i or I. No. You can't. Nor do you want to at that point. Once it has started it really should run until completion otherwise you really risk data corruption. If you want to stop it, you have to prevent it from starting in the first place. Yeah, that can really be a drag. Last night my Gentoo HTPC checked the 2TB drive for 2 hours when I rebooted after a movie we were watching froze. - Grant
Re: [gentoo-user] Can a forced volume check be interrupted?
- Original Message From: Grant emailgr...@gmail.com To: gentoo-user@lists.gentoo.org Sent: Tue, April 12, 2011 3:29:35 PM Subject: Re: [gentoo-user] Can a forced volume check be interrupted? Probably, but why would you want to? it fixes any errors, and makes the file system relatively clean again so that things function well - and things don't get lost. If you skip it, you risk data corruption on disk. That misses the point. I have rebooted sometimes just for a quick change, possibly to try a different kernel, and intending to reboot several times. Then whoops! it starts a long fsck scan, not to repair damage, but just because some counter went to zero. What a waste. It's like insisting on an oil change exactly every 3000 miles. No, sorry, I will wait until it is convenient for *me*, not the odometer. So his question is, once the fsck has started, can he ^C to bomb it off, or do anything else to skip what has started? Exactly. I couldn't get it to stop with ^C or i or I. No. You can't. Nor do you want to at that point. Once it has started it really should run until completion otherwise you really risk data corruption. If you want to stop it, you have to prevent it from starting in the first place. Yeah, that can really be a drag. Last night my Gentoo HTPC checked the 2TB drive for 2 hours when I rebooted after a movie we were watching froze. As I said, if you are anticipating such a situation - or like the situation you are in - you can use the interactive boot or other methods to keep it from running to start with. That is your best bet, and your safest. Ben
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, Apr 12, 2011 at 12:31 PM, Grant emailgr...@gmail.com wrote: Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? Not once it has started, but there are some ways to avoid it running in the first place: Add fastboot to your kernel commandline to make it bypass the auto-fsck. A grub entry for skip fsck might be handy. Edit /etc/fstab to prevent the auto-fsck from ever running by changing the last field to 0. If it's an ext[123] you can use tune2fs -i 0 to set the auto-check interval to never.
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, Apr 12, 2011 at 2:52 PM, Paul Hartman paul.hartman+gen...@gmail.com wrote: If it's an ext[123] you can use tune2fs -i 0 to set the auto-check interval to never. oops, I of course meant 234 not 123 :)
[gentoo-user] configure wlan0 route metric
Hi all, For my home network I am generally using wireless to get connected to the network and the internet. However for copying some large files I use the wire. That means I get 2 IPs in the same range. And both interfaces get the same metric : 0. I found out I can modify the metric for the default route using metric_wlan0. Code: Destination Gateway Genmask Flags Metric RefUse Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 wlan0 0.0.0.0 192.168.1.1 0.0.0.0 UG2 00 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG10000 wlan0 (this is not the full routing table) However this changes the metric of the default route. Not of the route that is specifically for the local network. of course I can do this manually. However that is alot of hassle and seems to be something that should be configurable use files. Does anyone knows how I can accomplish this? Or how I can change the metric for each route for the wlan0 interface? Thanks in advance!
[gentoo-user] Re: Can a forced volume check be interrupted?
Paul Hartman: On Tue, Apr 12, 2011 at 2:52 PM, Paul Hartman If it's an ext[123] you can use tune2fs -i 0 to set the auto-check interval to never. oops, I of course meant 234 not 123 :) ;) But i prefer setting the interval to 1000 with 'tune2fs -c'. | It is strongly recommended that either -c (mount-count-depen- | dent) or -i (time-dependent) checking be enabled to force peri- | odic full e2fsck(8) checking of the filesystem. Hartmut -- Usenet-ABC-Wiki http://www.usenet-abc.de/wiki/ Von Usern fuer User :-)
Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
On 12 April 2011 04:09, Philip Webb purs...@ca.inter.net wrote: 110412 Carlos Sura wrote: On 12 April 2011 00:00, Stroller strol...@stellar.eclipse.co.uk wrote: Is this when you click on the libreoffice icon, or are you opening terminal window and running `/path/to/bin/libreoffice`? The latter should (hopefully) output some error messages. I agree : make sure you start it from a command line in a user terminal -- just forget all about running it as root -- tell us if there are any error messages in the terminal, eg warning that it can't find a particular library file. But first, make sure you remerge LibreOffice: that often solves problems. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca Hello, thank you for answer me. Yes, running as root cause me that message. Anyway, I reinstalled LibreOffice, and isn't working yet. As I try to run as (normal) user -terminal-, does not show me any output, no errors, no message. Is there any log I can look for? Isn't working yet, and I do not have any clue about what could cause me this. Regards -- Carlos Sura.-
Re: [gentoo-user] Can a forced volume check be interrupted?
On Tue, 2011-04-12 at 14:52 -0500, Paul Hartman wrote: On Tue, Apr 12, 2011 at 12:31 PM, Grant emailgr...@gmail.com wrote: Sometimes the ext3 forced volume check at boot triggers at an inopportune time. Is there a way to skip it and let it run at the next boot? Not once it has started, but there are some ways to avoid it running in the first place: Add fastboot to your kernel commandline to make it bypass the auto-fsck. A grub entry for skip fsck might be handy. Edit /etc/fstab to prevent the auto-fsck from ever running by changing the last field to 0. If it's an ext[123] you can use tune2fs -i 0 to set the auto-check interval to never. Thats one reason I have been looking at btrfs - online fsck. Has been solid even on unexpected crashes (I am setting up remote power on/off and pressed the wrong button - more than once :) I actually had some minor corruption on reiserfs, but btrfs was fine and could be checked online anyway in a lot less time than reiserfsck took. BillK
Re: [gentoo-user] LibreOffice + GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: assertion failed
As I try to run as (normal) user -terminal-, does not show me any output, no errors, no message. What happens when you run X as the root user? Do you get the same error? That is, log into a regular system terminal, start X, and run LO.
