June 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 982661] YaST2 shows duplicated packets
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982661 http://bugzilla.suse.com/show_bug.cgi?id=982661#c2 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger(a)suse.com Assignee|yast2-maintainers(a)suse.de |lslezak(a)suse.com Flags| |needinfo?(marceloatie@gmail | |.com) --- Comment #2 from Josef Reidinger <jreidinger(a)suse.com> --- Please attach yast logs, so we can see what happen inside. Thanks https://en.opensuse.org/openSUSE:Report_a_YaST_bug#I_reported_a_YaST2_bug.2… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982447] New: jar files must be opened with Java environment (java - jar) by default
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982447 Bug ID: 982447 Summary: jar files must be opened with Java environment (java - jar) by default Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: marceloatie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- .jar files should be opened with java -jar by default in all the Desktop environments instead of Ark (as a simple compressed file). Even the simple option to "open with Java" cannot be used without typing java -jar, because Openjdk 7 and 8 dont create .desktop files in /usr/share/applications, as Openjdk 6 do (openjdk-6-java.desktop). The same bug has found in Ubuntu, more information at https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1474379 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 982666] New: jar files must be opened with Java environment (java - jar) by default
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982666 Bug ID: 982666 Summary: jar files must be opened with Java environment (java - jar) by default Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: openSUSE 42.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Java Assignee: bnc-team-java(a)forge.provo.novell.com Reporter: marceloatie(a)gmail.com QA Contact: qa-bugs(a)suse.de CC: marceloatie(a)gmail.com Depends on: 982447 Found By: Community User Blocker: --- +++ This bug was initially created as a clone of Bug #982447 +++ .jar files should be opened with java -jar by default in all the Desktop environments instead of Ark (as a simple compressed file). Even the simple option to "open with Java" cannot be used without typing java -jar, because Openjdk 7 and 8 dont create .desktop files in /usr/share/applications, as Openjdk 6 do (openjdk-6-java.desktop). The same bug has found in Ubuntu, more information at https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1474379 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 982329] LVs/VGs don't get activated with "use_lvmetad = 1"
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982329 http://bugzilla.suse.com/show_bug.cgi?id=982329#c9 --- Comment #9 from Liuhua Wang <lwang(a)suse.com> --- (In reply to Manfred Hollstein from comment #6) > FWIW2: I just tried to reject /dev/loop devices from lvm's filter by adding > > "r|/dev/loop.*|", > > to devices/filter in /etc/lvm/lvm.conf, set max_loop to 64, rebuilt > everything required, rebooted and failed again. Even if the /dev/loop > devices are explicitly excluded in lvm.conf, they appear to be scanned when > the system is booted, and 64 non-existing loop devices appear to be too many > to allow the dm/udev logic in the latest lvm2 package to succeed. > > I'm now back to max_loop set to 32 :( In case of use_lvmetad = 0, the effective filter is "devices/filter"; while in case of use_lvmetad = 1, the effective filter is "devices/global_filter". Please see the comment about this: # Since "filter" is often overridden from command line, it is not suitable # for system-wide device filtering (udev rules, lvmetad). To hide devices # from LVM-specific udev processing and/or from lvmetad, you need to set # global_filter. The syntax is the same as for normal "filter" # above. Devices that fail the global_filter are not even opened by LVM. # global_filter = [] So in your case you need to add this to your lvm.conf. global_filter = ["r|/dev/loop.*|", "a/.*/"] -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982329] LVs/VGs don't get activated with "use_lvmetad = 1"
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982329 http://bugzilla.suse.com/show_bug.cgi?id=982329#c8 --- Comment #8 from Liuhua Wang <lwang(a)suse.com> --- (In reply to Manfred Hollstein from comment #0) > This has some history. For some time, "use_lvmetad = 1" in /etc/lvm/lvm.conf > used to work. With some update this got reset to "0" by default. While the > system used to work, it became apparent that running "dracut" (former > "mkinitrd") now takes appr. 1 minute per installed kernel. Also, running > "lvs" almost takes forever... When I compared my Tumbleweed installation > with my other Leap installations, I found out that on Leap "lvmetad" is > running, resulting in snappy responses after "lvs" commands, and also pretty > fast "dracut" runs. > > OK, let's activate "lvmetad" in Tumbleweed. First I activated/enabled and > started "lvm2-lvmetad.socket", followed by stopping a potentially running > (but there was't any) "lvm2-lvmetad.service". I then set "use_lvmetad = 1" > in /etc/lvm/lvm.conf, started and enabled "lvm2-lvmetad.service" and rebuilt > the initrd. The following reboot then got hung at > > "Waiting for /dev/mapper/rdisk00-swapdev1 to appear" > > and a similar message for the corresponding LV for /var. > > My setup is using /dev/md0 (MD-raid10) as a physical volume, providing space > for such volumes as /var, /swapdev1 and /home. It is my understanding that > at some point "/usr/lib/udev/rules.d/69-dm-lvm-metad.rules" should run > "pvscan --cache" to provide the necessary udev events feeding into dm/udev > to actually activate volumes, but, apparently this doesn't happen. Yes, your understanding is quite right. In case of use_lvmetad=1, for NON-ROOT partitions on LVM, it is the command `pvscan --cache --activate ay major:minor` in lvm2-pvscan@.service to activate the volumes. So you need to make sure lvm2-lvmetad.service running and lvm2-pvscan@major:minor.service running during boot, which should be automatically. > Whe I got stuck in the single-boot/rescue phase after the boot, running > "pvscan --cache" manually, followed by a "udevadm trigger" made the missing > VG and LVs available; but, since /var is on an LV, the system is not > actually usable at that point in time. I then downgraded the "lvm2" package > (from "2.02.141-64.2" in current TW) to "2.02.120-67.1" to Leap's most > current version, repeated all the lvmetad related configs from above, > rebuilt the initrd, rebooted and - voila - my system boots again - and > running "dracut" is not at all that boring again (appr. 10 secs. per kernel > now). > > It looks to me that the current LVM2 package is not lvmetad capable. Would you please tell me whether the following service is running or not? systemctl status initrd-udevadm-cleanup-db.service Thank you for reporting and sorry for the problems brought to you! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982329] LVs/VGs don't get activated with "use_lvmetad = 1"
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.suse.com/show_bug.cgi?id=982329 Liuhua Wang <lwang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |lwang(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 856391] grub2-reboot sets default boot entry permanently
by bugzilla_noreply＠novell.com 02 Jun '16

02 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=856391 http://bugzilla.opensuse.org/show_bug.cgi?id=856391#c26 Nick Levinson <Nick_Levinson(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Version|Final |13.2 CC| |Nick_Levinson(a)yahoo.com Component|Bootloader |Bootloader Hardware|x86-64 |Other Resolution|FIXED |--- Target Milestone|--- |13.2 Product|openSUSE 13.1 |openSUSE Distribution OS|openSUSE 13.1 |openSUSE 13.2 --- Comment #26 from Nick Levinson <Nick_Levinson(a)yahoo.com> --- Version 13.2 bootup also produces the message "error: sparse file not allowed" which shortly disappears as booting continues without choices that used to be visible at this stage. Until recently, on my single-OS laptop installed with defaults (including for the filesystem) and kept evergreen, I got a screen with several choices, a picture of a lizard-top logo, and soon text lines with a mention of the specific kernel being used in booting. Now I just get the kernel lines. Speed seems unaffected. For a cause in how I use the laptop, perhaps it began after I (accidentally) let the battery run down because I forgot to plug the AC in. I know both the rundown and the lack of choices happened near each other in time, but I'm not sure that the latter began on the next bootup after the rundown. I never explicitly use sleep or hibernate modes but when a battery runs low the OS starts nagging me and maybe on rundown it automatically went into that mode. I have cold-rebooted a bunch of times without the boot menu coming back. I don't want to edit internal files and risk unwanted consequences I'm not geeky enough to figure out. I have the OS on a refurbished debranded laptop, formerly probably a HP 2000 notebook. For this bug report, I'm reopening and updating the version. I don't doubt a repair for an earlier version. Relevant, including technical discussions, are forum threads https://forums.opensuse.org/showthread.php/501545-13-2-RC-1-sparse-file on ver. 13.2, https://forums.opensuse.org/showthread.php/506811-Grub-message-quot-sparse-… on 64-bit ver. 13.2 about a year ago, and https://forums.opensuse.org/showthread.php/514241-Error-Sparse-files-not-al… on Leap 42.1. My hardware is an AMD laptop; I'm not sure if that's of an x86-64 architecture. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982232] libcap1 rebuild fail with newer glibc
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.novell.com/show_bug.cgi?id=982232 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| |ibs:running:2688:low -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982234] perl-Net-SSLeay rebuild fail
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.novell.com/show_bug.cgi?id=982234 SMASH SMASH <smash_bz(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard| | maint:planned:update -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 982177] New: home:pontostroy:X11/Mesa: Bug
by bugzilla_noreply＠novell.com 01 Jun '16

01 Jun '16

http://bugzilla.opensuse.org/show_bug.cgi?id=982177 Bug ID: 982177 Summary: home:pontostroy:X11/Mesa: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: pontostroy(a)gmail.com Reporter: flyhigh72(a)web.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- DRI3 could not be enabled. Kernel 4.4.11 Intel(R) Core(TM) i5-6600T Intel(R) Skylake DT GT2 Mesa Package Revision 1468 Using following entry in /etc/X11/xorg.conf.d/50-device.conf does nothing :-( -------- Section "Device" Identifier "Intel Graphics" Driver "intel" Option "DRI" "3" EndSection -------- Output /var/log/Xorg.0.log -------- 4.420] (II) intel(0): [DRI2] Setup complete [ 4.420] (II) intel(0): [DRI2] DRI driver: i965 [ 4.420] (II) intel(0): [DRI2] VDPAU driver: va_gl [ 4.420] (II) intel(0): direct rendering: DRI2 enabled -------- -- You are receiving this mail because: You are on the CC list for the bug.

1 14