August 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] BlueZ 5
by Dimstar / Dominique Leuenberger 30 Oct '13

30 Oct '13

Hi all, I've just ran across an issue with Bluetooth in openSUSE 13.1; mainly, the GNOME Stack does not work with BlueZ 4.x anymore. There are several components that have been ported to Bluez 5 already; and, as most of the stuff is not relying on the library (as this has been marked obsolete by upstream anyway), not much was seen prior to actually finding a BT device to pair it. The D-Bus APi changed and, as a result, stuff relying on it simply has a 50% chance to work or not work. To make matters worse, we can't even just 'parallel install' bluez and bluez5, as the DBus services clash (same name space). So, we have the hard bullet to bite: either we update (Fedora decided to do so, see https://lists.fedoraproject.org/pipermail/devel/2013-August/187738.html for reference) or we accept to have a non-working BT stack in GNOME. Updating it would likely still leave a few breakages here and there; but KDE's BlueDevil for example does have support in git. The 2nd alternative would be to 'try to undo' the Bluez 5 porting in the GNOME Stack; No idea if and how well this will work; we would be the only distro with GNOME 3.10 running on Bluez 4. Any opinions around here? -- Dimstar / Dominique Leuenberger <dimstar(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

15 59

[opensuse-factory] New sssd desires samba4
by Jan Engelhardt 30 Sep '13

30 Sep '13

This is something to think on for openSUSE 13.2. The 1.10.x series of sssd wants to have the Samba4 header files so it can build its AD integration plugins. (S4/AD cannot be turned off, and that is an sssd bug, but that is not the point -- we surely want to build that plugin anyway.) openSUSE still does not have Samba4 in its package selection, and I am wondering when that might be expected to show up in future Factory. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 12

[opensuse-factory] Warning: new systemd version landing in Factory
by Frederic Crozat 20 Sep '13

20 Sep '13

Hi all, systemd v202 should be landed in Factory soon. It contains a lot of changes (and bug fixes) compared to v195 we had in 12.3, like (this is an extract from the .changes I wrote): + udev now supports different naming policies for network interface for predictable names (this one is disabled by /usr/lib/tmpfiles.d/network.conf until network team had a chance to look at it and test it). This should be enabled by default in Factory soon (see http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac… ) This can be also be turned off with kernel command line switch: net.ifnames=0 (when the tmpfiles.d is removed in the near future) + udev gained support for loading additional device properties from an indexed database. %udev_hwdb_update macro should be used by packages adding entries to this database. + Journal gained support for "Message Catalog", indexed database to link up additional information with journal entries. %journal_catalog_update macro should be used by packages adding %entries to this database. + New rpm macros has been added: %udev_rules_update(), %_udevhwdbdir, %_udevrulesdir, %_journalcatalogdir, %_tmpfilesdir, %_sysctldir. + "age" field for tmpfiles entries can be set to 0, forcing removal of files matching this entry. + coredumpctl gained "gdb" verb to invoke gdb on selected coredump. + In service files, %U can be used for configured user name of the service. + nspawn can be invoked without a controlling TTY. + systemd and nspawn can accept socket file descriptors when started for socket activation. This allow socket activated nspawn containers. + logind can now automatically suspend/hibernate/shutdown system on idle. + ConditionACPower can be used in unit file to detect if AC power source is connected or if system is on battery power. + EnvironmentFile= in unit files supports file globbing. + Behaviour of PrivateTmp=, ReadWriteDirectories=, ReadOnlyDirectories= and InaccessibleDirectories= has changed. The private /tmp and /var/tmp directories are now shared by all processes of a service (which means ExecStartPre= may now leave data in /tmp that ExecStart= of the same service can still access). When a service is stopped its temporary directories are immediately deleted (normal clean-up with tmpfiles is still done in addition to this though). + Resource limits (as exposed by cgroup controlers) can be controlled dynamically at runtime for all units, using "systemctl set-cgroup-attr foobar.server cgroup.attribute value". Those settings are stored persistenly on disk. + systemd-vconsole-setup will now copy all fonts settings to all allocated VTs. + timedated now exposes CanNTP property to indicate if a local NTP service is available. + pstore file system is mounted by default, if available. + SMACK policies are loaded at early boot, if available. + Timer units now support calendar time events. + systemd-detect-virt detect xen PVs. + Some distributions specific LSB targets has been dropped: $x-display-manager, $mail-transfer-agent, $mail-transport-agent, $mail-transfer-agent, $smtp, $null. As well mail-transfer-agent.target and syslog.target has been removed. + systemd-journal-gatewayd gained SSL support and now runs as unprivileged user/group "systemd-journal-gateway:systemd-journal-gateway" + systemd-analyze will read, when available, boot time performance from EFI variable from boot loader supporting it. + A new generator for automatically mounting EFI System Partition (ESP) to /boot (if empty and no other file system has been configured in fstab for it). + logind will now send out PrepareForSleep(false) out unconditionally, after coming back from suspend. + tmpfiles gained a new "X" line type, that allows configuration of files and directories (with wildcards) that shall be excluded from automatic cleanup ("aging"). + udev default rules set the device node permissions now only at "add" events, and do not change them any longer with a later "change" event. + A new bootctl tool has been added that is an interface for certain EFI boot loader operations. + A new tool kernel-install has been added to install kernel images according to Boot Loader Specification. + A new tool systemd-activate can be used to test socket activation. + A new group "systemd-journal" is now owning journal files, replacing "adm" group. + journalctl gained "--reverse" to show output in reverse order, "--pager-end" to jump at the end of the journal in the pager (only less is supported) and "--user-unit" to filter for user units. + New unit files has been addedto ease for systemd usage in initrd. + "systemctl start" now supports "--irreversible" to queue operations which can be reserved. It is now used to make shutdown requests more robust. + Auke Kok's bootchart has been merged and relicensed to LGPLv2.1+. + nss-myhostname has been merged in systemd codebase. + some defaults sysctl values are now set by default: the safe sysrq options are turned on, IP route verification is turned on, and source routing disabled. The recently added hardlink and softlink protection of the kernel is turned on. + journald will now explicitly flush journal files to disk at the latest 5 min after each write and will mark file offline until next read. This should increase reliability in case of crash. + remote-fs-setup.target target has been added to pull in specific services when at least one remote file system is to be mounted. + timers.target and paths.target have been added as canonical targets to pull user timer and path units, similar to sockets.targets. + udev daemon now sets default number of worker processes in parallel based on number of CPUs instead of RAM. + Most unit file settings which takes likst of items can now be reset by assigning empty string to them, using drop-in. + Add support for drop-in configuration file for units. + Most unit file settings which takes likst of items can now be reset by assigning empty string to them, using drop-in. + 'hostnamectl set-hostname' allows setting FQDN hostnames. + fractional time intervals are now parsed properly. + localectl can list available X11 keymaps. + systemd-analyze dot can filter for specific units and has been rewritten in C. + systemctl gained "list-dependencies" command. + Inhibitors are now honored no only in GNOME. + 'systemctl list-jobs' got some polishing. '--type=' argument may now be passed more than once. 'systemctl list-sockets' has been added. + systemd gained a new unit 'systemd-static-nodes.service' that generates static device nodes earlier during boot, and can run in conjunction with udev. + systemd-nspawn now places all containers in the new /machine top-level cgroup directory in the name=systemd hierarchy. + bootchart can now store its data in the journal. + journactl can now take multiple --unit= and --user-unit= switches. + The cryptsetup logic now understands the "luks.key=" kernel command line switch. If a configured key file is missing, it will fallback to prompting the user. -- Frederic Crozat <fcrozat(a)suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 31

[opensuse-factory] KDE 4.11 in Tumbleweed testers wanted
by Greg KH 17 Sep '13

17 Sep '13

Hi all, Thanks to Jiri Slaby, it looks like we have a working KDE 4.11 release in Tumbleweed. Before I push it to the "main" Tumbleweed repo, could some people please add the: openSUSE:Tumbleweed:Testing repo to their machines, do a 'zypper dup', restart, and let me know if KDE works properly for them? As I don't run KDE here, I don't know what to expect from a "does it work or not" point of view. Also, if you saw the vim package downgrade, that should be taken care of after the build system catches up, that was due to the vim 7.4 release change in packaging, which should now be resolved, sorry about that. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 32

[opensuse-factory] /boot partition is too small when you selected "Create LVM Based Proposal"in "Suggested Partitioning" on installer .
by 1xx 15 Sep '13

15 Sep '13

Hi all . When I selected "Create LVM Based Proposal" in "Suggested Partitioning" on installer, Installer suggested "Create boot volume /dev/sda1 (156.88 MB)" . But it is too small for for updating the kernel . The present state is as follows. Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 154691 108188 38516 74% /boot rpm -qa 'kernel-desktop' kernel-desktop-3.7.10-1.16.1.x86_64 kernel-desktop-3.7.10-1.11.1.x86_64 Disk storage capacity runs short in update of the next kernel . In the past, disk storage capacity actually ran short by update of the kernel . I think that the /boot partition should be more than 256 M byte required. (ex: 1 G byte) I wrote https://bugzilla.novell.com/show_bug.cgi?id=826981 . I want you to tell your opinions . -- 1xx <ItSANgo(a)gmail.com> <https://twitter.com/ItSANgo> <http://d.hatena.ne.jp/Itisango/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 47

[opensuse-factory] a stop job is running for Session 1 of user root
by Felix Miata 13 Sep '13

13 Sep '13

This has been delaying both init and shutdown by at least a minute on several 13.1 systems for more than a week, maybe more than a month. Is anyone else seeing it? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 6

[opensuse-factory] python-gobject and python3-gobject
by Todd Rme 09 Sep '13

09 Sep '13

Currently python-gobject in the devel:languages:python and python3-gobject in devel:languages:python3 are separated into two packages. However, python-gobject is linked to the version on openSUSE:Factory, which still has python 2 and python 3 spec files in one package. Its devel project is GNOME:Factory, which also still has both spec files. This is leading to frequency breakage in the devel:languages:python version, since it links to a package that has two spec files while it only has one. If we are going to go with the separate packages we should to it in factory as well. It would be easy to provide a submit request for this. However, currently python3-gobject in openSUSE:Factory and GNOME:Factory are linked to their respective python-gobject packages, so doing the submission now would break python3-gobject. So if we are going to go with the separate python2 and python3 packages, can we do so for python-gobject as well? If not, we need to either unlike python-gobject from factory, go back to using two spec files, or remove it from devel:languages:python entirely (which may not be a bad idea since it often depends on the latest GTK version anyway). -- 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] pax is not tar
by Felix Miata 03 Sep '13

03 Sep '13

In 13.1M4, I did tar -cvf /mnt/usb/stuff.tar file1.ts file2.ts file3.ts On /mnt/usb was a NTFS formatted USB stick. The object of tarring was to preserve all native file attributes while transversing the foreign formatted media. After ejecting, I put it into a USB port on a Linux STB running busybox v1.0. After it automounted, I changed to the desired destination for extraction, and then tar -xvf <mountpoint>/stuff.tar . That gave me $SUBJECT. Apparently busybox tar isn't very smart. I've done this before successfully, making me believe something about tar in 13.1 is different. Is it? Is it a bug? Since I'm dealing with huge media files, experimenting is a lengthy process. I can't tell from the 13.1 tar man page what option might make busybox tar able to extract from a 13.1 tar file. Anyone know what's going on here? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

12 46

[opensuse-factory] OSS radeon driver craps with 3.10.x kernels form Tumbleweed
by Jimmy Berry 01 Sep '13

01 Sep '13

Since updating to 3.10.x kernels I am no longer able to boot my machine due to an error spit out from radeon driver. A sample from /var/log/messages, http://paste.kde.org/pa0a82f91/raw/. Key area of log included below. 2013-08-28T20:06:02.694885-07:00 boomba kernel: [ 6.108048] CPU: 4 PID: 1172 Comm: Xorg Not tainted 3.10.7-23.g771dec3-desktop #1 2013-08-28T20:06:02.694885-07:00 boomba kernel: [ 6.108451] Hardware name: System manufacturer System Product Name/SABERTOOTH Z77, BIOS 1504 08/03/2012 2013-08-28T20:06:02.694886-07:00 boomba kernel: [ 6.108957] task: ffff8807f22aa2c0 ti: ffff8807f283c000 task.ti: ffff8807f283c000 2013-08-28T20:06:02.694887-07:00 boomba kernel: [ 6.109358] RIP: 0010:[<ffffffffa02844e8>] [<ffffffffa02844e8>] radeon_vm_bo_add+0xa8/0xf0 [radeon] 2013-08-28T20:06:02.694888-07:00 boomba kernel: [ 6.109865] RSP: 0018:ffff8807f283db68 EFLAGS: 00010286 2013-08-28T20:06:02.694888-07:00 boomba kernel: [ 6.110147] RAX: ffff8807f45f0b50 RBX: ffff8807f1536840 RCX: 0000000000000000 2013-08-28T20:06:02.694889-07:00 boomba kernel: [ 6.110530] RDX: 0000000000000060 RSI: 0000000000000000 RDI: ffff8807f45f0b80 2013-08-28T20:06:02.694890-07:00 boomba kernel: [ 6.110912] RBP: ffff8807f45f0b40 R08: ffffffff81c34220 R09: ffff8807f1536840 2013-08-28T20:06:02.694890-07:00 boomba kernel: [ 6.111299] R10: 000000000e200000 R11: 0000000000000000 R12: 0000000000000000 2013-08-28T20:06:02.694891-07:00 boomba kernel: [ 6.111299] R13: ffff8807f1536870 R14: ffff8807f45f0b80 R15: ffff8807f1b64800 2013-08-28T20:06:02.694892-07:00 boomba kernel: [ 6.111300] FS: 00007ff8a36d5880(0000) GS:ffff88081ed00000(0000) knlGS:0000000000000000 2013-08-28T20:06:02.694893-07:00 boomba kernel: [ 6.111301] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 2013-08-28T20:06:02.694893-07:00 boomba kernel: [ 6.111302] CR2: 00000000000001f8 CR3: 00000007f5acd000 CR4: 00000000001407e0 2013-08-28T20:06:02.694894-07:00 boomba kernel: [ 6.111303] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 2013-08-28T20:06:02.694895-07:00 boomba kernel: [ 6.111303] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 2013-08-28T20:06:02.694895-07:00 boomba kernel: [ 6.111304] Stack: 2013-08-28T20:06:02.694905-07:00 boomba kernel: [ 6.111306] ffff8807f5eb8000 ffff8807f0e6f0a0 ffff8807f0d6dc00 ffff8807f45f0b40 2013-08-28T20:06:02.694906-07:00 boomba kernel: [ 6.111308] ffff8807f0d6dc00 ffffffffa026c543 ffff8807f22aa2c0 ffff8807f0e6f0a0 2013-08-28T20:06:02.694906-07:00 boomba kernel: [ 6.111310] ffff8807f1b64820 ffff8807f56572c0 ffff8807f0d6dc20 ffffffffa00e826a 2013-08-28T20:06:02.694907-07:00 boomba kernel: [ 6.111310] Call Trace: 2013-08-28T20:06:02.694908-07:00 boomba kernel: [ 6.111350] [<ffffffffa026c543>] radeon_driver_open_kms+0x83/0xe0 [radeon] 2013-08-28T20:06:02.694908-07:00 boomba kernel: [ 6.111363] [<ffffffffa00e826a>] drm_open+0x28a/0x6f0 [drm] 2013-08-28T20:06:02.694909-07:00 boomba kernel: [ 6.111371] [<ffffffffa00e87d6>] drm_stub_open+0x106/0x1a0 [drm] 2013-08-28T20:06:02.694910-07:00 boomba kernel: [ 6.111378] [<ffffffff81182446>] chrdev_open+0x96/0x1d0 2013-08-28T20:06:02.694911-07:00 boomba kernel: [ 6.111383] [<ffffffff8117ba56>] do_dentry_open+0x216/0x2a0 2013-08-28T20:06:02.694911-07:00 boomba kernel: [ 6.111386] [<ffffffff8118ac21>] do_last+0x2d1/0xed0 2013-08-28T20:06:02.694912-07:00 boomba kernel: [ 6.111389] [<ffffffff8118c776>] path_openat+0xc6/0x4b0 2013-08-28T20:06:02.694912-07:00 boomba kernel: [ 6.111391] [<ffffffff8118daf4>] do_filp_open+0x44/0xb0 2013-08-28T20:06:02.694913-07:00 boomba kernel: [ 6.111393] [<ffffffff8117cdc3>] do_sys_open+0xf3/0x1e0 2013-08-28T20:06:02.694914-07:00 boomba kernel: [ 6.111397] [<ffffffff815def7f>] tracesys+0xe1/0xe6 2013-08-28T20:06:02.694915-07:00 boomba kernel: [ 6.111402] [<00007ff8a28ecaf0>] 0x7ff8a28ecaef 2013-08-28T20:06:02.694915-07:00 boomba kernel: [ 6.111413] Code: 89 43 08 4c 89 68 30 4c 89 68 38 e8 b3 fe 34 e1 48 8b 45 10 4c 89 f7 4c 89 68 08 48 89 43 30 48 8d 45 10 48 89 43 38 4c 89 6d 10 <49> 8b 84 24 f8 01 00 00 49 89 9c 24 f8 01 00 00 49 81 c4 f0 01 2013-08-28T20:06:02.694916-07:00 boomba kernel: [ 6.111420] RIP [<ffffffffa02844e8>] radeon_vm_bo_add+0xa8/0xf0 [radeon] 2013-08-28T20:06:02.694917-07:00 boomba kernel: [ 6.111420] RSP <ffff8807f283db68> 2013-08-28T20:06:02.694918-07:00 boomba kernel: [ 6.111421] CR2: 00000000000001f8 2013-08-28T20:06:02.797420-07:00 boomba kernel: [ 6.214066] ---[ end trace f4ca0545372eb72b ]--- 2013-08-28T20:06:02.797658-07:00 boomba kdm[1130]: X server died during startup 2013-08-28T20:06:02.797910-07:00 boomba kdm[1130]: X server for display :0 cannot be started, session disabled I noticed the following. kernel-desktop tumbleweed kernel-firmware tubmbleweed libdrm_radeon1 openSUSE (2.4.42) Just a guess, but could the radeon package use an update for 3.10.x series? The kernel that I am using that works is as follows. $ uname -a Linux boomba.site 3.9.4-11.g51bf0ff-desktop #1 SMP PREEMPT Fri May 24 19:52:42 UTC 2013 (51bf0ff) x86_64 x86_64 x86_64 GNU/Linux A side note, the fglrx packages from AMD work with 3.10.x kernels which is why I did not notice right away. Decided to switch back to OSS drivers after I was done experimenting with fglrx and 3D stuff. Any thoughts would be appreciated. -- Jimmy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] Broken lvm2 after recent systemd change; bnc 837954
by Lars Müller 31 Aug '13

31 Aug '13

Hi, lvm of factory is broken at the moment. At least I had not been able to boot after a recent update. The quick fix is to sym link it: ln -s /sbin/lvm /usr/sbin/lvm At the long run we need to fix this. In bnc 837954 I suggested to create scripts/lvm2_activation_generator_systemd_red_hat.c.in and to generate scripts/lvm2_activation_generator_systemd_red_hat.c by replacing the sbin directory as set while we called configure. With osc getbinaries you're able to download packages and test them. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

1 0