2:37 p.m.
On 7/2/2013 3:34 PM, David wrote:
On 7/2/2013 2:42 PM, Luan Minh Pham wrote:
> On Tuesday, July 02, 2013 12:19:28 PM Paul W. Frields wrote:
>>> worked for my systems. I did a "fedup --network 19 -v" and a few
>>> hours later, all's good. Dell laptops all of them.
>>
>> Worked for me on two different vintage Dells (one a four-year-old XPS
>> workstation, the other a ~9 month old Inspiron something-or-other
>> desktop). Also worked well on a Lenovo laptop.
>
> Now how do I check if I run 18 or 19?
>
in a terminal type
cat /eat/fedora-release
and press the Enter key
sorry for my typo cat /etc/fedora-release
--
David
3:12 p.m.
On 02.07.2013 21:32, Lars E. Pettersson wrote:
On 07/02/2013 09:22 PM, poma wrote:
>> One way:
>> cat /etc/issue
>
> That's just one text file. :)
Yes, but:
$ rpm -qf /etc/issue
fedora-release-19-2.noarch
So the content gives quite a good clue :)
One could also chose "Settings" from the upper right menu in Gnome
(whatever that one is called), and chose "Details". On my computer it
says Fedora 19.
rpm -V rpm systemd
rpm -qif /usr/bin/rpm /usr/lib/systemd/systemd | grep Release :)
poma
6:18 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/02/2013 07:37 PM, Ed Greshko wrote:
On 07/03/13 07:34, Steven Stern wrote:
> On 07/02/2013 06:23 PM, Ed Greshko wrote:
>> On 07/03/13 06:13, Steven Stern wrote:
>>> On 07/02/2013 04:27 PM, Ed Greshko wrote:
>>>> On 07/03/13 04:32, Steven Stern wrote:
>>>>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>>>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>>>>> I'm about to try fedup f18->f19. Any reports good/bad
on
>>>>>>> this route?
>>>>>>>
>>>>>> Just finished the upgrade. Some of my XFCE settings aren't
>>>>>> quite right, but the changes aren't anything I can't
live
>>>>>> with... or care about enough to change right away.
>>>>>>
>>>>>> There doesn't seem to be an F19 Virtualbox repo yet, but the
>>>>>> F18 version is running OK.
>>>>>>
>>>>> Getting AVCs every time I start Chrome -- reported as a bug.
>>>> Hope you reported the bug to Google as it is a Chrome bug and and a
>>>> Fedora problem. This was discussed on the test list a while back.
>>>> A version of Chrome unstable had the fix....but it really was
>>>> unstable.
>>>>
>>>>
>>>>
>>> I reported it wherever the AVC bug reports go....
>>>
>>> https://bugzilla.redhat.com/show_bug.cgi?id=964651
>>>
>>> As it worked in F18 and not in F19, it seems to me it's a bug in the
>>> F19-supplied SELinux policy.
>>>
>> FWIW, I see in the report ....
>>
>> Source RPM Packages
>> google-chrome-stable-26.0.1410.63-192696.x86_64
>>
>> On my F19 test system, fedup'd from F18 I have....
>>
>> google-chrome-stable-28.0.1500.70-209565.x86_64
>> selinux-policy-3.12.1-54.fc19.noarch
>> selinux-policy-targeted-3.12.1-54.fc19.noarch
>>
>> And I am not seeing the AVC you're seeing. Have you considered
>> updating your Chrome?
>>
> My chrome package is google-chrome-beta-28.0.1500.70-209565.x86_64,
> straight from the Google repo. I switched from stable to beta to get rid
> of the last AVC problem.
>
So, you're saying that the beta of Chrome does not cause the AVC?
FWIW, my google-chrome-stable-28.0.1500.70-209565.x86_64 came directly from
the Google repo as well. But, I had to "yum clean metadata" before it was
picked up.
That bugzilla is waiting for the AVC output. Without the AVC we can not
understand the problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHUCIsACgkQrlYvE4MpobOe5ACfSb2RAGFryYFsMS/tc7AjGIWB
dncAoJMlz4UqypGB5CBNBDuKaSm540uX
=ueJf
-----END PGP SIGNATURE-----
10:51 p.m.
On Wed, 03 Jul 2013 11:10:50 +0800, Dick Roark wrote:
+1 Slick, quick(ish) and mighty, mighty pleasin'!
Thanks for the heads-up.
On Tue, Jul 2, 2013 at 11:32 PM, Harish Pillay
<harish.pillay(a)gmail.com>wrote:
> > I'm about to try fedup f18->f19. Any reports good/bad on this route?
>
> worked for my systems. I did a "fedup --network 19 -v" and a few hours
> later, all's good. Dell laptops all of them.
>
> Harish --
> users mailing list users(a)lists.fedoraproject.org To unsubscribe or
> change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users Guidelines:
> http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question?
> Ask away: http://ask.fedoraproject.org
Worked here as well, except for vncserver. I'm not sure what broke, but
systemctl status tells me it failed. I've forgotten how to get a more
complete message, so it's off to search I go.
I know, working on a laptop via vnc is kind of strange, but it's actually
pretty reasonable.
/mde/
10:10 p.m.
+1
Slick, quick(ish) and mighty, mighty pleasin'!
Thanks for the heads-up.
On Tue, Jul 2, 2013 at 11:32 PM, Harish Pillay <harish.pillay(a)gmail.com>wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on
this
> route?
worked for my systems. I did a "fedup --network 19 -v" and a few
hours later, all's good. Dell laptops all of them.
Harish
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
6:37 p.m.
On 07/03/13 07:34, Steven Stern wrote:
On 07/02/2013 06:23 PM, Ed Greshko wrote:
> On 07/03/13 06:13, Steven Stern wrote:
>> On 07/02/2013 04:27 PM, Ed Greshko wrote:
>>> On 07/03/13 04:32, Steven Stern wrote:
>>>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>>>> I'm about to try fedup f18->f19. Any reports good/bad on
this route?
>>>>>>
>>>>> Just finished the upgrade. Some of my XFCE settings aren't quite
right,
>>>>> but the changes aren't anything I can't live with... or care
about
>>>>> enough to change right away.
>>>>>
>>>>> There doesn't seem to be an F19 Virtualbox repo yet, but the F18
version
>>>>> is running OK.
>>>>>
>>>> Getting AVCs every time I start Chrome -- reported as a bug.
>>> Hope you reported the bug to Google as it is a Chrome bug and and a Fedora
problem. This was discussed on the test list a while back. A version of Chrome unstable
had the fix....but it really was unstable.
>>>
>>>
>>>
>> I reported it wherever the AVC bug reports go....
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=964651
>>
>> As it worked in F18 and not in F19, it seems to me it's a bug in the
>> F19-supplied SELinux policy.
>>
> FWIW, I see in the report ....
>
> Source RPM Packages google-chrome-stable-26.0.1410.63-192696.x86_64
>
> On my F19 test system, fedup'd from F18 I have....
>
> google-chrome-stable-28.0.1500.70-209565.x86_64
> selinux-policy-3.12.1-54.fc19.noarch
> selinux-policy-targeted-3.12.1-54.fc19.noarch
>
> And I am not seeing the AVC you're seeing. Have you considered updating your
Chrome?
>
My chrome package is google-chrome-beta-28.0.1500.70-209565.x86_64,
straight from the Google repo. I switched from stable to beta to get
rid of the last AVC problem.
So, you're saying that the beta of Chrome does not cause the AVC?
FWIW, my google-chrome-stable-28.0.1500.70-209565.x86_64 came directly from the Google
repo as well. But, I had to "yum clean metadata" before it was picked up.
--
The only thing worse than a poorly asked question is a cryptic answer.
6:34 p.m.
On 07/02/2013 06:23 PM, Ed Greshko wrote:
On 07/03/13 06:13, Steven Stern wrote:
> On 07/02/2013 04:27 PM, Ed Greshko wrote:
>> On 07/03/13 04:32, Steven Stern wrote:
>>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>>> I'm about to try fedup f18->f19. Any reports good/bad on this
route?
>>>>>
>>>> Just finished the upgrade. Some of my XFCE settings aren't quite
right,
>>>> but the changes aren't anything I can't live with... or care
about
>>>> enough to change right away.
>>>>
>>>> There doesn't seem to be an F19 Virtualbox repo yet, but the F18
version
>>>> is running OK.
>>>>
>>> Getting AVCs every time I start Chrome -- reported as a bug.
>> Hope you reported the bug to Google as it is a Chrome bug and and a Fedora
problem. This was discussed on the test list a while back. A version of Chrome unstable
had the fix....but it really was unstable.
>>
>>
>>
> I reported it wherever the AVC bug reports go....
>
> https://bugzilla.redhat.com/show_bug.cgi?id=964651
>
> As it worked in F18 and not in F19, it seems to me it's a bug in the
> F19-supplied SELinux policy.
>
FWIW, I see in the report ....
Source RPM Packages google-chrome-stable-26.0.1410.63-192696.x86_64
On my F19 test system, fedup'd from F18 I have....
google-chrome-stable-28.0.1500.70-209565.x86_64
selinux-policy-3.12.1-54.fc19.noarch
selinux-policy-targeted-3.12.1-54.fc19.noarch
And I am not seeing the AVC you're seeing. Have you considered updating your
Chrome?
My chrome package is google-chrome-beta-28.0.1500.70-209565.x86_64,
straight from the Google repo. I switched from stable to beta to get
rid of the last AVC problem.
--
-- Steve
6:23 p.m.
On 07/03/13 06:13, Steven Stern wrote:
On 07/02/2013 04:27 PM, Ed Greshko wrote:
> On 07/03/13 04:32, Steven Stern wrote:
>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>> I'm about to try fedup f18->f19. Any reports good/bad on this
route?
>>>>
>>> Just finished the upgrade. Some of my XFCE settings aren't quite right,
>>> but the changes aren't anything I can't live with... or care about
>>> enough to change right away.
>>>
>>> There doesn't seem to be an F19 Virtualbox repo yet, but the F18 version
>>> is running OK.
>>>
>> Getting AVCs every time I start Chrome -- reported as a bug.
> Hope you reported the bug to Google as it is a Chrome bug and and a Fedora problem.
This was discussed on the test list a while back. A version of Chrome unstable had the
fix....but it really was unstable.
>
>
>
I reported it wherever the AVC bug reports go....
https://bugzilla.redhat.com/show_bug.cgi?id=964651
As it worked in F18 and not in F19, it seems to me it's a bug in the
F19-supplied SELinux policy.
FWIW, I see in the report ....
Source RPM Packages google-chrome-stable-26.0.1410.63-192696.x86_64
On my F19 test system, fedup'd from F18 I have....
google-chrome-stable-28.0.1500.70-209565.x86_64
selinux-policy-3.12.1-54.fc19.noarch
selinux-policy-targeted-3.12.1-54.fc19.noarch
And I am not seeing the AVC you're seeing. Have you considered updating your Chrome?
--
The only thing worse than a poorly asked question is a cryptic answer.
5:43 p.m.
On 07/03/13 06:13, Steven Stern wrote:
On 07/02/2013 04:27 PM, Ed Greshko wrote:
> On 07/03/13 04:32, Steven Stern wrote:
>> On 07/02/2013 03:23 PM, Steven Stern wrote:
>>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>>> I'm about to try fedup f18->f19. Any reports good/bad on this
route?
>>>>
>>> Just finished the upgrade. Some of my XFCE settings aren't quite right,
>>> but the changes aren't anything I can't live with... or care about
>>> enough to change right away.
>>>
>>> There doesn't seem to be an F19 Virtualbox repo yet, but the F18 version
>>> is running OK.
>>>
>> Getting AVCs every time I start Chrome -- reported as a bug.
> Hope you reported the bug to Google as it is a Chrome bug and and a Fedora problem.
This was discussed on the test list a while back. A version of Chrome unstable had the
fix....but it really was unstable.
>
>
>
I reported it wherever the AVC bug reports go....
https://bugzilla.redhat.com/show_bug.cgi?id=964651
As it worked in F18 and not in F19, it seems to me it's a bug in the
F19-supplied SELinux policy.
OK.... the problem you've reported is different than the one previously discussed.
--
The only thing worse than a poorly asked question is a cryptic answer.
5:30 p.m.
I used the fedora-upgrade package with no problems at all. I'm not sure how
supported that package is but it was available from the base repo.
On Jul 2, 2013 12:14 PM, "Corinna Vinschen" <fedora(a)cygwin.de> wrote:
On Jul 2 23:32, Harish Pillay wrote:
> > I'm about to try fedup f18->f19. Any reports good/bad on this
> > route?
>
> worked for my systems. I did a "fedup --network 19 -v" and a few
> hours later, all's good. Dell laptops all of them.
Didn't work for me. fedup downloaded all packages and added the
"upgrade" entry to grub, but after the reboot, the upgrading failed
before any package was updated, and the system got rebooted. No entry
in the logs which would have helped or which would have allowed to
collect information for a bug report. I tried twice with the same
result. Eventually `yum distro-sync' did the job.
Corinna
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
5:13 p.m.
On 07/02/2013 04:27 PM, Ed Greshko wrote:
On 07/03/13 04:32, Steven Stern wrote:
> On 07/02/2013 03:23 PM, Steven Stern wrote:
>> On 07/02/2013 08:02 AM, Neal Becker wrote:
>>> I'm about to try fedup f18->f19. Any reports good/bad on this route?
>>>
>> Just finished the upgrade. Some of my XFCE settings aren't quite right,
>> but the changes aren't anything I can't live with... or care about
>> enough to change right away.
>>
>> There doesn't seem to be an F19 Virtualbox repo yet, but the F18 version
>> is running OK.
>>
> Getting AVCs every time I start Chrome -- reported as a bug.
Hope you reported the bug to Google as it is a Chrome bug and and a Fedora problem. This
was discussed on the test list a while back. A version of Chrome unstable had the
fix....but it really was unstable.
>
I reported it wherever the AVC bug reports go....
https://bugzilla.redhat.com/show_bug.cgi?id=964651
As it worked in F18 and not in F19, it seems to me it's a bug in the
F19-supplied SELinux policy.
--
-- Steve
4:27 p.m.
On 07/03/13 04:32, Steven Stern wrote:
--
The only thing worse than a poorly asked question is a cryptic answer.
On 07/02/2013 03:23 PM, Steven Stern wrote:
> On 07/02/2013 08:02 AM, Neal Becker wrote:
>> I'm about to try fedup f18->f19. Any reports good/bad on this route?
> > Just finished the upgrade. Some of my XFCE settings
aren't quite right,
> but the changes aren't anything I can't live with... or care about
> enough to change right away.
> There doesn't seem to be an F19 Virtualbox repo yet,
but the F18 version
> is running OK.
Getting AVCs every time I start Chrome -- reported as a bug.
Hope you reported the bug to Google as it is a Chrome bug and and a Fedora problem. This
was discussed on the test list a while back. A version of Chrome unstable had the
fix....but it really was unstable.
3:32 p.m.
On 07/02/2013 03:23 PM, Steven Stern wrote:
On 07/02/2013 08:02 AM, Neal Becker wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on this route?
>
Just finished the upgrade. Some of my XFCE settings aren't quite right,
but the changes aren't anything I can't live with... or care about
enough to change right away.
There doesn't seem to be an F19 Virtualbox repo yet, but the F18 version
is running OK.
Getting AVCs every time I start Chrome -- reported as a bug.
Also, my wifi card was renamed from wlan0 to wlp3s0.
--
-- Steve
3:23 p.m.
On 07/02/2013 08:02 AM, Neal Becker wrote:
I'm about to try fedup f18->f19. Any reports good/bad on this
route?
Just finished the upgrade. Some of my XFCE settings aren't quite right,
but the changes aren't anything I can't live with... or care about
enough to change right away.
There doesn't seem to be an F19 Virtualbox repo yet, but the F18 version
is running OK.
--
-- Steve
2:58 p.m.
Stephen Gallagher ha scritto / said the following il giorno/on
02/07/2013 15:03:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/02/2013 09:02 AM, Neal Becker wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on this
> route?
>
I'm mostly hearing good things at this point. A few people are
reporting that the final reboot at the end sometimes hangs[1], but
manually rebooting the system ends up in a workable state, so it's
survivable.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=957783
no, my system (quite old system, a Pentium 4
about 8 yo) cannot work
after fedup
I hope that we can debug otherwise I have to try a fesh installation...
First of all Gnome 3 works (I was running F18 in fallback mode)
when I enter an user name and password nothing happens, I get a blank
screen with fedora logo on the bottom and I have to issue a Ctrl+alt+f2
to enter as root or any other user, in text mode then with startx I am
in graphics...
If I start for example yumes as user I am requested the password, but I
get authentication error!!!
Systm is fully updated
--
Antonio M
Skype: amontag52
Linux Fedora F18(Spherical Cow) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHSz6EACgkQeiVVYja6o6N1kwCfeodraEGRCAfiY/crti8MOSNM
H+oAn2vPJ2adKtylJ/OJ0Dap42JtA9cu
=XUNr
-----END PGP SIGNATURE-----
2:34 p.m.
On 7/2/2013 2:42 PM, Luan Minh Pham wrote:
On Tuesday, July 02, 2013 12:19:28 PM Paul W. Frields wrote:
>> worked for my systems. I did a "fedup --network 19 -v" and a few
>> hours later, all's good. Dell laptops all of them.
>
> Worked for me on two different vintage Dells (one a four-year-old XPS
> workstation, the other a ~9 month old Inspiron something-or-other
> desktop). Also worked well on a Lenovo laptop.
Now how do I check if I run 18 or 19?
in a terminal type
cat /eat/fedora-release
and press the Enter key
--
David
2:32 p.m.
On 07/02/2013 09:22 PM, poma wrote:
> One way:
> cat /etc/issue
That's just one text file. :)
Yes, but:
$ rpm -qf /etc/issue
fedora-release-19-2.noarch
So the content gives quite a good clue :)
One could also chose "Settings" from the upper right menu in Gnome
(whatever that one is called), and chose "Details". On my computer it
says Fedora 19.
Lars
--
Lars E. Pettersson <lars(a)homer.se>
http://www.sm6rpz.se/
2:13 p.m.
On 07/02/2013 08:42 PM, Luan Minh Pham wrote:
Now how do I check if I run 18 or 19?
One way:
cat /etc/issue
Lars
--
Lars E. Pettersson <lars(a)homer.se>
http://www.sm6rpz.se/
1:42 p.m.
On Tuesday, July 02, 2013 12:19:28 PM Paul W. Frields wrote:
> worked for my systems. I did a "fedup --network 19 -v"
and a few
> hours later, all's good. Dell laptops all of them.
Worked for me on two different vintage Dells (one a four-year-old XPS
workstation, the other a ~9 month old Inspiron something-or-other
desktop). Also worked well on a Lenovo laptop.
Now how do I check if I run 18 or 19?
8:03 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/02/2013 09:02 AM, Neal Becker wrote:
I'm about to try fedup f18->f19. Any reports good/bad on
this
route?
I'm mostly hearing good things at this point. A few people are
reporting that the final reboot at the end sometimes hangs[1], but
manually rebooting the system ends up in a workable state, so it's
survivable.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=957783
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlHSz6EACgkQeiVVYja6o6N1kwCfeodraEGRCAfiY/crti8MOSNM
H+oAn2vPJ2adKtylJ/OJ0Dap42JtA9cu
=XUNr
-----END PGP SIGNATURE-----
11:19 a.m.
On Tue, Jul 02, 2013 at 11:32:26PM +0800, Harish Pillay wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on
this
> route?
worked for my systems. I did a "fedup --network 19 -v" and a few
hours later, all's good. Dell laptops all of them.
Worked for me on two different vintage Dells (one a four-year-old XPS
workstation, the other a ~9 month old Inspiron something-or-other
desktop). Also worked well on a Lenovo laptop.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
11:14 a.m.
On Jul 2 23:32, Harish Pillay wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on
this
> route?
worked for my systems. I did a "fedup --network 19 -v" and a few
hours later, all's good. Dell laptops all of them.
Didn't work for me. fedup downloaded all packages and added the
"upgrade" entry to grub, but after the reboot, the upgrading failed
before any package was updated, and the system got rebooted. No entry
in the logs which would have helped or which would have allowed to
collect information for a bug report. I tried twice with the same
result. Eventually `yum distro-sync' did the job.
Corinna
8:17 a.m.
On 2013-07-02 15:03, Stephen Gallagher wrote:
On 07/02/2013 09:02 AM, Neal Becker wrote:
> I'm about to try fedup f18->f19. Any reports good/bad on this
> route?
I'm mostly hearing good things at this point. A few people are
reporting that the final reboot at the end sometimes hangs[1], but
manually rebooting the system ends up in a workable state, so it's
survivable.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=957783
There is a serious issue when running inside VirtualBox on a 32 bit
architecture (X server won't start). See
https://bugzilla.redhat.com/show_bug.cgi?id=972095. The suggested fix
(comment 1) works for me.
--
Sjoerd Mullender
3951
days inactive
3952
days old
26 comments
18 participants
participants (18)
-
antonio montagnani -
Corinna Vinschen -
Daniel J Walsh -
David -
Dick Roark -
Ed Greshko -
Harish Pillay -
Joe Zeff -
Lars E. Pettersson -
Luan Minh Pham -
Mark Eggers -
Mark Haney -
Neal Becker -
Paul W. Frields -
poma -
Sjoerd Mullender -
Stephen Gallagher -
SternData