https://bugzilla.novell.com/show_bug.cgi?id=642456https://bugzilla.novell.com/show_bug.cgi?id=642456#c0
Summary: Permission issue for the "nut" UPS software
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: reg(a)capiogroup.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.10)
Gecko/20100914 SUSE/3.6.10-30.1 Firefox/3.6.10
On a standard install of nut (Network UPS Tools), classic version (not HAL) the
driver did not have permission to run until I added the the group "root" to the
user "upsd".
my nut.conf is:
[myups]
driver = usbhid-ups
port = /dev/usb/hiddev0
desc = "Tripp Lite UPS SU1500XL"
Once that change was made it worked just fine. I don't think this is a big
issue but they documentation goes out of it's way to make a point of keeping
permissions on the nut daemon restricted so I thought it should be noted.
Perhaps just a documentation change to let people know that it might be
necessary would be enough.
Reproducible: Always
Steps to Reproduce:
1.Install
2.Set the nut.conf file
3.Try to run the driver: /usr/lib/ups/driver/upsdrvctl start
Actual Results:
Permission denied error.
--
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=635303https://bugzilla.novell.com/show_bug.cgi?id=635303#c0
Summary: dump version incompatible with ext4
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.3
Status: NEW
Severity: Blocker
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: cilantro05(a)comcast.net
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
How can you possibly provide dump-0.4b41 on the OpenSuSE 11.3 download page,
when that version does not support the filesystem of your default installation,
ext4? I am a longtime SuSE (and dump) user, and it never would have occurred
to me to check this. OK, my mistake -- but I just lost a whole day's work
because my careully made backup was trash. Dump 0.4b42 does claim ext4
support... At the very lease, a prominent warning should be added to the
result of a search for dump on software.opensuse.org.
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=571841http://bugzilla.novell.com/show_bug.cgi?id=571841#c0
Summary: dump/restore version from oss fails when ext4
filesystem is used
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: All
OS/Version: openSUSE 11.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Maintenance
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: deligeo(a)physics.uoc.gr
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6)
Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6
Attempting to use the dump/restore backup tool (Version 0.4b41-161.1 x86_64)
from oss repository to backup and restore /home the resulting files where
corrupted.
This is a known issue upstream and is corrected in version 0.4b42.
See bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511651 for more
details.
Reproducible: Always
Steps to Reproduce:
1.use dump to backup an ext4 filesystem
2.move into a different computer
3.attempt to restore in an ext3 filesystem
Actual Results:
Files produced are not identical to original files. Several text files are now
reported as binary.
Expected Results:
Should produce a correct image of initial files in the new filesystem.
Or at the very least dump should NOT allow ext4 filesystems to be used until it
is properly working on them.
The main issue is that dump will not complain about ext4 partitions being
dumped. Thus the problem is encountered later (too late) on when one attempts
to restore the filesystem.
Version 0.4b42 should resolve this issue by dealing with ext4 filesystems
correctly thus restoring dump/restore functionality.
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=529135
Summary: openvas-client-2.0.1-1.33: missing call to close
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: dcb314(a)hotmail.com
QAContact: qa(a)suse.de
Found By: ---
I just had a look at factory package openvas-client-2.0.1-1.33
For source code file openvas-client-2.0.1/nessus/comm.c
around line 870 is the source code for the
function comm_send_file.
I notice the following line of code
fd = open(fname, O_RDONLY);
but I notice that close is only called on failure.
Suggest add a call to close at the end of the routine,
for the return success case. Like
network_gets(context->socket, buff, sizeof(buff) - 1);
fclose( fd);
return 0;
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=502531
Summary: bsd-games-2.17-81.44: undefined code
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: dcb314(a)hotmail.com
QAContact: qa(a)suse.de
Found By: ---
I just tried to build Factory package bsd-games-2.17-81.44
and the build said
monop/cards.c:138: warning: operation on "dp->last_card" may be undefined
The source code is
dp->last_card = ++(dp->last_card) % dp->num_cards;
I agree with the compiler. Better code would be
dp->last_card = (dp->last_card + 1) % dp->num_cards;
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=535926
Summary: openvas-client-2.0.4-1.3: bad call to close
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: dcb314(a)hotmail.com
QAContact: qa(a)suse.de
Found By: ---
I just had a look at factory package openvas-client-2.0.4-1.3
For source code file openvas-client-2.0.4/libnessus/rand.c
around line 60, function nessus_init_random
is the following code
if ((fd = open(EGD_PATH, O_RDWR)) >= 0)
but the matching call to close is
close(s);
which looks wrong. Maybe
close( fd);
would be better.
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=544454
Summary: openvas-client-2.0.4-1.6: missing call to close
Classification: openSUSE
Product: openSUSE 11.2
Version: Factory
Platform: All
OS/Version: openSUSE 11.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: dcb314(a)hotmail.com
QAContact: qa(a)suse.de
Found By: ---
I just had a look at factory package openvas-client-2.0.4-1.6
source code file openvas-client-2.0.4/nessus/read_target_file.c
function target_file_to_list
local variable fd
I notice the following code
HANDLE fd = open(filename, O_RDONLY);
but I fail to find a matching call to close. This looks like a resource
leak to me. Suggest add call to close near the end of the function.
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=505546
User Winfrid.Tschiedel(a)ts.fujitsu.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=505546#c500322
Summary: Grub fails to write bootrecord on dmraid disk (GPT
labeled)
Classification: openSUSE
Product: openSUSE 11.2
Version: Milestone 1
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: Winfrid.Tschiedel(a)ts.fujitsu.com
QAContact: jsrain(a)novell.com
Found By: ---
Created an attachment (id=293215)
--> (http://bugzilla.novell.com/attachment.cgi?id=293215)
saved installation logs
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Tablet PC
1.7; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR
3.0.04506.648; .NET CLR 3.5.21022; MS-RTC LM 8; InfoPath.2)
I tried to install openSUSE 11.2 Milestone 1 on Fujitsu Primergy RX220
( Promise FastTrak TX 150 S4 ), one disk with RAID0, GPT labeled
( Same problem exists also on Fujitsu Primergy rx200s4 with ESB2 (LSI Firmware)
and one disk RAID0. Installation works until the boot record should be written.
In case of rx220 the boot record should be written to the root partition.
Beside the error 22: No such partition also the MBR was destroyed.
Reproducible: Always
Steps to Reproduce:
1. Installed openSUSE 11.2 on fake raid with GPT
Actual Results:
No boot redord was written
Expected Results:
Correct operation, install a system which can be booted afterwards
In the latest release of fedora 11 (Preview) almost everything works out of the
box, which means only manual interaction for the following items is needed :
mklabel gpt (no botton for writing new partition table!)
mkinitrd on distribution is in error
for details please read #500322 (bugzilla.redhat.com)
I tried to write a new bootrecord with fedora 11 - which worked -
but openSUSE 11.2 cannot handle this bootrecord - so chainloading failed .
Next I tried to load the openSUSE boot menu with
configfile /boot/grub/menu.lst
So I could start openSUSE 11.2, but boot fails because root partition is not
found. This seems to be similar to #500979 - with one difference
that at that time (SLED 11) only the problem on ESB2 occurred.
There is also a second difference, in the previous edition (openSUSE 11.1,SLED
11) there was a problem with GPT and dmraid, which ended up, that the RAID
information was destroyed (please see #436825 )
--
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.
http://bugzilla.novell.com/show_bug.cgi?id=608457http://bugzilla.novell.com/show_bug.cgi?id=608457#c0
Summary: screen corruption when scrolling with window in the
foreground
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Firefox
AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com
ReportedBy: oneukum(a)novell.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
If another window is in front of firefox's window, text exposed by scrolling
firefox's window is corrupted. This happens only with firefox and regardless of
what kind of window is in front.
--
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.