February 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 666404] New: YAST>Software Management> Options Menu - Remove Default 'Show Devel' and 'Show Debug'
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=666404 https://bugzilla.novell.com/show_bug.cgi?id=666404#c0 Summary: YAST>Software Management> Options Menu - Remove Default 'Show Devel' and 'Show Debug' Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: scott(a)aphofis.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 In YAST>Software Management>Options Menu the 'Show Devel' and Show Debug' Options are ON by default - Whilst configuring Repositories, the DEBUG repository states it is for experts only and I would think many would not elect to add a Debug Repository, but most just add every repository. In the same contents most users do not want to see Debug or Development packages by default yet these conditions are default in Software Management. I feel that many users get unduly worried when the search for applications when the list includes both Debug and Applications are under development. My request is that we remove these two defaults and in their place have the 'System Verification Mode' and 'Clean-up When Deleting Packages' and 'Allow Vendor Change' - as the three defaults rather than Debug and Development being the default. Its by far a more user friendly approach however for those few users and at factory I can see their value. None the less the 2 current default only serve to confuse users and often result in applications being installed that are primarily still in developement. Having the default 'Allow Vendor Change' is a no brainer - so many users get frightened with conflict resolutions appearing when a simple change of vendor is the only requirement to accept new changes or additional software. QA - I'm not sure if this belongs to the Classification of Usability or of Yast - Your call Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 641528] New: 2.6.34.7-0.3-desktop update breaks ATI proprietary driver.
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=641528 https://bugzilla.novell.com/show_bug.cgi?id=641528#c0 Summary: 2.6.34.7-0.3-desktop update breaks ATI proprietary driver. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: IA64 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nmo.marques(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/5343 (KHTML, like Gecko) Chrome/6.0.472.62 Safari/534.3 Upon installing the referred update (kernel 2.6.34.7-0.3-desktop) the ATI proprietary driver no longer compiles. Reproducible: Always Steps to Reproduce: 1. Install kernel 2.6.34.7-0.3-desktop and after re-install fglrx driver. 2. 3. Actual Results: fglrx module no longer compiles reporting: /usr/src/kernel-modules/fglrx/kcl_ioctl.c: In function ‘KCL_IOCTL_AllocUserSpace32’: /usr/src/kernel-modules/fglrx/kcl_ioctl.c:196:5: error: implicit declaration of function ‘compat_alloc_user_space’ /usr/src/kernel-modules/fglrx/kcl_ioctl.c:196:5: warning: return makes pointer from integer without a cast make[3]: *** [/usr/src/kernel-modules/fglrx/kcl_ioctl.o] Error 1 make[2]: *** [_module_/usr/src/kernel-modules/fglrx] Error 2 make[1]: *** [sub-make] Error 2 make: *** [all] Error 2 Expected Results: the module would probably compile! One possible way of solving this is: http://ubuntuforums.org/showthread.php?p=9870037 Post #10. ATI proprietary driver already compiles after such change is commited. Not sure about the impact of it on the kernel itself though. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 654261] New: wlan pcmcia card not recognized correctly
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=654261 https://bugzilla.novell.com/show_bug.cgi?id=654261#c0 Summary: wlan pcmcia card not recognized correctly Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i686 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Mobile Devices AssignedTo: mobile-bugs(a)forge.provo.novell.com ReportedBy: estellnb(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 If I insert my wlan pcmcia card and configure it with Yast it is not recognized correctly. The first strange thing is that it appears as eth1 instead of wlan0. The second thing is that the eth1 wlan interface does not support basic wlan activities as scanning and can therefore not be used at all. The following occurs on a fresh booted, freshly configured system: root:~> wpa_supplicant -ieth1 -c /etc/wpa_supplicant.conf ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCSIWENCODEEXT]: Invalid argument ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan. ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCSIWSCAN]: Device or resource busy Failed to initiate AP scan. ^CCTRL-EVENT-TERMINATING - signal 2 received root:~> lspcmcia Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:02:04.0) Socket 1 Bridge: [yenta_cardbus] (bus ID: 0000:02:04.1) Socket 1 Device 0: [orinoco_cs] (bus ID: 1.0) root:~> pccardctl info 1 PRODID_1="Wireless" PRODID_2="LAN Adapter" PRODID_3="Version 01.02" PRODID_4="" MANFID=0156,0002 FUNCID=6 root:~> pccardctl status 1 5.0V 16-bit PC Card Subdevice 0 (function 0) bound to driver "orinoco_cs" root:~> iwlist eth1 scanning eth1 Interface doesn't support scanning : Network is down root:~> ifconfig eth1 eth1 Link encap:Ethernet Hardware Adresse 00:E0:98:9F:85:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 Sendewarteschlangenlänge:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:10 Basisadresse:0x3080 root:~> ethtool eth1 Settings for eth1: Link detected: no root:~> iwconfig eth1 eth1 IEEE 802.11b ESSID:"" Mode:Managed Frequency:2.412 GHz Access Point: None Bit Rate:11 Mb/s Sensitivity:1/0 Retry short limit:8 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality=0/70 Signal level=-68 dBm Noise level=-122 dBm Rx invalid nwid:0 Rx invalid crypt:3 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 547664] New: rtcwake one hour off
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

http://bugzilla.novell.com/show_bug.cgi?id=547664 Summary: rtcwake one hour off Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i586 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: uli.2001(a)gmx.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.14) Gecko/2009090900 SUSE/3.0.14-0.1.2 Firefox/3.0.14 rtcwake -s 10 is supposed to set my computer to sleep and wake it up 10 seconds later. However, rtcwake shows a time 1 hour and 1 seconds in the future as the planned wake up time. If I use date +%s to show the system time in seconds sind 1970, I get 1255709014, for example. Using this number plus 100 in rtcwake -t 1255709114 is supposed to wake my computer up 100 seconds in the future. However, rtcwake shows a time about 1 hour in the PAST. So rtcwake -t and rtcwake -s seem to be off by one hour - interestingly, in different directions. Furthermore, my computer is set to sleep, but I could not manage to wake it up yet (but I have not tested this thoroughly). Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 668435] New: VNC is producing heavily corrupted image.
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=668435 https://bugzilla.novell.com/show_bug.cgi?id=668435#c0 Summary: VNC is producing heavily corrupted image. Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: vodicka.petr(a)email.cz QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=411363) --> (http://bugzilla.novell.com/attachment.cgi?id=411363) Corrupted image from vncserver User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 After update to OpenSUSE 11.4 RC5 from 11.2, vncserver is not working correctly. It is running with errors, but when I connect from another computer or even over localhost with vncviewer or Krdc, image is corrupted (see attachment). Almost nothing can be recognized. vncserver is started with: vncserver -geometry 1024x768 -rfbauth /home/user/.vnc/passwd I also tried different pixel depths, but nothing changed. I also tried x11vnc - it is working correctly. Reproducible: Always Steps to Reproduce: 1. Start vncserver 2. Connect with vncviewer 3. Actual Results: Corrupted image - see attachment Expected Results: Correctly displayed remote desktop -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 379991] OpenOffice shows some the styles of some fonts in non-English languages
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=379991 https://bugzilla.novell.com/show_bug.cgi?id=379991#c25 --- Comment #25 from Petr Gajdos <pgajdos(a)novell.com> 2011-02-01 07:56:56 UTC --- (In reply to comment #24) > I'll forward to the dev mailing list ... thanks Petr ! :-) Caolan would want a > look I think. Definitely. Take this as very first try. I didn't test it much while I don't have time for that now, maybe later this week. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 668466] New: map file permissions set to low breaks autofs
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=668466 https://bugzilla.novell.com/show_bug.cgi?id=668466#c0 Summary: map file permissions set to low breaks autofs Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: marc(a)marcchamberlin.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 Being one user who is sick and tired of all the undocumented, inconsistent and obtuse security found on Linux, I often just give up and start opening up permissions to make things as permissive as possible in order to get things up and working on my OWN computers and my OWN network. As a sole user I OUGHT to be able to USE my computers without all this hassle. That said, I was trying to set up autofs to automatically mount file systems from other computers on my network. I set up my auto.master using references to other map files for mounting directories from other computers. For example with in auto.master I had lines such as - /mnt/auto/bigbang /etc/auto.bigbang --timeout=5 --ghost /mnt/auto/darkstar /etc/auto.darkstar --timeout=5 --ghost etc... This initially failed on me, and after many hours of debugging and trying to figure out why it was failing I finally discovered that when I had created my map files, such as /etc/auto.bigbang, the editor had saved the file with permissions of rwxr-xr-x and the executable permissions was the cause of failure. NO error messages, log messages, NOTHING gave me any clue as to why autofs was failing with these file permissions. And to an untrained eye, this does NOT appear to be an unreasonable setting for the map file permissions. To make matters worse, I tried as one of my experiments to simply chmod all the map files to 0x777 so as to open up the files for access by anyone and all users. That too failed! THIS IS YET ANOTHER EXAMPLE OF UNREASONABLE SECURITY PRACTICES and should be corrected. Either remove this restriction, or give the user clear concise error messages as to why this failure occurs. I would prefer the former. Reproducible: Always Steps to Reproduce: 1.Create map files with low file permissions. i.e. chmod them with 0x777 2. Try to use autofs and automount directories from another computer on your network. 3. Actual Results: autofs fails silently to automount files as described in the map files. Expected Results: I don't expect low/easy file permissions on map files to block autofs from mounting files specified in the map files. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 668486] New: at does not perform tasks to a time in the past in the future (tomorrow) properly
by bugzilla_noreply＠novell.com 01 Feb '11

01 Feb '11

https://bugzilla.novell.com/show_bug.cgi?id=668486 https://bugzilla.novell.com/show_bug.cgi?id=668486#c0 Summary: at does not perform tasks to a time in the past in the future (tomorrow) properly Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: aburgemeister(a)novell.com QAContact: qa(a)suse.de CC: bob(a)muhlenberg.edu, malcolm_lewis(a)bellsouth.net Found By: Customer Services Priority: 300 Blocker: --- +++ This bug was initially created as a clone of Bug #668485 +++ [Cloned for OpenSUSE 11.3] OpenSUSE 11.3 at 3.1.8 http://forums.novell.com/showthread.php?t=431213 A customer noticed that when setting their 'at' jobs to run at a time (no date specified) in the past as shown below, they would see the jobs scheduled to run in the past when running 'atq': <quote> nts105:~ # echo 'sleep 30;touch /tmp/testat-`date +%s`' | at 16:11 + 1 minute warning: commands will be executed using /bin/sh job 5 at 2011-01-31 16:12 nts105:~ # date Mon Jan 31 16:14:35 MST 2011 nts105:~ # atq 5 2011-01-31 16:12 = root </quote> Notice that despite the job being scheduled in the past it was not pushed forward to the same time tomorrow. It turns out that jobs specified in this way actually run immediately (this one shows up in the 'atq' output because of the thirty-second 'sleep' imposed delay, if atq is run within thirty seconds) but that is still not what is desired in the end. It makes the most sense for a job being scheduled at a time (even with an increment as in this case) that has already passed today to actually be scheduled for tomorrow. This works properly when a time ONLY (no increment after it) is specified. Considering the relatively low risk of this change (pretty obscure, SUSE doesn't enable 'at' by default, makes it more like how FreeBSD does things, possibly even used to work this way) it would be nice to have this implemented before the next SPs of the SLE product are released. This applies to OpenSUSE 11.3, SLES 11 SP1, and SLES 10 SP3. I'll clone these for the other builds. One of our Knowledge Partners has created a test build within the OpenSUSE Build Service (OBS) that partially solves the problem, though it also seems to break 'now' as the intended time, causing it to run at the same time as 'now' but tomorrow. The link for that build's code follows: https://build.opensuse.org/package/view_file?file=at-3.1.8-fix-current-time… Changing the code one more time to have: <code file="parsetime.y" line="378"> if (currtime > exectime) { </code> replaced with: <code file="parsetime.y" line="378"> if (currtime > exectime + 1) { </code> would probably resolve that issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1