November 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 931513] New: gnome-shell segfault when no display is connected
by bugzilla_noreply＠novell.com 18 Sep '17

18 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=931513 Bug ID: 931513 Summary: gnome-shell segfault when no display is connected Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 634735 --> http://bugzilla.opensuse.org/attachment.cgi?id=634735&action=edit coredumpctl gdb 2613 when is set as default display manager, computer is restarted and display is not connected, gnome-shell keeps crashing: Program terminated with signal SIGSEGV, Segmentation fault. #0 output_free (output=0x0, fd=8) at winsys/cogl-winsys-egl-kms.c:728 728 winsys/cogl-winsys-egl-kms.c: No such file or directory. (gdb) bt #0 output_free (output=0x0, fd=8) at winsys/cogl-winsys-egl-kms.c:728 #1 _cogl_winsys_egl_display_destroy (display=<optimized out>) at winsys/cogl-winsys-egl-kms.c:765 #2 0x00007fcde81ef05b in _cogl_winsys_display_destroy (display=display@entry=0x1972170) at winsys/cogl-winsys-egl.c:441 #3 0x00007fcde81ef0f6 in _cogl_winsys_display_setup (display=0x1972170, error=0x7ffffaedb518) at winsys/cogl-winsys-egl.c:484 #4 0x00007fcde81ab383 in cogl_display_setup (display=display@entry=0x1972170, error=error@entry=0x7ffffaedb518) at ./cogl-display.c:154 #5 0x00007fcde81aa8e9 in cogl_renderer_check_onscreen_template (renderer=<optimized out>, onscreen_template=onscreen_template@entry=0x1972100, error=error@entry=0x7ffffaedb518) at ./cogl-renderer.c:369 #6 0x00007fcdeb6f7a6b in clutter_backend_real_create_context (backend=0x1957060, error=0x7ffffaedb698) at clutter-backend.c:324 #7 0x00007fcdeb70f743 in _clutter_feature_init (error=error@entry=0x7ffffaedb698) at clutter-feature.c:107 #8 0x00007fcdeb72152b in clutter_init_real (error=0x7ffffaedb698) at clutter-main.c:1378 #9 0x00007fcdeb72174b in post_parse_hook (context=0x1972170, group=0x0, data=0x0, error=0x7ffffaedb698) at clutter-main.c:1550 #10 0x00007fcdea9ecd77 in g_option_context_parse (context=context@entry=0x19719a0, argc=argc@entry=0x0, argv=argv@entry=0x0, error=error@entry=0x7ffffaedb698) at goption.c:2163 #11 0x00007fcdeb7223a0 in clutter_parse_args (error=0x7ffffaedb690, argv=0x0, argc=0x0) at clutter-main.c:1770 #12 clutter_init (argc=argc@entry=0x0, argv=argv@entry=0x0) at clutter-main.c:1832 #13 0x00007fcdec308d6f in meta_clutter_init () at backends/meta-backend.c:628 #14 0x00007fcdec3384e5 in meta_init () at core/main.c:358 #15 0x0000000000401f8e in main (argc=1, argv=0x7ffffaedba88) at main.c:429 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 904520] New: upower memory leak
by bugzilla_noreply＠novell.com 17 Sep '17

17 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904520 Bug ID: 904520 Summary: upower memory leak Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sonichedgehog_hyperblast00(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since upgrading from openSUSE 13.1 to 13.2, the system immediately slows down and freezes after several hours to a day of uptime. Since this is usually the result of a memory leak, I waited to catch the process at fault before the machine went unresponsive. The cause appears to be a root process called upowerd, part of the upower package. http://software.opensuse.org/package/upower The process rests at about 1.1 MB of memory usage, so the leak is sudden and extreme when it happens. As a workaround, I kill the process immediately after logging in, which doesn't appear to break anything. Since this is likely an issue with the application, I suggest either disabling upower or downgrading / upgrading the version offered in 13.2 to one that doesn't have the problem. openSUSE 13.1 appears to have version 0.9.23 of upower, whereas 13.2 has version 0.99.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 905643] New: package plymouth-branding-openSUSE: installation error
by bugzilla_noreply＠novell.com 12 Sep '17

12 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905643 Bug ID: 905643 Summary: package plymouth-branding-openSUSE: installation error Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- During a standard installation, I found this error in /var/log/zypp/history: # 2014-11-15 14:32:54 plymouth-branding-openSUSE-13.2-3.6.1.noarch.rpm installed ok # Additional rpm output: # No kernel found in /boot or bad modules dir in /lib/modules # warning: %post(plymouth-branding-openSUSE-13.2-3.6.1.noarch) scriptlet failed, exit status 1 # 2014-11-15 14:32:54|install|plymouth-branding-openSUSE|13.2-3.6.1|noarch|root@192.65.176.237|openSUSE-13.2-0|3f6c3fd7921504a308efd01996c5a76eb8cfb3ae| The problem is that the postinstall scriptler runs: /usr/sbin/plymouth-set-default-theme which runs: /usr/lib/plymouth/plymouth-update-initrd which in turn runs: mkinitrd which does not find any kernel installed. A possible fix is to add this line in branding-openSUSE.spec: %package -n plymouth-branding-openSUSE Summary: openSUSE branding for Plymouth bootsplash License: GPL-2.0+ Group: System/Fhs PreReq: plymouth-plugin-script PreReq: plymouth-scripts +PreReq: multiversion(kernel) Supplements: packageand(plymouth:branding-openSUSE) Provides: plymouth-branding = %{version} -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 904468] New: Dolphin File Manager copy,cut and paste do not work as expected
by bugzilla_noreply＠novell.com 12 Sep '17

12 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904468 Bug ID: 904468 Summary: Dolphin File Manager copy,cut and paste do not work as expected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: iJohann-Peter.Schneider(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Start Dolphin File manager. First time a file item with right mouse button is selected. On the menu which shows up "cut" or "copy" is activated. The mouse is moved off the file item. Left mouse button is pressed to deselect file item. Right mouse button is pressed again not on any file item. The menu showed up does not contain a menu entry "Insert Item" as expected. Now a second time the same file item with right mouse button is selected. On the menu which shows up "cut" or "copy" is activated again. The mouse is moved off the file item. Left mouse button is pressed to deselect file item. Right mouse button is pressed again not on any file item. The menu shows up does now contain a menu entry "Insert Item" as expected. That is "cut","copy" and "paste" only work when activated two times, means every second try. This behaviour can be reproduced. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 918111] New: osc: triggerreason fails for openSUSE:13.2:Update
by bugzilla_noreply＠novell.com 12 Sep '17

12 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=918111 Bug ID: 918111 Summary: osc: triggerreason fails for openSUSE:13.2:Update Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: suse-tux(a)gmx.de Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- 19:10 ares60:../Update/zypper > osc -d -v tr openSUSE:13.2:Update/zypper standard x86_64 https://api.opensuse.org openSUSE:13.2:Update zypper standard x86_64 makeurl: https://api.opensuse.org ['build', 'openSUSE:13.2:Update', 'standard', 'x86_64', 'zypper', '_reason'] [] GET https://api.opensuse.org/build/openSUSE:13.2:Update/standard/x86_64/zypper/… Traceback (most recent call last): File "/usr/bin/osc", line 26, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 484, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1214, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 5132, in do_triggerreason reason = root.find('explain').text AttributeError: 'NoneType' object has no attribute 'text' > rpm -q osc osc-0.148.2-1.1.noarch -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 905665] New: Firefox crash on different pages with adobe flash
by bugzilla_noreply＠novell.com 12 Sep '17

12 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905665 Bug ID: 905665 Summary: Firefox crash on different pages with adobe flash Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: opensource(a)prodigy7.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Updated Linux Distribution from OpenSUSE 13.1 to OpenSUSE 13.2 on 2 systems which comes with firefox 33.0. Since then, most pages with flash crashed on call. Updates also to 33.1 from mozilla repo but same result. Try it with nightly (firefox-36.0a1.en-US) and nightly works without any problems on flash pages. Can't identify my problem directly but I think, this bug could be the reason. I think, it's bug #1074860 (https://bugzilla.mozilla.org/show_bug.cgi?id=1074860) Please patch firefox or update. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 937280] New: Digikam 4.11 crashes due to libkexiv2 built against old libexiv2-13 instead of libexiv2-14
by bugzilla_noreply＠novell.com 10 Sep '17

10 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=937280 Bug ID: 937280 Summary: Digikam 4.11 crashes due to libkexiv2 built against old libexiv2-13 instead of libexiv2-14 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: gpsanino(a)vtr.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 640301 --> http://bugzilla.opensuse.org/attachment.cgi?id=640301&action=edit Crash information Hi, this is an old issue but still alive. Development of Digikam has been very active and has included many features together with bug solving. The default Digikam version has been left way behind this process. However, more recent versions of Digikam can be found in KDE:EXTRA repo. The problem is that even the most recent Digikam 4.11, requires a version of libkexiv2-11 who still requires to have the file libexiv2.so.13 provided by libexiv2-13 (v.0.24 with the bugs we know about MP4 files among others). exiv2 has implemented many bug fixes and features having v0.25 available since long time. However, we still find libkexiv2 being built against libexiv2-13 (with the old and buggy version 0.24) even on the most recent libkexiv2 versions. The package issue is critical to be solved because anybody upgrading with KDE:EXTRA, had his/her Digikam killed since a couple of days after upgrading to DK 4.11.0 despite the wrong dependency of libkexiv2 to libexiv2-13 instead of libexiv2-14. Among the many bugs of libexiv2.so.13 (exiv2 0.24) there are problems with MP4 files. These were solved in exiv2 0.25 implemented by libexiv2.so.14 (provided by libexiv2-14), but even the most recent version of libkexiv2 has not been built against libexiv2-14. Then if the user has MP4 files within the collections managed by Digikam, among other known issues, it crashes at start-up every time. As Digikam, there are several other KDE apps using the buggy version libexiv2-13 instead of libexiv2-14. Most recent libkexiv2 (15.04.3) that I could find, is distributed by KDE:Applications repo and libexiv2-14 by "Graphics" among other repos. It seems to me that the fastest packaging and distribution solution would be to have a version of libkexiv2 built against libexiv2-14 and posted in KDE:Extra since it is where recent Digikam versions are posted as well. Then the three correct packages could finally met in a single repo. Thanks in advance gps -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 953013] New: Unable (or at least wasn't shown) to do "just" remove a package with zypper
by bugzilla_noreply＠novell.com 09 Sep '17

09 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=953013 Bug ID: 953013 Summary: Unable (or at least wasn't shown) to do "just" remove a package with zypper Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: trifanstanislav(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36 Build Identifier: I try to remove firefox package. But zypper try to install another one, but I don't want it, and there is no option for skipping new install. Reproducible: Always Steps to Reproduce: $> sudo zypper remove firefox Actual Results: root's password: Loading repository data... Reading installed packages... 'firefox' not found in package names. Trying capabilities. Resolving package dependencies... The following NEW package is going to be installed: MozillaThunderbird The following application is going to be REMOVED: Firefox The following package is going to be REMOVED: MozillaFirefox 1 new package to install, 1 to remove. Overall download size: 33.1 MiB. Already cached: 0 B After the operation, 5.9 MiB will be freed. Continue? [y/n/p/? shows all options] (y): Expected Results: Add in the line: `Continue? [y/n/p/? shows all options] (y):` an option for remove only. It may be used `ro` option for remove only, and there should be information what it means. This actually is an usability bug. You may found tricks over the web that people do for that. That's totally not good and makes SUSE to loose points in usability versus other OSes. BTW: is not meaningful to use `p` for restart whatever it is. It make sense to put option with 2 or 3 chars that will make action intuitive to remember and use. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 923072] New: Firefox crashes on several sites
by bugzilla_noreply＠novell.com 09 Sep '17

09 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=923072 Bug ID: 923072 Summary: Firefox crashes on several sites Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: info(a)tim-schuermann.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Firefox crashes on several sites (mostly cnet.com and Phoronix). Firefox eats up the whole processor time. After the crash Firefox remains as a zombie process in memory but without any open window. Even the crash reporter doesn't show up. The problem occures on three systems: - Intel Core i7 - Intel Core i5 - Within VirtualBox Each time with a "clean" openSUSE-Installation (with all system updates). -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 914656] New: seccheck in security repo won't run
by bugzilla_noreply＠novell.com 09 Sep '17

09 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=914656 Bug ID: 914656 Summary: seccheck in security repo won't run Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: werner.flamme(a)ufz.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The mail I get from the /usr/lib/secchk/security-control.sh daily cron job shows errors: ---snip--- /usr/lib/secchk/helper.inc: line 46: guessable_password_email: command not found sed: can't read blurbs/guessable_passwd.txt: No such file or directory /usr/lib/secchk/helper.inc: line 49: syntax error near unexpected token `}' /usr/lib/secchk/helper.inc: line 49: `}' /usr/lib/secchk/helper.inc: line 46: guessable_password_email: command not found sed: can't read blurbs/guessable_passwd.txt: No such file or directory /usr/lib/secchk/helper.inc: line 49: syntax error near unexpected token `}' /usr/lib/secchk/helper.inc: line 49: `}' /usr/lib/secchk/security-daily.sh: line 64: check_for_globally_exported_fs: command not found /usr/lib/secchk/security-daily.sh: line 70: list_loaded_kernel_modules: command not found /usr/lib/secchk/security-daily.sh: line 73: nfs_mounted_with_missing_nosuid: command not found /usr/lib/secchk/security-daily.sh: line 76: display_programs_with_bound_sockets: command not found /usr/lib/secchk/security-control.sh: line 52: send_daily_changes: command not found ---pins--- A look into /usr/lib/secchk/ tells me that the file /usr/lib/secchk/blurbs/guessable_passwd.txt exists. Maybe the script changes the CWD before accessing the file? I went back to the seccheck package of the distro itself. But: in line 46 of helper.inc the () are missing behind 'function guessable_password_email', even in the distro version of seccheck. After fixing that, the script runs and generates the expected mail. -- You are receiving this mail because: You are on the CC list for the bug.

1 2