[Bug 287411] Kernel loses track of CWD of process
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=287411
--- Comment #52 from Ian Kent <ikent(a)redhat.com> 2009-05-26 22:34:34 EDT ---
(In reply to comment #51)
> (In reply to comment #48)
> > (In reply to comment #47)
> > > I can reproduce this as well by hibernating/resuming without an autofs restart.
> >
> > That could only happen if the sleep/wake functionality is doing
> > something like restarting autofs.
> >
> > In any case this should be resolved in autofs-5.0.4 and with a
> > sufficiently recent kernel and F-10 doesn't have such a kernel
> > F-11 does and its autofs is based on 5.0.4.
>
> Well, I'm now running F-11. After a hibernate/resume I have lost current
> working directories but automount has not be restarted:
Was it an upgrade or a fresh install?
IOW is the functionality enabled in the config.
Check that USE_MISC_DEVICE is not commented and is set to "yes"
in /etc/sysconfig/autofs.
It would also be useful to enable debug logging and check that
autofs has in fact been restarted over the hibernate cycle.
Just in case, instructions to setup debug logging are at
http://people.redhat.com/jmoyer.
Ian
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months
[Bug 236831] metacity lets me resize a window underneath my panel
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=236831
Jonathan Kamens <jik(a)kamens.brookline.ma.us> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CLOSED |ASSIGNED
Resolution|WORKSFORME |
--- Comment #13 from Jonathan Kamens <jik(a)kamens.brookline.ma.us> 2009-05-26 15:52:17 EDT ---
For me, it doesn't stop at the bottom panel.
So, what is different between your environment and mine? How can we figure
that out?
I am running everything current from rawhide.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months
[Bug 287411] Kernel loses track of CWD of process
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=287411
--- Comment #51 from Orion Poplawski <orion(a)cora.nwra.com> 2009-05-26 15:49:28 EDT ---
(In reply to comment #48)
> (In reply to comment #47)
> > I can reproduce this as well by hibernating/resuming without an autofs restart.
>
> That could only happen if the sleep/wake functionality is doing
> something like restarting autofs.
>
> In any case this should be resolved in autofs-5.0.4 and with a
> sufficiently recent kernel and F-10 doesn't have such a kernel
> F-11 does and its autofs is based on 5.0.4.
Well, I'm now running F-11. After a hibernate/resume I have lost current
working directories but automount has not be restarted:
[root@orca ~]# cwdcheck
[root@orca ~]# pm-hibernate
[root@orca ~]# cwdcheck
CWD problems
[root@orca ~]# ls -l /proc/*/cwd
lrwxrwxrwx. 1 root root 0 2009-05-26 13:39 /proc/1021/cwd -> /
....
lrwxrwxrwx. 1 orion cora 0 2009-05-26 13:39 /proc/22695/cwd ->
src/IT_TEST
lrwxrwxrwx. 1 orion cora 0 2009-05-26 13:39 /proc/2348/cwd ->
Note that some are broken links. "src/IT_TEST" is in /home/orion which is nfs
automounted. Looks like "/home/orion" was simply stripped from the cwd.
2.6.29.3-155.fc11.i686.PAE
autofs-5.0.4-24.i586
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months
[Bug 124246] grubby fatal error: unable to find a suitable template
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=124246
--- Comment #37 from Eric Paris <eparis(a)redhat.com> 2009-05-26 11:20:34 EDT ---
Did a little poking today, btrfs_getattr has a line like:
static int btrfs_getattr(struct vfsmount *mnt,
struct dentry *dentry, struct kstat *stat)
{
struct inode *inode = dentry->d_inode;
generic_fillattr(inode, stat);
stat->dev = BTRFS_I(inode)->root->anon_super.s_dev;
So btrfs (unlike every other fs in kernel) sets the dev themselves rather than
using the dev from generic_fillattr.
I'm guessing (but haven't verified) that this is the reason the ->dev found
when poking the block device is different than the dev btrfs is reporting and
thus the rejection...
I just ask an upstream btrfs maintainer why they do this....
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months
[Bug 502569] New: gnome-cd crashes on /dev/hdd but not on /dev/cdrom
by Red Hat Bugzilla
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
Summary: gnome-cd crashes on /dev/hdd but not on /dev/cdrom
https://bugzilla.redhat.com/show_bug.cgi?id=502569
Summary: gnome-cd crashes on /dev/hdd but not on /dev/cdrom
Product: Red Hat Enterprise Linux 5
Version: 5.4
Platform: All
OS/Version: Linux
Status: NEW
Status Whiteboard: bzcl34nup
Severity: medium
Priority: medium
Component: cdparanoia
AssignedTo: pjones(a)redhat.com
ReportedBy: rkhadgar(a)redhat.com
QAContact: qe-baseos-auto(a)redhat.com
CC: p.van.egdom(a)gmail.com, peterd(a)uwo.ca,
chris(a)rebelbase.com, pzubaj(a)marticonet.sk,
fedora-triage-list(a)redhat.com
Estimated Hours: 0.0
Classification: Red Hat
Target Release: ---
Clone Of: 187602
+++ This bug was initially created as a clone of Bug #187602 +++
gnome-cd works correctly if the device name is exactly /dev/cdrom.
However is segfaults on any other device name, that point
to the the same device.
/dev/cdrom is linked to hdd, so is /dev/cdwriter
gnome-cd crashes on /dev/hdd and /dev/cdwriter, but not on /dev/cdrom.
When clicking on the audio cd icon that appears when an
audio cd is inserted, gnome-cd is started as:
gnome-cd --unique --play --device /dev/hdd
therefore it crashes.
In cdparanoia source in file scan_devices.c in function sgio_cdda_identify_scsi
is this test:
if (check_fd_sgio(d->cdda_fd))
sgio_init_sg_info(d);
else
sg2_init_sg_info(d);
Function check_fd_sgio returns value < 0, on error or argement if ok. For some
unknown reason when device other as /dev/cdrom is used (/dev/hdc /dev/hdd)
cdda_fd = 0 is opened (this is valid fd, but zero) and check fails and
s2_init_sg_info is used (which is wrong). Check should be changed to:
if (check_fd_sgio(d->cdda_fd) == d->cdda_fd)
sgio_init_sg_info(d);
else
sg2_init_sg_info(d);
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
14 years, 11 months