fedora-review and/or pkgdb problem?
by Tom Hughes
Attempts to run fedora-review seem to be failing today (it was working a
couple of days ago) when it tries to query pkgdb to see if there is
already a package with the same name:
02-23 14:44 requests.packages.urllib3.connectionpool DEBUG "POST
https://admin.fedoraproject.org/pkgdb/acls/name/nodejs-ms HTTP/1.1" 200 1800
02-23 14:44 root DEBUG Exception down the road...
Traceback (most recent call last):
File
"/usr/lib/python2.7/site-packages/FedoraReview/review_helper.py", line
183, in run
self._do_run()
File
"/usr/lib/python2.7/site-packages/FedoraReview/review_helper.py", line
176, in _do_run
self.__do_report()
File
"/usr/lib/python2.7/site-packages/FedoraReview/review_helper.py", line
75, in __do_report
self.__run_checks(self.bug.spec_file, self.bug.srpm_file)
File
"/usr/lib/python2.7/site-packages/FedoraReview/review_helper.py", line
89, in __run_checks
writedown=not Settings.no_report)
File "/usr/lib/python2.7/site-packages/FedoraReview/checks.py", line
310, in run_checks
run_check(name)
File "/usr/lib/python2.7/site-packages/FedoraReview/checks.py", line
292, in run_check
check.run()
File
"/usr/lib/python2.7/site-packages/FedoraReview/plugins/generic.py", line
2025, in run
p.get_package_info(name)
File "/usr/lib/python2.7/site-packages/fedora/client/pkgdb.py", line
139, in get_package_info
req_params=data)
File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py",
line 344, in send_request
auth_params=auth_params, retries=retries)
File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py",
line 394, in send_request
if 'exc' in data:
TypeError: argument of type 'NoneType' is not iterable
I'm not quite sure if this is a bug in fedora-review, python-fedora, or
whether pkgdb is returning broken responses or something?
Tom
--
Tom Hughes (tom(a)compton.nu)
http://compton.nu/
11 years, 2 months
Odd error message on build blender-2.66-1.fc19
by Jochen Schmitt
Hello,
I have tried to build the recent released version of blender. But unfotunately,
I have got the following odd error message:
+ /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/blender-2.66
extracting debug info from /builddir/build/BUILDROOT/blender-2.66-1.fc19.x86_64/usr/bin/blender
/usr/lib/rpm/debugedit: canonicalization unexpectedly shrank by one character
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.lr1DY2 (%install)
bogus date in %changelog: Sun Jan 30 2006 Jochen Schmitt <Jochen herr-schmitt de> 2.41-1
So I would to like to ask, if anyone have an idea about the error message
relating to /usr/lib/rpm/debugedit?
Thanks in advance.
Best Regards:
Jochen Schmitt
11 years, 2 months
Re: is it possible to download a spec file only using yum?
by poma
On 02/21/13 10:39, Matthew Miller wrote:
> On Wed, Feb 20, 2013 at 07:16:08PM -0600, Ranjan Maitra wrote:
>> I was wondering if it is possible to download a spec file using yum
>> or rpm only (without downloading the rpm)?
>
> No, but there's a better way! All of our spec files are available in git,
> and the "fedpkg" command is a nice wrapper around access to the repository.
> So:
>
> $ sudo yum install fedpkg
> [...]
> $ fedpkg clone firefox
> Cloning into 'firefox'...
> remote: Counting objects: 3234, done.
> remote: Compressing objects: 100% (1979/1979), done.
> remote: Total 3234 (delta 1702), reused 2424 (delta 1210)
> Receiving objects: 100% (3234/3234), 741.50 KiB | 313 KiB/s, done.
> Resolving deltas: 100% (1702/1702), done.
[…]
fedpkg --user poma -v clone firefox
Cloning ssh://poma@pkgs.fedoraproject.org/firefox
Running git clone ssh://poma@pkgs.fedoraproject.org/firefox directly on
the tty
Cloning into 'firefox'...
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Could not execute clone: Command '['git', 'clone',
'ssh://poma@pkgs.fedoraproject.org/firefox']' returned non-zero exit
status 128
--
In contrast:
fedpkg -v clone -a firefox
Cloning git://pkgs.fedoraproject.org/firefox
Running git clone git://pkgs.fedoraproject.org/firefox directly on the tty
Cloning into 'firefox'...
remote: Counting objects: 3234, done.
remote: Compressing objects: 100% (1979/1979), done.
remote: Total 3234 (delta 1704), reused 2424 (delta 1210)
Receiving objects: 100% (3234/3234), 708.87 KiB | 372 KiB/s, done.
Resolving deltas: 100% (1704/1704), done.
--
Shouldn't the default be an '-a'(anonymous) check out via git?
Cheers,
poma
11 years, 2 months
Finding build.log for an automatic build that failed.
by Brad Bell
In the bugzilla report below, the link
http://koji.fedoraproject.org/koji/taskinfo?taskID=4959059
works but the other links below do not.
If I follows the link above, I see the message
Result
BuildError: error building package (arch i686), mock exited with
status 1; see build.log for more information
How can I view the corresponding build log ?
On 02/13/2013 10:39 PM, Fedora Koji Build System wrote:
> Package: cppad-20130000.1-2.fc19
> Tag: f19-rebuild
> Status: failed
> Built by: ausil
> ID: 385392
> Started: Thu, 14 Feb 2013 05:11:34 UTC
> Finished: Thu, 14 Feb 2013 05:38:28 UTC
>
>
> cppad-20130000.1-2.fc19 (385392) failed on buildvm-22.phx2.fedoraproject.org (noarch), buildvm-15.phx2.fedoraproject.org (i386):
> BuildError: error building package (arch i686), mock exited with status 1; see build.log for more information
> SRPMS:
> cppad-20130000.1-2.fc19.src.rpm
>
> Failed tasks:
> -------------
>
> Task 4959059 on buildvm-22.phx2.fedoraproject.org
> Task Type: build (f19-rebuild, /cppad:04addcea97a7712c526b8696f35087605a5891e3)
>
> Task 4966918 on buildvm-15.phx2.fedoraproject.org
> Task Type: buildArch (cppad-20130000.1-2.fc19.src.rpm, i686)
> logs:
> http://koji.fedoraproject.org/koji/getfile?taskID=4966918&name=build.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966918&name=mock_outpu...
> http://koji.fedoraproject.org/koji/getfile?taskID=4966918&name=root.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966918&name=state.log
>
>
> Canceled tasks:
> ---------------
>
> Task 4966916 on buildvm-02.phx2.fedoraproject.org
> Task Type: buildArch (cppad-20130000.1-2.fc19.src.rpm, x86_64)
> logs:
> http://koji.fedoraproject.org/koji/getfile?taskID=4966916&name=build.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966916&name=mock_outpu...
> http://koji.fedoraproject.org/koji/getfile?taskID=4966916&name=root.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966916&name=state.log
>
>
> Closed tasks:
> -------------
>
> Task 4966584 on buildvm-02.phx2.fedoraproject.org
> Task Type: buildSRPMFromSCM (/cppad:04addcea97a7712c526b8696f35087605a5891e3)
> logs:
> http://koji.fedoraproject.org/koji/getfile?taskID=4966584&name=build.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966584&name=checkout.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966584&name=mock_outpu...
> http://koji.fedoraproject.org/koji/getfile?taskID=4966584&name=root.log
> http://koji.fedoraproject.org/koji/getfile?taskID=4966584&name=state.log
>
>
>
> Task Info: http://koji.fedoraproject.org/koji/taskinfo?taskID=4959059
> Build Info: http://koji.fedoraproject.org/koji/buildinfo?buildID=385392
>
11 years, 2 months
Orphaning PycURL
by Jeffrey Ollie
Hello,
I am going to be orphaning the PycURL package... Upstream is dead,
the last new release was in 2008. Yet, PycURL is a critical part of
Fedora as Yum uses it to download metadata and packages.
The final straw is that the package failed to build in the latest mass rebuild:
https://bugzilla.redhat.com/show_bug.cgi?id=914411
There are a number of other bugs associated with PycURL, but I didn't
want to become the de facto upstream so I've resisted efforts to apply
patches to the code.
Personally, I'd like to see Yum move away from PycURL but if someone
wants to take over upstream development more power to them.
--
Jeff Ollie
11 years, 2 months
systemd vs. SysV init script in .spec files for new packages
by Nico Kadel-Garcia
Good morning, folks:
I've been publishing a few packages for Repoforge and sent occasional
updates to EPEL, and I'd be happy to start getting them into Fedora.
While I work out how koji works, I note that the new use of systemd
means that the same SRPM cannot be used for both Fedora 18, and for
anything that runs a daemon and should be ported to EPEL.
I'm happy to write tools that use init scripts, or systemd scripts,
based on OS version. But are there best practices? Is anyone else
actually testing the code on RHEL or CentOS for cross compatibility,
to ease EPEL work and backporting to RHEL releases?
There's an example in my working backport of Samba 4.0.3 to RHEL 6, at
https://github.com/nkadel/samba-4.0.3-srpm/blob/master/samba.spec
The critical code, lifted from the current samba-4.03 package and tweaked, is:
# Use systemd, not SysV init scripts, as appropriate
%if 0%{?fedora} > 15 || 0%{?rhel} > 6
%global with_systemd 1
%else
%global with_systemd 0
%endif
I've also noticed that the use of the "rhel" macro can be a bit
confusing, since it's only been a standard part of RPM setups since
RHEL 6. For older releases such as RHEL 5, it's apparently built into
koji, but needs te be set for individual developers or software build
environments in $HOME/.rpmmacros otherwise. That's not critical for
recent Fedora releases, but may affect people like me who try to
backport tools from Fedora 18 or Fedora 19 to older systems.
Also note that the with_systemd macro *must* be defined as 0 for false
values, or later uses of this syntax fail miserably on older
operating systems, like RHEL 6.
%if %with_systemd
Requires(post): systemd
Requires(preun): systemd
Requires(postun): systemd
%else
Requires(post): /sbin/chkconfig, /sbin/service
Requires(preun): /sbin/chkconfig, /sbin/service
Requires(postun): /sbin/chkconfig, /sbin/service
%endif
Frankly, I'd prefer to use "%if 0%{with_systemd}", but that's a
syntactic choice I can work with either way. I just want to set and
follow a spec.
That's just an example: the full backport is at
https://github.com/nkadel/samba-4.0.3-srpm/
11 years, 2 months
kernel warning in btrfs
by Neal Becker
I'm not reporting, cause kernel was tainted by virtualbox, but should I be
worried?
Feb 22 09:21:58 nbecker1 kernel: [76101.244542] ------------[ cut here
]------------
Feb 22 09:21:58 nbecker1 kernel: [76101.244582] WARNING: at
fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xf4/0x100 [btrfs]()
Feb 22 09:21:58 nbecker1 kernel: [76101.244584] Hardware name: HP Pavilion
dv9500 Notebook PC
Feb 22 09:21:58 nbecker1 kernel: [76101.244586] Modules linked in: lp parport
vfat fat usb_storage vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) fuse
ip6table_filter ip6_tables ebtable_nat ebtables rfcomm bnep be2iscsi
iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser
nf_conntrack_ipv4 nf_defrag_ipv4 rdma_cm xt_conntrack ib_addr nf_conntrack iw_cm
ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi
btusb bluetooth snd_hda_codec_si3054 snd_hda_codec_realtek iTCO_wdt
iTCO_vendor_support hp_wmi sparse_keymap coretemp snd_hda_intel snd_hda_codec
snd_hwdep snd_seq snd_seq_device snd_pcm arc4 microcode iwl4965 i2c_i801
iwlegacy mac80211 r592 snd_page_alloc lpc_ich memstick r8169 mfd_core snd_timer
cfg80211 rfkill snd mii soundcore vhost_net tun macvtap macvlan kvm_intel kvm
uinput btrfs libcrc32c zlib_deflate sdhci_pci sdhci nouveau mmc_core mxm_wmi
i2c_algo_bit drm_kms_helper firewire_ohci ttm drm firewire_core crc_itu_t
i2c_core wmi video
Feb 22 09:21:58 nbecker1 kernel: [76101.244644] Pid: 246, comm: btrfs-transacti
Tainted: GF C O 3.7.9-201.fc18.x86_64 #1
Feb 22 09:21:58 nbecker1 kernel: [76101.244646] Call Trace:
Feb 22 09:21:58 nbecker1 kernel: [76101.244653] [<ffffffff8105e6df>]
warn_slowpath_common+0x7f/0xc0
Feb 22 09:21:58 nbecker1 kernel: [76101.244656] [<ffffffff8105e73a>]
warn_slowpath_null+0x1a/0x20
Feb 22 09:21:58 nbecker1 kernel: [76101.244671] [<ffffffffa0226074>]
btrfs_orphan_commit_root+0xf4/0x100 [btrfs]
Feb 22 09:21:58 nbecker1 kernel: [76101.244684] [<ffffffffa021f388>]
commit_fs_roots.isra.24+0xb8/0x190 [btrfs]
Feb 22 09:21:58 nbecker1 kernel: [76101.244699] [<ffffffffa0220238>]
btrfs_commit_transaction+0x598/0xae0 [btrfs]
Feb 22 09:21:58 nbecker1 kernel: [76101.244702] [<ffffffff81082740>] ?
wake_up_bit+0x40/0x40
Feb 22 09:21:58 nbecker1 kernel: [76101.244716] [<ffffffffa0218ec5>]
transaction_kthread+0x1a5/0x220 [btrfs]
Feb 22 09:21:58 nbecker1 kernel: [76101.244729] [<ffffffffa0218d20>] ?
btree_readpage_end_io_hook+0x290/0x290 [btrfs]
Feb 22 09:21:58 nbecker1 kernel: [76101.244731] [<ffffffff81081e30>]
kthread+0xc0/0xd0
Feb 22 09:21:58 nbecker1 kernel: [76101.244735] [<ffffffff81010000>] ?
ftrace_raw_event_xen_mmu_flush_tlb_others+0x50/0xe0
Feb 22 09:21:58 nbecker1 kernel: [76101.244738] [<ffffffff81081d70>] ?
kthread_create_on_node+0x120/0x120
Feb 22 09:21:58 nbecker1 kernel: [76101.244742] [<ffffffff8163f92c>]
ret_from_fork+0x7c/0xb0
Feb 22 09:21:58 nbecker1 kernel: [76101.244745] [<ffffffff81081d70>] ?
kthread_create_on_node+0x120/0x120
Feb 22 09:21:58 nbecker1 kernel: [76101.244747] ---[ end trace 93a78f651a830bbb
]---
11 years, 2 months
Frequent dbus(?) crashes with Samsung 840 Pro SSD
by Digimer
Last weekend, I both a new Samsung 840 Pro 256GB SSD. Prior to this, I
was using a Corsair Performance Pro 256 SSD without issue (F17 had been
upgrade to F18 about a week before). I got the drive to do a fresh install.
From last weekend until Saturday, I would get ~2~3 hard crashes a day.
Gnome 3 would lock up hard, but I could ctrl+alt+fX to get to other
terminals. Here's my original post/thread;
http://lists.fedoraproject.org/pipermail/users/2013-February/430993.html
Two days ago, I reinstalled F18 on my Corsair drive. I had the Samsung
connected as a USB drive to restore my files and after a few hours, the
system locked up again ('tail -n 100' below). I pulled the Samsung out
of the laptop and booted with just the Corsair and it's been rock solid
since.
Each time it crashed, it *looked* like a dbus hang-up. However, I am not
a programmer so I could be way off base with this guess. Here's the last
log from the system after the last crash (when the drive was the OS
drive, I didn't get the messages from the crash when it was connected
via USB);
===============
Feb 16 11:16:25 lemass avahi-daemon[694]: New relevant interface
em1.IPv4 for mDNS.
Feb 16 11:16:25 lemass avahi-daemon[694]: Registering new address record
for 10.255.0.229 on em1.IPv4.
Feb 16 11:16:26 lemass avahi-daemon[694]: Registering new address record
for fe80::f2de:f1ff:fefc:65b3 on em1.*.
Feb 16 11:16:26 lemass NetworkManager[860]: <info> (em1): device state
change: ip-config -> secondaries (reason 'none') [70 90 0]
Feb 16 11:16:26 lemass NetworkManager[860]: <info> Activation (em1)
Stage 5 of 5 (IPv4 Commit) complete.
Feb 16 11:16:26 lemass NetworkManager[860]: <info> (em1): device state
change: secondaries -> activated (reason 'none') [90 100 0]
Feb 16 11:16:26 lemass NetworkManager[860]: <info> Policy set 'Boot
Disk' (em1) as default for IPv4 routing and DNS.
Feb 16 11:16:26 lemass NetworkManager[860]: <info> Activation (em1)
successful, device activated.
Feb 16 11:16:26 lemass systemd[1]: Starting LSB: Starts and stops login
and scanning of iSCSI devices....
Feb 16 11:16:26 lemass iscsi[6568]: Starting iscsi: iscsiadm: No records
found
Feb 16 11:16:26 lemass iscsi[6568]: [ OK ]
Feb 16 11:16:26 lemass systemd[1]: Started LSB: Starts and stops login
and scanning of iSCSI devices..
Feb 16 11:16:26 lemass dbus-daemon[733]: Starting iscsi (via systemctl):
[ OK ]
Feb 16 11:16:26 lemass systemd[1]: Stopping Sendmail Mail Transport
Client...
Feb 16 11:16:26 lemass systemd[1]: Stopping Sendmail Mail Transport Agent...
Feb 16 11:16:26 lemass systemd[1]: Starting Sendmail Mail Transport Agent...
Feb 16 11:16:26 lemass systemd[1]: Started Sendmail Mail Transport Agent.
Feb 16 11:16:26 lemass systemd[1]: Starting Sendmail Mail Transport
Client...
Feb 16 11:16:26 lemass chronyd[780]: Source 174.36.71.205 online
Feb 16 11:16:26 lemass chronyd[780]: Source 50.97.210.169 online
Feb 16 11:16:26 lemass chronyd[780]: Source 70.88.148.4 online
Feb 16 11:16:26 lemass chronyd[780]: Source 96.44.142.5 online
Feb 16 11:16:26 lemass systemd[1]: Started Sendmail Mail Transport Client.
Feb 16 11:16:26 lemass chronyd[780]: Selected source 174.36.71.205
Feb 16 11:16:26 lemass chronyd[780]: System clock wrong by 1.803794
seconds, adjustment started
Feb 16 11:18:36 lemass chronyd[780]: Selected source 70.88.148.4
Feb 16 11:35:24 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 11:35:24 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 11:35:24 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 11:35:24 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 11:59:18 lemass kernel: [15870.934309] nf_conntrack: automatic
helper assignment is deprecated and it will be removed soon. Use the
iptables CT target to attach helpers instead.
Feb 16 12:23:20 lemass dbus-daemon[733]: dbus[733]: [system] Activating
via systemd: service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service'
Feb 16 12:23:20 lemass dbus[733]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service'
Feb 16 12:23:20 lemass systemd[1]: Starting Hostname Service...
Feb 16 12:23:20 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.hostname1'
Feb 16 12:23:20 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.hostname1'
Feb 16 12:23:20 lemass systemd[1]: Started Hostname Service.
Feb 16 12:26:34 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:26:34 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:26:34 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:26:34 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:26:40 lemass yum[7759]: Installed: nemo-1.1.2-1.fc18.x86_64
Feb 16 12:26:40 lemass yum[7759]: Installed:
nemo-extensions-1.1.2-1.fc18.x86_64
Feb 16 12:26:41 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:26:41 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:26:41 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:26:41 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:28:39 lemass dbus-daemon[733]: dbus[733]: [system] Activating
via systemd: service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service'
Feb 16 12:28:39 lemass dbus[733]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service'
Feb 16 12:28:39 lemass systemd[1]: Starting Hostname Service...
Feb 16 12:28:39 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.hostname1'
Feb 16 12:28:39 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.hostname1'
Feb 16 12:28:39 lemass systemd[1]: Started Hostname Service.
Feb 16 12:31:29 lemass yum[7982]: Installed: alacarte-3.6.1-1.fc18.noarch
Feb 16 12:31:30 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:31:30 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:31:30 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:31:30 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:39:14 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:39:14 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:39:14 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:39:14 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:39:21 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:39:21 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:39:21 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:39:21 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:40:25 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:40:25 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:40:25 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:40:25 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 12:40:45 lemass yum[8938]: Installed: zinnia-0.06-14.fc18.x86_64
Feb 16 12:40:46 lemass yum[8938]: Installed: libgcroots-0.2.3-3.fc18.x86_64
Feb 16 12:40:46 lemass yum[8938]: Installed:
pangox-compat-0.0.2-1.fc18.x86_64
Feb 16 12:40:46 lemass yum[8938]: Installed:
gtkglext-libs-1.2.0-18.fc18.x86_64
Feb 16 12:40:48 lemass yum[8938]: Installed:
zinnia-tomoe-0.06-14.fc18.x86_64
Feb 16 12:40:48 lemass yum[8938]: Installed: eb-4.4.1-5.fc18.x86_64
Feb 16 12:40:49 lemass yum[8938]: Installed: uim-1.8.4-1.fc18.x86_64
Feb 16 12:40:50 lemass yum[8938]: Installed: uim-anthy-1.8.4-1.fc18.x86_64
Feb 16 12:40:50 lemass yum[8938]: Installed:
ibus-handwrite-2.1.4-5.fc18.x86_64
Feb 16 12:40:50 lemass yum[8938]: Installed: ibus-sayura-1.3.1-6.fc18.x86_64
Feb 16 12:40:51 lemass yum[8938]: Installed:
ibus-panel-extensions-1.4.99.20111207-5.fc18.x86_64
Feb 16 12:40:51 lemass yum[8938]: Installed: ibus-qt-1.3.1-10.fc18.x86_64
Feb 16 12:40:51 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:40:51 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 12:40:51 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 12:40:51 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 13:35:24 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 13:35:24 lemass dbus[733]: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Feb 16 13:35:24 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'org.freedesktop.PackageKit'
Feb 16 13:35:24 lemass dbus[733]: [system] Successfully activated
service 'org.freedesktop.PackageKit'
Feb 16 14:05:58 lemass systemd[1]: Starting Getty on tty2...
Feb 16 14:05:58 lemass systemd[1]: Started Getty on tty2.
Feb 16 14:06:00 lemass dbus-daemon[733]: dbus[733]: [system] Activating
service name='net.reactivated.Fprint' (using servicehelper)
Feb 16 14:06:00 lemass dbus[733]: [system] Activating service
name='net.reactivated.Fprint' (using servicehelper)
Feb 16 14:06:00 lemass dbus-daemon[733]: dbus[733]: [system]
Successfully activated service 'net.reactivated.Fprint'
Feb 16 14:06:00 lemass dbus[733]: [system] Successfully activated
service 'net.reactivated.Fprint'
Feb 16 14:06:00 lemass dbus-daemon[733]: Launching FprintObject
Feb 16 14:06:00 lemass dbus-daemon[733]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint
Feb 16 14:06:00 lemass dbus-daemon[733]: ** Message: entering main loop
Feb 16 14:06:12 lemass systemd-logind[727]: New session 10 of user root.
===============
As it stands right now, I'm sitting on a fairly expensive paper weight.
I can't use it, obviously, but I am willing to test/torture it for you
guys and gals. I'd love to find out why it's crashing fedora 18.
lemass:/home/digimer# uname -a
Linux lemass.alteeve.ca 3.7.7-201.fc18.x86_64 #1 SMP Tue Feb 12 22:35:01
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
11 years, 2 months
