Nice work Benjamin. What options did you use for the configure? (More
specifically I guess I'm asking how to determine which options were used
in the official Ubuntu package).
--
2.6.24 reports invalid storage size in /sys [Sony Walkman NWZ-S618F doesn't
mount in Hardy]
Btw, rather than modifying the call to strtol() in util.c, would it not
be better to switch the call in blockdev.c to:
if (!hal_util_set_uint64_from_file (d,
volume.num_blocks, sysfs_path_real, size, 0)) {
And then in util.c change hal_util_set_uint64_from_file to use strtoll()
Sorry, that should have read to use strtoul() instead of strtoll().
--
2.6.24 reports invalid storage size in /sys [Sony Walkman NWZ-S618F doesn't
mount in Hardy]
https://bugs.launchpad.net/bugs/209483
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Fantastic, thanks Benjamin. I used two sed commands to implement the
change as I described above:
sed -i '255s/strtoll/strtoul/' hald/util.c
sed -i '1439s/_set_int_/_set_uint64_/' hald/linux/blockdev.c
FDI file for A828 attached.
It was necessary to manually add the Walkman as a UMS device in
I get roughly the same output in daemon.log as Benjamin:
Apr 27 16:56:46 hostname hald[4243]: 16:56:46.111 [I] blockdev.c:874:
block_add: sysfs_path=/sys/block/sdc/sdc1 dev=/dev/sdc1 is_part=1,
parent=0x080cf560
Apr 27 16:56:46 hostname hald[4243]: 16:56:46.112 [I] blockdev.c:1448: Ignoring
It might be worth noting that the A828, A818 and S618 support MTP as
well as mass-storage modes. Is there a way to force the kernel to pick
them up as MTP devices rather than mass storage?
--
Regression: Sony Walkman NWZ-S618F doesn't mount in Hardy
https://bugs.launchpad.net/bugs/209483
You
Seeing this same behaviour using Kubuntu Hardy with all updates to 20th
April 2008. Just connected a Sony NWZ -A828 and get the attempt to
access beyond end of device and p1 exceeds device capacity messages.
--
Regression: Sony Walkman NWZ-S618F doesn't mount in Hardy
Have taken advise from the LKML and the IOWait figures are considered
normal -- they indicate the time the CPU spends idle waiting for IO.
Other processes can make use of these idle cycles, so although the CPU
appears pegged at 100% it does in fact still have available cycles.
--
100% CPU usage
Marked as invalid as it's not a bug.
** Changed in: linux-meta (Ubuntu)
Status: New = Invalid
--
100% CPU usage during disk I/O with SATA/PATA
https://bugs.launchpad.net/bugs/192353
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you run Dolphin from a console window, what output do you get?
--
Dolphin shows BROKEN TRANSLATION
https://bugs.launchpad.net/bugs/164873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Anyway, the command in the console should be d3lphin.
There's a symlink from dolphin to d3lphin so it shouldn't matter
which you run.
The problem with the PPA source constantly wanting to upgrade seems to
have gone away, so you should be able to leave that in after running the
update now.
I'm
Have you tried adding the daily snapshot PPA as described above?
--
Dolphin shows BROKEN TRANSLATION
https://bugs.launchpad.net/bugs/164873
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
I'm seeing 100% CPU usage during SATA disk I/O in a new PC I've put
together. The machine consists of:
MSI K9N6GM-V Mainboard (nForce 410, MCP61)
AMD Sempron LE1100 CPU
512MB Generic 667MHz DDR2 Memory (PC2-5400)
Western Digital WD800AAJS 80GB Hard Drive (SATA-II)
Optiarc
Modified the bug title since this does seem to affect serial *and*
parallel ATA.
--
100% CPU usage during disk I/O with SATA/PATA
https://bugs.launchpad.net/bugs/192353
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I managed to dig out a PATA drive to repeat the above tests on the same
machine. Interestingly, this also wipes out 100% CPU, which I must admit
I wasn't expecting!
$ dd if=/dev/zero of=testfile
procs ---memory-- ---swap-- -io -system-- cpu
r b swpd free
Have been running Stijn's patch for the last 24 hours and every
suspend/resume has worked perfectly so far.
There still remains the question of whether this is a bug in HAL or in
the power manager, but for the time being the fix to the power manager
is working well for me :)
--
Feisty HAL
Stijn Vansummeren wrote on 2008-01-25:
(It is possible that this bug has already been fixed in the current
development
version of kde-guidance. I have been unable to find where to get the
development
version, however.)
Assuming I have the right location for the current KDE3/KDE4
*** This bug is a duplicate of bug 114595 ***
https://bugs.launchpad.net/bugs/114595
** This bug has been marked a duplicate of bug 114595
Feisty HAL upgrade broke suspend on lid close
--
guidance-power-manager needs restarting after resume in order to suspend again
After knocking up a very dodgy patch to getLidClosedState() I stumbled
across another bug in Launchpad that describes what appears to be a
proper fix:
https://bugs.launchpad.net/bugs/151648
--
Feisty HAL upgrade broke suspend on lid close
https://bugs.launchpad.net/bugs/114595
You received this
Getting the same problem here on Kubuntu Gutsy on a Dell Latitude D610.
The symptoms I see are that first suspend works, and then none after
that work. If I quit the Power Manager app and restart it, I get one
suspend and then subsquently suspend doesn't work again.
I'm afraid my Python skills
Here's a working d3lphin.mo file you can use temporarily until the
updated translations are released.
Rename your existing file and put this in its place as:
/usr/share/locale-langpack/en_GB/LC_MESSAGES/d3lphin.mo
** Attachment added: Updated Dolphin translation file to resolve BROKEN
The current version of the language pack in the repo is still from 27th
November 2007, so the updates definitely haven't made it there yet.
--
Dolphin shows BROKEN TRANSLATION
https://bugs.launchpad.net/bugs/164873
You received this bug notification because you are a member of Ubuntu
Bugs, which
I contacted the package maintainer, Martin Pitt, and he suggested adding
the repo for daily snapshots to sources.list:
deb http://ppa.launchpad.net/ubuntu-langpack/ubuntu gutsy main
The version there (currently 08/01/2008) works correctly, however after
adding the new apt source it wouldn't
Can confirm that this was user error, though the default settings for
the sticky keys may well cause problems for anyone playing shooters on
Kubuntu.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
--
Xorg sporadically requires long keypresses in order to register typing
The problem lies in the file /usr/share/locale-
langpack/en_GB/LC_MESSAGES/d3lphin.mo -- there are three translations at
the end of the file that are missing their plural versions.
For example, an original string is:
_n: 1 Item\n
%n Items
And the translated string is:
1 Item
The Translated
Public bug reported:
Although my Kubuntu Gutsy system is configured to use double-click for
launching icons, the System Settings application still uses a single-
click to launch modules.
Under System Settings - Keyboard Mouse - Mouse Settings - Icons, I
have chosen Double-click to open files
Public bug reported:
Binary package hint: xorg
Seemingly at random, my keyboard appears to stop responding in X
applications. I have had this problem very occasionally in Kubuntu
Feisty, and since upgrading to Gutsy I am seeing it much more
frequently. In each case the mouse continues to work.
One other possibly useful piece of information is that when the problem
occurs, interrupts seem to be generated by the i8042 as normal -- i.e. I
can see two interrupts against i8042 in /proc/interrupts for each brief
key press/release, even though that keypress is not registered in X
applications.
Having looked into the settings a little further, it turns out it
*might* be the gestures turning on Slow Keys.
I have the use system bell option enabled for gestures, but for some
reason there is no beep when a gesture is activated.
Will disable all gestures and see if the problem goes away.
If you are still seeing the bug, run dpkg-query -l adept-updater and
make sure you have version 2.1.3ubuntu17.1 or later.
--
feisty dist upgrade check does not work
https://bugs.launchpad.net/bugs/153889
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I certainly got the impression from Martin Pitt's comment that the
update had been made live, however I originally installed it by
selecting Proposed Updates in Adept Manager, upgrading all of the
Adept-related packages, and then de-selecting the proposed updates.
--
feisty dist upgrade check
*** This bug is a duplicate of bug 153889 ***
https://bugs.launchpad.net/bugs/153889
I have seen this bug on all three machines on which I run Kubuntu Gutsy.
The various install methods were:
1. Feisty, upgraded to Gutsy Beta, upgraded to Gutsy (using Adept)
2. Feisty, upgraded to Gutsy
*** This bug is a duplicate of bug 153889 ***
https://bugs.launchpad.net/bugs/153889
The adept updates in gutsy-proposed (as mentioned in the comments for
bug #153889) might have done the trick. Updated all adept components to
2.1.3ubuntu17.1 and the version upgrade option has disappeared
/etc/hosts:
127.0.0.1 localhost
127.0.1.1 gmckeown-laptop
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
/etc/hostname:
gmckeown-laptop
The
Having the same problem here on Kubuntu Feisty. The hplip daemon seems
to start OK. A side effect is that when trying to add a printer via
KDE's System Settings, the program hangs for a couple of minutes before
allowing me to add a printer.
* Netstat reports:
tcp0 0 127.0.0.1:2208
Btw, ignore the difference in hostnames in the log excerpts -- that was
a half-hearted attempt to shorten the line-lengths... D'oh.
--
tools can't connect to hpiod
https://bugs.launchpad.net/bugs/75483
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
36 matches
Mail list logo
