Re: [Bug 98955] Re: logd not running
On Saturday 14 March 2009, Charles Atkinson wrote: > I expected this change to cause some breakage; perhaps bootlogd depended > on something set by the earlier boot scripts; why would the package > designers not start it right at the beginning of the boot process so it > could capture all the boot messages? It may work or not depending on the system. The program uses pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel and have static pty* devices in your root filesystem, then yes, it should be possible to run bootlogd right from the beginning (perhaps even from the initial ramdisk). If not, you have to wait until /dev/pts is mounted by S11mountdevsubfs.sh. Best regards, Sergei -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
On Monday 27 April 2009, Charles Atkinson wrote: > In bootlogd.c, there is a while loop starting at line 585 and ending at > line 664. Each iteration it reads from the intercepted console output, > writes what it gets to the console and either buffers it or writes it to > logfile. What is the access() function on line 643? Lines 648 and 651 > try to open logfile in append mode, creating it if it does not exist. > As I understand it this should fail until there is a writeable /var/log > directory. If that is correct then it should work ... ? > I think it should work as you expect (but I never tried this kind of configuration). Are you sure that it is non-writable /var that breaks it? For example, can you mount root (with /var) read-write from the very beginning and see if this works? Keep in mind that one of my patches changed the name of the log file, it is /var/log/boot, not /var/log/bootmsg. Make sure this file exists or call bootlogd with the -c option. What is the status of bootlogd at the end of the boot sequence? Is it alive? If yes, can you check what it is doing? What files it has opened (see /proc/*/fd)? Does it work if started later? If yes, I suggest you bisect it and find the exact point after which it starts working. It might be mounting of /dev, for example. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 48146] Re: Poor font rendering in kpdf
> Is this also the cause of the poor fonts I get in Okular with my tex- > generated documents? If not I will start another bug thread. I did not test the patch with okular, I'm still using KDE3. > If it is, I wonder what file I should apply the patch to. I don't have > the SplashFTFont.cc file. I'm using Ubuntu and Gnome. It's in another package named poppler (it is a library that kpdf and okular use). -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 48146] Re: Poor font rendering in kpdf
I observe this bug too, both in kpdf (hardy) and okular (intrepid). Rendering is especially bad for Cyrillic fonts in pdfs generated by TeX (I guess this is because these fonts are bitmapped) but the problem is visible with latin fonts too. This bug annoyed me for a long time and I spent some time investigating it (with KDE3 on hardy) Rendering is good in Opensuse 10.3 and in Fedora 8. I narrowed the difference down to the file /usr/lib/kde3/libkpdfpart.so. Copying this file from Fedora to Ubuntu fixes the problem. I thought that the difference is due to compile-time options or patches but this is not the case. I compiled kdegraphics-3.5.10 (the upstream source with no patches) via 'configure && make' on the two systems. On Fedora, this compilation produced a good binary. On Ubuntu, it produced a bad binary. (The binaries were tested by copying the file libkpdfpart.so to the Ubuntu system and running kpdf, so it's not a matter of not having some library in the system). I am trying to investigate the issue futher. Does anyone know what can possibly cause this surprising effect? -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 48146] Re: Poor font rendering in kpdf
I fond the origin of the problem and a solution. The rendering propblem occurs when you have all of the following: 1. TrueType bytecode interpreter enabled in the freetype library. (This is a compile-time option which is off by default due to patent issues, Ubuntu turns it on while Fedora does not.) 2. Kpdf using anti-aliasing. (No idea where this is configured, maybe from the global KDE setting). 3. A pdf file with embedded bitmapped (or maybe any non-TrueType) fonts. This is typical for pdfs generated by TeX. When all of this happens, kpdf uses its own (or KDE's) anti-aliasing *and* freetype's autohinting. Each of the features is supposed to improve the view but their combination works poorly. A solution is to turn off the check for bytecode interpreter in kpdf. On Ubuntu, this piece of code actually lives in libpoppler which is a separate package. The attached patch to poppler fixes the problem for me. I don't know if it breaks something else. I checked evince and it does not seem to be affected. The same file is present in kpdf source. It should be patched there if kpdf is compiled without poppler. ** Attachment added: "disable freetype's autohinting when anti-aliasing" http://launchpadlibrarian.net/20554242/hinting.patch -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 98955] Re: logd not running
> Yes, I sure understand that you don't want to be a maintainer for it, that > would probably be quite a lot of work. For me the [ok] comes on it's own > separate: > Sun Jan 27 21:52:32 2008: * Starting system message bus dbus > Sun Jan 27 21:52:32 2008: [ OK ] > > Is this intentional? Otherwise this seems much nicer than before. Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll send the fixes there some day. The OK placement is yes, sort of intentional. They use a lot of terminal trickery to make output look better, and logging it correctly would require many changes to the code. I had to choose from a couple of simple rules, and the other choices led to worse results. After all, this "OK" is a separate message and its timing may be useful. You can make it appear on the same line by changing the source as follows. Go to bootlog.c line 361, there will be a part of switch like this: case '\n': case '\r": ... Change it to: case '\r': break; case '\n': ... (that is, interchange the two cases and insert "break;" between them). But then you will lose, among other things, the summary of a long fsck run (it will be truncated as a part of one extra long line). -- logd not running https://bugs.launchpad.net/bugs/98955 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 184675] Re: kate does not show newline inserted at the beginning
If my copy-pasting broke the patch, see the attached one here. It still works for me, now with kdelibs-3.5.8-0ubuntu3.2. I apply it before running anything from debian/rules. Here is what I do: apt-get source kdelibs patch -d kdelibs-3.5.8 -p1 < newline.patch cd kdelibs-3.5.8 debuild -us -uc -b sudo dpkg -i kdelibs4c2a_3.5.8-0ubuntu3.2_i386.deb Note that the affected fragment is in some obscure shared library which may be loaded via dlopen(). If you install the new version in /usr/local, the old one could still be used. It also makes sense to restart KDE to get rid of preloaded stuff (it works for me without restarting but generally KDE does not support live upgrading). ** Attachment added: "newline.patch" http://launchpadlibrarian.net/11600097/newline.patch -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 184675] Re: kate does not show newline inserted at the beginning
On Tuesday 29 January 2008, Cesare Tirabassi wrote: > My bad, I installed through upgrade and didn't notice that kdelibs4c2a > was held back. Yes, I can confirm that it works (using > 4:3.5.8-4ubuntu6), I'm subscribing u-m-s in case they care to include > this with the next update, but note that this was fixed for KDE 4 > (http://bugs.kde.org/show_bug.cgi?id=146300). Thanks. I hope KDE3 will be packaged and supported for a while (at this stage KDE4 is far from being usable for real work). -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 188950] [NEW] kmail composer uses wrong name for ibm866 charset
Public bug reported: Kmail composer understands the "ibm866" charset but uses "ibm 866" (with a space!) as its name in outgoing mail. This is incorrect, and other mail clients are confused by this space. I was hit by this when I received a mail with charset=ibm866, replied to it, and recipients could not read the reply because Kmail tried to use the same charset when replying but wrote 'charset="ibm 866"' in the header. To reproduce: In Kmail, go to Settings -> Composer -> Charset, try to add "ibm866" to the list. It adds "ibm 866" instead. Or, alternatively: Make sure the option "Keep original charset when replying ..." (in the same menu) is checked. Get a mail with charset="ibm866" (for example, create a simple ascii mail and edit "Content-Type:" field by hand). Reply to this mail and view the reply as plain text. It has Content-Type: text/plain; charset="ibm 866" The clients that cannot read this include (some versions of) SquirrelMail, MS Outlook Express, The Bat. I am using Gutsy, kmail version is 4:3.5.7enterprise20070926-0ubuntu2. Output of kmail --version is: Qt: 3.3.7 KDE: 3.5.8 KMail: 1.9.6 (enterprise 0.20070907.709405) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 155490] Re: [gutsy] Screensavers don't start automatically in Kubuntu
I have a similar behavior with just two of the screensavers: kswarm and kspace. They can be started by the "Test" button in the Configure Desctop -> Screen Saver menu, but not automatically. After the timeout, the mouse cursor disappears, the panel clock freezes, but otherwise nothing happens on the screen. This is a desktop machine running current Kubuntu Gutsy (32bit). I don't use screen locking. The behavior is the same with intel and nvidia drivers. Adding DPMS-dependent=false does not help. Other screensavers that I tried (kclock, klines and some others) do work. -- [gutsy] Screensavers don't start automatically in Kubuntu https://bugs.launchpad.net/bugs/155490 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 98955] Re: logd not running
I think that using the old bootlogd is the right fix. It seems that bootlogd and logd can and should coexist on the same system (of course, if they write to different logfiles). They just serve different purposes. Bootlogd is to save everything sent to /dev/console. It does not know who writes what. It can start and exit any time, and scripts do not notice any change (no SIGPIPESs, no failed IO, no nothing). This is the right tool for the problem "what did that scrolled-away messages say?". Logd is heavier. It uses redirected output of these scripts. This allows to log them separately, but at a price: it is not transparent (a process can detect that its stdout is a socket), and it is must run forever (or at least be extremely careful with those redirected file descriptors, as they could be even passed on to daemons). It can be useful for problems like "which of these scripts issued this message?" And normally the answer should be clear even from the mixed output, so I would consider logd as a tool for special cases. So my suggestion is to add bootlogd to the system and use logd (once it is working properly) as an additional tool when needed. Sorry if my analysis is incorrect, I'm not an expert. Maybe some developer can comment on this further. -- logd not running https://bugs.launchpad.net/bugs/98955 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 146306] Re: Kate can't insert newline character before first character in file
Please reopen this bug. I have it here on Gutsy with KDE 3.5.8. Package versions: kdelibs4c2a-3.5.8-0ubuntu3.1, kate-3.5.8-0ubuntu3.1. To reproduce: open a file which has more lines than fits in the screen. Go to line 1, column 1, and hit Enter. Then a new line is inserted but not shown. In fact, it needs not be the first line in the file, only the first line on the screen. Same behaviour in Kile, so the bug is in katepart. -- Kate can't insert newline character before first character in file https://bugs.launchpad.net/bugs/146306 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 184675] kate does not show newline inserted at the beginning
Public bug reported:
This was already reported as bug #146306 (which is closed as
unreproducible). I have this issue on Gutsy with current kdelibs
(kdelibs4c2a-3.5.8-0ubuntu3.1).
To reproduce: run Kate on a file with more lines than kate's window has
(this is essential), then hit Enter at the beginning of the file. Kate
inserts a line but does not display it (until you hit Uparrow or
something similar).
This also happens if it is not the beginning of the file but the
beginning of the visible part. You can hit Enter several times and still
see no effect (as if the key did not work). Same behavior with Kile
instead of Kate.
The bug was introduced at some point between KDE 3.5.5 and KDE 3.5.8.
The following patch fixes it.
--- kdelibs-3.5.8/kate/part/katesupercursor.cpp.orig2007-05-14
11:52:27.0 +0400
+++ kdelibs-3.5.8/kate/part/katesupercursor.cpp 2008-01-20 16:39:19.0
+0300
@@ -186,7 +186,7 @@
{
if (newLine)
{
-if (m_line > int(line) || (m_line == int(line) && m_col >= int(col)))
+if (m_line > int(line) || (m_line == int(line) && m_col > int(col)))
{
if(m_line == int(line))
m_col -= col;
** Affects: kdelibs (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
kate does not show newline inserted at the beginning
https://bugs.launchpad.net/bugs/184675
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 98955] Re: logd not running
> I think there is a good reason that they are not using bootlogd by > default. I think I read somewhere that bootlogd is quite buggy on some > systems, and it is hard to make it work correctly the way it is > designed. So the proper fix in the long run would be to redesign it > completely, as Scott is intending to do with logd in the future. I don't > remember where I read this however... Probably tekknokrat ran into one > of those problems. No, that error (cannot find console device 136:1) means that bootlogd was run from a terminal emulator (xterm or screen or mc or ... ). It must be run from a real console device. Passing console=/dev/console to the kernel is an error. I think the correct value is /dev/tty0 or /dev/tty1. And bootlogd will use something like this anyway. I have another problem with bootlogd. It gets confused by terminal control codes (those that make screen output prettier). I'll try to look at the source and see what can be done. -- logd not running https://bugs.launchpad.net/bugs/98955 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 177923] Re: some monospace fonts are not monospace
Sorry, I just discovered that email attachments do not work in launchpad. Including that screenshot now. ** Attachment added: "snapshot3.png" http://launchpadlibrarian.net/11569621/snapshot3.png -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 98955] Re: logd not running
To tekknokrat. You can try out the attached source package. This is bootlogd alone, separated from gutsy's sysvinit. I fixed logging of terminal codes and some other minor issues. It works for me here (Ubuntu stock kernel, no usplash, no mounting of /var). You can build and install it with the following commands: tar xzvf bootlogd_2.86.01.tar.gz # unpack the source cd bootlogd-2.86.01 debuild -us -uc -b # build the package cd .. sudo dpkg -i bootlogd_2.86.01_*.deb # install the package Please note that I am not an Ubuntu developer and the package is not official in any way. So it is a good measure to audit it before installing. In the long run, I agree that we should wait for a boot logging support in upstart. Doing such things properly may require cooperation with the rest of the init system. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I did attach it! Maybe launchpad does not allow this via email. Now I am trying to do this using the web interface. ** Attachment added: "bootlogd_2.86.01.tar.gz (unofficial package)" http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I am not willing to maintain it seriously, it is too system-dependent. Nevertheless, here is a new version. Changes are: - Improved logfile formatting. - The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in the future. Again, please do not install it blindly. You cannot be sure that I am not giving you a trojan. ** Attachment added: "bootlogd_2.86.02.tar.gz" http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 77395] Re: udev rules not created for all supported backends
In Kubuntu-7.10 (libsane-extras1.0.18.8) I have a similar problem
with Epson Stylus CX4900. It is supported by the epkowa backend
according to the manpage. It is recognized and works when an application
is run as root. But it does not work for normal user due to a permission
problem.
I fixed this by adding the following lines to /etc/udev/libsane-extras.rules:
# EPSON Stylus CX4900
SYSFS{idVendor}=="04b8", SYSFS{idProduct}=="082b", MODE="664", GROUP="scanner"
--
udev rules not created for all supported backends
https://bugs.launchpad.net/bugs/77395
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 177923] some monospace fonts are not monospace
Public bug reported: System: fresh kubuntu 7-10 (konsole 1.6.6, KDE 3.5.8), LANG=en_US.UTF-8. To reproduce: In konsole, run 'cat .kde/Autostart/.directory', then scroll back (preferably with shift-arrows) and watch the line "Name[km]=..." The letters are substituted by squares whose width is larger than 1 but smaller than 2 ordinary characters. They garble other lines when scrolled. There is a similar problem with the line 'Name[ta]=...' . The letters are rendered but the width is wrong, and it produces garbage when scrolled. On my system, the font in konsole is set to Monospace-Regular-15. Other fonts sizes have the same problem. Here are those lines (copy-pasted from konsole): Name[km]=ចាបផដើមសវយបរវតត Name[ta]=தானாகதுவககு ** Affects: ubuntu Importance: Undecided Status: New -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 177923] Re: some monospace fonts are not monospace
On Saturday 22 December 2007, Murat Güneş wrote: > Thanks for your report. Can you reproduce the problem in other > applications, or is it specific to Konsole? Posting a screenshot would > also help. See attachment. This is the result of 'cat .kde/Autostart/.directory' and scrolling up and down with shift-arrows. I've removed some Asian fonts since that, so there are more substituted characters than after a fresh install. But most of them work fine. Note the difference in width of squares for "km" and "ko" languages in the screenshot. Kate a also has a problem with these fonts though it shows up differently. First it sends a message to stderr: ASSERT: "width" in /build/buildd/kdelibs-3.5.8/./kate/part/katerenderer.cpp (798) repeated many times. Then it cannot place cursor correctly in those lines and messes up when I try to mouse-select a part of the line. Another effect that I just observed: these lines in konsole and kate change when I move another window over them (it seems that the characters change their horizontal coordinates and overlap). I am using "nvidia" driver at the moment but I've checked that the original problem is reproducible under "nv". -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 98955] Re: logd not running
> i installed Sergei's version and it works but it only captures 3 seconds > of my boot messages, how can i fix this? Is there a lot of text to capture? If so, it might overflow the internal 32K buffer. It is defined on line 52 in bootlogd.c. Try to increase it. Also, there is a stop-bootlogd script which stops bootlogd near the end of boot sequence. Check when this script is run. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i cant make the buffer big enough to log it all. my boot process takes > 23 seconds and the biggest buffer that i can get to work is 975kb > (999,999 bytes) which will only log 18 seconds. This is a strange constant. The 32-bit integer overflows near 2Gb. What is wrong with larger values? Doesn't the program compile, or doesn't it start? Do you measure the 18 seconds by the wall clock or by the timestamps in the log file? I'm not a great expert in bootlogd, but I thought that the internal buffer is used until /var is writeable, then it writes directly to the file. So if a buffer in bootlogd overflows *after* /var is made writeable, then this is a bug in bootlogd. Otherwise there is no way other than enlarging the buffer - it has to remember the messages somewhere until the disk is ready. > also is there a way to > log the shutdown messages? This is hard. You cannot save anything after the filesystems are unmounted. I've heard of someone who used a video camera to record screen messages. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> Can you give me layman steps of how to install your package? This is a Debian source package. It is meant to be installed using dpkg-related tools, not with "make; make install". A recipe was there in the post where I announced the package. Here it is again: # unpack the source tar xzvf bootlogd_2.86.02.tar.gz # build the package cd bootlogd-2.86.02 debuild -us -uc -b cd .. # install the package sudo dpkg -i bootlogd_2.86.02_*.deb As for the compilation warning, it looks harmless. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 29 October 2008, Richard Birnie wrote:
> I still haven't managed to reproduce this. KDE3.5.10 has now been
> released. Does this problem still occur for you?
>
Yes, it still inserts a space when I add "ibm866" in
Settings->Composer->Charset,
and it this space can occur in the outgoing mail.
I am pretty sure that this bug is in QT. I have libqt3-mt version
3.3.8-b-0ubuntu3
installed at the moment, you may have some better version.
Back then, I grepped the sources for "ibm 866" with a space and found an
occurence
in some table within QT sources but nowhere in KDE. I even made a patch (see
below)
and I think it worked then. Then I forgot about it, and then some apt-get
upgrade
killed it (sigh)... Sorry for not reporting this fact until now.
--- qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp.-space
+++ qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp
@@ -1971,7 +1971,7 @@
0x0E48, 0x0E49, 0x0E4A, 0x0E4B, 0x0E4C, 0x0E4D, 0x0E4E, 0x0E4F,
0x0E50, 0x0E51, 0x0E52, 0x0E53, 0x0E54, 0x0E55, 0x0E56, 0x0E57,
0x0E58, 0x0E59, 0x0E5A, 0x0E5B, 0xFFFD, 0xFFFD, 0xFFFD, 0xFFFD} },
-{ "IBM 866", "IBM 866", 2086,
+{ "IBM866", "IBM 866", 2086,
{ 0x0410, 0x0411, 0x0412, 0x0413, 0x0414, 0x0415, 0x0416, 0x0417,
0x0418, 0x0419, 0x041A, 0x041B, 0x041C, 0x041D, 0x041E, 0x041F,
0x0420, 0x0421, 0x0422, 0x0423, 0x0424, 0x0425, 0x0426, 0x0427,
--
kmail composer uses wrong name for ibm866 charset
https://bugs.launchpad.net/bugs/188950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 24 September 2008, Richard Birnie wrote: > Do you still observe this bug in more recent versions of kmail? Yes I still observe it in hardy. > I just tried to reproduce this in both hardy and intrepid both with kde4 and kmail 1.10.1 For some reason, the version I am using is older: ~$ kmail --version Qt: 3.3.8b KDE: 3.5.9 KMail: 1.9.9 The kmail package version (as shown by aptitude) is 4:3.5.9-0ubuntu3. However aptitude does not show any upgradable packages. Do I miss some repository to upgrade from? -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i installed Sergei's version and it works but it only captures 3 seconds > of my boot messages, how can i fix this? Is there a lot of text to capture? If so, it might overflow the internal 32K buffer. It is defined on line 52 in bootlogd.c. Try to increase it. Also, there is a stop-bootlogd script which stops bootlogd near the end of boot sequence. Check when this script is run. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i cant make the buffer big enough to log it all. my boot process takes > 23 seconds and the biggest buffer that i can get to work is 975kb > (999,999 bytes) which will only log 18 seconds. This is a strange constant. The 32-bit integer overflows near 2Gb. What is wrong with larger values? Doesn't the program compile, or doesn't it start? Do you measure the 18 seconds by the wall clock or by the timestamps in the log file? I'm not a great expert in bootlogd, but I thought that the internal buffer is used until /var is writeable, then it writes directly to the file. So if a buffer in bootlogd overflows *after* /var is made writeable, then this is a bug in bootlogd. Otherwise there is no way other than enlarging the buffer - it has to remember the messages somewhere until the disk is ready. > also is there a way to > log the shutdown messages? This is hard. You cannot save anything after the filesystems are unmounted. I've heard of someone who used a video camera to record screen messages. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> Can you give me layman steps of how to install your package? This is a Debian source package. It is meant to be installed using dpkg-related tools, not with "make; make install". A recipe was there in the post where I announced the package. Here it is again: # unpack the source tar xzvf bootlogd_2.86.02.tar.gz # build the package cd bootlogd-2.86.02 debuild -us -uc -b cd .. # install the package sudo dpkg -i bootlogd_2.86.02_*.deb As for the compilation warning, it looks harmless. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 24 September 2008, Richard Birnie wrote: > Do you still observe this bug in more recent versions of kmail? Yes I still observe it in hardy. > I just tried to reproduce this in both hardy and intrepid both with kde4 and kmail 1.10.1 For some reason, the version I am using is older: ~$ kmail --version Qt: 3.3.8b KDE: 3.5.9 KMail: 1.9.9 The kmail package version (as shown by aptitude) is 4:3.5.9-0ubuntu3. However aptitude does not show any upgradable packages. Do I miss some repository to upgrade from? -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 29 October 2008, Richard Birnie wrote:
> I still haven't managed to reproduce this. KDE3.5.10 has now been
> released. Does this problem still occur for you?
>
Yes, it still inserts a space when I add "ibm866" in
Settings->Composer->Charset,
and it this space can occur in the outgoing mail.
I am pretty sure that this bug is in QT. I have libqt3-mt version
3.3.8-b-0ubuntu3
installed at the moment, you may have some better version.
Back then, I grepped the sources for "ibm 866" with a space and found an
occurence
in some table within QT sources but nowhere in KDE. I even made a patch (see
below)
and I think it worked then. Then I forgot about it, and then some apt-get
upgrade
killed it (sigh)... Sorry for not reporting this fact until now.
--- qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp.-space
+++ qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp
@@ -1971,7 +1971,7 @@
0x0E48, 0x0E49, 0x0E4A, 0x0E4B, 0x0E4C, 0x0E4D, 0x0E4E, 0x0E4F,
0x0E50, 0x0E51, 0x0E52, 0x0E53, 0x0E54, 0x0E55, 0x0E56, 0x0E57,
0x0E58, 0x0E59, 0x0E5A, 0x0E5B, 0xFFFD, 0xFFFD, 0xFFFD, 0xFFFD} },
-{ "IBM 866", "IBM 866", 2086,
+{ "IBM866", "IBM 866", 2086,
{ 0x0410, 0x0411, 0x0412, 0x0413, 0x0414, 0x0415, 0x0416, 0x0417,
0x0418, 0x0419, 0x041A, 0x041B, 0x041C, 0x041D, 0x041E, 0x041F,
0x0420, 0x0421, 0x0422, 0x0423, 0x0424, 0x0425, 0x0426, 0x0427,
--
kmail composer uses wrong name for ibm866 charset
https://bugs.launchpad.net/bugs/188950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177923] some monospace fonts are not monospace
Public bug reported: System: fresh kubuntu 7-10 (konsole 1.6.6, KDE 3.5.8), LANG=en_US.UTF-8. To reproduce: In konsole, run 'cat .kde/Autostart/.directory', then scroll back (preferably with shift-arrows) and watch the line "Name[km]=..." The letters are substituted by squares whose width is larger than 1 but smaller than 2 ordinary characters. They garble other lines when scrolled. There is a similar problem with the line 'Name[ta]=...' . The letters are rendered but the width is wrong, and it produces garbage when scrolled. On my system, the font in konsole is set to Monospace-Regular-15. Other fonts sizes have the same problem. Here are those lines (copy-pasted from konsole): Name[km]=ចាបផដើមសវយបរវតត Name[ta]=தானாகதுவககு ** Affects: ubuntu Importance: Undecided Status: New -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 177923] Re: some monospace fonts are not monospace
On Saturday 22 December 2007, Murat Güneş wrote: > Thanks for your report. Can you reproduce the problem in other > applications, or is it specific to Konsole? Posting a screenshot would > also help. See attachment. This is the result of 'cat .kde/Autostart/.directory' and scrolling up and down with shift-arrows. I've removed some Asian fonts since that, so there are more substituted characters than after a fresh install. But most of them work fine. Note the difference in width of squares for "km" and "ko" languages in the screenshot. Kate a also has a problem with these fonts though it shows up differently. First it sends a message to stderr: ASSERT: "width" in /build/buildd/kdelibs-3.5.8/./kate/part/katerenderer.cpp (798) repeated many times. Then it cannot place cursor correctly in those lines and messes up when I try to mouse-select a part of the line. Another effect that I just observed: these lines in konsole and kate change when I move another window over them (it seems that the characters change their horizontal coordinates and overlap). I am using "nvidia" driver at the moment but I've checked that the original problem is reproducible under "nv". -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 77395] Re: udev rules not created for all supported backends
In Kubuntu-7.10 (libsane-extras1.0.18.8) I have a similar problem
with Epson Stylus CX4900. It is supported by the epkowa backend
according to the manpage. It is recognized and works when an application
is run as root. But it does not work for normal user due to a permission
problem.
I fixed this by adding the following lines to /etc/udev/libsane-extras.rules:
# EPSON Stylus CX4900
SYSFS{idVendor}=="04b8", SYSFS{idProduct}=="082b", MODE="664", GROUP="scanner"
--
udev rules not created for all supported backends
https://bugs.launchpad.net/bugs/77395
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 48146] Re: Poor font rendering in kpdf
I observe this bug too, both in kpdf (hardy) and okular (intrepid). Rendering is especially bad for Cyrillic fonts in pdfs generated by TeX (I guess this is because these fonts are bitmapped) but the problem is visible with latin fonts too. This bug annoyed me for a long time and I spent some time investigating it (with KDE3 on hardy) Rendering is good in Opensuse 10.3 and in Fedora 8. I narrowed the difference down to the file /usr/lib/kde3/libkpdfpart.so. Copying this file from Fedora to Ubuntu fixes the problem. I thought that the difference is due to compile-time options or patches but this is not the case. I compiled kdegraphics-3.5.10 (the upstream source with no patches) via 'configure && make' on the two systems. On Fedora, this compilation produced a good binary. On Ubuntu, it produced a bad binary. (The binaries were tested by copying the file libkpdfpart.so to the Ubuntu system and running kpdf, so it's not a matter of not having some library in the system). I am trying to investigate the issue futher. Does anyone know what can possibly cause this surprising effect? -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 177923] Re: some monospace fonts are not monospace
Sorry, I just discovered that email attachments do not work in launchpad. Including that screenshot now. ** Attachment added: "snapshot3.png" http://launchpadlibrarian.net/11569621/snapshot3.png -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 98955] Re: logd not running
To tekknokrat. You can try out the attached source package. This is bootlogd alone, separated from gutsy's sysvinit. I fixed logging of terminal codes and some other minor issues. It works for me here (Ubuntu stock kernel, no usplash, no mounting of /var). You can build and install it with the following commands: tar xzvf bootlogd_2.86.01.tar.gz # unpack the source cd bootlogd-2.86.01 debuild -us -uc -b # build the package cd .. sudo dpkg -i bootlogd_2.86.01_*.deb # install the package Please note that I am not an Ubuntu developer and the package is not official in any way. So it is a good measure to audit it before installing. In the long run, I agree that we should wait for a boot logging support in upstart. Doing such things properly may require cooperation with the rest of the init system. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I did attach it! Maybe launchpad does not allow this via email. Now I am trying to do this using the web interface. ** Attachment added: "bootlogd_2.86.01.tar.gz (unofficial package)" http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I am not willing to maintain it seriously, it is too system-dependent. Nevertheless, here is a new version. Changes are: - Improved logfile formatting. - The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in the future. Again, please do not install it blindly. You cannot be sure that I am not giving you a trojan. ** Attachment added: "bootlogd_2.86.02.tar.gz" http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
> Yes, I sure understand that you don't want to be a maintainer for it, that > would probably be quite a lot of work. For me the [ok] comes on it's own > separate: > Sun Jan 27 21:52:32 2008: * Starting system message bus dbus > Sun Jan 27 21:52:32 2008: [ OK ] > > Is this intentional? Otherwise this seems much nicer than before. Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll send the fixes there some day. The OK placement is yes, sort of intentional. They use a lot of terminal trickery to make output look better, and logging it correctly would require many changes to the code. I had to choose from a couple of simple rules, and the other choices led to worse results. After all, this "OK" is a separate message and its timing may be useful. You can make it appear on the same line by changing the source as follows. Go to bootlog.c line 361, there will be a part of switch like this: case '\n': case '\r": ... Change it to: case '\r': break; case '\n': ... (that is, interchange the two cases and insert "break;" between them). But then you will lose, among other things, the summary of a long fsck run (it will be truncated as a part of one extra long line). -- logd not running https://bugs.launchpad.net/bugs/98955 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 184675] Re: kate does not show newline inserted at the beginning
If my copy-pasting broke the patch, see the attached one here. It still works for me, now with kdelibs-3.5.8-0ubuntu3.2. I apply it before running anything from debian/rules. Here is what I do: apt-get source kdelibs patch -d kdelibs-3.5.8 -p1 < newline.patch cd kdelibs-3.5.8 debuild -us -uc -b sudo dpkg -i kdelibs4c2a_3.5.8-0ubuntu3.2_i386.deb Note that the affected fragment is in some obscure shared library which may be loaded via dlopen(). If you install the new version in /usr/local, the old one could still be used. It also makes sense to restart KDE to get rid of preloaded stuff (it works for me without restarting but generally KDE does not support live upgrading). ** Attachment added: "newline.patch" http://launchpadlibrarian.net/11600097/newline.patch -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 184675] Re: kate does not show newline inserted at the beginning
On Tuesday 29 January 2008, Cesare Tirabassi wrote: > My bad, I installed through upgrade and didn't notice that kdelibs4c2a > was held back. Yes, I can confirm that it works (using > 4:3.5.8-4ubuntu6), I'm subscribing u-m-s in case they care to include > this with the next update, but note that this was fixed for KDE 4 > (http://bugs.kde.org/show_bug.cgi?id=146300). Thanks. I hope KDE3 will be packaged and supported for a while (at this stage KDE4 is far from being usable for real work). -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 48146] Re: Poor font rendering in kpdf
I fond the origin of the problem and a solution. The rendering propblem occurs when you have all of the following: 1. TrueType bytecode interpreter enabled in the freetype library. (This is a compile-time option which is off by default due to patent issues, Ubuntu turns it on while Fedora does not.) 2. Kpdf using anti-aliasing. (No idea where this is configured, maybe from the global KDE setting). 3. A pdf file with embedded bitmapped (or maybe any non-TrueType) fonts. This is typical for pdfs generated by TeX. When all of this happens, kpdf uses its own (or KDE's) anti-aliasing *and* freetype's autohinting. Each of the features is supposed to improve the view but their combination works poorly. A solution is to turn off the check for bytecode interpreter in kpdf. On Ubuntu, this piece of code actually lives in libpoppler which is a separate package. The attached patch to poppler fixes the problem for me. I don't know if it breaks something else. I checked evince and it does not seem to be affected. The same file is present in kpdf source. It should be patched there if kpdf is compiled without poppler. ** Attachment added: "disable freetype's autohinting when anti-aliasing" http://launchpadlibrarian.net/20554242/hinting.patch -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 98955] Re: logd not running
On Saturday 14 March 2009, Charles Atkinson wrote: > I expected this change to cause some breakage; perhaps bootlogd depended > on something set by the earlier boot scripts; why would the package > designers not start it right at the beginning of the boot process so it > could capture all the boot messages? It may work or not depending on the system. The program uses pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel and have static pty* devices in your root filesystem, then yes, it should be possible to run bootlogd right from the beginning (perhaps even from the initial ramdisk). If not, you have to wait until /dev/pts is mounted by S11mountdevsubfs.sh. Best regards, Sergei -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
On Monday 27 April 2009, Charles Atkinson wrote: > In bootlogd.c, there is a while loop starting at line 585 and ending at > line 664. Each iteration it reads from the intercepted console output, > writes what it gets to the console and either buffers it or writes it to > logfile. What is the access() function on line 643? Lines 648 and 651 > try to open logfile in append mode, creating it if it does not exist. > As I understand it this should fail until there is a writeable /var/log > directory. If that is correct then it should work ... ? > I think it should work as you expect (but I never tried this kind of configuration). Are you sure that it is non-writable /var that breaks it? For example, can you mount root (with /var) read-write from the very beginning and see if this works? Keep in mind that one of my patches changed the name of the log file, it is /var/log/boot, not /var/log/bootmsg. Make sure this file exists or call bootlogd with the -c option. What is the status of bootlogd at the end of the boot sequence? Is it alive? If yes, can you check what it is doing? What files it has opened (see /proc/*/fd)? Does it work if started later? If yes, I suggest you bisect it and find the exact point after which it starts working. It might be mounting of /dev, for example. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188950] [NEW] kmail composer uses wrong name for ibm866 charset
Public bug reported: Kmail composer understands the "ibm866" charset but uses "ibm 866" (with a space!) as its name in outgoing mail. This is incorrect, and other mail clients are confused by this space. I was hit by this when I received a mail with charset=ibm866, replied to it, and recipients could not read the reply because Kmail tried to use the same charset when replying but wrote 'charset="ibm 866"' in the header. To reproduce: In Kmail, go to Settings -> Composer -> Charset, try to add "ibm866" to the list. It adds "ibm 866" instead. Or, alternatively: Make sure the option "Keep original charset when replying ..." (in the same menu) is checked. Get a mail with charset="ibm866" (for example, create a simple ascii mail and edit "Content-Type:" field by hand). Reply to this mail and view the reply as plain text. It has Content-Type: text/plain; charset="ibm 866" The clients that cannot read this include (some versions of) SquirrelMail, MS Outlook Express, The Bat. I am using Gutsy, kmail version is 4:3.5.7enterprise20070926-0ubuntu2. Output of kmail --version is: Qt: 3.3.7 KDE: 3.5.8 KMail: 1.9.6 (enterprise 0.20070907.709405) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 155490] Re: [gutsy] Screensavers don't start automatically in Kubuntu
I have a similar behavior with just two of the screensavers: kswarm and kspace. They can be started by the "Test" button in the Configure Desctop -> Screen Saver menu, but not automatically. After the timeout, the mouse cursor disappears, the panel clock freezes, but otherwise nothing happens on the screen. This is a desktop machine running current Kubuntu Gutsy (32bit). I don't use screen locking. The behavior is the same with intel and nvidia drivers. Adding DPMS-dependent=false does not help. Other screensavers that I tried (kclock, klines and some others) do work. -- [gutsy] Screensavers don't start automatically in Kubuntu https://bugs.launchpad.net/bugs/155490 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 98955] Re: logd not running
I think that using the old bootlogd is the right fix. It seems that bootlogd and logd can and should coexist on the same system (of course, if they write to different logfiles). They just serve different purposes. Bootlogd is to save everything sent to /dev/console. It does not know who writes what. It can start and exit any time, and scripts do not notice any change (no SIGPIPESs, no failed IO, no nothing). This is the right tool for the problem "what did that scrolled-away messages say?". Logd is heavier. It uses redirected output of these scripts. This allows to log them separately, but at a price: it is not transparent (a process can detect that its stdout is a socket), and it is must run forever (or at least be extremely careful with those redirected file descriptors, as they could be even passed on to daemons). It can be useful for problems like "which of these scripts issued this message?" And normally the answer should be clear even from the mixed output, so I would consider logd as a tool for special cases. So my suggestion is to add bootlogd to the system and use logd (once it is working properly) as an additional tool when needed. Sorry if my analysis is incorrect, I'm not an expert. Maybe some developer can comment on this further. -- logd not running https://bugs.launchpad.net/bugs/98955 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 146306] Re: Kate can't insert newline character before first character in file
Please reopen this bug. I have it here on Gutsy with KDE 3.5.8. Package versions: kdelibs4c2a-3.5.8-0ubuntu3.1, kate-3.5.8-0ubuntu3.1. To reproduce: open a file which has more lines than fits in the screen. Go to line 1, column 1, and hit Enter. Then a new line is inserted but not shown. In fact, it needs not be the first line in the file, only the first line on the screen. Same behaviour in Kile, so the bug is in katepart. -- Kate can't insert newline character before first character in file https://bugs.launchpad.net/bugs/146306 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 184675] kate does not show newline inserted at the beginning
Public bug reported:
This was already reported as bug #146306 (which is closed as
unreproducible). I have this issue on Gutsy with current kdelibs
(kdelibs4c2a-3.5.8-0ubuntu3.1).
To reproduce: run Kate on a file with more lines than kate's window has
(this is essential), then hit Enter at the beginning of the file. Kate
inserts a line but does not display it (until you hit Uparrow or
something similar).
This also happens if it is not the beginning of the file but the
beginning of the visible part. You can hit Enter several times and still
see no effect (as if the key did not work). Same behavior with Kile
instead of Kate.
The bug was introduced at some point between KDE 3.5.5 and KDE 3.5.8.
The following patch fixes it.
--- kdelibs-3.5.8/kate/part/katesupercursor.cpp.orig2007-05-14
11:52:27.0 +0400
+++ kdelibs-3.5.8/kate/part/katesupercursor.cpp 2008-01-20 16:39:19.0
+0300
@@ -186,7 +186,7 @@
{
if (newLine)
{
-if (m_line > int(line) || (m_line == int(line) && m_col >= int(col)))
+if (m_line > int(line) || (m_line == int(line) && m_col > int(col)))
{
if(m_line == int(line))
m_col -= col;
** Affects: kdelibs (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
kate does not show newline inserted at the beginning
https://bugs.launchpad.net/bugs/184675
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 98955] Re: logd not running
> I think there is a good reason that they are not using bootlogd by > default. I think I read somewhere that bootlogd is quite buggy on some > systems, and it is hard to make it work correctly the way it is > designed. So the proper fix in the long run would be to redesign it > completely, as Scott is intending to do with logd in the future. I don't > remember where I read this however... Probably tekknokrat ran into one > of those problems. No, that error (cannot find console device 136:1) means that bootlogd was run from a terminal emulator (xterm or screen or mc or ... ). It must be run from a real console device. Passing console=/dev/console to the kernel is an error. I think the correct value is /dev/tty0 or /dev/tty1. And bootlogd will use something like this anyway. I have another problem with bootlogd. It gets confused by terminal control codes (those that make screen output prettier). I'll try to look at the source and see what can be done. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
On Saturday 14 March 2009, Charles Atkinson wrote: > I expected this change to cause some breakage; perhaps bootlogd depended > on something set by the earlier boot scripts; why would the package > designers not start it right at the beginning of the boot process so it > could capture all the boot messages? It may work or not depending on the system. The program uses pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel and have static pty* devices in your root filesystem, then yes, it should be possible to run bootlogd right from the beginning (perhaps even from the initial ramdisk). If not, you have to wait until /dev/pts is mounted by S11mountdevsubfs.sh. Best regards, Sergei -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
On Monday 27 April 2009, Charles Atkinson wrote: > In bootlogd.c, there is a while loop starting at line 585 and ending at > line 664. Each iteration it reads from the intercepted console output, > writes what it gets to the console and either buffers it or writes it to > logfile. What is the access() function on line 643? Lines 648 and 651 > try to open logfile in append mode, creating it if it does not exist. > As I understand it this should fail until there is a writeable /var/log > directory. If that is correct then it should work ... ? > I think it should work as you expect (but I never tried this kind of configuration). Are you sure that it is non-writable /var that breaks it? For example, can you mount root (with /var) read-write from the very beginning and see if this works? Keep in mind that one of my patches changed the name of the log file, it is /var/log/boot, not /var/log/bootmsg. Make sure this file exists or call bootlogd with the -c option. What is the status of bootlogd at the end of the boot sequence? Is it alive? If yes, can you check what it is doing? What files it has opened (see /proc/*/fd)? Does it work if started later? If yes, I suggest you bisect it and find the exact point after which it starts working. It might be mounting of /dev, for example. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 48146] Re: Poor font rendering in kpdf
> Is this also the cause of the poor fonts I get in Okular with my tex- > generated documents? If not I will start another bug thread. I did not test the patch with okular, I'm still using KDE3. > If it is, I wonder what file I should apply the patch to. I don't have > the SplashFTFont.cc file. I'm using Ubuntu and Gnome. It's in another package named poppler (it is a library that kpdf and okular use). -- Poor font rendering in kpdf https://bugs.launchpad.net/bugs/48146 You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i installed Sergei's version and it works but it only captures 3 seconds > of my boot messages, how can i fix this? Is there a lot of text to capture? If so, it might overflow the internal 32K buffer. It is defined on line 52 in bootlogd.c. Try to increase it. Also, there is a stop-bootlogd script which stops bootlogd near the end of boot sequence. Check when this script is run. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i cant make the buffer big enough to log it all. my boot process takes > 23 seconds and the biggest buffer that i can get to work is 975kb > (999,999 bytes) which will only log 18 seconds. This is a strange constant. The 32-bit integer overflows near 2Gb. What is wrong with larger values? Doesn't the program compile, or doesn't it start? Do you measure the 18 seconds by the wall clock or by the timestamps in the log file? I'm not a great expert in bootlogd, but I thought that the internal buffer is used until /var is writeable, then it writes directly to the file. So if a buffer in bootlogd overflows *after* /var is made writeable, then this is a bug in bootlogd. Otherwise there is no way other than enlarging the buffer - it has to remember the messages somewhere until the disk is ready. > also is there a way to > log the shutdown messages? This is hard. You cannot save anything after the filesystems are unmounted. I've heard of someone who used a video camera to record screen messages. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 184675] Re: kate does not show newline inserted at the beginning
On Tuesday 29 January 2008, Cesare Tirabassi wrote: > My bad, I installed through upgrade and didn't notice that kdelibs4c2a > was held back. Yes, I can confirm that it works (using > 4:3.5.8-4ubuntu6), I'm subscribing u-m-s in case they care to include > this with the next update, but note that this was fixed for KDE 4 > (http://bugs.kde.org/show_bug.cgi?id=146300). Thanks. I hope KDE3 will be packaged and supported for a while (at this stage KDE4 is far from being usable for real work). -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 188950] [NEW] kmail composer uses wrong name for ibm866 charset
Public bug reported: Kmail composer understands the "ibm866" charset but uses "ibm 866" (with a space!) as its name in outgoing mail. This is incorrect, and other mail clients are confused by this space. I was hit by this when I received a mail with charset=ibm866, replied to it, and recipients could not read the reply because Kmail tried to use the same charset when replying but wrote 'charset="ibm 866"' in the header. To reproduce: In Kmail, go to Settings -> Composer -> Charset, try to add "ibm866" to the list. It adds "ibm 866" instead. Or, alternatively: Make sure the option "Keep original charset when replying ..." (in the same menu) is checked. Get a mail with charset="ibm866" (for example, create a simple ascii mail and edit "Content-Type:" field by hand). Reply to this mail and view the reply as plain text. It has Content-Type: text/plain; charset="ibm 866" The clients that cannot read this include (some versions of) SquirrelMail, MS Outlook Express, The Bat. I am using Gutsy, kmail version is 4:3.5.7enterprise20070926-0ubuntu2. Output of kmail --version is: Qt: 3.3.7 KDE: 3.5.8 KMail: 1.9.6 (enterprise 0.20070907.709405) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 155490] Re: [gutsy] Screensavers don't start automatically in Kubuntu
I have a similar behavior with just two of the screensavers: kswarm and kspace. They can be started by the "Test" button in the Configure Desctop -> Screen Saver menu, but not automatically. After the timeout, the mouse cursor disappears, the panel clock freezes, but otherwise nothing happens on the screen. This is a desktop machine running current Kubuntu Gutsy (32bit). I don't use screen locking. The behavior is the same with intel and nvidia drivers. Adding DPMS-dependent=false does not help. Other screensavers that I tried (kclock, klines and some others) do work. -- [gutsy] Screensavers don't start automatically in Kubuntu https://bugs.launchpad.net/bugs/155490 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 98955] Re: logd not running
I think that using the old bootlogd is the right fix. It seems that bootlogd and logd can and should coexist on the same system (of course, if they write to different logfiles). They just serve different purposes. Bootlogd is to save everything sent to /dev/console. It does not know who writes what. It can start and exit any time, and scripts do not notice any change (no SIGPIPESs, no failed IO, no nothing). This is the right tool for the problem "what did that scrolled-away messages say?". Logd is heavier. It uses redirected output of these scripts. This allows to log them separately, but at a price: it is not transparent (a process can detect that its stdout is a socket), and it is must run forever (or at least be extremely careful with those redirected file descriptors, as they could be even passed on to daemons). It can be useful for problems like "which of these scripts issued this message?" And normally the answer should be clear even from the mixed output, so I would consider logd as a tool for special cases. So my suggestion is to add bootlogd to the system and use logd (once it is working properly) as an additional tool when needed. Sorry if my analysis is incorrect, I'm not an expert. Maybe some developer can comment on this further. -- logd not running https://bugs.launchpad.net/bugs/98955 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 146306] Re: Kate can't insert newline character before first character in file
Please reopen this bug. I have it here on Gutsy with KDE 3.5.8. Package versions: kdelibs4c2a-3.5.8-0ubuntu3.1, kate-3.5.8-0ubuntu3.1. To reproduce: open a file which has more lines than fits in the screen. Go to line 1, column 1, and hit Enter. Then a new line is inserted but not shown. In fact, it needs not be the first line in the file, only the first line on the screen. Same behaviour in Kile, so the bug is in katepart. -- Kate can't insert newline character before first character in file https://bugs.launchpad.net/bugs/146306 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 184675] kate does not show newline inserted at the beginning
Public bug reported:
This was already reported as bug #146306 (which is closed as
unreproducible). I have this issue on Gutsy with current kdelibs
(kdelibs4c2a-3.5.8-0ubuntu3.1).
To reproduce: run Kate on a file with more lines than kate's window has
(this is essential), then hit Enter at the beginning of the file. Kate
inserts a line but does not display it (until you hit Uparrow or
something similar).
This also happens if it is not the beginning of the file but the
beginning of the visible part. You can hit Enter several times and still
see no effect (as if the key did not work). Same behavior with Kile
instead of Kate.
The bug was introduced at some point between KDE 3.5.5 and KDE 3.5.8.
The following patch fixes it.
--- kdelibs-3.5.8/kate/part/katesupercursor.cpp.orig2007-05-14
11:52:27.0 +0400
+++ kdelibs-3.5.8/kate/part/katesupercursor.cpp 2008-01-20 16:39:19.0
+0300
@@ -186,7 +186,7 @@
{
if (newLine)
{
-if (m_line > int(line) || (m_line == int(line) && m_col >= int(col)))
+if (m_line > int(line) || (m_line == int(line) && m_col > int(col)))
{
if(m_line == int(line))
m_col -= col;
** Affects: kdelibs (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
kate does not show newline inserted at the beginning
https://bugs.launchpad.net/bugs/184675
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 98955] Re: logd not running
> I think there is a good reason that they are not using bootlogd by > default. I think I read somewhere that bootlogd is quite buggy on some > systems, and it is hard to make it work correctly the way it is > designed. So the proper fix in the long run would be to redesign it > completely, as Scott is intending to do with logd in the future. I don't > remember where I read this however... Probably tekknokrat ran into one > of those problems. No, that error (cannot find console device 136:1) means that bootlogd was run from a terminal emulator (xterm or screen or mc or ... ). It must be run from a real console device. Passing console=/dev/console to the kernel is an error. I think the correct value is /dev/tty0 or /dev/tty1. And bootlogd will use something like this anyway. I have another problem with bootlogd. It gets confused by terminal control codes (those that make screen output prettier). I'll try to look at the source and see what can be done. -- logd not running https://bugs.launchpad.net/bugs/98955 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 177923] Re: some monospace fonts are not monospace
Sorry, I just discovered that email attachments do not work in launchpad. Including that screenshot now. ** Attachment added: "snapshot3.png" http://launchpadlibrarian.net/11569621/snapshot3.png -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 98955] Re: logd not running
To tekknokrat. You can try out the attached source package. This is bootlogd alone, separated from gutsy's sysvinit. I fixed logging of terminal codes and some other minor issues. It works for me here (Ubuntu stock kernel, no usplash, no mounting of /var). You can build and install it with the following commands: tar xzvf bootlogd_2.86.01.tar.gz # unpack the source cd bootlogd-2.86.01 debuild -us -uc -b # build the package cd .. sudo dpkg -i bootlogd_2.86.01_*.deb # install the package Please note that I am not an Ubuntu developer and the package is not official in any way. So it is a good measure to audit it before installing. In the long run, I agree that we should wait for a boot logging support in upstart. Doing such things properly may require cooperation with the rest of the init system. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I did attach it! Maybe launchpad does not allow this via email. Now I am trying to do this using the web interface. ** Attachment added: "bootlogd_2.86.01.tar.gz (unofficial package)" http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I am not willing to maintain it seriously, it is too system-dependent. Nevertheless, here is a new version. Changes are: - Improved logfile formatting. - The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in the future. Again, please do not install it blindly. You cannot be sure that I am not giving you a trojan. ** Attachment added: "bootlogd_2.86.02.tar.gz" http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
> Yes, I sure understand that you don't want to be a maintainer for it, that > would probably be quite a lot of work. For me the [ok] comes on it's own > separate: > Sun Jan 27 21:52:32 2008: * Starting system message bus dbus > Sun Jan 27 21:52:32 2008: [ OK ] > > Is this intentional? Otherwise this seems much nicer than before. Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll send the fixes there some day. The OK placement is yes, sort of intentional. They use a lot of terminal trickery to make output look better, and logging it correctly would require many changes to the code. I had to choose from a couple of simple rules, and the other choices led to worse results. After all, this "OK" is a separate message and its timing may be useful. You can make it appear on the same line by changing the source as follows. Go to bootlog.c line 361, there will be a part of switch like this: case '\n': case '\r": ... Change it to: case '\r': break; case '\n': ... (that is, interchange the two cases and insert "break;" between them). But then you will lose, among other things, the summary of a long fsck run (it will be truncated as a part of one extra long line). -- logd not running https://bugs.launchpad.net/bugs/98955 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 184675] Re: kate does not show newline inserted at the beginning
If my copy-pasting broke the patch, see the attached one here. It still works for me, now with kdelibs-3.5.8-0ubuntu3.2. I apply it before running anything from debian/rules. Here is what I do: apt-get source kdelibs patch -d kdelibs-3.5.8 -p1 < newline.patch cd kdelibs-3.5.8 debuild -us -uc -b sudo dpkg -i kdelibs4c2a_3.5.8-0ubuntu3.2_i386.deb Note that the affected fragment is in some obscure shared library which may be loaded via dlopen(). If you install the new version in /usr/local, the old one could still be used. It also makes sense to restart KDE to get rid of preloaded stuff (it works for me without restarting but generally KDE does not support live upgrading). ** Attachment added: "newline.patch" http://launchpadlibrarian.net/11600097/newline.patch -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 24 September 2008, Richard Birnie wrote: > Do you still observe this bug in more recent versions of kmail? Yes I still observe it in hardy. > I just tried to reproduce this in both hardy and intrepid both with kde4 and kmail 1.10.1 For some reason, the version I am using is older: ~$ kmail --version Qt: 3.3.8b KDE: 3.5.9 KMail: 1.9.9 The kmail package version (as shown by aptitude) is 4:3.5.9-0ubuntu3. However aptitude does not show any upgradable packages. Do I miss some repository to upgrade from? -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177923] some monospace fonts are not monospace
Public bug reported: System: fresh kubuntu 7-10 (konsole 1.6.6, KDE 3.5.8), LANG=en_US.UTF-8. To reproduce: In konsole, run 'cat .kde/Autostart/.directory', then scroll back (preferably with shift-arrows) and watch the line "Name[km]=..." The letters are substituted by squares whose width is larger than 1 but smaller than 2 ordinary characters. They garble other lines when scrolled. There is a similar problem with the line 'Name[ta]=...' . The letters are rendered but the width is wrong, and it produces garbage when scrolled. On my system, the font in konsole is set to Monospace-Regular-15. Other fonts sizes have the same problem. Here are those lines (copy-pasted from konsole): Name[km]=ចាបផដើមសវយបរវតត Name[ta]=தானாகதுவககு ** Affects: ubuntu Importance: Undecided Status: New -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 177923] Re: some monospace fonts are not monospace
On Saturday 22 December 2007, Murat Güneş wrote: > Thanks for your report. Can you reproduce the problem in other > applications, or is it specific to Konsole? Posting a screenshot would > also help. See attachment. This is the result of 'cat .kde/Autostart/.directory' and scrolling up and down with shift-arrows. I've removed some Asian fonts since that, so there are more substituted characters than after a fresh install. But most of them work fine. Note the difference in width of squares for "km" and "ko" languages in the screenshot. Kate a also has a problem with these fonts though it shows up differently. First it sends a message to stderr: ASSERT: "width" in /build/buildd/kdelibs-3.5.8/./kate/part/katerenderer.cpp (798) repeated many times. Then it cannot place cursor correctly in those lines and messes up when I try to mouse-select a part of the line. Another effect that I just observed: these lines in konsole and kate change when I move another window over them (it seems that the characters change their horizontal coordinates and overlap). I am using "nvidia" driver at the moment but I've checked that the original problem is reproducible under "nv". -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 77395] Re: udev rules not created for all supported backends
In Kubuntu-7.10 (libsane-extras1.0.18.8) I have a similar problem
with Epson Stylus CX4900. It is supported by the epkowa backend
according to the manpage. It is recognized and works when an application
is run as root. But it does not work for normal user due to a permission
problem.
I fixed this by adding the following lines to /etc/udev/libsane-extras.rules:
# EPSON Stylus CX4900
SYSFS{idVendor}=="04b8", SYSFS{idProduct}=="082b", MODE="664", GROUP="scanner"
--
udev rules not created for all supported backends
https://bugs.launchpad.net/bugs/77395
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 98955] Re: logd not running
> Can you give me layman steps of how to install your package? This is a Debian source package. It is meant to be installed using dpkg-related tools, not with "make; make install". A recipe was there in the post where I announced the package. Here it is again: # unpack the source tar xzvf bootlogd_2.86.02.tar.gz # build the package cd bootlogd-2.86.02 debuild -us -uc -b cd .. # install the package sudo dpkg -i bootlogd_2.86.02_*.deb As for the compilation warning, it looks harmless. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 29 October 2008, Richard Birnie wrote:
> I still haven't managed to reproduce this. KDE3.5.10 has now been
> released. Does this problem still occur for you?
>
Yes, it still inserts a space when I add "ibm866" in
Settings->Composer->Charset,
and it this space can occur in the outgoing mail.
I am pretty sure that this bug is in QT. I have libqt3-mt version
3.3.8-b-0ubuntu3
installed at the moment, you may have some better version.
Back then, I grepped the sources for "ibm 866" with a space and found an
occurence
in some table within QT sources but nowhere in KDE. I even made a patch (see
below)
and I think it worked then. Then I forgot about it, and then some apt-get
upgrade
killed it (sigh)... Sorry for not reporting this fact until now.
--- qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp.-space
+++ qt-x11-free-3.3.8really3.3.7/src/codecs/qtextcodec.cpp
@@ -1971,7 +1971,7 @@
0x0E48, 0x0E49, 0x0E4A, 0x0E4B, 0x0E4C, 0x0E4D, 0x0E4E, 0x0E4F,
0x0E50, 0x0E51, 0x0E52, 0x0E53, 0x0E54, 0x0E55, 0x0E56, 0x0E57,
0x0E58, 0x0E59, 0x0E5A, 0x0E5B, 0xFFFD, 0xFFFD, 0xFFFD, 0xFFFD} },
-{ "IBM 866", "IBM 866", 2086,
+{ "IBM866", "IBM 866", 2086,
{ 0x0410, 0x0411, 0x0412, 0x0413, 0x0414, 0x0415, 0x0416, 0x0417,
0x0418, 0x0419, 0x041A, 0x041B, 0x041C, 0x041D, 0x041E, 0x041F,
0x0420, 0x0421, 0x0422, 0x0423, 0x0424, 0x0425, 0x0426, 0x0427,
--
kmail composer uses wrong name for ibm866 charset
https://bugs.launchpad.net/bugs/188950
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 188950] Re: kmail composer uses wrong name for ibm866 charset
On Wednesday 24 September 2008, Richard Birnie wrote: > Do you still observe this bug in more recent versions of kmail? Yes I still observe it in hardy. > I just tried to reproduce this in both hardy and intrepid both with kde4 and kmail 1.10.1 For some reason, the version I am using is older: ~$ kmail --version Qt: 3.3.8b KDE: 3.5.9 KMail: 1.9.9 The kmail package version (as shown by aptitude) is 4:3.5.9-0ubuntu3. However aptitude does not show any upgradable packages. Do I miss some repository to upgrade from? -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 184675] Re: kate does not show newline inserted at the beginning
On Tuesday 29 January 2008, Cesare Tirabassi wrote: > My bad, I installed through upgrade and didn't notice that kdelibs4c2a > was held back. Yes, I can confirm that it works (using > 4:3.5.8-4ubuntu6), I'm subscribing u-m-s in case they care to include > this with the next update, but note that this was fixed for KDE 4 > (http://bugs.kde.org/show_bug.cgi?id=146300). Thanks. I hope KDE3 will be packaged and supported for a while (at this stage KDE4 is far from being usable for real work). -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 188950] [NEW] kmail composer uses wrong name for ibm866 charset
Public bug reported: Kmail composer understands the "ibm866" charset but uses "ibm 866" (with a space!) as its name in outgoing mail. This is incorrect, and other mail clients are confused by this space. I was hit by this when I received a mail with charset=ibm866, replied to it, and recipients could not read the reply because Kmail tried to use the same charset when replying but wrote 'charset="ibm 866"' in the header. To reproduce: In Kmail, go to Settings -> Composer -> Charset, try to add "ibm866" to the list. It adds "ibm 866" instead. Or, alternatively: Make sure the option "Keep original charset when replying ..." (in the same menu) is checked. Get a mail with charset="ibm866" (for example, create a simple ascii mail and edit "Content-Type:" field by hand). Reply to this mail and view the reply as plain text. It has Content-Type: text/plain; charset="ibm 866" The clients that cannot read this include (some versions of) SquirrelMail, MS Outlook Express, The Bat. I am using Gutsy, kmail version is 4:3.5.7enterprise20070926-0ubuntu2. Output of kmail --version is: Qt: 3.3.7 KDE: 3.5.8 KMail: 1.9.6 (enterprise 0.20070907.709405) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- kmail composer uses wrong name for ibm866 charset https://bugs.launchpad.net/bugs/188950 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdepim in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 155490] Re: [gutsy] Screensavers don't start automatically in Kubuntu
I have a similar behavior with just two of the screensavers: kswarm and kspace. They can be started by the "Test" button in the Configure Desctop -> Screen Saver menu, but not automatically. After the timeout, the mouse cursor disappears, the panel clock freezes, but otherwise nothing happens on the screen. This is a desktop machine running current Kubuntu Gutsy (32bit). I don't use screen locking. The behavior is the same with intel and nvidia drivers. Adding DPMS-dependent=false does not help. Other screensavers that I tried (kclock, klines and some others) do work. -- [gutsy] Screensavers don't start automatically in Kubuntu https://bugs.launchpad.net/bugs/155490 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 98955] Re: logd not running
I think that using the old bootlogd is the right fix. It seems that bootlogd and logd can and should coexist on the same system (of course, if they write to different logfiles). They just serve different purposes. Bootlogd is to save everything sent to /dev/console. It does not know who writes what. It can start and exit any time, and scripts do not notice any change (no SIGPIPESs, no failed IO, no nothing). This is the right tool for the problem "what did that scrolled-away messages say?". Logd is heavier. It uses redirected output of these scripts. This allows to log them separately, but at a price: it is not transparent (a process can detect that its stdout is a socket), and it is must run forever (or at least be extremely careful with those redirected file descriptors, as they could be even passed on to daemons). It can be useful for problems like "which of these scripts issued this message?" And normally the answer should be clear even from the mixed output, so I would consider logd as a tool for special cases. So my suggestion is to add bootlogd to the system and use logd (once it is working properly) as an additional tool when needed. Sorry if my analysis is incorrect, I'm not an expert. Maybe some developer can comment on this further. -- logd not running https://bugs.launchpad.net/bugs/98955 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 146306] Re: Kate can't insert newline character before first character in file
Please reopen this bug. I have it here on Gutsy with KDE 3.5.8. Package versions: kdelibs4c2a-3.5.8-0ubuntu3.1, kate-3.5.8-0ubuntu3.1. To reproduce: open a file which has more lines than fits in the screen. Go to line 1, column 1, and hit Enter. Then a new line is inserted but not shown. In fact, it needs not be the first line in the file, only the first line on the screen. Same behaviour in Kile, so the bug is in katepart. -- Kate can't insert newline character before first character in file https://bugs.launchpad.net/bugs/146306 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 184675] kate does not show newline inserted at the beginning
Public bug reported:
This was already reported as bug #146306 (which is closed as
unreproducible). I have this issue on Gutsy with current kdelibs
(kdelibs4c2a-3.5.8-0ubuntu3.1).
To reproduce: run Kate on a file with more lines than kate's window has
(this is essential), then hit Enter at the beginning of the file. Kate
inserts a line but does not display it (until you hit Uparrow or
something similar).
This also happens if it is not the beginning of the file but the
beginning of the visible part. You can hit Enter several times and still
see no effect (as if the key did not work). Same behavior with Kile
instead of Kate.
The bug was introduced at some point between KDE 3.5.5 and KDE 3.5.8.
The following patch fixes it.
--- kdelibs-3.5.8/kate/part/katesupercursor.cpp.orig2007-05-14
11:52:27.0 +0400
+++ kdelibs-3.5.8/kate/part/katesupercursor.cpp 2008-01-20 16:39:19.0
+0300
@@ -186,7 +186,7 @@
{
if (newLine)
{
-if (m_line > int(line) || (m_line == int(line) && m_col >= int(col)))
+if (m_line > int(line) || (m_line == int(line) && m_col > int(col)))
{
if(m_line == int(line))
m_col -= col;
** Affects: kdelibs (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
kate does not show newline inserted at the beginning
https://bugs.launchpad.net/bugs/184675
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 98955] Re: logd not running
> I think there is a good reason that they are not using bootlogd by > default. I think I read somewhere that bootlogd is quite buggy on some > systems, and it is hard to make it work correctly the way it is > designed. So the proper fix in the long run would be to redesign it > completely, as Scott is intending to do with logd in the future. I don't > remember where I read this however... Probably tekknokrat ran into one > of those problems. No, that error (cannot find console device 136:1) means that bootlogd was run from a terminal emulator (xterm or screen or mc or ... ). It must be run from a real console device. Passing console=/dev/console to the kernel is an error. I think the correct value is /dev/tty0 or /dev/tty1. And bootlogd will use something like this anyway. I have another problem with bootlogd. It gets confused by terminal control codes (those that make screen output prettier). I'll try to look at the source and see what can be done. -- logd not running https://bugs.launchpad.net/bugs/98955 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 177923] Re: some monospace fonts are not monospace
Sorry, I just discovered that email attachments do not work in launchpad. Including that screenshot now. ** Attachment added: "snapshot3.png" http://launchpadlibrarian.net/11569621/snapshot3.png -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 98955] Re: logd not running
To tekknokrat. You can try out the attached source package. This is bootlogd alone, separated from gutsy's sysvinit. I fixed logging of terminal codes and some other minor issues. It works for me here (Ubuntu stock kernel, no usplash, no mounting of /var). You can build and install it with the following commands: tar xzvf bootlogd_2.86.01.tar.gz # unpack the source cd bootlogd-2.86.01 debuild -us -uc -b # build the package cd .. sudo dpkg -i bootlogd_2.86.01_*.deb # install the package Please note that I am not an Ubuntu developer and the package is not official in any way. So it is a good measure to audit it before installing. In the long run, I agree that we should wait for a boot logging support in upstart. Doing such things properly may require cooperation with the rest of the init system. -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I did attach it! Maybe launchpad does not allow this via email. Now I am trying to do this using the web interface. ** Attachment added: "bootlogd_2.86.01.tar.gz (unofficial package)" http://launchpadlibrarian.net/11569042/bootlogd_2.86.01.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
I am not willing to maintain it seriously, it is too system-dependent. Nevertheless, here is a new version. Changes are: - Improved logfile formatting. - The logfile is renamed to /var/log/bootmsg, to avoid conflict with logd in the future. Again, please do not install it blindly. You cannot be sure that I am not giving you a trojan. ** Attachment added: "bootlogd_2.86.02.tar.gz" http://launchpadlibrarian.net/11578525/bootlogd_2.86.02.tar.gz -- logd not running https://bugs.launchpad.net/bugs/98955 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 98955] Re: logd not running
> Yes, I sure understand that you don't want to be a maintainer for it, that > would probably be quite a lot of work. For me the [ok] comes on it's own > separate: > Sun Jan 27 21:52:32 2008: * Starting system message bus dbus > Sun Jan 27 21:52:32 2008: [ OK ] > > Is this intentional? Otherwise this seems much nicer than before. Well, bootlogd *has* a maintainer, it's Debian sysvinit team. Maybe I'll send the fixes there some day. The OK placement is yes, sort of intentional. They use a lot of terminal trickery to make output look better, and logging it correctly would require many changes to the code. I had to choose from a couple of simple rules, and the other choices led to worse results. After all, this "OK" is a separate message and its timing may be useful. You can make it appear on the same line by changing the source as follows. Go to bootlog.c line 361, there will be a part of switch like this: case '\n': case '\r": ... Change it to: case '\r': break; case '\n': ... (that is, interchange the two cases and insert "break;" between them). But then you will lose, among other things, the summary of a long fsck run (it will be truncated as a part of one extra long line). -- logd not running https://bugs.launchpad.net/bugs/98955 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 184675] Re: kate does not show newline inserted at the beginning
If my copy-pasting broke the patch, see the attached one here. It still works for me, now with kdelibs-3.5.8-0ubuntu3.2. I apply it before running anything from debian/rules. Here is what I do: apt-get source kdelibs patch -d kdelibs-3.5.8 -p1 < newline.patch cd kdelibs-3.5.8 debuild -us -uc -b sudo dpkg -i kdelibs4c2a_3.5.8-0ubuntu3.2_i386.deb Note that the affected fragment is in some obscure shared library which may be loaded via dlopen(). If you install the new version in /usr/local, the old one could still be used. It also makes sense to restart KDE to get rid of preloaded stuff (it works for me without restarting but generally KDE does not support live upgrading). ** Attachment added: "newline.patch" http://launchpadlibrarian.net/11600097/newline.patch -- kate does not show newline inserted at the beginning https://bugs.launchpad.net/bugs/184675 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 177923] some monospace fonts are not monospace
Public bug reported: System: fresh kubuntu 7-10 (konsole 1.6.6, KDE 3.5.8), LANG=en_US.UTF-8. To reproduce: In konsole, run 'cat .kde/Autostart/.directory', then scroll back (preferably with shift-arrows) and watch the line "Name[km]=..." The letters are substituted by squares whose width is larger than 1 but smaller than 2 ordinary characters. They garble other lines when scrolled. There is a similar problem with the line 'Name[ta]=...' . The letters are rendered but the width is wrong, and it produces garbage when scrolled. On my system, the font in konsole is set to Monospace-Regular-15. Other fonts sizes have the same problem. Here are those lines (copy-pasted from konsole): Name[km]=ចាបផដើមសវយបរវតត Name[ta]=தானாகதுவககு ** Affects: ubuntu Importance: Undecided Status: New -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 177923] Re: some monospace fonts are not monospace
On Saturday 22 December 2007, Murat Güneş wrote: > Thanks for your report. Can you reproduce the problem in other > applications, or is it specific to Konsole? Posting a screenshot would > also help. See attachment. This is the result of 'cat .kde/Autostart/.directory' and scrolling up and down with shift-arrows. I've removed some Asian fonts since that, so there are more substituted characters than after a fresh install. But most of them work fine. Note the difference in width of squares for "km" and "ko" languages in the screenshot. Kate a also has a problem with these fonts though it shows up differently. First it sends a message to stderr: ASSERT: "width" in /build/buildd/kdelibs-3.5.8/./kate/part/katerenderer.cpp (798) repeated many times. Then it cannot place cursor correctly in those lines and messes up when I try to mouse-select a part of the line. Another effect that I just observed: these lines in konsole and kate change when I move another window over them (it seems that the characters change their horizontal coordinates and overlap). I am using "nvidia" driver at the moment but I've checked that the original problem is reproducible under "nv". -- some monospace fonts are not monospace https://bugs.launchpad.net/bugs/177923 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 77395] Re: udev rules not created for all supported backends
In Kubuntu-7.10 (libsane-extras1.0.18.8) I have a similar problem
with Epson Stylus CX4900. It is supported by the epkowa backend
according to the manpage. It is recognized and works when an application
is run as root. But it does not work for normal user due to a permission
problem.
I fixed this by adding the following lines to /etc/udev/libsane-extras.rules:
# EPSON Stylus CX4900
SYSFS{idVendor}=="04b8", SYSFS{idProduct}=="082b", MODE="664", GROUP="scanner"
--
udev rules not created for all supported backends
https://bugs.launchpad.net/bugs/77395
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 98955] Re: logd not running
> i installed Sergei's version and it works but it only captures 3 seconds > of my boot messages, how can i fix this? Is there a lot of text to capture? If so, it might overflow the internal 32K buffer. It is defined on line 52 in bootlogd.c. Try to increase it. Also, there is a stop-bootlogd script which stops bootlogd near the end of boot sequence. Check when this script is run. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> i cant make the buffer big enough to log it all. my boot process takes > 23 seconds and the biggest buffer that i can get to work is 975kb > (999,999 bytes) which will only log 18 seconds. This is a strange constant. The 32-bit integer overflows near 2Gb. What is wrong with larger values? Doesn't the program compile, or doesn't it start? Do you measure the 18 seconds by the wall clock or by the timestamps in the log file? I'm not a great expert in bootlogd, but I thought that the internal buffer is used until /var is writeable, then it writes directly to the file. So if a buffer in bootlogd overflows *after* /var is made writeable, then this is a bug in bootlogd. Otherwise there is no way other than enlarging the buffer - it has to remember the messages somewhere until the disk is ready. > also is there a way to > log the shutdown messages? This is hard. You cannot save anything after the filesystems are unmounted. I've heard of someone who used a video camera to record screen messages. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
> Can you give me layman steps of how to install your package? This is a Debian source package. It is meant to be installed using dpkg-related tools, not with "make; make install". A recipe was there in the post where I announced the package. Here it is again: # unpack the source tar xzvf bootlogd_2.86.02.tar.gz # build the package cd bootlogd-2.86.02 debuild -us -uc -b cd .. # install the package sudo dpkg -i bootlogd_2.86.02_*.deb As for the compilation warning, it looks harmless. -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 98955] Re: logd not running
On Saturday 14 March 2009, Charles Atkinson wrote: > I expected this change to cause some breakage; perhaps bootlogd depended > on something set by the earlier boot scripts; why would the package > designers not start it right at the beginning of the boot process so it > could capture all the boot messages? It may work or not depending on the system. The program uses pseudo-terminals (PTYs). If you have BSD PTYs compiled in the kernel and have static pty* devices in your root filesystem, then yes, it should be possible to run bootlogd right from the beginning (perhaps even from the initial ramdisk). If not, you have to wait until /dev/pts is mounted by S11mountdevsubfs.sh. Best regards, Sergei -- logd not running https://bugs.launchpad.net/bugs/98955 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98955] Re: logd not running
I think that using the old bootlogd is the right fix. It seems that bootlogd and logd can and should coexist on the same system (of course, if they write to different logfiles). They just serve different purposes. Bootlogd is to save everything sent to /dev/console. It does not know who writes what. It can start and exit any time, and scripts do not notice any change (no SIGPIPESs, no failed IO, no nothing). This is the right tool for the problem "what did that scrolled-away messages say?". Logd is heavier. It uses redirected output of these scripts. This allows to log them separately, but at a price: it is not transparent (a process can detect that its stdout is a socket), and it is must run forever (or at least be extremely careful with those redirected file descriptors, as they could be even passed on to daemons). It can be useful for problems like "which of these scripts issued this message?" And normally the answer should be clear even from the mixed output, so I would consider logd as a tool for special cases. So my suggestion is to add bootlogd to the system and use logd (once it is working properly) as an additional tool when needed. Sorry if my analysis is incorrect, I'm not an expert. Maybe some developer can comment on this further. -- logd not running https://bugs.launchpad.net/bugs/98955 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 146306] Re: Kate can't insert newline character before first character in file
Please reopen this bug. I have it here on Gutsy with KDE 3.5.8. Package versions: kdelibs4c2a-3.5.8-0ubuntu3.1, kate-3.5.8-0ubuntu3.1. To reproduce: open a file which has more lines than fits in the screen. Go to line 1, column 1, and hit Enter. Then a new line is inserted but not shown. In fact, it needs not be the first line in the file, only the first line on the screen. Same behaviour in Kile, so the bug is in katepart. -- Kate can't insert newline character before first character in file https://bugs.launchpad.net/bugs/146306 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 184675] kate does not show newline inserted at the beginning
Public bug reported:
This was already reported as bug #146306 (which is closed as
unreproducible). I have this issue on Gutsy with current kdelibs
(kdelibs4c2a-3.5.8-0ubuntu3.1).
To reproduce: run Kate on a file with more lines than kate's window has
(this is essential), then hit Enter at the beginning of the file. Kate
inserts a line but does not display it (until you hit Uparrow or
something similar).
This also happens if it is not the beginning of the file but the
beginning of the visible part. You can hit Enter several times and still
see no effect (as if the key did not work). Same behavior with Kile
instead of Kate.
The bug was introduced at some point between KDE 3.5.5 and KDE 3.5.8.
The following patch fixes it.
--- kdelibs-3.5.8/kate/part/katesupercursor.cpp.orig2007-05-14
11:52:27.0 +0400
+++ kdelibs-3.5.8/kate/part/katesupercursor.cpp 2008-01-20 16:39:19.0
+0300
@@ -186,7 +186,7 @@
{
if (newLine)
{
-if (m_line > int(line) || (m_line == int(line) && m_col >= int(col)))
+if (m_line > int(line) || (m_line == int(line) && m_col > int(col)))
{
if(m_line == int(line))
m_col -= col;
** Affects: kdelibs (Ubuntu)
Importance: Undecided
Status: New
** Tags: patch
--
kate does not show newline inserted at the beginning
https://bugs.launchpad.net/bugs/184675
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 98955] Re: logd not running
> I think there is a good reason that they are not using bootlogd by > default. I think I read somewhere that bootlogd is quite buggy on some > systems, and it is hard to make it work correctly the way it is > designed. So the proper fix in the long run would be to redesign it > completely, as Scott is intending to do with logd in the future. I don't > remember where I read this however... Probably tekknokrat ran into one > of those problems. No, that error (cannot find console device 136:1) means that bootlogd was run from a terminal emulator (xterm or screen or mc or ... ). It must be run from a real console device. Passing console=/dev/console to the kernel is an error. I think the correct value is /dev/tty0 or /dev/tty1. And bootlogd will use something like this anyway. I have another problem with bootlogd. It gets confused by terminal control codes (those that make screen output prettier). I'll try to look at the source and see what can be done. -- logd not running https://bugs.launchpad.net/bugs/98955 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
