openSUSE Factory September 2015

factory@lists.opensuse.org

126 participants
133 discussions

Re: [opensuse-factory] Frequent freezes on new Tumbleweed installation

by Jiri Slaby

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/21/2015, 05:28 PM, Chan Ju Ping wrote: > I have the log from the last crash just an hour ago. The panel in > KDE froze and wouldn't respond. Then programs would start becoming > non-responsive. > > > > The cause of the crash is using Adobe Connect for a course I am > taking. Hmm, but this log shows no reason for the crash. I think, it would be best to create a bug in bugzilla and continue there. For example, /var/log/message or journalctl output would be worth attaching to see if there is something... regards, - -- js suse labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWAQTpAAoJEL0lsQQGtHBJh8MP/3hOsfM4oRjvKopE4GFiI/eM cWRXDJ495y6WeS6PuaBYPgi/3tLt0nIK3k6TnpzcIy4HoXm9heohHy9x1+jYYNdR SUYyF/hl9MyP6WH3N85xcdK/CRhOkLWFIdHjfGw7Yc+EcdkphxYQ4ZdaKcPNQ/DQ G4JwpjNbp+TvJTB3ek9DKU+pPQ4NAYmIF+wap/kWQevfxvvbaH2NH3/WZ1uutIdJ cNxjrFHtflMNzNb3r1W6xa9jd14ujFhTUP4O1czdaGpo2CXEElsmeqhZ05bGrSpZ T7VkDRKgSDLEVLtJZFmX8k5X5VyYpvhWBfo2+cWBcBjLelk0VmW8t5DYnMGc5YOw q/uLmx5zuCI43nfoSYRMtS5+47kQOyrTeL4b1X9M/vEqCiOahz1LT6rBdIHDs0wi oD/frMskTF5TRa+e2Wl+1EUJoImE4MCo+ETq/99cH0pxlGxshhl+XJ2w6/QWYNTA 1X+gDlOyr3+/ADkkKWw2iQDz+HQ06Sc4uNbLcMexSXqpDY5ymWbTPH5pthkTRPwr 0iCDvaSZq1lUyQd+849sZL6h6/c4PvE39VZpWYk2IFxnd+7S3xwrMQ2ejH93s3bN tuPgqlZQ5qdzBKfpMkBChyZ5JF1Wbp225y8CsZDbhqmWVo6bY0Pnv2buOud21SUs WohAYc9V4wHnWmEkzE7j =Ld0M -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

RE: [opensuse-factory] Re: [opensuse] tumbleweed update repo link broken? Or installation borked

by stakanov＠freenet.de

> -----Ursprüngliche Nachricht----- > Von: Patrick Shanahan > Gesendet: Di. 22.09.2015 16:45 > An: opensuse-factory(a)opensuse.org > Betreff: [opensuse-factory] Re: [opensuse] tumbleweed update repo link broken? Or installation borked > > Please trim quotes and wrap lines to --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

[opensuse-factory] Leap 42.1 Bootloader/Grub2 installation failed to boot

by Terje J. Hanssen

I have experienced that installation of a second openSUSE version (for dual-boot) looze the menu.lst and fails to boot after the installation. I have also found a work-around to fix this, but I'm afraid unexperienced openSUSE users can give up and drop openSUSE for further testing if and when this happends. Therefore I wonder if the installation can be made more robust to avoid this confusing issue. Scenario: 1) On my hp laptop the SSD disk (sda 150G) was sliced in six partitions and applied as follows for a first installed andworking openSUSE 13.2: /dev/sda1 2G swap /dev/sda2 20G / (root for openSUSE 13.2) /dev/sda3 40G /home /dev/sda4 87G (Extended) /dev/sda5 20G (available for second root) /dev/sda6 67G /data (additional user data) 2) Next I installed Leap 42.1 M2 from the DVD, selected Expert partitioning, imported existing mount points and selected /dev/sda5 formatted ext4 as root for Leap /dev/sda3 unformatted and mounted as shared /home for 13.2 and Leap (yes I know the shared /home has some drawbacks but more benefits in my opinion) Beyond adding some extra appliactions and setup SSH, the installation else was kept as default. I didn't change anything regarding the bootloader installation. The installation went ok until the first reboot, the it stopped on the black console sreen after the word 'GRUB' and nothing else. I tried to startup again and the same happened; no GRUB menu.lst didn't become available. That is, neither the previous working openSUSE 13.2 nor 42.1 could be started. 3) Workaround: What I have found that works (mostly alsways) to fix boot problems, is to run an Upgrade installation from the 13.2 DVD by re-enabling all previous online repositories one by one (there should have been an single option to easier re-enable all !?). The upgrade then doesn't change anything than reinstall the boot-loader at the end. And after first reboot, the GRUB menu is back containing both 13.2 (default) and 42.1 boot options as it should. Can this issue be avoided to make dual or multiboot installations easier? 4) For one or another reason the same boot-issue doesn't happend on my stationary workstation with tripple boot setup between 13.2 - Tumbleweed and 42.1 over more internal disks. Though I have to run Upgrade from the 13.2 DVD afterwards as I want 13.2 to be kept as the be the default boot option (I guess there is another way to edit this). And after upgrade of i.e the TW kernel version I also have to run mkconfig on 13.2 to update the menu.lst Thanks, Terje J. Hanssen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

[opensuse-factory] Frequent freezes on new Tumbleweed installation

by Chan Ju Ping

Hi. I decided to upgrade from 13.2 to Tumbleweed, but couldn't get the login screen to load when I did the steps with `zypper dup` in the Tumbleweed installation guide. Some failure with Plymouth or X to load properly. Since that failed, I went ahead and downloaded the Tumbleweed ISO for KDE and installed it within my LUKS partition setup and by also importing the mount points from my previous installation. Amazingly enough, everything worked out of the box with the wipe and reinstallation of /, and I didn't have to reconfigure my core applications. However, I have now been running into frequent crashes and freezes, where the computer stops responding. This seems to happen every time online video is being played, for both Flash and HTML5. I have toggled the compositor via KDE's settings to use OpenGL 3.1 as the screen stutters on OpenGL 2.0. I suspect it is a compositor issue. Any thoughts on how to track down and resolve this issue? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

[opensuse-factory] Tumbleweed & ZRAM

by Hans Carlos Hofmann

Hello, I have System using SSD's In order to avoid destructive Write orgies to the Devices i have compcache used in the Past. On 13.2 it has used the Devices brw-rw---- 1 root disk 253, 0 Sep 19 07:39 /dev/zram0 brw-rw---- 1 root disk 253, 1 Sep 19 07:39 /dev/zram1 brw-rw---- 1 root disk 253, 2 Sep 19 07:39 /dev/zram2 brw-rw---- 1 root disk 253, 3 Sep 19 07:39 /dev/zram3 On Tumbleweed i dont found such a peace of Software I found there is successor https://software.opensuse.org/package/systemd-zram-service Ok unstabel ... But there i get also a signature Fail if i try to Install this mew service for zram ... The modprobe zram works, i get the devices ... But there is this systemd ... it is not my friend Carlos

6 years, 9 months

[opensuse-factory] No sound with skype on a newly installed Tumbleweed

by C. Brouerius van Nidek

As the subject says, skype does not give a sound. Looking in the skype program it informs me that it is trying to use a virtual device. How ccan I solve this problem> I have googled and at the installation I have seen to it that all necessary files have been installed. On this x86_64 computer that gives some 70 downloads of 32 bit files.. (interesting how Leap is going to handle this) Pavucontrol is installed and the sound card works great. . . -- Linux User 183145 using KDE4 and LXDE on a Pentium IV , powered by openSUSE 20150909 (x86_64) Kernel: 4.2.0-6.g31d60fb-desktop KDE Development Platform: 4.14.10 17:43pm up 0:17, 2 users, load average: 0.38, 0.90, 1.30 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

Re: [opensuse-factory] Re: openldap packages

by Ralf Haferkamp

Hi Howard, On Wed, Sep 16, 2015 at 09:58:05AM +0200, Howard Guo wrote: > Hello Ralf and Michael. > > If I remember correctly, the 2.3.x library has to do with SAP products, but I > do not know enough about SAP to comment further on this. Perhaps Peter could > share more insights. Ok, but it could still be moved to separate package/spec file, right? That's a pretty easy thing to do and I guess we don't really need those compat packages for Factory/Tumbleweed anyway. If I understood correctly, Michael would be willing spend more time on maintaining the OpenLDAP packages for openSUSE without those ancient bits. Are you ok with removing the 2.3 bits in network:ldap? > Kind regards, > Howard > > On Tue, 15 Sep 2015, Ralf Haferkamp wrote: > > >Hi Michael, > > > >On Tue, Sep 15, 2015 at 08:21:35AM +0200, Michael Ströder wrote: > >>Hello Ralf, > >> > >>Ralf Haferkamp wrote: > >>>True. The 2.3.X based builts of the slapcat tool were included for migrating > >>>from SLE10 to SLE11 (which already containted a 2.4 release). So I am not quite > >>>sure why that is still there. IMO it would be ok to remove that part from the > >>>packages now. (Note, I might be missing something as I am not currently actively > >>>working on the packages) > >>> > >>>Though having that semiautomatic migration was a specific > >>>requirement for SLE11 back then. > >> > >>Note that even the upstream package disabled SLE_11 builds and it does not > >>work IIRC because of missing krb5-mini: > >> > >>https://build.opensuse.org/package/show/network:ldap/openldap2 > >> > >>In my package the builds for SLE_12 seems to work. But I can't test them since > >>I don't have a SLE_12 machine. > >> > >>>>=> So there's no point to maintain this 2.3.x cruft (except compat libldap > >>>>2.3.x for legacy binary software). > >> > >>>Yeah. The compat libldap is a bit different. That probably has to stay in some > >>>way (at least for SLE). > >> > >>But who is going to maintain that? Likely not me because I can't test at all. > >> > >>So how to proceed from here? Could someone please start a new > >>compat-libldap-2.3 package herein? > >Yeah, that might be one solution. But I'd like to get Peter's or Howard's input > >on this. I put them on CC in case they are not subscribed here. I am not even > >sure if the compat libraries are still needed for SLE12. After all it's now > >almost 8 years after the 2.4 branch saw its first "stable" release. > > > >>https://build.opensuse.org/project/show/home:stroeder:branches:network:ldap -- regards, Ralf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

[opensuse-factory] OBS:Server:Unstable broken on Factory? (Passenger error)

by Andreas Färber

Hi, For some weeks I've been running a local OBS server on armv7hl Factory. After updating the machine this weekend, I get the following error page accessing its Web UI on https port 443: Web application could not be started cannot load such file -- phusion_passenger/platform_info/ruby (LoadError) /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:128:in `rescue in require' /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:39:in `require' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger.rb:237:in `require_passenger_lib' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:415:in `rescue in running_bundler' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:411:in `running_bundler' /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/loader_shared_helpers.rb:287:in `run_load_path_setup_code' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:99:in `preload_app' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:153:in `<module:App>' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:29:in `<module:PhusionPassenger>' /usr/lib/passenger/5.0.15//helper-scripts/rack-preloader.rb:28:in `<main>' Error ID 840136e9 Application root /srv/www/obs/api [...] Unfortunately I'm pretty clueless about Ruby... I do see a platform_info/ruby.rb here: -rw-r--r-- 1 root root 18826 Sep 20 11:51 /usr/lib/ruby/gems/2.2.0/gems/passenger-5.0.15/lib/phusion_passenger/platform_info/ruby.rb Can anyone clue me in on what is going wrong there? It seems that the OBS scheduler, for instance, is running fine, so I imagine this is either a Passenger/... packaging problem in Factory or a configuration/code problem on the OBS side? In order to get OBS running on armv7l, I needed to branch the following packages (in addition to OBS:Server:Unstable noarch packages), with no link diff left: apache2-mod_xforward perl-BSSolv rubygem-acts_as_list rubygem-acts_as_tree rubygem-clockwork rubygem-cocoon rubygem-dalli rubygem-escape_utils rubygem-hoptoad_notifier rubygem-innertube rubygem-joiner rubygem-kaminari rubygem-middleware rubygem-passenger rubygem-pundit rubygem-redcarpet rubygem-riddle rubygem-ruby-ldap rubygem-thinking-sphinx https://build.opensuse.org/project/show/home:a_faerber:branches:OBS:Server:… @Adrian, it would be nice if you could add openSUSE_Factory_ARM to OBS:Server:Unstable, to build them centrally instead. To save resources you could disable the build for aarch64/armv7l by default and just enable the above list of non-noarch packages for now. Also note that there's an OBS-WorkerOnly-midway Kiwi package that references obs://OBS:Server:Unstable/openSUSE_13.1_ports which no longer exists. rubygem-rails-4_2 is available in Tumbleweed already and probably shouldn't be rebuilt for openSUSE_Factory(_ARM) - it originally caused Gemfile problems that their 4.2.x versions between openSUSE:Factory:ARM and OBS:Server:Unstable were slightly out of sync: There's a link diff on that package, being at 4.2.2 while Factory has 4.2.4 currently - intentional? I am using the available Factory version. https://build.opensuse.org/package/show/OBS:Server:Unstable/rubygem-rails-4… In case anyone wonders why :Unstable, :2.6 is not being built for Factory at all. 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

6 years, 9 months

[opensuse-factory] Tumbleweed - Review of the Week 2015/38

by Dominique Leuenberger / DimStar

Dear Tumbleweed users and hackers, This week we were not able to deliver a single snapshot (yet). Sorry for this. The reason is actually rather simple: as RPM was switched to link against lua 5.3 instead of lua 5.1, the 'build' script needed to be updated to know of this difference. For this, the internally used version needed to be different from 132x (as only the first three digits are used). So, Tumbleweed has been 'bumped' to be suse_version 1330 and the build script was happy about this. Sadly, we missed kiwi in the game (and those version bumps can barely go through stagings). Anyway, kiwi has been fixed, it passed staging and has been checked in to openSUSE:Factory - that happened yesterday and we are now awaiting a full build that should hopefully soon go to openQA. If all goes well, you might get a release tomorrow. So, anyway, things that happened and are going to happen soon (based on the future outlook of last week): * Staging A with ncurses 6 is currently green! So you can expect NCurses 6.0 to land shortly (but not before the current snapshot starts to be tested) * Systemd 224: I debugged the issues currently seen in Staging:F. The KDE-related issues are tracked down to systemd currently not providing the pam libraries in a -32bit variant, thus failing to enable systemd integration. As a result, the session is not registering its seat. For GNOME, the same issue happens, PLUS wayland seems not to like to run in the new session. Additionally, plymouth seems to have trouble firing up in GUI mode, but stays in text mode. The last two items need more debugging... the first one 'only' needs somebody doing the fix. * libQt 5.5 got a step closer... still some yast modules missing to make this acceptable. * KDE Application 15.08.0: with the delays caused by the snapshots, we should be able to provide this next week too. * GNOME 3.18.0: RC2 (3.17.92) is submitted to staging and still looks like we're on track. You see, even without having produced snapshots this week, there is progress and you can expect a bunch of changes coming your way in the next few days (fingers crossed). I wish you a great weekend, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 years, 9 months

[opensuse-factory] Samba privatedir fix and content migration

by Lars Müller

Hi, with the next Samba package available to openSUSE Tumbleweed the private directory configuration will change from /etc/samba/ to /var/lib/samba/private/ The later is the upstream default and the breakage on the SUSE side got introduced ten years back. The private dir is _not_ the location of /etc/samba/smb.conf and other configuration files. The private dir is where files and directories are created which are private to Samba's daemons and tools. With the latest package we ensure to migrate the following files from /etc/samba/ to /var/lib/samba/private/ netlogon_creds_cli.tdb passdb.tdb secrets.tdb smbpasswd If you see the need to cover more files please reply to this mail or reopen https://bugzilla.opensuse.org/show_bug.cgi?id=946051 which covers the relocation of the private dir. I expect this will not have broken any Tumbleweed install as we had no published version in the last week. All you might have gotten is: a) A /etc/samba/sock directory. This dir is superfluous as soon as you have gotten /var/lib/samba/private/sock/ belonging to the samba-client package. b) Failing nmb, smb, and winbind daemons as AppArmor prevented access to /etc/samba/sock See https://bugzilla.opensuse.org/show_bug.cgi?id=945563 if you like to know how valueable bug reports are. Kudos to Giuseppe for filing the bug report and Christian who pushed the dicsussion to the AppArmor dev list. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

6 years, 9 months

← Newer
1
2
3
4
5
6
7
8
9
...
14
Older →

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 2015