February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 952324] [libsolv] nothing provides appdata(Thunar.appdata.xml) needed by application:Thunar File Manager-.noarch
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.novell.com/show_bug.cgi?id=952324 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:4649:moderate |obs:running:4649:moderate | |obs:running:4650:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 912062] New: freetype2 should use harfbuzz and enable bz2 compressions
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=912062 Bug ID: 912062 Summary: freetype2 should use harfbuzz and enable bz2 compressions Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: nadvornik(a)suse.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de CC: pgajdos(a)suse.com Found By: --- Blocker: --- As per subj we should enable hb and bz2 compressions in freetype2. Problem is that we also need to avoid build cycles so there is need for bootstrap package... :/ -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 952324] [libsolv] nothing provides appdata(Thunar.appdata.xml) needed by application:Thunar File Manager-.noarch
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.novell.com/show_bug.cgi?id=952324 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:4650:moderate |obs:running:4649:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 962214] hugin appdata
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.novell.com/show_bug.cgi?id=962214 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:4649:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 952324] [libsolv] nothing provides appdata(Thunar.appdata.xml) needed by application:Thunar File Manager-.noarch
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.novell.com/show_bug.cgi?id=952324 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |obs:running:4650:moderate -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 964548] VUL-1: KDE lockscreen bypass by switching display off and on
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=964548 http://bugzilla.opensuse.org/show_bug.cgi?id=964548#c21 --- Comment #21 from Martin Gräßlin <kde(a)martin-graesslin.com> --- (In reply to Lorenzo Desole from comment #20) > (In reply to Martin Gräßlin from comment #19) > > (In reply to Lorenzo Desole from comment #18) > > > Would it make sense, when there are no more screens, to exit > > > kscreenlocker_greet with exit value == 1, to notify that a valid log-in > > > didn't take place? > > > > No, that's kind of a useless information in that case. Assuming we would do > > so, it would result in KSlD restarting the greeter which would exit again > > with 1, because there are no screens. Resulting in either a restart loop or > > in the emergency window being shown. > > Not if the pre-condition is "there was a screen, now it's been removed, > there are no screens left". sorry, but that's totally useless information for KSld. It doesn't need to know about it and it's also a not needed information in future. With Qt 5.6 we will get proper dummy QScreens in case there is no screen and on Wayland, well KWin is not so stupid as to remove the last screen ;-) Anyway concerning the issue: upstream security team is involved now. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 960577] New: LO5: Creating, saving ODS then exiting LO5 locks Plasma 5
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=960577 Bug ID: 960577 Summary: LO5: Creating, saving ODS then exiting LO5 locks Plasma 5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: LibreOffice Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomi.schmid(a)swissonline.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am running Leap 42.1 on my PC, updated from openSuSE 13.2. When I try to use Libre Office 5 (5.0.2.2-1.2), in 90% of the cases when I manage and save a Calc-File, the whole Plasma 5 desktop locks up when I either a) close the file or b) close the file and exit Libre Office. I can move the mouse, but klicking has no effect and I cannot change workspaces using the mouse. However, I can switch to console by CTRL-ALT-F1, but there is in case b) nothing to see or in case a) a soffice.bin process in status "Z". I have to reboot the PC or do a "init 3/init 5" sequence to be able to use the Plasma 5 DE again. The process is very simple: 1) Login into SDDM, Plasma 5 desktop appears. No other GUI application is running. 2) Click on the openSuSE-provided "Office" icon on the desktop, LO5 opens. 3) Create a new calc-file, enter a bit of text into the first cell (Test"), save the calc file as "ODS" in my home directory 4) Close the file: In above case a) at this point the whole Plasma 5 DE locks up 5) Close the file, then exit LO5: In above case b) at this point the whole Plasma 5 DE locks up I ran "libreoffice" (the program the "Office" icon actually starts) with strace, but to my (uneducated) eyes there is nothing bad to see. Strace attached, as well as a "ps auxw" *after* such a lockup. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 854884] New: system crash after update opensuse-2013-954, opensuse-2013-956, opensuse-2013-957
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=854884 https://bugzilla.novell.com/show_bug.cgi?id=854884#c0 Summary: system crash after update opensuse-2013-954, opensuse-2013-956, opensuse-2013-957 Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gopitzohlsen(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 After the update KDE is not working. When I reboot the system crashes. 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 73

[Bug 963721] New: snapper: The command 'True' could not be found
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

http://bugzilla.opensuse.org/show_bug.cgi?id=963721 Bug ID: 963721 Summary: snapper: The command 'True' could not be found Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: axel.braun(a)gmx.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After the installation of some ATI drivers f***'ed up the system I tried to boot into a snapshot: Selected the snapshot, the hint 'If OK, run 'snapper Rollback' appeared, and then: Der Befehl 'True' konnte nicht gefunden werden (The command 'true' could not be found) No boot into snapshot possible. I tried various snapshots, all same result -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 841544] New: Long delay on shutdown stopping User Manager for 0
by bugzilla_noreply＠novell.com 08 Feb '16

08 Feb '16

https://bugzilla.novell.com/show_bug.cgi?id=841544 https://bugzilla.novell.com/show_bug.cgi?id=841544#c0 Summary: Long delay on shutdown stopping User Manager for 0 Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: arvidjaar(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 In beta 1 every shutdown waits for timeout stopping user manager: [ OK ] Stopped LSB: Configure network interfaces and set up routing. Stopping SuSEfirewall2 phase 1... [ OK ] Stopped SuSEfirewall2 phase 1. [ *] A stop job is running for User Manager for 0 This is VM in qemu KVM, minimal text only installation. 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 22