it would appear that i was unaware of a change in the base system which
caused scim to be the method to do this now. marking invalid.
** Changed in: ubuntu
Status: New = Invalid
--
[Hardy] Unicode Code Point entry (C-S-u code-point) is broken
https://bugs.launchpad.net/bugs/199590
You
organized
enough that I only had to spend probably 30 minutes narrowing down the
code that needed to be modified. I was made quite happy by that.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1
Public bug reported:
In Gutsy, C-S-u code-pointSpace/Enter used to enable one to type
symbols which exist in Unicode, but not on the keyboard (for example,
the ¶ symbol or pi). Now, if I want to enter these symbols, I have to
copy-paste from another source, such as fileformat.info's Unicode
I know that time is running low on getting fixes into Hardy and
everything, and there are probably far, far more important things to
look at... but is there a chnace that this can be looked at so that I
can re-submit changes if necessary?
--
Alltray fails to set window title with Compiz/Emerald
This bug also affects mergecap which is part of this package... I just
tried to create a merged file from a bunch of 100MB files, and the
output stopped at precisely 2 GiB with the error message mergecap:
Error writing to outfile: Less data was written than was requested.
Marking bug as
** Bug watch added: Wireshark Bugzilla #580
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=580
** Also affects: wireshark via
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=580
Importance: Unknown
Status: Unknown
--
wireshark does not have large file ( 2GiB) support
Confirming bug and dropping assignment prior to re-subscribing ubuntu-
universe-sponsors.
** Changed in: alltray (Ubuntu)
Assignee: Michael B. Trausch (mtrausch) = (unassigned)
Status: Incomplete = Confirmed
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray
-depends in debian/control.
* Modify debian/rules to use dpatch.
* Modify alltray.desktop comment to be more descriptive and thus useful.
-- Michael B. Trausch [EMAIL PROTECTED] Mon, 03 Mar 2008 22:17:28
-0500
** Attachment added: Updated debdiff per request
http://launchpadlibrarian.net
The policy for requesting sponsorship says to mark the bug as
confirmed, but that would seem to downgrade the bug's status. Should
I do so anyway, before requesting sponsorship?
--
name parameter for content-type for attachments should be last
https://bugs.launchpad.net/bugs/194642
You received
Here is the proper fix, against EDS.
Created a new helper function (_camel_header_param_format_append) to
handle the processing of MIME field parameters, and altered the main
function (camel_header_param_list_format_append) to use the new helper
and defer processing of the name= MIME field until
Public bug reported:
Binary package hint: emacs-snapshot
Using updated Emacs Snapshot in Hardy (emacs-snapshot (1:20080228-1)),
which seems to have a bug with regard to XFT display of fonts. Upstream
already has a bug report on the issue:
I just encountered bug 188344 in Brasero, and it looks like that these
two bugs are related and that there are several dupes of each.
Is this a bug with GLib, or is this a bug in the client applications
which use GLib? Any idea of a way to find out that information?
--
gnome-terminal crashed
Current version in Hardy (1:20080228-1) has XFT support.
It has a bug with the way that it handles XFT fonts at present, see bug
197366 for more information, but this particular bug is now fixed.
** Changed in: emacs-snapshot (Ubuntu)
Status: Triaged = Fix Released
--
Wishlist:
This fixes this bug by simply adding roman to the list of types, and
mapping it to normal the way it should be.
** Attachment added: Debdiff to fix this bug
http://launchpadlibrarian.net/12345833/lp197366.debdiff
--
Invalid face slant: roman when using XFT fonts
Marking confirmed prior to requesting sponsorship
** Changed in: emacs-snapshot (Ubuntu)
Status: New = Confirmed
--
Invalid face slant: roman when using XFT fonts
https://bugs.launchpad.net/bugs/197366
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Patch for use by upstream or users of other distributions
http://launchpadlibrarian.net/12345922/fix-xft-invalid-face-slant.diff
--
Invalid face slant: roman when using XFT fonts
https://bugs.launchpad.net/bugs/197366
You received this bug notification because you are a
Attaching diff for just the source files which may be used by upstream
** Attachment added: Diff for use on non-debian systems
http://launchpadlibrarian.net/12345920/fix-xft-invalid-face-slant.diff
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line
Ignore the last one; attached to wrong bug. :(
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line option.
https://bugs.launchpad.net/bugs/178541
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment removed: Diff for use on non-debian systems
http://launchpadlibrarian.net/12345920/fix-xft-invalid-face-
slant.diff
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line option.
https://bugs.launchpad.net/bugs/178541
You received this bug
Yes, this is still an issue in Hardy.
Am looking at the process to get the fix in now.
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line option.
https://bugs.launchpad.net/bugs/178541
You received this bug notification because you are a member of Ubuntu
Daniel: ppaput seems broken in Hardy. Is this easily fixable so that I
can follow the remainder of the instructions on
https://wiki.ubuntu.com/SponsorshipProcess/ppaput ?
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line option.
I think I managed to get this right without the ppaput utility. I am
not 100% sure if I am understanding the processes right for this,
though. I did confirm that this patch works using the instructions on
https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue under the section
Notes for
Setting to confirmed for pending review per
https://wiki.ubuntu.com/MOTU/Sponsorship/SponsorsQueue
** Changed in: alltray (Ubuntu)
Status: New = Confirmed
--
Alltray fails to set window title with Compiz/Emerald and --no-alltray command
line option.
This issue is not fixed—I just tested this on Hardy with the hardware
that I originally reported the issue on, out of the box and fully
updated, and jack sense still does not work.
Reverting to Confirmed status. This is something that does work in
that other system, though it seems that it is
Fix is confirmed.
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Fix Released
--
Unicode display and input is broken.
https://bugs.launchpad.net/bugs/181164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Fix is confirmed.
** Changed in: vte (Ubuntu)
Status: New = Fix Released
--
Unicode display and input is broken.
https://bugs.launchpad.net/bugs/181164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Am unsubscribing from this issue because I have no way to verify a fix
for it any longer. I no longer have the hardware that this issue was
reported for (I have 1 Broadcom and 1 Atheros chipset now.)
--
Wireless rt73usb requires Windows init and performs quite poorly
Would like to comment that I have encountered this bug myself, same
crash, different trigger. In my case, I triggered the bug by going to
Edit→Current Profile…→Colors, and unchecking the box that says Use
colors from system scheme. The good news is that it managed to save
the intended settings
into a build queue at the same time.
There is testing before it's sent off to be built by the machines that
build for the repository. This would not be unlike the way PPA works.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1
.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934 im: [EMAIL PROTECTED], jabber
Ubuntu Unofficial Backports Project:http://backports.trausch.us
Coreutils 6.10-3ubuntu1 is now in Hardy!
https://edge.launchpad.net/ubuntu/hardy/+source/coreutils/6.10-3ubuntu1
Party!
Thanks for getting it updated; I got stuck trying to figure out what was
wrong with “cp”. Seems like someone smarter than me figured it out :)
** Changed in: coreutils
for
a while. The fix is easy, but it's in another package which causes a
slight problem.
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934 im: [EMAIL PROTECTED], jabber
onto my other partition before I can do that. :)
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934 im: [EMAIL PROTECTED], jabber
Ubuntu Unofficial
Public bug reported:
This is a wishlist item to add the supermount package into the Ubuntu
family of systems to manage floppy drives, CD and DVD drives, USB keys,
and other removable filesystems.
It would be nice if the user would be able to choose whether supermount
or the current HAL managed
Confirmed yet again on a Gateway machine; this machine has no sound
working and the error message comes when the snd_hda_intel module is
inserted into the kernel. Discovered this bug while attempting to fix
audio on an nVidia Corporation MCP51 High Definition Audio (rev a2) on
a Gateway model
Public bug reported:
Binary package hint: banshee
Some devices (in particular the Motorola W490 cell phone device which
doubles as an audio player) are very picky about the way their files are
received. Banshee should support forced file formats with audio
devices. The W490 in particular
.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934 im: [EMAIL PROTECTED], jabber
Ubuntu Unofficial Backports Project:http://backports.trausch.us
Also, please note that this is new behavior in Hardy. In Feisty and
Gutsy, gnome-terminal handled UTF-8/Unicode input and output
correctly—e.g., not displaying diamond-question marks for UTF-8
characters, and not transliterating, ignoring, or mishandling Unicode
input by Unicode code point in the
Public bug reported:
When using GNOME Terminal in Hardy, the Unicode display and input is
broken. Some characters (e.g., «, », ©, ®, ™, and others) are
transliterated, and others still (é, á, í, ö, and more accented letters)
simply show up as ?. ß shows up as ss, and so forth. This is
horribly
Side note: LC_ALL=POSIX man ls works as well.
** Also affects: vte (Ubuntu)
Importance: Undecided
Status: New
--
Unicode display and input is broken.
https://bugs.launchpad.net/bugs/181164
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Better and quicker test case:
[EMAIL PROTECTED]:~$ apt-cache showsrc vte
Package: vte
Binary: python-vte, libvte-doc, python-vte-dbg, libvte-dev, libvte-common,
libvte9
Version: 1:0.16.11-1ubuntu1
Priority: optional
Section: libs
Maintainer: Ubuntu Core developers [EMAIL PROTECTED]
I can confirm this bug; was just about to file it myself.
Is there any information that can be collected and posted here on this
bug to get a fix going?
** Changed in: command-not-found (Ubuntu)
Status: New = Confirmed
--
gdbm fatal: lseek error
https://bugs.launchpad.net/bugs/180368
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
compiz will not launch with fglrx driver - falls back to metacity
https://bugs.launchpad.net/bugs/173663
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
I just started using Compiz and Emerald on my laptop, since I recently
gained that ability. Much to my dismay, the applications that I dock to
my system tray using Alltray (including Evolution) stopped showing a
window title when their window was visible, but AllTray had it
To apply this patch, simply:
$ apt-get source alltray
$ cat path/to/patch | patch -p0
Would like review on this patch, as it is the first that I have written
for Ubuntu or for any project other than web stuff. If this patch is
acceptable, it should probably be released in Gutsy and definitely
Here is a debdiff to update a source package from the Ubuntu repos to
the testing version that I have created. The problem with my prior
patch was that it triggered a CPU-hungry infinite loop for non-compiz
WMs which was not desired, obviously. This fixes that, and thus the
original issue
A new GNU coreutils should be packaged for Hardy. Is there anything in
the way of this? What will it take to get a current coreutils into
Ubuntu? I keep coming back to this one…
--
please update package coreutils
https://bugs.launchpad.net/bugs/130299
You received this bug notification
Yes, I did, up until the time in which my old laptop (which I had the
dual-head configuration setup for) died due to… non-natural causes. I
can no longer verify the situation, however, because I do not have a way
to run dual-head with a driver that works well enough to do it. I have
currently a
Charles: did you enable the gutsy-proposed update repository?
--
[gutsy] OpenOffice crashes/hangs with some Gtk themes (e.g. Crux)
https://bugs.launchpad.net/bugs/131526
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
TBH, I have never had that broken on my system, so I cannot tell you.
It is possible that the symptom that you are describing is one that is
related to this GTK+ issue, since when the auto-save kicks off it /does/
change some of the UI to indicate that the autosave is working. Normal
saving was
Fix from proposed is confirmed to fix the issue here. Thanks for
getting this one knocked out!
--
[gutsy] OpenOffice crashes/hangs with some Gtk themes (e.g. Crux)
https://bugs.launchpad.net/bugs/131526
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I have figured out why udev seems to not work with this version of
coreutils. It is executed using “/bin/sh -e” as a command interpreter,
and the behavior of cp has changed such that it throws an error and
returns exit status 1 with the cp command in /etc/init.d/udev at system
startup. I have
No. It does indeed appear to be fixed on OOo 2.3.0 on Gutsy. Mind you,
I am using a build that fixes the GTK+ issue (bug 131526), but I see no
reason that it would be any different from the official Ubuntu build,
since the only modification is the addition of the upstream patch that
fixes the
Do you still have the issue if you use an upstream build of OOo? (I
mean, the binary version that is on their web site for download)? That
is what I tried to ask you on the other bug report before you created
this one. And yes, thank you for creating the new bug report because
this is a
Marking invalid per reporter’s most recent comments.
** Changed in: openoffice.org (Ubuntu)
Status: New = Invalid
--
Exception when saving to file in OpenOffice using UNO API (Java bindings)
https://bugs.launchpad.net/bugs/160906
You received this bug notification because you are a
meba: dAniel has a working AMD64 version. See his PPA:
https://edge.launchpad.net/%7Eblueyed/+archive
I have been using it since he built it, without issue.
--
[gutsy] OpenOffice crashes/hangs with some Gtk themes (e.g. Crux)
https://bugs.launchpad.net/bugs/131526
You received this bug
Fabio,
Please report a new bug for the issue above, along with all the
information that you can provide to reproduce the bug. It is not a GTK
issue, and thus is not relevant to this bug. Also, are you able to
reproduce the bug with upstream’s OpenOffice.org builds? If so, that
eliminates
Wow. Nearly 40 duplicates. I don’t think that I have seen such a
duplicated bug report. :-)
Any idea when this patch will be officially included in Ubuntu and an
update will be released? I have been using dAniel’s build since October
26, and it has been working extremely well for me. I use
coreutils 6.10~20070907-3
This is in Debian experimental. I have re-built this on my system, and
it seems to work for me, though I had to restart hal, dbus, and udev
manually before I could login and use my system. Not sure why that is
just yet, but it is
I am in the same boat—i386 build failed both on PPA and my own server
running it under pbuilder, and the amd64 build succeeded both on PPA and
my server.
I am installing packages now to see if they fix the problem at least on
the amd64 platform, and if they do then we just need to figure it out
Man, I need to learn how to type.
I meant to say that my build regressed bug 153132.
--
[gutsy] OpenOffice crashes/hangs on errors in current gtk theme
https://bugs.launchpad.net/bugs/131526
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Daniel, your build seems to say that it ran out of space:
bzcat: I/O or other error, bailing out. Possible reason follows.
bzcat: No space left on device
Input file = (stdin), output file = (stdout)
make[1]: *** [debian/stampdir/gsi-export-ne] Error 1
Mine from PPA says the same thing:
dAniel,
Your build has fixed the bug in amd64, at least as far as I can tell. I
can once again use context menus and the like with various non-Human
themes selected. I would say that if others can test and verify, and
the i386 build is able to build and is also fixed, this should probably
go
Well, PPA still hasn't indicated that it received my src pkg. It's been
nearly an hour, so I can only conclude that something isn't right with
PPA. I will kick off a pbuilder again on my machine and hope that
builds things.
--
[gutsy] OpenOffice crashes/hangs on errors in current gtk theme
The build failed with something wrong in your PPA. I lost my build
because my laptop (which had the controlling terminal) went to sleep.
BUT! I have packages—probably all but the localization I think. Will
know very soon.
I have a debdiff coming from OOo from Gutsy and mine.
** Attachment
Hrm.
One of the following is true at least in my case: (a) the patch
applied, but did nothing, (b) the patch that I added did not get applied
to the build, (c) the patch did not fix the problem, or (d) Not the
entirety of OOo built and the patch applies to a pkg that I couldn't
build. I still
I guess that OOo is a far longer build than I had anticipated. It is
still going on.
I have a few questions for those that may be watching this bug, seeing
that it is still not picked up by anyone in the BTS.
(1) Is someone who is a maintainer for the main component of Ubuntu working
on this
I've added the patch from OOo bug 82608 to a local source tree and am
building it on my server as soon as it is uploaded. I should be able to
install it by mid-afternoon tomorrow, and see if it fixes the problem.
Here's hoping that the build does not fail. :-)
If it is successful, I will have
My testing version is _still_ building. It will be some time before it
is done. If someone knows how to build it and take advantage of large
numbers of CPUs for the build, and can do so, they might just beat my
little uniprocessor box. :-P
--
[gutsy] OpenOffice crashes/hangs on errors in
On Sun, 2007-10-21 at 18:01 +, Chris Cheney wrote:
- OpenOffice.org does not support OpenType fonts
+ OpenOffice does not support OpenType fonts
http://www.openoffice.org/FAQs/faq-other.html#4
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1
.
Alternatively, I have found that a (better, IMHO) workaround for me is
to simply use Abiword and Gnumeric.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934
On Mon, 2007-10-22 at 15:13 +, Pascal de Bruijn wrote:
What does the OpenOffice/OpenOffice.org trademark have to do with this?
The bug was renamed in violation of an existing trademark when it was
properly named the first time. I was merely pointing that out.
-- Mike
--
Michael B
down8ve:
While I have to use OOo/Abiword for my homework, I use LaTeX for
everything else. Oh, how I wished I could just use LaTeX for
everything. :-P
--
[gutsy] OpenOffice crashes/hangs on errors in current gtk theme
https://bugs.launchpad.net/bugs/131526
You received this bug notification
I attached the upstream bug to this issue. It seems that they have a
patch that fixes it. I will (try to) build and test it tomorrow, but I
am not sure if I can pull that off or not. The last time I tried to
build OOo, it took 16 hours and failed at the end. :-P
** Also affects: openoffice
GNU coreutils is vastly out-of-date, and should really be updated. Why
is the coreutils presently in use so old?
** Changed in: coreutils (Ubuntu)
Status: New = Confirmed
--
please update package coreutils
https://bugs.launchpad.net/bugs/130299
You received this bug notification because
*** This bug is a duplicate of bug 136278 ***
https://bugs.launchpad.net/bugs/136278
** This bug has been marked a duplicate of bug 136278
[Gutsy] Open Office freezes if i select print... from menu
--
Showstopper: OOo restricts theme choices
https://bugs.launchpad.net/bugs/154224
You
---the _last_ thing
that should make a piece of software crash is the theme you are using.
--- Mike
--
Michael B. Trausch [EMAIL PROTECTED]
home: 404-592-5746, 1 www.trausch.us
cell: 678-522-7934 im
Interesting. I was just commenting on how asinine the change your
theme fix is in bug 154224, which I reported and is a dup of this one.
It's not right: when did we go from expecting people to code
defensively to expecting users to take the brunt of a developer's
inability to defensively
** Attachment added: oocalc-crash.txt
http://launchpadlibrarian.net/10062611/oocalc-crash.txt
--
[Gutsy] Showstopper crashes in Writer, Calc
https://bugs.launchpad.net/bugs/154224
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Public bug reported:
Consistently, when I attempt to select any item from a context menu in a
document in Writer or Calc, OpenOffice locks up. Apport is not catching
a crash, and when I run it from a terminal, the same error is displayed
(see attachment to come).
The only way to close is it to
Marking confirmed per confirmation marked by Neatchee.
** Changed in: openoffice.org (Ubuntu)
Status: New = Confirmed
--
[Gutsy] Showstopper crashes in Writer, Calc
https://bugs.launchpad.net/bugs/154224
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: lspci.out.txt
http://launchpadlibrarian.net/10060688/lspci.out.txt
--
USB dies when using mass-storage
https://bugs.launchpad.net/bugs/154092
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
On a Dell Inspiron 1501, there are problems with the USB chipset and the
kernel. This probably needs to be filed upstream with the kernel
developers, because I was able to reproduce the issue with several
versions of the Linux kernel, including the latest one I could get my
** Attachment added: lshal.out.txt
http://launchpadlibrarian.net/10060686/lshal.out.txt
--
USB dies when using mass-storage
https://bugs.launchpad.net/bugs/154092
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Here is what happens when USB dies. The CPU usage on I/O wait goes way
up (to 100% on one core, and sometimes both), the USB processes and the
process that was using USB is stuck in a state of uninterruptable sleep,
and the only way to fix the issue is to re-boot. This happens on any
activity
Another one that is closed. This issue is cropping up again in Gutsy:
[EMAIL PROTECTED]:~$ strace -p 16345
Process 16345 attached - interrupt to quit
futex(0x2ae24380a980, FUTEX_WAIT, 2, NULL
I think that when I originally reported this bug, I was using a 32-bit
system. I am presently using a
Jack sense still is not working on the hardware that I originally
reported the problem with, in the Gutsy Gibbon distribution.
I think that there is some capability missing in the ALSA driver to
sense all of the ports that my system has. The switchover on this
hardware is definitely a soft
501 - 587 of 587 matches
Mail list logo
