No argument of any sort was made in #8, specious or otherwise; only an
observation.
And placing profiley stuff into bashrc slows down the shell (as if
it's not slow enough already!)
Adding things to PATH that you want access to in all your interactive
shells, belongs in the file sourced by
FWIW, the workaround I've been using for some time now is:
if [ \( x$COLORTERM = xgnome-terminal -o x$COLORTERM = xTerminal -o
x$COLORTERM = xxfce4-terminal \) -a x$TERM = xxterm ]
infocmp xterm-256color /dev/null 21; then
TERM=xterm-256color
fi
in my .bashrc or what have you. The
(the line wrapped for the first if line; that needs to be a single
line to work)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/778801
Title:
TERM unconditionally set to xterm,
According to the discussion on the Gnome VTE bug linked, calling
vte_terminal_set_emulation won't work either, unless it happens to be
recognized as a supported emulation mode. xterm-256color isn't, so
this solution wouldn't work.
There doesn't seem to be an obvious, clean way to fix the problem
Added vte, until it's clearer which of xfce4-terminal and vte should fix
this (as I said, though, it looks to me like only vte _can_ fix it,
though upstream seems unwilling).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in
Note that gnome-terminal isn't effected, since gnome-terminal doesn't
give the user the option to specify the TERM value to begin with. This
is generally a desirable feature to have, though.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
The fix is now in place for the Ubuntu Natty, and it looks like upstream
is going to include it for future versions of vte. Nice to finally be
able to use gnome-terminal with screen and tmux without glitchy graphics
:)
Note: at least one person had difficulty reproducing this on their
system
(Please note: the debdiff above is now out-of-date; but can still be
used, and then just replace the file in debian/patches.)
(There is also now a merge proposal against https://bazaar.launchpad.net
/~ubuntu-desktop/vte/ubuntu/changes, which does use the updated patch.)
--
You received this bug
Minor fix to patch; addresses the same problem in a few cases apparently
not exercised by the automated script.
** Patch added: Revised patch.
https://bugs.launchpad.net/ubuntu/+source/vte/+bug/246701/+attachment/1759318/+files/lp246701_scroll_region_updates.patch
--
You received this bug
Found the source of the problem. The vte_terminal_process_incoming
function from vte.c keeps track of a bounding box of cells to be
invalidated, and uses that to invalidate cells at points such as after
all input has been processed, or when a large enough cursor jump is made
(to avoid letting the
** Patch added: debdiff against Maverick's vte
https://bugs.launchpad.net/ubuntu/+source/vte/+bug/246701/+attachment/1750780/+files/vte_0.26.0-0ubuntu3.debdiff
--
Change Scroll Region and display glitch
https://bugs.launchpad.net/bugs/246701
You received this bug notification because you
Same issue on a Compaq CQ60. Only missing the brightness keys, no
others; were working fine in Jaunty. No messages from xev or
acpi_listen.
--
[Karmic] Brightness fn keys lost functionality (multiple laptops)
https://bugs.launchpad.net/bugs/406515
You received this bug notification because you
Public bug reported:
Steps to reproduce:
1. Open a fresh gnome-terminal. There must be lines below the prompt to which
text has never yet been written.
2. Enter the command: $ printf '\033[L'
(the INSERT LINE sequence will be sent to gnome-terminal)
3. gnome-terminal crashes.
My
I'm currently using these three, as unsetting just GPG_AGENT_INFO no
longer seems sufficient.
unset GPG_AGENT_INFO
unset SSH_AUTH_SOCK
unset GNOME_KEYRING_SOCKET
(Not all of these necessarily relate to seahorse? I dunno, I just fix
what breaks for me. :)
--
Passphrase dialog doesn't
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
(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
Desktop
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
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
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 screen
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
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
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
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
Desktop Bugs, which is subscribed to vte
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
** 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
Desktop Bugs, which is subscribed
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
Desktop
** 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
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
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
Desktop Bugs, which
** 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
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
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
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
(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
Desktop Bugs,
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
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
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
As previously mentioned, it's not nothing happens. It's accepting
input, but hiding it. Just type the password and hit return.
--
terminal wont accept typed input when prompting for password
https://bugs.launchpad.net/bugs/121739
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 121161 ***
https://bugs.launchpad.net/bugs/121161
Hi, and thanks for reporting this bug.
You've neglected to mention which version of gnome-terminal you're
running, but actually, I think the more pertinent question is what
version of libvte you're running.
For me, this happens in Feisty as well, though I suspect it depends on
the version of screen running (potentially, remotely)--or possibly bash
--rather than of gnome-terminal.
In order for such a thing to occur, bash must request screen to send it
mouse button events, and screen must in turn
*** This bug is a duplicate of bug 121161 ***
https://bugs.launchpad.net/bugs/121161
Hi!
This appears to be the same bug as bug 121161, so I'm marking this as a
duplicate and closing it out.
This issue has been fixed in the latest release of libvte in Gutsy.
** This bug has been marked a
If this is only a broblem for people using beryl or compiz, it seems
very likely the fault lies with those, rather than gnome-terminal.
--
Terminal displays as a blank window
https://bugs.launchpad.net/bugs/115100
You received this bug notification because you are a member of Ubuntu
Desktop
Sebastien, I don't find this a remotely simple feature request.
Implementing this would take a very significant amount of planning, IMO.
--
Ability to drag files out of the Terminal onto the Desktop or into other
Applications
https://bugs.launchpad.net/bugs/124251
You received this bug
Thanks for your report. Your idea might get more attention and have the
possibility of being implemented if you submit a specification for it.
First check whether the idea is already registered [WWW]
https://launchpad.net/ubuntu/+specs, and if so, contact the
specification's drafter about your
** Changed in: gnome-terminal (Ubuntu)
Status: New = Confirmed
--
gnome-terminal and others crash due to g_thread_init() not being called
https://bugs.launchpad.net/bugs/123306
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
Gerald, note that X-ing out of a terminal because of some program may
not be the best way to deal with that: if the program is ignoring SIGINT
(the ^C signal), it could be ignoring SIGHUP (the lost terminal
signal) as well; better to open another terminal, find the offending
process's pid, and use
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Wishlist
--
UI should allow easier access to editing title of terminal
https://bugs.launchpad.net/bugs/122601
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
Running under QEMU, I confirmed the bug in Feisty, and then after
upgrading to Gutsy, confirmed that it appears to be working correctly.
--
scim-chewing will crash GNOME terminal.
https://bugs.launchpad.net/bugs/121161
You received this bug notification because you are a member of Ubuntu
Desktop
Wasn't fighting for whose fault it was; was fighting whether it was a
really bug, and whether infocmp's output really was meant to describe
modified function keys. Now that that's been established, I think the
change should be relatively straightforward; assuming xterm has changed
its behavior
Note that commands that take passwords typically turn of local echo,
meaning your typing is in fact read as input, but you don't see it on
the screen. This is to protect you from people being able to see your
password by peering over your shoulder. Please verify that su really
isn't taking your
Alex, Izzy, I'm not sure where you get the idea that xterm should
generate those sequences. infocmp gives \EO5P for function key 25, not
for control-function key 1. Infocmp does not and has never had a
mechanism for specifying modifiers to special keys. It looks to me that
MC is in the wrong.
** Changed in: gnome-screensaver (Ubuntu)
Sourcepackagename: None = gnome-screensaver
Status: New = Confirmed
--
Resume from hibernation shouldn't ask for my password with automatic login
https://bugs.launchpad.net/bugs/58715
You received this bug notification because you are a member of
)
Sourcepackagename: None = shared-mime-info
Importance: Undecided = Wishlist
Assignee: (unassigned) = Micah Cowan
Status: New = Incomplete
--
soundfonts (*.sf2) get wrong MIME Type video/x-msvideo
https://bugs.launchpad.net/bugs/59840
You received this bug notification because you
Izzy, the second paragraph you wrote is rather uninformative. Many of
the characters being generated are being stripped out, using the method
you've described. Use cat instead.
Note that for many terminals, the sequences generated will depend
greatly upon whether the terminal is in keypad
(Ubuntu)
Assignee: (unassigned) = Micah Cowan
Status: New = Incomplete
--
gnome-terminal crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/121630
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome
Never mind; apport's retrace is useless, the one you originally gave
with your bug is great.
--
gnome-terminal crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/121630
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
#10 0xb77789a6 in IA__g_signal_emit_valist (instance=0x80baaa0, signal_id=8,
detail=0, var_args=0xbfd559b0 �Yտ\026)
at /build/buildd/glib2.0-2.13.5/gobject/gsignal.c:2209
...
#11 0xb7778d99 in IA__g_signal_emit (instance=0x80baaa0, signal_id=8,
detail=0) at
Is ssh-loop some sort of custom script, and what do the arguments
{build,orion,mountain} signify?
--
gnome-terminal crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/121630
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact
«Micah, since the purpose of terminfo is to recognize what xterm does,
it seems to me that suggesting that xterm should follow what terminfo
says it does is putting the cart before the horse. terminfo doesn't
describe what xterm should do, it (should) describe what xterm *does*.»
Xterm does, in
Okay, thanks Alex, that clarifies things quite a lot. I guess Xterm and
its sisters have repurposed the kfX strings. It might help for
terminfo(5) to clarify this situation (even though it really isn't
ncurses' responsibility to do so, since that's not the original meaning
of those names; still,
Did any terminal ever actually have 64 function keys, as the existence
of kf0-kf63 suggests?
I doubt it. And I had been wondering about that. :)
Seems to me, though, if terminfo has 'em in there _specifically_ for
usages like xterm's, they're without excuse for not saying something
about how
** Changed in: nautilus-cd-burner (Ubuntu)
Sourcepackagename: None = nautilus-cd-burner
Status: Unconfirmed = Confirmed
--
Cannot Burn CD/DVD on HL-DT-ST DVD-RW GWA-4082N
https://bugs.launchpad.net/bugs/57055
You received this bug notification because you are a member of Ubuntu
Desktop
Please specify the versions of the libvte-common and gnome-terminal
packages installed on your system.
What exactly do you mean by history scrolling? Do you mean that it
scrolls through bash's command line history?
gnome-terminal should never send _any_ escape codes for mouse actions,
unless it
Quite probably, this bug is related to bug 120046 (of which I marked
this as a duplicate, and then changed my mind, as the described problems
may be sufficiently different).
--
Last line disappears when switching tab
https://bugs.launchpad.net/bugs/121173
You received this bug notification
A similar bug, bug 121173, is claimed to be fixed in the very latest
update to libvte in Gutsy. Áron couldn't produce this anyway in Gutsy,
but if it was still present but required specific environments to
reproduce, it _may_ have been resolved by that same fix...
--
gnome-terminal mouse scroll
Is that with the brand-new libvte that was released for Gutsy yesterday?
--
gnome-terminal mouse scroll error when using tabs
https://bugs.launchpad.net/bugs/120046
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-terminal in
** Changed in: nautilus (Ubuntu)
Sourcepackagename: None = nautilus
--
Reboot/Shutdown hangs after connecting to a shared folder
https://bugs.launchpad.net/bugs/57885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for nautilus in
Here is valgrind output (xfce4-terminal did not crash for this run, but
valgrind seems to have found plenty to complain about). The test was to
type the text, echo 今日は、田中さん (Hello, Mr Tanaka), twice, then exit
via Ctrl+D.
** Changed in: vte (Ubuntu)
Sourcepackagename: gnome-terminal = vte
I have noticed the same problem with scim-anthy (for Japanese input), as
well. This used to work, but when I don't remember. I don't see any
recent package updates to either gnome-terminal, libvte-common or scim.
I don't seem to be able to reliably reproduce it, however, it appears at
this time
** This bug has been marked a duplicate of bug 120046
gnome-terminal mouse scroll error when using tabs
** This bug is no longer a duplicate of bug 120046
gnome-terminal mouse scroll error when using tabs
--
Last line disappears when switching tab
https://bugs.launchpad.net/bugs/121173
BTW, I checked to see if the U+823a2c0 could have been some strange
combination of actual Unicode characters involved in the text I typed;
this does not appear to be the case.
--
scim-chewing will crash GNOME terminal.
https://bugs.launchpad.net/bugs/121161
You received this bug notification
Probably, it's at least an interaction between gnome-terminal and your X
driver; where the bug lies is hard to say. I'm adding xserver-xorg-
video-ati so that between the two, perhaps we can find the bug in one or
both. Perhaps its a duplicate of bug 34435, though AFAICT the symptoms
are different
Ctrl-S controls the flow... by pausing all output on the terminal
(Ctrl-Q is used to resume output).
The output of the stty commands given above actually are not entirely
accurate, because bash changes the state of the tty just before, and
after, running a command. If you were to run stty against
It seems extremely likely to me that this is a bug with vte, rather than
vim, so I'm reassigning.
vim is expecting the same sequences it has always expected from xterm and
xterm-emulating ttys.
xterm normally sends ESC [ A for cursor up; when keypad send mode is on
(vim activates this mode), it
I can't reproduce this. Any further hints to help reproduce this?
--
gnome-terminal mouse scroll error when using tabs
https://bugs.launchpad.net/bugs/120046
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-terminal in ubuntu.
*** This bug is a duplicate of bug 2066 ***
https://bugs.launchpad.net/bugs/2066
** This bug has been marked a duplicate of bug 2066
Unable to load any usable fontset
--
Missing charsets in String to Fontset conversion - confirm kill
https://bugs.launchpad.net/bugs/576
You received this
It's not vim that emits these errors, it must be some library it's
using. There may be something missing from your desktop environment.
Are you running under a gnome session, or do you use Xubuntu?
I couldn't find the string device event controller in the Gtk+
sources, but I'm forwarding this to
** Changed in: gtk+2.0 (Ubuntu)
Sourcepackagename: vim = gtk+2.0
--
GTK assertion `g_path_is_absolute (filename)' failed
https://bugs.launchpad.net/bugs/102002
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gtk+2.0 in ubuntu.
--
Confirming for the screensaver, as while Ken is right that it's not a
bug with the screensaver when considering its original intended use, it
is a bug with the screensaver in consideration of the use for which we
have chosen it. It may not be Gnome's responsibility to fix, but it is
ours, and the
** Tags added: needs-i386-retrace
--
[apport] gnome-session crashed with SIGSEGV
https://bugs.launchpad.net/bugs/113694
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-session in ubuntu.
--
desktop-bugs mailing list
: (unassigned) = Micah Cowan
Status: Unconfirmed = Needs Info
--
x
https://bugs.launchpad.net/bugs/113445
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gedit in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
But, surely there must have been /something/ in the configuration that
caused metacity not to work, since blowing it away got it working again?
--
window manager crashes/does not work
https://bugs.launchpad.net/bugs/105390
You received this bug notification because you are a member of Ubuntu
Actually, just to be sure we know what the problem was, rather than
close the bug out yet, if you still have the old, moved-out-of-the-way
.gnome2/ directory around, could you maybe tar it up and attach it? «tar
xjf gnome2.tbz moved-gnome2/» should do.
--
window manager crashes/does not work
Just so you know, shirish, the DISPLAY=:0 is a guess, and is only
likely to work if that user is the first one to have logged into a
graphical desktop. You can get the actual value by looking at your
current .xsession-errors, the line that says:
/etc/gdm/PreSession/Default: running:
shirishag75 wrote:
ok would try that, just to inform the number of things which were tried so
everybody knows.
actually the command which u gave in the morning DISPLAY=:0 metacity
--replace use to give a warning
shirish @ubuntu $ Window Manager manager warning found in
Hm. I believe this is so that when the second user's session ends, the
first user, when his X session is made the current one, will be required
to log in. I agree that it would be beneficial to prevent the
screensaver from actually using up CPU unless it's the currently visible
one, but I think
Yeah, okay: you're right, that seems wrong. Confirmed for Feisty Edgy.
--
scripts running from desktop : $PWD = /home/user
https://bugs.launchpad.net/bugs/103144
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for nautilus in ubuntu.
Confirmed for Feisty Fawn.
I believe opening that dialog also queries the printer, which may be
part of the problem; but in any case, it should bring the window up
immediately, and then perhaps display some helpful querying the
printer progress bar or what have you, so that the user is provided
Hi, and thanks for taking the time to submit this bug report. I've
confirmed that this does occur; however, I do not believe it's a bug. It
should probably be prioritized as Wishlist. I'm guessing this is not
how upstream will want to go, but I'll let someone else make that
decision.
The PWD is
** Changed in: gnome-games (Ubuntu)
Status: Unconfirmed = Confirmed
--
[Edgy] gnome-games doesn't have proper license info
https://launchpad.net/bugs/62398
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Also affects: xorg (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
No keyboard previews
https://launchpad.net/bugs/58083
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
I can't reproduce this problem. I was able to move two folders into the
wastebasket by right-clicking in the Tree view.
Please provide a more detailed explanation of exactly what you tried
(exact filenames, what the current directory is, what the path buttons
list at the top was).
** Changed in:
I tested using version 2.14.3-0ubuntu1
--
Dapper: Nautilus crashes when deleting a folder from the side-pane
https://launchpad.net/bugs/61503
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: Ubuntu
Sourcepackagename: None = gnome-panel
--
edgy: translation error in dutch
https://launchpad.net/bugs/61158
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
** Changed in: gaim (Ubuntu)
Status: Unconfirmed = Confirmed
--
separated spelt incorrectly in usage string
https://launchpad.net/bugs/61157
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Hear, hear. This is a major reason why I use xpdf.
** Changed in: evince (Ubuntu)
Status: Unconfirmed = Confirmed
--
Evince takes a long time to render pages in PDF documents
https://launchpad.net/bugs/61161
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Assigning to gnome-screensaver, although it could be a session manager
thing.
** Changed in: Ubuntu
Sourcepackagename: None = gnome-screensaver
--
Can't lock desktop.
https://launchpad.net/bugs/57160
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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:
1 - 100 of 113 matches
Mail list logo
