lcdproc for imon_lcd stopped working

Bug #1176226 reported by Bengt Nilsson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The front panel display on my IMON-LCD served by the lcdproc daemon stopped working today 03-may-2013.

"dmesg | grep imon" shows

[ 2.522101] Registered IR keymap rc-imon-pad
[ 2.528111] imon 5-4:1.0: iMON device (15c2:0038, intf0) on usb<5:2> initialized
[ 2.528134] imon 5-4:1.1: iMON device (15c2:0038, intf1) on usb<5:2> initialized
[ 2.528150] usbcore: registered new interface driver imon
[ 2.796900] imon 5-4:1.0: Looks like you're trying to use an IR protocol this device does not support
[ 2.796903] imon 5-4:1.0: Unsupported IR protocol specified, overriding to iMON IR protocol
[ 6.286862] imon:send_packet: error submitting urb(-22)
[ 6.291026] imon:lcd_write: send packet failed!
[ 6.291052] imon:send_packet: error submitting urb(-22)
[ 6.296011] imon:lcd_write: send packet failed!
[ 6.296025] imon:send_packet: error submitting urb(-22)
[ 6.301019] imon:lcd_write: send packet failed!
[ 6.301030] imon:send_packet: error submitting urb(-22)
[ 6.306028] imon:lcd_write: send packet failed!
[ 6.306040] imon:send_packet: error submitting urb(-22)
[ 6.311062] imon:lcd_write: send packet failed!

Most obvious symptom is that my /etc/LCDd.conf is set to turn off the backlight at boot, and as of from today it does not do that anymore.
The daemon i still running:
bnilsson@HTPC:~$ ps -ef | grep LCD
nobody 1171 1 0 May03 ? 00:00:12 /usr/sbin/LCDd -s 1 -f -c /etc/LCDd.conf

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: update-manager 1:0.156.14.11
ProcVersionSignature: Ubuntu 3.2.0-41.45-lowlatency 3.2.42
Uname: Linux 3.2.0-41-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Sat May 4 00:19:34 2013
GsettingsChanges:
 com.ubuntu.update-manager first-run false
 com.ubuntu.update-manager launch-time 1367610737
 com.ubuntu.update-manager window-height 500
 com.ubuntu.update-manager window-width 600
InstallationMedia: Ubuntu-Studio 12.04 "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=sv:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager
Symptom: ubuntu-release-upgrader-core
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bnilsson 18734 F.... pulseaudio
                      tvtittare 26658 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=d813310e-6306-47f5-b238-5db3a4fc4c64
InstallationDate: Installed on 2013-08-24 (121 days ago)
InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Release amd64 (20130424)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-lowlatency root=UUID=292338a9-8841-4f3c-917a-b84a6834838a ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-34.26-lowlatency 3.8.13.12
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-34-lowlatency N/A
 linux-backports-modules-3.8.0-34-lowlatency N/A
 linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-34-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

dmi.bios.date: 09/30/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-880GMA-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GMA-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
---
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bnilsson 18734 F.... pulseaudio
                      tvtittare 26658 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=d813310e-6306-47f5-b238-5db3a4fc4c64
InstallationDate: Installed on 2013-08-24 (121 days ago)
InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Release amd64 (20130424)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-880GMA-UD2H
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-lowlatency root=UUID=292338a9-8841-4f3c-917a-b84a6834838a ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-34.26-lowlatency 3.8.13.12
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-34-lowlatency N/A
 linux-backports-modules-3.8.0-34-lowlatency N/A
 linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-34-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

dmi.bios.date: 09/30/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-880GMA-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd09/30/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GMA-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GMA-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-880GMA-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :
Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Could be related to unpredictable/changing /dev/lcd* device name between boots.
If the device name referred to in /etc/LCDd.conf does not match the real device name, nothing works.

affects: update-manager (Ubuntu) → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1176226

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

This is issue probably connected to Bug #1216366, which I reported later than this issue.
The device used by lcdproc, /dev/lcd0, if changing between /dv/lcd0 and /dev/lcd1 between boots, either toggling or random.
If /dev/lcd0 is set in LCDd.conf and the existing device is /dev/lcd1, of course nothing works.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

sudo apport-collect 1176226
ERROR: The launchpadlib Python module is not installed. This functionality is not available.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected raring
description: updated
Revision history for this message
Bengt Nilsson (bnilsson11) wrote : BootDmesg.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : Lspci.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : Lsusb.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcModules.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : UdevDb.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : UdevLog.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Ok, found python-launchpadlib (why call it "launchpadlib Python module" when it is really called "python-launchpadlib"?)
Logs sent.

description: updated
Revision history for this message
Bengt Nilsson (bnilsson11) wrote : AlsaInfo.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : BootDmesg.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : HookError_cloud_archive.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : Lspci.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : Lsusb.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : ProcModules.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : UdevDb.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote : UdevLog.txt

apport information

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Got this when collecting info:

(process:3526): GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0' failed
dpkg-query: inga paket hittades som matchar linux
ERROR: hook /usr/share/apport/general-hooks/cloud_archive.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 197, in _run_hook
    symb['add_info'](report, ui)
  File "/usr/share/apport/general-hooks/cloud_archive.py", line 18, in add_info
    if '~cloud' in packaging.get_version(package) and \
  File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 123, in get_version
    raise ValueError('package %s does not exist' % package)
ValueError: package linux does not exist

Is this serious? Is some required info still missing?

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc6-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

I will try to test during the next following days.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Got this:

root@HTPC:/home/bnilsson/Byggen# dpkg -i linux-image-3.13.0-031300rc6-generic_3.13.0-031300rc6.201312291935_amd64.deb
Väljer tidigare ej valt paket linux-image-3.13.0-031300rc6-generic.
(Läser databasen ... 345834 filer och kataloger installerade.)
Packar upp linux-image-3.13.0-031300rc6-generic (från linux-image-3.13.0-031300rc6-generic_3.13.0-031300rc6.201312291935_amd64.deb) ...
Done.

Ställer in linux-image-3.13.0-031300rc6-generic (3.13.0-031300rc6.201312291935) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
Error! Your kernel headers for kernel 3.13.0-031300rc6-generic cannot be found.
Please install the linux-headers-3.13.0-031300rc6-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-031300rc6-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-031300rc6-generic /boot/vmlinuz-3.13.0-031300rc6-generic
Genererar grub.cfg ...
Hittade linux-avbildning: /boot/vmlinuz-3.13.0-031300rc6-generic
Hittade initrd-avbildning: /boot/initrd.img-3.13.0-031300rc6-generic
Hittade linux-avbildning: /boot/vmlinuz-3.8.0-35-lowlatency
Hittade initrd-avbildning: /boot/initrd.img-3.8.0-35-lowlatency
Hittade linux-avbildning: /boot/vmlinuz-3.8.0-34-lowlatency
Hittade initrd-avbildning: /boot/initrd.img-3.8.0-34-lowlatency
Hittade linux-avbildning: /boot/vmlinuz-3.8.0-33-lowlatency
Hittade initrd-avbildning: /boot/initrd.img-3.8.0-33-lowlatency
Hittade linux-avbildning: /boot/vmlinuz-3.8.0-30-lowlatency
Hittade initrd-avbildning: /boot/initrd.img-3.8.0-30-lowlatency
Hittade linux-avbildning: /boot/vmlinuz-3.8.0-29-lowlatency
Hittade initrd-avbildning: /boot/initrd.img-3.8.0-29-lowlatency
Found memtest86+ image: /boot/memtest86+.bin
färdigt

Are the headers necessary?

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Tested the kernel without headers briefly, did not seem to improve.
The device had stayed /dev/lcd1 for a while with the old kernel, and I would have expected it would change to /dev/lcd0 stable with the new kernel but it did not. It remained as /dev/lcd1 after the first boot. Not conclusive, but I had no possibility to spend long time with the new kernel since it did not seem completely compatible with my system, I am using the lowlatency kernel in ubuntu-studio.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

I will give it a try once more over the weekend.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Now testing the 3.13 kernel.
Now (12-jan 11:30) I have rebooted about 10-15 times, and the first two times it flipped, but now it seems to be stable at /dev/lcd1.
I will keep the kernel and keep rebooting during the week.
However, I still think it is strange that it is /dev/lcd1 and not /dev/lcd0.

Revision history for this message
Bengt Nilsson (bnilsson11) wrote :

Seems to be fixed.

I added the tag "kernel-fixed-upstream"

tags: added: kernel-fixed-upstream
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.