** Changed in: fonts-noto (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fonts-noto in Ubuntu.
https://bugs.launchpad.net/bugs/1930695
Title:
Noto Fonts (without color emoji) break non-color
It shouldn't be Expired, but Confirmed. The bug's great age doesn't contribute
a fix.
(It no longer affects me. I dumped Gnome, and Ubuntu, on the desktop.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.ne
It doesn't matter where you move the directory to, if it can't be
stat(2)'d then it's a POSIX violation and breaks programs. The example
of a user running rsync on their home directory doesn't mean that's the
only situation that should work.
--
You received this bug notification because you are
Martin Pitt wrote:
> status: Triaged → Fix Released
So if this is considered the fix should we now raise bugs on all the
user-space programs that are disgruntled to find root can't stat .gvfs
as part of detecting it's a mount-point that shouldn't be crossed?
--
You received this bug notifi
So can rsync --one-file-system, find, etc., now stat the inode to know
it's another filesystem and not attempt to descend?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/225361
Title:
.gvfs can't b
"Fit page height" isn't always the case; depends on the aspect ratio of
the page and the window.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/877429
Title:
Manual resize of windo
Public bug reported:
Maximise evince with an A4 PDF, hit Best Fit, page fills vertical space,
much horizontal space empty. I now have to manually resize the evince
window to be narrower until the waste is tolerable. It would be nice if
evince itself let me ask it to minimise its window for the c
Yes, a friend with 11.04 confirms it's still readily apparent and easily
testable in a gnome-terminal.
** Changed in: vte (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to vte in Ubuntu.
h
As I stated in comment #4 above, this bug was fixed upstream. Ubuntu
10.10 seems fine; the bug's fixed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/234158
Title:
URL-related menu items don't a
rsync isn't trying to include .gvfs even with the -x option. It along
with find(1), etc., has to be able to do some things with .gvfs to even
work out it is the mount point of another filesystem and shouldn't be
descended into further. Those things fail in a way that they never
should with Unix s
valgrind still reports problems on 10.04, like jumping based on
uninitialised memory, but I can't get this particular problem to
trigger, no.
--
yelp crashed with SIGSEGV
https://bugs.launchpad.net/bugs/231051
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
I've obtained gnome-applets_2.30.0.orig.tar.gz and
gnome-applets_2.30.0-0ubuntu2.diff which I think are 10.04's. The
original code is as above when I opened the bug although the line
numbers are slightly different. The diff doesn't change them in any
way. 12_modem_applet_waitpid_fix.patch still
So, are we instead to raise a bug on every program and script that
doesn't expect a brain-damaged response due to ~/.gvfs? And then expect
the maintainers of those programs to work around the brain damage? E.g.
`alsa force-reload' causes `lsof: WARNING: can't stat() fuse.gvfs-fuse-
daemon file sy
Also easily re-created following my above instructions on 8.10, gnome-
terminal 2.24.1.1-0ubuntu1, libvte9 1:0.17.4-0ubuntu1 by someone else on
their machine, so it should be Confirmed.
--
`tput init' works inconsistently in gnome-terminal, but not xterm, etc.
https://bugs.launchpad.net/bugs/2511
Re-opening it because I think the required information was provided on
2008-08-16; the bug is present in Intredpid Alpha 3.
** Changed in: vte (Ubuntu)
Status: Invalid => Confirmed
--
`tput init' works inconsistently in gnome-terminal, but not xterm, etc.
https://bugs.launchpad.net/bugs/
> sudo chmod -R 700 /home/prophet
Hasn't that just made every file under there writable and executable?
--
When I login, I receive and error that the permissions are wrong for the file
.dmrc
https://bugs.launchpad.net/bugs/209464
You received this bug notification because you are a member of U
Actually, the bug was perfectly valid and was fixed upstream. They then
decided to change the title and the issue the bug was tracking and later
decided that this second issue wasn't a bug.
http://bugzilla.gnome.org/show_bug.cgi?id=385695#c13
--
URL-related menu items don't appear if pointer is
Why is this bug closed? Disabling polling should seem to do just that,
stop the frequent polling. I don't see why it should stop things
working when the user initiates the action; surely a one-off poll
should be done then. And the "WARNING **: Error getting media type"
diagnostic is very confus
I guess that's a pro forma comment because there's sufficient
information here, it's just neither you nor I have the time to raise it
upstream. Closing this bug means anyone looking to help out won't pop
along and raise it upstream for us.
--
gnome-terminal is Always 80x24. No global or per-pro
fuse-utils version 2.7.2-1ubuntu2 has a debian/fuse.conf that's
identical to my /etc one, i.e. everything commented out, so perhaps
you're right about the survival from an older release.
--
~/.gvfs causes various errors
https://bugs.launchpad.net/bugs/225361
You received this bug notification be
Nikolaus wrote:
> > https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/225361/comments/11
> > I understand this configuration of FUSE has been chosen because of
> > security concerns, as opposed to using its allow_users or allow_root
> > options.
>
> This is not a valid concern. In Ubuntu, allow
Phillip Susi wrote:
> That is really just a contributing factor, not the problem. The
> problem is that people are having utilities fail when they run into
> .gvfs because root can't access it ( and this is by design, not a bug
> ).
It is a bug in that, under Unix, by design, that should *never*
Just to be clear, mounting .gvfs somewhere other than $HOME doesn't
solve the problem this bug's covering IMO, which is that the filesystem
breaks the Unix norm that root can stat anything.
--
~/.gvfs causes various errors
https://bugs.launchpad.net/bugs/225361
You received this bug notification
The issue I raised in bug #260459, which was marked as a duplicate of
this one, was seen in 8.04, yes. In that bug report, it says "Ubuntu
8.04, gnome-panel 1:2.22.2-0ubuntu1.1.". But perhaps it's a different
issue and not a duplicate after all?
--
window list → bug in flashing effect
https://b
In my opinion, this doesn't reall give enough information to confirm
that the behaviour isn't down to user error. For example, on the second
machine the cut-and-pasted output of
for u in A B C; do ls -ld /home/$u{,/.gvfs}; df /home/$u/.gvfs; id
$u; done
would be useful.
--
Superuser canno
** Attachment added: "valgrind-logs-gnome-help.tar.gz"
http://launchpadlibrarian.net/18397609/valgrind-logs-gnome-help.tar.gz
--
yelp crashed with SIGSEGV
https://bugs.launchpad.net/bugs/231051
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug
Ubuntu 8.04, yelp 2.22.1-0ubuntu2.8.04.3.
On doing `gnome-help info:groff' the window appears correctly. Clicking
"Introduction" gives a SIGSEGV in strlen(). It's very consistent
behaviour. Attached is valgrind log.
** Changed in: yelp (Ubuntu)
Status: Incomplete => Confirmed
--
yelp
A little more info based on bug #260459 and its screenshot. The button
doesn't have to be flashing for this to occur. Once the flashing has
stopped and it reaches its steady `orange' state the lack of redraw when
a notify button or window iconising frame animation has passed over it
can still occ
Setting to New rather than Invalid based on
https://wiki.ubuntu.com/Bugs/Status If it's a duplicate, I'd welcome
knowing the other bug number, as normal.
** Changed in: gnome-panel (Ubuntu)
Status: Invalid => New
--
Iconised window button in gnome-panel gets corrupted when iconising anot
Hi Pedro, if it's a duplicate then can it be set as such rather than
Invalid so the other bug number is specified so I'm subscribed and can
follow things. Thanks. (I did look for gnome-panel bugs like this
before opening a new one but found nothing.)
--
Iconised window button in gnome-panel ge
** Attachment added: "gnome-panel_corruption.png"
http://launchpadlibrarian.net/17019184/gnome-panel_corruption.png
--
Iconised window button in gnome-panel gets corrupted when iconising another
window
https://bugs.launchpad.net/bugs/260459
You received this bug notification because you are
Public bug reported:
Binary package hint: gnome-panel
Ubuntu 8.04, gnome-panel 1:2.22.2-0ubuntu1.1.
On occasion, when iconising a window using Alt-F9 the black rectangle
animation that follows causes corruption on an existing button for a
window in the gnome-panel, see attached gnome-panel_corru
Hi Sam, my `global' in the bug's title means `not per-profile for a
single user', not `for all gnome-terminals across all users', so
although that solution may work for you, I have other users on this
machine so it isn't suitable. And files under /usr/share aren't
intended to be edited by a user
Public bug reported:
Binary package hint: gnome-terminal
Ubuntu 8.04, gnome-terminal 2.22.1-0ubuntu2.
xterm and other terminals I've tried correctly handle the standard `ESC
[ 8' and `ESC [ 4' escape sequences to alter the size of the terminal
window.
# Sets terminal to 100x40 characters.
Hi Sam, thanks for the pointers. The first isn't suitable because it's
editing a file that isn't intended to be edited by the user and also
changes the size for all users on the machine, not just me! :-) The
second shows others are having the same issue but there's no solution to
have per-profi
Hi Pedro, Thanks, I found
https://wiki.ubuntu.com/Bugs/Responses#Needing+testing+in+the+development+release
and followed the instructions there.
Under qemu using Intredpid Alpha 3 with gnome-terminal 2.23.4.2-0ubunut2
and libvte9 1:0.16.14-1ubuntu1, I can re-produce the bug. The attached
screensh
Hi Pedro, sorry, I wasn't clear. The ^[ seen in the single quotes in my
examples is a literal escape character typed as `Ctrl-V Escape'. If
xterm is giving `^[[18t' back then that suggests a circumflex and open
bracket have been given. Try
echo -n '@[18t' | tr @ \\033; sleep 1; echo
inste
Hi Pedro, Sorry I have only one machine here and it's running 8.04. I
suppose I could try the Alpha CD under qemu or something.
BTW, is this a correct use of the Incomplete status? I gave a very full
description of how to produce the problem in 8.04 but if it remains
Incomplete for four weeks t
Hi CalcProgrammer1, you're being a bit unclear. "I WANT others to
access my home directory" -- is that for reading the files in it or
creating and deleting files too? If the latter, then I don't know of a
workaround since my suggestion above, cd && chmod go-w . .dmrc, removes
write access for oth
Public bug reported:
Ubuntu 8.04, gnome-terminal 2.22.1-0ubuntu2, libvte9 1:0.16.13-1ubuntu1.
Using tput(1) to send the terminal's terminfo init string to
gnome-terminal, and hence vte as I understand it, gives inconsistent
results. It often fails to initialise the terminal back to its
defaults.
Given it's /usr/lib/gnome-keyring/gnome-keyring-ask displaying the
dialogue box I'm guessing gnome-keyring is the right package.
** Changed in: gnome-keyring (Ubuntu)
Sourcepackagename: openssh => gnome-keyring
--
gnome-keyring asks for passphrase for plain `ssh-add -l'
https://bugs.launchpad.ne
It may have originally been confirmed and triaged but surely it's normal
to respond to a `It looks like it's recently been fixed, please check'
request. To not do so might mislead people into thinking it has indeed
been fixed. That is not spamming.
--
Superuser cannot access ~/.gvfs folder whe
Interesting. There's a couple of differences in the .gvfs inode between
the two of us. Your perms are 0700, mine are 0500. Your access time is
today but your modify and change aren't, all three of mine are the same
value. Do you have anything mounted on .gvfs, if not, perhaps it's just
a normal
This is an up to date 8.04 i386.
$ sudo strace -e trace=lstat64 stat /home/ralph/.gvfs
lstat64("/home/ralph/.gvfs", 0xbfe8be54) = -1 EACCES (Permission denied)
stat: cannot stat `/home/ralph/.gvfs': Permission denied
Process 30706 detached
$
I think the problem still exists.
> what about --exclude=~/.gvfs ?
I don't think most shells will expand the tilde when it's not at the
start of a word like that.
$ echo --exclude=~/foo
--exclude=~/foo
$
The problem here isn't that the issue can't be worked around, typically
adding an --exclude or several as Chris
I'd argue that, based on https://wiki.ubuntu.com/Bugs/Importance, this
bug's Importance should be Medium. As described in the duplicate I
raised, things like automatically checking the success of a daily tar(1)
now fails because it always exits with a non-zero status instead of only
rarely:
For ~
Public bug reported:
Binary package hint: gnome-terminal
Ubuntu 8.04, gnome-terminal 2.22.1-0ubuntu2.
Take a URL in a gnome-terminal, the pointer can be moved over it, the
URL is underlined, and mouse button 3 will bring up a context menu with
Open Link, etc.
However, if that same URL is approa
The error message should, from reading the source of gdm
2.20.6-0ubuntu1, say
"User's $HOME/.dmrc file is being ignored. This prevents the default
session and language from being saved. File should be owned by user and
have 644 permissions. User's $HOME directory must be owned by user and
not w
Confirming as asharin has also experienced the problem.
** Changed in: gdm (Ubuntu)
Status: New => Confirmed
--
When I login, I receive and error that the permissions are wrong for the file
.dmrc
https://bugs.launchpad.net/bugs/209464
You received this bug notification because you are a
Switch to watching the new Gnome bug. Hope that's the right thing to
do. Couldn't see how to add two Gnome bug watches.
** Changed in: gnome-terminal
Bugwatch: GNOME Bug Tracker #342921 => GNOME Bug Tracker #533522
Status: Fix Released => Unknown
--
Blinking cursor can not be deact
Changing from Invalid to Confirmed. I'm assuming some bot changed it to
Invalid based on the Gnome bug status, hopefully it'll leave it alone
now. But journeying into the realms of the Gnome community made me
remember why I'm glad Ubuntu came to exist; it's a more polite society.
;-) Anyway, I'
Gnome have accepted this change was a mistake. See
http://bugzilla.gnome.org/show_bug.cgi?id=342921 which I've just link
this bug too. However, they're being sensitive flowers and are deleting
comments from the bug report. Some were from Jay L. T. Cornwall
willing to provide a patch he'd alread
** Also affects: gnome-terminal via
http://bugzilla.gnome.org/show_bug.cgi?id=342921
Importance: Unknown
Status: Unknown
--
Blinking cursor can not be deactivated anymore
https://bugs.launchpad.net/bugs/188732
You received this bug notification because you are a member of Ubuntu
Desk
This bug should clearly be confirmed. As well as Thomas Nybergh
spotting the same problem, I also raised a duplicate, bug #227724.
** Changed in: gvfs (Ubuntu)
Status: New => Confirmed
--
Superuser cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You rece
Just a point on the .fonts.conf provided above. `rgba' is being set to
`rgb'. This will make coloured pixels be used around the edges of black
text on a white background; it won't stick to just gray pixels. That
may be OK for an LCD but if you want grayscale, set rgba to `none'
instead. Many t
I understand this is a Gnome change, but they've applied logic a step
too far. There's a big physical difference between a one-pixel-wide
cursor used in Gtk+ text areas, etc., and a one-character-filled-
rectangle used by gnome-terminal. The former I want to blink because it
can be hard to spot.
>Status: Incomplete => Invalid
As an aside, maybe a bug status meaning `valid bug already fixed in
later version' would be nice. Invalid suggests that it wasn't a bug,
which isn't true. And having a separate status would let them be
separated in the statistics.
--
gnome-help Suffers g
Sigh, should have thought of that. OK, I've got a friend with 8.04 to
look and it works fine. The gnome-help line above doesn't segfault but
politely complains. And the Help on Dominosa menu item runs `yelp
/usr/share/sgt-puzzles/help/dominosa.html' which works fine. Sorry for
the noise.
--
g
Public bug reported:
Binary package hint: yelp
Ubuntu 7.10, yelp 2.20.0-0ubuntu3.
This command is done when choosing Help -> Help on Dominosa in the
`dominosa' program of package sgt-puzzles 7446-1, or any other program
in that package.
$ gnome-help ghelp:///usr/share/sgt-puzzles/gnome/help
I've also found that rxvt 1:2.6.4-12 responds correctly to the two
printf(1)s above. So gnome-terminal is so far the only one that
doesn't.
--
gnome-terminal is Always 80x24. No global or per-profile setting available.
https://bugs.launchpad.net/bugs/217167
You received this bug notification be
This is on a standard Ubuntu 7.10, gnome-terminal 2.18.2-0ubuntu1.
As you can't cut and paste those echo(1)s above, here's some printf(1)
equivalents.
$ printf '\x1b[8;40;100t'
$ printf '\x1b[4;200;200t'
--
gnome-terminal is Always 80x24. No global or per-profile setting available.
htt
Public bug reported:
Ubuntu 7.10. The escape sequence "Esc [ 1 8 t" is meant to make the
terminal reply with the height and width of the current window
characters. It's handled in vte-0.16.9/src/vteseq.c, line 3865. The
output on gnome-terminal is different to the xterm from xterm-229-1.
Here'
Sufficient detail provided that it can go straight to confirmed. Hope
that's OK.
** Changed in: vte (Ubuntu)
Status: New => Confirmed
--
"Esc [ 1 8 t" Response doesn't match xterm.
https://bugs.launchpad.net/bugs/208837
You received this bug notification because you are a member of Ubunt
There are other similar faults where the response is incorrect in that
same function.
^[[13t response should be ^[[3;x;yt but is ^[[x;yt.
^[[14t response should be ^[[4;h;wt but is ^[[h;wt.
^[[19t response should be ^[[9;h;wt but is ^[[h;wt.
On a similar note, although ^[[20t is handl
I've just followed Jonathan Fritz's path. Having freshly installed 7.10
I did System -> Preferences -> Main Menu to see what could be changed.
Finding Applications -> Other -> Gnome Font Viewer I thought it sounded
useful and ticked it. Selecting the newly appeared menu item show a
minimised butt
Regarding the importance of fixing this bug: As it stands, a new user
who has installed from a 6.10 CD can't get online using their modem and
diagnosing the problem isn't straightforward for 90% of those users. It
may be that they can use some other system or OS to get online and seek
advice, but
I've just installed Ubuntu 6.10 and have hit this problem having used
System -> Administration -> Networking to configure the modem.
/etc/ppp/peers/ppp0 doesn't contain noauth, unlike a much older version
of Ubuntu I used to use, probably 5.04. Consequently, pppd complains
during `ifup ppp0' as de
Setting status to Confirmed; James Stansell is clearly experiencing the
same problem in 5.04 and 5.10 Live Preview.
** Changed in: system-tools-backends (Ubuntu)
Status: Unconfirmed => Confirmed
--
Modem volume not turned off by AT&FH0M0.
https://launchpad.net/bugs/18331
--
desktop-bugs
Confirming as at least part of the original problem, grep on non-
existant file, exists.
** Changed in: gdm (Ubuntu)
Status: Unconfirmed => Confirmed
--
fails to install -- possibly due to implicit dependency on
default-display-manager?
https://launchpad.net/bugs/29389
--
desktop-bugs
gdm's postinst has code like
DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager
case "$1" in
configure)
if grep "/usr/bin/gdm" $DEFAULT_DISPLAY_MANAGER_FILE; then
echo "/usr/sbin/gdm" > $DEFAULT_DISPLAY_MANAGER_FILE
fi
;;
esac
which d
For reference, the text in 49134 was got on a fresh 6.06 desktop i386
install with a `apt-get upgrade'.
--
fails to install -- possibly due to implicit dependency on
default-display-manager?
https://launchpad.net/bugs/29389
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lis
Public bug reported:
Binary package hint: gdm
Did `apt-get upgrade' on recent 6.06 and gdm was to be upgraded to
2.14.6-0ubuntu2.1. Output included error from grep:
Setting up libfreetype6 (2.1.10-1ubuntu2.1) ...
Setting up gdm (2.14.6-0ubuntu2.1) ...
grep: /etc/X11/default-display-manager: No
72 matches
Mail list logo
