On Mon, May 19, 2014 at 12:31:10 +0800, Baoquan He wrote:
> On 05/16/14 at 02:50pm, Martin Milata wrote:
> > On Fri, May 16, 2014 at 08:10:02 -0400, Vivek Goyal wrote:
> > > On Thu, May 15, 2014 at 11:30:22AM +0200, Martin Milata wrote:
> > > [..]
> > > > > > Oops, I didn't catch this email yesterday and went
ahead implementing
> > > > > > it. Scratch builds if you want to try it:
> > > > > >
> > > > > > F20:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6848717
> > > > > > rawhide:
http://koji.fedoraproject.org/koji/taskinfo?taskID=6848763
> > > > >
> > > > > Hi Martin,
> > > > >
> > > > > If you have already done the changes, I guess there is no need
to
> > > > > revert it.
> > > > >
> > > > > So after your changes, how do all three fields look like for the
case
> > > > > where /var/crash is mounted on some other disk, say /dev/foo.
> > > >
> > > > If /dev/foo (ext4) is mounted on /var/crash then it looks like this:
> > > >
> > > > ------------------------------------------------------------------
> > > > Path: /var/crash
> > > > Local file system: Partition: Unspecified
> > > > core will be in /%DATE on ext4 /dev/foo
> > > > ------------------------------------------------------------------
> > >
> > > Ok, this looks reasonable.
> >
> > Now built as system-config-kdump-2.0.15-2.fc21 for rawhide. I'm ready to
> > drop the partition detection logic if it proves to be confusing or
> > buggy.
>
> Hi Martin,
>
> I tested your update, it's like what we have discussed as below:
>
> ------------------------------------------------------------------
> Path: /var/crash
> Local file system: Partition: Unspecified
> core will be in /%DATE on ext4 /dev/foo
> ------------------------------------------------------------------
>
> About the change related to "Path", we all have agreed on this. Thanks
> for your effort.
>
> After several times of operations, erorr happened and below
> message was printed, paste it here for your reference.
>
> [bhe@localhost ~]$ system-config-kdump
> /usr/share/system-config-kdump/system-config-kdump.py:343: GtkWarning:
> IA__gtk_radio_button_set_group: assertion '!g_slist_find (group,
> radio_button)' failed
> "/usr/share/system-config-kdump/system-config-kdump.glade")
Did system-config-kdump crash as a result of this warning? GTK tends to
print messages like that with no apparent effect. If it crashes
system-config-kdump, do you know how to reproduce it?
I remember I just open s-c-k in term, then close it to change the mount
information, then open again. After several times, it just crashed.