openSUSE Factory October 2014

factory@lists.opensuse.org

131 participants
140 discussions

[opensuse-factory] Re: XFS filesystem total failure on return from hibernation.
by Linda Walsh 06 Oct '14

06 Oct '14

Carlos E. R. wrote: > And finally, there is a patch: > 8018ec0 xfs: mark all internal workqueues as freezable > > I have reported now on our Bugzilla, against 13.1: > <https://bugzilla.opensuse.org/show_bug.cgi?id=899785> > > Requesting that the patch be backported to all openSUSE releases. This > bug can badly impact 13.2 and the new SLES 12, as by default they use > XFS for home. ---- Without question, I can't see this NOT being a requirement for 13.2. The iffy bits apply to earlier versions... **especially** recently 'browning' Evergreen platforms. I really don't get a strong impression that the majority of customers (esp. larger ones) have switched to 13.1 yet... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

Re: [opensuse-factory] Factory Snapshot 20141001, KDE hangs while copying big files
by Florian Koch 06 Oct '14

06 Oct '14

Hi again, i see very high i/o waiting while the problem happens (~90%), and i think its this Problem https://lwn.net/Articles/572911/, after setting vm.dirty_background_ratio = 1 (default 10) vm.dirty_ratio = 5 (default 20) the problem does not occour, and the i/o wait is only about ~50%. So KDE does something which calls sync, maybe the indexing? regards Florian 2014-10-04 21:22 GMT+02:00 Florian Koch <florian.koch1981(a)gmail.com>: > hm, if its a Kernel Bug it should happen also with Gnome > > 2014-10-04 20:38 GMT+02:00 Cristian Rodríguez <crrodriguez(a)opensuse.org>: >> El 04/10/14 a las #4, Neil Rickert escribió: >> >>> I think it's partly a hardware issue. The copy is hogging the bus or >>> the interrupt handler or something. >> >> Sounds like a kernel bug. >> >> >> -- >> Cristian >> "I don't know the key to success, but the key to failure is trying to >> please everybody." >> -- >> To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org >> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Questions regarding design choices in beta 1.
by Roger Luedecke 06 Oct '14

06 Oct '14

I wanted to get started on a 'sneak peek' article and had some questions. 1) In order to add a wifi connection, one must give administrative access. Is this a design choice (security choice that chased Linus away) or is this a bug? 2)YaST Installer is freakishly fast. Is this entirely due to switching to Ruby? Both the loading of each 'page' of the installer as well as the actual installation process is many factors faster than it was ever before. 3)The boot process is way faster than before. Previously my computer would slow when it was getting ready to launch Gnome. Now it often doesn't have time to display the splash before the desktop has loaded. Does this have to do with having graphical sessions handled by systemd? If you can elaborate on why it's so much faster that would be great. 4)Btrfs & XFS is a really odd choice for default filesystems. I can understand using btrfs for root (though I'd like to hear your reasoning) but I don't understand why home is XFS as opposed to also being btrfs or even ext4. Very curious design choices. 5)Are we not shipping with Geeko branded art this release? Is the art being used upstream? Thank you for your time in this regard, Roger Luedecke Member and Advocate, openSUSE Project http://opensuseadventures.blogspot.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 6

[opensuse-factory] Budget Fair Queueing (BFQ) Storage-I/O Scheduler for openSUSE 13.2?
by Roman Bysh 06 Oct '14

06 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, Has openSUSE thought about enabling Budget Fair Queueing (BFQ) Storage-I/O Scheduler in the kernel by default? Budget Fair Queueing is a disk scheduler which allows each process/thread to be assigned a portion of the disk throughput. It is supposed to increase throughput to your hard drive or SSD. And a number of distros have this enabled by default. See: http://algo.ing.unimo.it/people/paolo/disk_sched/ Any thoughts for openSUSE 13.2? Cheers! Roman -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJUG17sAAoJEISyH9AowGDQenUH/RLhSMjhqb/6B+dtEP9bQ2nG 3LayeUDAtJkisrA/JSpTt8sLJ9S2GSQXk5+Hr3viWjU38XZasIm3o2pungHSd87t DD93T6g+KiaI0zt/bqBGgDxnHDFHahjq++zi8aTaDJY/XLdjN5OQnqv1MhNjKlrK upQ75MMY5JAV8qjINOBCEqwBGAnUkpIAKcwsdwnZAhNjScXQ34OmwJx3etig6MNl aP0vbnAEMF1oCC1Aitzr2Gb841O08et8b7RpfN6Z77dLdCXBxY75qKf9KTicNlAR WfUUscRmjhZZO2IQhigsTJmd52FLq9t780puBHujl3FV79fNJ5hZ+6Jkhwp/UBg= =J9Bb -----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

4 4

[opensuse-factory] Pattern for Mate
by denisart benjamin2 06 Oct '14

06 Oct '14

Hello everyone ! I created patterns for Factory but absolutely don't know how and by who there are included or created in the patterns package. What have I to do ? Regards. Benjamin -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] Introduce btrfsmaintenance package to Factory
by David Sterba 06 Oct '14

06 Oct '14

Hi, let me introduce a new package that supplements the btrfs filesystem and aims to automate a few maintenance tasks. This means the scrub, balance, trim or defragmentation. The package comes from SLE12 where btrfs is going to be the default filesystem as well. Each of the tasks can be turned on/off and configured independently. The default config values were selected to fit the default installation profile. * scrub - go through all medatada/data and verify the checksums, default period is one month * balance - the balance command can do a lot of things, in general moves data around in big chunks, here we use it to reclaim back the space of the underused chunks so it can be allocated again according to current needs The point is to prevent some corner cases where it's not possible to eg. allocate new metadata chunks because the whole device space is reserved for all the chunks, although the total space occupied is smaller and the allocation should succeed. * trim - run TRIM on the filesystem using the 'fstrim' utility, makes sense for SSD devices. * defrag - run defrag on configured directories. This is for convenience and not necessary. There's a separate defragmentation task that happens automatically and defragments only the RPM database files in /var/lib/rpm. This is done via a zypper plugin and the defrag pass triggers at the end of the installation. This improves reading the RPM databases later, but the installation process fragments the files very quickly so it's not likely to bring a significant speedup here. Cron takes care of periodic execution of the scripts, but they can be run any time directly from /usr/share/btrfs/maintenance/, respecting the configured values in /etc/sysconfig/btrfsmaintenance. If the period is changed manually, the cron symlinks have to be refreshed, use "systemctl restart btrfsmaintenance-refresh" (or the "rcbtrfsmaintenance-refresh" shortcut). Changing the period via yast2 sysconfig editor triggers the refresh automatically. The project lives in obs://filesystems/btrfsmaintenance and I'm going to submit it to Factory. I'd like to ask volunteers to give it some testing. Feedback is welcome. Thanks, David -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Wallpaper : most elegant artwork
by ellanios82 06 Oct '14

06 Oct '14

Hello List , - openSUSE 13.1 default wallpaper deserves gold-medal for elegant artwork : - perhaps it could be offered as a choice in future openSUSE distros ? ............... regards -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 5

[opensuse-factory] Experiences installing factory on my new Acer laptop E15 E5-511
by Freek de Kruijf 06 Oct '14

06 Oct '14

Obviously this system comes with Windows 8.1, which I did not want to drop and with EFI, if that's the right term. My intention was to leave 50 GB to Windows and use the rest for openSUSE. I used a USB stick with Beta1 to do the initial installation. I changed the BIOS to start from a USB stick. The first problem was that I could not make a connection using WiFi. It complains that the packages iw and wpa_supplicant are not installed and apparently these packages are not on the USB stick (in the iso-file). So I started without a network connection and accepted the offer to leave about 150 GB to Windows and to a Windows restore system. The boot system on the USB stick does not offer the possibility to boot from the real hard disk. So after the installation I had to remove the USB stick before I could boot Linux. But first I had to change the BIOS to first try to boot from USB, second from the disk and a third possibility from the Windows Boot Manager. So at first I ended up in Windows. Maybe I did exit Windows too early, I don't recall to have seen a warning. After that I started a new installation removing all the Linux partitions and tried to shrink the main Windows partition down to the 50 GB like I wanted. I got a warning that the file system on it, NTFS, was corrupt. So I went back to Windows and had to restore Windows 8.1 completely, using the restore system. I could have chosen to leave any user data intact. During some exploration of Windows I found a feature to shrink the main windows partition so I made it 50 GB. My next installation removed all earlier Linux partitions and I managed to make the partitioning like I wanted it to be. Two 20 GB system partitions with Brtfs and two 20 GB home partitions with XFS for two versions of openSUSE next to each other. Next to that I have a large partition with XFS where users have their permanent data which is not OS version dependent. In the users home folders symbolic links are used to access this data. I got a warning about subvolumes not being correct, but I did not understand the meaning. Later I found out this was about the home folder being a subvolume on a Btrfs partition and also a folder on its own partition. The concept of subvolumes is new to me and now I realize you need to know about it to do a proper partitioning of your disk. Finally I got a system to boot. All goes well till I have the KDE splash screen showing the first of 5 icons on it. After that the screen blanks. After some time the background picture of the KDE desktop is shown, but when I touch a key on the keyboard or move the mouse, the screen blanks again. I tried also running KDE Live, but I got the same behavior. So it seems my graphics card, an Intel HD Graphics is not properly supported. Any suggestions? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

[opensuse-factory] New Factory snapshot 20141002 released!
by Ludwig Nussel 05 Oct '14

05 Oct '14

Changed packages: ==== apper ==== - Add patch apper-adjust-to-latest-packagekitqt.diff to make the plasmoid work based on the latest PackageKit Qt bindings. The patch should be pushed upstream. ==== java-1_7_0-openjdk ==== Subpackages: java-1_7_0-openjdk-devel java-1_7_0-openjdk-headless - Do not waste time building javadoc when building bootstrap - Ignore ant's java-devel require - we already have java-bootstrap-devel - Reformat the spec files with newer version of spec-cleaner - Use more generic requires and provides: * java-bootstrap and * java-bootstrap-devel - Allows us to use the same boostrap packages for building of java-1_8_0-openjdk ==== java-1_8_0-openjdk ==== Version update (1.8.0.20 -> 1.8.0.40~b07) Subpackages: java-1_8_0-openjdk-headless - Build template jvm interpreter on ppc64le * It was ported for this architecture in jdk8u49-b06 - Build depend on the generic java-bootstrap-devel * Allows to build against java-1_7_0-openjdk-bootstrap - Reformat the spec file with spec-cleaner - Upgrade to upstream tag jdk8u40-b07 * Unstable snapshot in view of jdk8u40 release - Removed patch: aarch64-jni-update.patch * Upstreamed changes - Modified patch: aarch64-misc.patch * Do not patch generated-configure.sh that is anyway regenerated. - Modified patch: system-libjpeg.patch * Do not patch generated-configure.sh that is anyway regenerated. * Rediff to apply cleanly - Modified patches: link-with-as-needed.patch, system-giflib5.patch, system-lcms.patch, system-libpng.patch * Rediff to apply cleanly ==== kiwi ==== Version update (5.06.165 -> 7.01.5) Subpackages: kiwi-desc-isoboot kiwi-desc-netboot kiwi-desc-oemboot kiwi-desc-vmxboot kiwi-doc kiwi-media-requires kiwi-pxeboot kiwi-templates kiwi-tools - v7.01.5 released - Fixed use of zypper package cache For unknown reasons zypper removes the pkg-cache-dir when calling the addrepo command. Because this is unwanted kiwi temporarly moves the current cache dir and moves it back after the addrepo call is done - DB: rebuild documentation - DB: update documentation first review by the documentation department - v7.01.4 released - Added support for custom boxname for vagrant images (bnc #896205) By default the name set to the vagrant .json file is the name of the image as specified in the kiwi XML description. However, in the world of https://vagrantcloud.com/, the convention for "fully-qualified" box names is "ORGANIZATION/BOXNAME" which does not apply to a standard kiwi image name. With the new boxname attribute people can now specify the name of the box to be vagrantcloud conform. e.g <vagrantconfig ... boxname="opensuse/minimal-13.1"/> - v7.01.3 released - Add error message to log file if downloadFile failed - Fixed uninstall make target Delete /dev/shm/lwp-download created by kiwi - v7.01.2 released - DB: rebuild documentation for version 7 - Branch created for SLE12, master open for development at version 7 - Fixed use of uninitialized value $time ==== liblightdm-gobject-1-0 ==== Version update (1.10.1 -> 1.12.0) Subpackages: lightdm lightdm-lang - update to version 1.12.0 - Fix assumption that the display server is X when running scripts. - Don't access .dmrc files until information from these files is required. - Don't check the logind CanGraphical seat property unless login-check-graphical option is set to true. There are too many cases of drivers that don't set the appropriate flags for this feature to work. - Make socket writing code used between greeter and daemon more robust to errors. - Fix small memory leaks. - Improve logging messages. - Test improvements. - Rework logind code that gets session ID. The previous method was racy and a change in lightdm 1.11.7 led to a lockup when this race occurred. - Handle CanGraphical property on logind seats - Use logind to provide the list of seats to use. Deprecate the old method of manually defining seats. - Add --show-config option that shows combined configuration. - Drop the surfaceflinger seat type. This was a temporary solution while Ubuntu Phone was migrating to Mir. - Add a seat option 'allow-user-switching' that can disable all user switching for that seat - Add a new session type 'mir-container' that allows the session to run inside a custom system compositor - Only seat0 takes VT from Plymouth - Removed unused GAsyncResultIface.is_tagged as this attribute was not available in earlier versions of Glib I/O. - Abort autogen if yelp-tools not installed - Return correct errors for D-Bus calls - Make PAM services configurable - Do timed autologin each time you are returned to the greeter - Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we are faking - dm-tool: Warn if trying to switch to user without username - Fix Mir sessions broken with unity-system-compositor 0.3. - Add back Vala bindings for LightDM.Greeter.connect_sync - just mark as deprecated. - Put unity-system-compositor's mir_socket under /run rather than /tmp. - Fix building with clang (3.5) and -Werror. - Correct section name in default users.conf file. - Add liblightdm method to get user UID - DBus-activate logind - Check for libgcrypt at configure time - Allow greeters to remain runing to reduce startup time when switching to a greeter - Add asynchronous methods to liblightdm - When switching to an existing session refresh PAM credentials and end session cleanly so no resources leak. - Support new standard DesktopNames field in session files - Set XDG_SESSION_TYPE and XDG_SESSION_DESKTOP as used by systemd - Emit DBus PropertiesChanged when Sessions/Seats properties change. Also add SessionAdded/SessionRemoved signals to Seat interface - update to version 1.10.2 - Use logind to provide the list of seats to use - Fix crash if running script hooks with non-X display servers - Add a seat option 'allow-user-switching' that can disable all user switching for that seat - Make PAM services configurable - Add liblightdm method to get user UID - Add a new session type 'mir-container' that allows the session to run inside a custom system compositor - Add --show-config option that shows combined configuration - Use XDG_SESSION_ID from PAM instead of using the logind D-Bus API - Make socket writing code used between greeter and daemon more robust to errors - Correct section name in default users.conf file - Fix tests failing with Qt 5.3 due to it checking getuid/geteuid which we are faking - Fix small memory leaks - Test improvements - fix users.conf section name - enable logind multiseat by default - configure lightdm to use the xdm PAM services directly instead of symlinking them ==== lzip ==== Version update (1.15 -> 1.16) - Update to new upstream release 1.16 * Compression ratio of option -9 has been slightly increased. * Compression time has been reduced by 4%. * `lzip -0` is now comparable in compression speed and ratio to `gzip -6` (gzip's default compression level). * Copying of file dates, permissions, and ownership now behaves like `cp -p`. (If the user ID or the group ID cannot be duplicated, the file permission bits S_ISUID and S_ISGID are cleared). * The license has been changed to GPL version 2 or later. ==== patterns-openSUSE-apparmor ==== Subpackages: patterns-openSUSE-apparmor_opt patterns-openSUSE-base patterns-openSUSE-books patterns-openSUSE-console patterns-openSUSE-devel_C_C++ patterns-openSUSE-devel_basis patterns-openSUSE-devel_gnome patterns-openSUSE-devel_ide patterns-openSUSE-devel_java patterns-openSUSE-devel_kde patterns-openSUSE-devel_kernel patterns-openSUSE-devel_mono patterns-openSUSE-devel_perl patterns-openSUSE-devel_python patterns-openSUSE-devel_qt4 patterns-openSUSE-devel_rpm_build patterns-openSUSE-devel_ruby patterns-openSUSE-devel_tcl patterns-openSUSE-devel_web patterns-openSUSE-dhcp_dns_server patterns-openSUSE-directory_server patterns-openSUSE-enhanced_base patterns-openSUSE-enhanced_base_opt patterns-openSUSE-file_server patterns-openSUSE-fonts patterns-openSUSE-fonts_opt patterns-openSUSE-games patterns-openSUSE-gateway_server patterns-openSUSE-gnome patterns-openSUSE-gnome_admin patterns-openSUSE-gnome_basis patterns-openSUSE-gnome_basis_opt patterns-openSUSE-gnome_games patterns-openSU SE-gnome_ide patterns-openSUSE-gnome_imaging patterns-openSUSE-gnome_imaging_opt patterns-openSUSE-gnome_internet patterns-openSUSE-gnome_laptop patterns-openSUSE-gnome_multimedia patterns-openSUSE-gnome_multimedia_opt patterns-openSUSE-gnome_office patterns-openSUSE-gnome_office_opt patterns-openSUSE-gnome_utilities patterns-openSUSE-gnome_yast patterns-openSUSE-imaging patterns-openSUSE-imaging_opt patterns-openSUSE-kde patterns-openSUSE-kde4_admin patterns-openSUSE-kde4_basis patterns-openSUSE-kde4_edutainment patterns-openSUSE-kde4_games patterns-openSUSE-kde4_ide patterns-openSUSE-kde4_imaging patterns-openSUSE-kde4_internet patterns-openSUSE-kde4_laptop patterns-openSUSE-kde4_multimedia patterns-openSUSE-kde4_office patterns-openSUSE-kde4_utilities patterns-openSUSE-kde4_utilities_opt patterns-openSUSE-kde4_yast patterns-openSUSE-kvm_server patterns-openSUSE-lamp_server patterns-openSUSE-laptop patterns-openSUSE-lxde patterns-openSUSE-lxde_laptop patterns-openSUSE-lxde_office patterns-openSUSE-mail_server patterns-openSUSE-minimal_base patterns-openSUSE-minimal_base-conflicts patterns-openSUSE-misc_server patterns-openSUSE-multimedia patterns-openSUSE-multimedia_opt patterns-openSUSE-network_admin patterns-openSUSE-non_oss patterns-openSUSE-non_oss_opt patterns-openSUSE-office patterns-openSUSE-office_opt patterns-openSUSE-print_server patterns-openSUSE-remote_desktop patterns-openSUSE-rest_dvd patterns-openSUSE-sw_management patterns-openSUSE-sw_management_gnome patterns-openSUSE-sw_management_kde4 patterns-openSUSE-tabletpc patterns-openSUSE-technical_writing patterns-openSUSE-x11 patterns-openSUSE-x11_opt patterns-openSUSE-x11_yast patterns-openSUSE-xen_server patterns-openSUSE-xfce patterns-openSUSE-xfce_basis patterns-openSUSE-xfce_laptop patterns-openSUSE-xfce_office patterns-openSUSE-yast2_basis patterns-openSUSE-yast2_install_wf - Pattern gnome_yast: Replace libyui-gtk-pkg and yast2-control-center-gnome in gnome_yast pattern with its qt version; the gtk bindings have critical bugs (see bnc#897910, bnc#891183, bnc#852730) but seem unmaintained for now. - package lxde * do not recommend imaging pattern: + it triggers the installation of GIMP that is redundant because mtPaint is in the pattern, has the same goal and is lighter + it recommends the installation of the pattern imaging_opt which in turn suggests calibre that is a heavyweight application that doesn't really fit in LXDE * do not recommend neither lxshortcut nor lxsession-edit: + lxshortcut is deprecated by LibFM 1.2.0 + lxsession-edit is now provided by LXSession * recommend uGet instead of transmission-gtk and do not suggests aria2: + uGet can manage both BitTorrent and Metalink protocols (in addition to HTTP, HTTPS and FTP) + aria2 is required by uGet ==== python-pyzmq ==== Version update (14.0.0 -> 14.3.1) - Update to 14.3.1 + Minor bugfixes to pyzmq 14.3: * Fixes to building bundled libzmq on OS X < 10.9 * Fixes to import-failure warnings on Python 3.4 * Fixes to tests * Pull upstream fixes to zmq.ssh for ssh multiplexing - Update to 14.3.0 + PyZMQ no longer calls :meth:`.Socket.close` or :meth:`.Context.term` during process cleanup. Changes to garbage collection in Python 3.4 make this impossible to do sensibly. + :meth:`ZMQStream.close` closes its socket immediately, rather than scheduling a timeout. + Raise the original ImportError when importing zmq fails. Should be more informative than `no module cffi...`. - Update to 14.2.0 + New Stuff * Raise new ZMQVersionError when a requested method is not supported by the linked libzmq. For backward compatibility, this subclasses NotImplementedError. + Bugs Fixed * Memory leak introduced in pyzmq-14.0 in zero copy. * OverflowError on 32 bit systems in zero copy. - Update to 14.1.0 + Security The headline features for 14.1 are adding better support for libzmq's security features. * When libzmq is bundled as a Python extension (e.g. wheels, eggs), libsodium is also bundled (excluding Windows), ensuring that libzmq security is available to users who install from wheels * New :mod:`zmq.auth`, implementing zeromq's ZAP authentication, modeled on czmq zauth. For more information, see the `examples <https://github.com/zeromq/pyzmq/tree/master/examples/>`_. + Other New Stuff * Add PYZMQ_BACKEND for enabling use of backends outside the pyzmq codebase. * Add :attr:`~.Context.underlying` property and :meth:`~.Context.shadow` method to Context and Socket, for handing off sockets and contexts. between pyzmq and other bindings (mainly pyczmq_). * Add TOS, ROUTER_HANDOVER, and IPC_FILTER constants from libzmq-4.1-dev. * Add Context option support in the CFFI backend. * Various small unicode and build fixes, as always. * :meth:`~.Socket.send_json` and :meth:`~.Socket.recv_json` pass any extra kwargs to ``json.dumps/loads``. + Deprecations * ``Socket.socket_type`` is deprecated, in favor of ``Socket.type``, which has been available since 2.1. - Update to 14.0.1 + Bugfix release * Update bundled libzmq to current (4.0.3). * Fix bug in :meth:`.Context.destroy` with no open sockets. * Threadsafety fixes in the garbage collector. * Python 3 fixes in :mod:`zmq.ssh`. ==== rsyslog ==== - Removed broken zpipe utility from diag-tools package (bnc#890228) ==== libthunarx-2-0 ==== Subpackages: thunar thunar-lang - Do not BuildRequire xorg-x11-devel, just pkgconfig(sm) and pkgconfig(x11) ==== xorg-x11-server ==== Subpackages: xorg-x11-server-extra xorg-x11-server-sdk - Backport upstream patches to enable Xephyr window placement via new "-output" option or new "-screen WxH+X+Y" syntax. * U_kdrive_extend_screen_option_syntax.patch * U_ephyr_enable_screen_window_placement.patch * U_ephyr_add_output_option_support.patch ==== xterm ==== Version update (311 -> 312) - Patch #312 - 2014/09/28 * undo change to do_select_regex() in patch #311 (reports by H Merijn Brand, Sven-Haegar Koch, Debian #762978). ==== yast2-network ==== Version update (3.1.101 -> 3.1.104) - The "change hostname via DHCP" setting is now configurable via control file (bnc#870896). - 3.1.104 - bnc#898620 - do not write LLADDR="00:00:00:00:00:00" into ifcfg in z/VM - 3.1.103 - bnc#897394, bnc#866250 - device specific routes configuration (ifroute-<devname>) is supported - 3.1.102 Removed packages: lxshortcut Added packages: uget > uget-lang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] After Hibernate, Monitor stays in StandBy
by immomail200＠gmx.de 05 Oct '14

05 Oct '14

Hello, since I'm using factory, the Monitor stays in StandBy after Hibernate. When I boot my PC after going to Hibernate, the Monitor is on during booting. But after booting the monitor goes back to StandyBy (even if I swith to the text console). The PC itself is reacting, e.g. I can (blind) login as root and restart the PC via the command reboot. With OpenSuse 13.1 is was working fine. Any ideas how to solve this issue? Thanks Albert -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory October 2014