[Desktop-packages] [Bug 589485]
(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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 589485]
(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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 619403]
(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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/619403 Title: [KDE] no option for mouse wheel acceleration Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: I am very used to mouse wheel acceleration but I haven't found any setting for it in the KDE settings. Also, the maximum possible value you can fill there (strangely it counts per lines) still is very slow. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kdebase (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.39-generic-pae 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 17 20:50:50 2010 InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-kde To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 619403]
(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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/619403 Title: [KDE] no option for mouse wheel acceleration Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: I am very used to mouse wheel acceleration but I haven't found any setting for it in the KDE settings. Also, the maximum possible value you can fill there (strangely it counts per lines) still is very slow. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kdebase (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.39-generic-pae 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Aug 17 20:50:50 2010 InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-kde To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 589485]
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 Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/589485 Title: Ignores physical display size and calculates based on 96DPI Status in X.Org X server: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The X server, starting with 1.7, ignores the physical size reported by the EDID or in xorg.conf and calculates it based on screen resolution and a DPI of 96. This is rather annoying for users of high DPI screens. GNOME and KDE (used?) to set 96 DPI by default in their settings. We should check whether they still do, and if so let them handle this; I don't think X should be handling this. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1425972]
(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 Desktop
Packages, which is subscribed to emacs24 in Ubuntu.
https://bugs.launchpad.net/bugs/1425972
Title:
Firefox no longer supports -remote parameter
Status in exo:
Fix Released
Status in One Hundred Papercuts:
Confirmed
Status in emacs24 package in Ubuntu:
Confirmed
Status in exo package in Ubuntu:
Confirmed
Status in firefox package in Ubuntu:
Fix Released
Status in emacs24 source package in Trusty:
Confirmed
Status in exo source package in Trusty:
Fix Committed
Status in firefox source package in Trusty:
Confirmed
Status in emacs24 source package in Utopic:
Confirmed
Status in exo source package in Utopic:
In Progress
Status in firefox source package in Utopic:
Confirmed
Status in exo package in Debian:
New
Bug description:
[Impact]
As of Firefox version 36, the -remote commandline parameter was dropped.
This parameter is used in versions of exo prior to 0.10.3. Because of this,
opening any URLs via exo-open will cause a new firefox window to launch at the
home screen.
As reported, this affects the terminal, ubuntu-bug, xchat, and
numerous other applications.
[Test Case]
1. Set Firefox as the default web browser in "Preferred Applications".
2. From a terminal, type the following:
exo-open "http://www.xfce.org";
Expected: Firefox opens at http://www.xfce.org
Actual: Firefox opens at the home page.
[Regression Potential]
No regressions by this change. This fixes the application call to correctly
open URLs.
---
[Original Report]
When I click a link from an email it does not work any more.
Instead of opening the link in a new tab, Firefox opens a new empty
window and does not follow the link.
If I change the default browser for my desktop from Firefox to Chrome,
then Chrome can open the link fine.
I have started seeing this today since firefox was upgraded from v35
to 36.
My email client is Mozilla thunderbird at the latest stable version.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: firefox 36.0+build2-0ubuntu0.14.10.4
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: dpottage 3729 F pulseaudio
BuildID: 20150224133805
Channel: Unavailable
CurrentDesktop: XFCE
Date: Thu Feb 26 14:30:41 2015
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2013-07-02 (604 days ago)
InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64
(20130423.1)
IpRoute:
default via 192.168.1.254 dev eth0 proto static
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.131 metric
1
MostRecentCrashID: bp-86a16931-63d2-435e-8324-421212140304
Plugins:
Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
LibreOffice Plug-in - /usr/lib/libreoffice/program/libnpsoplugin.so
(browser-plugin-libreoffice)
Java(TM) Plug-in 11.25.2 -
/usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=36.0/20150224133805 (In use)
RelatedPackageVersions: browser-plugin-libreoffice 1:4.3.3-0ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: firefox
SubmittedCrashIDs: bp-86a16931-63d2-435e-8324-421212140304
UpgradeStatus: Upgraded to utopic on 2014-10-29 (119 days ago)
dmi.bios.date: 11/23/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0XR1GT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA08:bd11/23/2012:svnDellInc.:pnVostro270:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 270
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/exo/+bug/1425972/+subscriptions
--
Mailing list:
