[Bug 141168] /bin/kill not compatible with redhat/opensuse

2007-09-20 Thread plord
Public bug reported: Binary package hint: coreutils Ubuntu ships /bin/kill from the procps package whilst other distributions ( such as redhat and opensuse ) use /bin/kill from coreutils. In most cases this doesn't matter, but the two commands do behave differently, especially in the use of proc

[Bug 139186] kde4 beta2 kmail ( and others ) fail

2007-09-12 Thread plord
Public bug reported: Binary package hint: kde4pim Following the instructions for kde4 on gusty, I can't get kmail ( or other pim applications ) running. Starting with kconsole running on kde3, I type :- $ export LD_LIBRARY_PATH=/usr/lib/kde4/lib $ export KDEDIRS=/usr/lib/kde4 $ export PATH=/usr

[Bug 138939] Re: [gutsy] acroread fails to startup

2007-09-12 Thread plord
*** This bug is a duplicate of bug 131949 *** https://bugs.launchpad.net/bugs/131949 I removed my install from the adobe web site and installed acroread from medibuntu instead ( and restored the libgtk-x11 sym links ) and all is now well :-) Many thanks ! Pete -- [gutsy] acroread fails to

[Bug 138939] Re: [gutsy] acroread fails to startup

2007-09-12 Thread plord
*** This bug is a duplicate of bug 131949 *** https://bugs.launchpad.net/bugs/131949 I'm using the download from adobe - although I see there is now a slightly newer version which I try ( I have 7.0.8 ) http://ardownload.adobe.com/pub/adobe/reader/unix/7x/7.0.9/enu/AdobeReader_enu-7.0.9-1.i38

[Bug 138939] [gutsy] acroread fails to startup

2007-09-11 Thread plord
Public bug reported: Binary package hint: acroread When starting acroread from the command line I see :- $ acroread 2>&1 | more expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax error expr: syntax err

[Bug 137916] CONFIG_NO_HZ

2007-09-07 Thread plord
Public bug reported: The powertop utility ( http://www.linuxpowertop.org/ ) recommends the following kernel configuration to reduce notebook power consumption :- Suggestion: Enable the CONFIG_NO_HZ kernel configuration option. This option is required to get any kind of longer sleep times in the C

[Bug 133362] Re: Gutsy x86-64 libc/gcc COMPLETELY BREAK valgrind

2007-09-04 Thread plord
Just hit this myself as well. It looks like this has already been fixed, see http://bugs.kde.org/show_bug.cgi?id=148447 -- Gutsy x86-64 libc/gcc COMPLETELY BREAK valgrind https://bugs.launchpad.net/bugs/133362 You received this bug notification because you are a member of Ubuntu Bugs, which is t

Re: [Bug 136330] Re: kterm - unknown terminal type

2007-09-02 Thread plord
Sarah Hobbs wrote, On 09/03/07 04:26: > I cant reproduce this. > > ncurses-term is dependancy of x11-common, so should automatically get > installed here. I cant really see the point of adding the dependancy > here as well. > Well, I had x11-common installed without ncurses-term ... so I guess

[Bug 136330] kterm - unknown terminal type

2007-08-31 Thread plord
Public bug reported: Binary package hint: konsole When running top in konsole I see :- bash$ top 'kterm': unknown terminal type. Also mailx reports "WARNING: terminal is not fully functional" I see usr/share/terminfo/k/kterm is shipped in ncurses-term, I think this package should be a dependen

Re: [Bug 135881] Re: /bin/arch missing

2007-08-30 Thread plord
Basilio Kublik wrote, On 08/30/07 17:39: > this seems to be a natural progression of the application since there's > no point in include another binary that does the same as other already > installed and which have more features. > > I'm tempted to mark this bug as invalid, but i let the decision t

[Bug 135881] /bin/arch missing

2007-08-30 Thread plord
Public bug reported: Binary package hint: util-linux /bin/arch appears to be missing from the latest version of util-linux ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- /bin/arch missing https://bugs.launchpad.net/bugs/135881 You received this bug notificat

[Bug 133710] Re: Blank screen on tribe4 boot

2007-08-25 Thread plord
Ah, some progress. If I use X to generate a configuration file ( attached ) then X fires up. So a work-around to boot tribe4/tribe5 is :- 1) boot up in single user mode 2) X -config 3) cp /root/xorg.conf.new /etc/X11/xorg.conf 4) init 3 ** Attachment added: "xorg.conf generated by X -config"

[Bug 133710] Re: Blank screen on tribe4 boot

2007-08-25 Thread plord
Oh, I found the full log - see attached ** Attachment added: "xorg.0.log" http://launchpadlibrarian.net/8983259/Xorg.0.log -- Blank screen on tribe4 boot https://bugs.launchpad.net/bugs/133710 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact

[Bug 133710] Re: Blank screen on tribe4 boot

2007-08-25 Thread plord
Debugging further :- 1) remove the splash and quiet options from the boot line, added single to boot up in single user mode 2) run X -probeonly This is what I see :- X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System:

[Bug 133710] Re: Blank screen on tribe4 boot

2007-08-24 Thread plord
tribe5 x86_64 also gives a blank screen on boot -- Blank screen on tribe4 boot https://bugs.launchpad.net/bugs/133710 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https:/

[Bug 133710] Re: Blank screen on tribe4 boot

2007-08-21 Thread plord
Note that Feisty Fawn x86_64 cd boots fine, as does tribe 3 gusty gibbon. Its just tribe 4 which seems to get the graphics wrong. -- Blank screen on tribe4 boot https://bugs.launchpad.net/bugs/133710 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug con

[Bug 133710] Blank screen on tribe4 boot

2007-08-20 Thread plord
Public bug reported: Whilst booting x86_64 version of kubuntu gutsy tribe4 on a dell inspiron 9400 I just get a blank screen. The machine is on the network ( ping works ) and I see some ntp traffic, but I can't access the machine from either the keyboard or ssh, so I have no logs. This also happ