August 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 760420] New: Some KDE applications does not follow global font settings (font hinting)
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=760420 https://bugzilla.novell.com/show_bug.cgi?id=760420#c0 Summary: Some KDE applications does not follow global font settings (font hinting) Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: espinosa_cz(a)centrum.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 Some KDE applications have strange font. They do not respect my global font settings. They use visibly heavy hinted fonts despite I regularly set no hinting everywhere (quality of font hinting in Xorg/Freetype/Fonconfig leaves a lot to be desired, best is to stay away; I'm surprised that openSuse has it as default) My font settings are set through KDE Control Center (or however it is called now). So I guess they are defined in ~/.fonts.conf All applications (Gnome, Mozilla, ..) and most KDE4 follows my global settings, these are the few exceptions: - KSnapshot (PrintScr) - KRunner (Alt-F2), - some file pickers dialogs (Open/Save file dialog) but not all (always) but definitively those fired by (also affected) KSnapshot - System Activity (Ctrl+Esc) KDE 4.8 only, from OBS. Reproducible: Always Steps to Reproduce: 1. 2. 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.

1 2

[Bug 876277] New: Bluetooth audio device not recognized by pulseaudio
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=876277 https://bugzilla.novell.com/show_bug.cgi?id=876277#c0 Summary: Bluetooth audio device not recognized by pulseaudio Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Sound AssignedTo: tiwai(a)suse.com ReportedBy: quentin(a)links2linux.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 I have an issue with bluetooth audio. A couple of months ago when I first tried my bluetooth audio receiver (Philipps BT) everything worked out of the box. Now, probably due to one of the numerous updates, the BT device is not added to pulseaudio when it is paired. I suspect pulseaudio-module-bluetooth to be missing, but since it is the first time I dig into that issue, I am not sure if this was required back when it still worked. modprobe: FATAL: Module module-bluetooth-discover not found. Reproducible: Always Steps to Reproduce: 1. connect to paired BT device 2. check in pavucontrol: no output device added -- 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.

1 7

[Bug 883992] New: suspend to disk and memory fails
by bugzilla_noreply＠novell.com 01 Aug '14

01 Aug '14

https://bugzilla.novell.com/show_bug.cgi?id=883992 https://bugzilla.novell.com/show_bug.cgi?id=883992#c0 Summary: suspend to disk and memory fails Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: lmuelle(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Suspend to disk works but the following boot up doesn't resume. Instead it performs a normal boot. Also suspend to memory works but the following boot results in blinking caps-lock and scroll keyboard lights. -- 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.

1 4