openSUSE Bugs August 2016

bugs@lists.opensuse.org

1 participants
3311 discussions

[Bug 952198] New: django-admin does not work, django-admin.py does
by bugzilla_noreply＠novell.com 20 Mar '23

20 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=952198 Bug ID: 952198 Summary: django-admin does not work, django-admin.py does Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: o.kurz(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- observation: The django tutorial https://docs.djangoproject.com/en/1.8/intro/tutorial01/ suggests to use the tool "django-admin" with django >= v1.7 which is also available in Leap but does not work. "django-admin.py" also exists and works ok. steps to reproduce: - "zypper in python-Django python-sqlite" # confirm uninstallation of blocker package - "django-admin startproject mysite" - observe error with python traceback problem: unknown so far. Is ist maybe related that python-Django (still) uses python2? workaround: - Use django-admin.py which works flawlessly, e.g. example project can be configured and run: "django-admin.py startproject mysite && python manage.py migrate && python manage.py runserver", connect with webbrowser to http://localhost:8000. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 980292] New: Yast shouldn't allow running two instances of module at once
by bugzilla_noreply＠novell.com 08 Mar '23

08 Mar '23

http://bugzilla.suse.com/show_bug.cgi?id=980292 Bug ID: 980292 Summary: Yast shouldn't allow running two instances of module at once Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's very easy to mistakenly double click on a module icon in Yast2, causing two instances of the module to be started, and there's absolutely no point in using more than one instance of any yast module. Please disallow double click on yast2, and prevent more than one instance of module to be started. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 976384] New: Qt-Creator Documentation is not found out-of-the-box
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=976384 Bug ID: 976384 Summary: Qt-Creator Documentation is not found out-of-the-box Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: VMWare OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gorgoglione(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In Qt-Creator 3.6.0, selecting Help -> Contents from menu, the following error message is displayed: The page could not be found Error loading: qthelp://org.qt-project.qtcreator.360/doc/index.html Check that you have the corresponding documentation set installed. Probably the documentation it's not installed into the default folder and Qt-Creator configuration was not updated to point to the right location. The fix which worked for me was to select Tools -> Options... -> Help -> Documentation -> Add, and select the following file: /usr/share/doc/packages/libqt5/qtcreator.qch -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 972678] New: KDE:Qt/python-pyside: Bug - Installation of this breaks software "opensesame"
by bugzilla_noreply＠novell.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=972678 Bug ID: 972678 Summary: KDE:Qt/python-pyside: Bug - Installation of this breaks software "opensesame" Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: dmueller(a)suse.com Reporter: patrickmurphy221(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- - Overview Tumbleweed zypper dup requests installation of python-pyside, but installing it breaks the program "opensesame". - More detail Installed OpenSUSE Tumbleweed (snapshot 2016-03-18). Installed package "opensesame" (psychology experiment builder, homepage: http://osdoc.cogsci.nl/) from OpenSUSE Science repository (https://build.opensuse.org/project/show/science). It works fine. When I do a "zypper dup" (March 23rd or 24th), the package "python-pyside" is installed (requested by the distribution; not a dependency of opensesame) and it breaks opensesame. Trying to run opensesame gives this error instead of launching the program: python: siplib.c:8551: sip_api_can_convert_to_type: Assertion `td == ((void *)0) || (((td)->td_flags & 0x0007) == 0x0000) || (((td)->td_flags & 0x0007) == 0x0002)' failed. Aborted (core dumped) Uninstalling python-pyside makes opensesame work again (but "zypper dup" continues to request that I install python-pyside). This does not seem to be specific to the OpenSUSE Science repository, since downloading the opensesame python source from its official website and running that gives the exact same result. - To reproduce 1. Install opensesame, from OpenSUSE Science repo or from source. 2. Install python-pyside (as requested by zypper dup). Reversing the order has same effect. Happens on Tumbleweed. In the past I've run opensesame on Leap without problems, but I don't think it ever requested installation of python-pyside, so breakage would not be expected. (First time submitting a bug; apologies if I didn't include the right detail or use the right format.) -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 987114] New: Bluetooth headset connected but not showing under 'Sound Settings'
by bugzilla_noreply＠novell.com 16 Nov '22

16 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Bug ID: 987114 Summary: Bluetooth headset connected but not showing under 'Sound Settings' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: damien.lloyd21(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: On openSUSE Tumbleweed, my bluetooth headset pairs and connects successfully through GNOME's bluetooth interface, but after going to the 'Sound Settings' my bluetooth headset doesn't show up, even though it is paired up. Because I can't see my bluetooth headset under 'Sound Settings' it's not possible to re-route sound through it, which means I can't use my bluetooth headset. Reproducible: Always Steps to Reproduce: 1. Make bluetooth headset discoverable; 2. Open up GNOME's bluetooth interface and select bluetooth headset; 3. Connect to bluetooth headset; 4. Once paired, access 'Sound Settings': bluetooth headset doesn't show up. Actual Results: The bluetooth headset doesn't show up under 'Sound Settings' even though it is connected and paired. Expected Results: The bluetooth headset should appear under 'Sound Settings' so that sound can be re-routed through it. My headset is a UE MEGABOOM and it worked under Ubuntu 14.04/16.04 extremely well. It doesn't work under openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 993011] New: [openQA] CTRL-ALT-DEL does not show the logout dialog
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=993011 Bug ID: 993011 Summary: [openQA] CTRL-ALT-DEL does not show the logout dialog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Seen by openQA tests, e.g. https://openqa.opensuse.org/tests/239654 After the system was upgraded from openSUSE 13.2 to Tumbleweed (20160808, first to have plasma 5.7.2), the logout dialog no longer shows when pressing ctrl-alt-del This appears on updates performed using the DVD and boot from the Network CD, but seems not to happen in the case when the system was updated using zdup. The tests had been re-run a couple times. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 941884] New: libcamgm fails test suite due to expired certificates
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=941884 Bug ID: 941884 Summary: libcamgm fails test suite due to expired certificates Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- since recently, libcamgm no longer passes the test suite... the build lo ends with: [...] [ 358s] Running ListTest... [ 358s] Output doesn't match expected data: [ 358s] --- ./single.out/ListTest.out 2014-04-12 17:19:43.000000000 +0000 [ 358s] +++ ./single.out/out/ListTest.out 2015-08-16 18:11:50.226671071 +0000 [ 358s] @@ -125,7 +125,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 07 [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] New Entry [ 358s] certificate = 08:40717a16174dc4d516f6fa7ee8eeb18c-1124792802 [ 358s] commonName = Full Test Certificate [ 358s] @@ -153,7 +153,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 0B [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] getCertificateList successfully executed [ 358s] =================== end List tests ======================== [ 358s] DONE [ 358s] FAIL: ListTest [...] [ 364s] Running VerifyTest... [ 365s] Output doesn't match expected data: [ 365s] --- ./single.out/VerifyTest.out 2014-04-12 17:19:43.000000000 +0000 [ 365s] +++ ./single.out/out/VerifyTest.out 2015-08-16 18:11:57.086773026 +0000 [ 365s] @@ -6,10 +6,10 @@ [ 365s] 04: Verify failed: Found revoked certificate [ 365s] 05: Verify failed: Found revoked certificate [ 365s] 06: Verify failed: Found revoked certificate [ 365s] -07: Verify success [ 365s] +07: Verify failed: Found expired certificate [ 365s] 08: Verify failed: Found expired certificate [ 365s] 09: Verify failed: Found revoked certificate [ 365s] 0A: Verify failed: Found expired certificate [ 365s] -0B: Verify success [ 365s] +0B: Verify failed: Found expired certificate [ 365s] =================== end List tests ======================== [ 365s] DONE [ 365s] FAIL: VerifyTest [...] libcamgm is a dependency to yast2-ca-management, which in turn is required by yast2-auth-server (which is why a delete request for libcamgm back in May could not be fullfilled) This whole thing is a ring, packae, causing all stagings to fail, hence I mark it major -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 971006] New: rpmlint: no-dependency-on perl-base 5.22.1
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=971006 Bug ID: 971006 Summary: rpmlint: no-dependency-on perl-base 5.22.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpmlint does not understand how openSUSE specifies perl dependencies and falsly reports: no-dependency-on perl-base 5.22.1 in openSUSE, we use the macro %perl_requires which translates to: Requires: perl(:MODULE_COMPAT_5.22.1) It would be great to get this recognized as dependency being satisfied -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 920901] New: USB mouse disconnects every 60 seconds without X
by bugzilla_noreply＠novell.com 11 Oct '22

11 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=920901 Bug ID: 920901 Summary: USB mouse disconnects every 60 seconds without X Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: oneukum(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some mice need X to run or will disconnects and reconnect every 60 seconds. The fix is a new quirk to always poll. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs August 2016