[Bug 1739805]

2020-01-17 Thread Main-haarp
> With the patch applied, on the General tab of Xfce Power Manager,
there should be a "Brightness step count" field and an "Exponential"
checkbox next to it.

Weird, I'm not seeing those. But don't let that worry you, I'm sure the
next proper release will have those setting show up.

> I believe the effect of exponential steps is very much dependent on
the characteristics of the LCD backlight.  For my last two laptops,
there are very visible differences between every step on the scale.
Perhaps you can try reducing the number of steps to 6?

Tried that. Funnily enough, it did nothing to change the lower end. Now
I have 3 steps that do nothing and 3 steps that quickly increase
brightness :)

Seems like a large case of YMMV.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739805

Title:
  Backlight tuning has not enough steps

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1739805]

2020-01-15 Thread Main-haarp
Thank you, Timothy Lee. This was long needed. I've applied attachment
8653 from comment 25 on top of xfce4-power-manager-1.6.5. I couldn't
apply the newer patches due to the aforementioned code style changes.

Where are the settings to be found? I can't find anything new in the
Power Manager's setting screen. I ended up manually adding them with the
settings editor.

The exponential feature is really comfortable to use. However there's
one caveat. It starts too slow, so that the first 3 of 10 steps have
pretty much no effect at all. Is there a way to weigh it a little more
towards the later steps?

Cheers!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1739805

Title:
  Backlight tuning has not enough steps

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797417]

2019-09-19 Thread Main-haarp
(In reply to Simon Steinbeiss from comment #29)
> Created attachment 9037 [details]
> Always set parent-relative background
> 
> I'm not sure it's helpful to not set a parent-relative background when
> compositing is disabled, so I went for always enabling it.
> This fixes the problem for me.
> 
> Please test the attached patch! Thanks

Can't confirm, the icons are still corrupted with the patch applied to
panel 4.14.0 and compositing disabled.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797417

Title:
  Background of system tray icons not drawn properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-panel/+bug/1797417/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1063140]

2019-04-02 Thread Main-haarp
Additionally, when new elements are created, they always end up on the
leftmost output, instead of the output they were created on. See
https://www.reddit.com/r/xfce/comments/b6341f/new_icons_appear_on_the_wrong_monitor/ejhm472/

4.13.3

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063140

Title:
  Drag and Drop position ignored by xfdesktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfdesktop/+bug/1063140/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 589485]

2018-12-19 Thread Main-haarp
(In reply to Michael Shigorin from comment #32)
> (In reply to main.haarp from comment #31)
> > Do you happen to have a more recent patch?
> 
> 1.19.3:
> http://git.altlinux.org/gears/x/xorg-server.git?p=xorg-server.git;
> a=commitdiff;h=c5b77a90d7e0d6a1874fcb545969f355d1ed0293

Applies well. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 589485]

2018-12-19 Thread Main-haarp
(In reply to Michael Shigorin from comment #30)
> FWIW we've patched xorg-server in the distribution.
> Shame on those breaking base functionality instead of fixing their crap!

Do you happen to have a more recent patch? The ones posted here are very
outdated.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 619403]

2018-12-19 Thread Main-haarp
(In reply to Peter Hutterer from comment #16)
> Adam: I'm really hesitant to put it into libinput because I'm not sure the
> problem scope is well understood (at least by me) and what the actual point
> of it is. So far it's been a "would be nice" but - at least these days :) -
> we require a bit more information about use-cases and precise behaviours.
> 

At least from my corner of mouse usage, the problem is that X has no
scroll distance multiplier like Windows does. Scrolling is slow.

Some applications have their own mechanisms to deal with that, like
Firefox's hidden about:config preferences, or extensions for Chrome. Or
you can also try to hack something together with imwheel.

If it's a touchpad, you can reduce the distance needed to send one
"scroll event". This makes scrolling faster, but also less accurate and
more error-prone.

Obviously none of these solutions are very good.

The future is going towards smooth scrolling, which is an incredible
experience. But while it's buttery smooth, it still doesn't solve the
problem of configurable scroll speed/distance.

Configurable acceleration on the input device driver level would solve
this nicely. You could have fast scrolling when you need it, and even
still retain slow but precise scrolling when you don't.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 619403]

2018-12-19 Thread Main-haarp
(In reply to Peter Hutterer from comment #20)
> (In reply to main.haarp from comment #17)
> If the document is long enough
> that scrolling acceleration is needed, the application (or toolkit) should
> honor that and provide the appropriate methods - that may include
> acceleration.
> libinput sits too low to have the semantic awareness here. For example,
> scrolling events during alt-tab switch between applications but libinput
> doesn't know that, it merely forwards the hardware events.

You have a point there, libinput will always lack the semantic awareness
and thus not provide an ideal solution.

But I'll have to disagree. In an ideal world, you can offload
acceleration to the app/toolkit. But since we have tons of legacy
applications or developers unaware or unwilling to implement
acceleration, they'll never receive the benefits. And even if they
implement it, you get lots of duplicated efforts and functionality
between apps.

If  acceleration depends on the toolkit/application, I fear it'll remain
a toy for select applications on modern distros only.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512120]

2018-06-08 Thread Main-haarp
(In reply to Yan Pas from comment #185)
> I agree with comment #184. I face an app being frozen in event loop. Do we
> need to open a new bug?

Yes, please do and let us know the bug number.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  [SRU] thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512120]

2018-06-08 Thread Main-haarp
Could we please keep the support and packaging stuff to a minimum here?

I appreciate the work people do on getting these critical fixes
packaged, but this isn't a support forum. This section is for the bug
itself.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  [SRU] thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512120]

2018-06-08 Thread Main-haarp
(In reply to slumbergod from comment #101)
> Nothing can proceed forwards until we get some feedback from the main xfce
> developers. 
> 
> I'm not even sure if anyone is in charge of the thunar project and my
> attempts in the past to ask what the status of the project is with regard to
> fixing the bugs have gone unanswered.
> 
> Perhaps they have a plan in action already (other than just applying patches
> to address the symptoms)? It would be nice to know "yes, we have it sorted"
> or "no, we have no clue".

Harald Judt is in charge of Thunar, but he appears to not have much
spare time at the moment. I highly doubt anyone is working on porting
Thunar to GTK3 at the moment, nor could I find anything about it in the
mailing list (it would be wise to ask around tho).

My impression is that many Xfce components are severely lacking
manpower.

Hence my suggestion. Porting to Python would kill multiple birds with
one stone:

- Port to GTK3
- Fix this crash
- Fix other bugs
- Easier to use language
- Pull in more developers


I think this is getting off-topic tho. Should we move this to the mailing list?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  [SRU] thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512120]

2018-06-08 Thread Main-haarp
(In reply to slumbergod from comment #99)
> Offering a bounty is a nice idea but I still think this requires something
> bigger. We really need to crowdfund to hire a software engineer to re-write
> a significant chunk of code rather than just work out a single fix.
> 
> It might even lead to some of the other papercut bugs getting sorted (I know
> I've posted bug reports for several small "weird" behaviours that shouldn't
> be considered "normal" behaviour in a file manager.
> 
> Too bad thunar is written in C. If it was Python or something higher level
> we'd probably have these things sorted because more people would be able to
> contribute (myself included).

If a significant portion of it needs to be rewritten anyway, maybe it
could be worth considering porting it to another language entirely. I
agree that Python would be an excellent candidate.

It would make development much easier and as you said, take care of the
many papercuts that Thunar does indeed currently have. Plus, Thunar
needs to be ported to GTK3 eventually anyway.


I like C, but writing GUI applications in it is a nightmare.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  [SRU] thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512120]

2018-06-08 Thread Main-haarp
At this point it almost seems less work to strip everything remotely
related to renaming and rewrite it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512120

Title:
  [SRU] thunar crashes on file renaming

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/1512120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 589485]

2016-02-27 Thread Main-haarp
I too would like Xorg to not blatantly lie.

The proposed patch from 2011 does not apply anymore to recent versions,
is there an updated one?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 899624]

2015-06-12 Thread Main-haarp
(In reply to Harald Judt from comment #10)
> The patch from some duplicate doesn't seem to work for me?

Hmm, weird. It works very well for me.


I just discovered a case that's not covered by this patch however. The "Image" 
tab in file properties of pictures is shown only for local files, even with the 
patch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899624

Title:
  thunar actions only on local drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/899624/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1368402]

2015-04-26 Thread Main-haarp
My bet is that since GTK3 applications use smooth scrolling
(http://who-t.blogspot.de/2011/09/whats-new-in-xi-21-smooth-
scrolling.html), they listen to different scroll events than the
(correctly-inverted) GTK2-based ones.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368402

Title:
  GTK3 apps doesn't understand natural scrolling in Xubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1368402/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 899624]

2015-04-19 Thread Main-haarp
(In reply to Jérôme Guelfucci from comment #4)
> Patch proposed in a duplicate:
> https://bugzilla.xfce.org/attachment.cgi?id=3482&action=diff

I can confirm this patch as working.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/899624

Title:
  thunar actions only on local drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunar/+bug/899624/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1425972]

2015-03-07 Thread Main-haarp
(In reply to Evangelos Foutras from comment #6)
> FTR, Firefox 36.0.1 has restored the -remote option as it broke many use
> cases without any real benefit. We could possibly revert commit 8022a52 in
> exo, though I can't think of an upside to using -remote in this context.

Seeing as -remote seems to enjoy a semi-deprecated status now, it's
probably best to avoid it if possible for the time being.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425972

Title:
  Firefox no longer supports -remote parameter

To manage notifications about this bug go to:
https://bugs.launchpad.net/exo/+bug/1425972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 421621]

2014-06-24 Thread Main-haarp
Confirming that the patch fixed this bug for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/421621

Title:
  pavucontrol's window width depends on stream names, may get very wide

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/421621/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs