Bug#969188: Upstream informed of RFP
I mentioned this RFP to the Duplicati issues just to centralise the information. At this stage the project doesn't have the resources to complete the packaging. https://github.com/duplicati/duplicati/issues/4305
Bug#969188: RFP: duplicati -- user-friendly remote, encrypted, incremental backups; capable GUI via built-in local server
Package: wnpp Severity: wishlist * Package name: duplicati Version : 2.0 Upstream Author : Kenneth Skovhede , Rene Stach * URL : http://www.duplicati.com/ * License : LGPL-2.1 Programming Lang: C# Description : user-friendly remote, encrypted, incremental backups; capable GUI via built-in local server I have looked at most of the backup packages in Debian and duplicati has a better combination ot features and ease-of-use, at least for personal use. It can perform remote, encrypted, incremental backups over several transports. It has a very capable GUI with well-designed configuration options. It makes a pragmatic, simplifying default choice of largely trusting the user's machine but not the remote host. The built-in web server for configuration and administration is very convenient (and excellent for remote administration using port forwarding). A debian package exists and requires little more than automated installation of systemd configuration.
Bug#682426: #682426 - related ghostscript changelog?
http://www.ghostscript.com/doc/current/News.htm Version 9.14 (2014-03-26) ... Ghostscript now reduces memory usage when processing PDF files that use transparency and output is to display devices such as Windows display or x11 (i.e. devices that are strictly full framebuffer devices), and to high level vector devices that cannot reproduce the PDF transparency model, such as the ps2write device or pdfwrite when 'flattening' to PDF 1.3 or earlier (- dCompatibilityLevel=1.3). This uses banding (clist) files to render the transparent areas in bands to reduce memory use, and unlike the existing page level banding, this is hidden from the target device. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692984: Expected upload of sogo-connector
I'm interested in obtaining the sogo-connector, as this seems to be the only way to sync contacts with owncloud. I'd prefer to get it through the debian repositories. The messages above suggest that it could be (or has been) uploaded, which is good news. When might we expect it to appear? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746036: iceowl-extension: Event not shown when calendar view refreshed.
Package: iceowl-extension Version: 24.4.0-1 Severity: grave Justification: renders package unusable Using the default local calendar (home), I create an event and save it. It is shown in the Week view. If I switch tabs, synchronise, switch views, and the return to the view, it has disappeared. It seems that any refresh of the view causes the event to disappear. If I select it from the events list above the view and resave it, the event reappears until the next refresh. The event remains visible in the Multiweek view, but shows the disappearing behaviour in Day, Week and Month views. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iceowl-extension depends on: ii icedove 24.4.0-1 ii libc62.18-4 ii libgcc1 1:4.8.2-16 ii libnspr4 2:4.10.4-1 ii libnspr4-0d 2:4.10.4-1 ii libstdc++6 4.8.2-16 Versions of packages iceowl-extension recommends: ii calendar-google-provider 24.4.0-1 Versions of packages iceowl-extension suggests: ii fonts-lyx 2.0.6-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746036: iceowl-extension: Event not shown when calendar view refreshed.
So, after a restart all is now OK. I have screenshots to prove it did happen! But if it doesn't recur, I guess this can be ignored. Apologies for the noise. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691064: Fixed in 3.10-2-amd64
I'm running the stock 3.10-2-amd64 kernel and I notice that this problem seems to have resolved itself. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716851: Similar backtrace on launchpad
There is a very similar backtrace attached to a bug report on the Ubuntu Launchpad: https://bugs.launchpad.net/kicad/+bug/911963 in particular comment #5 and https://bugs.launchpad.net/kicad/+bug/911963/+attachment/2671141/+files/Xorg.gdblog.4975 For what it's worth, that reporter also uses intel drivers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563748: installation-reports: Provide script to update resume and uswsusp.conf files?
Thanks for looking at this old bug. Yes, fine by me to close the bug. Perhaps my main problem as an inexperienced user was just discovering which package should generate the files (i.e. it was less obvious for /etc/initramfs- tools/conf.d/resume). Maybe this discussion will help others in the same situation. Quoting Boris Barbour (boris.barb...@ens.fr): On migrating my long-running system to a new disk (by cp), I discovered that /etc/uswsusp.conf and /etc/initramfs-tools/conf.d/resume then contained stale information regarding the partition to resume from. apt-file reports no package as responsible for these files; they appear to have been written out by the installer. It might be useful to provide a small script to update these files (update-resume-info?). Changes in the way devices are represented or the configuration of other disks in the computer may also be a scenarios where such an updater would prove useful. I doubt this should be in the scope of the installer. As you mentioned, the job was done properly during the initial install. I doubt, by the way, that this initial setting of the resume partition was done by D-I itself. It happened during the installation of the uswsusp package. What you want is probably something that belongs to that one package. It's indeed probably enough to just dpkg-reconfigure uswsusp. Hi Boris, Christian, The files /etc/uswsusp.conf and /etc/initramfs-tools/conf.d/resume are conffiles, but these files are different in every host, so we shouldn't include them as conffiles. See [1] and [2]. For this reason you cannot find them using 'apt-file' or 'dpkg -S'. IMO, the current configuration (no automatic conffile) is right. When you move your filesystems, some things could change. For example, the /etc/fstab could be different. If you change the machine, the hardware could be different and some drivers (pe. video) should be changed. In those cases, you edit the fstab file and update your X11 package. Why should be different with uswsusp? uswsusp doesn't have any bug, simply your filesystems are different and you should reconfigure it. 'dpkg-reconfigure uswsusp' do it. IMO, nothing is wrong, your script update-resume-info is dpkg-reconfigure uswsusp and probably this bug should be closed. Please, tell us if you agree with closing this bug. Best regards, kix. [1] http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html [2] http://www.debian.org/doc/manuals/maint-guide/dother.en.html#conffiles -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702474: Fixed in kde-workspace-bin 4:4.8.4-6
So I installed the latest version of kde-workspace-bin = 4:4.8.4-6 (and related dependencies) from unstable. Screen locking now works again. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702474: dbus: Screensaver service seems to be absent.
Thanks for the quick reply and explanation. I've now had time to examine a working system. I can't find anything under /usr/share/dbus-1/services or /etc/dbus-1/ that mentions screen So I have no idea how locking should work or what is now missing/wrong... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702474: krunner crashes on login
Further investigation suggests that the locking action should involve krunner. krunner isn't running. Indeed it crashes upon log in. Probably worth fixing that first... The backtrace is probably not useful (I include in below anyway). The crash handler suggests I install debugging symbols for /usr/bin/krunner /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so but as far as I can see, they _are_ already installed $ aptitude search kde | grep dbg p debconf-kde-dbg i A kde-baseapps-dbg i A kde-runtime-dbg p kde-telepathy-approver-dbg p kde-telepathy-auth-handler-dbg p kde-telepathy-call-ui-dbg p kde-telepathy-contact-list-dbg p kde-telepathy-send-file-dbg p kde-telepathy-text-ui-dbg i A kde-workspace-dbg i kdeaccessibility-dbg i kdeadmin-dbg i kdeartwork-dbg i kdebase-dbg i A kdebase-runtime-dbg i kdebase-workspace-dbg -dbg i kdebindings-dbg i kdeedu-dbg i kdegames-dbg i kdegraphics-dbg p kdelibs-dbg i kdelibs5-dbg i kdemultimedia-dbg i kdenetwork-dbg p kdenlive-dbg i kdepim-dbg i kdepim-runtime-dbg i kdepimlibs-dbg i kdeplasma-addons-dbg i kdesdk-dbg p kdesvn-dbg i kdetoys-dbg i kdeutils-dbg p kdevelop-dbg p kdevelop-php-dbg iB kdevplatform-dbg i kdewebdev-dbg p libkdeedu-dbg p liblockdev1-dbg p libsmokekde4-dbg p python-kde3-dbg p python-kde4-dbg p python3-pykde4-dbg p ruby-kde4-dbg Application: Run Command Interface (krunner), signal: Aborted Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [Current thread is 1 (Thread 0x7f57e7f95780 (LWP 4680))] Thread 2 (Thread 0x7f57e0a2f700 (LWP 4980)): #0 0x7f57fbb48e33 in *__GI___poll (fds=optimized out, nfds=optimized out, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f57f1043624 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f57f1043744 in g_main_context_iteration () from /lib/x86_64-linux- gnu/libglib-2.0.so.0 #3 0x7f57f858e296 in QEventDispatcherGlib::processEvents (this=0x127aa00, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7f57f855e8af in QEventLoop::processEvents (this=this@entry=0x7f57e0a2edf0, flags=...) at kernel/qeventloop.cpp:149 #5 0x7f57f855eb38 in QEventLoop::exec (this=0x7f57e0a2edf0, flags=...) at kernel/qeventloop.cpp:204 #6 0x7f57f8461d70 in QThread::exec (this=optimized out) at thread/qthread.cpp:501 #7 0x7f57f853f1bf in QInotifyFileSystemWatcherEngine::run (this=0x11183a0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f57f8464d0b in QThreadPrivate::start (arg=0x11183a0) at thread/qthread_unix.cpp:307 #9 0x7f57f1511b50 in start_thread (arg=optimized out) at pthread_create.c:304 #10 0x7f57fbb53a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f57e7f95780 (LWP 4680)): [KCrash Handler] #6 0x7f57fbaab475 in *__GI_raise (sig=optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #7 0x7f57fbaae6f0 in *__GI_abort () at abort.c:92 #8 0x7f57f7ec389d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f57f7ec1996 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f57f7ec19c3 in std::terminate() () from /usr/lib/x86_64-linux- gnu/libstdc++.so.6 #11 0x7f57f7ec1c36 in __cxa_rethrow () from /usr/lib/x86_64-linux- gnu/libstdc++.so.6 #12 0x7f57f8575ee0 in QMetaObject::activate (sender=0x12d0c10, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3576 #13 0x7f57faff6968 in Plasma::FrameSvg::setImagePath (this=0x12d0c10, path=...) at ../../plasma/framesvg.cpp:113 #14 0x7f57fbe2c2cf in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #15 0x7f57fbe2cd75 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #16 0x7f57fbe32644 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #17 0x7f57fbe2f686 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #18 0x7f57fbe2fef3 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #19 0x7f57fbe2ff45 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #20 0x7f57fbe30695 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_krunner.so #21 0x7f57fba97ead in __libc_start_main (main=optimized out, argc=optimized out, ubp_av=optimized out, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff2d81ee78) at libc-start.c:228 #22 0x004006f1 in _start
Bug#702474: dbus: Screensaver service seems to be absent.
Package: dbus Version: 1.7.0-1 Severity: normal I'm not sure I'm reporting this against the right package (apologies). After a recent upgrade (and after testing the very latest dbus suggested by reportbug), I can no longer lock my kde session (in particular, using the Lock/Logout widget). Invoking qdbus org.freedesktop.ScreenSaver /ScreenSaver Lock tells me Service 'org.freedesktop.ScreenSaver' does not exist. Indeed, I can't seem to find any screensaver.service in /usr/share/dbus-1/services Should there be one? In contrast /usr/lib/kde4/libexec/kscreenlocker --forcelock works just fine. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable'), (600, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dbus depends on: ii adduser3.113+nmu3 ii libc6 2.13-38 ii libdbus-1-31.6.8-1 ii libexpat1 2.1.0-1 ii libselinux12.1.9-5 ii libsystemd-login0 44-10 ii lsb-base 4.1+Debian8 dbus recommends no packages. Versions of packages dbus suggests: ii dbus-x11 1.6.8-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701209: obnam: DEBUG OSError ((95, 'Operation not supported', 'filename'), ) sshfs problem?
Package: obnam
Version: 1.1-1.1
Severity: normal
I'm trying to backup a directory that is mounted via sshfs to an sftp
repository.
I get many errors in the log of this sort (where I've replaced the true
filname):
2013-02-22 19:27:13 DEBUG OSError((95, 'Operation not supported',
'filename'),)
Obnam eventually quits and the following is found at the end of the log
2013-02-22 19:28:29 DEBUG Handling exception (95, 'Operation not supported',
'filename')
2013-02-22 19:28:29 DEBUG Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 258, in backup
self.backup_roots(roots)
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 367, in backup_roots
self.backup_parents('.')
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 491, in backup_parents
metadata = obnamlib.read_metadata(self.fs, root)
File /usr/lib/python2.7/dist-packages/obnamlib/metadata.py, line 190, in
read_metadata
metadata.xattr = get_xattrs_as_blob(fs, filename)
File /usr/lib/python2.7/dist-packages/obnamlib/metadata.py, line 130, in
get_xattrs_as_blob
names = fs.llistxattr(filename)
File /usr/lib/python2.7/dist-packages/obnamlib/vfs_local.py, line 165, in
llistxattr
raise OSError((ret, os.strerror(ret), filename))
OSError: (95, 'Operation not supported', '/home/barbour/share')
2013-02-22 19:28:29 INFO Unlocking client because of error
2013-02-22 19:28:29 DEBUG Got second exception while unlocking: have not got
lock on shared B-trees
2013-02-22 19:28:29 DEBUG Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 285, in unlock_when_error
self.repo.unlock_client()
File /usr/lib/python2.7/dist-packages/obnamlib/repo.py, line 455, in
unlock_client
self._really_remove_generations(self.added_generations)
File /usr/lib/python2.7/dist-packages/obnamlib/repo.py, line 566, in
_really_remove_generations
self.require_shared_lock()
File /usr/lib/python2.7/dist-packages/obnamlib/repo.py, line 221, in
require_shared_lock
raise LockFail('have not got lock on shared B-trees')
LockFail: have not got lock on shared B-trees
2013-02-22 19:28:29 CRITICAL Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/cliapp/app.py, line 169, in _run
self.process_args(args)
File /usr/lib/python2.7/dist-packages/obnamlib/app.py, line 170, in
process_args
cliapp.Application.process_args(self, args)
File /usr/lib/python2.7/dist-packages/cliapp/app.py, line 416, in
process_args
method(args[1:])
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 258, in backup
self.backup_roots(roots)
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 367, in backup_roots
self.backup_parents('.')
File /usr/lib/python2.7/dist-packages/obnamlib/plugins/backup_plugin.py,
line 491, in backup_parents
metadata = obnamlib.read_metadata(self.fs, root)
File /usr/lib/python2.7/dist-packages/obnamlib/metadata.py, line 190, in
read_metadata
metadata.xattr = get_xattrs_as_blob(fs, filename)
File /usr/lib/python2.7/dist-packages/obnamlib/metadata.py, line 130, in
get_xattrs_as_blob
names = fs.llistxattr(filename)
File /usr/lib/python2.7/dist-packages/obnamlib/vfs_local.py, line 165, in
llistxattr
raise OSError((ret, os.strerror(ret), filename))
OSError: (95, 'Operation not supported', '/home/barbour/share')
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental'), (500,
'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages obnam depends on:
ii libc6 2.13-38
ii python2.7.3-4
ii python-cliapp 1.20120630-1
ii python-larch 1.20121006-1
ii python-paramiko 1.7.7.1-3.1
ii python-tracing0.6-2
ii python-ttystatus 0.19-1
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691064: linux-image-3.5-trunk-amd64: Blank screen between earliest boot messages and X.
Package: src:linux Version: 3.5.2-1~experimental.1 Severity: normal Hi, When booting 3.5-trunk-amd64 and 3.1.0-1-amd64 but not 3.0.0-1-amd64 the boot messages disappear early on (at switch to graphics console?), roughly after udev gets started. There is just a blank screen until X starts, after which everything works. The timing and problem seem rather like #681743, but adjusting the brightness controls don't make any boot messages appear for me. -- Package-specific info: ** Version: Linux version 3.5-trunk-amd64 (Debian 3.5.2-1~experimental.1) (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Aug 20 04:17:46 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.5-trunk-amd64 root=UUID=59d895fb-43e5-417b-bf49-c2824431a9ed ro quiet ** Not tainted ** Kernel log: [3.475787] intel_rng: FWH not detected [3.486791] Bluetooth: Core ver 2.16 [3.486822] NET: Registered protocol family 31 [3.486825] Bluetooth: HCI device and connection manager initialized [3.486829] Bluetooth: HCI socket layer initialized [3.486832] Bluetooth: L2CAP socket layer initialized [3.486840] Bluetooth: SCO socket layer initialized [3.500337] input: PC Speaker as /devices/platform/pcspkr/input/input5 [3.502533] usbcore: registered new interface driver btusb [3.510832] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [3.513526] ACPI Warning: 0xf400b410-0xf400b414 SystemMemory conflicts with Region \RCRB 1 (20120320/utaddress-251) [3.513540] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [3.513544] lpc_ich: Resource conflict(s) found affecting iTCO_wdt [3.515124] microcode: CPU0 sig=0x6f2, pf=0x20, revision=0x57 [3.538282] yenta_cardbus :02:01.0: CardBus bridge found [1028:0201] [3.561817] kvm: disabled by bios [3.604965] coretemp coretemp.0: Using relative temperature scale! [3.604994] coretemp coretemp.0: Using relative temperature scale! [3.621520] input: Dell WMI hotkeys as /devices/virtual/input/input6 [3.634000] leds_ss4200: no LED devices found [3.634301] cfg80211: Calling CRDA to update world regulatory domain [3.659526] [drm] Initialized drm 1.1.0 20060810 [3.665016] yenta_cardbus :02:01.0: ISA IRQ mask 0x0cb8, PCI irq 19 [3.665026] yenta_cardbus :02:01.0: Socket status: 3006 [3.665034] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #03 to #06 [3.665051] yenta_cardbus :02:01.0: pcmcia: parent PCI bridge window: [io 0x5000-0x5fff] [3.665057] yenta_cardbus :02:01.0: pcmcia: parent PCI bridge window: [mem 0xefb0-0xefbf] [3.665063] pcmcia_socket pcmcia_socket0: cs: memory probe 0xefb0-0xefbf: [3.665087] excluding 0xefbf-0xefbf [3.665096] yenta_cardbus :02:01.0: pcmcia: parent PCI bridge window: [mem 0x8000-0x83ff pref] [3.665101] pcmcia_socket pcmcia_socket0: cs: memory probe 0x8000-0x83ff: [3.665127] excluding 0x8000-0x83ff [3.706768] microcode: CPU1 sig=0x6f2, pf=0x20, revision=0x57 [3.726361] microcode: Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk, Peter Oruba [3.728409] kvm: disabled by bios [3.749869] i915 :00:02.0: setting latency timer to 64 [3.753079] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s [3.753084] iwl3945: Copyright(c) 2003-2011 Intel Corporation [3.774163] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [3.774167] [drm] Driver supports precise vblank timestamp query. [3.774288] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.809727] iwl3945 :0c:00.0: Tunable channels: 13 802.11bg, 23 802.11a channels [3.809735] iwl3945 :0c:00.0: Detected Intel Wireless WiFi Link 3945ABG [3.809903] iwl3945 :0c:00.0: irq 43 for MSI/MSI-X [3.810207] Registered led device: phy0-led [3.818061] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs' [3.826271] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: [3.826288] excluding 0xc-0xc 0xe-0xf [3.826343] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: [3.826373] clean. [3.826401] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: [3.826434] excluding 0x6000-0x60ff [3.945089] cfg80211: World regulatory domain updated: [3.945095] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [3.945100] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [3.945105] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [3.945109] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [3.945113] cfg80211: (517 KHz -
Bug#605210: linux-image-2.6.32-5-amd64: cdrom stops working
Was this a regression? I tested this by booting off a couple of live cds of debian 5.09 (it must have worked back then) and 6.03. The live cds work on another computer, but didn't get much beyond the boot menu here. A newer kernel (3.2) was also no help. It now seems most likely that the drive itself is broken (and that I have lots of broken drives). If a new drive works I won't be chasing this further. Sorry for the noise. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#658778: Suspend from X session hangs Asus laptop.
Thanks for the quick reply, Jonathan. Is this a regression? Not really (the machine is new). I tried older debian 5.09 and 6.03 live cds. With 6.03 suspending from a session worked under some conditions (lid) but not all (menu). Does suspend-to-disk (triggered with echo disk /sys/power/state This doesn't work. ) work? If you have time to follow the instructions from basic-pm-debugging.txt[1] to narrow down the cause, that would be very useful. Thanks for the pointer! For some reason I didn't find it while searching around (we beginners don't know to search for pm- instead of suspend). Maybe a link could be added on the debian wiki at http://wiki.debian.org/Suspend ? The shutdown method described in the document seems to work. But it is a bit clunky and it wasn't immediately obvious how to set this option permanently or whether it even applies to suspend to RAM (more for the wiki...) In the meantime I found the following site http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not- working-bug and shamelessly copy-pasted the suggested script. It works pretty well - the only obvious problem at the moment is that waking from sleep requires a press of the power button (lid-opening doesn't suffice). But at least there is no freeze with data loss and reboot. Huge progress. The working shutdown method suggests a bios issue and the copied script indicates a usb problem. Follow up might therefore look at the usb settings in the bios and investigate a bios upgrade (the changelog mumbles something about usb). The comments on the web site suggest that the solution has helped a lot of people and with different machines. Thanks and best wishes, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#605210: linux-image-2.6.32-5-amd64: cdrom stops working
Package: linux-2.6
Version: 2.6.32-27
Severity: important
If a cdrom is inserted, things work for a short while. I can for instance read
one or two
files on the CD. But, invariably, it stops working and a number of error
messages are logged.
Typical messages are:
[ 329.673137] UDF-fs: Partition marked readonly; forcing readonly mount
[ 329.740260] UDF-fs INFO UDF: Mounting volume 'Antidote HD', timestamp
2010/06/30 16:20 (1000)
[ 446.568967] ata6: drained 32768 bytes to clear DRQ.
[ 446.575346] ata6.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 446.575352] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 1f 00
[ 446.575368] ata6.01: cmd a0/01:00:00:00:f8/00:00:00:00:00/b0 tag 0 dma 63488
in
[ 446.575369] res 40/00:02:08:08:00/00:00:00:00:00/b0 Emask 0x4
(timeout)
[ 446.575373] ata6.01: status: { DRDY }
[ 446.575426] ata6: soft resetting link
[ 451.728152] ata6.01: qc timeout (cmd 0xa1)
[ 451.728172] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 451.728175] ata6.01: revalidation failed (errno=-5)
[ 451.728225] ata6: soft resetting link
[ 461.884122] ata6.01: qc timeout (cmd 0xa1)
[ 461.884141] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 461.884145] ata6.01: revalidation failed (errno=-5)
[ 461.884195] ata6: soft resetting link
[ 492.040124] ata6.01: qc timeout (cmd 0xa1)
[ 492.040144] ata6.01: failed to IDENTIFY (I/O error, err_mask=0x5)
[ 492.040147] ata6.01: revalidation failed (errno=-5)
[ 492.040151] ata6.01: disabled
[ 492.040265] ata6: soft resetting link
[ 492.196802] ata6: EH complete
[ 492.196832] sr 5:0:1:0: [sr0] Unhandled error code
[ 492.196835] sr 5:0:1:0: [sr0] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 492.196839] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 1f 00
[ 492.196850] end_request: I/O error, dev sr0, sector 7700
[ 492.196856] Buffer I/O error on device sr0, logical block 1925
[ 492.196864] Buffer I/O error on device sr0, logical block 1926
[ 492.196867] Buffer I/O error on device sr0, logical block 1927
[ 492.196871] Buffer I/O error on device sr0, logical block 1928
[ 492.196874] Buffer I/O error on device sr0, logical block 1929
[ 492.196878] Buffer I/O error on device sr0, logical block 1930
[ 492.196881] Buffer I/O error on device sr0, logical block 1931
[ 492.196885] Buffer I/O error on device sr0, logical block 1932
[ 492.196888] Buffer I/O error on device sr0, logical block 1933
[ 492.196891] Buffer I/O error on device sr0, logical block 1934
[ 492.196927] sr 5:0:1:0: [sr0] Unhandled error code
[ 492.196929] sr 5:0:1:0: [sr0] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK
[ 492.196933] sr 5:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 07 85 00 00 01 00
[ 492.196943] end_request: I/O error, dev sr0, sector 7700
[ 492.197355] VFS: busy inodes on changed media or resized disk sr0
[ 492.197851] VFS: busy inodes on changed media or resized disk sr0
[ 492.200278] VFS: busy inodes on changed media or resized disk sr0
(Then quite a few more of these. They continue after the cd has been reomved.)
I have tried another drive and get the same errors, so I don't think the
problem is
related to the drive itself. A harddisk is attached to the same controller,
making
a controller error a little less likely.
The problem has been around for a while. Less than a year, but certainly for
several
kernel versions.
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-27) (m...@debian.org) (gcc version
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sat Oct 30 14:18:21 UTC 2010
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64
root=UUID=4213b79c-6f32-4f5d-9690-825d96ebc45f ro quiet
** Not tainted
** Kernel log:
See above.
** Model information
sys_vendor:
product_name:
product_version:
chassis_vendor:
chassis_version:
bios_vendor: Award Software International, Inc.
bios_version: F2
board_vendor: Gigabyte Technology Co., Ltd.
board_name: 965GM-S2
board_version: x.x
** Loaded modules:
Module Size Used by
udf66628 1
binfmt_misc 6431 1
ip6table_filter 2384 0
ip6_tables 15075 1 ip6table_filter
ebtable_nat 1588 0
ebtables 13933 1 ebtable_nat
ppdev 5030 0
lp 7462 0
sco 7209 2
bridge 39646 0
stp 1440 1 bridge
bnep9443 2
rfcomm 29613 0
l2cap 24736 6 bnep,rfcomm
crc16 1319 1 l2cap
bluetooth 41827 6 sco,bnep,rfcomm,l2cap
rfkill 13044 2 bluetooth
kvm_intel 38050 0
kvm 213800 1 kvm_intel
battery 4998 0
autofs420805 1
acpi_cpufreq 0
cpufreq_powersave902 0
cpufreq_stats 2659 0
cpufreq_userspace 1992 0
Bug#595148: xserver-xorg: xorg freeze with 100% CPU, possibly VT switch or resume related.
Boris Barbour boris.barb...@ens.fr (01/09/2010): ii xserver-xorg-video-int 2:2.9.1-4 X.Org X server -- Intel i8xx, i9xx you may want to give a try to 2:2.12.0+legacy1-1. I have tried it and I think the problem has disappeared. At least, it hasn't recurred in a few days, while before I would get a freeze daily at least. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595148: xserver-xorg: xorg freeze with 100% CPU, possibly VT switch or resume related.
Package: xserver-xorg Version: 1:7.5+6 Severity: important I am writing this from a machine on which cpu usage by xorg is stuck at 100%. This happens quite often, but never during continuous single-user use, so I think it is triggered by VT switching or possibly upon resuming. The symptom is either the monitor displays an out of range error or the screen is frozen, with only the mouse moving - impossible to click on anything, switch VT etc. I can however ssh into the machine and thus see that xorg is occupying one cpu totally. Possibly related to #573994, #574989, #581223. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Dec 30 2009 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1878528 Jul 15 17:31 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82G965 Integrated Graphics Controller (rev 02) /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.32-5-amd64 (Debian 2.6.32-20) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Thu Aug 12 13:01:50 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 23136 Jan 18 2010 /var/log/Xorg.5.log -rw-r--r-- 1 root root 24740 May 9 14:38 /var/log/Xorg.4.log -rw-r--r-- 1 root root 21482 Aug 31 20:01 /var/log/Xorg.0.log -rw-r--r-- 1 root root 22876 Aug 31 20:17 /var/log/Xorg.1.log -rw-r--r-- 1 root root 21483 Sep 1 12:45 /var/log/Xorg.3.log -rw-r--r-- 1 root root 24743 Sep 1 12:46 /var/log/Xorg.2.log Contents of most recent Xorg X server log file /var/log/Xorg.2.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian Current Operating System: Linux bordel 2.6.32-5-amd64 #1 SMP Thu Aug 12 13:01:50 UTC 2010 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=4213b79c-6f32-4f5d-9690-825d96ebc45f ro quiet Build Date: 15 July 2010 03:08:26PM xorg-server 2:1.7.7-3 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.2.log, Time: Tue Aug 31 20:17:58 2010 (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |--Screen Default Screen Section (0) (**) | |--Monitor default monitor (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x7c6000 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 9 (--) PCI:*(0:0:2:0) 8086:29a2:1458:d000 Intel Corporation 82G965 Integrated Graphics Controller rev 2, Mem @ 0xf410/1048576, 0xe000/268435456, I/O @ 0xa000/8 (II) Open ACPI successful (/var/run/acpid.socket) (II) LoadModule: extmod (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension SELinux (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.7.7, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II)
Bug#571289: SOLVED: Re: Bug#571289: xorg: X gives black screen and pointer only with 2.6.32 kernel
Hi, At least revision -8 (linux-image-2.6.32-2-*) would help, revision -9 (linux-image-2.6.32-3-*) is going to be available shortly (currently in NEW). In the meanwhile, passing i915.powersave=0 through your kernel command line might help. I had overlooked the availablity of the -2 version of that kernel. I have installed it and 3d acceleration is back $ glxinfo | grep render direct rendering: Yes OpenGL renderer string: Mesa DRI Intel(R) 965G GEM 20090712 2009Q2 RC3 Thank you. Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571273: SOLVED
I confused the two bugs (#571273 and #571289) in reporting success. In any case, with the linux-image-2.6.32-2-amd64 kernel X now starts successfully AND 3d acceleration works. Thank you. Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571273: xorg: No 3d acceleration because Failed to open DRM device
Package: xorg Version: 1:7.5+3 Severity: normal My system has become as slow as molasses after a recent upgrade. It appears to be because it has fallen back on to software rendering: $ glxinfo | grep render direct rendering: Yes OpenGL renderer string: Software Rasterizer And in turn this appears to be some problem with dri/drm (I'm out of my depth here). $ cat Xorg.0.log | grep drm drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: Searching for BusID pci::00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card1 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card2 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card3 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card4 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card5 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card6 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card7 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card8 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card9 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card10 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card11 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card12 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card13 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card14 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card15 drmOpenByBusid: drmOpenMinor returns -1 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card1 drmOpenDevice: node name is /dev/dri/card2 drmOpenDevice: node name is /dev/dri/card3 drmOpenDevice: node name is /dev/dri/card4 drmOpenDevice: node name is /dev/dri/card5 drmOpenDevice: node name is /dev/dri/card6 drmOpenDevice: node name is /dev/dri/card7 drmOpenDevice: node name is /dev/dri/card8 drmOpenDevice: node name is /dev/dri/card9 drmOpenDevice: node name is /dev/dri/card10 drmOpenDevice: node name is /dev/dri/card11 drmOpenDevice: node name is /dev/dri/card12 drmOpenDevice: node name is /dev/dri/card13 drmOpenDevice: node name is /dev/dri/card14 drmOpenDevice: node name is /dev/dri/card15 (EE) intel(0): [drm] Failed to open DRM device for : No such file or directory (WW) intel(0): DRI2: failed to open drm device (WW) intel(0): drmSetMaster failed: Bad file descriptor (I'll append the full log below). The problem arises with the xorg.conf that I'll also append below or with none. I can't test a newer stock kernel (2.6.32) because I get a blank screen when X tries to start (should post another bug report). Any guidance for debugging this or working around it appreciated. Best regards, Boris -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-em 2.28.2-1 The GNOME terminal emulator applic ii konsole [x-terminal-emulator] 4:4.3.4-1 X terminal emulator for KDE 4 ii libgl1-mesa-dri 7.6.1-1A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.6.1-1A free implementation of the OpenG ii libglu1-mesa 7.6.1-1The OpenGL utility library (GLU) ii x11-apps 7.5+2 X applications ii x11-session-utils 7.5+1 X session utilities ii x11-utils 7.5+2 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.5+1 X11 XKB utilities ii x11-xserver-utils 7.5+1 X server utilities ii xauth 1:1.0.4-1 X authentication utility ii xfonts-100dpi 1:1.0.1100 dpi fonts for X ii xfonts-75dpi 1:1.0.175 dpi fonts for X ii xfonts-base 1:1.0.1standard fonts for X ii xfonts-scalable 1:1.0.1-1 scalable fonts for X ii xfonts-utils 1:7.5+2X Window System font utility progr ii xinit 1.2.0-1X server initialisation tool ii xkb-data 1.7-2 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.5-1Core documentation for the X.org X ii xserver-xorg 1:7.5+3the X.Org X server ii xterm
Bug#571273: xorg: No 3d acceleration because Failed to open DRM device
Thanks for your instantaneous reply, Brice. Are drm and i915 kernel modules loaded ? Yes: $ lsmod | grep i915 i915 168328 0 drm 172512 1 i915 video 21884 1 i915 i2c_algo_bit5988 2 i915,intelfb i2c_core 25424 5 i915,drm,intelfb,i2c_algo_bit,i2c_i801 $ lsmod | grep drm drm 172512 1 i915 i2c_core 25424 5 i915,drm,intelfb,i2c_algo_bit,i2c_i801 You want to use 2.6.32 anyway... OK - I'll file a separate bug report concerning that Xorg/kernel combination shortly... Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#571289: xorg: X gives black screen and pointer only with 2.6.32 kernel
Package: xorg Version: 1:7.5+3 Severity: important Booting with the stock linux-image-2.6.32-trunk-amd64 kernel can only start X as far as providing a black screen and a pointer. Neither kdm dialog nor its background image are visible. After a few switches to and from a totally black screen, I just get a VGA cursor. The system log contains quite a few messages of the following sort: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung The X log also contains errors. Ill attach the Xorg.0.log, dmesg and lspci to a second email. Note that the problem arose when using no xorg.conf file. Best regards, Boris -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xorg depends on: ii gnome-terminal [x-terminal-em 2.28.2-1 The GNOME terminal emulator applic ii konsole [x-terminal-emulator] 4:4.3.4-1 X terminal emulator for KDE 4 ii libgl1-mesa-dri 7.6.1-1A free implementation of the OpenG ii libgl1-mesa-glx [libgl1] 7.6.1-1A free implementation of the OpenG ii libglu1-mesa 7.6.1-1The OpenGL utility library (GLU) ii x11-apps 7.5+2 X applications ii x11-session-utils 7.5+1 X session utilities ii x11-utils 7.5+2 X11 utilities ii x11-xfs-utils 7.4+1 X font server utilities ii x11-xkb-utils 7.5+1 X11 XKB utilities ii x11-xserver-utils 7.5+1 X server utilities ii xauth 1:1.0.4-1 X authentication utility ii xfonts-100dpi 1:1.0.1100 dpi fonts for X ii xfonts-75dpi 1:1.0.175 dpi fonts for X ii xfonts-base 1:1.0.1standard fonts for X ii xfonts-scalable 1:1.0.1-1 scalable fonts for X ii xfonts-utils 1:7.5+2X Window System font utility progr ii xinit 1.2.0-1X server initialisation tool ii xkb-data 1.7-2 X Keyboard Extension (XKB) configu ii xorg-docs-core1:1.5-1Core documentation for the X.org X ii xserver-xorg 1:7.5+3the X.Org X server ii xterm [x-terminal-emulator] 253-1 X terminal emulator xorg recommends no packages. Versions of packages xorg suggests: pn xorg-docs none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563748: installation-reports: Provide script to update resume and uswsusp.conf files?
Package: installation-reports Severity: wishlist On migrating my long-running system to a new disk (by cp), I discovered that /etc/uswsusp.conf and /etc/initramfs-tools/conf.d/resume then contained stale information regarding the partition to resume from. apt-file reports no package as responsible for these files; they appear to have been written out by the installer. It might be useful to provide a small script to update these files (update-resume-info?). Changes in the way devices are represented or the configuration of other disks in the computer may also be a scenarios where such an updater would prove useful. Best regards, Boris -- Package-specific info: Boot method: CD Image version: testing netinst Date: Date and time of the install Machine: intel core duo amd64 gigabyte motherboard intel graphics Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=4.0 (installer build 20070308) X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux bordel 2.6.18-4-amd64 #1 SMP Wed Feb 21 14:29:38 UTC 2007 x86_64 unknown lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation P965/G965 Memory Controller Hub [8086:29a0] (rev 02) lspci -nn: 00:02.0 VGA compatible controller [0300]: Intel Corporation G965 Integrated Graphics Controller [8086:29a2] (rev 02) lspci -nn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 [8086:2834] (rev 02) lspci -nn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 [8086:2835] (rev 02) lspci -nn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 [8086:283a] (rev 02) lspci -nn: 00:1b.0 Audio device [0403]: Intel Corporation 82801H (ICH8 Family) HD Audio Controller [8086:284b] (rev 02) lspci -nn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 [8086:283f] (rev 02) lspci -nn: 00:1c.1 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 [8086:2841] (rev 02) lspci -nn: 00:1c.2 PCI bridge [0604]: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 [8086:2843] (rev 02) lspci -nn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 [8086:2830] (rev 02) lspci -nn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 [8086:2831] (rev 02) lspci -nn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 [8086:2832] (rev 02) lspci -nn: 00:1d.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 [8086:2836] (rev 02) lspci -nn: 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev f2) lspci -nn: 00:1f.0 ISA bridge [0601]: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller [8086:2810] (rev 02) lspci -nn: 00:1f.2 IDE interface [0101]: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller [8086:2820] (rev 02) lspci -nn: 00:1f.3 SMBus [0c05]: Intel Corporation 82801H (ICH8 Family) SMBus Controller [8086:283e] (rev 02) lspci -nn: 00:1f.5 IDE interface [0101]: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller [8086:2825] (rev 02) lspci -nn: 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. Unknown device [11ab:4364] (rev 12) lspci -nn: 03:00.0 IDE interface [0101]: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller [197b:2363] (rev 02) lspci -nn: 03:00.1 IDE interface [0101]: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller [197b:2363] (rev 02) lspci -nn: 04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10) lspci -nn: 04:01.0 RAID bus controller [0104]: VIA Technologies, Inc. VT6421 IDE RAID Controller [1106:3249] (rev 50) lspci -nn: 04:07.0 FireWire (IEEE 1394)
Bug#553404: Fixed in cups 1.4.1-4
This bug appears to be fixed in cups 1.4.1-4. Thanks to however repaired it. Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#553404: cups: n-up printing incorrect
Package: cups Version: 1.3.11-1+b1 Severity: normal n-up printing does not work correctly. Use of the -o number-up=2 option (with the lpr command) causes two pages of the original document to be printed in half the output sheet (as if n-up=4 had been chosen). If I use -o number-up=4, the 4 pages are printed squashed into a quarter of the sheet. From okular (where I first discovered the bug), if I change the page order (from default LRTB to BTLR) 2-up printing then causes two full sheets of paper with the original pages sizes to be printed. Changing to landscape does not solve the problem in okular at least. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser3.111 add and remove users and groups ii bc 1.06.94-3.1 The GNU bc arbitrary precision cal ii cups-client1.3.11-1+b1 Common UNIX Printing System(tm) - ii cups-common1.3.11-1 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.27Debian configuration management sy ii ghostscript8.70~dfsg-2+b1The GPL Ghostscript PostScript/PDF ii libavahi-compat-libdns 0.6.25-1 Avahi Apple Bonjour compatibility ii libc6 2.9-25GNU C Library: Shared libraries ii libcups2 1.4.1-4 Common UNIX Printing System(tm) - ii libcupsimage2 1.3.11-1+b1 Common UNIX Printing System(tm) - ii libdbus-1-31.2.16-2 simple interprocess messaging syst ii libgcc11:4.4.1-4 GCC support library ii libgnutls262.8.3-3 the GNU TLS library - runtime libr ii libgssapi-krb5-2 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - k ii libijs-0.350.35-7IJS raster image transport protoco ii libkrb5-3 1.7dfsg~beta3-1 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.17-1 OpenLDAP libraries ii libpam0g 1.1.0-4 Pluggable Authentication Modules l ii libpaper1 1.1.23+nmu1 library for handling paper charact ii libpoppler40.10.6-1 PDF rendering library ii libslp11.2.1-7.6 OpenSLP libraries ii libstdc++6 4.4.1-4 The GNU Standard C++ Library v3 ii lsb-base 3.2-23Linux Standard Base 3.2 init scrip ii perl-modules 5.10.0-25 Core Perl modules ii poppler-utils [xpdf-ut 0.10.6-1 PDF utilitites (based on libpopple ii procps 1:3.2.8-1.1 /proc file system utilities ii ssl-cert 1.0.23simple debconf wrapper for OpenSSL ii ttf-freefont 20090104-4Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages cups recommends: ii avahi-utils 0.6.25-1 Avahi browsing, publishing and dis ii cups-driver-gutenprint5.2.4-1printer drivers for CUPS ii foomatic-filters 4.0-20090509-1 OpenPrinting printer support - fil ii ghostscript-cups 8.70~dfsg-2+b1 The GPL Ghostscript PostScript/PDF ii smbclient 2:3.3.4-1 command-line SMB/CIFS clients for Versions of packages cups suggests: ii cups-bsd 1.3.11-1+b1 Common UNIX Printing System(tm) - ii cups-pdf 2.5.0-8 PDF printer for CUPS ii foomatic-db20090616-1OpenPrinting printer support - dat ii foomatic-db-engine 4.0-20090509-1+b1 OpenPrinting printer support - pro ii hplip 3.9.4b-1 HP Linux Printing and Imaging Syst pn xpdf-korean | xpdf-jap none(no description available) -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551768: cups: socket failed error / problem parsing terminal colons in URI?
Package: cups Version: 1.4.1-4 Severity: normal Several configured printers no longer worked with cups after an upgrade (to testing and ustable). It appears that the DeviceURI socket entry in /etc/cups.printers.conf of some printers (configured a while ago) have a terminal colon that is no longer parsed correctly, causing a socket failed error. Reconfiguring the printer (making sure to renew the connection description) or removing the colon by hand both reestablish printing. Best regards, -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (700, 'experimental'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser3.111 add and remove users and groups ii bc 1.06.94-3.1 The GNU bc arbitrary precision cal ii cups-client1.4.1-4 Common UNIX Printing System(tm) - ii cups-common1.4.1-4 Common UNIX Printing System(tm) - ii debconf [debconf-2.0] 1.5.27Debian configuration management sy ii ghostscript8.70~dfsg-2+b1The GPL Ghostscript PostScript/PDF ii libavahi-client3 0.6.25-1 Avahi client library ii libavahi-common3 0.6.25-1 Avahi common library ii libc6 2.9-25GNU C Library: Shared libraries ii libcups2 1.4.1-4 Common UNIX Printing System(tm) - ii libcupscgi11.4.1-4 Common UNIX Printing System(tm) - ii libcupsdriver1 1.4.1-4 Common UNIX Printing System(tm) - ii libcupsimage2 1.4.1-4 Common UNIX Printing System(tm) - ii libcupsmime1 1.4.1-4 Common UNIX Printing System(tm) - ii libcupsppdc1 1.4.1-4 Common UNIX Printing System(tm) - ii libdbus-1-31.2.16-2 simple interprocess messaging syst ii libgcc11:4.4.1-4 GCC support library ii libgnutls262.8.4-1 the GNU TLS library - runtime libr ii libgssapi-krb5-2 1.7dfsg~beta3-1 MIT Kerberos runtime libraries - k ii libijs-0.350.35-7IJS raster image transport protoco ii libkrb5-3 1.7dfsg~beta3-1 MIT Kerberos runtime libraries ii libldap-2.4-2 2.4.17-1 OpenLDAP libraries ii libpam0g 1.1.0-4 Pluggable Authentication Modules l ii libpaper1 1.1.23+nmu1 library for handling paper charact ii libpoppler40.10.6-1 PDF rendering library ii libslp11.2.1-7.6 OpenSLP libraries ii libstdc++6 4.4.1-4 The GNU Standard C++ Library v3 ii libusb-0.1-4 2:0.1.12-13 userspace USB programming library ii lsb-base 3.2-23Linux Standard Base 3.2 init scrip ii perl-modules 5.10.1-5 Core Perl modules ii poppler-utils [xpdf-ut 0.10.6-1 PDF utilitites (based on libpopple ii procps 1:3.2.8-2 /proc file system utilities ii ssl-cert 1.0.23simple debconf wrapper for OpenSSL ii ttf-freefont 20090104-4Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime Versions of packages cups recommends: ii cups-driver-gutenprint5.2.4-1printer drivers for CUPS ii foomatic-filters 4.0-20090509-1 OpenPrinting printer support - fil ii ghostscript-cups 8.70~dfsg-2+b1 The GPL Ghostscript PostScript/PDF Versions of packages cups suggests: ii cups-bsd 1.4.1-4 Common UNIX Printing System(tm) - ii cups-pdf 2.5.0-8 PDF printer for CUPS ii cups-ppdc 1.4.1-4 Common UNIX Printing System(tm) - ii foomatic-db20090616-1OpenPrinting printer support - dat ii foomatic-db-engine 4.0-20090509-1+b1 OpenPrinting printer support - pro ii hplip 3.9.4b-1 HP Linux Printing and Imaging Syst ii smbclient 2:3.4.2-1 command-line SMB/CIFS clients for ii udev 146-5 /dev/ and hotplug management daemo pn xpdf-korean | xpdf-jap none(no description available) -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, parallel, scsi, serial, socket, usb, snmp, dnssd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540059: Boot hangs during udev; udev segfaults several times
I should have specified that the above tests were carried out with the stock 2.6.30-1-amd64 kernel. Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540059: Boot hangs during udev; udev segfaults several times
On Saturday 15 August 2009 23:40:14 Marco d'Itri wrote: Boot with init=/bin/bash, open a second console using something like openvt and then start running manually the scripts in rcS.d/. This way you will be able to understand exactly where the boot process is hanging and why. Thanks for the debugging instructions. I appended init=/bin/bash to the boot line I then used the following commands: openvt -s bash cd /etc/rcS.d ./S01glibc start etc ./S03udev start hangs and produces the same last message as before the hang during normal boot. That message is input: HDA Intel HP out at Ext Front jack as /devices/pci:00/:00:1b.0/input/input9 So it does seem the problem is triggered by the udev start script. Any suggestions for how to narrow down the problem would be appreciated. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540059: Boot hangs during udev; udev segfaults several times
Package: udev Version: 0.141-1 Severity: important Following a large upgrade, my testing machine no longer boots correctly. It appears to hang, always at the same place, but will eventually continue. I have determined the following: - The hang occurs after messages relating to the sound card and before messages relating to the hard disk (the exact messages differ between kernels) - Ctrl-C during the hang will allow the boot to continue - It occurs with stock kernels 2.6.26-2-amd64, 2.6.28, 2.6.29, 2.6.30 - Rescue disks (testing of 04-Aug-2009 and 5.01) seem to boot correctly (the testing disk only works in graphical mode, but the problem with text mode doesn't appear to be the same, as the keyboard is hung also) - The udev version on the testing rescue disk appears to be the same as that installed - Reinstallation of the udev package doesn't help - Reinstallation of the kernel doesn't help (tested for 2.6.26-2-amd64) - Booting with UDEV_DISABLED=yes doesn't hang, but other things maybe don't work afterwards (e.g. konsole doesn't reach a prompt) (tested with 2.6.30) - bootchart seems to indicate that udev is holding things up and consuming near 100% CPU most of the time - dumping process information with sysrq during the hang lists udevd, vol_id, path_id, events/3 and sleep among runnable processes - on a single occasion, repeating error messages from mptbase were reported (I didn't note the exact message) - fsck reports no issues on the filesystem - Using Dell's bootable Drivers and Utilities disk to check the hardware reported no failures on any test, in particular there were no issues with the hard disk or sound card - After adding udev_log=debug in /etc/udev/udev.conf: --- *many* console messages fly past during the hang --- they include messages about sd_mod, bsg, block, so might indicate a disk issue --- if the boot is allowed to continue spontaneously, these messages do not appear in the system log, but several segfaults in udev are reported in the log --- if ctrl-c is issued during the hang, several hundred megabytes of udev messages are written to the log - googling for similar reports has not thrown up much (I have disabled the floppy in the bios and blacklisted the floppy module; booting with pci=nomsi does not resolve the problem either) I am open to suggestions for how to decide whether this is a bug or a hardware problem. I have most of the debugging output mentioned above available, but some of it is quite large, so I shall await instructions on what to send or how to analyse it. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 128 lrwxrwxrwx 1 root root19 2008-01-04 17:19 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root22 2008-01-04 19:58 025_logitechmouse.rules - ../logitechmouse.rules -rw-r--r-- 1 root root 495 2009-05-21 01:10 56-hpmud_support.rules -rw-r--r-- 1 root root 1137 2009-03-10 11:39 65_dmsetup.rules -rw-r--r-- 1 root root 700 2008-01-04 17:11 70-persistent-cd.rules -rw-r--r-- 1 root root 513 2009-08-05 11:28 70-persistent-net.rules -rw-r--r-- 1 root root 283 2009-05-22 19:20 85_dmraid.rules lrwxrwxrwx 1 root root15 2009-04-28 11:15 comedi.rules - ../comedi.rules lrwxrwxrwx 1 root root15 2008-03-05 12:05 libnjb.rules - ../libnjb.rules lrwxrwxrwx 1 root root15 2008-04-28 16:11 z60_hdparm.rules - ../hdparm.rules -rw-r--r-- 1 root root 5354 2009-03-17 11:09 z60_hplip.rules -rw-r--r-- 1 root root 13445 2009-06-30 10:31 z60_iscan.rules -rw-r--r-- 1 root root 1240 2009-04-06 20:06 z60_kpartx.rules -rw-r--r-- 1 root root 1914 2007-12-31 17:57 z60_libccid.rules -rw-r--r-- 1 root root 2656 2008-02-16 18:00 z60_libpisock9.rules -rw-r--r-- 1 root root 1152 2009-05-06 14:26 z60_libsane-extras.rules -rw-r--r-- 1 root root 55330 2009-06-26 14:46 z60_libsane.rules -rw-r--r-- 1 root root 6658 2008-10-31 13:35 z60_xserver-xorg-input-wacom.rules -- /sys/: /sys/dev /sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4/event4/dev /sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/bsg/sas_host6/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/bsg/end_device-6:0/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sda/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sda/sda1/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sda/sda2/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/block/sda/sda5/dev /sys/devices/pci:00/:00:02.0/:01:00.3/:05:0b.0/host6/port-6:0/end_device-6:0/target6:0:0/6:0:0:0/bsg/6:0:0:0/dev
Bug#540059: Some additional information
Because hdparm is run during the hang, I tried the command. It reports some problems : ...:/home/barbour# hdparm -I --verbose /dev/sda /dev/sda: outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 ec 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 18 00 00 00 00 20 00 00 c0 00 00 00 00 15 0a 00 00 00 00 00 00 00 00 00 00 outgoing cdb: 85 08 2e 00 00 00 00 00 00 00 00 00 00 40 a1 00 SG_IO: ATA_16 status=0x2, host_status=0x0, driver_status=0x8 SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 18 00 00 00 00 20 00 00 c0 00 00 00 00 15 0a 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(identify) failed: Invalid exchange Below is a snippet from the udev debugging output during the boot hang (there's lots more like it!): Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1403]: GROUP 6 /lib/udev/rules.d/91- permissions.rules:9 Aug 5 11:34:20 nrpc111 udevd-event[1454]: LINK 'char/253:2' /lib/udev/rules.d/50-udev.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN '/sbin/modprobe -b sd_mod' /lib/udev/rules.d/80-drivers.rules:29 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1403]: RUN '/etc/init.d/hdparm hotplug' /etc/udev/rules.d/z60_hdparm.rules:1 Aug 5 11:34:20 nrpc111 udevd-event[1454]: NAME 'bsg/6:0:0:0' /lib/udev/rules.d/50-udev.rules:20 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1403]: LINK 'block/8:0' /lib/udev/rules.d/50-udev.rules:1 Aug 5 11:34:20 nrpc111 udevd-event[1454]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN '/sbin/modprobe -b sd_mod' /lib/udev/rules.d/80-drivers.rules:29 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1403]: IMPORT 'edd_id --export /dev/block/8:0' /lib/udev/rules.d/60-persistent-storage.rules:52 Aug 5 11:34:20 nrpc111 udevd-event[1454]: LINK 'char/253:2' /lib/udev/rules.d/50-udev.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1403]: 'edd_id --export /dev/block/8:0' Aug 5 11:34:20 nrpc111 udevd-event[1454]: NAME 'bsg/6:0:0:0' /lib/udev/rules.d/50-udev.rules:20 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN '/sbin/modprobe -b sd_mod' /lib/udev/rules.d/80-drivers.rules:29 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1454]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1454]: LINK 'char/253:2' /lib/udev/rules.d/50-udev.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN '/sbin/modprobe -b sd_mod' /lib/udev/rules.d/80-drivers.rules:29 Aug 5 11:34:20 nrpc111 udevd-event[1569]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1987]: RUN 'socket:@/org/freedesktop/hal/udev_event' /lib/udev/rules.d/90-hal.rules:2 Aug 5 11:34:20 nrpc111 udevd-event[1454]: NAME 'bsg/6:0:0:0' /lib/udev/rules.d/50-udev.rules:20 Aug 5 11:34:20 nrpc111 udevd-event[1568]: RUN
