[Bug 334844] Re: Totem error dialog: size makes errmsg unreadable
> do you still get the issue? > Is this still an issue for you? I still don't know how to reproduce the error, and I haven't been using totem much, so I don't really know. But isn't it clear that the cause is a hard coded constant in the source code? And the solution is to (1) come up with a better design; and (2) replacing the current hard coding with the better design. Or am I missing something obvious here... ? -- Totem error dialog: size makes errmsg unreadable https://bugs.launchpad.net/bugs/334844 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 334844] Re: Totem error dialog: size makes errmsg unreadable
> how do you start totem, is that running locally or over ssh? Locally. $ totem & > could you try on jaunty? I don't know how to reproduce the error message. Should I abruptly terminate dbus? The message seems to complain about a "dangling socket" (meaning there's a file but no one to connect to). > do you have similar issue with other software? As far as I can remember, only totem has been giving me an error in a widget that's way too small (considering the length of the error message). Again: the bug isn't the error message, but how the message is displayed. Your questions seem (to me) to aim more at finding out why the error message is there. I probably killed dbus or something equally nasty. It doesn't happen often, but it happened at least once. -- Totem error dialog: size makes errmsg unreadable https://bugs.launchpad.net/bugs/334844 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 341083] [NEW] window drag: should snap to intended (!nearest) corner
Public bug reported: In metacity you can snap-drag by holding down alt, click-dragging a window and then pressing shift. Consider the following scenario: - There are three windows, A, B and C. None overlap, A is slightly to the left of B, C slightly above B. - If you alt-drag B just enough to pick it up, then move it a little, it's going to snap such that it's edge-to-edge with both A and C. If you want to drag B to the "opposite" corner, the one furthest away from the intersection of the bottom line of C and right line of A, you're going to be dragging the window away from the place it snaps to. The window snapping away from where you're dragging it is very counter- intuitive. Wouldn't it be better if metacity snapped the window to the position that the most recent mouse motion is pointing towards? ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- window drag: should snap to intended (!nearest) corner https://bugs.launchpad.net/bugs/341083 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334307] Re: gnome-appearance-properties: remove + arrow keys = broken
> how do you delete it? If "it" is my wallpaper as it appears in the G-A-P dialog, then I delete it by hitting the Alt shortcut key (Alt+R, I think). > clicking on the delete button This is the one labeled "Remove", correct? (Just to dispel all ambiguity) As an added observation: when I remove a wallpaper, pressing leftarrow (instead of rightarrow) takes me to the last wallpaper. -- gnome-appearance-properties: remove + arrow keys = broken https://bugs.launchpad.net/bugs/334307 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 334844] Re: Totem error dialog: size makes errmsg unreadable
> could you please attach your ~/.xsession-errors file to the report? Well, I can attach some ~/.xsession-errors which happens to be mine, but it has [acm]time after 2009-03-08 10:00:00, so it's probably not the one you want. $ totem --version GNOME totem 2.24.3 $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 8.10 Release:8.10 Codename: intrepid (I run a few Jaunty packages) Also, I should probably clarify: the bug isn't the error message, but that the message is hard to read. If the error message itself is also a bug, that's cool, but shouldn't it be a distinct bug report? ** Attachment added: ".xsession-errors" http://launchpadlibrarian.net/23603614/.xsession-errors -- Totem error dialog: size makes errmsg unreadable https://bugs.launchpad.net/bugs/334844 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 334844] Re: Totem error dialog: size makes errmsg unreadable
** Attachment added: "Screenshot-Untitled Window.png" http://launchpadlibrarian.net/23145951/Screenshot-Untitled%20Window.png -- Totem error dialog: size makes errmsg unreadable https://bugs.launchpad.net/bugs/334844 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 334844] [NEW] Totem error dialog: size makes errmsg unreadable
Public bug reported: When I opened a playlist in totem, I got an error message; see the attached single-window screenshot. Based on that screenshot, take a guess as to how long you think the error message is. Here it is, it its entirety: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-hJx8vg34dm: Connection refused) Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system cras
[Bug 334307] [NEW] gnome-appearance-properties: remove + arrow keys = broken
Public bug reported: The arrow keys in gnome-appearance-properties don't work right: 1. Go to the backgrounds tab 2. Select any background 3. Remove it (this selects the next background) 4. Press rightarrow to move to the next of that (that is, deleted->next->next) 5. Observe that the *first* background becomes selected. Clearly this isn't what one expects. G-A-P should be changed so that it conforms to user expectations. (this is with GNOME version 2.24.1, built 2008-10-24, on intrepid; G-C-C is version 1:2.24.0.1-0ubuntu7.1) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- gnome-appearance-properties: remove + arrow keys = broken https://bugs.launchpad.net/bugs/334307 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 320469] Re: Evince goes to page 1 when reloading
This happens to me as well. I've attached a document for which it happens. Also, if the text in the page textbox (next to " of 11", in the toolbar) is selected when evince reloads the document, the text becomes unselected. I think that's not a good default behavior: I didn't ask for it to become deselected, why should it be? If it wouldn't be deselected, I could type in the number of the page I was at a little faster. [Should I put the page textbox behavior in a different bug report?] ** Attachment added: "Document that triggers the reported behavior" http://launchpadlibrarian.net/21654425/slides.pdf -- Evince goes to page 1 when reloading https://bugs.launchpad.net/bugs/320469 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 268412] Re: Evince - keyboard nav with arrow keys and pgup/-dn is counterintuitive
The bug is no longer. I experienced it in a pdf file generated by lilypond; it spanned two pages. It's a bunch of notes for a song that I don't hold the copyrights to. I can probably get permission to give you a copy (Poke me if you want the pdf from me), but I don't see the point. With almost the same pdf (c- and mtime being september 12th) and most definitely the same version of lilypond, but a newer evince, I see sane behavior from evince. I've generated a more minimal (and more publishable) example (1024 times the 440 Hz a-note) with intrepid-rc's lilypond, and I still see sane behavior from evince. Again, poke me. As far as I can tell, there was a bug at some point in time, but not any longer. And if you all excuse me, I'll be off chasing wild geese :) -- Evince - keyboard nav with arrow keys and pgup/-dn is counterintuitive https://bugs.launchpad.net/bugs/268412 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 268412] [NEW] Evince - keyboard nav with arrow keys and pgup/-dn is counterintuitive
Public bug reported: Binary package hint: evince The keyboard navigation in evince is very counterintuitive. When you press uparrow and downarrow, evince moves by one page. When you press page down and page up, evince scrolls down/up the current page (or jumps to the top of the next/previous page). I propose instead the following behavior: When you press page up and page down, evince jumps to the top of the next/previous page. When you press uparrow and downarrow, evince scrolls a little (a lot less than page up and page down currently). Also, note that when you cross a page boundary from cur to prev with a small movement (i.e. the arrow keys in my suggestion, or page up and page down as it is currently), it's more sensible to put the user near the bottom of the newly entered page, not the top---i.e. next to where they came from instead of far away. Here's the output of some commands (the localhost repository is apt- cacher-ng) Description:Ubuntu 8.04.1 Release:8.04 evince: Installed: 2.22.2-0ubuntu1 Candidate: 2.22.2-0ubuntu1 Version table: *** 2.22.2-0ubuntu1 0 500 http://localhost hardy-updates/main Packages 100 /var/lib/dpkg/status 2.22.1.1-0ubuntu1 0 500 http://localhost hardy/main Packages 2.20.1-0ubuntu1 0 500 http://localhost gutsy-updates/main Packages 2.20.0-0ubuntu3 0 500 http://localhost gutsy/main Packages ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- Evince - keyboard nav with arrow keys and pgup/-dn is counterintuitive https://bugs.launchpad.net/bugs/268412 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
