The machine details:
- Dell XPS 17 (L702X) BIOS A19
- Intel Core i7-2720QM (2.2GHZ)
- Intel Sandybridge
- Nvidia GeForce GT 555M
From a complete fresh install of F19, I’m seeing 214 updates. The updates break down into 8 security, 80 bugfix, 22 enhancements, and the rest are dependencies. I am attempting to narrow down which update is causing the problem, and so far I believe it to be in the 80 bugfix updates, because after a `yum –bugfix update` the machine starts having the issue.
A little history:
This machine was on F18 and I did a FedUp to F19 without issue. On July 10th I decided to install F19 fresh and at that time there were only 191 updates which installed fine; however, I decided I wanted to encrypt the partition and started from scratch again, but now there are 214 updates and the machine has this issue.
Is there some way I can have yum update based on a timestamp or display a timestamp on when these updates were posted to help me narrow the field?
Thanks
On 07/14/13 06:46, Powell, Michael wrote:
Is there some way I can have yum update based on a timestamp or display a timestamp on when these updates were posted to help me narrow the field?
/var/log/yum.log has date/time updates were applied
Greshko, Ed wrote:>
/var/log/yum.log has date/time updates were applied
Thanks, Ed. Unfortunately I don't need a timestamp of when the updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191 updates of the 214 worked a few days ago, if I can narrow down to the newest 23 packages, I might be able to find the trouble maker.
On 07/14/13 07:30, Powell, Michael wrote:
Greshko, Ed wrote:>
/var/log/yum.log has date/time updates were applied
Thanks, Ed. Unfortunately I don't need a timestamp of when the updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191 updates of the 214 worked a few days ago, if I can narrow down to the newest 23 packages, I might be able to find the trouble maker.
I'm not aware of a way to do it via yum. But, you could always do it manually by connecting to an update server via ftp or http and checking the dates. Should give you an idea.
On 07/14/13 07:30, Powell, Michael wrote:
Greshko, Ed wrote:>
/var/log/yum.log has date/time updates were applied
Thanks, Ed. Unfortunately I don't need a timestamp of when the
updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191 updates of the 214 worked a few days ago, if I can narrow down to the newest 23 packages, I might be able to find the trouble maker.
I'm not aware of a way to do it via yum. But, you could always do it manually by connecting to an update server via ftp or http and checking the dates. Should give you an idea.
Thanks, Ed! I've narrowed it down:
- xorg-x11-server-Xorg-1.14.2-3.fc19.x86_64.rpm - xorg-x11-server-common-1.14.2-3.fc19.x86_64.rpm
One or both of those packages hose my machine. I'm going to put xorg-x11-server* in my yum.conf for a while to avoid any more issues.
Maybe I'll open a bug report, but I'm sure without some more info it wouldn't help.
On 07/14/13 09:39, Powell, Michael wrote:
On 07/14/13 07:30, Powell, Michael wrote:
Greshko, Ed wrote:>
/var/log/yum.log has date/time updates were applied
Thanks, Ed. Unfortunately I don't need a timestamp of when the
updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191 updates of the 214 worked a few days ago, if I can narrow down to the newest 23 packages, I might be able to find the trouble maker.
I'm not aware of a way to do it via yum. But, you could always do it manually by connecting to an update server via ftp or http and checking the dates. Should give you an idea.
Thanks, Ed! I've narrowed it down:
- xorg-x11-server-Xorg-1.14.2-3.fc19.x86_64.rpm
- xorg-x11-server-common-1.14.2-3.fc19.x86_64.rpm
One or both of those packages hose my machine. I'm going to put xorg-x11-server* in my yum.conf for a while to avoid any more issues.
Maybe I'll open a bug report, but I'm sure without some more info it wouldn't help.
If you can duplicate the problem you really should open a bugzilla. You may not know what additional information is needed.....but if more info is needed you'll be asked to provide it by the person assigned.
On 07/14/13 09:39, Powell, Michael wrote:
On 07/14/13 07:30, Powell, Michael wrote:
Greshko, Ed wrote:>
/var/log/yum.log has date/time updates were applied
Thanks, Ed. Unfortunately I don't need a timestamp of when the
updates were applied to the machine, but instead, I need a timestamp of when those updates were posted to the yum server. My thought is that since I know 191 updates of the 214 worked a few days ago, if I can narrow down to the newest 23 packages, I might be able to find the trouble maker.
I'm not aware of a way to do it via yum. But, you could always do
it
manually by connecting to an update server via ftp or http and checking the dates. Should give you an idea.
Thanks, Ed! I've narrowed it down:
- xorg-x11-server-Xorg-1.14.2-3.fc19.x86_64.rpm
- xorg-x11-server-common-1.14.2-3.fc19.x86_64.rpm
One or both of those packages hose my machine. I'm going to put xorg-
x11-server* in my yum.conf for a while to avoid any more issues.
Maybe I'll open a bug report, but I'm sure without some more info it
wouldn't help.
If you can duplicate the problem you really should open a bugzilla. You may not know what additional information is needed.....but if more info is needed you'll be asked to provide it by the person assigned.
Looks like someone beat me to it :) https://bugzilla.redhat.com/show_bug.cgi?id=984121
On 07/14/13 10:17, Powell, Michael wrote:
Looks like someone beat me to it :) https://bugzilla.redhat.com/show_bug.cgi?id=984121
Yeah, and it seems you can download and test a potential fix at,
https://admin.fedoraproject.org/updates/FEDORA-2013-12886/xorg-x11-server-1....