re: [Cooker] [Bug 6138] [gnome-session] Unable to start gnome preference daemon
>One more time again, I'm facing this "Gnome n'a pu démarrer le >démon de >préférence. Pour l'instant il sera désactivé et vous n'aurez pas >accès >aux thèmes, sons ... ) -> Gnome was unable to launch gnome >preferences >daemon. >So i don't have theme ( ugly default one for style, color, theme, >nautilus icons ), can't launch some applets ( windows list/systray, >desktop switcher ) because of an OAFIID cryptic error ... I've been seeing this alot lately and I believe it has something to do (in my case, may be similar) with dhcp. In my situation I've configured my machine using zeroconf with my adsl connection (machine doesn't seem to retain the given hostname and still uses the hostname provided by the ISP but that's another issue) which obtains its configuration via dhcp. Now what I have seen is that whenever my lease is renewed and I am issued another IP, anything that is currently running on the desktop is fine whereas anything that is attempted to be ran (any application trying to connect to the X server) fails, even when attempting to run the application as the root user. The typical error message is that the application cannot connect to the X server on the running display. I've even tried running xhost to string up a temporary fix so I can continue to use the machine. In relation to the above bug, I have found that restarting the X server does not resolve the issue, whereas a reboot will. Perhaps even a change of runlevels from 5 to 1 and back may fix it but I have not yet tried. If the X server is restarted, and you log in again, you will get the above messages consistantly. Perhaps there are others that have experienced this but just are not aware of it. :) Anyway, enough from me, I'll go back to lurking now. Deryk
[Cooker] [Bug 2851] [kernel] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-11-12 12:56 --- Suprisingly, that did the trick. I wasn't aware that nodes stuck around with devfs. From my previous experiences in the 2.3.x days writing the devfs patches for the nVidia driver, devfs created _everything_ on the fly as required. I guess this has changed. Sorry to carry this fault on longer than needed. All is working now. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] [Bug 2851] [kernel] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2003-10-25 12:57 --- This bug is still valid. [EMAIL PROTECTED] newlook]# rpm -q devfsd devfsd-1.3.25-32mdk [EMAIL PROTECTED] newlook]# uname -r 2.4.22-18mdk I changed commented out the DEVICE=/dev/lirc line in /etc/sysconfig/lircd and uncommented the DEVICE=/dev/lirc/0. I then restarted lircd with the following results: Stopping Linux Infrared Remote Control mouse daemon:[ OK ] Stopping Linux Infrared Remote Control daemon: [ OK ] Starting Linux Infrared Remote Control daemon: [ OK ] Starting Linux Infrared Remote Control mouse daemon:[ OK ] [EMAIL PROTECTED] newlook]# tail /var/log/syslog Oct 25 18:50:54 i216-191 kernel: lirc_dev: lirc_register_plugin:sample_rate: 10 Oct 25 18:50:54 i216-191 kernel: _devfs_append_entry(0): dir: "lirc" is not a directory Oct 25 18:50:54 i216-191 kernel: devfs_register(lirc/0): could not append to parent, err: -20 Oct 25 18:50:54 i216-191 lircd 0.6.6[12840]: lircd(any) ready Oct 25 18:50:54 i216-191 lircd: lircd startup succeeded Oct 25 18:50:54 i216-191 lircd 0.6.6[12840]: accepted new client on /tmp/.lircd Oct 25 18:50:54 i216-191 lircd 0.6.6[12840]: could not open /dev/lirc/0 Oct 25 18:50:54 i216-191 lircd 0.6.6[12840]: default_init(): Not a directory Oct 25 18:50:54 i216-191 lircd 0.6.6[12840]: caught signal Oct 25 18:50:54 i216-191 lircmd: lircmd startup succeeded [EMAIL PROTECTED] newlook]# ls /dev/lirc* -l crw-r--r--1 root root 61, 0 Oct 25 15:54 /dev/lirc srw-rw-rw-1 root root0 Oct 25 15:54 /dev/lircd= prw-r--r--1 root root0 Oct 25 15:54 /dev/lircm| --- Additional Comments From [EMAIL PROTECTED] 2003-11-12 11:25 --- [EMAIL PROTECTED] sysconfig]# rpm -q devfsd devfsd-1.3.25-32mdk [EMAIL PROTECTED] sysconfig]# uname -r 2.4.22-24mdk [EMAIL PROTECTED] sysconfig]# rpm -qa|grep lirc liblirc0-0.6.6-3mdk lirc-remotes-0.6.6-1mdk lirc-0.6.6-3mdk Nov 12 18:19:03 i115-184 kernel: lirc_dev: IR Remote Control driver registered, at major 61 Nov 12 18:19:03 i115-184 kernel: lirc_i2c: chip found @ 0x4b (PV951 IR) Nov 12 18:19:03 i115-184 kernel: tuner: type already set (1) Nov 12 18:19:03 i115-184 kernel: lirc_dev: lirc_register_plugin:sample_rate: 10 Nov 12 18:19:03 i115-184 kernel: _devfs_append_entry(0): dir: "lirc" is not a directory Nov 12 18:19:03 i115-184 kernel: devfs_register(lirc/0): could not append to parent, err: -20 Nov 12 18:19:03 i115-184 lircd 0.6.6[11488]: lircd(any) ready Nov 12 18:19:03 i115-184 lircd: lircd startup succeeded Nov 12 18:19:03 i115-184 lircd 0.6.6[11488]: accepted new client on /tmp/.lircd Nov 12 18:19:03 i115-184 lircd 0.6.6[11488]: could not open /dev/lirc/0 Nov 12 18:19:03 i115-184 lircd 0.6.6[11488]: default_init(): Not a directory Nov 12 18:19:03 i115-184 lircd 0.6.6[11488]: caught signal Nov 12 18:19:03 i115-184 lircmd: lircmd startup succeeded [EMAIL PROTECTED] sysconfig]# ls -l /dev/lirc* -l crw-r--r--1 root root 61, 0 Nov 12 15:26 /dev/lirc srw-rw-rw-1 root root0 Nov 12 15:26 /dev/lircd= prw-r--r--1 root root0 Nov 12 15:26 /dev/lircm| As previously, the fix is to change the device used in /etc/sysconfig/lircd to the non-devfs device. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: REOPENED creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] [Bug 1438] [xawtv] Starting xawtv from KDE desktop icon disables full screen.
http://qa.mandrakesoft.com/show_bug.cgi?id=1438 --- Additional Comments From [EMAIL PROTECTED] 2003-16-10 13:05 --- I can confirm this bug still exists in xawtv-3.88-4 and is reproduceable with the originally mentioned methods. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: I have bt878 TV card. By default, an icon for xawtv is placed on the desktop. If xawtv is launched from this icon, enabling fullscreen mode (by pressing the "f" key) will make xawtv use the whole screen, but the image is still a small box centered on the screen. However, if I start xawtv from the menu (multimedia->video->xawtv) and enter full screen mode, the picture uses the whole screen as expected. The desktop icon executes: "/usr/bin/XawTV -c /dev/v4l/video0" The menu item executes: "XawTV"
[Cooker] Konsole
Does anyone NOT have konsole installed with their 3.1.3 packages? It hasn't been available for me with the cooker packages (not 100% sure) since either a) the beginning of 3.1.3, or b) somewhere late in 3.1.2. I'm thinking that if it maybe perhaps be in a package that didn't make it to the cooker mirror I'm using. Regards, Deryk
[Cooker] [Bug 5117] [mandrake_theme] ln error
http://qa.mandrakesoft.com/show_bug.cgi?id=5117 --- Additional Comments From [EMAIL PROTECTED] 2003-06-09 06:54 --- Updated today, issue resolved with mandrake_theme-0.0.5-1mdk.noarch.rpm and mandrake_desk-9.2-6mdk. Please close. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: 54:mandrake_theme ## ln: `/usr/share/mdk/backgrounds//default.png': File exists ln: `/usr/share/mdk/backgrounds//root/default.png': File exists error: %post(mandrake_theme-0.0.4-1mdk) scriptlet failed, exit status 1 When upgrading from cooker via urpmi, the above error message is returned. The package is installed fine. Perhaps a test to see if the files in question already exist would correct the issue.
[Cooker] [Bug 5117] [mandrake_theme] New: ln error
http://qa.mandrakesoft.com/show_bug.cgi?id=5117 Product: mandrake_theme Component: packaging Summary: ln error Product: mandrake_theme Version: 0.0.4-1mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: packaging AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] 54:mandrake_theme ## ln: `/usr/share/mdk/backgrounds//default.png': File exists ln: `/usr/share/mdk/backgrounds//root/default.png': File exists error: %post(mandrake_theme-0.0.4-1mdk) scriptlet failed, exit status 1 When upgrading from cooker via urpmi, the above error message is returned. The package is installed fine. Perhaps a test to see if the files in question already exist would correct the issue. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Re: [Cooker] rc1 torrent
On Thu, 28 Aug 2003 10:27 am, Tom Brinkman wrote: > On Wednesday August 27 2003 07:45 pm, Brook Humphrey wrote: > > However I was only getting about 2k or 3k max > > and most the time it was sitting at 0. > > Yep, it sux. That's about the incomin I was gettin too Bittorrent is a tit for tat system. You only get what you put in. Combine that with the number of sources avaialable and you get your swarm. > > This was my first and last > > use of bittorrent. > >First time, tho I right'a way figured out how to get all 3 iso's > goin at once. Even a 3x, bittorrent SUX. After 5 hours, you've > hardly left the starting gate. Plus now I reckon they're not > resumable either. Further suckyiness You would be reckoning wrong. -- Regards, Deryk Robosson
[Cooker] [Bug 3032] [kernel] No AGP GART found on i810 video
http://qa.mandrakesoft.com/show_bug.cgi?id=3032 --- Additional Comments From [EMAIL PROTECTED] 2003-24-08 22:26 --- Add the following to your lilo.conf then rerun /sbin/lilo. append=" agp_try_unsupported=1" -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Installing Mandrake 9.1 RC1 on a "Saintsong Expresso" pocket PC (http://www.worldssmallestpc.com/ex1_specs.html). When testing the video configuration at any resolution the test fails with the error message "no AGP GART found". There was a message about the kernel but it got cut off. I can get it going using the Vesa driver. Once installed I can then select the i810 driver successfully with no error message.
[Cooker] [Bug 3964] [apache2-mod_php] Can't have both apache2-mod_php and php-cli
http://qa.mandrakesoft.com/show_bug.cgi?id=3964 --- Additional Comments From [EMAIL PROTECTED] 2003-26-07 09:12 --- This also happens with the packages mod_php-4.3.2-3mdk.i586.rpm and php-cli-4.3.2-8mdk.i586.rpm as well. You can have one installed, but not both. Installing one removes the other no matter the order installed and the user is never asked about this. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: ASSIGNED creation_date: description: I need to have both apache2-mod_php and php-cli (to launch scripts) == # urpmi apache2-mod_php Les paquetages suivants ont des signatures non valides: /mnt/nfs/dis/cooker/cooker/Mandrake/RPMS/apache2-mod_php-2.0.45_4.3.1-1mdk.i586.rpm Voulez-vous continuer l'installation ? (o/N) o installation de /mnt/nfs/dis/cooker/cooker/Mandrake/RPMS/apache2-mod_php-2.0.45_4.3.1-1mdk.i586.rpm Préparation... ## 1:apache2-mod_php## Shutting down httpd2: [ OK ] Checking configuration sanity for Apache 2.0: [ OK ] Starting httpd2: [ OK ] == So it installs fine, and : == # rpm -qa | grep -i php libphp_common430-430-13mdk php-ini-4.3.1-1mdk emacs-php-mode-102-5mdk apache2-mod_php-2.0.45_4.3.1-1mdk php-mysql-4.3.1-1mdk == It is even listed ! ;-) But, now I want to install php-cli : == # urpmi php-cli Les paquetages suivants ont des signatures non valides: /mnt/nfs/dis/cooker/cooker/Mandrake/RPMS/php-cli-4.3.1-13mdk.i586.rpm Voulez-vous continuer l'installation ? (o/N) o installation de /mnt/nfs/dis/cooker/cooker/Mandrake/RPMS/php-cli-4.3.1-13mdk.i586.rpm Préparation... ## 1:php-cli## Shutting down httpd2: [ OK ] Checking configuration sanity for Apache 2.0: [ OK ] Starting httpd2: [ OK ] == It installs fine, BUT : == # rpm -qa | grep -i php libphp_common430-430-13mdk php-ini-4.3.1-1mdk php-cli-4.3.1-13mdk emacs-php-mode-102-5mdk php-mysql-4.3.1-1mdk == It removed mod_php without telling me ! I really need both packages, and I'm sure other people do too. Thanks Aurélien
[Cooker] [Bug 4218] [kernel-2.4.21.3mdk] missing ntfs module
http://qa.mandrakesoft.com/show_bug.cgi?id=4218 --- Additional Comments From [EMAIL PROTECTED] 2003-21-07 20:17 --- Sorry but bugzilla must've been on some good drugs when I did query it first off for the summary field of 'ntfs' and it only returned one result (I did this three times to verify I just wasn't seeing things). -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: RESOLVED creation_date: description: The NTFS module is missing from this kernel removing the ability to read (and write for the daring) Win32 NTFS partitions.
[Cooker] [Bug 4218] [kernel-2.4.21.3mdk] New: missing ntfs module
http://qa.mandrakesoft.com/show_bug.cgi?id=4218 Product: kernel-2.4.21.3mdk Component: kernel-2.4.21.3mdk Summary: missing ntfs module Product: kernel-2.4.21.3mdk Version: 1-1mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel-2.4.21.3mdk AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The NTFS module is missing from this kernel removing the ability to read (and write for the daring) Win32 NTFS partitions. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 3537] [kernel] APCI fails on MSI 6547 system board
http://qa.mandrakesoft.com/show_bug.cgi?id=3537 --- Additional Comments From [EMAIL PROTECTED] 2003-19-07 16:45 --- This bug is no longer valid with kernel-2.4.21.3mdk-1-1mdk -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: Problem: Using the 2.4.21-0.13mdk kernel leads to apparent interrupt conflicts between devices installed on this system using the MSi 6547 system board. These symptoms exist when setting the BIOS to APIC revision 1.1 or 1.4. The first signs of trouble during boot are seen when the Advansys SCSI module attempts to probe the bus for devices followed later on during the boot process by the ethernet adapter, bt878 device, and USB subsystem. Solution: Disable APIC in the BIOS or pass "pci=noapci" via the bootloader config or the commandline. Information: lspci -vvv output can be obtained here: http://fragfest.homelinux.net:81/test/lspciout.txt dmesg output can be obtained here: http://fragfest.homelinux.net:81/test/dmesgout.txt This problem has existed and required the bootloader option since after kernel 2.4.18.8.2mdk-1-3mdk. I had just hoped things would get sorted out sooner or later as there had been quite a few bugs related to this subsystem.
[Cooker] [Bug 2851] [kernel] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 --- Additional Comments From [EMAIL PROTECTED] 2003-19-07 16:43 --- This bug is still valid with kernel-2.4.21.3mdk-1-1mdk -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] Loading order of modules and assignment of programs to video devices
Is it possible in 9.1 final to firmly specify that v4l devices that are on the system to use precise device names as you can with ethernet devices for example? I've tried setting aliases in modules.conf as I've done for ethernet cards in the past but my bt878 card and Logitech Quickcam Express are consistantly loading (or assigned during boot..not sure which) alternatively when booting (ie first boot, video0 would be tuner, video1 would be cam, then reverse every subsequent reboot). It's rather frustrating because you can't really use scripts for webcams as intended on your tuner card..it just doesn't have the same effect. :) -- Regards, Deryk Robosson Robosson Business Services 22 Flemington Street Albany, WA 6330 ABN: 56 728 377 499 Phone: +61 4 0842 9835 Email: [EMAIL PROTECTED]
[Cooker] [Bug 3537] [kernel] New: APCI fails on MSI 6547 system board
http://qa.mandrakesoft.com/show_bug.cgi?id=3537 Product: kernel Component: booting Summary: APCI fails on MSI 6547 system board Version: 2.4.21-0.13mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Problem: Using the 2.4.21-0.13mdk kernel leads to apparent interrupt conflicts between devices installed on this system using the MSi 6547 system board. These symptoms exist when setting the BIOS to APIC revision 1.1 or 1.4. The first signs of trouble during boot are seen when the Advansys SCSI module attempts to probe the bus for devices followed later on during the boot process by the ethernet adapter, bt878 device, and USB subsystem. Solution: Disable APIC in the BIOS or pass "pci=noapci" via the bootloader config or the commandline. Information: lspci -vvv output can be obtained here: http://fragfest.homelinux.net:81/test/lspciout.txt dmesg output can be obtained here: http://fragfest.homelinux.net:81/test/dmesgout.txt This problem has existed and required the bootloader option since after kernel 2.4.18.8.2mdk-1-3mdk. I had just hoped things would get sorted out sooner or later as there had been quite a few bugs related to this subsystem. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 2851] [kernel] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 --- Additional Comments From [EMAIL PROTECTED] 2003-03-26 04:06 --- Yes, this is still valid. Tested with the latest kernel release available on cooker as of 26.Mar.03 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] [Bug 2851] [kernel] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 15:29 --- [EMAIL PROTECTED] newlook]$ ls -l /dev/lirc crw-r--r--1 root root 61, 0 Mar 7 01:35 /dev/lirc [EMAIL PROTECTED] newlook]$ /sbin/lsmod Module Size Used byTainted: P sch_ingress 2784 1 (autoclean) cls_u32 5948 5 (autoclean) sch_sfq 4096 2 (autoclean) sch_cbq14784 1 (autoclean) sr_mod 16920 0 (autoclean) (unused) ide-cd 33856 0 (autoclean) cdrom 31648 0 (autoclean) [sr_mod ide-cd] floppy 55132 0 (autoclean) agpgart40896 3 (autoclean) NVdriver 1149824 10 (autoclean) ppp_async 9216 0 (unused) ppp_generic24060 0 [ppp_async] slhc6564 0 [ppp_generic] af_packet 14952 1 (autoclean) ipt_TOS 1592 1 (autoclean) iptable_mangle 2712 1 (autoclean) ipt_MASQUERADE 2104 2 (autoclean) iptable_nat21048 1 (autoclean) [ipt_MASQUERADE] ipt_state 1080 6 (autoclean) ip_conntrack 27264 2 (autoclean) [ipt_MASQUERADE iptable_nat ipt_state] ipt_multiport 1176 8 (autoclean) iptable_filter 2348 1 (autoclean) ip_tables 14648 9 [ipt_TOS iptable_mangle ipt_MASQUERADE iptable_nat ipt_state ipt_multiport iptable_filter] 8139too17160 1 (autoclean) mii 3832 0 (autoclean) [8139too] nls_cp437 5148 1 (autoclean) vfat 11820 1 (autoclean) fat37944 0 (autoclean) [vfat] mod_quickcam 41392 0 nls_iso8859-1 3516 2 (autoclean) ntfs 76812 1 (autoclean) tuner 11744 1 (autoclean) bttv 78496 2 (autoclean) i2c-algo-bit9064 1 (autoclean) [bttv] videodev7872 3 (autoclean) [mod_quickcam bttv] lirc_i2c4256 1 lirc_dev9112 1 [lirc_i2c] tvaudio15068 1 i2c-core 21192 0 [tuner bttv i2c-algo-bit lirc_i2c tvaudio] i810_audio 26248 0 soundcore 6276 0 [bttv i810_audio] ac97_codec 12488 0 [i810_audio] usb-ohci 20584 0 (unused) usbcore72992 1 [mod_quickcam usb-ohci] rtc 8060 0 (autoclean) reiserfs 175120 2 sd_mod 11548 0 (unused) advansys 85100 0 (unused) scsi_mod 91796 3 [sr_mod sd_mod advansys] --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: NEW creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] [Bug 2851] [lirc] lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 --- Additional Comments From [EMAIL PROTECTED] 2003-03-06 18:45 --- I'm using the default driver with the hardware driver lirc_i2c. This is a PV951 board which is bt878 based. Some more possibly relevant information from dmesg: lirc_dev: IR Remote Control driver registered, at major 61 lirc_i2c: probe 0x1a @ bt848 #0: no lirc_i2c: probe 0x18 @ bt848 #0: no lirc_i2c: probe 0x4b @ bt848 #0: yes lirc_i2c: chip found @ 0x4b (PV951 IR) lirc_dev (lirc_i2c[0]): poll thread started lirc_dev: plugin lirc_i2c registered at minor number = 0 lirc_i2c: probe 0x64 @ bt848 #0: no lirc_i2c: probe 0x30 @ bt848 #0: no --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is. --- Reminder: --- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release.
[Cooker] [Bug 2851] [lirc] New: lircd does not create /dev/lirc/0
http://qa.mandrakesoft.com/show_bug.cgi?id=2851 Product: lirc Component: lirc Summary: lircd does not create /dev/lirc/0 Version: 0.6.6-1mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] With the latest cooker update from 6th of March, lircd does not create /dev/lirc/0. I am taking a stab in the dark and assuming that because I run a system with devfs that the module is not creating the devfs entry. Changing /etc/sysconfig/lircd from: (this results in lircmd and crew not being able to communicate with the kernel space portion of this and hence all the problems that arrise from that) # The device node that communicates with the IR device. # with devfs enabled DEVICE=/dev/lirc/0 # without devfs #DEVICE=/dev/lirc To: # The device node that communicates with the IR device. # with devfs enabled #DEVICE=/dev/lirc/0 # without devfs DEVICE=/dev/lirc Fixes the problem and all other remaining mdk packages work as expected (tested with irw and xawtv). I've banged my head about this one for a month or so now since getting my new PV951 tuner card and just decided to have another dig at it. Hopefully this will get fixed for the final release. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Re: [Cooker] kde, gnome select problem
On Sat, 26 Oct 2002 02:50 am, Guy McArthur wrote: > This issue has been present for a long time, I would like to know what the > solution is. Select an input field in a GTK app (e.g. the image width > field in Gimp's resize dialog), and the KDE url handler pops up... very > annoying. I too have experienced the same issue. I have not however attempted to duplicate it. It appears to have been introduced with the more recent kde betas (i.e. just before 9.0 release). -- Regards, Deryk Robosson
Re: [Cooker] LIRC problem...
On Thu, 17 Oct 2002 02:14 am, Malte Starostik wrote: > On Wednesday 16 October 2002 19:41, Maxim Heijndijk wrote: > > I have a problem with LIRC on 9.0. For some reason it can never find a > > device file, devfs or no devfs. I have upgraded to 0.6.5-3mdk from > > Cooker. I've got the exact same problem. The lirc_i2c module loads (as well as lirc_dev) but no device ever shows up in /dev running devfs. I looked at the source included in the kernel-source rpm and it says it's registering the device but the compiled module does no such thing. -- Regards, Deryk Robosson Robosson Business Services 22 Flemington Street Albany, WA 6330 ABN: 56 728 377 499 Phone: +61 4 0842 9835 Email: [EMAIL PROTECTED]
[Cooker] BUG: panel configuration options missing
Problem: Previously, in order to resize, position, or alter a panel, one would right click on the panel and select configure. With the release of the kdebase-3.1-0.beta2.2mdk package this ability has diappeared. Quick Fix: It would seem that the file /usr/share/applnk/Settings/LookNFeel/panel.desktop is not complete as /usr/share/applnk/Settings/LookNFeel/panel_appearance.desktop is. 1) Using menudrake and selecting default KDE menus will restore the proper desktop item. 2) Calling "kcmshell panel" from a prompt will also yield the tools you are after. Solution: Unknown. I would speculate that the contents of the panel.desktop file is not up to par with what needs to be in it. I'll leave that up to those in the know. :) -- Regards, Deryk Robosson Robosson Business Services 22 Flemington Street Albany, WA 6330 ABN: 56 728 377 499 Phone: +61 4 0842 9835 Email: [EMAIL PROTECTED]
