August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 770239] New: 'zypper pa' lacks support for @System repo
by bugzilla_noreply＠novell.com 12 Aug '17

12 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=770239 https://bugzilla.novell.com/show_bug.cgi?id=770239#c0 Summary: 'zypper pa' lacks support for @System repo Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: ma(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- ma@fibonacci:~ (0) $ zypper pa -i -R|grep libclucene-core0_9_23 ma@fibonacci:~ (1) $ zypper pa -R|grep libclucene-core0_9_23 ma@fibonacci:~ (1) $ zypper info libclucene-core0_9_23 Loading repository data... Reading installed packages... Information for package libclucene-core0_9_23: Repository: @System Name: libclucene-core0_9_23 ... ma@fibonacci:~ (0) $ zypper pa @System Repository '@System' not found by its alias, number, or URI. Use 'zypper repos' to get the list of defined repositories. --- In this case libclucene-core0_9_23 is orphaned (installed but not avaliable in any repo). 'pa' is a kind of search and search should support something like '-r @System'. -- 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 900841] New: Foobnix segmentation fault at startup
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900841 Bug ID: 900841 Summary: Foobnix segmentation fault at startup Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: PC OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: whoknows2012(a)myopera.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Can not start Foobnix program. Output from program in terminal emulator: ** Message: pygobject_register_sinkfunc is deprecated (GstObject) start program Segmentation fault dima@linux-fivg:~$ java version "1.7.0_51" OpenJDK Runtime Environment (IcedTea 2.4.4) (suse-24.13.5-x86_64) OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) After this output nothing happens & I am pressing Ctrl + C key combination. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 912903] New: python3-requests crashes with https
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=912903 Bug ID: 912903 Summary: python3-requests crashes with https Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: jnweiger(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reproduce ---------- python3 >>> import requests # using python3-requests-2.4.1-17.3.noarch >>> r = requests.get('https://owncloud.com') # produces a stack trace saying '[Errno 21] Is A Directory' multiple times, but does not mention the path name it tried. Traceback (most recent call last): File "/usr/lib/python3.3/site-packages/requests/packages/urllib3/util/ssl_.py", line 114, in ssl_wrap_socket context.load_verify_locations(ca_certs) IsADirectoryError: [Errno 21] Is a directory .... Workaround ---------- >>> verify='/etc/ssl/ca-bundle.pem' >>> if not os.path.exists(verify): verify='/etc/ssl/certs/ca-certificates.crt' # seen in https://urllib3.readthedocs.org/en/latest/security.html >>> if not os.path.exists(verify): verify=True # default, but fails on python3(a)openSUSE-13.1 with DEFAULT_CA_BUNDLE_PATH=/etc/ssl/cersts/ >>> requests.get(url, verify=verify) <Response [200]> # works fine. # Maybe DEFAULT_CA_BUNDLE_PATH should have been '/etc/ssl/ca-bundle.pem' instead? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 904316] New: Python PIP should use the 2.7.8 and not the 3.x one!
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904316 Bug ID: 904316 Summary: Python PIP should use the 2.7.8 and not the 3.x one! Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: abdelouahab_al(a)yahoo.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2125.111 Safari/537.36 Build Identifier: Installed Python by the default one, if i run python in console, i get the 2.7.8, but if i use pip install some_module it uses python 3 solution, because setuptools uses the 3 and not 2.7 one! already posted it here https://forums.opensuse.org/showthread.php/502235-Python-2-7-is-the-default… Reproducible: Always Steps to Reproduce: 1.run pip install a module 2.uses the python 3 3.cant compile python 2 Actual Results: delete setuptools and installed it manually, and reinstalled pip manually, now everything is used with python 2. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 903628] New: plymouth-set-default-theme -R : variable THEME_NAME not allocated
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903628 Bug ID: 903628 Summary: plymouth-set-default-theme -R : variable THEME_NAME not allocated Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: i686 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mathias.froehlich(a)f-i.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Overview: # sh -x plymouth-set-default-theme -R + set -e + '[' -z '' ']' + PLYMOUTH_LIBEXECDIR=/usr/lib + '[' -z '' ']' + PLYMOUTH_DATADIR=/usr/share + '[' -z '' ']' + PLYMOUTH_CONFDIR=/etc/plymouth/ + '[' -z '' ']' + PLYMOUTH_POLICYDIR=/usr/share/plymouth/ + '[' -z '' ']' + '[' -z '' ']' ++ plymouth --get-splash-plugin-path + PLYMOUTH_PLUGIN_PATH=/usr/lib/plymouth/ + DO_RESET=0 + DO_INITRD_REBUILD=0 + DO_LIST=0 + DO_HELP=0 + THEME_NAME= + '[' 1 -gt 0 ']' + case "$1" in + DO_INITRD_REBUILD=1 + shift + '[' 0 -gt 0 ']' + '[' 0 -eq 1 ']' + '[' 0 -ne 0 ']' + '[' 0 -eq 0 ']' + '[' 1 -eq 0 ']' ++ id -u + '[' 0 -ne 0 ']' + '[' 0 -ne 0 ']' + '[' '!' -e /usr/share/plymouth/themes//.plymouth ']' + echo '/usr/share/plymouth/themes//.plymouth does not exist' /usr/share/plymouth/themes//.plymouth does not exist + exit 1 Steps to Reproduce: plymouth-set-default-theme -R Actual Results: No new initrd is built. Expected Results: initrd should build with selected plymouth theme Build Date & Hardware: NAME=openSUSE VERSION="13.2 (Harlequin)" VERSION_ID="13.2" PRETTY_NAME="openSUSE 13.2 (Harlequin) (i586)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:13.2" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" Linux hostname 3.16.6-2-desktop #1 SMP PREEMPT Mon Oct 20 13:47:22 UTC 2014 (feb42ea) i686 i686 i386 GNU/Linux I found a workaround by editing the script directly to call the correct function when passing the -R parameter: -R|--rebuild-initrd) get_default_theme DO_INITRD_REBUILD=1 ;; -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 903543] New: systemd kadmind.service missing openldap dependency
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903543 Bug ID: 903543 Summary: systemd kadmind.service missing openldap dependency Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: gleixner(a)lrz.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- If you configure auth-server via yast2 and herein kerberos using ldap as storage (default), then kadmind.service fails to start on next reboot: systemctl -l status kadmind.service kadmind.service - Kerberos 5 Password-changing and Administration Loaded: loaded (/usr/lib/systemd/system/kadmind.service; enabled) Active: failed (Result: exit-code) since Sat 2014-11-01 09:38:21 CET; 1h 5min ago Process: 1035 ExecStart=/usr/lib/mit/sbin/kadmind -P /var/run/kadmind.pid $KADMIND_ARGS (code=exited, status=1/FAILURE) Nov 01 09:38:21 opensuse132beta kadmind[1035]: kadmind: Cannot bind to LDAP server 'ldapi://' as 'cn=Administrator,dc=kerberos,dc=test': Can't contact LDAP server while initializing, aborting The service should also depend on slapd.service as krb5kdc.service does: # grep slap /usr/lib/systemd/system/krb5kdc.service After=network.target slapd.service # grep After /usr/lib/systemd/system/kadmind.service After=network.target -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 902582] New: Firefox fails to connect when launched before Internet connection is up
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902582 Bug ID: 902582 Summary: Firefox fails to connect when launched before Internet connection is up Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I have noticed that if I launch Firefox before my network connection is up (NetworkManager WiFI connection), it will fail to connect even after the network comes up. The only way to make it connect is by closing all instances and restarting Firefox. Thanks for looking into this! -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 902407] New: system-config-printer can't find driver, doesn't offer manual selection
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902407 Bug ID: 902407 Summary: system-config-printer can't find driver, doesn't offer manual selection Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: sb56637(a)gmail.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- Hi there, In view of bug 889187, I tried to add a network printer via dnssd with system-config-printer. It does find the printer, but under KDE some kind of "helper" screen (apper related maybe?) appears with an error. (See attachment #1) Then, after dismissing the error, system-config-printer gets stuck at "searching for drivers". (See attachment #2) At this point, it gets stuck. I have let it sit there for 5 minutes on a very fast computer, and I have very few drivers installed (no Gutenprint or HPLIP) so it definitely should not be searching for long. I believe that an internal python process is crashing, as the terminal spits out this error when it starts searching for drivers: ---------------------- ERROR:dbus.proxies:Introspect error on :1.344:/org/freedesktop/PackageKit: dbus.exceptions.IntrospectionParserException: Error parsing introspect data: <class 'xml.parsers.expat.ExpatError'>: unbound prefix: line 5, column 4 HTTP Status 403 None Exception in thread Thread-3: Traceback (most recent call last): File "/usr/lib64/python2.7/threading.py", line 810, in __bootstrap_inner self.run() File "/usr/lib/python2.7/site-packages/cupshelpers/openprinting.py", line 54, in run self.callback (403, self.user_data, None) File "/usr/lib/python2.7/site-packages/cupshelpers/openprinting.py", line 163, in parse_result callback (status, user_data, result) File "/usr/share/system-config-printer/newprinter.py", line 3267, in openprinting_printers_found print traceback.extract_tb(printers[2], limit=None) TypeError: 'NoneType' object has no attribute '__getitem__' ---------------------- I don't really care if it finds the correct driver or not, as long as it lets me manually select my correct driver, which I can't do. When running system-config-printer as root in IceWM, the KDE "helper" error dialog doesn't appear. But it still gets stuck on "searching for drivers". Thanks for looking into this! -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 902382] New: Booting with Plymouth puts first user on vt:8
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902382 Bug ID: 902382 Summary: Booting with Plymouth puts first user on vt:8 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: s.parry316(a)btinternet.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I had some problems when using switch user in KDE4. Some investigation shows that I (first user) was at vt:8 instead of the default vt:7. When I logged in as another KDE user, I found that she was at vt:7.... On the forums, a more expert user suggested that Plymouth may be the cause, so I booted with plymouth.enable=0 and sure enough, the 'seats' were allocated as normal. Here is the thread: https://forums.opensuse.org/showthread.php/501821-Switch-user-When-did-this… here is a (I hope) relevant snippet booted as normal: linux:~ # cat /var/log/Xorg.0.log |grep -C 5 "VT" [ 6.174] (II) Module nvidia: vendor="NVIDIA Corporation" [ 6.174] compiled for 4.0.2, module version = 1.0.0 [ 6.174] Module class: X.Org Video Driver [ 6.177] (II) NVIDIA dlloader X Driver 304.123 Wed Jul 2 11:01:29 PDT 2014 [ 6.177] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 6.178] (++) using VT number 8 [ 6.186] (II) Loading sub module "fb" [ 6.186] (II) LoadModule: "fb" [ 6.187] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 6.193] (II) Module fb: vendor="X.Org Foundation" Here is the whole Xorg.0.log http://paste.opensuse.org/52414761 And here the snippet booted with plymouth.enable=0 linux:~ # cat /var/log/Xorg.0.log |grep -C 5 "VT" [ 1194.446] (II) Module nvidia: vendor="NVIDIA Corporation" [ 1194.446] compiled for 4.0.2, module version = 1.0.0 [ 1194.446] Module class: X.Org Video Driver [ 1194.446] (II) NVIDIA dlloader X Driver 304.123 Wed Jul 2 11:01:29 PDT 2014 [ 1194.446] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 1194.446] (++) using VT number 7 [ 1194.453] (II) Loading sub module "fb" [ 1194.453] (II) LoadModule: "fb" [ 1194.453] (II) Loading /usr/lib64/xorg/modules/libfb.so [ 1194.454] (II) Module fb: vendor="X.Org Foundation" And the whole log: http://paste.opensuse.org/75391735 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 908258] New: Xfwm > 1px wide xpms are transparent
by bugzilla_noreply＠novell.com 11 Aug '17

11 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908258 Bug ID: 908258 Summary: Xfwm > 1px wide xpms are transparent Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: punx665(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 615811 --> http://bugzilla.opensuse.org/attachment.cgi?id=615811&action=edit opensuse 13.2 as guest, Debian testing as host same xfwm theme If a xfwm theme contains 1px wide and height XPMs the window decoration becomes unusable and transparent you can also see ths on the "default" xfwm theme (side borders missing) or this one ( https://github.com/sixsixfive/themes/tree/master/Glare )which is used in the screenshots -- You are receiving this mail because: You are on the CC list for the bug.

1 7