*** This bug is a duplicate of bug 1368402 ***
https://bugs.launchpad.net/bugs/1368402
BTW: I just started using qpdfview. Seems to work equally well. Not
overly long dependency list from the qt set of software and it seems to
be able to highlight text in files.
Aaaah, and it scrolls into the
*** This bug is a duplicate of bug 1368402 ***
https://bugs.launchpad.net/bugs/1368402
This is evince 3.10.3 on Mint.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1396378
Title:
*** This bug is a duplicate of bug 1368402 ***
https://bugs.launchpad.net/bugs/1368402
Like @Aaron I doubt it is a duplicate, since I see the same: all
applications I use scroll in a certain way --- as if grabbing a paper
and pushing it around. Only evince insists that an up-moving gesture
sho
Same here:
# cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.2
DISTRIB_CODENAME=rafaela
DISTRIB_DESCRIPTION="Linux Mint 17.2 Rafaela"
The workaround described in comment #30 works for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Can confirm the workaround of johannes (#50) on Linux Mint
DISTRIB_DESCRIPTION="Linux Mint 17.2 Rafaela"
I had a file browser open listing the device under its name after using
a "browse files on device" button in one of the bluetooth applets. I had
to "eject" this device in the file browser. The
Reading the bugzilla bug linked in #16, we are asked to not use gnome if
we want to be able to tweak one or the other key on our keyboard,
because they are not able to build a working UI on top of xmodmap. At
least this is what I read from it.
--
You received this bug notification because you are
Well,
% find /usr/share/X11/xkb/ -type f|wc -l
273
there are 273 files in this folder a I would definitively need a whole
tutorial to change keyboard settings. My hunch is that changing xkb is a
developer's job, while .Xmodmap is just great to change these one or two
odd keys on the keyboard.
--
Finally I got so fed up with gnome that I switched to XFCE and never
looked back. Despite all the other benefits I personally think it has,
.Xmodmap works as expected again, in particular also when waking up from
sleep.
--
You received this bug notification because you are a member of Desktop
Pac
Well, what is strange is that lsmod does not show fglrx. So it may be
that I installed fglrx but am not using it and still it seems to have
helped.-(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https:/
Wow, what a day. Hoping for relieve on this bug I apt-get install'ed
xfce. It has the same problem with a crashing settings-deamon (it has
its own). And I noticed that even xrandr just crashed on, what I think,
where completely sane inputs with a floating point exception. And I did
not really like
If the login screen is not properly set, it may actually help to copy a
working monitors.xml to /etc/gnome-settings-daemon/xrandr. If Windows
drag ghost pictures, gnome-settings-daemon was still started to early.
For my setup it helped to increase the waiting time to 6 seconds.
--
You received th
Tried the approach of thw-th (comment #46) and it kind of works. This is
an 8 year old Lenovo T500 laptop and I had to enter 6 seconds delay
before it started to work. A downside is that my selected desktop
background image is not set, or rather removed that way: it is set at
some time first, then
Now here is something that did help. In effect it is likely much the
same as killing gnome-settings-manager, except it is not killed, but
just started later:
sudo echo manual >/usr/share/upstart/sessions/gnome-settings-
daemon.override
This prevents the gnome-settings-daemon to be started by the
What do you mean "on the left"? Somehow it is hard to believe the actual
physical location should be important. But clearly one of the monitors
must be listed first in monitors.xml and gets x,y=0,0 assigned, while
the other monitor is then relative to this one.
So we have three properties a monito
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
** This bug has been marked a duplicate of bug 1292398
multi-monitor : second screen position isn't saved from one session to
another
--
You received this bug notification because you are a member of D
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
** This bug has been marked a duplicate of bug 1292398
multi-monitor : second screen position isn't saved from one session to
another
--
You received this bug notification because you are a member of D
Public bug reported:
The upstart .desktop file mentions an executable which does not exist.
% apt-cache show gnome-power-manager|grep -i version
Version: 3.8.2-1ubuntu2
% dpkg -L gnome-power-manager |grep desktop
/usr/share/applications/gnome-power-statistics.desktop
/etc/xdg/autostart/gnome-pow
man-year-wasting indeed :-(
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1243642
Title:
.Xmodmap not automatically loaded on start
Status in “xorg” package in Ubuntu:
Confirmed
Bug
Can confirm Juliens solution of killing the gnome-settings-daemon on
statup. It may help to delete ~/.config/monitors.xml and configure your
monitos freshly to clean this file up.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-cont
19 matches
Mail list logo
