April 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 498566] New: Feature Request: Valkyrie
by bugzilla_noreply＠novell.com 29 Apr '10

29 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=498566 Summary: Feature Request: Valkyrie Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Commercial AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: noloader(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 Valkyrie [1], the visual front end to valgrind, might be a nice addition to the distribution. [1] http://valgrind.org/downloads/ Reproducible: Always Steps to Reproduce: N/A Actual Results: N/A Expected Results: N/A -- 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 496656] New: from time to time touchpad is dead but trackpoint is functional
by bugzilla_noreply＠novell.com 28 Apr '10

28 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=496656 Summary: from time to time touchpad is dead but trackpoint is functional Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- from time to time touchpad is dead but trackpoint is functional Steps to reproduce with workaround: 1) start computer, start working with KDE(3) 2) for mouse movement use touchpad (only) 3) after some time touchpad will be "disabled" -- at that point I can move several time my finger along the touchpad and the cursor is simply stuck, no response 4) after some time touchpad will be operational again but trackpoint is functional also so it is possible to simply touch trackpoint so it will cause minimal mouse cursor movement, and immediately after that touchpad is alive again -- 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 16

[Bug 498266] New: Change of repo priority from Configuration - Repositories in Software Management requires restart of Software Management
by bugzilla_noreply＠novell.com 26 Apr '10

26 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=498266 Summary: Change of repo priority from Configuration - Repositories in Software Management requires restart of Software Management Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rajko(a)opensuse.org QAContact: jsrain(a)novell.com Found By: Community User Background: Many users installed KDE 4.2.2 using 1-click install, which ads repo with priority 99. When comes time for update there is nothing to find. Check in YaST software management shows available version 4.1.3. Problem is that update repo is priority 20 and masks repo with priority 99. Workaround is to set KDE repo to 20 and then whatever version is newer will win. Problem is that changing repo priority from Configuration -> Repositories in Software Management requires restart of Software Management in order to see effects of new settings, which defeats purpose of having access to change repositories from Software Management, To reproduce: 1. Start Software Management 2. Go to Configuration -> Repositories change priority 3. Refresh all enabled; not sure is it necessary, but I do that regularly 4. Go back to Software Management and check Available Version What happens: The version is still the same. Restart Software Management and all is OK, there is no more "updates" with version 4.1.3, but 4.2.2-(build) if available. It is expected: That there is no need to restart Software Management, after changes in repository management module. -- 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 14

[Bug 498797] New: Wrong rpmlint warning: files-attr-not-set
by bugzilla_noreply＠novell.com 26 Apr '10

26 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=498797 User vuntz(a)novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=498797#c470409 Summary: Wrong rpmlint warning: files-attr-not-set Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: vuntz(a)novell.com QAContact: qa(a)suse.de Found By: --- I can see this warning: nautilus.src:174: W: files-attr-not-set nautilus.src:175: W: files-attr-not-set A file or a directory entry in a %files section does not have attributes set which may result in security issues in the resulting binary package depending on the system where the package is built. Add default attributes using %defattr before it in the %files section, or use per line %attr's. However, the lines are: %files lang -f %{name}.lang # remove the comment on the %if once bnc#470409 is fixed #%if %suse_version <= 1110 # exclude locales which don't exist on old versions of openSUSE %exclude %{_datadir}/locale/ha/LC_MESSAGES/* %exclude %{_datadir}/locale/ig/LC_MESSAGES/* #%endif It's complaining about the %exclude lines. This sounds wrong to me. -- 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 4

[Bug 492300] New: Attempting CDMA connection kills NetworkManager
by bugzilla_noreply＠novell.com 26 Apr '10

26 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=492300 User bjohnson(a)blakeanthonyjohnson.com added comment http://bugzilla.novell.com/show_bug.cgi?id=492300#c777 Summary: Attempting CDMA connection kills NetworkManager Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bjohnson(a)blakeanthonyjohnson.com QAContact: qa(a)suse.de CC: tambet(a)novell.com, cthiel(a)novell.com, clarkt(a)cnsp.com, captain.magnus(a)opensuse.org, mark(a)hanoverbeacon.org Found By: --- As of recently, my CDMA connection no longer works. (Sorry Tambet :-) It always kills NetworkManager at the marked spot below. Problem using the latest modem-manager (0.1_20081203-6.1.1) Downgrading to the original modem-manager and NetworkManager fixes the issue. EEE2008:/home/bjohnson # /usr/sbin/modem-manager --debug ** Message: Loaded plugin Novatel ** Message: Loaded plugin Option ** Message: Loaded plugin Huawei ** Message: Loaded plugin HSO ** Message: Loaded plugin MBM ** Message: Loaded plugin Sierra ** (modem-manager:10354): DEBUG: Created new generic modem (/org/freedesktop/Hal/devices/usb_device_1410_4100_091050674211000_if0_serial_usb_0) ** (modem-manager:10354): DEBUG: (/dev/ttyUSB0) opening serial device... ** (modem-manager:10354): DEBUG: --> 'ATZ E0 V1 X4 &C1<CR>' ** (modem-manager:10354): DEBUG: <-- 'ATZ E0 V1 X4 &C1' ** (modem-manager:10354): DEBUG: <-- '<CR>' ** (modem-manager:10354): DEBUG: <-- '<CR><LF>OK<CR><LF>' ** (modem-manager:10354): DEBUG: --> 'AT+CMEE=1<CR>' ** (modem-manager:10354): DEBUG: <-- '<CR><LF>ERROR<CR><LF>' ** (modem-manager:10354): DEBUG: Got failure code 100: Unknown error ** (modem-manager:10354): WARNING **: Your CDMA modem does not support +CMEE command ** (modem-manager:10354): DEBUG: --> 'ATDT#777<CR>' ** (modem-manager:10354): DEBUG: <-- '<CR><LF>CONNECT<CR><LF>' #### NetworkManager dies here #### ** (modem-manager:10354): DEBUG: <-- '<CR><LF>NO CARRIER<CR><LF>' ** (modem-manager:10354): DEBUG: Got failure code 3: No carrier EEE2008:/home/bjohnson # wvdial --> WvDial: Internet dialer version 1.60 --> Cannot get information for serial port. --> Initializing modem. --> Sending: ATZ ATZ OK --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 OK --> Modem initialized. --> Idle Seconds = 300, disabling automatic reconnect. --> Sending: ATDT#777 --> Waiting for carrier. ATDT#777 CONNECT --> Carrier detected. Starting PPP immediately. --> Starting pppd at Sun Apr 5 15:06:10 2009 --> Pid of pppd: 10417 --> Using interface ppp0 --> pppd: �[7f]��8�[06][08](�[06][08] --> pppd: �[7f]��8�[06][08](�[06][08] --> local IP address 174.158.120.62 --> pppd: �[7f]��8�[06][08](�[06][08] --> remote IP address 68.28.89.69 --> pppd: �[7f]��8�[06][08](�[06][08] --> primary DNS address 68.28.90.91 --> pppd: �[7f]��8�[06][08](�[06][08] --> secondary DNS address 68.28.82.91 --> pppd: �[7f]��8�[06][08](�[06][08] --> Script /etc/ppp/ip-up run successful --> Default route Ok. --> Nameserver (DNS) Ok. --> Connected... Press Ctrl-C to disconnect --> pppd: �[7f]��8�[06][08](�[06][08] -- 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 10

[Bug 497101] New: enhancement: NetworkManager and suspend/resume cooperation
by bugzilla_noreply＠novell.com 23 Apr '10

23 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=497101 Summary: enhancement: NetworkManager and suspend/resume cooperation Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: grey-olli(a)ya.ru QAContact: qa(a)suse.de Found By: --- User-Agent: Opera/9.64 (X11; Linux i686; U; en) Presto/2.1.1 After resuming from suspend to disk the network manager (if flag autoconnect is not checked) is not starting wifi connection. That would be nice to see special flag 'restore state after suspend'. I like the existing flag that stops from autoconnecting to 1st avaliable network (would be nice to apply that to ethernets also). It would be nice to try reconnect to the same essid if on suspend to disk we where connected, but only if special flag is checked. 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 498307] New: Network Manager Applet will Not Control Network Connection on a PC After Re-boot.
by bugzilla_noreply＠novell.com 23 Apr '10

23 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=498307 Summary: Network Manager Applet will Not Control Network Connection on a PC After Re-boot. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: qa(a)suse.de Found By: --- Created an attachment (id=288209) --> (http://bugzilla.novell.com/attachment.cgi?id=288209) 1 of 4 screen shots User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 In V11.1 we have disabled all control over the Network when we configure Yast>Network Devices>Network....change to Network Manager. A warning message is displayed once we have chosen to manage the network connection by Network Manager and the Window is totally greyed out. We then need to load the KDE3 Network Manager Applet to make any changes to the Network Connections. Despite configuring the Applet with a static IP, a Reboot will NOT activate Network Manager Applets conf. In fact at this point in time there is NO control over the Network Connection by any application at time of re-boot Reproducible: Always Steps to Reproduce: 1.Open Yast>Network Devices and change control from IFUP to Network Manager. 2.Re-Boot 3. Activate Network Manager Applet and create a Static IP and other connection information. 4. Save and Connect Network Manager Applet 5. Re-boot PC - Note that Network Manager has not connected and at this point in time no application appears to be controlling Network Connection Setting of ANY sort - Yet the PC seems to activate DHCP without any reference to DNS Servers IP. Actual Results: After the Network Manager Applet is configured and connected, subsequent PC re-starts will not connect according to any config in the Applet. Expected Results: Network Manager Applet was drastically changed for the worst in 10.3. Now in 11.1 we still do not have the Network Manager Applet back to it far better predecessor in 10.2. The current Network Manager is a KDE3 Applet and despite it retaining its very poor interface that was present in 10.2; the Applet config is not auto connected after PC reboot. Despite bug requests to change the applet back to is usable state in 10.2 - nothing has happened and the disastrous Applet has not changed since 10.3. Now at V 11.1 not only is the Applet still in its very poor regressive interface since 10.3, but the Applet does not even load and connect without manual user action. The Applets configuration will only hold true for 1 session as a re-boot will not re-connect the Applets configuration. After changing Yast>Network Devices> ..to be managed by Network Manager it would appear that nothing is directly managing any network connection and I have no idea what is managing the connection -- 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 14

[Bug 498735] New: latex with graphicx package: Package graphics Error: No driver specified.
by bugzilla_noreply＠novell.com 22 Apr '10

22 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=498735 Summary: latex with graphicx package: Package graphics Error: No driver specified. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: krienke(a)uni-koblenz.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.1.1 Firefox/3.0.8 When using graphicx style like in this demo document: \documentclass {article} \usepackage{graphicx} \begin{document} In diesem Text sollen die wichtigsten Befehle \includegraphics[scale=0.5]{logo} \end{document} Latex reports this error: .. ! Package graphics Error: No driver specified. See the graphics package documentation for explanation. Type H <return> for immediate help. ... The included graphics is a .eps file. This happens only with the texlive on openSuSE 11.1 not eg on a SLES10 machine with the very same file. A working fix is to include the driver name in the the head of the file like: \documentclass [dvips] {article} But this of course means you have to edit possibly many files manually to get them working again. It looks similar to this bug report I found: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg456878.html Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 492724] New: Handling of obsolete packages in yast2 sw_single
by bugzilla_noreply＠novell.com 21 Apr '10

21 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=492724 Summary: Handling of obsolete packages in yast2 sw_single Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: tgoettlicher(a)novell.com ReportedBy: vpelcak(a)novell.com QAContact: jsrain(a)novell.com Found By: --- It would be nice if yast2 sw_single was able to offer more option to handle obsolete packages. Now user typically has to display installed packages and pass through the list, manually select obsolete packages one by one and select action to perform. It would be cool if there was option to display obsolete packages in Installation summary. Together with feature which would allow multiple packages selection, that would ease handling of those packages. It would be also nice, if there was option in menu that would trigger automatic obsolete package handling. Then would be obsoleted packages replaced by available version or deleted. -- 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 5

[Bug 494842] New: Networkmanager is unable to connect across WiFi using ndiswrapper WPA encryption
by bugzilla_noreply＠novell.com 20 Apr '10

20 Apr '10

http://bugzilla.novell.com/show_bug.cgi?id=494842 Summary: Networkmanager is unable to connect across WiFi using ndiswrapper WPA encryption Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rastislav.krupansky(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; sk; rv:1.9.0.8) Gecko/2009032600 SUSE/3.0.8-1.2 Firefox/3.0.8 Hi. I use networkmanager with ndiswrapper on HP NX 6110, Broadcom BCM4318. Output lspci -v: Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) Subsystem: Hewlett-Packard Company Broadcom 802.11b/g WLAN Flags: bus master, fast devsel, latency 64, IRQ 21 Memory at d0000000 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: ndiswrapper Kernel modules: ssb Networkmanager is unable to connect to WiFi network encrypted in WPA, even though it is listed, and with a very good signal. The connection lasts very long and then is finished without the connection. Networkmanager displays no connected icon. Connection with no encryption ans WEP encryption are succesful. The wireless connection with b43 native driver using b43-fwcutter firmware works also without any troubles, but signal strenght is lower than using ndiswrapper. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 6