[Bug 1930695] Re: Noto Fonts (without color emoji) break non-color emoji in QT applications
** 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 emoji in QT applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1930695/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail
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.net/bugs/225361 Title: .gvfs can't be stat'd by root causing backup tools to fail To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail
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 a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/225361 Title: .gvfs can't be stat'd by root causing backup tools to fail To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail
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 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 be stat'd by root causing backup tools to fail To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: .gvfs can't be stat'd by root causing backup tools to fail
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 be stat'd by root causing backup tools to fail To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/225361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877429] Re: Manual resize of window required after Best Fit
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 window required after Best Fit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/877429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 877429] [NEW] Manual resize of window required after Best Fit
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 current size selected, e.g. 50%. It would do a better job than my manual resize and be quicker. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- 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 window required after Best Fit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/877429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 251105] Re: `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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. https://bugs.launchpad.net/bugs/251105 Title: `tput init' works inconsistently in gnome-terminal, but not xterm, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/251105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 234158] Re: URL-related menu items don't appear if pointer is on bottom pixel of URL
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 appear if pointer is on bottom pixel of URL -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: other users don't have access to .gvfs
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 semantics for root. You're just seeing other symptoms of the same underlying problem; FUSE's configuration not allowing root to do anything, as it normally can. But this bug report isn't the place for discussion, I suspect. I just wanted to clarify that there isn't a further bug. -- 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: other users don't have access to .gvfs -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 231051] Re: yelp crashed with SIGSEGV
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, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 18572] Re: modem_applet: waitpid()'s return value causes wedging.
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 applies OK with an offset of -15 lines. So the problem remains in the code. My concern over the patch remains, detailed in #3 above. waitpid() is clearly being wrongly used. That can be fixed without further test results. Then the underlying problem may come to light once the code processes waitpid's response properly. -- modem_applet: waitpid()'s return value causes wedging. https://bugs.launchpad.net/bugs/18572 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: ~/.gvfs causes various errors
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 system /home/peter/.gvfs' to appear. -- ~/.gvfs causes various errors https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 251105] Re: `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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/251105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 251105] Re: `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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/251105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 209464] Re: When I login, I receive and error that the permissions are wrong for the file .dmrc
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 Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 137830] Re: [gutsy] sound-juicer can not see audio CD in drive
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 confusing to the normal user. Luckily, Google found this bug for me so I know the workaround, but it shouldn't be necessary. -- [gutsy] sound-juicer can not see audio CD in drive https://bugs.launchpad.net/bugs/137830 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to sound-juicer in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 234158] Re: URL-related menu items don't appear if pointer is on bottom pixel of URL
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 on bottom pixel of URL https://bugs.launchpad.net/bugs/234158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217167] Re: gnome-terminal is Always 80x24. No global or per-profile setting available.
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-profile setting available. https://bugs.launchpad.net/bugs/217167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: ~/.gvfs causes various errors
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_root is by default enabled in /etc/fuse.conf. In my untouched 8.04 /etc/fuse.conf, both mount_max and user_allow_other are commented out, meaning the file has no active options. So even if gvfs does not use --allow-root, a malicious user can simply mount a filesystem of his choice manually and with --allow-root. It's my understanding that Ubuntu have set up automounting of user filesystems (non-FUSE ones) so a malicious user can have root mount their concocted filesystem anyway, so I'm not sure what the current troublesome, non-Unix, FUSE configuration is protecting us from? -- ~/.gvfs causes various errors https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: ~/.gvfs causes various errors
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 because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: ~/.gvfs causes various errors
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* happen to a process running as root. The utilities in question shouldn't be messing with .gvfs in the first place, so a simple solution is to move it somewhere they aren't going to run into it. Sorry, that's not possible. As root, it's entirely valid, and not uncommon, for me to run `find / ...' which will descend and find .gvfs wherever to decide to move it to. Nikolaus Rath and S B, take a look at my earlier comment 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. However, I'm not sure those concerns remain valid given Ubuntu automatically mounts the filesystems on a USB flash drive I insert, and I doubt every piece of filesystem code in the kernel is robust against maliciously concocted corrupt filesystems. -- ~/.gvfs causes various errors https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: ~/.gvfs causes various errors
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 because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 98637] Re: window list → bug in flash ing effect
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://bugs.launchpad.net/bugs/98637 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 cannot access ~/.gvfs folder when mounted
https://bugs.launchpad.net/bugs/225361
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is the registrant for gvfs.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 231051] Re: yelp crashed with SIGSEGV
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 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 231051] Re: yelp crashed with SIGSEGV
** 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 assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 98637] Re: window list → bug in flash ing effect
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 occur. -- window list → bug in flashing effect https://bugs.launchpad.net/bugs/98637 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 260459] Re: Iconised window button in gnome-panel gets corrupted when iconising another window
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 another window https://bugs.launchpad.net/bugs/260459 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 260459] [NEW] Iconised window button in gnome-panel gets corrupted when iconising another window
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_corruption.png showing the top of the screen. The XChat button should be tinted `current window' orange but slivers of it corresponding the rectangles that passed across it have been rendered in `non-current window' gray. This has happened in various Ubuntus since at least 5.04. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- 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 a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 260459] Re: Iconised window button in gnome-panel gets corrupted when iconising another window
** 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 a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 260459] Re: Iconised window button in gnome-panel gets corrupted when iconising another window
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 gets corrupted when iconising another window https://bugs.launchpad.net/bugs/260459 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 258775] [NEW] gnome-terminal doesn't resize on `ESC [ 8' or `ESC [ 4' despite vte's resize_window()
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. $ echo -n '@[8;40;100t' | tr @ \\033 # Sets terminal to 200x200 pixels. $ echo -n '@[4;200;200t' | tr @ \\033 gnome-terminal doesn't, which is wrong. This is despite vte's vteapp.c' resize_window() which tries to handle both escape sequences. I suspect there's something lacking in gnome-terminal to make use of this. Not supporting these escape sequences means gnome-terminal, the default Ubuntu terminal, is unsuitable for some legacy console apps, and it also means it's not possible to work around bug #217167. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- gnome-terminal doesn't resize on `ESC [ 8' or `ESC [ 4' despite vte's resize_window() https://bugs.launchpad.net/bugs/258775 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217167] gnome-terminal is Always 80x24. No global or per-profile setting available.
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 or admin. of the machine. I think this bug is probably really two. The lack of configurability over the terminal size, with per-profile settings, means I can't, for example, quickly open a new log-file monitoring terminal, or a new IRC client one. A user can match profiles to uses rather than just appearance, e.g. a dark blue background is log-file monitoring with a small font size but that needs a particular terminal size too. The second issue is gnome-terminal's lack of compliance with the `ESC [ 8' and `ESC [ 4' sequences. This is a hard, concrete bug; not a `wishlist' item. I've opened a second bug for that, bug #258775, so this bug can concentrate on the lack of per-profile setting. -- gnome-terminal is Always 80x24. No global or per-profile setting available. https://bugs.launchpad.net/bugs/217167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 251105] Re: `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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 screenshot has three red Ys in the first `tput init' output and two in the second, none in the third. This is a lower frequency than with 8.04 but I suspect this is just a side effect of using qemu as I think the bug is a timing issue in VTE's handling of escape sequences. With qemu, a whole load of XYs would draw on the screen at once. Natively, I can see them appearing one by one. ** Attachment added: tput_init_bug.png http://launchpadlibrarian.net/16868212/tput_init_bug.png -- `tput init' works inconsistently in gnome-terminal, but not xterm, etc. https://bugs.launchpad.net/bugs/251105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 217167] Re: gnome-terminal is Always 80x24. No global or per-profile setting available.
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-profile default sizes. I think the fact that the `ESC [ 8' escape sequence doesn't work in gnome-terminal despite vte's resize_window() code also suggests this is a valid bug. -- gnome-terminal is Always 80x24. No global or per-profile setting available. https://bugs.launchpad.net/bugs/217167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 208837] Re: Esc [ 1 8 t Response doesn't match xterm.
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 instead which can be cut-and-pasted. This uses tr(1) to turn the `@' into an ASCII ESC. -- 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 Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 251105] Re: `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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 then the next step is to make it Invalid. That doesn't seem right. -- `tput init' works inconsistently in gnome-terminal, but not xterm, etc. https://bugs.launchpad.net/bugs/251105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 209464] Re: When I login, I receive and error that the permissions are wrong for the file .dmrc
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 others to your home directory. Could you instead have a subdirectory of $HOME, give that permissions 777, and use that as the directory that all and sundry can fiddle with? -- 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 Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 251105] [NEW] `tput init' works inconsistently in gnome-terminal, but not xterm, etc.
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. Here's a command to show the desired behaviour. tr \\0 \\012 /dev/zero | head -100 | while read f; do tput setf 4; printf X; tput setf 0; printf Y; done It gives an alternating sequence of red X's and black Y's. Replacing the `setf 0', which is setting the foreground colour to black, with `init', as in tr \\0 \\012 /dev/zero | head -100 | while read f; do tput setf 4; printf X; tput init; printf Y; done gives many red Y's, i.e. the `tput init' is *sometimes* failing to have effect. I suspect it's a subtle timing issue where vte is examining the time between characters in escape sequences to determine if they are, in fact, an escape *sequence*. Note, xterm(1), and other terminal emulators I've tried, give consistent results, the `tput init' is always interpreted the same way. Here's a couple of bits of information that may be useful to confirm it isn't something odd on my local setup. $ echo $TERM xterm $ tput init | od -c 000 033 [ ! p 033 [ ? 3 ; 4 l 033 [ 4 l 033 020 021 $ This bug causes legacy programs that work consistently on other Unix and Linux systems to have display glitches with varying impact depending on when vte decides not to honour the request. The red/black XYs is just my simplification. :-) ** Affects: vte (Ubuntu) Importance: Undecided Status: New -- `tput init' works inconsistently in gnome-terminal, but not xterm, etc. https://bugs.launchpad.net/bugs/251105 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 242666] Re: gnome-keyring asks for passphrase for plain `ssh-add -l'
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.net/bugs/242666 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 when mounted https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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. -- Superuser cannot access ~/.gvfs folder when mounted https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 directory now in your system? Anyway, I am up to date with the 8.04 packages and I still get the problem. -- Superuser cannot access ~/.gvfs folder when mounted https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 Hines points out, but that it shouldn't be neccessary; the basic Unix premise that root can stat the inode has been broken. I assume that FUSE's allow_users and allow_root options aren't being used because they'd allow a plain user to DoS root. However, isn't a plain user already allowed to plug in a USB flash drive with a filesystem on it and have the system mount that? Do all filesystems rigorously detect hierarchy loops, etc., caused by a malicious user tweaking the filesystem's structures manually before the system kindly mounting it for them; something normally only root could do? -- Superuser cannot access ~/.gvfs folder when mounted https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 ~/.gvfs to not follow normal Unix semantics is a major pain. As root, one can normally tar up a user's home directory, perhaps as part of a daily backup regime, without problems. That's the point of running it as root. Since the introduction of ~/.gvfs: $ sudo tar cf /dev/null .gvfs .bash_profile tar: .gvfs: Cannot stat: Permission denied tar: Error exit delayed from previous errors $ echo $? 2 $ So checking the exit status of tar for any backups problems now fails. Every day. I'd argue tar is pretty core and it's having a medium or severe impact, as outlined under Medium. -- Superuser cannot access ~/.gvfs folder when mounted https://bugs.launchpad.net/bugs/225361 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 234158] [NEW] URL-related menu items don't appear if pointer is on bottom pixel of URL
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 approached from below, a pixel at a time, and the pointer stops moving when the underline appears, and then button 3 is pressed, the context menu is lacking the URL related items. This is despite the visual feedback of the URL being underlined. Similarly, if the URL is approached from above, moving the pointer down a pixel at a time until the underline appears, and then the pointer is move back up a pixel so the underline goes, the context menu *contains* the URL related items even though the visual feedback said it shouldn't because of the lack of underlining. It seems the coordinates used to determine when to underline are one-off from the calculation of when the context menu should contain URL-related items. There's also a one-off error left/right as opposed up/down. I found this because I got fed up of having an underlined URL yet the menu not containing Open Link. I was sure I hadn't moved the mouse in the meantime, and I hadn't; I was just on the bottom row for pixels for the URL. So it's not theoretical but bites in real life. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- URL-related menu items don't appear if pointer is on bottom pixel of URL https://bugs.launchpad.net/bugs/234158 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 209464] Re: When I login, I receive and error that the permissions are wrong for the file .dmrc
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 writable by other users. That seems to match what the code checks and be clear. It's warning that the .dmrc file could be modified by someone other than the user. To avoid this, do cd chmod go-w . .dmrc to remove `write' permission for `group' and `other'. -- 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 Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 209464] Re: When I login, I receive and error that the permissions are wrong for the file .dmrc
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 member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188732] Re: Blinking cursor can not be deactivated anymore
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 deactivated anymore https://bugs.launchpad.net/bugs/188732 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188732] Re: Blinking cursor can not be deactivated anymore
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've tracked down Jay Cornwall; http://www.jcornwall.me.uk/2008/04/hardy-heron-and-the-blinkin-terminal/ ** Changed in: gnome-terminal (Ubuntu) Status: Invalid = Confirmed -- 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 Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188732] Re: Blinking cursor can not be deactivated anymore
** 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 Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188732] Re: Blinking cursor can not be deactivated anymore
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 already prepared to revert this change. Olav deleted them; see my comment #46. Olav is insisting that reverting isn't an option and someone must write a new patch that provides a three-way option, Blink, Don't blink, Use system default. In lieu of a useful change from Gnome, perhaps Jay Cornwall's patch can be examined to see if Ubuntu can pick it up directly? -- 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 Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225361] Re: Superuser cannot access ~/.gvfs folder when mounted
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 received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190848] Re: font in terminal does not resemble font in preview
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 thanks for the .fonts.conf being provided by John Buncher in the first place. -- font in terminal does not resemble font in preview https://bugs.launchpad.net/bugs/190848 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 188732] Re: Blinking cursor can not be deactivated anymore
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. The latter is easy to spot and its blinking is a distraction, just like animated ads or blink text on a web page; and we block those! I see why it was set to Invalid, this isn't a bug but a `feature' imposed by Gnome. But it is a bug because they made it based on them both being `cursors' without regard for their different physical appearance, so I'm setting this bug to Confirmed. There seems to be a considerable body of people that had the two cursors with different blink settings. ** Changed in: gnome-terminal (Ubuntu) Status: Invalid = Confirmed -- 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 Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225644] [NEW] gnome-help Suffers g_filename_to_uri() assertion failure.
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/C/index.html (gnome-help:6482): GLib-CRITICAL **: g_filename_to_uri: assertion `filename != NULL' failed Segmentation fault (core dumped) $ $ file /usr/share/sgt-puzzles/gnome/help/C/index.html /usr/share/sgt-puzzles/gnome/help/C/index.html: HTML document text ** Affects: yelp (Ubuntu) Importance: Undecided Status: New -- gnome-help Suffers g_filename_to_uri() assertion failure. https://bugs.launchpad.net/bugs/225644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 225644] Re: gnome-help Suffers g_filename_to_uri() assertion failure.
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. -- gnome-help Suffers g_filename_to_uri() assertion failure. https://bugs.launchpad.net/bugs/225644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 225644] Re: gnome-help Suffers g_filename_to_uri() assertion failure.
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_filename_to_uri() assertion failure. https://bugs.launchpad.net/bugs/225644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217167] Re: gnome-terminal is Always 80x24. No global or per-profile setting available.
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 because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 217167] Re: gnome-terminal is Always 80x24. No global or per-profile setting available.
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. https://bugs.launchpad.net/bugs/217167 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 208837] Re: Esc [ 1 8 t Response doesn't match xterm.
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 handled correctly in responding with the icon's label, the response to ^[[21t also outputs an `L' when it should be using a lowercase `l'. The above URL and xterm confirm lowercase `l' for 21 is the correct behaviour. -- 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 Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 208837] Re: Esc [ 1 8 t Response doesn't match xterm.
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 Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 208837] [NEW] Esc [ 1 8 t Response doesn't match xterm.
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's the correct, xterm, behaviour. $ echo -n '^[[18t'; sleep 1; echo ^[[8;24;80t $ And the gnome-terminal: $ echo -n '^[[18t' ; sleep 1; echo ^[[24;80t $ There should be an 8; before the height of 24. This in theory allows the string to be echoed back to the terminal to restore this size in the future. As well as xterm providing different behaviour, I've found various references on the Internet, e.g. http://invisible- island.net/xterm/ctlseqs/ctlseqs.html, which also suggest vte is wrong. ** Affects: vte (Ubuntu) Importance: Undecided Status: 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 Ubuntu Desktop Bugs, which is subscribed to vte in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 163451] Re: Unable to run GNOME Font Viewer in Ubuntu 7.10 from menu
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 button in the panel saying starting which disappears after a bit. The user is left confused and puzzled and has to waste time investigating. If it doesn't make sense to run it from a menu then it shouldn't be there in the menu choices for the user to trip over. It would be nice if some effort can be made to see if it can be removed without impacting its use an a Nautilus action. ** Changed in: gnome-control-center (Ubuntu) Status: Invalid = Confirmed -- Unable to run GNOME Font Viewer in Ubuntu 7.10 from menu https://bugs.launchpad.net/bugs/163451 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 82378] Re: [network-admin] creates /etc/ppp/peers/ppp0 without noauth
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 described above. The vanilla 6.10 install has left me with gnome-system-tools 2.15.5-0ubuntu2. ** Changed in: gnome-system-tools (Ubuntu) Status: Needs Info = Confirmed -- [network-admin] creates /etc/ppp/peers/ppp0 without noauth https://launchpad.net/bugs/82378 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 18331] Re: Modem volume not turned off by ATFH0M0.
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 ATFH0M0. https://launchpad.net/bugs/18331 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 29389] Re: fails to install -- possibly due to implicit dependency on default-display-manager?
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 mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 49134] apt-get upgrade of gdm reports default-display-manager ENOENT.
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 such file or directory * Reloading GNOME Display Manager configuration... * Changes will take effect when all current X sessions have ended. [ ok ] Setting up libpq4 (8.1.4-0ubuntu1) ... I realise the upgrade probably went OK, but the error from grep shouldn't appear. ** Affects: gdm (Ubuntu) Importance: Untriaged Status: Unconfirmed -- apt-get upgrade of gdm reports default-display-manager ENOENT. https://launchpad.net/bugs/49134 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 29389] Re: fails to install -- possibly due to implicit dependency on default-display-manager?
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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 29389] Re: fails to install -- possibly due to implicit dependency on default-display-manager?
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 doesn't check /etc/X11/default-display-manager exists before grepping it. Elsewhere, debian/* files do check /etc/X11/default-display-manager exists before reading it. debian/changelog says gdm (2.8.0.0-0ubuntu1) breezy; urgency=low * debian/postinst: - update the gdm value for default-display-manager. -- Sebastien Bacher [EMAIL PROTECTED] Wed, 15 Jun 2005 22:53:12 +0200 -- 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://lists.ubuntu.com/mailman/listinfo/desktop-bugs
