June 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 617732] New: MD: newly created window is not displayed
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617732 http://bugzilla.novell.com/show_bug.cgi?id=617732#c0 Summary: MD: newly created window is not displayed Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 I had no such problem prior to 2.4. I created window, added vbox, and to each entry -- label, progressbar and button. In designer the window is properly shown, but when I run the app, the window is empty and I get such warning: Gtk-WARNING **: Attempting to add a widget with type GtkVBox to a __gtksharp_2_prim_ProgressDialog, but as a GtkBin subclass a __gtksharp_2_prim_ProgressDialog can only contain one widget at a time; it already contains a widget of type GtkVBox So it cannot exists, because it exists. -- 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 0

[Bug 617731] New: MD: resizing pads in IDE is dead slow
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617731 http://bugzilla.novell.com/show_bug.cgi?id=617731#c0 Summary: MD: resizing pads in IDE is dead slow Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 I have several pads opened (CPU is 2.8GHz, Core2Duo) and resizing then is dead slow. -- 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 0

[Bug 617730] New: MD designer: offer drop down list with events when setting handler of the signal
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617730 http://bugzilla.novell.com/show_bug.cgi?id=617730#c0 Summary: MD designer: offer drop down list with events when setting handler of the signal Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 Go to properties of the widgets -> signals -> it would be nice if I could click on combobox (non existing now) for signal onclick for example and pick up already existing handler for it. -- 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 0

[Bug 617729] New: MD: deleting files from project does not delete data from designer
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617729 http://bugzilla.novell.com/show_bug.cgi?id=617729#c0 Summary: MD: deleting files from project does not delete data from designer Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 Add some dialog to project. Then delete it from the solution (chose "delete", not "remove from project"). Now -- create new dialog and name it the same. Go to designer -- you will see your old stuff. -- 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 0

[Bug 617728] New: MD: cannot change initial dialog
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617728 http://bugzilla.novell.com/show_bug.cgi?id=617728#c0 Summary: MD: cannot change initial dialog Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 Mission impossible. Initial dialog has action area. The moment I delete it and I add some my stuff I get exceptions (from MD). I save&quit, I run MD again and I get my stuff but action area is back. Now with undeleteable buttons -- I delete button, and it is recreated. I cannot simply use dialog in MD 2.4 because of it. -- 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 0

[Bug 617727] New: MD: add the ability to drag&drop nodes of documents outline
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617727 http://bugzilla.novell.com/show_bug.cgi?id=617727#c0 Summary: MD: add the ability to drag&drop nodes of documents outline Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 The reason: to reorder the elements. Currently reorganizing the dialog is very hard. Currently I am redoing whole dialog from scratch because no matter I do I cannot get rid of top level Vbox added automatically by MD. -- 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 0

[Bug 617726] New: MD: RMB does not select element
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617726 http://bugzilla.novell.com/show_bug.cgi?id=617726#c0 Summary: MD: RMB does not select element Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 I am working with document outline and it is very time consuming to click on every element LMB and then RMB just to show context menu. I should point out element and click RMB -- that's it. Twice less clicks = productivity. -- 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 0

[Bug 617723] New: MD: use consistent name for checkbox
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617723 http://bugzilla.novell.com/show_bug.cgi?id=617723#c0 Summary: MD: use consistent name for checkbox Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 In toolbox checkbox is listed as "check box", when created the default name is "checkbutton". -- 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 0

[Bug 617719] New: MD: incorrect caret placement on error
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=617719 http://bugzilla.novell.com/show_bug.cgi?id=617719#c0 Summary: MD: incorrect caret placement on error Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mono AssignedTo: bnc-team-mono(a)forge.provo.novell.com ReportedBy: bluedzins(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- MD 2.4 let's say I have error Error CS0246: The type or namespace name `Glib' could not be found. Are you missing a using directive or an assembly reference? (CS0246) so I click on it (error message). MD jumps to the line (| denotes caret) var thread = new Glib.Thread (n|ew ParameterizedThreadStart (doUpdateCorpusInfo)); It should be placed directly after "Glib", not inside "new". -- 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 0

[Bug 267903] KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
by bugzilla_noreply＠novell.com 27 Jun '10

27 Jun '10

http://bugzilla.novell.com/show_bug.cgi?id=267903 http://bugzilla.novell.com/show_bug.cgi?id=267903#c21 Thomas Mitterfellner <tomm(a)sbox.tugraz.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomm(a)sbox.tugraz.at --- Comment #21 from Thomas Mitterfellner <tomm(a)sbox.tugraz.at> 2010-06-27 10:27:38 UTC --- I think the problem is that the script /usr/share/kde4/apps/kdm/read_sysconfig.sh generates the file /var/adm/kdm/kdmrc.sysconfig on the fly (according to the settings in /etc/sysconfig/displaymanager kdmrc.sysconfig is used for configuration of kdm instead of /usr/share/kde4/apps/kdm/kdmrc which is the file edited by the kde control panel settings. In my opinion, this is a design issue in the yast sysconfig method, which causes a lot of confusion. Maybe the kdm configuration should be left to kde tools, so the script read_sysconfig.sh will just cat the kdmrc file to the kdmrm.sysconfig file. This would require a hint or documentation what's going on. It's e.g. not possible to have only certain users with password-less login, becaus read_sysconfig has: f [ "$DISPLAYMANAGER_PASSWORD_LESS_LOGIN" = "yes" ]; then echo "NoPassEnable=true" echo "NoPassAllUsers=true" else echo "NoPassEnable=false" echo "NoPassAllUsers=false" fi There is eg. no equivalent setting for NoPassUsers in sysconfig/displaymanager, so whatever the setting for the users which aren't required entering a password done via the kde systemsettings might be - it has no effect. (I changed the echo "NoPassAllUsers=true to echo "NoPassUsers=user1,user2,user4" as a dirty workaround for getting what I want). -- 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 0