https://bugzilla.novell.com/show_bug.cgi?id=304571
Summary: sieve kioslave garbles sieve scripts
Product: openSUSE 10.3
Version: Beta 2
Platform: x86-64
OS/Version: openSUSE 10.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: herbert(a)graeber-clan.de
QAContact: qa(a)suse.de
Found By: ---
sieve scripts accessed using the sieve kioslave are truncated at some point.
The cut position varies from script to script, but seems to be the same when
reading the same script.
Accessing the same scripts using sieveshell work fine.
This happens with KDE from openSUSE 10.3 Beta2 and KDE from KDE:KDE3 build
service repository for openSUSE 10.2 (2007-08-24).
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=307026
Summary: YaST cannot configure Atheros-Chip based WLAN card
Product: openSUSE 10.3
Version: Beta 2
Platform: i686
OS/Version: openSUSE 10.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: juergen.mell(a)t-online.de
QAContact: jsrain(a)novell.com
Found By: ---
Created an attachment (id=161364)
--> (https://bugzilla.novell.com/attachment.cgi?id=161364)
YaST's log when trying to configure the card while it is up and running
I have an Atheros based WLAN card. I compiled the current Madwifi kernel
modules and loaded them. YaST now detects the network card and shows it as 'not
configured'. I went through the whole configuration dialog masks (IP address,
WPA passphrase etc.). After that the card appeared in YaST's network devices
table with an IP address and all seemed to be well. But after clicking on
'Finish' YaST did not write any file to /etc/sysconfig/network.
After copying the ifcfg- file from SUSE 10.2 and renaming it to ifcfg-ath0 I
could set-up the network card correctly and it works fine. But still YaST shows
the card as 'not configured', even while it is up and running. Going through
the configuration dialog again does not cause any modifications to the
ifcfg-ath0 file in /etc/sysconfig/network.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=304301
Summary: marble does not start
Product: openSUSE 10.3
Version: Beta 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: mvidner(a)novell.com
QAContact: qa(a)suse.de
CC: mzugec(a)novell.com
Found By: ---
kde4-marble.rpm does not start out of the box. It seems that some path prefix
is undefined (note "systempath: /mwdbii/...").
martin@totoro:~> marble
localpath: /home/martin/.marble/data/legend.html
systempath: /legend.html
Using path: /legend.htmlQFSFileEngine::open: No file name specified
[...]
localpath: /home/martin/.marble/data/mwdbii/DATELINE.PNT
systempath: /mwdbii/DATELINE.PNT
Using path: /home/martin/.marble/data/mwdbii/DATELINE.PNT
Couldn't find any maps! Exiting ...
Workaround:
mkdir ~/.marble; ln -snf /usr/share/kde4/apps/marble/data ~/.marble/data
sudo chmod ugo+w /usr/share/kde4/apps/marble/data/maps/earth/srtm/
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=297616
Summary: Yast doesn't write/save WLAN device settings
Product: openSUSE 10.3
Version: Alpha 7
Platform: x86-64
OS/Version: openSUSE 10.3
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: funtasyspace(a)yahoo.com
QAContact: jsrain(a)novell.com
Found By: ---
Created an attachment (id=155635)
--> (https://bugzilla.novell.com/attachment.cgi?id=155635)
tail -f /var/log/YaST2/y2log
Yesterday I installed Alpha 7, it's the first time I installed an openSUSE 10.3
version at all. As openSUSE 10.3 ships the new mac80211 subsystem, I tried to
make the 'Intel PRO/Wireless 3945ABG' device of my ThinkPad T60p work, using
the iwlwifi driver from intellinuxwireless.org, which was written for the
mac80211 subsystem.
So I got the iwlwifi driver (version 0.1.8) from http://intellinuxwireless.org/
together with the microcode image (version iwlwifi-3945-ucode-2.14.1.5). It
compiles without errors and loading the iwl3945 kernel module works fine and
brings up the 'wlan0' interface. Well, only the wlan LED on my ThinkPad does
not light!
Now the device shows up in Yast too, and it seems like it can be configured as
usual. But actually it doesn't work, because the settings are not written to
disk. Every time I launch the Yast network device settings section again, my
WLAN device appears unconfigured. Looking in /etc/sysconfig/network reveals,
that no configuration file for the wlan devices is ever created. I nearly tried
all possible settings in Yast by now, just to see if it will save the
configuration to /etc/sysconfig/network/ under any circumstances, but that
never happened. In contrast, the settings of my wired e1000 device are written
to /etc/sysconfig/network/ifcfg-eth0 with no problem.
Next I tried copying the configuration of my wlan device from my openSUSE 10.2
configuration, to see if Yast will recognize and read it, at least. On openSUSE
10.2 the configuration file of my wlan device had the filename
ifcfg-wlan-id-00:10:20:30:40:50 (where 00:10:20:30:40:50 is not my real mac
address, I just don't want to post it here). Copying that file to
/etc/sysconfig/network on openSUSE 10.3, won't let Yast detect the
configuration, the device still appears as not configured in Yast. An
'rcnetwork restart' won't use the configuration, too. Here the output:
wlan0 device: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev
02)
No configuration found for wlan0 unused
Well, renaming 'ifcfg-wlan-id-00:10:20:30:40:50' to 'ifcfg-wlan0' causes the
configuration to be recognized by ifup and rcnetwork start/restart will
successfully establish a connection with my access point. Anyway, even now my
wlan0 device still doesn't show up as configured in Yast.
I also tried the 'User Controlled with NetworkManager' Option, but this way, I
can only connect using WEP encryption. WPA doesn't work with NetworkManager.
Anyway, since I make heavy use of SCPM, NetworkManager is not really an option
for me.
I come to the conclusion, that this is a YaST problem, because manually
creating the ifcfg file and placing it in /etc/sysconfig/network works well.
Next I did a 'tail -f /var/log/YaST2/y2log' to find out, why Yast doesn't write
down the configuration for the wlan interface, but for the wired interface. I
append the complete output as a file to this post. Interesting are the lines
where it says:
2007-08-05 16:34:27 <1> myhost(21379) [YCP] NetworkModules.ycp:220 No changes
to netcard modules -> nothing to write
2007-08-05 16:34:27 <1> myhost(21379) [YCP] NetworkDevices.ycp:651 No changes
to netcard devices -> nothing to write
I hope this information helps to track down the problem.
Regards,
Jörg
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=304803
Summary: kitchensync can't show differences between two blobs
Product: openSUSE 10.3
Version: Beta 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Mobile Devices
AssignedTo: dgollub(a)novell.com
ReportedBy: cstender(a)novell.com
QAContact: qa(a)suse.de
Found By: ---
In openSUSE 10.2 Kitchensync was able to show differences between two blobs (in
conflict case). We used the xml diff algo to provide this functionality. This
is not included in openSUSE 10.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.
https://bugzilla.novell.com/show_bug.cgi?id=196855#c11
Lubos Lunak <llunak(a)novell.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |sven.burmeister(a)gmx.net
--- Comment #11 from Lubos Lunak <llunak(a)novell.com> 2007-09-01 04:42:02 MST ---
Can you please provide a screenshot? I don't see any untranslated entries here,
in Czech.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=302546
Summary: Novell Customer Center Configuration failed
Product: openSUSE 10.3
Version: Beta 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: lmichnovic(a)novell.com
QAContact: jsrain(a)novell.com
Found By: ---
Created an attachment (id=159108)
--> (https://bugzilla.novell.com/attachment.cgi?id=159108)
y2logs
I'm installing openSUSE-10.3-Beta2-GNOME-i386-Build936-CD1.iso
and the configuring of Novell Customer Center Configuration failed.
Attaching y2logs.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=239570
Summary: "Novell Customer Center Configuration": error message
truncated
Product: openSUSE 10.3
Version: unspecified
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: gp(a)novell.com
QAContact: jsrain(a)novell.com
When trying to register a STABLE/FACTORY machine I installed today, I got
the following error message in a dialog without title:
Error
None of the installed products can be registerd at the Novell reistrati
Here the message ended, and I would have needed to scroll.
This is rather bad. The window is, by far, sufficiently large and we should
show the user the full message without scrolling.
This was in graphical/Qt YaST.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=288730
Summary: Hardware settings: aspect ratio of screen crashes X
Product: openSUSE 10.3
Version: Alpha 5
Platform: i686
OS/Version: Linux
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: danielstefanmader(a)web.de
QAContact: jsrain(a)novell.com
Found By: Beta-Customer
When performing the installation (DVD medium), the final step is Hardware
settings. Being curious what the aspect ratio settings offers I clicked this.
Since I was unsure what diagonal size my 15" laptop screen has I pressed
Cancel. The Xsession crashed, restarted and offered the login screen right
away. I rebooted and received a complaint about an unfinished previous
installation :)
Looks like the sax2 component is not very tolerant towards errors or screens
not reporting their size?
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=294146
Summary: /dev/null permission denied
Product: openSUSE 10.3
Version: Alpha 6
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: Hotplug
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: silviu_marin-caea(a)otpbank.ro
QAContact: qa(a)suse.de
Found By: ---
I have performed an update from Alpha6 to latest Factory.
After the update I could not log in to KDE, it would just sit there after I
have entered the password in KDM.
Then I have seen that I get many /dev/null access denied errors if I log in the
text console.
It seems that /dev/null does not have sufficient permissions for my user. I
have chmod a+rw /dev/null and stopped resmgr so it would not restrict the
permissions again.
After that, I could login to KDE and the console login didn't give /dev/null
permission denied errors anymore.
The bug has probably something to do with the new hal version too.
--
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.