On Mon, 2016-12-26 at 16:45 +, Patrick O'Callaghan wrote:
> On Mon, 2016-12-26 at 21:56 +0800, Ed Greshko wrote:
> >
> > On 12/26/16 20:37, Patrick O'Callaghan wrote:
> > > On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
> > > > For some reason there is no "Waiting for process" in the fai
On Mon, 2016-12-26 at 21:56 +0800, Ed Greshko wrote:
>
> On 12/26/16 20:37, Patrick O'Callaghan wrote:
> > On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
> > > For some reason there is no "Waiting for process" in the failing case.
> > > So, it would seem,
> > > either the PID being checked
On 12/26/16 20:37, Patrick O'Callaghan wrote:
> On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
>> For some reason there is no "Waiting for process" in the failing case. So,
>> it would seem,
>> either the PID being checked had already finished but another one had
>> started and locked
>>
On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
> For some reason there is no "Waiting for process" in the failing case. So,
> it would seem,
> either the PID being checked had already finished but another one had started
> and locked
> the database but somehow dnf is unaware of it and trie
On 12/25/16 00:14, Patrick O'Callaghan wrote:
> It seems unlikely that a specific package could be the cause of the bug
> rather than dnf itself (including the plugin of course). Package
> installation is often going to run scripts (complex ones in the case of
> akmod) so it would be up to dnf to
On Sat, 2016-12-24 at 08:34 +0800, Ed Greshko wrote:
>
> On 12/19/16 06:22, Patrick O'Callaghan wrote:
> > Of course, but in this case there is clearly a database lock for some
> > unexplained reason, which the dnf authors(s) did not expect to ever
> > happen (or they would have caught the excepti
On 12/19/16 06:22, Patrick O'Callaghan wrote:
> Of course, but in this case there is clearly a database lock for some
> unexplained reason, which the dnf authors(s) did not expect to ever
> happen (or they would have caught the exception).
>
> I guess I should BZ it.
Just a side note which *may*
On Mon, 2016-12-19 at 07:28 +0800, Ed Greshko wrote:
>
> On 12/19/16 06:22, Patrick O'Callaghan wrote:
> > Of course, but in this case there is clearly a database lock for some
> > unexplained reason, which the dnf authors(s) did not expect to ever
> > happen (or they would have caught the excepti
On 12/19/16 06:22, Patrick O'Callaghan wrote:
> Of course, but in this case there is clearly a database lock for some
> unexplained reason, which the dnf authors(s) did not expect to ever
> happen (or they would have caught the exception).
>
> I guess I should BZ it.
Looks like it already has be
On Mon, 2016-12-19 at 05:22 +0800, Ed Greshko wrote:
>
> On 12/19/16 02:49, Patrick O'Callaghan wrote:
> > On Sun, 2016-12-18 at 07:36 +0800, Ed Greshko wrote:
> > > On 12/18/16 07:22, Patrick O'Callaghan wrote:
> > > > This is fine as far as it goes, however I just had a failed boot
> > > > becau
On 12/19/16 02:49, Patrick O'Callaghan wrote:
> On Sun, 2016-12-18 at 07:36 +0800, Ed Greshko wrote:
>> On 12/18/16 07:22, Patrick O'Callaghan wrote:
>>> This is fine as far as it goes, however I just had a failed boot
>>> because although the akmod RPM did compile, it had an install error
>>> (t
On Sun, 2016-12-18 at 07:36 +0800, Ed Greshko wrote:
>
> On 12/18/16 07:22, Patrick O'Callaghan wrote:
> > This is fine as far as it goes, however I just had a failed boot
> > because although the akmod RPM did compile, it had an install error
> > (the key line being "sqlite3.OperationalError: dat
Thanks guys for all the output! However I did reinstall my whole system
yesterday so now I will go the RPMfusion way. Thanks again.
On Sun, Dec 18, 2016 at 1:36 AM, Ed Greshko wrote:
>
>
> On 12/18/16 07:22, Patrick O'Callaghan wrote:
> > This is fine as far as it goes, however I just had a fail
On 12/18/16 07:22, Patrick O'Callaghan wrote:
> This is fine as far as it goes, however I just had a failed boot
> because although the akmod RPM did compile, it had an install error
> (the key line being "sqlite3.OperationalError: database is locked").
> When I managed to track it down I went ba
On Sun, 2016-12-18 at 06:55 +0800, Ed Greshko wrote:
>
> On 12/17/16 23:39, Georgi Tsanov wrote:
> > I also installed the drivers this way:
> > https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ I dont
> > know if i was
> > uding RPMfusion
>
> You're not using RPMfusion. The metho
On 12/17/16 23:39, Georgi Tsanov wrote:
> I also installed the drivers this way:
> https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ I dont know
> if i was
> uding RPMfusion
You're not using RPMfusion. The method you're using requires a bit more skill
and
understanding than usi
I also installed the drivers this way:
https://www.if-not-true-then-false.com/2015/fedora-nvidia-guide/ I dont
know if i was uding RPMfusion
On Sat, Dec 17, 2016 at 5:52 AM, Ed Greshko wrote:
> Apologies if this makes it to the list twice. Not sure if it went out as
> a cat jumped on
> the keyb
The output of "uname -r":
4.8.13-300.fc25.x86_64
The output of "rpm -qa | grep ^kmod":
kmod-23-1.fc25.x86_64
kmod-libs-23-1.fc25.x86_64
On Sat, Dec 17, 2016 at 1:24 AM, Ed Greshko wrote:
>
>
> On 12/17/16 03:32, Rick Stevens wrote:
> > If you're not getting a GUI login, then the first thing to c
Apologies if this makes it to the list twice. Not sure if it went out as a cat
jumped on
the keyboard while sending. It left my screen but I don't see it in my "sent
mail".
On 12/17/16 03:32, Rick Stevens wrote:
> If you're not getting a GUI login, then the first thing to check are
> the sys
On 12/17/16 03:32, Rick Stevens wrote:
> If you're not getting a GUI login, then the first thing to check are
> the system logs by getting a console login (ALT-F2) and doing things
> like "journalctl -a -b" to see the log entries for the current boot (or
> "journalctl -a -b -1" to see them for th
On 12/16/2016 10:24 AM, Richard Ibbotson wrote:
> On Friday, 16 December 2016 17:13:35 GMT Georgi Tsanov wrote:
>> Thanks to responding i ran blkid to see the partitions and ran fsck
>> comman only for swap partition (dont know what this is) and home
>> partition. when i tried to run the fsck comma
On Friday, 16 December 2016 17:13:35 GMT Georgi Tsanov wrote:
> Thanks to responding i ran blkid to see the partitions and ran fsck
> comman only for swap partition (dont know what this is) and home
> partition. when i tried to run the fsck command for the root
> partition it said that the root is
i had an issue with kde after the update going to
4.8.13-300.fc25.x86_64 kernel
rebooted into the old kernel it worked, still have tried to debug it,
maybe try going back to the previous kernel
On Fri, Dec 16, 2016 at 10:13 AM, Georgi Tsanov wrote:
> Thanks to responding i ran blkid to see t
Thanks to responding i ran blkid to see the partitions and ran fsck comman
only for swap partition (dont know what this is) and home partition. when i
tried to run the fsck command for the root partition it said that the root
is mounted and it can cause damage. still cant figure out how to bring th
On Friday, 16 December 2016 15:25:15 GMT Georgi Tsanov wrote:
> My issue: I installed fedora 25 a few days ago alongside windows7. I
> had no problems with fedora i did an update, installed nvidia
> drivers and all the apps i need made the necessary configurations
> and everything was okey. Today (
My issue: I installed fedora 25 a few days ago alongside windows7. I had no
problems with fedora i did an update, installed nvidia drivers and all the
apps i need made the necessary configurations and everything was okey.
Today (2-3 days after the installation) when i rebooted from my windows7,
wen
26 matches
Mail list logo
