I have been trying to find out why my mythbox hangs on every shutdown.
Checked a lot of components (even switching to GDM from KDM) to no
avail.
Today I've found that it was the lirc process that hung. Disabling the
in_kernel_support in the stop part of the stop/start script fixed the
issue (like
Sorry, I should have been more clear on that one: it is the one Nicoalas
is seeing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/794234
Title:
imon and/or rc_imon_pad cause kernel oops
--
** Description changed:
I have a HTPC with and imon VFD / IR device (usb id: 15c2:ffdc).
If the system is off (shutdown) the first boot will cause the kernel to
oops on it. If I boot again, a fsck is performed on my root drive, which
will slow down the boot, but results in a successful
Public bug reported:
I have a HTPC with and imon VFD / IR device (usb id: 15c2:ffdc).
If the system is off (shutdown) the first boot will cause the kernel to
oops on it. If I boot again, a fsck is performed on my root drive, which
will slow down the boot, but results in a successful boot (in 90%
Since my HTPC has no keyboard and I do not have a serial cable it will
be hard for me to record the oops myself. If any other information is
needed, I will be more than happy to supply that though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Fabian: Although your issue might be somewhat related you are looking
at a different thing. Within natty the kernel comes with a complete new
imon driver. Therefore the ones in lirc-modules-source will fail. You
should not use the ones in lirc-modules-source anymore.
To completely get rid of it
This issue is still available in 10.10. A manual copy is still needed,
since dkms will not install the module from lirc based on the same
reasons mentioned above.
--
lirc_imon.ko does not get installed through dkms
https://bugs.launchpad.net/bugs/563727
You received this bug notification because
Sorry, I guess I somehow missed your question Dave: I do not see any
reason why the one included in the kernel fails. It seems to load
correctly. My imon device reamins blank though. With the one from the
dkms libraries text is displayed on my imon device.
If you could point me in the direction
I just found out I've made an error in the initial case: I need to
overwrite the original kernel version, not copy the lirc_imon.ko into
the updates, but I need to copy it into
/lib/modules/2.6.32-21-generic/kernel/ubuntu/lirc/lirc_imon/.
To answer your question: I removed all the lirc_imon.ko
Public bug reported:
Binary package hint: lirc
Dkms does not install the lirc_imon.ko from lirc_modules_source when the
kernel gets upgraded (in current lucid). The dkms output reads:
lirc_imon.ko:
Running module version sanity check.
Error! Module version 0.6 for lirc_imon.ko
is not newer
*** This bug is a duplicate of bug 513042 ***
https://bugs.launchpad.net/bugs/513042
I can confirm that this works for me as well.
--
[lucid] lirc-modules-source fails to build in dkms
https://bugs.launchpad.net/bugs/538105
You received this bug notification because you are a member of
I can confirm that the patch works for me.
--
package lirc-modules-source 0.8.6-0ubuntu2 failed to install/upgrade: lirc
kernel module failed to build
https://bugs.launchpad.net/bugs/513042
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I guess the flickering is normal and to be expected with the nvidia
driver. The nv driver doesn't have that problem with new kernels. Forgot
the what it is called, but with open drivers the kernel is now able to
set the display resolution.
Concerning gdm, I personally use kdm (it is QT based,
I can confirm the above solution fixes the issue. Fact remains that this
should somehow be updated/included in the package so people won't run
into it when installing hardy.
I can understand people want to promote KDE packages, but when you need
the Gnome ones, you don't want them to look that
*** This bug is a duplicate of bug 183173 ***
https://bugs.launchpad.net/bugs/183173
Did a dist-upgrade just today and flash plugin is working again!
--
Cannot install flash in Ubuntu Hardy 64 bit
https://bugs.launchpad.net/bugs/180854
You received this bug notification because you are a
Any new status. I think there are four people here who can confirm that
the new ia32-libs breaks flashplugin-nonfree. This should be fixed
before Hardy can go live IMHO. Anything we can do to help out?
--
Cannot install flash in Ubuntu Hardy 64 bit
https://bugs.launchpad.net/bugs/180854
You
*** This bug is a duplicate of bug 155015 ***
https://bugs.launchpad.net/bugs/155015
Sorry, me thinks this is not a duplicate. Installing the ia32-libs
package didn't fix my installation (ia32-libs was already installed by
the way).
I think the recent upgrade of the ia32-libs breaks the
Can confirm the bug on a Dell D830. It is almost driving me back to
feisty.
--
ipw3945: Error sending LEDS_CMD. Random driver crash.
https://bugs.launchpad.net/bugs/109887
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Installing the Dell tools, does improve the situation but it is not a
fix. Heavy NFS work (my Amarok rescan) will still crash the wireless
connection, although I do get a different error now in syslog:
Nov 6 08:51:25 bilbo NetworkManager: info Error getting killswitch
power arguments:
Seem that installing the Dell tools, results in the following bug:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/138794
The solution for that one now seems to be in gutsy-proposed. I am
currently testing that one and it seems to work!
** Changed in: linux-source-2.6.22 (Ubuntu)
Wrong package, fix in Networkmanager.
** Changed in: linux-ubuntu-modules-2.6.22 (Ubuntu)
Status: New = Fix Released
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
https://bugs.launchpad.net/bugs/155971
You received this bug notification because you are a
Wrong package, fix in Networkmanager.
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: Fix Committed = Fix Released
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
https://bugs.launchpad.net/bugs/155971
You received this bug notification because you are a
Fixed it for me. Used to have problems with rescanning my collection
with Amarok. Collection was on an NFS share always failed. Updated it
now while using Google Maps and ktorrent. All fine.
--
Error getting killswitch power arguments:
org.freedesktop.DBus.Error.InvalidArgs - Argument 0 is
Well that at least shows that the problem is not for AMD64 only.
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
https://bugs.launchpad.net/bugs/155971
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Not 100% sure yet, but the solution proposed here:
https://bugs.launchpad.net/ubuntu/+source/hal/+bug/131835 seems to fix
my problem.
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
https://bugs.launchpad.net/bugs/155971
You received this bug notification because you
As far as I can see this in not a duplicate of bug
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/154762.
It seems that they can regain their wireless by restarting
Networkmanager. For me this is not an option, since the daemon will not
restart (I guess because it is unable to kill
Public bug reported:
Binary package hint: linux-image-2.6.22-14-generic
Just did a complete new installation of gutsy removing my feisty
installation on my Dell D830.
Wireless is working flawlessly until some heavy load is required. To
reproduce the problem, I do an amarok collection scan which
For completeness sake (although it could be obvious): the amarok update
is done through an NFS share.
** Also affects: linux-ubuntu-modules-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
Syslog has some infos about the moment of the crash. Here it is.
** Attachment added: ipw3945_error.txt
http://launchpadlibrarian.net/10124825/ipw3945_error.txt
--
Gutsy regression: ipw3945 goes up to 100%CPU. No way to kill the process.
https://bugs.launchpad.net/bugs/155971
You received
The script (EBox.pm) is referring to user ebox and group ebox, that do
not exist yet.
I also found that the ebox user needs to control the /var/log/ebox
directory (chown -R ebox:ebox /var/log/ebox).
After fixing those, the startup script fails with the apache is not a
valid module name error.
** Changed in: ebox (Ubuntu)
Status: Fix Released = Incomplete
--
eBox configure fails
https://bugs.launchpad.net/bugs/127353
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
31 matches
Mail list logo
