November 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 423460] New: openSuSE updater error
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=423460 Summary: openSuSE updater error Product: openSUSE 11.0 Version: Final Platform: 64bit OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jimdusis(a)yahoo.gr QAContact: jsrain(a)novell.com Found By: Community User After an update the updater applet made of itself, I mean the zypp components, everytime I do an update at a patch or upgrade an rpm it keeps showing me the following message in the end of the procedure: Problem occured during or after installation or removal of packages: rpmdb2solv -r '/' '/var/cache/zypp/solv/@System/solv' > '/var/cache/zypp/solv/@System/solvLoB90I' db->get: No such file or directory corrupt rpm database Please see the above error message for a hint. I really don't understand what is this, any ideas?? Jim -- 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 241611] New: incorrect snmptrapd initscript
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=241611 Summary: incorrect snmptrapd initscript Product: SUSE Linux 10.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rich(a)hq.vsaa.lv QAContact: qa(a)suse.de actually, a sles 10 problem. snmptrapd init script, located in /usr/share/doc/packages/net-snmp, has slightly incorrect snmptrapd start command : startproc $SNMPTRAPD -c /etc/snmptrapd.conf -Lf /var/log/net-snmpd.log there are two problems with this : 1. config file actually resides in /etc/snmp/ 2. if the config file path is correct, this leads to another problem - the file is read twice, because snmptrapd by default reads the configuration file and it can read several files (and it can read the same file twice). this leads to, for example, scripts being executed twice and so on. there are two simple solutions (unless snmptrapd behaviour is modified) : a) add -C switch; b) remove "-c /etc/snmptrapd.conf" note that file header says : # Copyright (c) 1996-2002 SuSE GmbH Nuernberg, Germany. All rights reserved. # # Author: Christopher Mahmood <ckm(a)suse.de>, 2002 additionally, would be nice to have the file by default available in /etc/init.d, as snmpd init script is available - but i won't open a new enhancement report regarding this unless requested. -- 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, or are watching someone who is.

1 7

[Bug 439096] New: Cannot connect to UMTS network using NetworkManager ( nm-applet) any more
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=439096 Summary: Cannot connect to UMTS network using NetworkManager (nm- applet) any more Product: openSUSE 11.1 Version: Beta 3 Platform: i686 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)novell.com QAContact: qa(a)suse.de Found By: Product Management This has been working fine with openSUSE 11.0 and the same system (configuration), and it still works with kinternet. Using nm-applet I get the following in /var/log/messages: Oct 20 13:18:42 rana rcnetwork: Starting the NetworkManager Oct 20 13:18:46 rana modem-manager: (/dev/noz0) opening serial device... Oct 20 13:18:49 rana modem-manager: Closing device '/dev/noz0' Oct 20 13:18:54 rana modem-manager: (/dev/noz0) opening serial device... Oct 20 13:19:03 rana pppd[19284]: Plugin /usr/lib/pppd/2.4.4/nm-pppd-plugin.so loaded. Oct 20 13:19:03 rana pppd[19284]: pppd 2.4.5 started by root, uid 0 Oct 20 13:19:03 rana pppd[19284]: Removed stale lock on noz0 (pid 16351) Oct 20 13:19:03 rana pppd[19284]: Using interface ppp0 Oct 20 13:19:03 rana pppd[19284]: Connect: ppp0 <--> /dev/noz0 Oct 20 13:19:03 rana pppd[19284]: CHAP authentication succeeded Oct 20 13:19:03 rana pppd[19284]: CHAP authentication succeeded Oct 20 13:19:18 rana pppd[19284]: Terminating on signal 15 Oct 20 13:19:18 rana pppd[19284]: Connection terminated. Oct 20 13:19:19 rana modem-manager: Closing device '/dev/noz0' Oct 20 13:19:19 rana pppd[19284]: Exit. /var/log/NetworkManager has the following: Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) starting connection 'ZyXEL' Oct 20 13:18:15 rana NetworkManager: <info> (eth1): device state change: 3 -> 4 Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Oct 20 13:18:15 rana NetworkManager: <info> (eth1): device state change: 4 -> 5 Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1/wireless): access point 'ZyXEL' has security, but secrets are required. Oct 20 13:18:15 rana NetworkManager: <info> (eth1): device state change: 5 -> 6 Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Oct 20 13:18:15 rana NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... [some stuff on eth1 which is wireless] -- 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 4

[Bug 413570] New: [Feature-request] Yast should show Changelog of not installed packages
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=413570 Summary: [Feature-request] Yast should show Changelog of not installed packages Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: al4321(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Hi All ! Today, when trying to use Yast to view "Change Log" or "File List" of not yet installed packages, it shows me: "Information only available for installed packages." However I believe it is possible to fix Yast, because RPM provides it. Why should Yast be worse than RPM ? Like this: rpm -qilp --changelog mypackage.rpm This is example where RPM shows info about not-yet installed package. Please provide similar feature for Yast package manager. (maybe it will require adding metadata for Yast repositories, or reading directly from RPMs if they are in local repository) -Technologov, 31.7.2008. -- 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 7

[Bug 440821] New: Help for g-c-c does not work
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=440821 Summary: Help for g-c-c does not work Product: openSUSE 11.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: captain.magnus(a)opensuse.org QAContact: qa(a)suse.de Found By: --- Pressing F1 on the Desktop, then selecting GNOME Applications then Control Center shows this error dialog; The requested URI "help:control-cent" is invalid -- 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 369531] New: Mirror support in libzypp
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=369531 Summary: Mirror support in libzypp Product: openSUSE 11.0 Version: Alpha 2plus Platform: All OS/Version: openSUSE 11.0 Status: NEW Severity: Major Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: guru(a)unixtech.be QAContact: dmacvicar(a)novell.com Found By: --- Currently and unlike e.g. yum or smart, libzypp/yast2/zypper doesn't have support for a client-side list of mirrors. This is an issue during redirector (download.opensuse.org) downtime for several reasons: - people not able to install security patches - people not able to install openSUSE (network install) Experienced users can reconfigure the list of repository sources to use mirrors, but that isn't an option to less experienced users as they don't know where nor how to work around the issue. Client-side failover would greatly address the somewhat frequent downtime issues with the redirector as it could fall back on other servers. Another advantage would be a much more robust handling of various error scenarios that can occur when a file cannot be downloaded from a mirror as expected. One scenario is e.g. ftp5.gwdg.de is not being available for 5 minutes, because a router is being rebooted there (which actually happened today). What happens now is that after 1 to 3 minutes the redirection to that mirror is disabled by the redirector, since its probing notices it. But in the time window before disabling, many libzypp clients are sent to that server and get timeouts. With client-side mirror support, zypper and yast2 would try to fetch from the next mirror and succeed, without any user intervention (nor required expertise). Nevertheless, the mirror list should be dynamic instead of static (as it was implemented before the redirector) as that list changes frequently do to the ever changing content (security patches and especially Build Service repositories). A pretty precise approach is even documented on the wiki (http://en.opensuse.org/Libzypp/Failover), and other established, solid and widely tested implementations can be looked at for inspiration (smart, yum). While this sounds like an enhancement request, it is a much more critical point than one would think, as it regularly prevents people from updating with patches or even installing openSUSE in the first place. The following presentation given at FOSDEM by Peter Poeml gives some background: http://www.poeml.de/~poeml/talks/redirector/ References: - http://en.opensuse.org/Libzypp/Failover - http://lists.opensuse.org/zypp-devel/2007-06/msg00022.html - http://lists.opensuse.org/zypp-devel/2007-06/msg00006.html - http://www.poeml.de/~poeml/talks/redirector/ -- 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 10

[Bug 380735] New: can't specify that repositories conflict
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=380735 Summary: can't specify that repositories conflict Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: BuildService AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dmueller(a)novell.com QAContact: adrian(a)novell.com Found By: --- KDE:KDE4:STABLE:Desktop and KDE:KDE4:UNSTABLE:Desktop contain the same packages, just in different versions. it is not working that both repositories are added at the same time, therefore I would like to make sure that this is not the case. missing feature "this repository conflicts iwth another repository.." -- 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 7

[Bug 413508] New: Need elegant solution to disable Pulseaudio or other audio daemons.
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=413508 Summary: Need elegant solution to disable Pulseaudio or other audio daemons. Product: openSUSE 11.0 Version: Final Platform: i586 OS/Version: openSUSE 11.0 Status: NEW Severity: Enhancement Priority: P5 - None Component: Sound AssignedTo: tiwai(a)novell.com ReportedBy: nonfatmatt(a)gmail.com QAContact: qa(a)suse.de Found By: --- Pulseaudio causes many problems for the users of may pro audio applications, chiefly by introducing latency and obfuscating important sound card functions. Also, for users with sound cards that have hardware mixing, it's completely redundant and pointless. Currently there is no easy way to disable pulse other than manually removing the packages, but this causes problems insofar as the default GNOME mixer does not recognize straight ALSA because it has been replaced with a pulseaudio control and that many applications are confused and do not default to ALSA or are plain non-switchable. What opensuse needs is a robust but simple way to choose an audio infrastructure and default audio daemon, so those of us who use it for pro audio work (which it's suited for because of the rt kernel and up to date packages) and those of us with more advanced audio hardware don't have to rip out major portions of our system to gain functionality which is already included. -- 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 9

[Bug 434389] Incorrect screen resolution
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=434389 User sndirsch(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434389#c3 Stefan Dirsch <sndirsch(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |DUPLICATE --- Comment #3 from Stefan Dirsch <sndirsch(a)novell.com> 2008-11-03 05:05:48 MDT --- > Please don't call this WONTFIX/CANNOTFIX as I can make my mouse usable by > using kernel paramter > > i8042.nomux > > when GRUB shows up when I press the poweron button of my laptop. Please open a seperate bugreport for this filed against Kernel component. *** This bug has been marked as a duplicate of bug 440973 *** https://bugzilla.novell.com/show_bug.cgi?id=440973 -- 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 434389] Incorrect screen resolution
by bugzilla_noreply＠novell.com 03 Nov '08

03 Nov '08

https://bugzilla.novell.com/show_bug.cgi?id=434389 User stilo_vingyou(a)hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=434389#c2 Praveen Kunjapur <stilo_vingyou(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | Version|Beta 2 |Beta 3 --- Comment #2 from Praveen Kunjapur <stilo_vingyou(a)hotmail.com> 2008-11-03 04:45:38 MDT --- Please don't call this WONTFIX/CANNOTFIX as I can make my mouse usable by using kernel paramter i8042.nomux when GRUB shows up when I press the poweron button of my laptop. I reconfigured resolution to 1280*800 (which is the real resolution of my laptop unlike 1024*768 stated above. Sorry about that) by going to Kickoff Menu -> Applications -> Configure Desktop -> General -> (in section Computer Administration) Display. But, every time I logout/reboot from KDE 4 after reconfiguring the resolution to 1280*800, the resolution again revert backs to 800*600. Additionally, when the GRUB login screen shows up where one enters USERNAME and PASSWORD, by default, the GRUB login screen resolution is set to 800*600 when the real resolution of my laptop is 1280*800. The KDE splash screen which comes after logging one's USERNAME and PASSWORD, by default, also displays itself in the resolution of 800*600 which is incorrect since the correct resolution is 1280*800. Further, when I set my resolution to 1280*800 by going to Kickoff Menu -> Applications -> Configure Desktop -> General -> (in section Computer Administration) Display, KDE reverts to 1280*800, but the panel at the bottom doesn't set itself to 1280*800 resolution but stays at 800*600 resolution thereby displaying an incomplete panel bar. I will upload the screenshot of the panel to Bugzilla soon. The whole problem stated in this comment is prevalent in Beta 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 0