[Bug 137916] CONFIG_NO_HZ
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 CPU. Does it make sense to enable this in the shipped kernel ? ** Affects: ubuntu Importance: Undecided Status: New -- CONFIG_NO_HZ https://bugs.launchpad.net/bugs/137916 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138939] [gutsy] acroread fails to startup
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 error This seems to be because the script tries to get the verion number from libgtk and fails ... the file I have installed is :- libgtk-x11-2.0.so.0.1106.0 Add in set -x to the script it starts to fail when getting the version number :- + echo libgtk-x11-2.0.so.0.1106.0 + sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g' + return 0 + version='' + [ 0 -ne 0 ] + expr length expr: syntax error ** Affects: acroread (Ubuntu) Importance: Undecided Status: New -- [gutsy] acroread fails to startup https://bugs.launchpad.net/bugs/138939 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138939] Re: [gutsy] acroread fails to startup
*** 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.i386.tar.gz I worked around this issue by breaking the sym link at libgtk-x11-2.0.so & libgtk-x11-2.0.so.0 rm libgtk-x11-2.0.so cp libgtk-x11-2.0.so.0.1106.0 libgtk-x11-2.0.so.0 rm libgtk-x11-2.0.so.0 cp libgtk-x11-2.0.so.0.1106.0 libgtk-x11-2.0.so.0 I'm not sure why this library has this extra weird version number ... perhaps this is really a bug with libgk-x11. -- [gutsy] acroread fails to startup https://bugs.launchpad.net/bugs/138939 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138939] Re: [gutsy] acroread fails to startup
*** 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 startup https://bugs.launchpad.net/bugs/138939 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Blank screen on tribe4 boot
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 happens when booting with the safe vga option. This means I can't install kubuntu :-( ** Affects: Ubuntu Importance: Undecided Status: New -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Re: Blank screen on tribe4 boot
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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139186] kde4 beta2 kmail ( and others ) fail
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/lib/kde4/bin/:$PATH $ export KDEHOME=~/.kde4 $ kmail kmail: symbol lookup error: /usr/lib/kde4/lib/libkdepim.so.4: undefined symbol: _ZTI18KStaticDeleterBase Is this possibly due to the fact that we don't yet have all of the 3.93 packages ( at least for 64-bit ) ? Perhaps kmail was compiled against older libraries ? Is this a case of waiting ? ** Affects: kde4pim (Ubuntu) Importance: Undecided Status: New -- kde4 beta2 kmail ( and others ) fail https://bugs.launchpad.net/bugs/139186 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Re: Blank screen on tribe4 boot
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Re: Blank screen on tribe4 boot
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: Linux Ubuntu Current Operating System: Linux ubuntu 2.6.22-10-generic #1 SMP Wed Aug 22 07:42:05 GMT 2007 x86_64 Build Date: 26 July 2007 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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.0.log", Time: Sat Aug 25 18:32:10 2007 (==) Using config file: "/etc/X11/xorg.conf" (II) Module already built-in Backtrace: 0: X(xf86SigHandler+0x6d) [0x4858ad] 1: /lib/libc.so.6 [0x2b6a9870e760] 2: /lib/libc.so.6 [0x2b6a9874ee49] 3: /lib/libc.so.6(__libc_malloc+0x93) [0x2b6a98750d73] 4: X(XNFalloc+0x18) [0x571258] 5: X(xf86CVTMode+0x41a) [0x4833aa] 6: /usr/lib/xorg/modules/drivers//vesa_drv.so [0x2b6a9a2460ba] 7: X(xf86ValidateModes+0x818) [0x495be8] 8: /usr/lib/xorg/modules/drivers//vesa_drv.so [0x2b6a9a2475c1] 9: X(InitOutput+0x9bd) [0x46867d] 10: X(main+0x275) [0x439cc5] 11: /lib/libc.so.6(__libc_start_main+0xf4) [0x2b6a986fab44] 12: X(FontFileCompleteXLFD+0x231) [0x4391a9] Fatal server error: Caught signal 11. Server aborting Note that this notebook comes with ATI radeon X1400 -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Re: Blank screen on tribe4 boot
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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133710] Re: Blank screen on tribe4 boot
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" http://launchpadlibrarian.net/8983279/xorg.conf.new -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135881] /bin/arch missing
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 135881] Re: /bin/arch missing
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 to you, > since you could ask as wishlist item that the package maintainer enable > the necessary arguments to enable the inclusion of this particular > binary. > > Util-linux-ng 2.13 Release Notes > > > Release highlights: > -- > arch(1) is deprecated in favor of "uname -m" or arch(1) from coreutils (>= > 6.9+). The util-linux-ng package doesn't build arch by default, you have to > use the option --enable-arch. > > ** Changed in: util-linux (Ubuntu) > Assignee: (unassigned) => Basilio Kublik >Status: New => Incomplete > Many scripts I have rely on /bin/arch - so I see this as a regression. Also, we don't yet have coreutils >=6.9 I can obviously write a /bin/arch script which calls uname -m, but I would suggest that we need to ship /bin/arch in util-linux until its shipped in coreutils -- /bin/arch missing https://bugs.launchpad.net/bugs/135881 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 136330] kterm - unknown terminal type
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 dependency of the konsole package. ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- kterm - unknown terminal type https://bugs.launchpad.net/bugs/136330 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 136330] Re: kterm - unknown terminal type
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 there is a bug here somewhere. Also, I can't spot the dependency you mention from http://packages.ubuntu.com/gutsy/x11/x11-common -- Peter Lord -- Please bottom post, for examples, please see http://mailformat.dan.info/quoting/bottom-posting.html and http://www.kassj.com/netiquette/netiquette.html#5 -- kterm - unknown terminal type https://bugs.launchpad.net/bugs/136330 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133362] Re: Gutsy x86-64 libc/gcc COMPLETELY BREAK valgrind
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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141168] /bin/kill not compatible with redhat/opensuse
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 process groups and the "--" option. For compatibility between distributions, can we have /bin/kill made available from coreutils ? ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- /bin/kill not compatible with redhat/opensuse https://bugs.launchpad.net/bugs/141168 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
