On 07/01/16 13:39, Ed Greshko wrote:
>
> On 07/01/16 13:16, Tim wrote:
>> Well, you're participating on a list for Fedora, and many services are
>> managed by those people. If it's the Fedora list that's misidentifying
>> spam on the way through, its software needs looking at. But I seem to
>>
On 07/01/16 13:16, Tim wrote:
> Well, you're participating on a list for Fedora, and many services are
> managed by those people. If it's the Fedora list that's misidentifying
> spam on the way through, its software needs looking at. But I seem to
> recall the conversation pointing the finger a
Allegedly, on or about 01 July 2016, Joel Rees sent:
> (The blame lies elsewhere.
Yes. While I can't answer to the causes for other people's mail turning
up misidentified as spam, I can say that when I mail this list using a
Yahoo address, it's sent through the Yahoo SMTP servers, and I have
logg
To keep this off-list as much as possible, the rant is here:
http://reiisi.blogspot.com/2016/07/to-gil-tim-fedora-et-al.html
(The blame lies elsewhere. I wish I had the network and social cred to
get a real movement started, away from the current faceless CA system
and towards a different identit
On 07/01/16 05:29, Stephen Morris wrote:
> On 30/06/16 07:19, Tom Horsley wrote:
>> I was so happy when the nouveau driver finally worked
>> on my nvidia maxwell card in fedora 24, but now after
>> about a week, this happened:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1351286
>>
>> Total
On 30/06/16 07:19, Tom Horsley wrote:
I was so happy when the nouveau driver finally worked
on my nvidia maxwell card in fedora 24, but now after
about a week, this happened:
https://bugzilla.redhat.com/show_bug.cgi?id=1351286
Total screen freeze :-(.
At least it took as long as a week.
If it
On 06/29/2016 05:31 PM, a...@clueserver.org wrote:
I was so happy when the nouveau driver finally worked
on my nvidia maxwell card in fedora 24, but now after
about a week, this happened:
https://bugzilla.redhat.com/show_bug.cgi?id=1351286
Total screen freeze :-(.
At least it took as long as a
On 06/30/2016 12:40 PM, Richard Shaw wrote:
> Ok, I think I was able to catch the error without having to get that
> desparate :)
>
> I logged in from work and did journalctl -f and got the following:
>
> http://pastebin.com/3JAL297z
>
> Looks disk hardware related but it's not getting worse so
Ok, I think I was able to catch the error without having to get that
desparate :)
I logged in from work and did journalctl -f and got the following:
http://pastebin.com/3JAL297z
Looks disk hardware related but it's not getting worse so I doubt it's the
disk itself, driver problem instead?
Thank
On 06/30/2016 12:10 PM, stan wrote:
On Thu, 30 Jun 2016 11:54:45 -0400
"Eddie O'Connor" wrote:
Is this something that's going to affect my EXTREMELY OLD Gateway
T6321 laptop?
Unlikely if you aren't having issues already. Nouveau has been having
lockup issues for a long time.
The nouveau bu
On Thu, 30 Jun 2016 11:54:45 -0400
"Eddie O'Connor" wrote:
> Is this something that's going to affect my EXTREMELY OLD Gateway
> T6321 laptop?
Unlikely if you aren't having issues already. Nouveau has been having
lockup issues for a long time.
The nouveau bug report about lockups seems to sugg
On Thu, Jun 30, 2016 at 8:56 AM, Chris Murphy wrote:
>
>
> On Thu, Jun 30, 2016, 6:21 AM Richard Shaw wrote:
>>
>> Ok, apparently I need to reboot this conversation :)
>>
>> The filesystem is not corrupted (other than what occurs during a forced
>> power off). Many days, it boots and runs just fi
Is this something that's going to affect my EXTREMELY OLD Gateway T6321
laptop?I was under the impression that "Wayland" was going to solve the
issues with drivers that didn't quite work? (I was thinking of upgrading my
hardware to a Lenovo IdeaPad...but if there might be funky things happening
On Thu, Jun 30, 2016, 6:21 AM Richard Shaw wrote:
> Ok, apparently I need to reboot this conversation :)
>
> The filesystem is not corrupted (other than what occurs during a forced
> power off). Many days, it boots and runs just fine for the whole day,
> when it does have a problem, it's not a bo
On 06/30/16 20:49, Tom Horsley wrote:
> On Thu, 30 Jun 2016 19:53:51 +0800
> Ed Greshko wrote:
>
>>> The rpmfusion repos don't seem to have an akmod-nvidia package
>>> for fedora 24.
>> What do you mean?
> It wasn't there this morning. I cleaned metadata, I reinstalled
> the rpmfusion repos, dn
I have a USB ethernet adapter on my desktop system that I use when
configuring new equipment (servers, routers, switches, etc.). I have a
variety of pre-set configs in NM, like 192.168.0.x, 10.0.0.x, etc.
Often while configuring something, I need to reboot it, which drops the
link. NM "helpfully
On Thu, 30 Jun 2016 19:53:51 +0800
Ed Greshko wrote:
> > The rpmfusion repos don't seem to have an akmod-nvidia package
> > for fedora 24.
>
> What do you mean?
It wasn't there this morning. I cleaned metadata, I reinstalled
the rpmfusion repos, dnf install kept telling me there is no akmod-nv
Ok, apparently I need to reboot this conversation :)
The filesystem is not corrupted (other than what occurs during a forced
power off). Many days, it boots and runs just fine for the whole day, when
it does have a problem, it's not a boot but rather towards the latter part
of the day.
So somethi
On 06/30/16 19:47, Tom Horsley wrote:
> I had to back up one kernel release to get kmod-nvidia to work :-(.
>
> The rpmfusion repos don't seem to have an akmod-nvidia package
> for fedora 24.
What do you mean?
[egreshko@meimei ~]$ rpm -q akmod-nvidia
akmod-nvidia-358.16-2.fc24.x86_64
--
You'
I had to back up one kernel release to get kmod-nvidia to work :-(.
The rpmfusion repos don't seem to have an akmod-nvidia package
for fedora 24.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lis
I followed your guideline and it works just as expected now.
Thank you very much Richard! :)
Cheers
Mat
Am 30.06.2016 um 10:14 schrieb Richard Hughes:
> On 30 June 2016 at 08:37, Richard Hughes wrote:
>> You can get it from koji; I forgot to do the f24 build:
> Done:
> https://bodhi.fedorapro
On Thu, Jun 30, 2016 at 9:35 AM, Walter Cazzola wrote:
> On Wed, 29 Jun 2016, Michal Domonkos wrote:
>
>> It looks like something that is being updated is pulling in the yum
>> package as a dependency. As Tom mentioned, you can find out by trying
>> to remove yum, or even better, by running "dnf
On 30 June 2016 at 08:37, Richard Hughes wrote:
> You can get it from koji; I forgot to do the f24 build:
Done:
https://bodhi.fedoraproject.org/updates/fwupd-0.7.2-1.fc24%20libappstream-glib-0.5.16-1.fc24
You need to install it, reboot, remove the USB device, replug and then
you should be good
On 30 June 2016 at 06:57, Matthew Colton wrote:
> Update fwupd. There is a DFU issue we only recently found and fixed. Richard
Sorry for the short response, I was on mobile and too tired to find a
laptop. See https://github.com/hughsie/fwupd/issues/50 for the
upstream bug.
> Do you mean updating
On Wed, 29 Jun 2016, Michal Domonkos wrote:
It looks like something that is being updated is pulling in the yum
package as a dependency. As Tom mentioned, you can find out by trying
to remove yum, or even better, by running "dnf repoquery --installed
--whatrequires yum".
at the moment yum is
25 matches
Mail list logo
