[Cooker] [Bug 6161] [drakxtools] Drakconnect automagically installs adiusbadsl without confirmation
http://qa.mandrakesoft.com/show_bug.cgi?id=6161 --- Additional Comments From [EMAIL PROTECTED] 2003-18-10 11:10 --- Am Samstag, 18. Oktober 2003 00:16 schrieb [baud]: Yep, alltough using the name adsl instead the name of the connection/ISP is not so optimal. with your way you have to specify the options file for pppd. The way mandrake has choosen gives the possibility to use another approach, alltough i have seen, that it isn't really used. If you put options files in /etc/ppp/peers/ you can dial up the connection with pppd call . This can be done too by an unprivileged user(non-root) as well if you are giving the rights well. Further it gives the possibility of configuring different ISPs/modems/options and choosing the wished at the time you connect (using different peerscript names). Further you can organize the peerscripts in an directory structure under /etc/ppp/peers/ , f.i. using isdn/, modem/ and adsl/ and put some script in that dirs, you can later use 'pppd call isdn/isp1' or 'pppd call adsl/isp1' You can read in man pppd about peer scripts. I find it far better than options. and link that file to options or the like. HTH Steffen -- 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: With Tux and Sl33p3r we are working of the next release of eagle-usb, the driver formerly known as adiusbadsl for ADSL Modems Sagem Fast800, Comtrend CT350, AT-AR215 (based on Analog Eagle Chip) used in France, England, Poland, Spain... When launching Drakconnect, it keeps insisting on installing adiusbadsl-1.0.4 which overwrites the installation made from tar.gz and erases part of the configuration. Suppose there is an RPM v1.0.5 available, how would it replace the existing 1.0.4 version ? Would it be automagically installed ? From where ? As it would not be the original cdrom and there are chances the internet connection is down...) Could it be possible to deactivate this "functionality" not to be annoyed any more ? And avoid losing configuration... BTW, you are using a config file for pppd that is /etc/ppp/peers/adsl : is it standard ? We had chosen /etc/ppp/options.adsl and had not clearly understood your move in Mandrake 9.1, so that startadsl (provided by the same rpm) would not work without manual creation of /etc/ppp/options.adsl from /etc/ppp/options.adsl.template. Is it the same structure for all modem drivers (either dial-up or ADSL) and for other distributions ? Where is there a recommendation to put it this way rather than the other ? We would like to adapt our scripts to be fully compliant with Mandrake (and remain compatible with other distributions as well).
[Cooker] [Bug 4926] [drakxtools] drakconnect support for AVM fritz DSL ?
http://qa.mandrakesoft.com/show_bug.cgi?id=4926 --- Additional Comments From [EMAIL PROTECTED] 2003-17-09 18:23 --- Am Mittwoch, 17. September 2003 17:47 schrieb [dchaumette]: Its some days back i wrote it and i saw at that moment how similar other DSL connections are;) It are ISDN/DSL or just DSL Modems (Fritz DSL USB/Fritz DSL => ISDN/DSL, Fritz DSL SL => DSL). Sorry i should had that idea earlier. Steffen -- 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: >From what i have seen it would be relative simple to support fritz DSL from AVM. capiplugin is in isdn4kutils now, the only thing that would be needed is to edit the peerscript right. If there is time for this, i can provide a peerscript for it and the ldetect entries for it. Or something like that possible right now ? Steffen
[Cooker] [Bug 5500] [hotplug] Please add Zaurus 5500 support
http://qa.mandrakesoft.com/show_bug.cgi?id=5500 --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 01:30 --- Am Donnerstag, 11. September 2003 00:54 schrieb [jan.ciger]: Read the source luke ;). >From top of my head (You should verify what i will say, i only describe it basically, how i have it understood): The proper way is, to put a script that returns the mentioned line(s) in /usr/lib/hotplug/ dir. The name in the line that stands normally for the module, is the name of the script, that gets executed. This script have to be placed in /etc/hotplug/usb dir. The script gets called with one argument (add or remove) and this should do the needed/wished things then on plug or unplug. Very nice thing to play with, if you have a digikam or the like (load the pictures from the cam, convert them in a webgallery or the like) BTW: In the usb.useragent script is a typo as far as i have understood it. The name of the script must not have the name of a modul what needs eventually to be loaded. In the script was written, that it must have the name. It may be fixed in the meantime, but was very confusing. Steffen -- 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: Please add Zaurus 5500 support. It can be recognised in hotplug for use with qtopiadesktop. Just add it to hotplug map. The instructions have been sent by bluegreenone on Mandrakeclub : http://www.mandrakeclub.com/modules.php?op=modload&name=Splatt_Forum&file=viewtopic&topic=8225&forum=10&post_id=25952 1) Add this line to the end of /etc/hotplug/usb.handmap : Code: usbdnet 0x0003 0x04dd 0x8004 0x 0x 0x02 0x00 0x00 0xff 0x01 0x00 0x (if last line in file make sure to add a linefeed at the end) 2) Add a script called /etc/hotplug/usb/usbdnet (this forum malfunctions when i try to format this using CODE like I did above.) #! /bin/bash typeset -i num num=`ifconfig | grep usb0 | wc -l` if [ $num -eq 0 ] ; then ifconfig usb0 192.168.129.1 netmask 255.255.255.255 up route add -host 192.168.129.201 usb0 fi 3) Then setup shorewall to both allow the zaurus to talk to the PC and to have it do connection sharing so the zaurus can get to the Internet. Check out the two interface example of shorewall here. This assumes that you have one regular ethernet card and then the zaurus (usb0) as the second interface. 4) Set zaurus usbd networking to IP: 192.168.129.201 Subnet mask: 255.255.255.0 Gateway: 192.168.129.1 DNS: use your own
[Cooker] [Bug 5500] [hotplug] Please add Zaurus 5500 support
http://qa.mandrakesoft.com/show_bug.cgi?id=5500 --- Additional Comments From [EMAIL PROTECTED] 2003-11-09 01:20 --- Am Donnerstag, 11. September 2003 00:20 schrieb [tvignaud]: Hmmm. That doesn't set up the network on plug in, as far as i have understood all the usb stuff. All you might get this way is a loaded module, not an executed script. Alltough, with right config, an ifup usb0 should be enough. Maybe i just don't know usbdnet ?? ;) Steffen -- 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: Please add Zaurus 5500 support. It can be recognised in hotplug for use with qtopiadesktop. Just add it to hotplug map. The instructions have been sent by bluegreenone on Mandrakeclub : http://www.mandrakeclub.com/modules.php?op=modload&name=Splatt_Forum&file=viewtopic&topic=8225&forum=10&post_id=25952 1) Add this line to the end of /etc/hotplug/usb.handmap : Code: usbdnet 0x0003 0x04dd 0x8004 0x 0x 0x02 0x00 0x00 0xff 0x01 0x00 0x (if last line in file make sure to add a linefeed at the end) 2) Add a script called /etc/hotplug/usb/usbdnet (this forum malfunctions when i try to format this using CODE like I did above.) #! /bin/bash typeset -i num num=`ifconfig | grep usb0 | wc -l` if [ $num -eq 0 ] ; then ifconfig usb0 192.168.129.1 netmask 255.255.255.255 up route add -host 192.168.129.201 usb0 fi 3) Then setup shorewall to both allow the zaurus to talk to the PC and to have it do connection sharing so the zaurus can get to the Internet. Check out the two interface example of shorewall here. This assumes that you have one regular ethernet card and then the zaurus (usb0) as the second interface. 4) Set zaurus usbd networking to IP: 192.168.129.201 Subnet mask: 255.255.255.0 Gateway: 192.168.129.1 DNS: use your own
[Cooker] [Bug 5098] [kernel] RC1 - 2.4.22-1 - Webcam logitech quickcam stops the boot when plugged in
http://qa.mandrakesoft.com/show_bug.cgi?id=5098 --- Additional Comments From [EMAIL PROTECTED] 2003-01-09 12:52 --- Am Sonntag, 31. August 2003 16:17 schrieb [gsarsons]: That problem is well known, and there are other bugs that describes the same problem. I suppose that the camera is using pwc as driver ? Putting snd-usb-audio in hotplugs blacklist prevents at least the reboots, but doesn't solve the problem really. I think snd-usb-audio is the problem if i got the mails of Austin right. Greets Steffen -- 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 installed a clean copy of RC1 with the cam plugged into a USB port but when I go to boot the system doesn't make it out of resolving sysmbols. It just keeps rebooting. If I unplug the cam and try and boot/use the system everything works great. Logitech QuickCam Pro is the camera
[Cooker] [Bug 4926] [drakxtools] New: drakconnect support for AVM fritz DSL ?
http://qa.mandrakesoft.com/show_bug.cgi?id=4926 Product: drakxtools Component: DrakConnect Summary: drakconnect support for AVM fritz DSL ? Product: drakxtools Version: 9.2-3mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: DrakConnect AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] >From what i have seen it would be relative simple to support fritz DSL from AVM. capiplugin is in isdn4kutils now, the only thing that would be needed is to edit the peerscript right. If there is time for this, i can provide a peerscript for it and the ldetect entries for it. Or something like that possible right now ? Steffen -- 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 4435] [drakxtools] New: wrong handling of autologin
http://qa.mandrakesoft.com/show_bug.cgi?id=4435 Product: drakxtools Component: drakboot Summary: wrong handling of autologin Product: drakxtools Version: 9.2-0.23mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: drakboot AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] kdm, mdkkdm, and gdm all know the feature autologin. drakboot does not make use of this feature and works around it with the package autologin. Since with the package autologin no dm is started and those XDM_MANAGED is not set, the logout dialog for kde is the first time you log out the small one what you get if you start X from console. This is bug #375, #2002. If you then configure autologin in kde/kcontrol it gets even stranger. You log out the first time and you get logged in immediately again (since kdm/mdkkdm gets started the first time) this is bug 382. What should drakboot do about it ? It should not use the package autologin in case gdm or kdm is used. It should alter the config-files of kdm to enable this feature. This would save drakboot to be inconsistent to the settings in kcontrol too. This bug is in Mandrake since 9.0 or the like, it would be nice to have this fixed :) Steffen -- 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 3572] [drakxtools-newt] drakfirewall don't work
http://qa.mandrakesoft.com/show_bug.cgi?id=3572 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 22:53 --- The bug is still valid as of mandrake 9.2 beta1 ]# drakfirewall SCALAR(0x8ae3c2c) at /usr/lib/libDrakX/network/drakfirewall.pm line 110. One isdn-card, no network card. Steffen -- 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: I've setup my connection with drakconnect and all worked fine, but after that I tried to use drakfirewall to setup à basic firewall, but it failed. I choose the services I want to be availlable and it crashe saying (launched from a console, but crash either when started from the control center) : SCALAR(0x8ebf078) at /usr/lib/libDrakX/network/drakfirewall.pm line 110 I'm using an alcatel speedtouch usb modem, maybe it's related.
[Cooker] [Bug 375] [kdebase] With autologin enabled Reboot and Shutdown missing from logout
http://qa.mandrakesoft.com/show_bug.cgi?id=375 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 22:03 --- drakboot uses the package autolgin to provide this feature. autologin doesnt use the possibility of kdm/gdm as it seems. Greets Steffen -- 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 Autologin enabled, when I exit KDE I am only presented with an option to Logout. I have to log out before I can shut down the machine. It autologin is disabled, the Shutdown and Reboot options re-appear when I press the Exit button (bottom right of screen). I would really like to be able to shutdown the machine directly from KDE. Security level is at "High".
[Cooker] [Bug 3632] [autologin] Autologin should use ~/.wmrc rather than ~/.desktop
http://qa.mandrakesoft.com/show_bug.cgi?id=3632 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 22:46 --- If kdm/gdm is used the autologinfeature of the dm's should be used instead of autologin. It would then work as expected. -- 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: Description: Autologin uses ~/.desktop to record a user's prefered desktop whereas (as far as my tests can tell), GDM, KDM, MdkKDM all allow user's to switch between their prefered desktop (e.g. IceWM, GNOME, KDE) and record the last selection in ~/.wmrc. The format of the files is different so a simple symlink is not enough. Steps to reproduce: 1. Note which desktop autologin logs you in on. 2. Set your login manager to KDM/GDM 3. Log in using another desktop other than the autologin selected one. 4. GDM/KDM remembers the previous desktop. 5. Log out 6. run /etc/init.d/dm restart as root Expected: To be logged in with the newly selected desktop Result: Logged in with the same desktop regardless of the selection in GDM/KDM. Mandrake 9.1 i586 (I hope this is new enough to still count as cooker...)
[Cooker] [Bug 2002] [autologin] Autologin doesn't login to kde right.
http://qa.mandrakesoft.com/show_bug.cgi?id=2002 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 22:39 --- Ok some other reboots later and a bit playing around, I think the guilty here is drakboot. I have tried if mdkkdm has the kdm autologin feature. It works ! If autologin in kcontrol is enabled and autologin in drakboot is enabled one can easily reproduce bug 382. You log out the first time, kdm/mdkkdm gets started the first time => autologin logs in => logout again and it finally works. If nobody minds I will file a bug against drakboot now. drakboot should change the kdm/gdm config in order to get autologin enabled. Steffen -- 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: When I use drakboot to setup the autologin process to autologin into kde it logs me in as if i started kde from a console with startx. The problem with this is that the logout button only allows the user to logout, not to shutdown and or reboot the machine. Now.. If i set drakeboot not to autologin and i configure mdkkdm and or normal kdm to automatically login the user i want to login, the logout button provides all the options to the user when it is pressed to either logout, reboot , or shutdown.
[Cooker] [Bug 2002] [autologin] Autologin doesn't login to kde right.
http://qa.mandrakesoft.com/show_bug.cgi?id=2002 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 21:52 --- Yep using an autologin feature is of the dm is the only way to make it work. What happens if it is done w/O the dm we can see here. With the XDM_MANAGED set, the wished KDE Logout appears. Since the DM doesn't really run the logout dialog can't connect to it and thus the logout dialog is unfunctional. To have autologin enabled we need to let the dm do that. If kdm and gdm can do that and mdkkdm can't do it, this bug has to be filed against mdkkdm. Steffen -- 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: When I use drakboot to setup the autologin process to autologin into kde it logs me in as if i started kde from a console with startx. The problem with this is that the logout button only allows the user to logout, not to shutdown and or reboot the machine. Now.. If i set drakeboot not to autologin and i configure mdkkdm and or normal kdm to automatically login the user i want to login, the logout button provides all the options to the user when it is pressed to either logout, reboot , or shutdown.
[Cooker] [Bug 1628] [KDE] PATH for autologin not login shell PATH
http://qa.mandrakesoft.com/show_bug.cgi?id=1628 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 21:24 --- Nope. I have only the normal path then. The kdm path I get only with standard-autologin. And the solution in #2002 is at the moment just the half truth. More there. Steffen -- 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: I expect that the PATH for a non-root user should be the same whether she gets to the desktop via autologin or via a login window. This appears not to be the case. Path upon autologin to desktop: /usr/X11R6/bin:/usr/local/bin:/bin:/usr/bin Path after loging out of desktop and back in: /usr//bin:/bin:/usr/bin::/usr/local/bin:/usr/X11R6/bin:/usr/games:/home/craig/bin: Path after logging into a pseudoterminal: /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/home/craig/bin: Note the peculiar /usr//bin: entry in the second situation above.
[Cooker] [Bug 4413] [ldetect-lst] New: 2 wrong entries in ldetect-lst regarding vendor Eicon
http://qa.mandrakesoft.com/show_bug.cgi?id=4413 Product: ldetect-lst Component: ldetect-lst Summary: 2 wrong entries in ldetect-lst regarding vendor Eicon Product: ldetect-lst Version: 0.1.7-16mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: ldetect-lst AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] See http://archives.mandrakelinux.com/cooker/2003-07/msg02633.php for further description of the problem. Steffen -- 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 1628] [KDE] PATH for autologin not login shell PATH
http://qa.mandrakesoft.com/show_bug.cgi?id=1628 [EMAIL PROTECTED] changed: What|Removed |Added BugsThisDependsOn||2002 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 19:27 --- Bug is valid too for Mandrake 9.1, will prove for 9.2b1, but w/o prove I guess it is valid too. If XDM_MANAGED is set the path is sane. With current autologin the above strange path is set. grep doesn't find /usr//bin so it seems to be a buggy script somewhere. Haven't found the reason with some research now. Steffen -- 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: I expect that the PATH for a non-root user should be the same whether she gets to the desktop via autologin or via a login window. This appears not to be the case. Path upon autologin to desktop: /usr/X11R6/bin:/usr/local/bin:/bin:/usr/bin Path after loging out of desktop and back in: /usr//bin:/bin:/usr/bin::/usr/local/bin:/usr/X11R6/bin:/usr/games:/home/craig/bin: Path after logging into a pseudoterminal: /usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/usr/games:/home/craig/bin: Note the peculiar /usr//bin: entry in the second situation above.
[Cooker] [Bug 375] [kdebase] With autologin enabled Reboot and Shutdown missing from logout
http://qa.mandrakesoft.com/show_bug.cgi?id=375 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 18:35 --- This isn't a kde-bug and kwin does not need to be patched. The problem here is autologin. XDM_MANAGED needs to be set otherwise kde thinks it is started from console . I have added export XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched to startx.autologin and the logout is now allways the right one. Steffen -- 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 Autologin enabled, when I exit KDE I am only presented with an option to Logout. I have to log out before I can shut down the machine. It autologin is disabled, the Shutdown and Reboot options re-appear when I press the Exit button (bottom right of screen). I would really like to be able to shutdown the machine directly from KDE. Security level is at "High".
[Cooker] [Bug 2002] [autologin] Autologin doesn't login to kde right.
http://qa.mandrakesoft.com/show_bug.cgi?id=2002 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 18:49 --- The environment variable XDM_MANAGED needs to be set, so the right logout window appears, otherwise kde assumes to be started via startx from console and those showing only the cutted down logout window. Adding export XDM_MANAGED=/var/run/xdmctl/xdmctl-:0,maysd,mayfn,sched to startx.autologin fixes the problem. -- 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: When I use drakboot to setup the autologin process to autologin into kde it logs me in as if i started kde from a console with startx. The problem with this is that the logout button only allows the user to logout, not to shutdown and or reboot the machine. Now.. If i set drakeboot not to autologin and i configure mdkkdm and or normal kdm to automatically login the user i want to login, the logout button provides all the options to the user when it is pressed to either logout, reboot , or shutdown.
[Cooker] [Bug 382] [kdebase] Logout not handled correctly when Auto-Login enabled
http://qa.mandrakesoft.com/show_bug.cgi?id=382 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 18:38 --- This is the same bug as 375 just a bit strange described. Solution is provided in bug 375. -- 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: 1. Auto-Login and Truly Automatic Login is enabled. 2. PC Boots, and default user is auto-logged in. 3. User settings specify that on Logout, the user should be given the option to Reboot or Shutdown the system. 4. When User selects Logout from the K-Menu, only the 'Save settings' checkbox is presented. The user is not allowed to shutdown or reboot. 5. User presses the 'Logout' button. 6. Window goes blank, but then auto-login sequence starts again, and default user it auto-logged in. 7. The user once again selects 'Logout' from the K-menu. THis time the Shutdown and Reboot options are visible. 8. User selects Shutdown, and presses the Logout button. 9. Machine is shutdown correctly. So it seems that the first logout after bootup is not being handled correctly.
[Cooker] [Bug 4355] [initscripts] localized umlauts shows up as ? on startup...
http://qa.mandrakesoft.com/show_bug.cgi?id=4355 --- Additional Comments From [EMAIL PROTECTED] 2003-29-07 17:45 --- With the patch it works for me too. All umlauts are now displayed correctly. Steffen -- 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: Upon bootup when the initscripts output scrolls by, all "special characters" a.k.a umlauts (for example å, ä, ö, ...) shows up as ? This bug apeared somewhere after MDK 9.1 Release... And it is present in 9.2beta1 and current Cooker... This is on a Finnish locale, but I have seen others complain about it on th ML... my settings: [EMAIL PROTECTED] root]# cat /etc/sysconfig/i18n SYSFONTACM=iso15 LC_TELEPHONE=fi_FI LC_CTYPE=fi_FI LANGUAGE=fi_FI:fi LC_MONETARY=fi_FI LC_ADDRESS=fi_FI LC_COLLATE=fi_FI LC_NAME=fi_FI LC_PAPER=fi_FI LC_NUMERIC=fi_FI SYSFONT=lat0-16 LC_TIME=fi_FI LC_MEASUREMENT=fi_FI LANG=fi_FI LC_MESSAGES=fi_FI LC_IDENTIFICATION=fi_FI
[Cooker] [Bug 4126] [drakxtools] net_monitor shows error message when viewing logs on mandrake 9.1
http://qa.mandrakesoft.com/show_bug.cgi?id=4126 --- Additional Comments From [EMAIL PROTECTED] 2003-27-07 20:10 --- Same here, but I thought it could be ISDN related. If it is called with --testing it is allways online and hangs if going offline is called. After a while it says that it can't go offline (that is normal, since I'm offline) . Can confirm that logdrake is unfunctional. Steffen -- 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: Using drakxtools-9.1-31.3mdk. Start net_monitor from a terminal. Click on the logs button. Nothing happens except for an error message that appears on the terminal: Can't call method "freeze_updates" on an undefined value at /usr/sbin/logdrake line 220.
[Cooker] [Bug 4329] [rpm-build] New: files in the package are owned by user rpm, which does not exist
http://qa.mandrakesoft.com/show_bug.cgi?id=4329 Product: rpm-build Component: packaging Summary: files in the package are owned by user rpm, which does not exist Product: rpm-build Version: 4.2-9mdk Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: packaging AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] While installing the package rpm-build I got a waring that files should be owned by user rpm. The user does not exist and so the ownership was transferred to user root. Either a user rpm should be created per default or the package should be changed. Since the installation of rpm-build has shown the error, I fill the bug in here. Greets Steffen -- 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 4328] [Installation] New: orphan file - directory 0755/ and file halt in root (/) (9.2beta1)
http://qa.mandrakesoft.com/show_bug.cgi?id=4328 Product: Installation Component: Installation Summary: orphan file - directory 0755/ and file halt in root (/) (9.2beta1) Product: Installation Version: 1.810 Platform: Other OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: Installation AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] After Installation of 9.2 beta 1 I have a dir called 0755. From the creation date it is created by the installer, So I guess the installer has a typo somewhere. Further there is a file called "halt" which is empty. If this file is needed bey the initscript it should go to /tmp/ or the like, it should not mess up / Steffen -- 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 4202] [kernel] New: /dev/isdninfo unreliable - can crash apps (from 8.2 to cooker)
http://qa.mandrakesoft.com/show_bug.cgi?id=4202 Product: kernel Component: kernel Summary: /dev/isdninfo unreliable - can crash apps (from 8.2 to cooker) Product: kernel Version: 2.4.21-pre2.1mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Hi ! In http://archives.mandrakelinux.com/cooker/2003-01/msg00073.php I have reported a strange problem. I have finally found out what causes the problem. Other then I have written there, this bug is triggered too with channelbundling and some providers. Ok. Whats causing the problem: /dev/isdninfo only produces output if the output can be wriiten all at once. If the buffer for reading is to small nothing is written. A lot of applications are using a buffer of 1024 bytes (I guess standard with fopen() calls). Mandrake Kernel defines in isdn.h a maximum of 32 devices and so 64 channels. This leads very fast to exceed this 1024 byte limit as the output of /dev/isdninfois dependent on the ISDNMAXCHAN set in isdn.h . An strace shows that only the difference of HiSax vs. capidrv-1 leads to exceed the limit the current setup. --- write(1, "idmap:\tcapidrv-1 capidrv-1 - - -"..., 1024idmap: capidrv-1 capidrv-1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - chmap: 0 1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 drmap: 0 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 usage: 131 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 flags: 1 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? phone: 0191011 ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? ??? -- 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 3572] [drakxtools-newt] drakfirewall don't work
http://qa.mandrakesoft.com/show_bug.cgi?id=3572 --- Additional Comments From [EMAIL PROTECTED] 2003-04-12 21:10 --- Am Samstag, 12. April 2003 20:54 schrieb patrice.ferlet: No you got me wrong. If you have the drakfirewall crash => insert a network card in your system and the crash is gone. If you can't reach the internet after drakfirewall runs w/o error => mostly the interface is set wrong. if you have ppp0 as interface set net ppp0 - After that restart shorewall and be sure to not start again drakfirewall as it sets it back again to eth0. Thats how I experienced it here. I can't tell more then my experience here ;) Greets Steffen --- 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: I've setup my connection with drakconnect and all worked fine, but after that I tried to use drakfirewall to setup à basic firewall, but it failed. I choose the services I want to be availlable and it crashe saying (launched from a console, but crash either when started from the control center) : SCALAR(0x8ebf078) at /usr/lib/libDrakX/network/drakfirewall.pm line 110 I'm using an alcatel speedtouch usb modem, maybe it's related.
[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-04-12 20:30 --- Am Samstag, 12. April 2003 19:46 schrieb arvidjaar: Yes lirc_serial is full functional (in use here) --- 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 1449] [Bugzilla] Page too heavy, and products list is reloaded each time by the browser.
http://qa.mandrakesoft.com/show_bug.cgi?id=1449 --- Additional Comments From [EMAIL PROTECTED] 2003-04-04 00:24 --- Just for your interest I stopped the time how long the bug page loads. ISDN 64k: 55 sec and that for every page with the product list on it. Lets say you want to search if a related bug was reported, you may look on 10 bugs and have some intermediate pages with a pruct list on it results in 20-30 min waiting. I give up for today on bugzilla --- 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: The weight of the mandrakesoft bugzilla page is very high : ~= 280ko, and it is very slow from a 56k or 64k connection. This is due to the generated list of products, see below : (...) 3ddesktop 4stAttack a2ps a2ps-devel a2ps-static-devel a52dec aalib-progs abcde abiword abiword-plugin-abigimp abiword-plugin-babelfish (...) - There should be a way to generate this list differently, so that the browser can put it into the cache. For example, the "select" list could be stored in a different URL, so that there would be no need for the borwser to reload it each time.
[Cooker] [Bug 1449] [Bugzilla] Page too heavy, and products list is reloaded each time by the browser.
http://qa.mandrakesoft.com/show_bug.cgi?id=1449 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Additional Comments From [EMAIL PROTECTED] 2003-04-04 00:17 --- *** This bug has been confirmed by popular vote. *** --- 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: The weight of the mandrakesoft bugzilla page is very high : ~= 280ko, and it is very slow from a 56k or 64k connection. This is due to the generated list of products, see below : (...) 3ddesktop 4stAttack a2ps a2ps-devel a2ps-static-devel a52dec aalib-progs abcde abiword abiword-plugin-abigimp abiword-plugin-babelfish (...) - There should be a way to generate this list differently, so that the browser can put it into the cache. For example, the "select" list could be stored in a different URL, so that there would be no need for the borwser to reload it each time.
[Cooker] [Bug 430] [drakxtools] Security problem w/ ifcfg-* files being world readable
http://qa.mandrakesoft.com/show_bug.cgi?id=430 --- Additional Comments From [EMAIL PROTECTED] 2003-04-04 00:09 --- is still valid as reported, but i think this is a minor issue . At least r-x for other could be taken out. --- 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: In /etc/sysconfig/network-scripts, the drakconnect_conf* files are correctly set to permissions 600. But currently, ifcfg-* files are 775. Since secure information may be contained in these files (WLAN keys for instance), they must no be world read/executable.
[Cooker] [Bug 1847] [drakxtools] isdn startup at boot after configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1847 [EMAIL PROTECTED] changed: What|Removed |Added Version|9.1-21mdk |9.1-26mdk --- Additional Comments From [EMAIL PROTECTED] 2003-04-03 23:31 --- Still valid in final. ONBOOT of network device ippp0 ist set to no and I get not asked like on normal NICs --- 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: After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands.
[Cooker] [Bug 2027] [isdn4k-utils] No Bugreport/collections of thoughts on this package and related.
http://qa.mandrakesoft.com/show_bug.cgi?id=2027 [EMAIL PROTECTED] changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2003-04-03 23:18 --- I thinks this is a misuse of bugzilla and will anyway be ignored ;-) closing --- 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: I just want to collect some thoughts about this package in here. I have allready posted some of them maybe. Update this package? There is a 3.2pre1 out since some time. Current in mandrake is 3.1pre10. I don't know if the isdn4linux folks never release stable releases. Split up the package? Debian did split this package in several smaller packages. I guess this should be done here to. As suggestion could be used the debian packages. Some of my thoughts after reading the debian package site: - isdn4k- core utils - isdn4k- capi utils/active-cards aka capi4k-utils - vbox2 Suggestions (there are several solutions/extensions vor vbox) - - vbox2www - vbox3 - vbox3www - raccess4vbox - vbox-cm () (for people who understand german: www.malte-wetz.de) - isdn4k- xtools - isdn4k- eurofile . Currently the package is 5MB big and some things are missing. divertctrl is missing . Alltough the kerneldrivers are compiled with divert-support (divert-dsss1.o), the isdn4k-utils are not, so the divertctrl tool is missing. This tools can do things like call-deflection. call forwarding and so on with a rule set very similar to ipchains. In short a "nice to have" it woud be nice to have isdn-compression. Some ISPs provides different compression methods for isdn-connections. Due the compression loading of a lot of uncompressed data (like big text-sites) can be a lot faster than normal (for text I would say 5 times faster). As far as I can see isdn_ccp and lzs compression is missing. I would not mind to discover this further if there is interest. capi4hylafax is missing. capi4hylax is an extension to hylafax to use hylafax with fax-capable isdn-cards that have a capi interface. (mainly all cards from AVM with their propritary driver, all active AVM Cards, Eicon Diva should have capi-drivers too, I don't know about auerswald). pppdcapiplugin is missing. this is part of the actual isdn4k utils. it makes possible to use pppd in order with isdn-cards with capi-driver. There seems to be a problem with the driver capidrv.o and devfs. Alltough the /lib/dev-state/isdn/isdninfo is working (as I understand a copy of /dev/isdn/isdninfo ??) the /dev/isdn/isdninfo worked not in the last releases. I don't know about the current, since I could not test it yet. Think thats all for now I could think of. I posted something similar to cooker allready but wanted to save this here.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 21:50 --- On Thursday 13 March 2003 17:22, qa wrote: As it is mainly isdn4net related I guess it is still valid. --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 3233] [isdn4net] hisax_fcpcipnp unknown in isdn4net
http://qa.mandrakesoft.com/show_bug.cgi?id=3233 --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 19:18 --- Created an attachment (id=347) --> (http://qa.mandrakesoft.com/attachment.cgi?id=347&action=view) fixed source rpm As this package is only a collection of shellscripts, i made a fixed src.rpm ready. The resulting rpm is tested on two machines --- 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: In current isdn4net hisax_fcpcipnp is unknown. Because of that isdn doesn't start if a fritz pci v2 is recognized and right configured. I provided a patch in related bug 3142. drakconnect.isdn_internal: --- protocol=2 speed=64 Kb/s id=e00 dialing_mode=auto description=A1 ISDN Adapter [Fritz] login=hansenet passwd=direkt card_type=pci huptimeout=180 phone_out=0192312 driver=hisax_fcpcipnp vendor=1244 --- The driver is there and isdn starts if the patch is applied.
[Cooker] [Bug 3233] [isdn4net] New: hisax_fcpcipnp unknown in isdn4net
http://qa.mandrakesoft.com/show_bug.cgi?id=3233 Product: isdn4net Component: program Summary: hisax_fcpcipnp unknown in isdn4net Version: 1.4.5-5mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] In current isdn4net hisax_fcpcipnp is unknown. Because of that isdn doesn't start if a fritz pci v2 is recognized and right configured. I provided a patch in related bug 3142. drakconnect.isdn_internal: --- protocol=2 speed=64 Kb/s id=e00 dialing_mode=auto description=A1 ISDN Adapter [Fritz] login=hansenet passwd=direkt card_type=pci huptimeout=180 phone_out=0192312 driver=hisax_fcpcipnp vendor=1244 --- The driver is there and isdn starts if the patch is applied. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 00:09 --- (From update of attachment 329) >--- isdn4linux.old 2003-03-11 15:53:22.0 +0100 >+++ isdn4linux 2003-03-11 15:59:45.0 +0100 >@@ -104,6 +104,15 @@ > fi > ;; > >+ 'hisax_fcpcipnp') >+ >+echo "Loading driver hisax_fcpcipnp" >+/sbin/modprobe -v "hisax_fcpcipnp protocol=$I4L_PROTOCOL" >>/dev/null >+if test $? -ne 0; then >+cleanup >+fi >+ ;; > >+ > 'hisax') > > CARDTYPE=`echo $I4L_TYPE | tr -d ' '` --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 16:26 --- Don't know there this should be fixed. Look for the other comments --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 16:21 --- Created an attachment (id=329) --> (http://qa.mandrakesoft.com/attachment.cgi?id=329&action=view) patch for isdn4net 1.4.5-6 for file /etc/rc.d/init.d/isdn4linux I add it here in case it should be fixed in isdn4net instead of drakxtools. --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 16:09 --- OK I tracked this bug down together with erik. He has a fritz pci v2. This one needs the driver hisax_fcpcipnp. This driver is not known by isdn4net and isdn can not be used because of this. Solution 1: Force isdn-light if Fritz pci v2 is detected Solution 2: Add hisax_fcpcipnp to the known cards in isdn4net Note: isdn4net-1.4.5-5 is still in Cooker. It was updated to 1.4.5-6 (fixed doc bug) back in february but -6 is not in cooker yet ! --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 3142] [drakxtools] isdn configuration problems
http://qa.mandrakesoft.com/show_bug.cgi?id=3142 --- Additional Comments From [EMAIL PROTECTED] 2003-03-11 01:40 --- On Tuesday 11 March 2003 00:47, info wrote: You mean your card was not detected ? Or is there no way at all to configure isdn ? --- 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: There are problems with the internet connection over isdn using drakconnect (mandrake 9.1 rc2). There is no possiblity to choose the 'way' (lan or isdn) to connect with the internet in the configuration wizard like in mandrake 9.0. In addition to that no device 'ippp0' is created so that connection by manual configuration with 'isdn setup' is also not possible. So connecting with the internet using drakconnect (over isdn with isdn4linux) is simply impossible in the curent version.
[Cooker] [Bug 2932] [Hardware] Network/Internet Connection issue..
http://qa.mandrakesoft.com/show_bug.cgi?id=2932 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 22:00 --- On Friday 07 March 2003 21:33, dwilliams wrote: Where is the bugreport ? menudrake does not make any internet connections. Does it establish the connection at all ? In which situation does it fail ? How exactly are you trying to connect to the internet ? What says route -n , can you ping IPs, can you ping hostnames, output of ifconfig ? Have you running a firewall, have you configured the firewall ? Are there any related messages in /var/log/messages ? Please post some informations otherwise the bug won't be fixed. Greets Steffen --- 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 a Kingston KNE120TX network card that RC2 picks up just fine, but when i go through menudrake to start an internet connection, i always get minimal data transfer and then it fails, every time. So i have no internet connection whatsoever. The network/internet worked great for me in RC1. I have dsl with a linksys router..
[Cooker] [Bug 2648] [shorewall] shorewall disable any ppp connectivity
http://qa.mandrakesoft.com/show_bug.cgi?id=2648 --- Additional Comments From [EMAIL PROTECTED] 2003-03-07 20:41 --- A pitty I can't test Cooker. But as I see drakfw does not know anything about the ppp0 if this one is established by kppp or similar. Some Questions: Is this also true if the modem is configured with drakconnect ? (If not I would say this would be a valid solution) Could ppp0 and similar be added so it can be choosen if not automatically detected ? Could someone confirm if it is so, that drakfw does not work with dialup ? If it does not work generally with dialup, what is the reason ? --- 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: After enabling shorewall, (and enabling all the services proposeb by default) i can use ethernet connection, but ppp connexion stop to work. ppp atblishies the link, but that's all.
[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 17:30 --- On Thursday 06 March 2003 16:36, fcrozat wrote: Shouldn't lirc_serial usually creating /dev/lirc/serial and not /dev/lirc/0 ? Could someone please doublecheck this ? --- 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 1847] [drakxtools] isdn startup at boot after configuration
http://qa.mandrakesoft.com/show_bug.cgi?id=1847 --- Additional Comments From [EMAIL PROTECTED] 2003-03-05 20:50 --- On Wednesday 05 March 2003 19:53, qa wrote: Still valid, the device should be set to ONBOOT="yes" after configuration or it should be asked like it is done for network cards. --- 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: After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands.
[Cooker] [Bug 636] [isdn4k-utils] example-files stated in the documation are missing
http://qa.mandrakesoft.com/show_bug.cgi?id=636 --- Additional Comments From [EMAIL PROTECTED] 2003-02-26 22:17 --- The current version of isdn4k-utils is some years old now too, I have asked on the mailing list and according to Karsten Keil the latest release is from a few days ago ( v3.2p3 in the cvs (tag v3_2p3).) In isdn4k-utils are only bugfixes, so it maybe can be updated against the freeze ?? --- 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: If I want configure vbox the examples as stated in the documentation aren't anywhere on my system. The are needed for having some initial files, so own files can be recorded. Will add a tar.gz I got from another Distri. Please add the missing files. Greets Steffen
[Cooker] [Bug 2278] [drakxtools] scsi emulation not enabled for all CD drives
https://qa.mandrakesoft.com/show_bug.cgi?id=2278 --- Additional Comments From [EMAIL PROTECTED] 2003-02-24 00:02 --- On Sunday 23 February 2003 23:40, aw280 wrote: Hmm you could say that it should not be default, but since all Linux-burnapps have this problem I would not consider this as app-bug. That is stupid. Maybe a little nifty button in MCC would do the trick for people, that would like to have it or asking on installation. This is a serious problem for many people, since they have to relink all the links for cdrom afterwards and that is not really easy to understand. So maybe not a bugreport, but a good suggestion --- 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: Using mdk-9.1rc1. Currently, only ide CD-RW drives are scsi-emulated. If a system has two CD drives (1 CD-RW and 1 CD), the CD drive is not scsi-emulated. This prevents cdrecord from detecting the CD drive and as a result any CD-burning program (xcdroast, koncd) that uses cdrecord cannot do CD-to-CD copy. For a desktop oriented distribution, enabling this feature is very important. So, if scsi-emulation is enabled for one CD-RW-drive, it should be enabled for all CD drives on the system.
[Cooker] [Bug 1659] [initscripts] /etc/ppp/ip-down not checking before editing /etc/resolv.conf
https://qa.mandrakesoft.com/show_bug.cgi?id=1659 --- Additional Comments From [EMAIL PROTECTED] 2003-02-21 20:30 --- I would say this is not really a problem. You can add dns-server above the described line in resolv.conf and the will stay in the file, only the one or two dns of the provider will be added. --- 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: /etc/ppp/ip-down seems to be the only script that does not first check either $PEERDNS or $RESOLV_MODS before editing /etc/resolv.conf. It probably should.
[Cooker] [Bug 2027] [isdn4k-utils] New: No Bugreport/collections of thoughts on this package and related.
https://qa.mandrakesoft.com/show_bug.cgi?id=2027 Product: isdn4k-utils Component: isdn4k-utils Summary: No Bugreport/collections of thoughts on this package and related. Version: 3.1-1.pre1.10mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I just want to collect some thoughts about this package in here. I have allready posted some of them maybe. Update this package? There is a 3.2pre1 out since some time. Current in mandrake is 3.1pre10. I don't know if the isdn4linux folks never release stable releases. Split up the package? Debian did split this package in several smaller packages. I guess this should be done here to. As suggestion could be used the debian packages. Some of my thoughts after reading the debian package site: - isdn4k- core utils - isdn4k- capi utils/active-cards aka capi4k-utils - vbox2 Suggestions (there are several solutions/extensions vor vbox) - - vbox2www - vbox3 - vbox3www - raccess4vbox - vbox-cm () (for people who understand german: www.malte-wetz.de) - isdn4k- xtools - isdn4k- eurofile . Currently the package is 5MB big and some things are missing. divertctrl is missing . Alltough the kerneldrivers are compiled with divert-support (divert-dsss1.o), the isdn4k-utils are not, so the divertctrl tool is missing. This tools can do things like call-deflection. call forwarding and so on with a rule set very similar to ipchains. In short a "nice to have" it woud be nice to have isdn-compression. Some ISPs provides different compression methods for isdn-connections. Due the compression loading of a lot of uncompressed data (like big text-sites) can be a lot faster than normal (for text I would say 5 times faster). As far as I can see isdn_ccp and lzs compression is missing. I would not mind to discover this further if there is interest. capi4hylafax is missing. capi4hylax is an extension to hylafax to use hylafax with fax-capable isdn-cards that have a capi interface. (mainly all cards from AVM with their propritary driver, all active AVM Cards, Eicon Diva should have capi-drivers too, I don't know about auerswald). pppdcapiplugin is missing. this is part of the actual isdn4k utils. it makes possible to use pppd in order with isdn-cards with capi-driver. There seems to be a problem with the driver capidrv.o and devfs. Alltough the /lib/dev-state/isdn/isdninfo is working (as I understand a copy of /dev/isdn/isdninfo ??) the /dev/isdn/isdninfo worked not in the last releases. I don't know about the current, since I could not test it yet. Think thats all for now I could think of. I posted something similar to cooker allready but wanted to save this here. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 1847] [drakxtools] New: isdn startup at boot after configuration
https://qa.mandrakesoft.com/show_bug.cgi?id=1847 Product: drakxtools Component: DrakConnect Summary: isdn startup at boot after configuration Version: 9.1-1mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] After the configuration of ISDN is done, it should be started at bootup. Currently it is handled like a pppd-connection. But this handling is wrong. /etc/sysconfig/networkscripts/ifcfg-ippp0 should be switched to ONBOOT="yes" to ensure the ippp0 is up after boot. Note: this do not cause ISDN to dialin. Only the Pseudo-NIC is up. After a isdnctrl dial ippp0 the dialout is started. So it is safe to handle ippp0 as any other NIC and ask to start it at boot time. This issue leads to confusion since the beginnig of isdn-support in Mandrake back in 7.0. Further it would be nice to be able to configure several connections(for dialing different ISPs at different times), asking if ibod (automatic channelbundling) should be used or not and so on. But I guess this would be a TODO for 9.2 or so. Further if ISDN is configured and kisdndial is in the distro it should be installed/started for easier dial out. This would need to ensure the correct rights on devices and needed commands. --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Cooker] [Bug 1062] [drakxtools] No ip over 1394
https://qa.mandrakesoft.com/show_bug.cgi?id=1062 --- Additional Comments From [EMAIL PROTECTED] 2003-02-19 16:35 --- I had it working here as far as I could see. shouldn't be a alias eth1394 eth1 be enough if firewire is working ? As far as I know firewire is not bad supported under linux. This should be at least be proved. --- 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: DrakConnect doesn't list eth1394 as a driver, and expert mode crashes when I try it. This is after I have done insmod eth1394.o.gz and re booted. Actually, this option should be offered during the install, automatically, so those of us who are relying on our firewire cards to connect two windows machines will be able to network our new Linux install to, say, our winxp machine. (My case). Even though my Linux bootup screen says eth0 is "OK", my winxp machine can't tell it's there. xp says "1394 Connection A network cable is unplugged." The Linux machine is dual booted with winme which does work with ip over 1394, Internet and everything. Linux needs to do ip over 1394 "out of the box", firewire has been around for some time now. And I can't find ANY documentation on the eth1394 module anywhere. Any ideas?
[Cooker] [Bug 636] [isdn4k-utils] example-files stated in the documation are missing
https://qa.mandrakesoft.com/show_bug.cgi?id=636 --- Additional Comments From [EMAIL PROTECTED] 2003-02-19 16:26 --- The example-files are in the src.rpm, but are cutted out during packaging. As the isdn4-k-utils are such a monster, i can't see where the problem is. --- 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: If I want configure vbox the examples as stated in the documentation aren't anywhere on my system. The are needed for having some initial files, so own files can be recorded. Will add a tar.gz I got from another Distri. Please add the missing files. Greets Steffen
