[Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
** Changed in: f-spot (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/885324/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170164] Re: can't switch input method at all
** Also affects: ibus Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1170164 Title: can't switch input method at all To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1170164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170164] Re: can't switch input method at all
** Description changed: Normally gnome-terminal allows the user to switch the input method by pressing a special key combination. Sometimes gnome-terminal gets into a state where it seems to ignore the special key combination for switching the input method in ibus - it is permanently locked in the default input method for English. There is no clear pattern of usage or trigger for when it happens. 1. The problem is not solved by resetting the terminal using the menu Terminal - Reset, or Terminal - Reset and Clear 2. The problem is also not solved even by starting a new gnome-terminal from the menu, File - Open Terminal - Default 3. However, using the command-line to start a new terminal with the factory disabled does make input method switching work again: gnome-terminal --disable-factory but doing this obviously loses all the session information in the previous gnome-terminal. + 4. Also, when the problem occurs, opening a new tab re-enables the input mode to be switched in the new tab as well as in the original tab. However, the problem usually re-occurs soon in the original tab. This has been happening in all versions of Ubuntu since 10.04 until 12.04.02 precise, with gnome-terminal up to and including version 3.4.1.1-0ubuntu1 and ibus version 1.4.1-3ubuntu1 This is a really annoying bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1170164 Title: can't switch input method at all To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1170164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170164] [NEW] can't switch input method at all
Public bug reported: Normally gnome-terminal allows the user to switch the input method by pressing a special key combination. Sometimes gnome-terminal gets into a state where it seems to ignore the special key combination for switching the input method in ibus - it is permanently locked in the default input method for English. There is no clear pattern of usage or trigger for when it happens. 1. The problem is not solved by resetting the terminal using the menu Terminal - Reset, or Terminal - Reset and Clear 2. The problem is also not solved even by starting a new gnome-terminal from the menu, File - Open Terminal - Default 3. However, using the command-line to start a new terminal with the factory disabled does make input method switching work again: gnome-terminal --disable-factory but doing this obviously loses all the session information in the previous gnome-terminal. This has been happening in all versions of Ubuntu since 10.04 until 12.04.02 precise, with gnome-terminal up to and including version 3.4.1.1-0ubuntu1 and ibus version 1.4.1-3ubuntu1 This is a really annoying bug. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-terminal input-method ** Description changed: Normally gnome-terminal allows the user to switch the input method by pressing a special key combination. Sometimes gnome-terminal gets into a state where it seems to ignore the special key combination for switching the input method in ibus - it is - permanently locked in the default input method for English. + permanently locked in the default input method for English. There is no + clear pattern of usage or trigger for when it happens. 1. The problem is not solved by resetting the terminal using the menu Terminal - Reset, or Terminal - Reset and Clear 2. The problem is also not solved even by starting a new gnome-terminal from the menu, File - Open Terminal - Default 3. However, using the command-line to start a new terminal with the factory disabled does make input method switching work again: gnome-terminal --disable-factory but doing this obviously loses all the session information in the previous gnome-terminal. This has been happening in all versions of Ubuntu since 10.04 until 12.04.02 precise, with gnome-terminal up to and including version 3.4.1.1-0ubuntu1 and ibus version 1.4.1-3ubuntu1 This is a really annoying bug. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1170164 Title: can't switch input method at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1170164/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383700] Re: eog uses too much memory
Hey bug-watch-updater, this is a real bug in Eye of GNOME, so quit trying to hide the existence of this bug from the devs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/383700 Title: eog uses too much memory To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/383700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383700] Re: eog uses too much memory
rv unexplained change by robot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/383700 Title: eog uses too much memory To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/383700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 986275] Re: eog segmentation faults on standard input
Did you read mine? I gave all the details necessary to reproduce the bug in eog on Oneiric. I cannot run apport, and I do not think that is necessary to reproduce the bug . Precise is not yet out of beta testing. Why is it considered the current series in that state? The beta doesn't even boot on my hardware. ** Changed in: eog (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/986275 Title: eog segmentation faults on standard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/986275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 986275] Re: eog segmentation faults on standard input
If the bug exists only in the earlier versions, it would still be valid. Oneiric and Natty are still supported; Precise is not yet out of beta testing. ** Changed in: eog (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/986275 Title: eog segmentation faults on standard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/986275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 583056] Re: Assertion error (r == n_visible_rows) in gtk_file_system_model_sort causes applications to crash
I'm still seeing this bug with gtk2+2.24.6 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/583056 Title: Assertion error (r == n_visible_rows) in gtk_file_system_model_sort causes applications to crash To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/583056/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383700] Re: eog uses too much memory
** Tags added: eog memory -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/383700 Title: eog uses too much memory To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/383700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 172416] Re: eog determines image type from filename
True, but if you want to view lots of images with a responsive user- interface, feh is more than 10 times faster than shotwell. If you start shotwell from the command-line with a large number of images as arguments, then type Space as fast as you can (or increase your keyboard's default autorepeat rate) to load the next image, shotwell takes about 1/3 second to move to the next image. With feh, it takes about 30 milliseconds. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/172416 Title: eog determines image type from filename To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/172416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 986275] [NEW] eog segmentation faults on standard input
Public bug reported: Inadequate validation of standard input: $ echo extremelybuggy | eog - (eog:32094): GRIP-CRITICAL **: register_internal: assertion `GRIP_IS_GESTURE_MANAGER (manager)' failed Segmentation fault This bug has been confirmed to exist in eog-3.2.1 in Oneiric and earlier versions in Maverick and Natty. ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: crash eog -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/986275 Title: eog segmentation faults on standard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/986275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 855637] Re: eog cannot rotate tif image pi/2
feh can do rotations by pi/2, and is overall much faster than eog and has fewer serious bugs. $ apt-get install feh $ feh -dZF image Type '' to rotate pi/2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/855637 Title: eog cannot rotate tif image pi/2 To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/855637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 172416] Re: eog determines image type from filename
It's been 5 years and still no sign of this bug being fixed. The eog project looks nearly dead. feh doesn't have this bug, is more featureful and runs much much faster than eog. $ apt-get install feh $ mv image.jpg image.gif $ feh -dZF image.gif -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/172416 Title: eog determines image type from filename To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/172416/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 383700] Re: eog uses too much memory
It's been 3 years with no sign of this bug being fixed. feh is similar to but better than eog. It can load large images ok, runs much much faster than eog, and is more featureful. $ apt-get install feh $ feh -dZF Image-Grand_central_Station_Outside_Night_2.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/383700 Title: eog uses too much memory To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/383700/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 275213] Re: Can't resize larger than 10000 pixels
** Tags added: f-spot ** Summary changed: - Can't resize larger than 1 pixels + Can't resize larger than 1 pixels in f-spot -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/275213 Title: Can't resize larger than 1 pixels in f-spot To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/275213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/885324/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 275213] Re: Can't resize larger than 10000 pixels
@pmjdebruijn Is there an actual sane use-case for this? Panoramas, spectroscopic images, astronomical images, cam/cad images, etc etc. I use images larger than this regularly in some of these applications. There is no upper bound on the dimensions of images that users may need to create. f-spot should not be assuming one. It is better if f-spot can catch exception on memory allocation failure. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/275213 Title: Can't resize larger than 1 pixels To manage notifications about this bug go to: https://bugs.launchpad.net/f-spot/+bug/275213/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 3923] Re: Cannot change default character encoding
Chris Coulson, neither of the comments which you appear to dislike are simply +1 votes; rgaobr said he doesn't know how to use the .diff patch file, and Haarvard Ostermann wrote that the workarounds are neither user friendly nor reliable, both of which are perfectly legitimate comments on a bug tracker. To rgaobr, you need to download gnome-terminal-dev which contains the source code for the software, as well as the .diff patch file. To use the patch, change directory cd gnome-terminal and type patch -p1 ../default_encoding-2.13.91.diff (or whatever path you downloaded the patch file). -- Cannot change default character encoding https://bugs.launchpad.net/bugs/3923 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 567331] Re: [nautilus] preferences dialog too tall and unusable in VESA video mode
Thanks, Clement. I'd like to clarify I'm not reporting a bug regarding lack of support in Mint for more than VESA resolution on this pc; this pc's chipset is so new, nobody has got linux+X running ok on it yet, but I know the bug is being worked on by kernel and xorg devs. -- [nautilus] preferences dialog too tall and unusable in VESA video mode https://bugs.launchpad.net/bugs/567331 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 476092] Re: nautilus edit'preferences dialog too big for 1024x576 UNR display
Another suggested fix: Automatically reduce gnome's default font-sizes on smaller displays. For example, using 8pt fonts (changed in the control centre from the default 12pt) for application font, desktop font, window title font, fixed width font makes this dialog (and other oversize ones too) fit completely on an 800x600 display. For me this seems a cleaner solution than adding a scrollbar to the dialog or sliding the window up while holding down Alt. By the way, I searched for nautilus preferences related bugs on Launchpad's Mint section but for some reason it didn't bring up this bug report, so I made a new bug report https://bugs.launchpad.net/linuxmint/+bug/567331 and was then told it was a duplicate of this one. -- nautilus edit'preferences dialog too big for 1024x576 UNR display https://bugs.launchpad.net/bugs/476092 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
