http://bugzilla.novell.com/show_bug.cgi?id=584970http://bugzilla.novell.com/show_bug.cgi?id=584970#c0
Summary: Yast gives error -4017 when trying to partition using
LVM
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: HP
OS/Version: openSUSE 11.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Installation
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: p.c.manning(a)swansea.ac.uk
QAContact: jsrain(a)novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US)
AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.89 Safari/532.5
Hardware: HP ML115 with E200 SmartArray card. 4 250GB drives built as raid 5.
Use OpenSUSE DVD installer, select LVM partitioning scheme, installation dies
when preparing disks with error -4017
Reproducible: Always
Steps to Reproduce:
1.Use OpenSUSE 11.2 DVD 64bit to Install OS
2.Get to partitioning scheme - select LVM
3.Continue through installation, installation dies at preparing disks stage
Actual Results:
Retried this with text mode installer which enabled me to switch to a working
shell console, I could see that the installer had created a boot partition, an
LVM partition and an LVM group. But had failed to create any logical volumes
Expected Results:
A properly partitioned disk!
http://forums.opensuse.org/install-boot-login/433990-yast-partitioning-erro…
Workround was to partition manually via a shell console.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=691709https://bugzilla.novell.com/show_bug.cgi?id=691709#c0
Summary: synergy makes cursor disapear over GVIM windows
Classification: openSUSE
Product: openSUSE 11.4
Version: Factory
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X11 Applications
AssignedTo: adam(a)mizerski.pl
ReportedBy: jmatejek(a)novell.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
this happens on the computer where synergy server is running, not sure about
client
to reproduce:
1. start synergy server
2. open gvim window
3. start typing in gvim window (for non-vi folk, you initiate insert mode by
typing "i" or pressing Ins)
4. the mouse cursor disappears
5. stop typing and move your mouse
expected behavior:
mouse curshor should reappear - this is standard behavior, designed so that the
cursor is hidden while typing
actual behavior:
the mouse cursor never reappears. if you move mouse out of gvim's window,
cursor is visible, but it is invisible when positioned over the window
sorry if you're not the right assignee, but you are the only active user in the
X11:Utilities project and you did the last change to synergy, so...
--
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=714551https://bugzilla.novell.com/show_bug.cgi?id=714551#c0
Summary: Vim's ":tag" command should search corresponding
header file first.
Classification: openSUSE
Product: openSUSE 11.3
Version: Final
Platform: x86-64
OS/Version: openSUSE 11.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: nn.dm55(a)gmail.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0)
Gecko/20100101 Firefox/6.0
In a C++ project with many variables with the same name, searching for the
definition of a variable mentioned in a ".cpp" file using Ctrl-] gives me the
definition of an unrelated variable with the same name. The ":tag" command
should prefer the definition in the corresponding header file to any other
definitions to make finding the correct definition easier.
Reproducible: Always
Steps to Reproduce:
1. Download SuperTuxKart
2. Open src/karts/kart_model.cpp in Vim
3. Type "/::attachModel" and press Enter
4. Type "/else" and press Enter
5. Type "/m_mesh" and press Enter.
6. Hold Ctrl and press ], then release both keys
Actual Results:
You end up looking at the following line in src/graphics/shadow.hpp instead of
src/karts/kart_model.hpp:
scene::IMesh *m_mesh;
Expected Results:
I expected Vim to show me these line from src/karts/kart_model.hpp:
scene::IAnimatedMesh *m_mesh;
This bug happens even without having a .vimrc file.
I am using openSUSE 11.3 64-bit.
--
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=743548https://bugzilla.novell.com/show_bug.cgi?id=743548#c0
Summary: opensuse wiki misses a WYSIWYG editor
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Wiki
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: jw(a)suse.com
QAContact: tschmidt(a)suse.com
Blocks: 743547
Found By: ---
Blocker: ---
The wiki should have a WYSIWYG Editor.
tinyMCE can be enabled on MediaWiki. It can also be extended to offer
templates.
The current editor features only a source code view, and a very limited markup
support.
Typical editing requires multiple Preview-Edit cycles until the results come
out as intended. E.g. I myself often need a few attempts to get link target and
link labels in the right order with the right seperator in between.
--
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=680148https://bugzilla.novell.com/show_bug.cgi?id=680148#c0
Summary: kiwi complains about no clicfs tools if there is no
cdrkit compat
Classification: openSUSE
Product: openSUSE 11.4
Version: Factory
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: ms(a)novell.com
ReportedBy: coolo(a)novell.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
I wanted to create a small ISO with clicfs and kiwi complained that there are
no tools for clicfs.
After digging the code I figured it actually looked for mkisofs first and set
the toolerror flag because it's not there.
Afaik it's not even using mkisofs but genisoimage
--
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=688776https://bugzilla.novell.com/show_bug.cgi?id=688776#c0
Summary: outdated midnight commander man page
Classification: openSUSE
Product: openSUSE 11.4
Version: Factory
Platform: All
OS/Version: openSUSE 11.4
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: pcerny(a)novell.com
QAContact: qa(a)suse.de
Found By: Development
Blocker: ---
The manpage of midnight commander seems to be outdated, at least wrt the
description of the skins (as compared with the default skin file shipped in the
package) - it doesn't contain all recognized keywords (and some might even be
not supported any more). Creating a reasonbale skinn is hence impossible.
--
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=564306http://bugzilla.novell.com/show_bug.cgi?id=564306#c0
Summary: mc can not copy big files via shell to another local
networked computer.
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: i686
OS/Version: openSUSE 11.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: carlos.e.r(a)opensuse.org
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
I try to copy a large .iso file from one computer to another using mc, with its
shell link over ssh capability.
Of the 4169M file, just 74806Kb are copied to the remote filesystem, while the
rest is copied to the localfilesystem instead, to directory ???? To somewhere
in the root filesystem I have been unable to locate (yet?). Ah, somehow it has
been automatically erased, by mc on exit, I hope. I know it was copied to /
somewhere because I saw the available free space decreasing.
I did the test twice.
However, the command:
scp Copia.iso root@nimrodel://Grande/copia/Copia.iso
succeeds.
--
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.
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.