Bug#832265: suck: Stack smash if lockfile exists (pid_t cast to long *)
Package: suck
Version: 4.3.2-15+b1
Severity: important
Tags: security upstream
The switch to using -fstack-protector-strong in stretch has exposed a
stack-smashing bug.
The problem affects 64-bit platforms, as the code is assuming
sizeof(pid_t) == sizeof(long), yet on x86_64:
sizeof(pid_t) == 4
sizeof(long) == 8
The relevant code is in suckutils.c, do_lockfile():
int do_lockfile(PMaster master) {
...
pid_t pid;
...
fscanf(f_lock, "%ld", (long *) &pid);
...
}
This writes an 8-byte long to the location of the 4-byte pid variable,
smashing 4 bytes of the stack.
I doubt this is usefully exploitable (with the stack protector enabled,
it's only overwriting the canary), but it does mean a stale lockfile
causes suck to crash (but helpfully, the lockfile is unlinked before the
crash, so the next run will be successful).
This is obviously an upstream bug, but unfortunately there no longer
appears to be an upstream...
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages suck depends on:
ii debconf [debconf-2.0] 1.5.59
ii libc6 2.23-1
ii libssl1.0.21.0.2h-1
Versions of packages suck recommends:
ii perl 5.22.2-2
Versions of packages suck suggests:
ii inn2 [news-transport-system] 2.6.0-2
ii slrn [news-reader]1.0.2-5
-- no debconf information
Bug#773984: lvm2: New package python-lvm2 to install Python bindings for liblvm2app2.2
Source: lvm2
Version: 2.02.111-2
Severity: wishlist
Tags: patch
The upstream lvm2 source includes Python bindings for the lilvm2app2.2 API.
These would be useful for scripting snapshots for backups, etc., but are
not enabled in the current Debian packages.
I have attached a patch I created to locally enable the Python bindings to be
built
and installed as a separate package (python-lvm2).
I have not submitted a patch to Debian before, so apologies if I've
got anything wrong (particularly the Python-related bits!).
--
David Taylor
diff -Nru lvm2-2.02.111/debian/changelog lvm2-2.02.111/debian/changelog
--- lvm2-2.02.111/debian/changelog 2014-09-25 21:05:16.0 +0200
+++ lvm2-2.02.111/debian/changelog 2014-12-21 19:55:15.0 +0100
@@ -1,3 +1,9 @@
+lvm2 (2.02.111-3) experimental; urgency=medium
+
+ * Add new binary package python-lvm2, with liblvm2app2.2 python bindings.
+
+ -- David Taylor Fri, 19 Dec 2014 22:30:13 +
+
lvm2 (2.02.111-2) unstable; urgency=medium
* Install additional man-pages. (closes: #587277, #760679)
diff -Nru lvm2-2.02.111/debian/control lvm2-2.02.111/debian/control
--- lvm2-2.02.111/debian/control 2014-09-06 18:47:11.0 +0200
+++ lvm2-2.02.111/debian/control 2014-12-21 19:55:15.0 +0100
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Debian LVM Team
Uploaders: Bastian Blank
-Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 8.1.3~), dh-systemd, automake, libcman-dev (>> 2), libcorosync-dev, libdlm-dev (>> 2), libreadline-gplv2-dev, libselinux1-dev, libudev-dev, openais-dev, pkg-config
+Build-Depends: dpkg-dev (>= 1.16.1~), debhelper (>= 8.1.3~), dh-systemd, automake, libcman-dev (>> 2), libcorosync-dev, libdlm-dev (>> 2), libreadline-gplv2-dev, libselinux1-dev, libudev-dev, openais-dev, pkg-config, dh-python, python-all-dev (>= 2.6.6-3~)
Standards-Version: 3.9.5
Homepage: http://sources.redhat.com/lvm2/
Vcs-Svn: svn://svn.debian.org/pkg-lvm/lvm2/trunk/
@@ -165,6 +165,15 @@
to the basic LVM objects and provides functions to enumerate, create or
modify them.
+Package: python-lvm2
+Section: python
+Architecture: any
+Depends: ${shlibs:Depends}, ${misc:Depends}, liblvm2app2.2 (= ${binary:Version}), ${python:Depends}
+Multi-Arch: same
+Description: Python bindings for LVM2 application library
+ This package contains the Python bindings for the lvm2app shared library.
+ It allows the LVM2 API to be used from Python scripts.
+
Package: liblvm2cmd2.02
Section: libs
Architecture: any
diff -Nru lvm2-2.02.111/debian/python-lvm2.install lvm2-2.02.111/debian/python-lvm2.install
--- lvm2-2.02.111/debian/python-lvm2.install 1970-01-01 01:00:00.0 +0100
+++ lvm2-2.02.111/debian/python-lvm2.install 2014-12-21 19:55:15.0 +0100
@@ -0,0 +1 @@
+usr/lib/python2.7/site-packages/lvm.so
diff -Nru lvm2-2.02.111/debian/rules lvm2-2.02.111/debian/rules
--- lvm2-2.02.111/debian/rules 2014-09-14 23:37:03.0 +0200
+++ lvm2-2.02.111/debian/rules 2014-12-21 19:55:15.0 +0100
@@ -94,7 +94,8 @@
--enable-pkgconfig \
--enable-readline \
--enable-udev_rules \
- --enable-udev_sync
+ --enable-udev_sync \
+ --enable-python_bindings
touch $@
$(STAMPS_DIR)/setup_udeb: SOURCE_DIR = $(BUILD_DIR)/source
@@ -241,6 +242,14 @@
dh_makeshlibs -V -- -c2
+$(MAKE_SELF) install-base
+install_python-lvm2: export DH_OPTIONS = -ppython-lvm2
+install_python-lvm2: DIR = $(BUILD_DIR)/install_deb
+install_python-lvm2: install_liblvm2
+ +$(MAKE_SELF) install-base-prep INSTALL_DIR='$(DIR)'
+ dh_makeshlibs -V -- -c2
+ dh_python2
+ +$(MAKE_SELF) install-base
+
install_lvm2: export DH_OPTIONS = -plvm2
install_lvm2: DIR = $(BUILD_DIR)/install_deb
install_lvm2: $(STAMPS_DIR)/install_deb
@@ -258,7 +267,7 @@
+$(MAKE_SELF) install-base
binary-indep:
-binary-arch: $(addprefix install_,libdevmapper libdevmapper-udeb libdevmapper-event libdevmapper-dev dmsetup dmsetup-udeb dmeventd liblvm2 lvm2 lvm2-udeb clvm)
+binary-arch: $(addprefix install_,libdevmapper libdevmapper-udeb libdevmapper-event libdevmapper-dev dmsetup dmsetup-udeb dmeventd liblvm2 python-lvm2 lvm2 lvm2-udeb clvm)
binary: binary-indep binary-arch
Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots
Package: systemd Version: 232-13 Severity: critical Justification: breaks the whole system Currently running systemd_231-9, first experienced this problem when trying to upgrade to 232-8, 232-13 is still giving the same problem. During upgrade or boot systemd aborts due to an assertion failure: Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT): systemd[1]: Caught , dumped core as pid 1535. Message from syslogd@ Jan 22 12:59:45 ... systemd[1]: Caught , dumped core as pid 1535. Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT): systemd[1]: Freezing execution. Message from syslogd@deb550s at Jan 22 12:59:45 ... systemd[1]: Freezing execution. syslog shows: systemd[1]: Assertion 'u' failed at ../src/core/unit.c:521, function unit_free(). Aborting. A similar problem appears to have been fixed upstream: https://github.com/systemd/systemd/issues/4747 -- Package-specific info: -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-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 Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.115 ii libacl1 2.2.52-3 ii libapparmor12.11.0-1 ii libaudit1 1:2.6.7-1 ii libblkid1 2.29-1 ii libc6 2.24-8 ii libcap2 1:2.25-1 ii libcryptsetup4 2:1.7.3-3 ii libgcrypt20 1.7.5-2 ii libgpg-error0 1.26-1 ii libidn111.33-1 ii libip4tc0 1.6.0+snapshot20161117-4 ii libkmod223-2 ii liblz4-10.0~r131-2 ii liblzma55.2.2-1.2 ii libmount1 2.29-1 ii libpam0g1.1.8-3.5 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3 ii libsystemd0 232-13 ii mount 2.29-1 ii util-linux 2.29-1 Versions of packages systemd recommends: ii dbus1.10.14-1 ii libpam-systemd 232-13 Versions of packages systemd suggests: ii policykit-10.105-17 pn systemd-container pn systemd-ui Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.126 ih udev 232-13 -- no debconf information
Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots
On Sun, 22 Jan 2017, Michael Biebl wrote: Control: tags -1 + moreinfo Am 22.01.2017 um 14:14 schrieb David Taylor: Currently running systemd_231-9, first experienced this problem when trying to upgrade to 232-8, 232-13 is still giving the same problem. Upgrading from -9 to -8? I guess you mistyped this. What is the first version you encountered the problem? Which version was still working fine? Were other changes made to the system? No typo - the first failed upgrade was from 231-9 to 232-8. Nothing else changed at that time (except other package upgrades, but they seem irrelevant, given that downgrading to 231-9 leaves a working system and upgrading to either 232-8 or 232-13 leaves it failing to boot.) During upgrade or boot systemd aborts due to an assertion failure: Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT): systemd[1]: Caught , dumped core as pid 1535. Message from syslogd@ Jan 22 12:59:45 ... systemd[1]: Caught , dumped core as pid 1535. Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT): systemd[1]: Freezing execution. Message from syslogd@deb550s at Jan 22 12:59:45 ... systemd[1]: Freezing execution. syslog shows: systemd[1]: Assertion 'u' failed at ../src/core/unit.c:521, function unit_free(). Aborting. A similar problem appears to have been fixed upstream: https://github.com/systemd/systemd/issues/4747 Can you attach the core file (should be found at /core) from the crash with the exact systemd version you were using. I built the systemd_232-13 package locally from source, so I'm not sure how useful the core file would be to you. I have reproduced the backtrace below. If you need any more details (or feel the core would still be useful) let me know. Reading symbols from /bin/systemd...Reading symbols from /usr/lib/debug/.build-id/24/30880e7d50808599be7bb2bafe54dab1a14bb8.debug...done. done. [New LWP 5370] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/lib/systemd/systemd --system --deserialize 19'. Program terminated with signal SIGABRT, Aborted. (gdb) bt #0 0x7f7f747302f7 in kill () at ../sysdeps/unix/syscall-template.S:84 #1 0x560a0a3188aa in crash (sig=6) at ../src/core/main.c:189 #2 #3 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 #4 0x7f7f7473140a in __GI_abort () at abort.c:89 #5 0x7f7f75ebd4c2 in log_assert_failed (text=, file=, line=, func=) at ../src/basic/log.c:795 #6 0x560a0a3838c1 in unit_free (u=) at ../src/core/unit.c:521 #7 0x560a0a32c4a0 in device_setup_unit.lto_priv.274 (m=m@entry=0x560a0ab5e800, dev=dev@entry=0x560a0ac26690, path=path@entry=0x560a0ac2cef0 "/dev/disk/by-partlabel/", '†' , main=main@entry=false) at ../src/core/device.c:369 #8 0x560a0a32cc20 in device_process_new.lto_priv.276 (m=0x560a0ab5e800, dev=0x560a0ac26690) at ../src/core/device.c:420 #9 0x560a0a36bf15 in device_enumerate.lto_priv.149 (m=0x560a0ab5e800) at ../src/core/device.c:689 #10 0x560a0a360a1f in manager_enumerate (m=) at ../src/core/manager.c:1141 #11 0x560a0a312389 in manager_startup (fds=0x560a0ab5f2d0, serialization=, m=0x560a0ab5e800) at ../src/core/manager.c:1269 #12 main (argc=4, argv=) at ../src/core/main.c:1774 The above bug report suggests a problem with unicode partition labels. Do you have such a partition? I didn't think so, but double-checking in /dev/disk/by-partlabel shows I do have an NTFS partition with the label †††: # ls -l /dev/disk/by-partlabel/ total 0 lrwxrwxrwx 1 root root 10 Jan 22 13:19 ††† -> ../../sdb3 lrwxrwxrwx 1 root root 10 Jan 22 13:19 EFI\x20system\x20partition -> ../../sdb1 lrwxrwxrwx 1 root root 10 Jan 22 13:19 Microsoft\x20reserved\x20partition -> ../../sdb2 I'm not sure where that PARTLABEL came from (I definitely didn't choose it), but the filesystem is part of a Windows 10 install. Can you reproduce the problem reliably? Do you know how we can reproduce the problem? Yes, the problem occurs every time I upgrade the package (or reboot with the upgraded package installed). I assume you could reboot it by creating an NTFS filesystem with PARTLABEL="†††" -- David Taylor
Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots
Hi Michael, On Sun, 22 Jan 2017, Michael Biebl wrote: Am 22.01.2017 um 18:20 schrieb David Taylor: On Sun, 22 Jan 2017, Michael Biebl wrote: Am 22.01.2017 um 14:14 schrieb David Taylor: I built the systemd_232-13 package locally from source, so I'm not sure how useful the core file would be to you. I have reproduced the backtrace below. If you built 232-13 from source, can you cherry-pick the upstream patch and see if that fixes your issue? We might then cherry-pick that patch in the official package as well. I can prepare packages if you prefer that. I cherry-picked the two commits referenced by the upstream issue #4747: d112eae7da77899be245ab52aa1747d4675549f1 device: Avoid calling unit_free(NULL) in device setup logic (#4748) c9d5c9c0e19eea79ca0f09fe58e5c0b76b8001e2 core: make unit_free() accept NULL pointers They have resolved the problem -- 232-13 plus those two patches is now running successfully on my machine. The above bug report suggests a problem with unicode partition labels. Do you have such a partition? I didn't think so, but double-checking in /dev/disk/by-partlabel shows I do have an NTFS partition with the label †††: # ls -l /dev/disk/by-partlabel/ total 0 lrwxrwxrwx 1 root root 10 Jan 22 13:19 ††† -> ../../sdb3 Ah, ok. So this is a dual boot system, I assume. Yes, dual boot with Windows 10. Is /dev/sdb3 the partition holding the actual Windows 10 system? [1] suggests that the partition layout is System | MSR | Windows | Recovery Yes, it's the main Windows partition. If you boot Windows, what's the partion label shown there? Is it the default label created by the Windows installer? blkid shows: /dev/sdb1: LABEL="SYSTEM" UUID="5C7A-5FAE" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="8bc4e64e-f2b7-47da-8048-ab445242bf /dev/sdb2: PARTLABEL="Microsoft reserved partition" PARTUUID="dd5c4d6d-dd1b-4908-b83e-e6b44d12ca63" /dev/sdb3: LABEL="win550s" UUID="886450D76450C998" TYPE="ntfs" PARTLABEL="†††" PARTUUID="77178a46-30b6-11e5-9bd1-5ce0c5c724c2" Windows displayes the volume label as win550s (which I set, manually when installing). For some reason the GPT partition label has been set to †††, although the two other Windows partitions have sensible partition labels. -- David Taylor
Bug#307202: More detail
I wish to add that I am using an Nvidia graphics card (nVidia Corporation NV18 [GeForce MX 440 AGP 8x]) using the Nvidia drivers (built from nvidia-kernel-source 1.0.7174-3) and some unbranded generic monitor but has happened since I first started using the nVidia drivers. This happens on resolutions 1280x1024, 1280x960, 1024x760, 800x600 and downwards I presume. It doesn't seem to occur with the basic "nv" drivers at 1024x760 but I have never managed to put them on a resolution other than that. This also seems to happen on the Politics, Health, Business, Wales, Scotland, England, UK and World sections but not the Science and Nature, Education, Northern Ireland News front page and Entertainment which are fine. Thanks DT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#303306: Crash whilst using www.torrentsearch.us
Package: konqueror Version: 4:3.3.2-1 When one goes to http://www.torrentsearch.us , searches for a torrent (any will do) clicks on it, selects open from the pop-up so that the garbled text of the torrent file appears and presses the back button konqueror will just crash and this is reproducible. I've got all the details from "The KDE Crash Handler" if this helps at all (I've removed all the "No debugging symbols found" but can post them up if needs be): Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at 0xe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1229971328 (LWP 10016)] [KCrash handler] #3 0xb6399ea7 in KHTMLPart::browserExtension () from /usr/lib/libkhtml.so.4 #4 0xb64fe035 in EmbedLiveConnect::~EmbedLiveConnect () from /usr/lib/libkhtml.so.4 #5 0xb62a9670 in KJS::Reference::getValue () from /usr/lib/libkjs.so.1 #6 0xb626de42 in KJS::timeClip () from /usr/lib/libkjs.so.1 #7 0xb626fd89 in KJS::timeClip () from /usr/lib/libkjs.so.1 #8 0xb626ff83 in KJS::timeClip () from /usr/lib/libkjs.so.1 #9 0xb627062b in KJS::timeClip () from /usr/lib/libkjs.so.1 #10 0xb6274fca in KJS::timeClip () from /usr/lib/libkjs.so.1 #11 0xb627ba3c in KJS::timeClip () from /usr/lib/libkjs.so.1 #12 0xb6274ddf in KJS::timeClip () from /usr/lib/libkjs.so.1 #13 0xb627aee3 in KJS::timeClip () from /usr/lib/libkjs.so.1 #14 0xb629dd7c in KJS::DeclaredFunctionImp::execute () from /usr/lib/libkjs.so.1 #15 0xb629d14c in KJS::FunctionImp::call () from /usr/lib/libkjs.so.1 #16 0xb62a26b0 in KJS::Object::call () from /usr/lib/libkjs.so.1 #17 0xb6270943 in KJS::timeClip () from /usr/lib/libkjs.so.1 #18 0xb6274fca in KJS::timeClip () from /usr/lib/libkjs.so.1 #19 0xb627ba3c in KJS::timeClip () from /usr/lib/libkjs.so.1 #20 0xb6274ddf in KJS::timeClip () from /usr/lib/libkjs.so.1 #21 0xb627aee3 in KJS::timeClip () from /usr/lib/libkjs.so.1 #22 0xb629dd7c in KJS::DeclaredFunctionImp::execute () from /usr/lib/libkjs.so.1 #23 0xb629d14c in KJS::FunctionImp::call () from /usr/lib/libkjs.so.1 #24 0xb62a26b0 in KJS::Object::call () from /usr/lib/libkjs.so.1 #25 0xb6270943 in KJS::timeClip () from /usr/lib/libkjs.so.1 #26 0xb6274fca in KJS::timeClip () from /usr/lib/libkjs.so.1 #27 0xb627ba3c in KJS::timeClip () from /usr/lib/libkjs.so.1 #28 0xb6274ddf in KJS::timeClip () from /usr/lib/libkjs.so.1 #29 0xb627aee3 in KJS::timeClip () from /usr/lib/libkjs.so.1 #30 0xb6292737 in KJS::SourceCode::cleanup () from /usr/lib/libkjs.so.1 #31 0xb62a464a in KJS::Interpreter::evaluate () from /usr/lib/libkjs.so.1 #32 0xb6504a7f in EmbedLiveConnect::~EmbedLiveConnect () from /usr/lib/libkhtml.so.4 #33 0xb639aead in KHTMLPart::executeScript () from /usr/lib/libkhtml.so.4 #34 0xb63fcaa6 in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #35 0xb64017ed in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #36 0xb64ad541 in QPtrList::deleteItem () from /usr/lib/libkhtml.so.4 #37 0xb63fc97f in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #38 0xb63fc2f4 in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #39 0xb63ff107 in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #40 0xb640051c in KStaticDeleter >::~KStaticDeleter () from /usr/lib/libkhtml.so.4 #41 0xb639f5e7 in KHTMLPart::write () from /usr/lib/libkhtml.so.4 #42 0xb639dfe9 in KHTMLPart::slotRestoreData () from /usr/lib/libkhtml.so.4 #43 0xb63ba670 in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #44 0xb72235ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #45 0xb63c79fa in KHTMLPageCacheDelivery::emitData () from /usr/lib/libkhtml.so.4 #46 0xb63c732b in KHTMLPageCache::sendData () from /usr/lib/libkhtml.so.4 #47 0xb63c7788 in KHTMLPageCache::qt_invoke () from /usr/lib/libkhtml.so.4 #48 0xb72235ac in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #49 0xb756126a in QSignal::signal () from /usr/lib/libqt-mt.so.3 #50 0xb723d78d in QSignal::activate () from /usr/lib/libqt-mt.so.3 #51 0xb7244f73 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #52 0xb71c6bff in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #53 0xb71c61fe in QApplication::notify () from /usr/lib/libqt-mt.so.3 #54 0xb7800e43 in KApplication::notify () from /usr/lib/libkdecore.so.4 #55 0xb71b6425 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #56 0xb716fc6b in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #57 0xb71d8f58 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #58 0xb71d8e08 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #59 0xb71c6e51 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #60 0xb69f4e4c in kdemain () from /usr/lib/libkdeinit_konqueror.so #61 0xb6a98896 in kdeinitmain () from /usr/lib/kde3/konqueror.so #62 0x0804cd30 in ?? () #63 0x0002 in ?? () #64 0x080701c8 in ?? () #65 0x0001 in ?? () #66 0x in ?? () #67 0x0
Bug#307201: Konqueror displaying undesired behaviour at www.deviantart.com
Package: konqueror Version: 4:3.3.2-1 When I go to www.deviantart.com and haven't logged in so the Username and Password boxes and login button are showing, they vibrate up and down a pixel very rapidly and do not allow text to be entered in to the their fields. For anyone who has found this a problem you can go to http://shop.deviantart.com/join/ to log in using Konqueror and not face the same problems as with the normal login mechanism. Dave Taylor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#307202: BBC's technology news website drawn incorrectly
Package: konqueror Version: 4:3.3.2-1 When I go to http://news.bbc.co.uk/1/hi/technology/default.stm in konqueror there is a main article at the top followed by two articles below that (they are taking up half the space of the main story) and two more articles below them however they are contained within a green band (I'm not completely sure if it is Green as I am colour blind), that green band draws up incorrectly as it is supposed to be straight but is broken up across the bottom. Dave Taylor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
