openSUSE Factory September 2016

factory@lists.opensuse.org

131 participants
147 discussions

[opensuse-factory] TW: XFCE : LibreOffice Calc cannot Red Negative Numbers

by ellanios82

Hello List , Since about 2 months , TW: XFCE : LibreOffice Calc it is not possible to produce Negative Numbers in Red Color . [ same files show Red Negative Numbers OK using OpenOffice.] ........ regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] Intention to drop e17 (Enlightenment will stay)

by Simon Lees

Hi All, I think the time has finally come to drop e17, It's not currently in leap and its mostly stayed in tumbleweed because while it still built it was less effort then removing it, now it no longer builds and the people who I know were using it have migrated to the latest enlightenment or something else I think its time to drop it. As a bit of history e17->e18 broke a bunch of much older themes and some modules (that didn't work well anyway) and introduced a compulsory compositor even though its quite fast all this annoyed some people so given I had to rename the new package anyway I just left the old one to keep people happier. If anyone is strongly apposed to this (and would like to fix the build issue) or has anything they need help migrating please don't hesitate to let me know. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B

5 years, 11 months

[opensuse-factory] New Tumbleweed snapshot 20160901 released!

by Dominique Leuenberger

Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&versio… When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: MozillaFirefox (48.0.1 -> 48.0.2) MozillaThunderbird (45.2 -> 45.3.0) binutils (2.26.1 -> 2.27) elfutils (0.166 -> 0.167) gcc6 (6.1.1+r239476 -> 6.2.1+r239849) grub2 libgcj-gcc6 (6.1.1+r239476 -> 6.2.1+r239849) lsof mailman (2.1.22 -> 2.1.23) python-setuptools (23.1.0 -> 26.1.1) systemd === Details === ==== MozillaFirefox ==== Version update (48.0.1 -> 48.0.2) Subpackages: MozillaFirefox-translations-common - Mozilla Firefox 48.0.2: * Mitigate a startup crash issue caused on Windows (bmo#1291738) ==== MozillaThunderbird ==== Version update (45.2 -> 45.3.0) Subpackages: MozillaThunderbird-translations-common - update to Thunderbird 45.3.0 (boo#991809) * Disposition-Notification-To could not be used in mail.compose.other.header * "edit as new message" on a received message pre-filled the sender as the composing identity. * Certain messages caused corruption of the drafts summary database. security fixes: * MFSA 2016-62/CVE-2016-2836 Miscellaneous memory safety hazards * MFSA 2016-63/CVE-2016-2830 (bmo#1255270) Favicon network connection can persist when page is closed * MFSA 2016-64/CVE-2016-2838 (bmo#1279814) Buffer overflow rendering SVG with bidirectional content * MFSA 2016-65/CVE-2016-2839 (bmo#1275339) Cairo rendering crash due to memory allocation issue with FFmpeg 0.10 * MFSA 2016-67/CVE-2016-5252 (bmo#1268854) Stack underflow during 2D graphics rendering * MFSA 2016-70/CVE-2016-5254 (bmo#1266963) Use-after-free when using alt key and toplevel menus * MFSA 2016-72/CVE-2016-5258 (bmo#1279146) Use-after-free in DTLS during WebRTC session shutdown * MFSA 2016-73/CVE-2016-5259 (bmo#1282992) Use-after-free in service workers with nested sync events * MFSA 2016-76/CVE-2016-5262 (bmo#1277475) Scripts on marquee tag can execute in sandboxed iframes * MFSA 2016-77/CVE-2016-2837 (bmo#1274637) Buffer overflow in ClearKey Content Decryption Module (CDM) during video playback * MFSA 2016-78/CVE-2016-5263 (bmo#1276897) Type confusion in display transformation * MFSA 2016-79/CVE-2016-5264 (bmo#1286183) Use-after-free when applying SVG effects * MFSA 2016-80/CVE-2016-5265 (bmo#1278013) Same-origin policy violation using local HTML file and saved shortcut file ==== binutils ==== Version update (2.26.1 -> 2.27) Subpackages: binutils-devel - Update to binutils 2.27. * Add a configure option, --enable-64-bit-archive, to force use of a 64-bit format when creating an archive symbol index. * Add --elf-stt-common= option to objcopy for ELF targets to control whether to convert common symbols to the STT_COMMON type. GAS: * Default to --enable-compressed-debug-sections=gas for Linux/x86 targets. * Add --no-pad-sections to stop the assembler from padding the end of output sections up to their alignment boundary. * Support for the ARMv8-M architecture has been added to the ARM port. Support for the ARMv8-M Security and DSP Extensions has also been added to the ARM port. * ARC backend accepts .extInstruction, .extCondCode, .extAuxRegister, and .extCoreRegister pseudo-ops that allow an user to define custom instructions, conditional codes, auxiliary and core registers. * Add a configure option --enable-elf-stt-common to decide whether ELF assembler should generate common symbols with the STT_COMMON type by default. Default to no. * New command line option --elf-stt-common= for ELF targets to control whether to generate common symbols with the STT_COMMON type. * Add ability to set section flags and types via numeric values for ELF based targets. * Add a configure option --enable-x86-relax-relocations to decide whether x86 assembler should generate relax relocations by default. Default to yes, except for x86 Solaris targets older than Solaris 12. * New command line option -mrelax-relocations= for x86 target to control whether to generate relax relocations. * New command line option -mfence-as-lock-add=yes for x86 target to encode lfence, mfence and sfence as "lock addl $0x0, (%[re]sp)". * Add assembly-time relaxation option for ARC cpus. * Add --with-cpu=TYPE configure option for ARC gas. This allows the default cpu type to be adjusted at configure time. GOLD: * Add a configure option --enable-relro to decide whether -z relro should be enabled by default. Default to yes. * Add support for s390, MIPS, AArch64, and TILE-Gx architectures. * Add support for STT_GNU_IFUNC symbols. * Add support for incremental linking (--incremental). GNU ld: * Add a configure option --enable-relro to decide whether -z relro should be enabled in ELF linker by default. Default to yes for all Linux targets except FRV, HPPA, IA64 and MIPS. * Support for -z noreloc-overflow in the x86-64 ELF linker to disable relocation overflow check. * Add -z common/-z nocommon options for ELF targets to control whether to convert common symbols to the STT_COMMON type during a relocatable link. * Support for -z nodynamic-undefined-weak in the x86 ELF linker, which avoids dynamic relocations against undefined weak symbols in executable. * The NOCROSSREFSTO command was added to the linker script language. * Add --no-apply-dynamic-relocs to the AArch64 linker to do not apply link-time values for dynamic relocations. - Add binutils-2.27-branch.diff with fixes on the branch sofar. - Remove gold-relocate-tls.patch, included in binutils 2.27. ==== elfutils ==== Version update (0.166 -> 0.167) Subpackages: libasm1 libdw1 libelf1 libelf1-32bit - Update to version 0.167: libasm: Add eBPF disassembler for EM_BPF files. backends: Add m68k and BPF backends. ld: Removed. dwelf: Add ELF/DWARF string table creation functions. dwelf_strtab_init, dwelf_strtab_add, dwelf_strtab_add_len, dwelf_strtab_finalize, dwelf_strent_off, dwelf_strent_str and dwelf_strtab_free. Support compressed sections from binutils 2.27. - Remove patch elfutils-0.166-elfcmp-comp-gcc6.patch: included upstream. ==== gcc6 ==== Version update (6.1.1+r239476 -> 6.2.1+r239849) Subpackages: cpp6 gcc6-c++ gcc6-fortran gcc6-info gcc6-locale gcc6-objc libasan3 libatomic1 libcilkrts5 libgcc_s1 libgcc_s1-32bit libgfortran3 libgomp1 libitm1 liblsan0 libmpx2 libmpxwrappers2 libobjc4 libquadmath0 libstdc++6 libstdc++6-32bit libstdc++6-devel-gcc6 libtsan0 libubsan0 - Update to gcc-6-branch head (r239849). * Includes GCC 6.2 release. * Includes fix for OVMF compilation. - Refresh gcc-dir-version.patch. - gcc6-devel: require gmp-devel and mpc-devel - Update HSA_RUNTINE_LIB in gcc6-hsa-enablement.patch ==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - binutils 2.27 creates empty modules without a symtab. Add patch grub2-accept-empty-module.patch to not reject them. ==== libgcj-gcc6 ==== Version update (6.1.1+r239476 -> 6.2.1+r239849) Subpackages: gcc6-gij gcc6-java libgcj-devel-gcc6 libgcj-jar-gcc6 libgcj_bc1 - Update to gcc-6-branch head (r239849). * Includes GCC 6.2 release. * Includes fix for OVMF compilation. - Refresh gcc-dir-version.patch. - gcc6-devel: require gmp-devel and mpc-devel - Update HSA_RUNTINE_LIB in gcc6-hsa-enablement.patch ==== lsof ==== - modify lsof_4.89-nfs_hanging.patch and add a check for HasNFS variable as HasNFS may already have been set to 2 in the readmnt() function [bsc#995061] ==== mailman ==== Version update (2.1.22 -> 2.1.23) - update to 2.1.23 * CSRF protection in user options page (CVE-2016-6893) * header_filter_rules matching: headers and patterns are all decoded to unicode * another possible REMOVE_DKIM_HEADERS setting * SMTPDirect.py can now do SASL authentication and STARTTLS * bug fixes, i18n updates * for further details see NEWS ==== python-setuptools ==== Version update (23.1.0 -> 26.1.1) - fix certificate handling with certifi, add support for SUSE's CA bundle (setuptools-certpath.patch, fixes boo#993968) - remove shebang lines, strip executable bit from README, to silence the easy rpmlint warnings - update to 26.1.1: * Re-release of 26.1.0 with pytest pinned to allow for automated deployement and thus proper packaging environment variables, fixing issues with missing executable launchers. * #763: ``pkg_resources.get_default_cache`` now defers to the `appdirs project <https://pypi.org/project/appdirs>`_ to resolve the cache directory. Adds a vendored dependency on appdirs to pkg_resources. * #748: By default, sdists are now produced in gzipped tarfile format by default on all platforms, adding forward compatibility for the same behavior in Python 3.6 (See Python #27819). * #459 via #736: On Windows with script launchers, sys.argv[0] now reflects the name of the entry point, consistent with the behavior in distlib and pip wrappers. * #752 via #753: When indicating ``py_limited_api`` to Extension, it must be passed as a keyword argument. * Add Extension(py_limited_api=True). When set to a truthy value, that extension gets a filename apropriate for code using Py_LIMITED_API. When used correctly this allows a single compiled extension to work on all future versions of CPython 3. The py_limited_api argument only controls the filename. To be compatible with multiple versions of Python 3, the C extension will also need to set -DPy_LIMITED_API=... and be modified to use only the functions in the limited API. * #739 Fix unquoted libpaths by fixing compatibility between `numpy.distutils` and `distutils._msvccompiler` for numpy < 1.11.2 (Fix issue #728, error also fixed in Numpy). * #731: Bump certifi. * Style updates. See #740, #741, #743, #744, #742, #747. * #735: include license file. * #612 via #730: Add a LICENSE file which needs to be provided by the terms of the MIT license. * #725: revert `library_dir_option` patch (Error is related to `numpy.distutils` and make errors on non Numpy users). * #720 * #723: Improve patch for `library_dir_option`. * #717 * #713 * #707: Fix Python 2 compatibility for MSVC by catching errors properly. * #715: Fix unquoted libpaths by patching `library_dir_option`. * #714 and #704: Revert fix as it breaks other components downstream that can't handle unicode. See #709, #710, and #712. * #704: Fix errors when installing a zip sdist that contained files named with non-ascii characters on Windows would crash the install when it attempted to clean up the build. * #646: MSVC compatibility - catch errors properly in RegistryInfo.lookup. * #702: Prevent UnboundLocalError when initial working_set is empty. * #686: Fix issue in sys.path ordering by pkg_resources when rewrite technique is "raw". * #699: Fix typo in msvc support. * #609: Setuptools will now try to download a distribution from the next possible download location if the first download fails. This means you can now specify multiple links as ``dependency_links`` and all links will be tried until a working download link is encountered. * #688: Fix AttributeError in setup.py when invoked not from the current directory. * Cleanup of setup.py script. * Fixed documentation builders by allowing setup.py to be imported without having bootstrapped the metadata. * More style cleanup. See #677, #678, #679, #681, #685. * #674: Default ``sys.path`` manipulation by easy-install.pth is now "raw", meaning that when writing easy-install.pth during any install operation, the ``sys.path`` will not be rewritten and will no longer give preference to easy_installed packages. To retain the old behavior when using any easy_install operation (including ``setup.py install`` when setuptools is present), set the environment variable: SETUPTOOLS_SYS_PATH_TECHNIQUE=rewrite This project hopes that that few if any environments find it necessary to retain the old behavior, and intends to drop support for it altogether in a future release. Please report any relevant concerns in the ticket for this change. * #398: Fix shebang handling on Windows in script headers where spaces in ``sys.executable`` would produce an improperly-formatted shebang header, introduced in 12.0 with the fix for #188. * #663, #670: More style updates. * #516: Disable ``os.link`` to avoid hard linking in ``sdist.make_distribution``, avoiding errors on systems that support hard links but not on the file system in which the build is occurring. * #667: Update Metadata-Version to 1.2 when ``python_requires`` is supplied. * #631: Add support for ``python_requires`` keyword. * More style updates. See #660, #661, #641. * #659: ``setup.py`` now will fail fast and with a helpful error message when the necessary metadata is missing. * More style updates. See #656, #635, #640, [#644], #650, #652, and #655. * Updated style in much of the codebase to match community expectations. See #632, #633, #634, [#637], #639, #638, #642, #648. * If MSVC++14 is needed ``setuptools.msvc`` now redirect user to Visual C++ Build Tools web page. * #625 and #626: Fixes on ``setuptools.msvc`` mainly for Python 2 and Linux. * Pull Request #174: Add more aggressive support for standalone Microsoft Visual C++ compilers in msvc9compiler patch. Particularly : Windows SDK 6.1 and 7.0 (MSVC++ 9.0), Windows SDK 7.1 (MSVC++ 10.0), Visual C++ Build Tools 2015 (MSVC++14) * Renamed ``setuptools.msvc9_support`` to ``setuptools.msvc``. Re-release of v23.2.0, which was missing the intended commits. * #623: Remove used of deprecated 'U' flag when reading manifests. ==== systemd ==== Subpackages: libsystemd0 libsystemd0-32bit libudev-devel libudev1 libudev1-32bit systemd-32bit systemd-bash-completion systemd-logger systemd-sysvinit udev - Add a script to fix /var/lib/machines to make it suitable for rollbacks (bsc#992573992573) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] btrfs quotas enabled by default

by Chris Murphy

Hi, Could someone urgently check a default installation of the current Leap beta? btrfs qgroup show / It seems at least one user has found in Tumbleweed that Btrfs quotas are enabled by default, and experiencing bogus enospc as a result (actually they're the result of quotas so they aren't entirely bogus). I don't know how this happened, and I'm actually very curious how it happened. But the priority is to find out if Leap has them enabled by default and if so what's doing that so it can be reverted. It's bad to do this in Tumbleweed, but it's a blocker bug for Leap. It can't ship if quotas are enabled. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] Desktop freeze on login/logout

by ianseeks

Hi This is an occasional issue, sometimes once a day, sometimes once every couple of days. Sometimes its the very first login after startup and sometimes its hours later during a login after quite a few successful login/logouts. When the progress bar bar on the login splash gets to about 85%, it will sometimes stop and needs a ctrl backspace backspace to recover. Sometimes i can't recover it as its locked/frozen the keyboard so no keys work, so its a full reboot. The same also happens on logout but its even more rare than the login. Just wondering if anyone else is experiencing this issue? Regards Ian -- Qt: 5.6.1 KDE Frameworks: 5.25.0 kf5-config: 1.0 KDE Plasma: 5.7.4 Kwin5: 5.7.4-152.1 Kernel: 4.7.2-1-default opensuse:tumbleweed:20160831 Nouveau: 1.0.12-1.3 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

Re: [opensuse-factory] btrfs qgroup concerns

by Richard Brown

On 3 September 2016 at 18:24, Chris Murphy <lists(a)colorremedies.com> wrote: > On Fri, Sep 2, 2016 at 8:27 PM, Jeff Mahoney <jeffm(a)suse.com> wrote: >> No, it's not. We publish the code for every single one of our kernels >> both in patch series and expanded tree form. Every maintenance update >> is tagged and even if they weren't, the last commit that was included in >> the RPM is included in the RPM metadata. We also have a very >> longstanding, public policy regarding code going upstream and a outsize >> percentage of our kernel teams in upstream maintainer roles. So you can >> imagine that when someone suggests that we're not being good community >> members with our kernels, it ruffles a few feathers. You're the one >> leveling an accusation (using typically incorrect assumptions). You >> bring the proof. > > 1. > On the Btrfs mailing list, most every time anyone has a quota problem, > they're informed if they need stable quota support to use XFS or ext4. > And not a single Btrfs developer ever contradicts that advice in the > slightest way. And this most recent non-contradicted advice happened > just a few weeks ago. Well now you've seen at least one of our btrfs developers contradicting that advice. And it's not like Jeff is some novice who doesn't know what he's been talking about, he's been intimately involved with the kernel and explicitly btrfs and other filesystems for years now. He knows what he's talking about, he's very rarely wrong, and he is one of those boring "don't change anything, ship it only when it's absolutely ready" Enterprise developers. And even IF he is wrong, it's going to be the job of him and his team to fix it in both SLE and openSUSE, so you can take extra reassurance from that. And he works for SUSE, and SUSE has invested a lot of time, effort, engineering and testing on this. You've heard of the testing Jeff's team has done. In addition I can tell you that SUSE QA have been doing additional testing on btrfs qgroups and shaken out a corner case bug or two, but nothing that would classify as a 'Ship Stopper'. SUSE's Beta customers have all been using the feature also as part of the SLE 12 SP2 Open Beta programme. You've heard of the strategic importance of this feature from Matthias, SUSE's Senior Director of SLE Product Management. As a default option in our installation, almost all of SUSE's customers will be relying on this to work when they install SLE 12 SP2 at the end. SUSE isn't going to do that unless it's confident in the quality of the feature and its ability to support it for years. As an openSUSE contributor, you have an opportunity to contribute to this and to bring additional knowledge and data points to the table, but that comes with a responsibility to ensure that your data is accurate, correct, reproducible and actionable. By quoting random commits and mailinglist threads you do not have a full understanding of, while actively rejecting any suggestion to do your own testing, you have failed to contribute responsibly to this discussion. > The very first time I have ever read anywhere, by any Btrfs developer, > that enabling quotas is considered stable, was on this list. You heard it here first :) > 2. > https://github.com/kdave/btrfs-progs/commit/637c005ac881a7def923e3f56c9f928… > > Upstream has performance and stability concerns in the current code. > That commit is two weeks old. I will quote from that commit "Signed-off-by: David Sterba <dsterba(a)suse.com>" David is another one of SUSEs btrfs developers, we ARE upstream. The advice in David's documentation is true. There is a performance hit and you should only turn it on if you' are using it. We are using it in snapper, therefore we turn it on and take that hit. That's not a performance concern, that's good documentation. And yes, there have been corner cases, and our developers have fixed them, and will fix them when they're reported. That doesn't mean it's 'unstable', that means there are corner cases. > Matthias, Richard, and some of your comments, while circumspect, can > be inferred to mean your quota code substantially differs from the > current stable kernel, and that's why you consider it stable. But then > just yesterday you say "the only [Btrfs] patches we have applied to > the 4.4-based SLE12-SP2/Leap kernel are backports and patches we've > submitted upstream". 4.4 is the latest upstream LTS Kernel 4.7 is the latest upstream kernel You have tested 4.7 in tumbleweed, and quoted from commits for 4.7 The current 4.4 Kernel contains many backports from 4.7. It also contains code which 4.7 has totally changed, so has specific fixes for 4.4 that are nothing to do with the current state in 4.7. These 4.4 backports+fixes number in the thousands. Many of them were written by SUSE engineers as part of their work for SLE 12 SP2/Leap 42.2 and then submitted upstream (it's our policy to submit all of our patches upstream). In the very unlikely event of upstream not accept a small amount of our patches, there is also the possibility that OUR 4.4 LTS Kernel might have some patches and configuration that differs from upstream vanilla 4.4 LTS. So, to put it bluntly, everything you tested in 4.7 is irrelevant unless you prove otherwise. everything you read about the current upstream development is not conclusive unless you prove otherwise. You were invited to help confirm the issues you feared were present in the 4.4 LTS Kernel used by Leap 42.2 or SLE 12 SP2. You were given advice from Jeff on how to do this. You have outright refused to do so, so frankly I feel you have no credibility to imply that there are deeper issues. To put it very directly, with all due respect, either contribute or shut up - this is a mailinglist for contributors to discuss the development of the openSUSE distributions, not a soap box for ill-informed rants. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] New package: bcm43xx-firmware

by Andreas Färber

Hello, I have submitted a new package bcm43xx-firmware for inclusion in Tumbleweed (and later Leap 42.2), containing two things: 1) Redistributable BCM43430 Wifi+Bluetooth firmware files 2) NVRAM config files for BCM43430 and BCM43362 The former will hopefully at some point go into kernel-firmware package via linux-firmware.git (open GitHub ticket for Raspberry Pi Foundation) and could then be dropped from this package. However, both pcie and sdio variants of brcmfmac driver use a single per-chipset .txt file for initialization that will not go into linux-firmware.git because it doesn't depend on just the chipset but on the "wiring" of the module or board. We therefore may have multiple configs for the same chipset, as demonstrated for bcm43362, and need to determine at installation time which file to use. For Kiwi images - where we cannot detect this during %post - the idea is to not provide a potentially wrong config file by default and instead add a symlink manually from a Kiwi hook script. https://build.opensuse.org/request/show/424758 Note: Please do not add additional firmware files to this package without obtaining confirmation that they are in fact redistributable! For non-redistributable firmware see pullin-bcm43xx-firmware package. A corresponding arm64 kernel config patch to enable brcmfmac on master branch is pending; on openSUSE-42.2 branch it is already enabled and on stable branch it's not needed. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] Question about VirtualBox build failure in 42.2

by Larry Finger

The build of VirtualBox 5.1.4 for Leap 42.2 has failed because it is "unresolvable" due to "nothing provides kernel-default-devel = 4.7.2-2 needed by kernel-syms". Is this a transient failure, or is the kernel structure for 42.2 borked? This project builds locally with osc. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] 42.2 Live DVD with KDE

by Linux Kamarada

Hi everyone. I started this discussion in another mailing list: https://lists.opensuse.org/opensuse/2016-08/msg00466.html Then, I was instructed to proceed here, at opensuse-factory. Since I believe Live media are important to Linux - especially because they present Linux to newcomers - I'm here to volunteer myself to build (or to help anyone that already started building) an official LiveDVD for openSUSE Leap 42.2. Before seeking for help, I was doing all the work on my own. You can check what I've done until now here: - Download of ISO image: https://sourceforge.net/projects/kamarada/files/latest/download - KIWI source: https://github.com/kamarada/kiwi-config-Kamarada/tree/42.2 - Commit history: https://github.com/kamarada/kiwi-config-Kamarada/commits/42.2 With that Leap 42.2 Live media, I tried to come as close as possible from a clean openSUSE Leap 42.2 install made using Network install. Except for Brazilian Portuguese translations and a few customizations to the software selection and YaST Firstboot, my Live media is equivalent to a clean openSUSE install. I'm facing some issues, which I reported at GitHub, and I would appreciate the help of any of you who have sufficient knowledge to solve them (maybe someone who knows very well openSUSE and/or KIWI could help solving those issues): https://github.com/kamarada/kiwi-config-Kamarada/issues/ Briefly, here is what I'm facing: 1) I'm unable to ping, when I try to do so I get the following error message: ping: error while loading shared libraries: libcap.so.2: cannot stat shared object: Permission denied 2) Live system loses keyboard configuration after initial setup, it looks like YaST Firstboot does not store the keyboard layout I select In the meantime, I managed to solve this issue: 3) LiveDVD asks for root password (the latest version based on Leap 42.2 Beta 1 does not ask for root password anymore) Any help would be really appreciated. Thank you in advance! Antonio The Linux Kamarada Project https://kamarada.github.io/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

[opensuse-factory] RFC - pattern console still requires wodim

by Dave Plater

Leap:42.2 is about to go beta and the console pattern still requires wodim which causes cdrtools to be uninstalled. This has caused many problems with the recording of dvds by k3b in the past. This requirement remains due to kiwi having a specific requirement for genisoimage. This requirement is removed in kiwi versions 8x but apparently there are some python packages that can't be accepted. Regards Dave Plater -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 11 months

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory September 2016