[Bug 1956181] [NEW] Jabref missing dependency?
Public bug reported: Tried to install jabref on KDE Neon (Ubuntu 20.04) and it fails to start with the following error message: ``` Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libawt_xawt.so ``` After installing `openjdk-11-jdk` it works fine. Should this packages simply be in the dependency list? ** Affects: jabref (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956181 Title: Jabref missing dependency? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jabref/+bug/1956181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 463078] Re: Dia export to Cairo PNG causes mangled text fonts
To asavah, check above I believe he said you need version 15.04 or better. However, I will admit I have not tested it, having moved to CentOS some years ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/463078 Title: Dia export to Cairo PNG causes mangled text fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/463078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
No thank you sir! The only problem remains how to explain to people that their data has turned upside down after they upgrade. Fortunately that's no problem of mine :-) At any rate, as far as I'm concerned that about fixes this bug... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
No thank you sir! The only problem remains how to explain to people that their data has turned upside down after they upgrade. Fortunately that's no problem of mine :-) At any rate, as far as I'm concerned that about fixes this bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924100] [NEW] CSV headers are wrong -- two missing columns
Public bug reported: If you run with -x4 or similar to output a CSV and then load up the CSV into a spreadsheet (e.g. gnumeric) then you see the columns don't line up with the headers properly. I believe that two extra header items are required. This is with Ubuntu 10.04.2 LTS bonnie++ version 1.96 Note that I recompiled from source to give bigger values to Seeks and UpdateSeek in order to test a RAID system that is faster than the standard bonnie++ compile values can cater for. However, I pulled down the ubuntu source archive (with apt-get source and the CSV headers are the same as earlier testing on the same version from the ubuntu binary package). I will add some files below. ** Affects: bonnie++ (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924100 Title: CSV headers are wrong -- two missing columns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bonnie++/+bug/924100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924100] Re: CSV headers are wrong -- two missing columns
Here are two CSV outputs from bonnie++ that I generated (note the = lines are stuff I put in myself to separate the O_DIRECT trial run from the non O_DIRECT trial run). I've put all the outputs into a single file. The series was generated with: bonnie++ -f -s 33000:4096 -n 1024 -x4 -D Also, same again without the -D option. ** Attachment added: 2012-01-31_bonnie.csv https://bugs.launchpad.net/ubuntu/+source/bonnie++/+bug/924100/+attachment/2702246/+files/2012-01-31_bonnie.csv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924100 Title: CSV headers are wrong -- two missing columns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bonnie++/+bug/924100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924100] Re: CSV headers are wrong -- two missing columns
Here is the same in gnumeric format. Note that the columns do not line up. It does not make sense that the file_size would be 1 and the io_chunk_size would be 1327979580 because actually these headers should be two steps over. Actually file_size should really be 33000M and io_chunk_size should be 4k. Most probably the two missing columns in the header are concurrency and random_seed, that's my best guess. This would just require a change to a print statement to fix (but it makes a big difference when reading out the results). ** Attachment added: 2012-01-31_bonnie.gnumeric https://bugs.launchpad.net/ubuntu/+source/bonnie++/+bug/924100/+attachment/2702273/+files/2012-01-31_bonnie.gnumeric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924100 Title: CSV headers are wrong -- two missing columns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bonnie++/+bug/924100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
For what it's worth, I've attached a graph of the same machine, running normally, with IO Service time over a day, after modification -- no random downward streaks to zero, much more readable, and the numbers actually make sense. ** Attachment added: IO Service Time - by day (modified plugin) https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2694148/+files/iostat_ios-day.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here's the Disk Latency graph as a comparison -- similar information, but not exactly the same. ** Attachment added: Disk Latency per device - by day https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2694149/+files/diskstats_latency-day.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
For what it's worth, I've attached a graph of the same machine, running normally, with IO Service time over a day, after modification -- no random downward streaks to zero, much more readable, and the numbers actually make sense. ** Attachment added: IO Service Time - by day (modified plugin) https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2694148/+files/iostat_ios-day.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here's the Disk Latency graph as a comparison -- similar information, but not exactly the same. ** Attachment added: Disk Latency per device - by day https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2694149/+files/diskstats_latency-day.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is my suggestion, taking into account the U to mean NaN and also
I note that you can get deep negative spikes when the counters clock
over (unless I'm mistaken they are 32 bit counters, even on a 64 bit
kernel, and yes I do seem to have managed to clock at least one over).
LINE 202: print(${dev}_rtime.value , ($rio_diff 0 and $rtime_diff 0) ?
($rtime_diff / $rio_diff) : 'U', \n,
LINE 203: ${dev}_wtime.value , ($wio_diff 0 and $wtime_diff
0) ? ($wtime_diff / $wio_diff) : 'U', \n,
LINE 204: );
I've tested this for about half a day and it looks much nicer than the old
version, less clutter. When IO is not happening on a drive, the trace goes
away, and I think that's what should happen (people might for example use a
drive only for backups or some other intermittent activity).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/919429
Title:
Munin IO Service Time graph gives completely implausible numbers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is my suggestion, taking into account the U to mean NaN and also
I note that you can get deep negative spikes when the counters clock
over (unless I'm mistaken they are 32 bit counters, even on a 64 bit
kernel, and yes I do seem to have managed to clock at least one over).
LINE 202: print(${dev}_rtime.value , ($rio_diff 0 and $rtime_diff 0) ?
($rtime_diff / $rio_diff) : 'U', \n,
LINE 203: ${dev}_wtime.value , ($wio_diff 0 and $wtime_diff
0) ? ($wtime_diff / $wio_diff) : 'U', \n,
LINE 204: );
I've tested this for about half a day and it looks much nicer than the old
version, less clutter. When IO is not happening on a drive, the trace goes
away, and I think that's what should happen (people might for example use a
drive only for backups or some other intermittent activity).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919429
Title:
Munin IO Service Time graph gives completely implausible numbers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Agree that the IO Service time is made somewhat redundant by the Disk Latency graph which shows much the same information. However, IO Service time itemises read and write, and after coming this far, seems a shame not to make the small fix to get it working properly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Agree that the IO Service time is made somewhat redundant by the Disk Latency graph which shows much the same information. However, IO Service time itemises read and write, and after coming this far, seems a shame not to make the small fix to get it working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] [NEW] Munin IO Service Time graph gives completely implausible numbers
Public bug reported: Recently a process wrote lots of data to the disk (and I'll take responsibility for that) but the Disk IOs per device went up (makes sense) and the Disk latency per device also went up (yup, so far so good) but the IO Service time strangely went down! Yes, it showed more latency but less service time. That's incredible. I'm incredulous. I've been suspicious of this for some time, because I absolutely know that /dev/sdc is a faster device than /dev/sda and /dev/sdb and for a long time it has been showing the lowest latency and the highest service time. It always did seem weird, but now I'm sure these numbers are bogus. ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
** Attachment added: Versions and stuff from apport-cli https://bugs.launchpad.net/bugs/919429/+attachment/2684644/+files/bug.apport -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is the graph of the latency, also from munin. Showing the exact opposite to the other graph. This one gives an answer that I believe is correct (or at least it is plausible). Note that /dev/sdc is the fastest drive, and shows the lowest latency. Also note that when loaded heavily, the latency on /dev/sda and /dev/sdb go up (they are RAID mirror so they move together). ** Attachment added: Disk latency per device - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684669/+files/diskstats_latency-week.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is the offending graph, from munin. NOTE: the purple line is the fast drive, and the yellow line is a slower drive, but for some strange reason the yellow line goes DOWN under additional load (should go UP I would expect). Also, the results are completely the other way to the latency graph. ** Attachment added: IO Service time - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684645/+files/iostat_ios-week.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Just for reference, here is a graph of IO operations, showing the additional load. The green line is /dev/md0 but that is a RAID mirror of /dev/sda and /dev/sdb so they are taking the load. NOTE: the load on /dev/sdc is constant and would typically be the drive taking the most load. This graph seems very plausible to me. ** Attachment added: Disk IOs per device - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684671/+files/diskstats_iops-week.png -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Quite likely the kernel version may be significant here: Linux version 2.6.32-33-server (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #70-Ubuntu SMP Thu Jul 7 22:28:30 UTC 2011 linux-headers-2.6.32-332.6.32-33.70 linux-headers-2.6.32-33-server 2.6.32-33.70 linux-headers-server 2.6.32.33.39 linux-image-2.6.32-33-server 2.6.32-33.70 linux-image-server 2.6.32.33.39 linux-server 2.6.32.33.39 Also, see attached CPU info, not sure if that changed IOstat stuff, possibly it does. ** Attachment added: /proc/cpuinfo https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684681/+files/proc_cpuinfo.text -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
I can see one problem in the file /usr/share/munin/plugins/iostat_ios as
follows:
LINE 202: print(${dev}_rtime.value , ($rtime_diff != 0) ?
($rio_diff / $rtime_diff) : 0, \n,
LINE 203: ${dev}_wtime.value , ($wtime_diff != 0) ?
($wio_diff / $wtime_diff) : 0, \n,
LINE 204: );
Here we see it divides number of IO operations by time in milliseconds. However
the graph has the vertical axis in seconds. Dividing by time gives Hz never
back to seconds again. So the graph results are really in Hz (not a useful unit
given the context we are working with here). I suggest that the calculation
should be:
LINE 202: print(${dev}_rtime.value , ($rio_diff != 0) ?
($rtime_diff / $rio_diff) : 0, \n,
LINE 203: ${dev}_wtime.value , ($wio_diff != 0) ?
($wtime_diff / $wio_diff) : 0, \n,
LINE 204: );
There's another (minor) problem which is to say that returning 0 in a situation
where no IO has occurred is a lie, should return NaN or NA but if you read the
Munin protocol specification (see link below) it claims Output must be integer
or decimal number, so the have no provision for a plugin saying hey, this
value does not exist right now and that's strange because the RRD system does
support NaN for missing values -- but that's a bigger problem for another day.
http://munin-monitoring.org/wiki/protocol-config
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/919429
Title:
Munin IO Service Time graph gives completely implausible numbers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
http://munin- monitoring.org/browser/trunk/node/node.d.linux/iostat_ios.in?rev=121 (lines 147, 148, 149) Ha ha, sysadmins have been muddling over bogus values for the past 8 years. No one noticed all the readings were backwards, but I bet there have been plenty of reports handed to bosses over those years with charts fully of meaningless squiggly lines. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to munin in Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 919429] [NEW] Munin IO Service Time graph gives completely implausible numbers
Public bug reported: Recently a process wrote lots of data to the disk (and I'll take responsibility for that) but the Disk IOs per device went up (makes sense) and the Disk latency per device also went up (yup, so far so good) but the IO Service time strangely went down! Yes, it showed more latency but less service time. That's incredible. I'm incredulous. I've been suspicious of this for some time, because I absolutely know that /dev/sdc is a faster device than /dev/sda and /dev/sdb and for a long time it has been showing the lowest latency and the highest service time. It always did seem weird, but now I'm sure these numbers are bogus. ** Affects: munin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
** Attachment added: Versions and stuff from apport-cli https://bugs.launchpad.net/bugs/919429/+attachment/2684644/+files/bug.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is the offending graph, from munin. NOTE: the purple line is the fast drive, and the yellow line is a slower drive, but for some strange reason the yellow line goes DOWN under additional load (should go UP I would expect). Also, the results are completely the other way to the latency graph. ** Attachment added: IO Service time - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684645/+files/iostat_ios-week.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Here is the graph of the latency, also from munin. Showing the exact opposite to the other graph. This one gives an answer that I believe is correct (or at least it is plausible). Note that /dev/sdc is the fastest drive, and shows the lowest latency. Also note that when loaded heavily, the latency on /dev/sda and /dev/sdb go up (they are RAID mirror so they move together). ** Attachment added: Disk latency per device - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684669/+files/diskstats_latency-week.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Just for reference, here is a graph of IO operations, showing the additional load. The green line is /dev/md0 but that is a RAID mirror of /dev/sda and /dev/sdb so they are taking the load. NOTE: the load on /dev/sdc is constant and would typically be the drive taking the most load. This graph seems very plausible to me. ** Attachment added: Disk IOs per device - by week https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684671/+files/diskstats_iops-week.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
Quite likely the kernel version may be significant here: Linux version 2.6.32-33-server (buildd@yellow) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #70-Ubuntu SMP Thu Jul 7 22:28:30 UTC 2011 linux-headers-2.6.32-332.6.32-33.70 linux-headers-2.6.32-33-server 2.6.32-33.70 linux-headers-server 2.6.32.33.39 linux-image-2.6.32-33-server 2.6.32-33.70 linux-image-server 2.6.32.33.39 linux-server 2.6.32.33.39 Also, see attached CPU info, not sure if that changed IOstat stuff, possibly it does. ** Attachment added: /proc/cpuinfo https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+attachment/2684681/+files/proc_cpuinfo.text -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
I can see one problem in the file /usr/share/munin/plugins/iostat_ios as
follows:
LINE 202: print(${dev}_rtime.value , ($rtime_diff != 0) ?
($rio_diff / $rtime_diff) : 0, \n,
LINE 203: ${dev}_wtime.value , ($wtime_diff != 0) ?
($wio_diff / $wtime_diff) : 0, \n,
LINE 204: );
Here we see it divides number of IO operations by time in milliseconds. However
the graph has the vertical axis in seconds. Dividing by time gives Hz never
back to seconds again. So the graph results are really in Hz (not a useful unit
given the context we are working with here). I suggest that the calculation
should be:
LINE 202: print(${dev}_rtime.value , ($rio_diff != 0) ?
($rtime_diff / $rio_diff) : 0, \n,
LINE 203: ${dev}_wtime.value , ($wio_diff != 0) ?
($wtime_diff / $wio_diff) : 0, \n,
LINE 204: );
There's another (minor) problem which is to say that returning 0 in a situation
where no IO has occurred is a lie, should return NaN or NA but if you read the
Munin protocol specification (see link below) it claims Output must be integer
or decimal number, so the have no provision for a plugin saying hey, this
value does not exist right now and that's strange because the RRD system does
support NaN for missing values -- but that's a bigger problem for another day.
http://munin-monitoring.org/wiki/protocol-config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919429
Title:
Munin IO Service Time graph gives completely implausible numbers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919429] Re: Munin IO Service Time graph gives completely implausible numbers
http://munin- monitoring.org/browser/trunk/node/node.d.linux/iostat_ios.in?rev=121 (lines 147, 148, 149) Ha ha, sysadmins have been muddling over bogus values for the past 8 years. No one noticed all the readings were backwards, but I bet there have been plenty of reports handed to bosses over those years with charts fully of meaningless squiggly lines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919429 Title: Munin IO Service Time graph gives completely implausible numbers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/munin/+bug/919429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 408016] Re: Xorg crashes when handed bad xrender glyph data
Made a tiny bit more progress, trying to get upstream wine bug re-opened but they want to fob the blame onto X11 and ignore their own problems, so chance of a quick solution is unlikely. Summary of the wine problem as far as I can tell: badly behaved win32 exe programs will call CreateFontIndirect() with bogus parameters and somehow under real Microsoft Win-XP these programs actually work. Under wine the bogus parameters gumby up the font metric calculator, which in turn cranks the handle on the X11 drivers -- whole lot of code, not many error checks. Getting X11 fixed might be a good step towards getting other buggy applications fixed, then they can stop trying to blame everything on the X server! I'll be patching up my own version of wine but I hesitate to post any public patch because it is rather a delicate matter to deal with badly behaved exe programs in a way that maintains maximum Microsoft compatibility. Doing the job right requires excellent understanding of how the win32 fonts work and a bit of research into how Microsoft deal with the questionable cases. I've gone about as far as I can go with this so I would appreciate someone pushing my NULL pointer check into the X server code and close off this bug. Thanks. -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
Out on a limb, but the info might help someone :-( I've been tinkering with CentOS v5.4 and compiling wine-1.1.29-fe.tar.bz2 to run my EXE program. I've run up against similar problems (same hardware as above). Versions are: xorg-x11-drv-i810-1.6.5-9.25.el5 xorg-x11-server-Xorg-1.1.1-48.67.el5 Just for reference the RedHat package for i810 contains both of the drivers: /usr/lib/xorg/modules/drivers/i810_drv.so /usr/lib/xorg/modules/drivers/intel_drv.so and I'm using the intel driver, although the i810 driver also works on the same hardware. X does NOT crash for me in this configuration, but neither will wine actually run, I merely get the error message: X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 155 (RENDER) Minor opcode of failed request: 20 (RenderAddGlyphs) Serial number of failed request: 76507 Current serial number in output stream: 76512 If you check upstream ... http://cgit.freedesktop.org/xorg/xserver/tree/render/render.c ... you can see there is no NULL pointer check on pDstPix around line 1160 so I can't explain why the RedHat version does not crash in the same place, don't have time to go through it with a fine tooth comb. Still waiting for some patch that will prevent wine from delivering the bad glyph data in the first place. Here is an old bug report from 2003 were similar problems were evident (and no fix found back then either). http://www.mail-archive.com/xfre...@xfree86.org/msg06098.html Some Russian guy is coming up with almost exactly the same error using Kubuntu 9.10 + Wine 1.1.34 http://linuxforum.ru/index.php?s=ded24b144d5aca3620acdab78ec69455showtopic=106168pid=990715st=0#entry990715 Another wine bug (this time from only a few month ago, from a Russian using fedora 11 and wine 1.1.29) http://bugs.winehq.org/show_bug.cgi?id=19986 I just have to quote the resolution of wine bug 19986: Most likely bad video drivers. Wine is a user app and by definition can not crash X server. Invalid. As they say, you can learn a lot, just by looking but Oh Boy! It is so difficult to get people to look. Maybe someone can have a good laugh out of all this. I'm off to have a cry now. Does launchpad offer a tissuebox feature? Probably it should... ** Bug watch added: Wine Bugzilla #19986 http://bugs.winehq.org/show_bug.cgi?id=19986 ** Also affects: xserver-xorg-video-intel via http://bugs.winehq.org/show_bug.cgi?id=19986 Importance: Unknown Status: Unknown -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 242844] Re: [ooo-build] cannot start OpenOffice.org with xvfb-run
On close inspection the soffice script is not the real culprit because although it always backgrounds the binary it also has wait $! right afterward so the critical behaviour occurs at a deeper level when the binary forks various layers of itself. I'd like to just add a comment here that it should not be a guessing game to figure out whether a program will detach itself or not. Consider this file: /usr/lib/mime/packages/openoffice.org-writer The contents get into /etc/mailcap when /usr/sbin/update-mime runs, and hence various programs (for example the mutt email client) are instructed how they should execute OpenOffice in order to display a file. The current setting is: soffice -no-oosplash -writer '%s' Sadly, this will detach if OpenOffice is running somewhere on the desktop, but it will not detach should this be the first instance of OpenOffice. In other words, arbitrarily it may or may not detach for reasons unrelated to (and unknowable to) the program that tries to invoke the MIME entry. By the way, the -no-oosplash option still shows a splash screen (go figure), the open office wiki does not document the -no-oosplash option either (maybe it is not a supported option). What should happen is that certain command line options force it to NEVER detach, strictly if those options are present. In every other situation it should ALWAYS detach because OpenOffice is primarily an interactive desktop application. The behaviour of a command should never depend on factors beyond the options of that command, otherwise everyone is back into guessing games. For what it's worth, the /usr/bin/oowriter script does appear to always detach as far as I can check. Would be nice if the OpenOffice website would make more of an effort to document the supported command line options so people working with this had some idea of what is supposed to happen. -- [ooo-build] cannot start OpenOffice.org with xvfb-run https://bugs.launchpad.net/bugs/242844 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 463078] [NEW] Dia export to Cairo PNG causes mangled text fonts
Public bug reported: Binary package hint: dia Description:Ubuntu 9.10 Release:9.10 dia 0.97-2 dia-common 0.97-2 dia-libs 0.97-2 libcairo2 1.8.8-2ubuntu1 libfreetype6 2.3.9-5 libpango1.0-0 1.26.0-1 libpango1.0-common 1.26.0-1 Method to demonstrate: load the file text.dia then export to PNG using Cairo and export to PNG using Pixbuf -- the character layout has a strange gap in the Cairo output. Note that output PNG files are also attached to this bug report, and this problem happens with various other more complex dia outputs as well as this simple example. ** Affects: dia (Ubuntu) Importance: Undecided Status: New -- Dia export to Cairo PNG causes mangled text fonts https://bugs.launchpad.net/bugs/463078 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 463078] Re: Dia export to Cairo PNG causes mangled text fonts
** Attachment added: Output to PNG using Cairo http://launchpadlibrarian.net/34581953/text_cairo.png -- Dia export to Cairo PNG causes mangled text fonts https://bugs.launchpad.net/bugs/463078 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 463078] Re: Dia export to Cairo PNG causes mangled text fonts
** Attachment added: Output to PNG using Pixbuf http://launchpadlibrarian.net/34581967/text_pixbuf.png -- Dia export to Cairo PNG causes mangled text fonts https://bugs.launchpad.net/bugs/463078 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 463078] Re: Dia export to Cairo PNG causes mangled text fonts
** Attachment added: DIA source file with very simple drawing http://launchpadlibrarian.net/34581919/text.dia -- Dia export to Cairo PNG causes mangled text fonts https://bugs.launchpad.net/bugs/463078 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 463078] Re: Dia export to Cairo PNG causes mangled text fonts
Possibly the locale might be relevant here: LANG=en_AU.UTF-8 GDM_LANG=en_AU.UTF-8 XTERM_LOCALE=en_AU.UTF-8 I tried changing the local to the basic C locale and got exactly the same result (just changing environment variables). My screen is only 1024x600 if that makes a difference (but fonts onscreen always display correctly so seems unlikely that would be a factor). -- Dia export to Cairo PNG causes mangled text fonts https://bugs.launchpad.net/bugs/463078 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 416073] Re: [i965] [karmic][GM965] low intel graphics performance - again
glxgears runs smooth now. Seems to genlock at exactly 60 frames per second. Linux version 2.6.31-10-generic (bui...@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu1) ) #35-Ubuntu SMP Tue Sep 22 17:33:42 UTC 2009 xserver-xorg-video-intel 2:2.8.1-1ubuntu2 libgl1-mesa-dri7.6.0~git20090817.7c422387-0ubuntu5 Extreme tux racer is down to around 15 frames per second. pinball now runs at 55 fps or sometimes down to 50, Tungsten Graphics, Inc. Mesa DRI Intel(R) 945GME GEM 20090712 2009Q2 RC3 x86/MMX/SSE2 Same processor as above (intel Atom 1600MHz hyperthreading) -- [i965] [karmic][GM965] low intel graphics performance - again https://bugs.launchpad.net/bugs/416073 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 416073] Re: [karmic][GM965] low intel graphics performance - again
I recently upgraded from Jaunty to Karmic and found that the 3D performance can be greatly effected by the kernel version. Using /usr/games/pinball as a reference (Tux table with effects turned off), I get: -- Linux version 2.6.27-14-generic (bui...@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Fri Jul 24 22:19:33 UTC 2009 pinball = 8 fps using software rendering (acceleration will not kick in). -- Linux version 2.6.28-14-generic (bui...@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #47-Ubuntu SMP Sat Jul 25 00:28:35 UTC 2009 pinball = 30 fps using Tungsten Graphics Mesa DRI Intel(R) 945GME GEM 20090712 2009Q2 RC3 x86/MMX/SSE2 -- Linux version 2.6.31-6-generic (bui...@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-1ubuntu3) ) #26-Ubuntu SMP Fri Aug 21 17:48:16 UTC 2009 pinball = 115 fps using Tungsten Graphics Mesa DRI Intel(R) 945GME GEM 20090712 2009Q2 RC3 x86/MMX/SSE2 -- In all cases: xserver-xorg-video-intel 2:2.8.0-0ubuntu2 xserver-xorg-core 2:1.6.3-1ubuntu4 libgl1-mesa-dri 7.5-1ubuntu1 CPU is Intel Atom, running hyperthreading at 1600MHz Using the latest kernel, games run quite smoothly, using older kernels they feel a bit surgy like some stop/start is happening. Flash games also run nicely, but not with the older kernels. Strangely, glxgears runs terribly jerky on my system, even with the 2.6.31-6 kernel. The extreme tux racer only manages around 20 fps but still feels smooth to play. -- [karmic][GM965] low intel graphics performance - again https://bugs.launchpad.net/bugs/416073 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 408016] Re: Xorg crashes when handed bad xrender glyph data
A brief update... Upgrading to Karmic does *NOT* fix the X11 xrender crash. Same program xrender_bug.c will demonstrate the crash, same patch from above will block the NULL pointer. Tested against: xserver-xorg-core 2:1.6.3-1ubuntu4 My problems with wine also remain after the upgrade to Karmic. Wine version 1.0.1 has the font size bug, but the wine1.2 (version 1.1.27) has other problems that kill my application so what I really need is a bit of each. Details of this wine problem no doubt belong in some other bug, once I have a bit more info. -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
For what it's worth, I found this wine bug: http://bugs.winehq.org/show_bug.cgi?id=17338 My wine application is giving very similar results, when I set: WINEDEBUG=+xrender,+synchronous I get this bit of trace: trace:xrender:LookupEntry found font in cache 0 trace:xrender:X11DRV_XRender_UpdateDrawable freeing pict = 1a008cc dc = 0x1d0 trace:xrender:X11DRV_XRender_SelectFont h=16 w=7 weight=400 it=0 charset=0 name=LSystem trace:xrender:dec_ref_cache dec'ing entry 0 to 22 trace:xrender:LookupEntry 0 trace:xrender:LookupEntry found font in cache 0 trace:xrender:X11DRV_XRender_SelectFont h=16 w=7 weight=400 it=0 charset=0 name=LSystem trace:xrender:dec_ref_cache dec'ing entry 0 to 22 trace:xrender:LookupEntry 0 trace:xrender:LookupEntry found font in cache 0 trace:xrender:X11DRV_XRender_SelectFont h=-11 w=65580 weight=100 it=64 charset=12 name=LMS Sans Serif trace:xrender:dec_ref_cache dec'ing entry 0 to 22 trace:xrender:LookupEntry 0 trace:xrender:LookupEntry 4 trace:xrender:LookupEntry 1 trace:xrender:LookupEntry 9 trace:xrender:LookupEntry 3 trace:xrender:LookupEntry 2 trace:xrender:LookupEntry 5 trace:xrender:LookupEntry 8 trace:xrender:LookupEntry 6 trace:xrender:LookupEntry 7 trace:xrender:LookupEntry font not in cache trace:xrender:AllocEntry freeing unused glyphset at cache 7 trace:xrender:X11DRV_XRender_ExtTextOut bitmap is not a DIB trace:xrender:X11DRV_XRender_ExtTextOut bitmap is not a DIB trace:xrender:X11DRV_XRender_ExtTextOut bitmap is not a DIB trace:xrender:X11DRV_XRender_SelectFont h=-11 w=65580 weight=100 it=64 charset=12 name=LMS Sans Serif trace:xrender:dec_ref_cache dec'ing entry 7 to 0 trace:xrender:LookupEntry 7 trace:xrender:LookupEntry found font in cache 7 trace:xrender:X11DRV_XRender_ExtTextOut bitmap is not a DIB trace:xrender:X11DRV_XRender_ExtTextOut allocing pict = 1a008ce dc = 0x1d0 drawable = 01e6 trace:xrender:UploadGlyph buflen = 1023100. Got metrics: 78700x13 adv=13160,0 origin=-1,11 *** buffer overflow detected *** After that things go south very rapidly. Obviously width 65580 is ridiculous, looks like a 16 bit signed/unsigned mismatch with a negative number slipping through some calculation. Based on the wine version, supposedly it is fixed in 1.1.21 so will try the dist upgrade to Karmic... what's the worst that could happen? ** Bug watch added: Wine Bugzilla #17338 http://bugs.winehq.org/show_bug.cgi?id=17338 -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
This patch protects against xrender_bug.c program from above (see attached patch). At least the desktop remains stable. I still can't run my application under wine, but the patched X gives these errors: X Error of failed request: BadLength (poly request too large or internal Xlib length error) Major opcode of failed request: 149 (RENDER) Minor opcode of failed request: 20 (RenderAddGlyphs) Serial number of failed request: 90044 Current serial number in output stream: 90053 Probably a step in the right direction, guess there is something wrong with wine font rendering (oh really? how shocking). ** Attachment added: Patch against xorg-server (2:1.6.0-0ubuntu14) jaunty, checks for NULL pointer http://launchpadlibrarian.net/30664626/nocrash_408016.patch -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
Did you try running the attached progam? -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
I have found that certain programs running under wine will trigger this crash. Recommended workaround to avoid the crash if you need to use some program that has problems... append to /etc/X11/xorg.conf Section Extensions Option RENDER disable EndSection -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] [NEW] Xorg crashes when handed bad xrender glyph data
Public bug reported: Binary package hint: xserver-xorg-air-core Description:Ubuntu 9.04 Release:9.04 xserver-xorg-core2:1.6.0-0ubuntu14 Backtrace: 0: /usr/X11R6/bin/X(xorg_backtrace+0x3b) [0x813518b] 1: /usr/X11R6/bin/X(xf86SigHandler+0x55) [0x80c7be5] 2: [0xb7fe5400] 3: /usr/X11R6/bin/X [0x817c1c7] 4: /usr/X11R6/bin/X [0x8175125] 5: /usr/X11R6/bin/X(Dispatch+0x33f) [0x808d57f] 6: /usr/X11R6/bin/X(main+0x3bd) [0x80722ed] 7: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bb2775] 8: /usr/X11R6/bin/X [0x80717a1] Saw signal 11. Server aborting. (II) AT Translated Set 2 keyboard: Close (II) UnloadModule: evdev (II) Video Bus: Close (II) UnloadModule: evdev (II) Macintosh mouse button emulation: Close (II) UnloadModule: evdev (II) UnloadModule: synaptics (II) AIGLX: Suspending AIGLX clients for VT switch (II) intel(0): xf86UnbindGARTMemory: unbind key 0 ddxSigGiveUp: Closing log See attached C program... ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
** Attachment added: xrender_bug.c http://launchpadlibrarian.net/29799552/xrender_bug.c -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
Wants to link to wrong package... ** Package changed: xorg-air (Ubuntu) = xorg-server (Ubuntu) -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
/var/log/Xorg.0.log.old ** Attachment added: Xorg.0.log.old http://launchpadlibrarian.net/29799939/Xorg.0.log.old -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 408016] Re: Xorg crashes when handed bad xrender glyph data
Have tested this against two different Nvidia graphics cards on ununtu (running the non-free Nvidia drivers) and Nvidia drivers seem to be completely immune to the crash. The crash did occur on a different machine also running intel driver and using Mobile Intel® GM45 Express Chipset so this is looking like something that depends on the particular graphics driver in use. Suggestion that someone with the same intel chipset should be the first to debug this problem. -- Xorg crashes when handed bad xrender glyph data https://bugs.launchpad.net/bugs/408016 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 103933] Re: Java install via Add/Remove crashed
I have seen the same error with the missing libjli.so when installing Java into an ubuntu chroot. Making sure that the /proc was correctly mounted in the chroot caused the error to go away. Seems that the binary /usr/lib/jvm/java-6-sun-1.6.0.00/bin/java checks inside its own /proc/self/exe to find a path, and then mangles that path to find the shared library files. In other words, the libraries are found in a path RELATIVE to the running executable rather than normal absolute library paths. This allows it access to libraries outside the standard ldconfig system. I would guess that such a method might be fragile so hopefully this gives people a hint about where to look for problems. -- Java install via Add/Remove crashed https://bugs.launchpad.net/bugs/103933 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
