Ok. I will edit the post to clarify everything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023645
Title:
ndiswrapper-dkms 1.57-1ubuntu1: ndiswrapper kernel module failed to
build [error:
Yes, it is the same version I used to generate the module.
I don't see anything special in your make.log. It's very similar to the
one generated by my computer. There are no errors. The compilation
process looks fine, but however it doesn't seem to find the binary after
the process...
I may know
Yes, this would be the most straightforward solution.
However, I arranged it the other way (using dkms) to automatise the
process when upgrading the kernel. Wouldn't it stop working if the
Ubuntu team released, let's say, a 3.5.0-18 kernel update? Then make +
make install would be necessary for
Can you post more information about the error? Make sure that you are
using the right version of the source code. Only the dkms.conf must be
preserved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Happens to me too. The problem is in the ndiswrapper source, as the
problem is present also when compiling manually ndiswrapper-source.
Updating to the newer 1.58rc1 version fixes the bug. I managed to
compile it through dkms using the same dkms.conf file from 1.57-1 (only
changing the
I tried the solution in the post linked by htrex, and it works perfectly
for me! (64 bit Ubuntu) :D
It really is only a matter of adding some text at the end of the 4th
line in the file /etc/X11/Xsession.d/10fglrx
The text is:
32 bit systems -- :/usr/lib32/dri/
64 bit systems --
Has someone digged into solving this bug?
With a fresh 12.04.1 install + post-release version of fglrx this bug
affects me as well. I haven't tried the workaround/solution posted by
htrex yet, but I assume that these problems should not be tolerated on
an LTS that has been released for months
But I don't understand your point. I have the same bug and I'm using a
wallpaper from the default Ubuntu set. I don't think it is a non
existing picture...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've been trying some possibilities and I think I found the trigger of
the bug in my system.
The idea is that the bug appears when the default user of the login
screen uses a wallpaper DIFFERENT from the default one. This means that
the bug won't appear if a user has changed the wallpaper but the
It seems to work.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/946674
Title:
unity-greeter crashed with SIGSEGV in background_loader_ready_cb()
To manage notifications about this bug
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971775
Title:
Light-dm enters a loop of crash and restart of the login screen
To manage notifications about this bug
In my case, the bug appeared every time I used the login screen (now I'm
using GDM as a workaround).
As said above, one way to stop the loop is moving up-down in the user
list (if you have more than 1 user, if not simply moving to the guest
session as the other user already said). I managed to
12 matches
Mail list logo
