[Bug 38512] Re: Window close should close, not quit
There should be a plugin available in rhythmbox to switch to the desired behaviour. As far as I understand this is the most we will ever get (and it is enough for me at least). -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262550] Re: WARNING: Intrepid might burn down MacBook Pro
With applesmc my mbp5.1 is stable but stil a lot hotter than in OSX. I am not sure if this needs a new bugreport... By the way cpufreq-info shows this: cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs to [EMAIL PROTECTED], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 1.60 GHz - 2.53 GHz available frequency steps: 2.53 GHz, 2.39 GHz, 2.13 GHz, 1.86 GHz, 1.60 GHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1.60 GHz and 2.53 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. analyzing CPU 1: driver: acpi-cpufreq CPUs which need to switch frequency at the same time: 0 1 hardware limits: 1.60 GHz - 2.53 GHz available frequency steps: 2.53 GHz, 2.39 GHz, 2.13 GHz, 1.86 GHz, 1.60 GHz available cpufreq governors: userspace, powersave, ondemand, conservative, performance current policy: frequency should be within 1.60 GHz and 2.53 GHz. The governor ondemand may decide which speed to use within this range. current CPU frequency is 1.60 GHz. I think the CPU should be able to go as down as 800MHz, but I am unable to confirm this from OSX. -- WARNING: Intrepid might burn down MacBook Pro https://bugs.launchpad.net/bugs/262550 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247393] Re: [Intrepid KDE4] regression -- systray is incorrectly painted
I confirm this on Intrepid with Gnome. Skype's tray icon has garbled background. -- [Intrepid KDE4] regression -- systray is incorrectly painted https://bugs.launchpad.net/bugs/247393 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117583] Re: ipod: album art not added unless the file is playing
The patch I mentioned was working last time I tried: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/117583/comments/45 -- ipod: album art not added unless the file is playing https://bugs.launchpad.net/bugs/117583 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249220] [NEW] update manager does not check for updates after suspend
*** This bug is a security vulnerability *** Public security bug reported: Binary package hint: update-manager I am using Hardy Heron. It seems updates are not checked in some situations when you suspend. I use suspend every night and resume every evening after I come back from work. Update manager did never check for updates. I found out since I expected some security updates which never come, then I started update manager and it showed that package information was 27 days old. I checked manually and found a lot of updates... Under software sources I have the following options selected: Important security updates (hardy-security) Recommended updates (hardy-updates) Check for updates: Daily Only notify about available updates Show new distribution releases: Normal releases I am fairly sure updates were working when I was simply rebooting (there were problems with suspend at that time). I guess update manager checks for updates at every boot. Maybe it has to check after every resume from suspend too? Flagging as security vulnerability since important security updates can be missed (like it happened to me...). There is another report here: http://brainstorm.ubuntu.com/idea/10305/ ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Visibility changed to: Public -- update manager does not check for updates after suspend https://bugs.launchpad.net/bugs/249220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 249220] Re: update manager does not check for updates after suspend
I just found this anacron bug in dapper which maybe is related: https://bugs.launchpad.net/ubuntu/dapper/+source/update- manager/+bug/36816 But the proposed solution is present in my system (the anacron scripts). After resume ps shows anacron running, so maybe this is not a duplicate. -- update manager does not check for updates after suspend https://bugs.launchpad.net/bugs/249220 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Sebastien, do you know if it's possible to get a log of the discussion and where? I am quite interested in it. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Sebastien, As you said, developers are free to do what they want, but this does not mean users are not allowed to complain when they believe developers are wrong or are behaving in an unprofessional way. It is perfectly right for a user to express his opinion, even in a very direct way, and I find very childish postponing the merit of an issue with a personal problem (that's what happened in my understanding of your previous comment about the discussion in IRC). The bugreport has been very constructive until 2 years from start. Then, since there was no feedback from rhythmbox developers, I asked very politely what was planned for this bug, since the fix were there for such a long time (http://bugzilla.gnome.org/show_bug.cgi?id=318629#c28). You can check the response to that for yourself and what followed, maybe then we can discuss again exactly who has not been constructive and why people stop contributing. Negative energy did not come from nothing. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
why should people who are hobbists and working for free should behave in a professional way? To avoid unnecessary attrition with the users. To have constructive discussions with the goal of improving the software under development. To avoid negative energy as you called it. In my opinion these are very valid reasons. I agree some users crossed the line with some caustic comments, nobody ever denied that, but if you check again the whole bugreport you'll see that discussion and good sense had been ignored for years. Expressing frustration might not be the right way, but it does not surprise me it happened given the history of the issue. As I said, I don't justify it but I for sure understand it. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
The upstream bug has been closed with WONTFIX. Last comment was: Comment #46 from Jonathan Matthew (rhythmbox developer, points: 23) 2008-07-01 22:16 UTC [reply] I am tired of even thinking about this issue. In future, I'm not even going to comment on it (or anything related), let alone commit any patches. So now the question is if the plugin can be included in ubuntu or if this bug too will be closed with WONTFIX. For my part, it doesn't matter, I am not going to use a software developed by people with this attitude anymore. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Sebastien, I'd like to address some of your comments: could everybody stop comment spamming this bug? the default will not be changed because some vocal users decided to add lot of comments there I don't care about the default, I care about having an option. We are vocal because the option is easy to include in rhythmbox and we don't se a rational reason not to provide it for the many users who would like it. - the notification area is not made to have applications staying there that's not what a lot of other application developers think and for sure is not what I am used to and lots of other users are used to. Rhythmbox is the exception, and does not offer choice. - consistancy is good, but do you have many applications not closing when you close those? that's rather pidgin and the reboot notifications which should be changed if they are not consistant in the default installation As I said, at least for the applications I use, Rhythmbox is the exception. When I have an application with a persistent icon in the notification area, I identify the application with the icon, not the window. When I close the window, I expect to close the window, not quit the application, like with all the other similar applications I have. - seems that users will not agree on that so the best way is probably to have a plugin available to change the setting, that's where recent comments are going It is obvious to me that when different users wish different reasonable behaviours you offer choice, that's what made a lot of people vocal about all of this story. This seems not obvious to the rhythmbox developers and at least I cannot figure out why. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Sebastien, - launchpad is a distribution bug tracker and people who read your comments are packagers and bug triagers, not people who writte this code Since from upstream it is not clear if and when at least the plugin will be released I just asked for a fix included in the distribution package: see https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/38512/comments/35 - you will not convince people who are working for free on the code and trying to fix your issues by being vocal or rant, quite the contrary If you check my posts here and on the upstream bugreport you can see that I have never ranted, I said that rants are not justifiable but are understandable. Also, the code is already fixed, the plugin is there. - the issue is usually that people working on free software projects are really busy so better to be constructive and try to give a hand on the changes As i said the plugin is there since ages: it is not a problem of being busy or not having time. working on code changes to have an option is a constructive behaviour there rather than complaining about other contributors The plugin is there since ages, it just has to be included with rhythmbox, that's not the problem. The problem is in my opinion convincing the rhythmbox developers of the wrong attitude they are having, as I tried here: http://bugzilla.gnome.org/show_bug.cgi?id=318629#c44 I think I have been constructive in that post, if you disagree please be specific about it. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
the comment was not especially about your contribution but a note for the people ranting on this bug, your comment upstream is mostly constructive though nobody claims to know better, whoever is writting the software is just free to take the choice he wants for his code and being agressive to convince him to change is not really good. I am sorry that I took it personally, but you replied to me talking about my strategy so I inferred you were discussing about my personal doing. I agree that flaming and ranting will lead to nothing. I also agree that developers are free to do what they like, that's why discussion is the only option in this case. The fix is there, what lacks is convincing the developers it's worth inclusion in rhythmbox. I agree that being aggressive is not a good thing, but it is understandable given the history of this issue. I've to admit I also have difficulties to get why users go in flame mode for such a detail, clicking on the icon is not that hard, is it? I've to admint I also have difficulties to get why developers go in flame mode for such a detail, adding an option is not that hard, is it? Not to mention that I am used to have this behaviour with all my other applications with a persistent notification icon and it is difficult to remember oh, this is rhythmbox, don't do what you usually do, instead do something completely different! when you are clicking away your window. For sure it is annoying, but probably you don't understand this because you have different habits. The fact the problem for you is irrelevant does not mean it is irrelevant for everybody else. By the way I agree that this should be fixed upstream with an option somewhere. Lacking this, including the patch in ubuntu is better than nothing. Also, the idea of the common behaviour for GNOME is nice, but let's say that they decide ok, all the applications should behave like A. All the users who like the behaviour of application B will be disappointed when it gets changed to behave like A. Of course if you reverse it it is the same, users of A will be disappointed. I understand there are cases in which it is clear which is the right way, but this is not, since a lot of different people seem to know a different right way: I'd say in this case, stick with a default coherent behaviour and give choice to the user who wants a different thing. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Sebastien, among the 8 comments you mention there is described a workaround which interested users (I guess every users who is interested in this bug) can use to get what they want quickly and somewhat painlessly. They also made clear that a fix at ubuntu level is unlikely, even if I would find it nice to have. I don't consider this bringing no value, especially the workaround provided. People look into bugreports for this kind of things too until there is a nice fix released. - the example you mention are just opinion on the topic, there is no reason to consider the notification area as a part of the application rather than an indication of the fact that the application is running There is no reason to consider the notification area icon as only an indicator either. The guidelines might say that, but all the other applications I use consider the notification area icon as part of the application, then I assume this should be true for all the applications. That's what a coerent user interface should allow you to do, and it should be the goal of any desktop environment. Rhythmbox is an exception to the usual user experience with applications with notification area icon. And even if this would not have been the case, given the number of users interested in this I'd say adding this option would make Rhythmbox a better software. About the patch you mention, I don't understand what needs to be patched. Rhythmbox itself does not need any patch, just the plugin needs to be included in the release (I don't care if it's from upstream or added by ubuntu). -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Alleluja! There is a plugin which does not require patches to rhythmbox itself! My bad I didn't get it... You can get it from there: http://methlab42.itee.uq.edu.au/~jonathan/rhythmbox-plugins/dontreallyclose/ If you prefer I changed it a bit to get the correct animation when hiding the window: http://bugzilla.gnome.org/attachment.cgi?id=113594 As a side note would be nice to have this plugin easily installable in Ubuntu, but personally I'm already satisfied. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
You're right, I'm sorry. Please disregard my version, I'll try to get it working later. -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
erlguta, you can upgrade to the new (unpatched) version ad use the plugin from http://methlab42.itee.uq.edu.au/~jonathan/rhythmbox-plugins/dontreallyclose/ -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 38512] Re: Window close should close, not quit
Alexander, I very much doubt Ubuntu will be shipping this feature as a distribution patch. Is there a particular reason for this? -- Window close should close, not quit https://bugs.launchpad.net/bugs/38512 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
