August 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "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 For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

Re: [opensuse-factory] repository priorities with Tumbleweed
by Thomas Langkamp 16 Jul '15

16 Jul '15

> No, please don't confuse people, if you add more repos than just > Tumbleweed you really had better know what you are doing or bad things > can, and will, happen :) I understand. I just would like to add the following to http://en.opensuse.org/Portal:Tumbleweed - between ## is the new stuff: "The only supported method of repo use for Tumbleweed is to have only the main repos (Oss, Non-oss, and Update) and the Tumbleweed repo active. ## If you use more repositorys you have to know how repo-priorities work, but even then Tumblweed does NOT support this ## " It would also be good to move this information to "Special concerns" and to move the whole "Special concerns"-section up. For example "Special Concerns Virtual Machines ... Third Party Drivers ... ## Non-Standard Repos: Only use Oss, Non-oss, and Update combined with the Tumbleweed-Standard repo. Everything else is not supported and might break the system ## " >You do know the legal reasons behind why packman is there, right? Yes. Then I do not whish you personaly to support Packman with TW - I understand now that this is not possible from your perspectivg. But...as the OS community discusses right now if/how to strengthen Tumbleweed... one way would be, that Packman+TW would be supported BY Packman. So I will ask the Packman-guys to do that... I hope this is possible for them. Without Packman Tumbleweed is so ... "anti-multimedia" ;) thanks anyway :D -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 18

[opensuse-factory] Export broken for KinfoCenter
by Roger Luedecke 30 Jan '15

30 Jan '15

Export button is greyed out no matter what. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] New Package - libhal1-flash (re-enabling Flash-Player DRM content on Linux)
by Christopher Horler 13 Sep '14

13 Sep '14

Good afternoon! I've written and packaged a compatibility library for flash to enable playback of DRM content (this removes the dependency on the HAL package). I'd like to know what steps I can take to have the package considered for inclusion in openSUSE 12.3 and 13.1. Can I submit the package to devel:openSUSE:Factory, or is there another action I should be taking? Details of the bug and links to upstream are here (please briefly review): https://bugzilla.novell.com/show_bug.cgi?id=768562#c19 OBS location: https://build.opensuse.org/package/show?package=hal-flash&project=home%3Ach… I will maintain the package until such time that HTML5 Video content is a viable alternative or the Flash plugin is completely withdrawn. RPMs, debs... are all available on the build service. Three noteworthy points: - package naming (libhal1-flash) doesn't 100% align with the Shared Library Policy (I've suffixed -flash to make clear this is not a fully functional HAL layer and also to avoid naming conflicts as some distros seem to have a shared library package already named libhal1). - The packages depends on dbus and udisks. It seems to work find when udisks is launched on demand (as for openSUSE 12.3) - The flash-player package could have some kind of RPM dependency on this package to assist the user when looking in YaST (Install / Remove Software) / Package Manager. Chris -- 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] source_validator error: signature does not validate
by Kyrill Detinov 25 Aug '14

25 Aug '14

Hello. I can't build a package. Service source_validator failed. % osc build Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpVbBhay Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector.keyring gpg: enabled debug flags: memstat gpg: keyring `/tmp/check_if_valid_source_dir-NL8Ezs/.checkifvalidsourcedir-gpg-keyring' created gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: key 015475F5: public key "Jakub Wilk <jwilk(a)jwilk.net>" imported gpg: Total number processed: 1 gpg: imported: 1 (RSA: 1) random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks gpg: enabled debug flags: memstat gpg: Signature made Mon Jun 24 22:36:51 2013 MSK using RSA key ID 015475F5 gpg: Oops: keyid_from_fingerprint: no pubkey gpg: Oops: keyid_from_fingerprint: no pubkey gpg: key 00000000 occurs more than once in the trustdb gpg: Good signature from "Jakub Wilk <jwilk(a)jwilk.net>" gpg: aka "Jakub Wilk <jwilk(a)debian.org>" gpg: aka "Jakub Wilk <ubanus(a)users.sf.net>" random usage: poolsize=600 mixed=0 polls=0/0 added=0/0 outmix=0 getlvl1=0/0 getlvl2=0/0 secmem usage: 0/32768 bytes in 0 blocks (E) signature /home/kent/rpmbuild/projects/M17N/i18nspector/i18nspector-0.11.1.tar.gz.asc does not validate Aborting: service call failed: /usr/lib/obs/service/source_validator --outdir /tmp/tmpIQYU6i Source service run failed! As far as I can see, the signature is good. This also happens with another package (graphics/icoutils). What is the problem? -- WBR Kyrill

2 5

[opensuse-factory] libav and multimedia idea
by Tomáš Chvátal 14 May '14

14 May '14

Hello guys, I have created proof of concept libav library with disabled patented codecs in my home project [1]. This means that this library si up par with what we have in chromium and it should be legal to distribute. Apart from the library the repo contains vlc chromium and xbmc (built localy fails on obs, meh) which seems to run fine, just not to play almost anything ^_^. The possibility here is to include all the media players and stuff around it into openSUSE release, where one has to flip the switch in libav (see the spec file) and can build full-fledged-european-edition which can play our sweet movies. Let me know what you think about this plan and what would you use as base devel project for this. Cheers Tom [1] https://build.opensuse.org/project/show?project=home%3Ascarabeus_iv

8 11

[opensuse-factory] YaST2 "install/remove" doesn't display solver diagram
by Kyrill Detinov 13 Jan '14

13 Jan '14

Hello. There is a regression in YaST2 *Qt* "install/remove software" module. It doesn't show solver diagram. First, no dependencies on libqdialogsolver. Second, installed libqdialogsolver doesn't help. Reported ages ago. And confirmed. All the info is provided. https://bugzilla.novell.com/show_bug.cgi?id=785431 WBR Kyrill

3 3

Re: [opensuse-factory] Nothing provides /usr/bin/php5
by Sascha Peilicke 11 Jan '14

11 Jan '14

On 12/01/2011 11:44 AM, Kyrill Detinov wrote: > > Hello. > > We have one package affected in standard repo: leechcraft-eiskaltdcpp. > The program itself doesn't require php5. But the package includes > example scripts with shebang '!/usr/bin/php5'. So the package isn't > installable. > > Also I see the same problem with pgfouine from Contrib (written in > PHP) and eiskaltdcpp from filesharing repo. Maybe more in third-party > repositories. > > Can we have symlink /usr/bin/php -> php5 in php5 package? Or affected > packages should be fixed? > Please file a bug against php5 and assign to Cristian Rodríguez. -- Viele Grüße, Sascha -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 4

Re: [opensuse-factory] SOLVED: postfix does not run
by Christian Boltz 06 Nov '13

06 Nov '13

Hello, Am Freitag, 22. März 2013 schrieb Patrick Shanahan: > /etc/postfix/main.cf had @_some-parameter_@ setting for every > "xxxxxxx_directory =" line. > > After correcting "xxxxxxxx_directory =" settings per my Tumbleweed > machine, postfix appears working correctly. > > This mess probably occurred on installing/upgrading postfix: > postfix-2.9.6-2.1.x86_64 Sun Mar 10 11:14:39 2013 > but the rpm main.cf does not contain "@.............@". This sounds like https://bugzilla.novell.com/show_bug.cgi?id=796162 which should be fixed since some time. I'd guess some older postfix package broke your main.cf. Nevertheless, if you want to be really sure, uninstall postfix, move away /etc/postfix and re-install the postfix package. Regards, Christian Boltz -- Argh, ich wollte heute doch gar nicht mehr siggen! [Michael Hoffmann in dag°] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] brcms oops after tethering WLAN connection
by s131 03 Nov '13

03 Nov '13

Hi, I'm following factory closely and since about more then one week it is no longer possible for me to use tethering my notebook with my Nexus 4 over WLAN: Actually setting up the connection with NetworkManager is no problem. But if I do a HTTP request with a browser, my notebook will immediately and reliably get a kernel Oops, leaving me at the terminal with a blinking keyboard LED and no interaction possible. With a normal WLAN connection I do not have this problem! The circumstances of the problem and the kernel backtrace I get are the same as described in https://lkml.org/lkml/2013/8/19/549: > brcms_c_compute_rtscts_dur > brcms_c_ampdu_finalize > ampdu_finalize > dma_txfast > brcms_c_txfifo > brcms_c_sendpkt_mac80211 > brcms_ops_tx Since the LKML post suggests that this problem may be fixed with 3.11-rc6, I waited until 3.11-rc6 appeared downstream on factory But the problem did not disappear. Unfortunately the LKML post does not mention a bugzilla entry. Can anyone reproduce this problem? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[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

[opensuse-factory] Fatal Python error: pycurl: libcurl link-time version is older than compile-time version
by doiggl＠velocitynet.com.au 30 Aug '13

30 Aug '13

Hello, Which package needs updating to fix following error[1] -- Thanks Glenn [1] Fatal Python error: pycurl: libcurl link-time version is older than compile-time version. -- 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] Shorewall for 13.1
by toganm＠opensuse.org 29 Aug '13

29 Aug '13

Hi, I have just submitted newest shorewall to factory sr# 196694. Since it is a leaf package it would be great if it is included in 13.1. I have added a comment via the webui for this as well. I know coolo doesn't like changing horses during the course but this is a leaf package, it should not harm ;=) Thanks Togan -- Life is endless possibilities -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] nfsserver doesn't start
by Stefan Zimmer 28 Aug '13

28 Aug '13

I was trying to setup a new NAS server, based on suse-tumbleweed, but cannot start nfsserver. in the file /etc/init.d/nfsserver, on line 33, the "/etc/rc.status" file is sourced. But in this file, on line 63, systemctl is called, which causes a "no such file or directory" error. Any suggestions? Thanks, Zingel -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 9

Re: [opensuse-factory] Re: Qt in KDE:Qt problems
by Marguerite Su 27 Aug '13

27 Aug '13

On Tue, Aug 27, 2013 at 6:54 PM, Cristian Morales Vega <reddwarf(a)opensuse.org> wrote: >> Or just typing in the proper library name. > > > Guys, being explicit doesn't hurt. > > They are talking about -lpthreads vs -lpthread. Notice the extra 's'. > > Not that it solves your problem. But it may be a hint... Now I understand your guys concern. Interestingly, neither '-lpthreads' nor '-lpthread' occur in kmoefm's source code. And I didn't make a typo. The "-lpthreads" comes from build/CMakeFiles/CMakeError.log But: -- Looking for include file pthread.h -- Looking for include file pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - not found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Performing Test __KDE_HAVE_GCC_VISIBILITY -- Performing Test __KDE_HAVE_GCC_VISIBILITY - Success Both pthread_create and -fvisibility-hidden seem to get found already. Any more clues? Greetings Marguerite -- 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] Qt in KDE:Qt problems
by Marguerite Su 27 Aug '13

27 Aug '13

Hi, listmates, Recently I updated my 12.3 to K:R:411 with all of its Qt packages. (The Qt related packages in 411 are aggregated from KDE:Qt project) Then I need to local build some stuff. https://github.com/csslayer/kmoefm But cmake fails at a simple: find_package(KDE4 required) and suspect: CMake Error at /usr/share/kde4/apps/cmake/modules/FindKDE4Internal.cmake:1294 (message): Qt compiled without support for -fvisibility=hidden. This will break plugins and linking of some applications. Please fix your Qt installation (try passing --reduce-exports to configure). /usr/share/cmake/Modules/FindKDE4.cmake:95 (find_package) CMakeLists.txt:6 (find_package) which is not true. Because our Qt did compiled with that gcc-c++ flag. https://build.opensuse.org/package/rawlog/KDE:Qt/libqt4/openSUSE_12.3/x86_64 (grep "-fvisibility=hidden") Futher, in build/CMakeFiles/CMakeError.log: error: ‘Q_WS_WIN’ undeclared (first use in this function) error: ‘Q_WS_QWS’ undeclared (first use in this function) error: ‘Q_WS_MAC’ undeclared (first use in this function) undefined reference: ‘pthread_create’ cannot find -lpthreads which is really weird, because Q_WS_* is the basic env test for any Qt...and pthread is a basic Linux function coming from glibc-devel installed. But... I make a package on OBS: https://build.opensuse.org/package/show/home:MargueriteSu/kmoefm download the 12.3 srpm, `rpmbuild --rebuild` it, no problem at all. I think the rebuild environment is exactly the same environment of your local build while now the outputs are different. Can any experienced guys with 12.3 & 411 please cmake the `kmoefm` project and examine what happened? Greetings Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3