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.
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.
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.
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.
http://bugzilla.suse.com/show_bug.cgi?id=958483
Bug ID: 958483
Summary: 3rd party application UI is not behaving as required
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: tchvatal(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
When using 3rd party module (like Virtualization) that tries to install
additional packages it at this moment works like this when you are in X
environment:
For each package there is pop-up showing progress and then this pop-up is
closed.
This causes severe issue if user runs compoziting enabled environment.
Imagine it like disco-bulb turning on and off as only on-top window is supposed
to be rendered right and all the underlying windows are greyed out.
More apps you install the more "funky" blinking you get.
Prefferable solution would be to somehow include the yast2 sw_single interface
that has the bottom progressbar and prints the installed packages.
Added value would be mostly for openSUSE, where the default DE's have enabled
compositing, but also for SLE case it would get at minimal prettier and at best
more understandable about what is happening for the installed packages.
For openSUSE it is quite commonly reported issue as I closed 3-4 during the
bugzilla cleanup mentioning this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=952799
Bug ID: 952799
Summary: bogofilter-{db,sqlite3} insists on using wordlist.tc
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: 2015*
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: gour(a)atmarama.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
In the past, when using other Linux distros I was mostly using bogofilter with
sqlite3 back-end, but after switching to openSUSE I've decided to convert to
'default' (Berkeley) DB backend.
Unfortunately, after bogofilter package was updated in openSUSE, it looks it
does insist on using $HOME/.bogofilter/wordlist.tc for the database name even
if one uses Berkeley DB or Sqlite3 back-ends?
When I try to use my old wordlist.db, Bogofilter plugin (Claws & Evolution)
starts from the scratch and creates wordlist.tc.
I wonder about this line in *.spec:
%if 0%{?suse_version} > 1320
iow. whether the new Bogofilter package is ready to use existing setup with
appropriate back-end (not equal to TokyoCabinet)?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=907495
Bug ID: 907495
Summary: adding a manual route to a dhcp configured interface
results in failed dhcp setup (wicked managed)
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: hpj(a)urpla.net
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
When adding a manual route to a dhcp configured eth interface managed by
wicked, the dhcp setup fails with a silly message:
device enp7s0 failed: "call to
org.opensuse.Network.Addrconf.ipv4.static.requestLease failed: General failure"
Add a manual route to a dhcp configured interface and restart your system.
Be prepared, that this interface will not come up correctly.
BTW: the routing editor allows selecting configured interfaces only. The usual
order is: setup interface, add route, but you have to confirm the interface
setup first, reenter yast network and add the interface based route there
after.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=938955
Bug ID: 938955
Summary: Desktop selection overridden when installing without
recommended packages.
Classification: openSUSE
Product: openSUSE Factory
Version: 201505*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Installation
Assignee: yast2-maintainers(a)suse.de
Reporter: cwh(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
Chosing not to install recommnded packages leads to a minimal installation even
without xorg and desktop environment although a desktop environment has been
selected before.
Either the patterns have to be fixed or the no-recommends option should only be
allowed for the minimal pattern.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=948370
Bug ID: 948370
Summary: One-Click-Installer YMP file cannot match group
section for Tumbleweed
Classification: openSUSE
Product: openSUSE Factory
Version: 2015*
Hardware: Other
OS: openSUSE 13.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: tgoettlicher(a)suse.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101
Firefox/39.0
Build Identifier:
One-Click-Installer YMP files can contain sections for different distribution
versions, e.g.:
<group distversion="openSUSE 13.2">
You can match against a specific Tumbleweed build:
<group distversion="openSUSE 20150924">
But it's not possible to match for Tumbleweed in general because the version of
Tumbleweed changes with every build.
Can the one-click-installer be extended to not only match against the version
but also against the codename?
For example:
<group distcodename="openSUSE Tumbleweed">
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=930110
Bug ID: 930110
Summary: yast ncurses menus not properly formatted for
tumbleweed ppc64 guest install
Classification: openSUSE
Product: openSUSE Factory
Version: 201503*
Hardware: PowerPC-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: normand(a)linux.vnet.ibm.com
QA Contact: jsrain(a)suse.com
Found By: ---
Blocker: ---
yast ncurses menus not properly formatted for tumbleweed ppc64 guest install
Detailed flow:
* On a Power KVM host I defined a libvirt twppc64.xml
using the Tumbleweed-BE-DVD-ppc64-Snapshot20150505-Media.iso
retrieved from https://openqa.opensuse.org/tests/60778/asset/3110
* from a ssh session to the PowerKVM I started a screen window
from which I started the ppc64 guest.
===
virsh define twppc64.xml
virsh start --console twppc64
===
* I captured successively the ncurses menus and did a
yast2_ncurse_bad_format.tgz tarball with all those png files.
* The first problem is that the text is not properly aligned
eg: yast2_img1_installation.png
* The 2nd problem is that some characters from previous menu
are not cleaned up when new menu is presented.
eg: yast2_img4_installation_option.png
* The third problem is popup window hardly visible
eg: yast2_img9_confirm_password.png
--
You are receiving this mail because:
You are on the CC list for the bug.