If screen has a poor idea of the number of lines in the display, or
gives incorrect information on the number of lines in a screen to the
shell, it could definitely cause the problems you describe. I notice
that it sounds like most of the corruption you're experiencing has to do
with line displacem
Reassigning to ncurses from screen, as proper terminfo description files
is that package's responsibility, and not screen's (except things like
/usr/share/terminfo/s/screen, but I don't know that those other screen
ones are part of the screen package proper).
The offending bit is probably "kb=^H";
Gavin Panella wrote:
> Thanks for the reply Micah. C-a i reported one row less than C-a :dinfo
> -- but I think that's correct because of the caption bar I have
> configured. rxvt-unicode agrees with :dinfo. I'll experiment today with
> detaching and reattaching, and also using C-a F.
Sounds like
*** This bug is a duplicate of bug 360950 ***
https://bugs.launchpad.net/bugs/360950
Note that wget never uses MSG_PEEK anywhere.
Last I heard, it sounded like this bug was in the kernel, and has been
fixed in upstream (kernel)? Unfortunately, I have no references to
substantiate this: if som
*** This bug is a duplicate of bug 360950 ***
https://bugs.launchpad.net/bugs/360950
Aha! :)
--
TCP(wget:3084): Application bug, race in MSG_PEEK
https://bugs.launchpad.net/bugs/389043
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(I'll just add here that FWIW Ubuntu does not in fact ship with
.bash_profile at all, just the .bashrc)
--
newly opened gnome-terminal windows don't have .bash_profile sourced
https://bugs.launchpad.net/bugs/17962
You received this bug notification because you are a member of Ubuntu
Bugs, which i
As an end user, then, you should add ~/bin/ to your path from within
.bashrc, rather than .bash_profile. It has long been historical practice
for xterms and the like not to spawn login shells by default. For this
reason, people have for many years followed the practice of placing
anything important
This is usually a symptom of a broken terminfo description for whatever
terminal you happen to use screen from (specifically, the "ti/te"
capabilities). A workaround would probably be to place
termcapinfo ti@:te@
in your ~/.screenrc; where is the name your terminal identifies
itself as (via t
Could it possibly be the same bug, or at least related to
https://savannah.gnu.org/bugs/?26742 ?
The fact that the backend crashes strongly suggests to me that it's not
screen-profiles's/byobu's fault (though it may have generated the config
that triggers the bug in screen). Even if screen-profile
No, everyone's busy with other stuff :\
However, as you wrote that, I was (am) in the middle of writing an
outline of exactly what doc work needs to be done before a release can
happen. There are also a few small showstopper bugs that would need to
be fixed, but the doc work is by far the more dau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
So, as the documentation seems to be one of the biggest remaining
obstacles to a 4.1.0 release of GNU Screen, and as it's been this way a
very long time, I've taken one step towards trying to ease the prospect
of getting this work done.
I've gone thro
I'm not sure I understand: is the problem gone now that you've fixed
your $TERM? If so, this bug should be closed out.
It's a bad idea to lie to screen and tell it it's running under "screen"
when it's not (despite the fact that this piece of poor advice is
apparently all over the web).
I'm not a
"Wuff --- Wuff" is the vbell message; to disable it, put "vbell off" in
your ~/.screenrc.
The broken backspace thing... hit the backspace key a few times while
running "cat" within screen for clues to its source. A common cause is a
broken terminfo description (usually on xterm-color, I think), th
** Changed in: screen (Ubuntu)
Status: Incomplete => Invalid
** Changed in: screen (Ubuntu)
Assignee: greenmoss (ktyubuntu) => (unassigned)
--
A subset of input keys temporarily stop working
https://bugs.launchpad.net/bugs/349636
You received this bug notification because you are a m
Nonconventionally Creative wrote:
> Public bug reported:
>
> Binary package hint: wget
>
>>From the man page:
>Use of -O is not intended to mean simply "use the name file
> instead of the one in the URL;" rather, it is analogous to shell redirection:
> wget -O file http://foo
>
I don't wish to denigrate the seriousness of this bug; but it may be
worth pointing out that large organizations will more frequently deploy
"transparent" proxies, rather than configure everyone's browsers to use
something (which employees can more easily work around).
Of course, there are still p
I hadn't noticed this before, but of course in this case it's not
Synaptic downloading a package, but the package itself that downloads a
tarball during the "install" phase. In that case, it could well be
considered a bug in flashplugin-nonfree.
** Also affects: flashplugin-nonfree (Ubuntu)
Imp
See also the bugtracker for GNU Screen, where I discovered and analyzed
the problem.
https://savannah.gnu.org/bugs/?23699
--
Change Scroll Region and display glitch
https://bugs.launchpad.net/bugs/246701
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Attachment added: "scr-fix-min"
http://launchpadlibrarian.net/15894412/scr-fix-min
** Bug watch added: GNOME Bug Tracker #542087
http://bugzilla.gnome.org/show_bug.cgi?id=542087
** Also affects: vte via
http://bugzilla.gnome.org/show_bug.cgi?id=542087
Importance: Unknown
St
Public bug reported:
Please describe the problem:
After sending CSR so that the final line in the terminal is excluded from the
scroll region, glitches can occur when interspersing writes to the bottom line
with scrolls of the upper region.
Steps to reproduce:
I will attach a script (scr-fix-min)
Wget doesn't forget to download it; it can't. Wget groks HTML, not CSS,
so it can't even determine that the background image exists. Support for
CSS would fall under a feature request, not a bug report.
However, you may be pleased to know that CSS support has been
implemented in a development vers
No, the manpage is not incorrect. -p will download all inlined images,
sounds, and referenced stylesheets. It will _not_ download anything that
is linked to only from CSS files: that's true whether you use -p or -r
or some combination. If it can find it from HTML attributes (src="",
href=""), it wi
> That means that the sentence in the man page
> "all the files that are necessary to properly display a given HTML page."
> will not come true before ubuntu 9.x.
Well, "as determined by the specifications that Wget understands" is of
course implied. When Wget was originally written, CSS hadn't be
That's a different problem, if it's the first line that's working for
you.
A much better solution is to keep the backspace as ^?, and make sure
"stty erase ^?" is set for the terminal (or that the terminal is
otherwise set to send ^?). It makes a much better choice than ^H, which
confuses some pro
That link is not the same issue; it has to do with the terminfo and stty
disagreeing with eachother. Fixing either the terminfo or stty should
fix the problem (they agree with each other in upstream screen AFAICT;
they disagree in some packages).
This bug has to do with vte-based terminals, such a
ould replace data appearing in HTTP "Authorization"
headers with X's, as your username and password are easily recovered
from the real values for that field.
** Changed in: wget (Ubuntu)
Assignee: (unassigned) => Micah Cowan (micahcowan)
Status: New => Incomplete
--
wge
You neglected to mention the version. I'm assuming it was 1.10.2,
because this is a known bug that's been fixed since version 1.11 (so,
Intrepid Ibex should be fine).
--
Wget crashes on empty set-cookie header
https://bugs.launchpad.net/bugs/256819
You received this bug notification because you a
Fixing changeset is
http://hg.addictivecode.org/wget/mainline/rev/75578b1c235b
** Changed in: wget (Ubuntu)
Status: New => Confirmed
--
Crashed on recursive download.
https://bugs.launchpad.net/bugs/123521
You received this bug notification because you are a member of Ubuntu
Bugs, which i
See https://savannah.gnu.org/bugs/index.php?23472 for why this isn't a
bug
** Changed in: screen (Ubuntu)
Status: Incomplete => Invalid
--
Cannot connect to X server when screen is detached, then reattached
https://bugs.launchpad.net/bugs/47033
You received this bug notification because y
Reported upstream at https://savannah.gnu.org/bugs/index.php?20277
--
unable to re-encode some CJK punctuation from utf8 to gbk
https://bugs.launchpad.net/bugs/123370
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Changed in: screen (Ubuntu)
Status: New => Invalid
--
reattached screen partially useless in a different or new X session because of
changed env variables
https://bugs.launchpad.net/bugs/201660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Public bug reported:
Binary package hint: seahorse
Since upgrading to Hardy Heron, I ran into problems with the Passphrase
dialog when using Enigmail with Thunderbird. It'll plug along fine, not
grabbing focus, but accepting input. But then, at some point, I'll hit
"send" on a message, the passph
Public bug reported:
Binary package hint: seahorse
Since upgrading to Hardy, a few times I've discovered my
~/.gnupg/secring.gpg to be truncated to zero bytes. I suspect seahorse,
only because it's the major thing I can think of that has changed since
the upgrade; I have never explicitly installe
(setting to Confirmed due to an identified fix)
** Changed in: gnome-terminal (Ubuntu)
Status: Incomplete => Confirmed
--
[Hardy] Key combination Ctrl-] is ignored
https://bugs.launchpad.net/bugs/221516
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
Binary package hint: gnome-terminal
Steps to reproduce (some steps may not be necessary; I'm not on my home
machine right now so can't eliminate the unnecessary steps):
1. Open gnome-terminal
2. Type some stuff (may not be necessary)
3. Open a new tab via Control-Shift
Note: some common scripts use timestamping in combination with -O. That
has never worked, and was made an error in 1.11; however, since this can
potentially introduce brokenness to poorly-written system scripts (or,
some scripts could conceivably break on users' .wgetrc files), it has
been downgrad
Tracked upstream with https://savannah.gnu.org/bugs/index.php?23868
(Note that producing "Wuff Wuff!" is not enough to reproduce this bug:
you need to verify, say by typing into the "cat" command, that you're
actually getting ^@ characters for backspace: other problems with
backspaces are more com
This happens in xfce4 when preferences for sending backspace is set to
"autodetect". Not when an explicit value ^H or DELETE is set. Hm...
seems likely to be an xfce4 or vte thing, then. Retargetting for
xfce4-terminal.
For some annoying reason I can't for the life of me figure out (unless
it's so
Retargeting at vte; All xfce4-terminal does is call
vte_terminal_set_backspace_binding with VTE_ERASE_AUTO.
** Changed in: vte (Ubuntu)
Sourcepackagename: xfce4-terminal => vte
Status: Invalid => New
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/297
Just because it's a config issue, does not mean it's not a bug. The bug
(as explained in the original description) is that changing it away from
autodetect is required.
Tracked down the source of the problem: vte will send whatever the
terminal's erase character is, even when it's undefined (that
The problem isn't gnome-terminal: I've recently noticed that things like
changing workspaces, or closing windows, can cause input not to be
received in a window until I Alt-Tab twice to transfer focus away and
back. This happens in a variety of applications, and so is not gnome-
terminal specific.
** Attachment added: "Debdiff (hardy)"
http://launchpadlibrarian.net/16103643/vte.debdiff
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/29787
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Note; the patch above includes literal control characters in the source,
namely the ^? (DEL) character; it may not display properly, depending on
what you use to view it. I find this practice distasteful, but the
surrounding code included literal control characters as well, so I bowed
to consistenc
** Attachment added: "Debdiff (intrepid)"
http://launchpadlibrarian.net/16104491/vte-intrepid.diff
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/29787
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscrib
Setting to Confirmed per https://wiki.ubuntu.com/Bugs/HowToFix
** Changed in: vte (Ubuntu)
Status: New => Confirmed
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpad.net/bugs/29787
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Bug watch added: GNOME Bug Tracker #543379
http://bugzilla.gnome.org/show_bug.cgi?id=543379
** Also affects: vte via
http://bugzilla.gnome.org/show_bug.cgi?id=543379
Importance: Unknown
Status: Unknown
--
Backspace key in GNU Screen not detected correctly
https://bugs.launchpa
I thought it was quite clear: what is unclear about it? (Being unclear,
and being unreproducible to you, strike me as distinct complaints.)
No other steps. The given steps reproduce the problem very reliably for
me. Obviously there's a difference between my environment and yours, but
as to what it
Okay, so I verified that, while blowing away my gnome-terminal config
and restarting GNOME does not eliminate the problem, a fresh new account
does not exhibit the symptoms.
The difference appears to be that my normal account is set up to use the
SCIM X Input Method. On a fresh account, if I do an
Thanks, Seb. I'm going to go ahead and close this out then. I'm not
using Seahorse any more, so there's no way I'll be reproducing this any
time soon.
** Changed in: seahorse (Ubuntu)
Status: New => Invalid
--
Seahorse possibly deletes secret keys
https://bugs.launchpad.net/bugs/231504
Yo
Heh. Since the time this bug was filed, I've become an upstream co-
maintainer for GNU screen ^_^
Thanks for your patience. I've only recently discovered the full truth
of this issue.
As previously mentioned, there are three parts to this: (1) ncurses, (2)
screen, and (3) vim. As it turns out, (1
I'm not crazy about setting it when you press enter: it's at least as
confusing to people when they're running a program as it is when they're
typing a command. If we're going to disable it, I vote for disabling it
completely (until the user explicitly enables it with stty, or by
removing the appro
As I said, Ctrl-S doesn't currently do anything directly on the
commandline, other than to possibly invoke the search facility.
By default, when a command is actively running (I use
while true; do echo foo; sleep 1; done
), Ctrl-S does work to pause terminal output, for me at least.
--
Pleas
The most-recent release is now 1.11.3, which has significant
improvements over 1.11. 1.11.3 is actually already available in Debian
unstable, which means it will certainly be included for Intrepid Ibex
when they sync with Debian.
To get it into Hardy Heron, you'll need to file a backport request,
Note that, in the meantime, you can download the Debian package from
http://packages.debian.org/unstable/web/wget directly, and install it
with "sudo dpkg -i ". This doesn't always work for all
packages, but it often will, and does for this case.
--
Please upgrade wget to version 1.11
https://bug
I don't think we'll manage to make that date; there is still a large
amount of documentation work left to be done. Hopefully we'll make
Kreepy Kangaroo ;)
--
update to cvs version of screen
https://bugs.launchpad.net/bugs/183849
You received this bug notification because you are a member of Ubunt
This issue should be resolved in Wget-1.11.4, which is available in
Ubuntu 8.10, so this bug should be closed, as it has been fixed in
recent releases of Ubuntu (please re-open if you find this is not in
fact the case).
I expect this qualifies for a Stable Release Update for Hardy, so if you
would
g mc, and attach the
resulting screenlog.0 file to this report (if you view it with a pager
like less, it may mimick a text file; but it is actually a binary file,
so treat it like one: don't attempt to copy/paste it)
Thanks!
** Changed in: screen (Ubuntu)
Assignee: (unassigned) =
It's the value of $TERM that is wrong when you're running within screen.
Screen sets TERM=screen before it invokes a shell, so something is
changing that (most likely your shell profile or rcfile, but also look
for a "setenv" command in your ~/.screenrc).
I'll go ahead and close this bug out, as i
Confirmed that this bug still remains in latest upstream git sources,
and added tracking upstream
** Changed in: screen (Ubuntu)
Status: New => Confirmed
** Bug watch added: GNU Savannah Bug Tracker #25338
http://savannah.gnu.org/bugs/?25338
** Also affects: screen via
http://savann
Morten, is this the same "Wuff, Wuff" problem, which shows ^@ chars
inside cat?
If so, the way to fix this is to turn off any "autodetection" settings
for what backspace should send, and explicitly specify the code it
should send (probably, ^?). You could also download the latest sources
for scree
(Launchpad doesn't like the "index.php" part, otherwise it can track
Savannah bugs)
** Changed in: screen
Importance: Undecided => Unknown
Bugwatch: None => GNU Savannah Bug Tracker #25296
Status: New => Unknown
--
Insecure creation of /tmp/screen-exchange (symlink attack)
https:/
(It works so long as you remove the index.php part)
** Bug watch added: GNU Savannah Bug Tracker #25348
http://savannah.gnu.org/bugs/?25348
** Also affects: screen via
http://savannah.gnu.org/bugs/?25348
Importance: Unknown
Status: Unknown
--
running applications at startup does
It's still valid. Upstream Screen (now git, not cvs:
http://git.savannah.gnu.org/gitweb/?p=screen.git) has a number of new
features, and is shaping up to be pretty stable at this point. The main
gating factor for the next release right now is a massive amount of
documentation that needs doing (none
Unfortunately, no (and I'm an upstream co-maintainer). As I said, it's
pretty much just the docs, but there's a _lot_ of work to do there.
There are a couple people who volunteered to do the docs, but I haven't
seen anything out of them, so I'll have to find out where they're at. My
primary focus i
Yeah; at the moment I need to ascertain what the status is for the
existing volunteers on that, though. There are other sources for
volunteers, too, should it become clear that I need to find some others.
I sent a mail to them just recently, and am waiting to hear back.
I personally don't care whe
** Bug watch added: GNU Savannah Bug Tracker #22146
http://savannah.gnu.org/bugs/?22146
** Also affects: screen via
http://savannah.gnu.org/bugs/?22146
Importance: Unknown
Status: Unknown
--
Increase MAX_WINMSG_REND constant from 16 to 80
https://bugs.launchpad.net/bugs/315871
Yo
David, that's really a separate issue and should get a separate report
(but I can confirm the same behavior on Intrepid, though showkey doesn't
work for me).
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you
TERM=screen screen is _never_ good advice (unless you're running "screen
-m" directly inside of a screen session). Also, if TERM=screen screen
fixes your problem, then your problem had nothing to do with this bug,
which is specifically that some terminals send ^@ screen, rather than
the usual ^? or
hggdh, did you even read the thread? dpkg has everything to do with this
issue. In particular, Debian's own custom version of "install-info"
(part of the dpkg package) was the problem. That said, I understand
Debian's moved to GNU's install-info, and I'm actually surprised that
the problem doesn't
** Bug watch added: GNU Savannah Bug Tracker #25573
http://savannah.gnu.org/bugs/?25573
** Also affects: screen via
http://savannah.gnu.org/bugs/?25573
Importance: Unknown
Status: Unknown
--
show encoding feature
https://bugs.launchpad.net/bugs/286810
You received this bug notifi
Still experiencing this on Intrepid. I hadn't been worrying about it
because I wasn't using SCIM often enough to make it worth having
enabled; however, I've been needing it again lately, and the symptoms
are severe and annoying, to the point that the desktop is on the border-
line of usable. Even s
*** This bug is a duplicate of bug 66104 ***
https://bugs.launchpad.net/bugs/66104
** This bug has been marked a duplicate of bug 66104
[Gutsy] scim: input freezes in various applications under XIM mode
--
Input ignored when switching workspaces, closing windows...
https://bugs.launchpad.
*** This bug is a duplicate of bug 66104 ***
https://bugs.launchpad.net/bugs/66104
Thanks for the swift response, Arne.
I managed to find the core report, which at least has some suggested
workarounds. Switching from "scim" to "scim-immodule" seems to have
fixed it for so far (for 30 seconds'
*** This bug is a duplicate of bug 66104 ***
https://bugs.launchpad.net/bugs/66104
Arne, well, this issue report is now a duplicate, so I don't believe you can
"resolve" this report.
This issue will be resolved when the core report is resolved; at this time, the
problem still exists as of In
I'm fairly confident it isn't; in some locales, the @ will definitely be
ignored (relative to surrounding alphabetic chars?). The output of
"locale" will hopefully clarify what is being used (the LC_COLLATE value
should be the important one).
--
'sort' does not correctly sort non-latin utf-8 enco
Hi Julián,
If the problem is that synaptic needs to set the proxy environment
variables for wget, then I'm not sure why you've reassigned the bug to
wget, as there's nothing to do in the wget package. If, instead, you're
recommending that wget respect Gnomish proxy settings, then that would
be a l
I'm only using Jaunty, and can't seem to find a install-info package
there; but given that the core issue (documentation not matching
reality) is resolved already, and based on this new statement, I'd
consider it closed. (Also, the coreutils bit should probably already
have been closed, right?)
--
** Changed in: coreutils (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: dpkg (Ubuntu)
Status: Confirmed => Fix Committed
--
man pages suggest info pages that don't exist.
https://bugs.launchpad.net/bugs/38538
You received this bug notification because you are a member of
Public bug reported:
1. Right-click on the clock applet
2. Choose "Adjust Date & Time"
3. Attempt to change the time
The time in the three input fields (hour, minute, second) continues to
update every second, overwriting attempts to change it, making it
impossible to set the time.
** Affects: gn
Edgy Eft. This bug does not occur in Dapper Dan (which I run at work).
--
Can't edit the time in clock-applet
https://launchpad.net/bugs/55932
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Adjusting the minutes field (which is what I've been primarily testing) with
the up or down arrow controls seems effective: just not typing it in.
Some combinations of activating the arrow controls and then adjusting via
typing seem to be effective.
--
Can't edit the time in clock-applet
https:
Public bug reported:
When NTP support is not installed, checking "Synchronize clock..." gives
the message about needing to install NTP support, but does not offer to
do so, nor give instructions as to the appropriate packages to install.
This in edgy (2.15.91-0ubuntu2)
** Affects: gnome-panel (U
Public bug reported:
A user just posted to #ubuntu the regex
'[ugoa]*([-+=]([rwxXst]*|[ugo]))+', asking for an explanation.
The regex appears in the chmod manpage, in isolation, without the
remotest explanation (or even an explanation that it is, in fact, a
regex). A path-expression-type version
problem would be with time-admin, not clock-applet.
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: gnome-panel => gnome-system-tools
--
clock-panel no longer installs NTP support
https://launchpad.net/bugs/55988
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
problem would be with time-admin, not clock-applet.
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: gnome-panel => gnome-system-tools
Status: Needs Info => Unconfirmed
--
Can't edit the time in clock-applet
https://launchpad.net/bugs/55932
--
ubuntu-bugs mailing list
ubuntu-bugs@
Attached is a debdiff that implements the "other" solution (fixing the
references in the manpages from "info " to "info coreutils ").
The debdiff also includes a fix for bug #55991.
--
man pages suggest info pages that don't exist.
https://launchpad.net/bugs/38538
--
ubuntu-bugs mailing list
u
(debdiff that addresses this may be found attached to bug 38538)
--
Ugly, redundant and confusing regular expression in chmod manpage
https://launchpad.net/bugs/55991
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Hi foolishchild,
Yeah, I understand you're point. And you're probably right (though,
IIRC, Fedora Core uses the "info coreutils ls" version, which is why I
did it that way: also, I thought it was closer to the upstream's
intentions, but on closer investigation I don't believe that any
longer).
Ho
Okay, I found the problem.
GNU's install-info (ginstall-info) sees both direntries and installs
them both. Debian's just uses the top one. Sounds like the bug should be
assigned to dpkg (containing Debian's install-info).
** Also affects: dpkg (Baltix)
Importance: Untriaged
Status: Unco
(adding /Baltix/'s dpkg was not intentional...)
--
man pages suggest info pages that don't exist.
https://launchpad.net/bugs/38538
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Never mind the debdiff on bug 38538: it looks like that fix may go in a
different direction.
Here's a debdiff for just this fix.
--
Ugly, redundant and confusing regular expression in chmod manpage
https://launchpad.net/bugs/55991
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Bug watch added: Debian Bug tracker #180127
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180127
** Also affects: dpkg (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=180127
Importance: Unknown
Status: Unknown
--
man pages suggest info pages that don't exist.
--
jstest SEGFAULTs with usb joystick
https://launchpad.net/bugs/45930
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Source patch accepted and uploaded. It'll be in 1ubuntu2.
** Changed in: joystick (Ubuntu)
Status: Confirmed => Fix Released
--
jstest SEGFAULTs with usb joystick
https://launchpad.net/bugs/45930
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/l
Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.
** Changed in: ubiquity (Ubuntu)
Status: Unconfirmed => Rejected
--
Installer crash of Ubuntu Dapper Drake desktop for powerpc
https://l
Public bug reported:
This is on edgy, with brand new version 2.15.2-0ubuntu3.
Previously, editing this field simply failed to work... now, attempting
to edit the field crashes (the bug report dialog comes up).
Simply select the contents of the minutes field and retype it; or
backspace over the c
Seems to be assertion failure (at least when run by hand from terminal):
Here's the full stderr output:
/usr/share/themes/IndustrialTango/gtk-2.0/gtkrc:29: error: invalid identifier
`xthickness', expected valid identifier
10614: arguments to dbus_message_iter_init() were incorrect, assertion "me
What version do you have installed?
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed => Needs Info
--
Wrong Spanish translations
https://launchpad.net/bugs/56592
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Never mind... thought this was fixed for edgy, but I just reproduced it
in 0.6.3-2ubuntu3. Note that (at least for me), the "A" in
"desconectatado" was not capitalized.
** Changed in: network-manager (Ubuntu)
Status: Needs Info => Confirmed
--
Wrong Spanish translations
https://launchpad.
Translations look to be correct in the source package for network-
manager. Needs to be updated in the language packs, which are known to
be outdated.
** Also affects: language-pack-gnome-es-base (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
** Changed in: language-pack-gnome-es-ba
1 - 100 of 923 matches
Mail list logo
