Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Control: tags -1 - moreinfo + sid stretch upstream fixed-upstream Control: forwarded -1 https://github.com/mate-desktop/caja/issues/755 Control: found -1 1.16.2-2 So this was finally reproduced and subsequently fixed upstream. The fix will be included in the upcoming 1.16.5 release.
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Le 29/12/2016 à 18:57, Vlad Orlov a écrit : > It's been a while, and MATE 1.16 is now in Unstable and Testing, > with various fixes for GTK+ 3.22 support. I can't reproduce this > bug now. Do you still see it? If it's so, which view (icon view or > list view) and which themes can be used to reproduce it? Hi, Sorry, I don't use MATE anymore. I may re-install it to check if the bugs I filed have been fixed, but right now I'm quite busy. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Control: tags -1 moreinfo Hi, upstream MATE developer here. It's been a while, and MATE 1.16 is now in Unstable and Testing, with various fixes for GTK+ 3.22 support. I can't reproduce this bug now. Do you still see it? If it's so, which view (icon view or list view) and which themes can be used to reproduce it?
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Control: severity -1 important On Fr 02 Sep 2016 05:15:40 CEST, Raphaël Halimi wrote: Package: caja Version: 1.14.2-1 Severity: grave This bug certainly has the same root cause as #826261, as it has the same symptoms: it doesn't appear with Adwaita theme, and it only appear when the window is maximized. When a scrollbar is displayed, it can't be dragged all the way to the bottom, making the last files of the folder "hidden". You can still blindly select them by moving around with the arrow keys, but you can't select them with the mouse or right-click on them, which severely diminishes the number of possible actions on those files. This, in addition to #826261, makes caja quite unusable for daily use. Please fix either caja or mate-themes (or marco ? Why does the bug only appear when the window is maximized ?). I know that someone who uses unstable should expect breakage from time to time, but this one has been going on for too long (and, people who maintain Debian packages *have to* use unstable for various reasons you most probably already know). Regards, Dropping severity to important, this bug may be experienced personally as grave, but in the Debian distro context, severity "important" is more appropriate. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de pgpQwo6YxKGm8.pgp Description: Digitale PGP-Signatur
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Le 02/09/2016 à 13:57, John Paul Adrian Glaubitz a écrit :
> You are clearly are regular end user if you don't understand how bug reporting
> and fixing works in the FOSS community. If you need updated versions of
> certain packages, you are supposed to use Debian Backports, not unstable.
>
> Again, if you want to use unstable because you need updated versions of
> certain packages then Debian unstable is definitely the wrong distribution!
git-buildpackage isn't backported in Jessie, nor are gcc 5 and 6. Now
stop being so condescending whereas you are obviously wrong about many
things.
>> "People like me" ? What exactly do you mean by that ?
>
> People who will always resort to reporting a bug first instead of doing
> some research to figure out whether this is maybe a known issue.
>
> Filing a bug report should always be your *last* resort, not the first
> one.
Your choice of words ("first" and "last resort") is interesting, because
I'm plagued by this bug from the day 1.14 entered unstable, and I
patiently waited until now to report it - when I was on the verge of
switching to another desktop - precisely because I naively thought that
you cared about users of unstable needing a working file manager.
By the way, I didn't yet report the F3/Ctrl+L bug for the exact same
reason (plus that it's not as serious as having a scrollbar which
refuses to go down all the way to the bottom).
So please stop considering everyone but yourself as naive and lazy (or
should I say dumb ?) clueless end-users who barely know to just whine on
the BTS as soon as something is broken.
>> Also, please remind me when I showed to "constantly ignore" that Debian
>> developers get a lot of e-mail traffic due to bug reports. Don't you
>> think I already know that after using Debian for seventeen years ?
>
> Apparently you do. Otherwise we wouldn't have this discussion, would we?
No. We are having this discussion because your views about how the bugs
should be processed by Debian is deeply flawed.
>> Please show me a bug that I reported that was already (or that
>> I didn't merge by myself very quickly after realizing it). I honestly
>> take kindly to learn from my mistakes.
>
> This one? It has already been reported as #836246.
No. #836246 is about general breakage in MATE due to GTK3, the bug I
reported here is about a precise problem, which is not mentioned in
#836246. Moreover, it's funny that you mention this bug, because even
then, you already ranted about OP when he filed it, and Michael Biebl
already reminded you that people people reporting bugs is the whole
point of unstable.
>> That's not what the Debian documentation says (I mean the official
>> Debian documentation, not the wiki):
>>
>>> Don't file bugs upstream
>
> Yes, and I wholeheartedly disagree with that statement because the
> people who usually fix the bugs are upstream, not in Debian.
Oh, so because *you* disagree with a Debian official document, all
Debian users and developers should follow your way of thinking instead
of what's written in that *official* document ? Are you even listening
to yourself ?
>> It means that I should report the bug to Debian first, and that *you*
>> decide afterwards if it should be forwarded upstream.
>
> Why should I do that for you when you can do that yourself perfectly
> fine? Do you expect me to do your homework?
Because, mind you, that's what Debian, as a project, is expecting from
me, and from you.
>> Ironically, this is *especially true* in this particular case, since
>> upstream still uses GTK2 by default, and building the whole MATE desktop
>> against GTK3 was a decision made solely by the Debian maintainers (and,
>> IMHO, not a very clever one, since the Gnome devs, who took over GTK a
>> long time ago, are notorious for being oblivious to anything non-Gnome -
>> especially other desktop environments, which they see as competitors to
>> their "brand" (I quote) - and happily (or is it purposefully ? I may be
>> a bit paranoid here, but who knows) break GTK every six months).
>
> GTK2 is going to be abandoned sooner or later. Also, the decision was
> made by people who also happen to be MATE upstream. But again, you
> are complaining about things breaking in unstable where breaking
> things is *expected*.
Expecting things to break from time to time and being treated as a
testing ground for alpha-grade software are two different things. Even
if it's not explicitly written in the Policy, Debian is well-known for
sticking to upstream configuration as closely as possible. If upstream
still defaults to GTK2 and you decide to build the whole MATE desktop
against GTK3, Debian MATE diverges from upstream MATE, and you should
expect people to report bugs *to Debian* about it.
>> I gladly admit that I forgot to add the "upstream" tag, but you can't
>> seriously blame me for reporting bugs in the Debian BTS only because
>> they come from upstream, whereas the official Debian documentation
>> explicitly says otherwi
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
On 09/02/2016 01:46 PM, Raphaël Halimi wrote: > Oh, I am a "regular end user" now ? What on earth makes you think that I > use unstable only for the "pleasure" of having bleeding-edge versions of > my software ? Why is it so far fetched from your point of view that I, > too, also might develop Debian packages (personal *and* official ones), > and need the latest versions of devscripts, git-buildpackage, lintian, > et al on my development machine ? You are clearly are regular end user if you don't understand how bug reporting and fixing works in the FOSS community. If you need updated versions of certain packages, you are supposed to use Debian Backports, not unstable. Again, if you want to use unstable because you need updated versions of certain packages then Debian unstable is definitely the wrong distribution! >> People like you constantly ignore the fact that at the other end of >> the bug tracker you will find people which are receiving all these >> bug report mails and I can tell you that if you get more than half a >> dozen bug reports describing the same problem over and over again you >> will loose your patience and tamper as well. > > "People like me" ? What exactly do you mean by that ? People who will always resort to reporting a bug first instead of doing some research to figure out whether this is maybe a known issue. Filing a bug report should always be your *last* resort, not the first one. > Also, please remind me when I showed to "constantly ignore" that Debian > developers get a lot of e-mail traffic due to bug reports. Don't you > think I already know that after using Debian for seventeen years ? Apparently you do. Otherwise we wouldn't have this discussion, would we? > Please show me a bug that I reported that was already (or that > I didn't merge by myself very quickly after realizing it). I honestly > take kindly to learn from my mistakes. This one? It has already been reported as #836246. >> No, not really. The pinpointing is done *upstream*. As I have >> explained many many times, this is the Debian bug tracker which >> tracks Debian-specific bugs. The bug you are seeing is an upstream >> bug and therefore affects all distributions and therefore belongs to >> the upstream bug tracker where it will reach the people who can fix >> the actual code. Reporting your bug upstream will dramatically >> increase the bug fixing process and also mean less burden and stress >> for downstream. It also makes sure all distributions are receiving >> the fix as quickly as possible. > > That's not what the Debian documentation says (I mean the official > Debian documentation, not the wiki): > >> Don't file bugs upstream Yes, and I wholeheartedly disagree with that statement because the people who usually fix the bugs are upstream, not in Debian. > It means that I should report the bug to Debian first, and that *you* > decide afterwards if it should be forwarded upstream. Why should I do that for you when you can do that yourself perfectly fine? Do you expect me to do your homework? > Ironically, this is *especially true* in this particular case, since > upstream still uses GTK2 by default, and building the whole MATE desktop > against GTK3 was a decision made solely by the Debian maintainers (and, > IMHO, not a very clever one, since the Gnome devs, who took over GTK a > long time ago, are notorious for being oblivious to anything non-Gnome - > especially other desktop environments, which they see as competitors to > their "brand" (I quote) - and happily (or is it purposefully ? I may be > a bit paranoid here, but who knows) break GTK every six months). GTK2 is going to be abandoned sooner or later. Also, the decision was made by people who also happen to be MATE upstream. But again, you are complaining about things breaking in unstable where breaking things is *expected*. > I gladly admit that I forgot to add the "upstream" tag, but you can't > seriously blame me for reporting bugs in the Debian BTS only because > they come from upstream, whereas the official Debian documentation > explicitly says otherwise. Again, I fully disagree with the official Debian documentation here and once I find the fime, I will request the documentation to be changed because routing all bug reports through Debian will just add an extra layer of indirection which is never good. Really, there is no point in reporting the bug to Debian if it turns out to be an upstream issue. I have reported tons of bugs upstream, heck, I usually even test the latest git revision from upstream to make sure I'm not reporting something that has already been fixed. Why annoy people with things they already know or have taken care of? All you achieve is annoying them or keep them from doing useful things as opposed to reading redundant or invalid bug reports. >> Thank you. My advise would also be to use another distribution >> altogether, I advise using something other than a development >> release, then you won't be bo
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Le 02/09/2016 à 12:05, John Paul Adrian Glaubitz a écrit : > Yes, this is *exactly* what you are supposed to do before filing a > bug report, especially when using *unstable*. If that is too much for > you, please refrain from using *unstable* which is not targeted at > regular end users but primarily developers, in particular people who > develop Debian. You can search the bug tracker with Google, after > all. So I don't really think asking for some research before filing a > new bug report is too much asked for, really. I do that all the > time. Oh, I am a "regular end user" now ? What on earth makes you think that I use unstable only for the "pleasure" of having bleeding-edge versions of my software ? Why is it so far fetched from your point of view that I, too, also might develop Debian packages (personal *and* official ones), and need the latest versions of devscripts, git-buildpackage, lintian, et al on my development machine ? This was exactly the whole point of the last sentence in my initial bug report (which I also tried to hint in my initial reply to your harsh response) but apparently your ego prevented you to get the message. > People like you constantly ignore the fact that at the other end of > the bug tracker you will find people which are receiving all these > bug report mails and I can tell you that if you get more than half a > dozen bug reports describing the same problem over and over again you > will loose your patience and tamper as well. "People like me" ? What exactly do you mean by that ? Also, please remind me when I showed to "constantly ignore" that Debian developers get a lot of e-mail traffic due to bug reports. Don't you think I already know that after using Debian for seventeen years ? Please show me a bug that I reported that was already (or that I didn't merge by myself very quickly after realizing it). I honestly take kindly to learn from my mistakes. > No, not really. The pinpointing is done *upstream*. As I have > explained many many times, this is the Debian bug tracker which > tracks Debian-specific bugs. The bug you are seeing is an upstream > bug and therefore affects all distributions and therefore belongs to > the upstream bug tracker where it will reach the people who can fix > the actual code. Reporting your bug upstream will dramatically > increase the bug fixing process and also mean less burden and stress > for downstream. It also makes sure all distributions are receiving > the fix as quickly as possible. That's not what the Debian documentation says (I mean the official Debian documentation, not the wiki): > Don't file bugs upstream > > If you file a bug in Debian, don't send a copy to the upstream > software maintainers yourself, as it is possible that the bug exists > only in Debian. If necessary, the maintainer of the package will > forward the bug upstream. (Source: https://www.debian.org/Bugs/Reporting.en.html, so it can't even be a translation error) It means that I should report the bug to Debian first, and that *you* decide afterwards if it should be forwarded upstream. Ironically, this is *especially true* in this particular case, since upstream still uses GTK2 by default, and building the whole MATE desktop against GTK3 was a decision made solely by the Debian maintainers (and, IMHO, not a very clever one, since the Gnome devs, who took over GTK a long time ago, are notorious for being oblivious to anything non-Gnome - especially other desktop environments, which they see as competitors to their "brand" (I quote) - and happily (or is it purposefully ? I may be a bit paranoid here, but who knows) break GTK every six months). I gladly admit that I forgot to add the "upstream" tag, but you can't seriously blame me for reporting bugs in the Debian BTS only because they come from upstream, whereas the official Debian documentation explicitly says otherwise. > Thank you. My advise would also be to use another distribution > altogether, I advise using something other than a development > release, then you won't be bothered anymore by things being broken > during *development*. I would also suggest learning the difference > between upstream and distribution downstream and understanding when > to report bugs upstream and when to report them downstream. For both points, see above. > PS: The bug you are seeing is because of a change in GTK3, not MATE, > so you're actually also yelling at the wrong people when you > complain about things being broken this time. I didn't "yell" at anyone, you did (and in an incredibly condescending tone, I might add). Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
On 09/02/2016 11:47 AM, Raphaël Halimi wrote: > And how, exactly, are *we* supposed to know that ? Are we expected to > read all bug reports about *every* MATE component, on Debian's BTS and > upstream's, before reporting a bug against any of those components ? Yes, this is *exactly* what you are supposed to do before filing a bug report, especially when using *unstable*. If that is too much for you, please refrain from using *unstable* which is not targeted at regular end users but primarily developers, in particular people who develop Debian. You can search the bug tracker with Google, after all. So I don't really think asking for some research before filing a new bug report is too much asked for, really. I do that all the time. People like you constantly ignore the fact that at the other end of the bug tracker you will find people which are receiving all these bug report mails and I can tell you that if you get more than half a dozen bug reports describing the same problem over and over again you will loose your patience and tamper as well. > Besides, isn't the additional information on all those little symptoms, > supposed to help you pinpoint the bug and fix it ? No, not really. The pinpointing is done *upstream*. As I have explained many many times, this is the Debian bug tracker which tracks Debian-specific bugs. The bug you are seeing is an upstream bug and therefore affects all distributions and therefore belongs to the upstream bug tracker where it will reach the people who can fix the actual code. Reporting your bug upstream will dramatically increase the bug fixing process and also mean less burden and stress for downstream. It also makes sure all distributions are receiving the fix as quickly as possible. > You know, yesterday night when I was hit by this bug, I was so fed up > with those problems that I contemplated just ditching MATE altogether in > favor of another desktop, but I decided to calm down and to report the > bug. This is the last straw: rest assured that you won't receive any > more bug reports emanating from me regarding MATE. Thank you. My advise would also be to use another distribution altogether, I advise using something other than a development release, then you won't be bothered anymore by things being broken during *development*. I would also suggest learning the difference between upstream and distribution downstream and understanding when to report bugs upstream and when to report them downstream. PS: The bug you are seeing is because of a change in GTK3, not MATE, so you're actually also yelling at the wrong people when you complain about things being broken this time. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 signature.asc Description: OpenPGP digital signature
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Le 02/09/2016 à 06:43, John Paul Adrian Glaubitz a écrit : > Can you people *please* stop filing bug reports telling us that MATE has > currently > issues with gtk+3.0 3.21.x? We know that, alright? And how, exactly, are *we* supposed to know that ? Are we expected to read all bug reports about *every* MATE component, on Debian's BTS and upstream's, before reporting a bug against any of those components ? Besides, isn't the additional information on all those little symptoms, supposed to help you pinpoint the bug and fix it ? > If you cannot live with things being broken, please stop using unstable. Did you read the last sentence of my report ? You know, yesterday night when I was hit by this bug, I was so fed up with those problems that I contemplated just ditching MATE altogether in favor of another desktop, but I decided to calm down and to report the bug. This is the last straw: rest assured that you won't receive any more bug reports emanating from me regarding MATE. Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
On 09/02/2016 05:15 AM, Raphaël Halimi wrote: > This bug certainly has the same root cause as #826261, as it has the > same symptoms: it doesn't appear with Adwaita theme, and it only appear > when the window is maximized. Can you people *please* stop filing bug reports telling us that MATE has currently issues with gtk+3.0 3.21.x? We know that, alright? There is no point in writing a bug report for every single MATE package now. This isn't helpful, this is just outright annoying. If you cannot live with things being broken, please stop using unstable. Than you! Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 signature.asc Description: OpenPGP digital signature
Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita
Package: caja Version: 1.14.2-1 Severity: grave This bug certainly has the same root cause as #826261, as it has the same symptoms: it doesn't appear with Adwaita theme, and it only appear when the window is maximized. When a scrollbar is displayed, it can't be dragged all the way to the bottom, making the last files of the folder "hidden". You can still blindly select them by moving around with the arrow keys, but you can't select them with the mouse or right-click on them, which severely diminishes the number of possible actions on those files. This, in addition to #826261, makes caja quite unusable for daily use. Please fix either caja or mate-themes (or marco ? Why does the bug only appear when the window is maximized ?). I know that someone who uses unstable should expect breakage from time to time, but this one has been going on for too long (and, people who maintain Debian packages *have to* use unstable for various reasons you most probably already know). Regards, -- Raphaël Halimi signature.asc Description: OpenPGP digital signature
