Re: [Bug 1025119] Re: Exporting photos fails due to file error
Thanks. Updating to 0.12.3 seems to have fixed it. On Mon, Jul 16, 2012 at 2:04 PM, Lucas Beeler <1025...@bugs.launchpad.net>wrote: > Hi TZ, > > I'm one of the Shotwell devs. To resolve your problem, I think you > should do two things. First, Shotwell 0.11.6 is now nearly a year old. > The current version of Shotwell is 0.12.3. So simply upgrading Shotwell > may solve your problem. You can learn more about how to upgrade here: > http://www.yorba.org/shotwell/install.html. > > If upgrading doesn't fix your problem, then we'll need some diagnostic > information about why these files are not being exported. Shotwell > includes a built-in logging facility. To learn how to enable diagnostic > logging, see the "I found a bug in Shotwell. How can I report it?" > section of the Shotwell FAQ here: > http://redmine.yorba.org/projects/shotwell/wiki/ShotwellFAQ. When > Shotwell is run with logging on, it will produce a log file that you can > attach to this ticket. > > Lucas > > ** Changed in: shotwell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1025119 > > Title: > Exporting photos fails due to file error > > Status in “shotwell” package in Ubuntu: > Incomplete > > Bug description: > I have a number of photos(roughly 20) that I want to export. Around > half of them do export, the other half fail due to file system errors. > > I retry and it is always the same files that work and same photos that > do not work. > > ProblemType: Bug > DistroRelease: Ubuntu 11.10 > Package: shotwell 0.11.6-0ubuntu0.1 [modified: > usr/share/glib-2.0/schemas/gschemas.compiled] > ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33 > Uname: Linux 3.0.0-22-generic x86_64 > ApportVersion: 1.23-0ubuntu4 > Architecture: amd64 > Date: Sun Jul 15 17:52:13 2012 > InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 > (20101007) > SourcePackage: shotwell > UpgradeStatus: Upgraded to oneiric on 2012-01-10 (187 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025119/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1025119 Title: Exporting photos fails due to file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025119] Re: Exporting photos fails due to file error
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1025119 Title: Exporting photos fails due to file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1025119] [NEW] Exporting photos fails due to file error
Public bug reported: I have a number of photos(roughly 20) that I want to export. Around half of them do export, the other half fail due to file system errors. I retry and it is always the same files that work and same photos that do not work. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: shotwell 0.11.6-0ubuntu0.1 [modified: usr/share/glib-2.0/schemas/gschemas.compiled] ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33 Uname: Linux 3.0.0-22-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Jul 15 17:52:13 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: shotwell UpgradeStatus: Upgraded to oneiric on 2012-01-10 (187 days ago) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1025119 Title: Exporting photos fails due to file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1025119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 240916] Re: can't configure display resolution (monitor, graphics card) manually in gui
I had forgotten about this yet another thing Ubuntu refuses to even provide a workaround much less fix. Some quick notes - yes I want this fixed too (actually I've abandoned Ubuntu - they will ruin notifications, but not put a refresh in the network manager which is similarly broken, nor fix it - more of the "automatic is broken but we won't give you a manual option theory). First, it isn't just monitors. My original problem was a laptop with a VIA chipset. The original driver had a few problems (mainly wiht 3d), but was usable (E-F). G or H broke it and removed the manual configuration. The VIA driver locked up constantly (no, they never fixed that), but I could use the default minimal VESA, but it was 800x600 although the bios and everything else said the screen was 1024x768. But now there was no way to tell X even to use a plain VESA mode of 1024x768 with what amounted to standard VESA monitor timings. There is no detection involved. Worse, it wasn't just removed from the distribution disk, it was removed from the repositories. If I wanted it, I would have to track down the old source and recompile from scratch. It isn't a big, complex job looking into strange driver code and hardware, it is just putting back one tiny freaking program into the repositories if not the main distro. Right now I can't tell it that my monitor is a plain, vanilla, standard VESA with resolution of 1024x768. VESA is not some complex or quirky hardware, it is a freaking standard! And Ubuntu doesn't support it. It isn't a high priority because their policy seems never to fix severely broken automatic configuration - either setup like this or ongoing like network-manager (they have time for vanity UI changes though), but at the same time rip out all the manual configuration so if your hardware is affected there is no way for you to fix it. I'm in the process of switching to Fedora (13) - it seems to be more stable, and although not everything is fixed, it has a large package library and so far they seem to be more friendly to older hardware. -- can't configure display resolution (monitor, graphics card) manually in gui https://bugs.launchpad.net/bugs/240916 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 553313] [NEW] notifyosd is still horrible in lucid beta
Public bug reported: Binary package hint: gnome-terminal I still get that horribly large fecal-dark-brown box (regardless of theme). On a netbook size screen anything is large. It stays up for far too long and there is no way to control the amount of time I can find. There is still no apparent way to bring the notifying application to front. There is no way to dismiss it - it is stuck there until it decides to disappear (at least anything I can find). There is no way to move it to a different location (I can find). ** Affects: notify-osd (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-terminal (Ubuntu) => notify-osd (Ubuntu) -- notifyosd is still horrible in lucid beta https://bugs.launchpad.net/bugs/553313 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 552555] Re: lucid upgrade terminal window too large and can't resize
It is the terminal window WITHIN update manager. My normal terminal windows use a small monofont and work very well. But there is no way I can find to change the update window's terminal screen - the fonts for the update manager follow the theme, but if I show the terminal window, it is (for me) huge white characters on a black background that would be 24x80, and might work except since there are lots of lines in the upgrade, the terminal window has to be below them so goes off-screen. -- lucid upgrade terminal window too large and can't resize https://bugs.launchpad.net/bugs/552555 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 261289] Re: Preferences option to prevent auto mounting of removable hard disks has been removed
If this is intended, then the people intending it are stupid. There are many other cases where you don't want every volume of every drive mounted (sometimes crippled like HFS or NTFS) when you insert or attach a device. If it is a lower priority issue, then it should still be a checkbox in an advanced tab, not some CLI or complex config editor tool entry. Unless your "intent" is to make Gnome as bad as linux in that you have to use regedit to override settings. -- Preferences option to prevent auto mounting of removable hard disks has been removed https://bugs.launchpad.net/bugs/261289 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 130786] Re: [gutsy] NetworkManager Feature Request - manually trigger ssid scan
This goes back to Gutsy and is not yet fixed in Karmic. Supposedly it is fixed in the Gnome branch but is a wontfix here? It is still stupid that I have to disable and enable wireless just to see my access point when I can watch windows, two cell phones, Mac OSX and everything else find it in under 2 seconds. Try holding your breath for 20 seconds (use a stopwatch or a seconds display). But that is only sometimes and if I activate the applet - it still takes 2 minutes to "automatically" find an AP even when it is completely disconnected. You don't like or want to put in manual scans? THEN FIX THE AUTOMATIC SCAN! -- [gutsy] NetworkManager Feature Request - manually trigger ssid scan https://bugs.launchpad.net/bugs/130786 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 130786] Re: [gutsy] NetworkManager Feature Request - manually trigger ssid scan
This isn't adequate. I leave my computer on so it will have no network connection and be at the 120 second interval when I get to work and turn my local AP on. 20 seconds is also a long time. Just try waiting 20 seconds from now before you read the next paragraph. The only way currently is to right click and disable and reenable wireless. This is inefficient and stupid. And it isn't a driver problem. "sudo iwlist scan" ALWAYS shows the network, and it is marked auto. If I knew what the supersecret magic dbus incantation to get it to rescan, I would code it as a launcher, but it would still belong as part of the applet. -- [gutsy] NetworkManager Feature Request - manually trigger ssid scan https://bugs.launchpad.net/bugs/130786 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 240916] Re: can't configure display resolution (monitor, graphics card) manually in gui
It is horribly difficult to put back an existing manual configuration utility that was present in a recent version? That is the original solution I wanted. Fixing every possible permutation of hardware in the automatic config would be horribly difficult, but that seems to be the only thing you might be willing to do. I simply want SOME mechanism to configure my laptop, and I had one, and it went away and the replacement is broken. On Fri, Mar 6, 2009 at 3:05 AM, Sebastien Bacher wrote: > those comment about how things are urgent and have to be fixed now will > not make those fixed faster, quite the contrary if you insist on blaming > the graphical tool where the issue is also in infrastructure it's using, > nobody disagree that should be fixed but that's not as easy as you seem > to think > > -- > can't configure display resolution (monitor, graphics card) manually in gui > https://bugs.launchpad.net/bugs/240916 > You received this bug notification because you are a direct subscriber > of a duplicate bug. > -- can't configure display resolution (monitor, graphics card) manually in gui https://bugs.launchpad.net/bugs/240916 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
