December 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 558477] New: GTK applications do not use the same Qtcurve settings as other applications
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=558477 http://bugzilla.novell.com/show_bug.cgi?id=558477#c0 Summary: GTK applications do not use the same Qtcurve settings as other applications Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: neptunia(a)mail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 When choosing Qtcurve style both for GTK and Qt applications, and then customizing the Qtcurve appearance, the new customization affects only Qt apps and GTK apps still appear as default. This happens because GTK looks for Qtcurve settings in $XDG_CONFIG_HOME/qtcurvestylerc. $XDG_CONFIG_HOME should default to ~/.config but this variable does not exist. Qtcurve settings are written to ~/config/qtcurve/stylerc, but ~/.config/qtcurvestylerc does not exist. So if toi add the following line export XDG_CONFIG_HOME=~/.config to /etc/profile.local so to create XDG_CONFIG_HOME and create a shortcut ~/.config/qtcurvestylerc pointing to ~/config/qtcurve/stylerc, all works well. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 3

[Bug 558135] New: KDE4 cannot deal with GNOME-produced modal dialogs (e.g. gnome-keyring)
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=558135 http://bugzilla.novell.com/show_bug.cgi?id=558135#c0 Summary: KDE4 cannot deal with GNOME-produced modal dialogs (e.g. gnome-keyring) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: pbaudis(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- If gnome-keyring-askpass pops up within KDE4 session, very strange things happen - suddenly, all keyboard input is lost for _no apparent reason_, since: * The window can pop up on a *different* workspace than the current one! * There is no visual indication that the dialog just stole all focus. This can happen when using some non-KDE application in KDE4, e.g. nm-applet or pidgin. When this does happen, it's a critical usability bug, if the user does not switch to all workspaces (using mouse only!) and notices the dialog, the whole computer is as good as crashed. Moreover, this seems to trigger application bugs, e.g. in case of pidgin, even after a restart, from user perspective all the account settings get lost since pidgin stops using gnome-keyring for passwords and resets its account settings (which is probably a pidgin bug). I'm not sure if this is KDE4 or GNOME bug. Maybe there are good security reasons to make the keyring prompt completely modal, but in that case: (i) It must be ensured that the window is always visible - in current workspace and on top of all other windows! (ii) There must be clear visual indication that a modal dialog stole all focus, e.g. greying out all other windows like in case of native KDE4 modal windows. KDE4 should treat GNOME modal dialogs the same way as native ones, or if that is too complicated for a quick fix, gnome-keyring should be modified not to create modal prompts until other common desktop environments can support them properly. -- 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 7

[Bug 557778] New: Inkscape: left ruler mangled
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=557778 http://bugzilla.novell.com/show_bug.cgi?id=557778#c0 Summary: Inkscape: left ruler mangled Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: madworm_de.novell(a)spitzenpfeil.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 The top ruler is fully visible, the left one is almost completely gone. Seems like some offset is wrong. This will be fixed in 0.47. I managed to compile 0.47-pre4 and it is OK there. Please upgrade once 0.47 is available. This will likely occur before 11.3 is out. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 557619] New: screen light is off when I turn off sleep mode and I can't turn the screen light on
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=557619 http://bugzilla.novell.com/show_bug.cgi?id=557619#c0 Summary: screen light is off when I turn off sleep mode and I can't turn the screen light on Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: szopi.neo(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 When I enter to sleep mode, and when I trying to turn off sleep mode, than I can see the desktop, but without the screen light, the screen is Dark, I can see whats on desktop but very hard, I have OpenSuse 11.2 installed on IBM thinkpad x40. Reproducible: Always Steps to Reproduce: 1.turn on sleep mode 2.turn off sleep mode 3. black screen apears Actual Results: After that, the screen light is turned off, but I can hardly see something on desktop Expected Results: when i turn off sleep mode the screen light should turn on with the desktop -- 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 1

[Bug 557567] New: Totem crashes when trying to open audio
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=557567 http://bugzilla.novell.com/show_bug.cgi?id=557567#c0 Summary: Totem crashes when trying to open audio Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: davideoli(a)alice.it QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.4) Gecko/20091016 Firefox/3.5.4 Whenever I try to open a media file with Totem (i tried only with audio, several formats) it crashes. Following the crash details: Distribution: openSUSE 11.2 (i586) Gnome Release: 2.28.0 (null) (SUSE) BugBuddy Version: 2.28.0 System: Linux 2.6.31.5-0.1-default #1 SMP 2009-10-26 15:49:03 +0100 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Sonar Icon Theme: Gilouche GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Output of custom script "/usr/lib/totem/totem/totem-bugreport.py": gst-typefind-0.10 version 0.10.24 GStreamer 0.10.25 Unknown package origin Listened to a "application/x-id3" file on 2009-11-21T22:21:48 I also found a workaround to solve the issue, which is to uncheck the field "show_vfx" under apps -> totem in gconf-editor. Reproducible: Always Steps to Reproduce: 1. just try to open any audio file with the program Actual Results: Program crashes. Expected Results: Play the audio file. I found a workaround to solve the issue, which is to uncheck the field "show_vfx" under apps -> totem in gconf-editor. After this Totem does its job. -- 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 2

[Bug 557447] New: gnome-terminal: colored text corruption in less pager
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=557447 http://bugzilla.novell.com/show_bug.cgi?id=557447#c0 Summary: gnome-terminal: colored text corruption in less pager Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bphilips(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.247.0 Safari/532.5 When paging around in less on colored output like git log --color text disappears at random. Reproducible: Always Steps to Reproduce: 1) Go into a git tree 2) Run git log --color 3) Page up and down with j/k in less I couldn't reproduce in xterm. Actual Results: Some colored text turns black and black text disappears Expected Results: Text to stay the same color and not go away. If you press Ctrl + L the screen refreshes and the text comes back. -- 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 8

[Bug 556874] New: Gwibber problems
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=556874 http://bugzilla.novell.com/show_bug.cgi?id=556874#c0 Summary: Gwibber problems Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: dspolleke(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: No Gwibber [ gwibber-1.2.0+bzr358-4.1.noarch ](twitter and other microblogging client) has some strange glitches the icon in the taskbar sometimes is not scaled down to match the size of the panel Gwibber does not pop-up whan clicking ont he icon nor is it reachable via alt-tab -- 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 3

[Bug 556861] New: There is Live Install link on the desktop after nework instalation
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=556861 http://bugzilla.novell.com/show_bug.cgi?id=556861#c0 Summary: There is Live Install link on the desktop after nework instalation Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: iron.bone(a)wp.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux i686; U; pl) Presto/2.2.15 Version/10.01 After network installation the new user see on the desktop (Gnome) a link to the Live Install. When executing it the program start to install a new system like from a LiveCD - but I have never used LiveCD, I have no LiveCD. What for I need this link. Reproducible: Always Steps to Reproduce: 1. Install openSuse 11.2, internet instalation - Gnome 2. In my case I downloaded the InstallDVD, then I mounted it in public_html on a second computer. Then during the installation as repo I gave the appropriate URL on the second computer 3. After a new user login the first time (not only) and use Gnome the is on the desktop a link to Live Install -- 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 1

[Bug 556834] New: Inkscape crashes upon using the Text object tool
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=556834 http://bugzilla.novell.com/show_bug.cgi?id=556834#c0 Summary: Inkscape crashes upon using the Text object tool Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mail(a)patrick-nagel.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 Upon selecting the Text object tool and clicking into the page in order to insert text into the page, a dialog window appears, saying "Inkscape encountered an internal error and will close now." - Clicking the 'Close' button closes Inkscape. When started from a console, the following is being printed (from starting Inkscape until the crash): >inkscape (inkscape:5319): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (inkscape:5319): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated [the warning above appears many times] ** Gdk:ERROR:gdkinput-xfree.c:337:_gdk_input_grab_pointer: assertion failed: (input_window != NULL) Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. Aborted Reproducible: Always Steps to Reproduce: 1. Open Inkscape 2. Press F8 or click the Text object tool button on the left (the one with the big A) 3. Click into the page Actual Results: Inkscape crashes Expected Results: Being able to use the text object tool without a crash -- 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 7

[Bug 555959] New: keyboardlayout changes
by bugzilla_noreply＠novell.com 31 Jul '12

31 Jul '12

http://bugzilla.novell.com/show_bug.cgi?id=555959#c0 Summary: keyboardlayout changes Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: HP OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: zscherni(a)arcor.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.0.3, Ant.com Toolbar 1.1 I thought to have solved the problems I had because X.org changed some keycodes. See issues: 539135, 544573 and 551727. But new I got new troubles. After letting sleep the computer for a while, the Num-keys behave bad. 5 sometimes opens the menu (or does nothing) + and , sometimes focus the window/Frame, where the mouse-pointer stands in that moment or they select the word before the cursor or they don't anything... 0-4 and 6-9, don't do anything. Num-Lock switches the led at the keyboard but doesn't take any effekt. xev says for NumLock, 1-4 and 6-9 the right values. For they other key nothing... I don't understand at all. I did xmodmap -v -pke > .Xmodmap-what-goes-on and I saw - this file is not the same as the one (my personal .Xmodmap-mine) I loaded before. But it is also not the same as suse (gnome, x) brought with (which i had saved before xmodmap -v -pke > .Xmodmap-suse112 Also the keys are well defined there: keycode 77 = Num_Lock Pointer_EnableKeys keycode 78 = Scroll_Lock keycode 79 = KP_Home KP_7 keycode 80 = KP_Up KP_8 keycode 81 = KP_Prior KP_9 keycode 82 = KP_Subtract XF86_Prev_VMode keycode 83 = KP_Left KP_4 keycode 84 = KP_Begin KP_5 keycode 85 = KP_Right KP_6 keycode 86 = KP_Add XF86_Next_VMode keycode 87 = KP_End KP_1 keycode 88 = KP_Down KP_2 keycode 89 = KP_Next KP_3 keycode 90 = KP_Insert KP_0 keycode 91 = KP_Delete KP_Separator ( no keycode 84 = Menu ) Very strange bug. Bad behavior, which changes the xmodmap on its own. And bad behavior, which doesn't suit the xmodmap. Btw - there is another strange thing: ctrl+U (means ctrl+shift+u) works as unicode-hex-input. But I dont find, where such behavior is defined. In the gnome control-center this hotkey is NOT defined! Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 2