[Bug 554002] Re: gstreamer decoding of ac3 fails when pulseaudio device is set to surround in lucid
I didn't have this problem in Lucid, but it's now in Maverick (and that's final, not alpha or beta). -- gstreamer decoding of ac3 fails when pulseaudio device is set to surround in lucid https://bugs.launchpad.net/bugs/554002 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-good0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 532633] Re: [Master] Window Control buttons: position/order/alignment
While Jefspa Leta brings up all good points, I don't see a need to keep saying could'a would'a should'a or I told you so to Mark at this point. I do hope Mark takes this to heart for future design changes. Most critics of the change fully understand that Mark is in charge and that this isn't a democracy. But even a dictator can be open-minded to constructive feedback and provide guidelines in advance for how that should be given. At this point, let's just get together what data we can that we think will help. -- [Master] Window Control buttons: position/order/alignment https://bugs.launchpad.net/bugs/532633 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 532633] Re: [Master] Window Control buttons: position/order/alignment
Yes, Mark, if you can clarify a bit about what kind of data you will actually consider as a factor in your decision, perhaps people here can actually help you by providing that data so we can avoid arguments that just go around in circles. What are you looking for? Polls? Anecdotes? If polls, what would you like the poll options to be? If anecdotes, what specific things do you want people to test for? Believe me, most of the people here who are opposed to the change would love to be able to work with you to get you what you need to make a well-informed decision. We just need guidance on what will actually help you. So far, you haven't seemed to really take into consideration the valid criticisms that have been brought up (and, no, they haven't just been we're used to something else). You keep mentioning data, so it'd be great to know either what data you are currently collection and what userbase that consists of or what data you would like us to collect for you and how you would like that approached so that you do take it seriously. -- [Master] Window Control buttons: position/order/alignment https://bugs.launchpad.net/bugs/532633 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 532633] Re: [Master] Window Control buttons: position/order/alignment
That should say currently collecting -- [Master] Window Control buttons: position/order/alignment https://bugs.launchpad.net/bugs/532633 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 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
The problem with your Forums post is that it says this is what really happened and is, in fact, quite incorrect. Some members of the design team asked that the window controls be grouped on the left, and presented the visualisation. So it wasn't that I prefer it that way. I didn't like it initially, anticipating that it would generate a great deal of resistance. However, it does line things up nicely for work I would like us to do in future. No, Mark, the real problem is that is what the public perception of what happened is. And that matters as much as, if not more than, what really happened. The first indication we had of any part of the decision-making process was you saying in an IRC chat that you do prefer it that way. You didn't say you were initially opposed to it. Perhaps instead of focusing on minor factual clarifications, you can focus on the bit about how things could have gone? I fully respect that you're self-appointed benevolent dictator for life. I fully support your prerogative in making decisions without opening it up to a vote. It does behoove you, as a leader of an open source project that touts itself as a community-based distro, to have a certain kind of transparency in your process. You can even be secretive about it while also being transparent. A simple Wiki entry or Blueprint (or even just a quick email on a mailing list) that goes along these lines Lucid alpha users will see a small change in the button order with this latest update. I know this will take a little getting used to, but rest assured we on the design team have a good reason for changing it up, and you'll be excited to see what we put on the freed-up right side. We aren't opening this up to a voting process, but if you have legitimate concerns about the move, please let us know, and we will take them into consideration. Would that have been so difficult to do? And the major argument against it appears solely to be we're used to it here, which is important, but not overriding. Mark Mark, you're a busy guy, so I know you don't read all forum posts and brainstorms, but maybe you can take a second look at the comments in this very bug report. Comment #71 has quite an extensive list of arguments against the change, and they aren't just we're used to it here: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/532633/comments/71 I'm hoping you just skimmed over and missed that and that you aren't being deliberately obtuse. I have a lot of respect for what you've done these past five years with Ubuntu. I want to give you the benefit of the doubt here. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
People wouldn't have to second-guess your decisions if you would simply explain the reasons for your decisions. A benevolent dictatorship goes so much better when you're transparent about the process and give rational explanations for decisions instead of just making arbitrary decisions that appear to have no usability benefits, letting the community scratch their heads and try to figure out what you were thinking, and then making vague references to wanting to experiment with the right side that gets freed up. For more details on how you can not be a slave to the peanut gallery while also not experiencing this kind of unprecedented backlash with regard to your decisions, see this Ubuntu Forums thread post: http://ubuntuforums.org/showthread.php?p=8978434#post8978434 -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
Why should it be wrong to place the buttons on the left side like on Mac OS X. It isn't on the left side like Mac OS X. It's on the left side unlike Mac OS X. Here are some key differences: * On Mac OS X, the close button is still the outside button, even though the controls are on the left. * Mac OS X has always had controls on the left. They didn't suddenly move there in Snow Leopard. * Mac OS X has a universal toolbar, so the window controls aren't bunched up with the menu items. It's not just about right v. left. It's about an arbitrary change midstream that has no benefit. It's about OS X having other design decisions (not implemented in Lucid) that make a left-side control work. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 532633] Re: [light-theme] please revert the order of the window controls back to menu:minimize, maximize, close
I don't think anyone's purposes are served by approaching this as an 'or' question and dwelling on personal and pseudo-logical reasons for supporting one form or another. Some people like the previous Windows- style setup; others are fond of the left, OSX-like orientation. Well, as I explained before, the left orientation is not OS X-like. It's not just a simple matter of left and right, not to mention the button order is all messed up. As we've seen from the workaround, this issue can be addressed and changed very simply with the modification of a single key. Why not simply make this an option, just a radio button in the course of the setup or even upgrade procedures? The customizability is, itself, a selling point, a point of differentiation for Ubuntu as compared to other OSes. Ubuntu is supposed to have one application per task and, more importantly, sane defaults. Yes, customizability is part of the appeal of a Linux distro, but the sane defaults should also be a selling point. So, yeah, put the controls back on the right as they were and then have a simple radio button for people who want it on the left to put it on the left. -- [light-theme] please revert the order of the window controls back to menu:minimize,maximize,close https://bugs.launchpad.net/bugs/532633 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 538636] [NEW] gnome power manager applet not appearing consistently
Public bug reported: Binary package hint: gnome-power-manager 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System - About Ubuntu. Description:Ubuntu lucid (development branch) Release:10.04 2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic. gnome-power-manager: Installed: 2.29.91-0ubuntu6 Candidate: 2.29.91-0ubuntu6 Version table: *** 2.29.91-0ubuntu6 0 500 http://us.archive.ubuntu.com lucid/main Packages 100 /var/lib/dpkg/status 3) What you expected to happen In System Preferences Power Management General Notification Area, I have Always display icon selected. The applet should always display an icon. 4) What happened instead But the Gnome power manager applet doesn't appear consistently. When I resume from suspend, it blinks on and off quickly. Then after things settle down, it'll appear for longer stretches of time (say 5 or 10 seconds) and then disappear for longer stretches (5 or 10 seconds). ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- gnome power manager applet not appearing consistently https://bugs.launchpad.net/bugs/538636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 538636] Re: gnome power manager applet not appearing consistently
** Attachment added: apport.gnome-power-manager.iD_4Wo.apport http://launchpadlibrarian.net/40920918/apport.gnome-power-manager.iD_4Wo.apport -- gnome power manager applet not appearing consistently https://bugs.launchpad.net/bugs/538636 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 465081] [NEW] GStreamer plugins that Totem searches for to play an MP3 file do not actually allow Totem to play MP3
Public bug reported: In older versions of Ubuntu, if you double-click on an MP3 file after a fresh install, Totem will attempt to play the MP3 file, prompt you that it needs to search for suitable plugins, find the plugins, install the plugins, and then actually play the file. In a fresh install of Karmic, if you double-click the MP3 file, Totem will attempt to play the MP3 file, prompt you that it needs to search for suitable plugins, appear to install the plugins, and then tell you it can't play the file. ProblemType: Bug Architecture: i386 Date: Fri Oct 30 12:04:35 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/totem InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: libgstreamer0.10-0 0.10.25-2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gstreamer0.10 Uname: Linux 2.6.31-14-generic i686 ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- GStreamer plugins that Totem searches for to play an MP3 file do not actually allow Totem to play MP3 https://bugs.launchpad.net/bugs/465081 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 465081] Re: GStreamer plugins that Totem searches for to play an MP3 file do not actually allow Totem to play MP3
** Attachment added: can't play mp3 after gstreamer plugins installed.png http://launchpadlibrarian.net/34700218/can%27t%20play%20mp3%20after%20gstreamer%20plugins%20installed.png ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34700219/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/34700221/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/34700223/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/34700224/XsessionErrors.txt -- GStreamer plugins that Totem searches for to play an MP3 file do not actually allow Totem to play MP3 https://bugs.launchpad.net/bugs/465081 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gstreamer0.10 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207583] Re: [hardy] Two instances of applet icon are displayed in notification area
Still a bug in Jaunty as well. If you run gksu update-manager, a second gnome-power-manager applet appears and won't go away unless you use sudo killall gnome-power-manager. -- [hardy] Two instances of applet icon are displayed in notification area https://bugs.launchpad.net/bugs/207583 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 351056] Re: Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta
With today's updates (I think there was a kernel upgrade in there, too), both vertical and horizontal scrolling appear to be working again on my Eee PC. I hope there aren't any regressions before the final release of Jaunty. -- Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta https://bugs.launchpad.net/bugs/351056 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 351056] [NEW] Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta
Public bug reported: Binary package hint: gnome-control-center When I go to System Preferences Mouse Touchpad and select to enable vertical and horizontal scrolling, neither works. The other touchpad options do work, however (enable touchpad and enable mouse clicks with touchpad). I'm using the Eee PC 701. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: horizontal scrolling touchpad vertical ** Tags added: horizontal scrolling touchpad vertical -- Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta https://bugs.launchpad.net/bugs/351056 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 351056] Re: Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta
Thanks. That was a really fast response! Here are the log files. Let me know if you need anything else. ** Attachment added: lspci-vvnn http://launchpadlibrarian.net/24487602/lspci-vvnn -- Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta https://bugs.launchpad.net/bugs/351056 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 351056] Re: Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta
** Attachment added: uname-a http://launchpadlibrarian.net/24487607/uname-a -- Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta https://bugs.launchpad.net/bugs/351056 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 351056] Re: Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta
** Attachment added: version_signature http://launchpadlibrarian.net/24487620/version_signature -- Vertical and horizontal touchpad scrolling don't work on the Eee PC in Jaunty beta https://bugs.launchpad.net/bugs/351056 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 295638] [NEW] file-roller makes you explicitly click on Desktop to extract to desktop, even if desktop is already focused
Public bug reported: Binary package hint: file-roller This is actually I think a duplicate of another bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/80755 but that was reported for Feisty over a year ago. This occurs in Intrepid (sorry I'm late with the bug reporting, but I have only one main computer, so I can't afford to alpha and beta test with it). If I double-click a .tar.gz file, File-Roller appears. Then I click Extract, and I get the Extract dialogue. The dialogue focuses on Desktop, but if I just click OK, nothing happens. I have to click explicitly on Desktop (even though it's already focused), and then I can click OK to get it to extract the archive to the desktop. Can this be fixed for Jaunty? I'm using Ubuntu Intrepid 8.10 on an Eee PC 701. Thanks. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- file-roller makes you explicitly click on Desktop to extract to desktop, even if desktop is already focused https://bugs.launchpad.net/bugs/295638 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 208629] [NEW] f-spot doesn't work with gnome-screensaver
Public bug reported: Binary package hint: f-spot 1) lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 2) apt-cache policy f-spot f-spot: Installed: 0.4.2-1ubuntu1 Candidate: 0.4.2-1ubuntu1 Version table: *** 0.4.2-1ubuntu1 0 500 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status apt-cache policy gnome-screensaver gnome-screensaver: Installed: 2.21.6-0ubuntu3 Candidate: 2.21.6-0ubuntu3 Version table: *** 2.21.6-0ubuntu3 0 500 http://archive.ubuntu.com hardy/main Packages 100 /var/lib/dpkg/status 3) I expected, having selected in both F-Spot and Gnome-Screensaver to have the screensaver use F-Spot photos, to see F-Spot photos when the screensaver turned on. 4) I just get a black screen. This happens when the actual screensaver activates and when I try to preview the screensaver in the Gnome- Screensaver dialogue. All the other screensavers (snowflakes, GLSlideshow, etc.) all work fine. It's just the F-Spot one that's not working. ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- f-spot doesn't work with gnome-screensaver https://bugs.launchpad.net/bugs/208629 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 182038] Re: Black rectangle instead of image in FF3 [Hardy]
So people using the nv driver will just have to live with the black rectangle? -- Black rectangle instead of image in FF3 [Hardy] https://bugs.launchpad.net/bugs/182038 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35112] Re: MP3 track times are incorrect
I can also confirm that the bug still exists in Feisty. -- MP3 track times are incorrect https://bugs.launchpad.net/bugs/35112 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 76193] Re: gnome-screenshot in Edgy crashes... but still works
No. Should I try it with them turned on? -- gnome-screenshot in Edgy crashes... but still works https://launchpad.net/bugs/76193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 76918] Feature request: GDM login box separation
Public bug reported: Binary package hint: gdm Is it possible to have the login box and password box separate and both visible at the same time? If not, could there at least be a way to go back to the username box to correct if after you press Enter? It seems silly to have to enter a password and be told the login is incorrect before you can go back to retyping the username. Thoughts? ** Affects: gdm (Ubuntu) Importance: Undecided Status: Unconfirmed -- Feature request: GDM login box separation https://launchpad.net/bugs/76918 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 76193] gnome-screenshot in Edgy crashes... but still works
Public bug reported: Binary package hint: gnome-utils If I use gnome-screenshot in Edgy Eft (regardless of whether I use it in Gnome or IceWM), it will successfully take a screenshot and then Bug Buddy will come up with the message below. The screenshot works fine and saves the image. But the message still appears: Memory status: size: 1671168 vsize: 0 resident: 1671168 share: 0 rss: 548864 rss_rlim: 0 CPU usage: start_time: 1166374206 rtime: 0 utime: 98 stime: 0 cutime:0 cstime: 0 timeout: 98 it_real_value: 0 frequency: 681 Backtrace was generated from '/usr/bin/gnome-panel-screenshot' (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. ** Affects: gnome-utils (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-screenshot in Edgy crashes... but still works https://launchpad.net/bugs/76193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 76193] Re: gnome-screenshot in Edgy crashes... but still works
I start gnome-screenshot with a keyboard shortcut. I unchecked run_on_crash, and now everything seems to work fine. If apport got a crash file for it, where would it be? There didn't seem to be a visible crash this time. So is this really a bug with Bug Buddy and not gnome-screenshot? -- gnome-screenshot in Edgy crashes... but still works https://launchpad.net/bugs/76193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 76193] Re: gnome-screenshot in Edgy crashes... but still works
Yes, I have apport, apport-gtk, and python-apport-utils all installed, but there's nothing in the /var/crash directory. And, yes, the crashes (really it's just Bug Buddy appearing) happen every time I used gnome-screenshot... well, at least until I changed that option in gconf-editor. -- gnome-screenshot in Edgy crashes... but still works https://launchpad.net/bugs/76193 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 59985] Re: gnome-panel-screenshot crashes when saving PNG
Happens to me, too, and this is generated: Memory status: size: 1667072 vsize: 0 resident: 1667072 share: 0 rss: 548864 rss_rlim: 0 CPU usage: start_time: 1161131168 rtime: 0 utime: 95 stime: 0 cutime:0 cstime: 0 timeout: 95 it_real_value: 0 frequency: 6124 Backtrace was generated from '/usr/bin/gnome-panel-screenshot' (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. -- gnome-panel-screenshot crashes when saving PNG https://launchpad.net/bugs/59985 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 53592] Lack of easy authentication for system files
Public bug reported: Binary package hint: nautilus When a user with sudo privileges double-clicks a system file, she is unable to save it, and if it's read-only for root, then she is told she's unable to open said file. Rather than being denied access, a user with sudo rights should have a dialogue that allows her to grant herself administrative privileges (should she wish to) to view or modify the file. This dialogue would be similar to gDebi's dialogue allowing one to install .deb files with a double-click. ** Affects: nautilus (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Lack of easy authentication for system files https://launchpad.net/bugs/53592 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 52914] Re: Lack of visual feedback on password entry
By the way, a similar problem exists in Konsole, too. -- Lack of visual feedback on password entry https://launchpad.net/bugs/52914 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
