https://bugzilla.novell.com/show_bug.cgi?id=861081https://bugzilla.novell.com/show_bug.cgi?id=861081#c0
Summary: blas-devel symlinks libblas.so -> libblas.so.3.4.2 ,
rendering update-alternatives useless. Also for
lapack-devel.
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Development
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: asmunder(a)stud.ntnu.no
QAContact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101
Firefox/21.0
When blas-devel is installed or upgraded, it creates a symlink
libblas.so -> libblas.so.3.4.2 (or similar).
This does not play nice with update-alternatives, which expects
libblas.so -> libblas.so.3
so that update-alternatives can change what libblas.so.3 points to.
Please fix blas-devel to play nicely with other blas versions (e.g. openblas
from the Science repo).
The same is valid for lapack-devel. Please also fix lapack-devel.
Reproducible: Always
Steps to Reproduce:
1. Install blas-devel
2. Install openblas-devel from the Science repo
3. Use update-alternatives --config libblas.so.3 to change which BLAS is used
Actual Results:
libblas.so still links to the version from blas-devel, no matter what I specify
using update-alternatives.
Expected Results:
libblas.so should link to the version I specified with update-alternatives
--
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=885406https://bugzilla.novell.com/show_bug.cgi?id=885406#c0
Summary: KDE:Extra/luminance-hdr: runtime dependency:
libqt5-sql-sqlite
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Platform: x86-64
OS/Version: openSUSE 13.1
Status: NEW
Severity: Minor
Priority: P5 - None
Component: 3rd party software
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: rickscafe.casablanca(a)gmx.net
QAContact: opensuse-communityscreening(a)forge.provo.novell.com
Found By: ---
Blocker: ---
luminance-hdr offers storing of tonemapping settings in sqlite DB. After
installation of luminance-hdr rpm, a push to the "DB save" button fails
silently because qt5-sqlite driver is not loaded.
Could libqt5-sql-sqlite be added to luminance-hdr Requires?
On the other hand, luminance-hdr pulled qt5 libraries and that in turn
installed libqt5-sql-mysql but not libqt5-sql-sqlite. One could argue that qt5
should install either none or both. The latter is because sqlite has become
kind of default with mysql being the first "upgrade" option, if one wants to
use a full scale RDBMS. Not me though, I prefer pg ;-)
--
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=885402https://bugzilla.novell.com/show_bug.cgi?id=885402#c0
Summary: Connecting a galaxy note 3 results in 6 entries in
KDE's device manager
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: 64bit
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Workspace
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: grueni75(a)web.de
QAContact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created an attachment (id=596965)
--> (http://bugzilla.novell.com/attachment.cgi?id=596965)
Screenshot showing several entries of single Galaxay Note 3 device
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101
Firefox/30.0
KDE's device manager (Geräteüberwachung) shows 6 entries for the same device
(Galaxy Note 3). Five of them are named media player (Tragbarer Medienspieler).
One is named "SAMSUNG_Android". In my previous installation (Opensuse 12.2),
only one entry (SAMSUNG_Android) was shown.
Reproducible: Always
Steps to Reproduce:
1. Connect samsung galaxy note 3 via usb
2. Check entries in device manager of KDE
Actual Results:
The device is listed several times
Expected Results:
The device is listed only once
--
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=861976https://bugzilla.novell.com/show_bug.cgi?id=861976#c0
Summary: "When battery power is critical" in
gnome-control-center, "Power" does not allow changes
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: gp(a)suse.com
QAContact: qa-bugs(a)suse.de
CC: fcrozat(a)suse.com
Found By: ---
Blocker: ---
Created an attachment (id=577012)
--> (http://bugzilla.novell.com/attachment.cgi?id=577012)
Screenshot
Unlike "Automatic suspend", the field "When battery power is critical"
does not allow changing its value but is hard coded to "Power Off".
This is a regression from earlier versions. I do want to make that
"Suspend to Disk"/"Hibernate", and the GUI should offer this configuration.
See the attached screenshot.
--
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=858101https://bugzilla.novell.com/show_bug.cgi?id=858101#c0
Summary: Vinagre can't connect to Win 7 VM
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Platform: HP
OS/Version: openSUSE 13.1
Status: NEW
Severity: Major
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: sthompson(a)barrday.com
QAContact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/32.0.1700.68 Safari/537.36
Starting vinagre from the command line, I get the following when trying to
connect to a Win 7 VM:
sthompson@cam-it-l-suse13:~> vinagre
connected to cam-vmi-win7.barrday.com:3389
creating directory /home/BARRDAY/sthompson/.freerdp/certs
Password:
Certificate details:
Subject: CN = cam-vmi-win7.barrday.com
Issuer: CN = cam-vmi-win7.barrday.com
Thumbprint: 4f:ab:7c:e7:cb:3c:85:6e:a1:22:5e:c4:2f:30:7e:01:9d:4a:06
The above X.509 certificate could not be verified, possibly because you do not
have the CA certificate in your certificate store, or the certificate has
expired. Please look at the documentation on how to create local certificate
store for a private CA.
Do you trust the above certificate? (Y/N)
Error: Could not read answer from stdin.
SSL_write: Failure in SSL library (protocol error?)
Authentication failure, check credentials.
If credentials are valid, the NTLMSSP implementation may be to blame.
Reproducible: Always
Steps to Reproduce:
1. Open Remote Desktop
2. Setup connection
3. Try to connect
Actual Results:
I received the error indicated above.
Expected Results:
Should have connected to the RDP session.
--
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=878255https://bugzilla.novell.com/show_bug.cgi?id=878255#c0
Summary: rpm: %restart_on_update only works for init scripts
Classification: openSUSE
Product: openSUSE Factory
Version: 13.2 Milestone 0
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: mls(a)suse.com
ReportedBy: lnussel(a)suse.com
QAContact: qa-bugs(a)suse.de
CC: ro(a)suse.com
Found By: ---
Blocker: ---
%restart_on_update calls /etc/init.d/$service try-restart, therefore only works
for init scripts.
It should call /usr/bin/systemctl try-restart $service instead.
--
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=844043https://bugzilla.novell.com/show_bug.cgi?id=844043#c0
Summary: YaST2 "Software Management" Module simply closes after
refreshing the repositories
Classification: openSUSE
Product: openSUSE Factory
Version: 13.1 Beta 1
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: Antoine.Saroufim(a)gmail.com
QAContact: jsrain(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/538.1 (KHTML,
like Gecko) Chromium/25.0.1349.2 Chrome/25.0.1349.2 Safari/538.1 SUSE/13.1
(3.10.0) Epiphany/3.10.0
Launching the "Software Management" Module would cause YaST2 (GTK) to close
(without any displayed errors) after refreshing the repositories.
Reproducible: Always
Steps to Reproduce:
1.launch YaST2
2.navigate to "Software Management"
3.Wait for the repositories to refresh
Actual Results:
"Software Management" closes after refreshing the software
Expected Results:
The Software Management window to opened.
Two instances of the Software Management module are launched with a single
click. One of them refreshes the repositories and the other returns an error
stating that zypper is in use.
--
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=885253https://bugzilla.novell.com/show_bug.cgi?id=885253#c0
Summary: FATE: Release Notes "Challenge" cannot be added if
initially left empty
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: openFATE
AssignedTo: tschmidt(a)suse.com
ReportedBy: tstaudt(a)de.ibm.com
QAContact: roland.haidl(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101
Firefox/24.0
Release Notes "Challenge" cannot be added if initially left empty.
A workaround is to delete everything and add all 3 fields at once, but that's
ugly.
I haven't checked if the same happens when a different field is left empty.
Reproducible: Always
Steps to Reproduce:
Steps to reproduce:
1. "Add release notes" only filling out "Title" and "Solution"
2. Save changes
3. "Edit release notes"
4. Add something to "Challenge"
5. Save changes => internal error
Actual Results:
Internal Error => " Saving Feature #315337 failed due to an internal error. The
development team has been notified."
Expected Results:
Successful update
--
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=875098https://bugzilla.novell.com/show_bug.cgi?id=875098#c0
Summary: Yast Services Manager does not list proper targets for
"default system target" dropdown
Classification: openSUSE
Product: openSUSE Factory
Version: 13.2 Milestone 0
Platform: Other
OS/Version: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: yast2-maintainers(a)suse.de
ReportedBy: mark_buell(a)yahoo.com
QAContact: jsrain(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:28.0) Gecko/20100101
Firefox/28.0
OS and hardware: openSUSE Factory (Bottle) (armv6hl) - raspberrypi
YaST ncurses version.
Services Manager module has "default system target" dropdown box at the top of
the Services Manager window. A choice is mandated. The only available targets
(in the dropdown) on this installation are
halt
kexec
poweroff
reboot
Remote File Systems
Rescue Mode
runlevel0
runlevel1
runlevel6
And I don't want any of those targets as my system default!
Command line
systemctl list-units --type target
results:
UNIT LOAD ACTIVE SUB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User System
network.target loaded active active Network
nss-lookup.target loaded active active Host and Network Name Lookups
paths.target loaded active active Paths
remote-fs-pre.target loaded active active Remote File Systems (Pre)
remote-fs.target loaded active active Remote File Systems
rpcbind.target loaded active active RPC Port Mapper
slices.target loaded active active Slices
sockets.target loaded active active Sockets
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
time-sync.target loaded active active System Time Synchronized
timers.target loaded active active Timers
So, I know the system has a more normal choice of available targets.
I copied multi-user.target to /etc/systemd/system, in case the dropdown reads
that dir to locate available targets. Dropdown did not change.
I change the default using command line "systemctl" (to multi-user). It creates
a symlink appropriately. This action DOES change the contents of the dropbox,
as my default is now shown correctly.
So, it looks like a bug to me.
Reproducible: Always
Steps to Reproduce:
1. As root, open ncurses yast.
2. Navigate to <System><Services Manager>
3. Observer "default system target" dropdown.
--
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.