The fix is barely adequate for only a few people IMO.
Some 1990s-era programs for graphical work had the ability to drag the
corner where the rulers meet, out into the document somewhere, to set a
new origin.
I would expect to _at least_ have a document-specific setting to set the
origin anywhere
Public bug reported:
This causes a problem building qdoc on Ubuntu 18.04:
https://bugreports.qt.io/browse/QTBUG-69044
In summary, #include doesn't work unless one adds an
extra -I include path. On some other Linux OSes, that's not necessary.
So I wonder if this is a matter of policy to have t
Public bug reported:
I suspect this means there should be another package, libxcb-xinput-dev
perhaps?
I already did sudo apt install "libxcb*dev" to get all related dev
packages, but none of them provide xcb/xinput.h.
The result is that when building Qt from source, it's necessary to use a
copy
I verified that the stylus does still work OK (using the Qt tablet
example which demonstrates pressure-sensitivity etc.) So I think it's
probably OK to remove that stanza completely: there's probably no reason
to use wacom.drv for the touchscreen, just let it fall back to libinput
or evdev, whiche
Public bug reported:
/usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this:
Section "InputClass"
Identifier "Wacom touchscreen class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Driver "w
Maybe it's a little better, but not there yet. I have two monitors
attached. I tried running Creator and Assistant, then running my script
which uses xrandr to remove and re-add the displays. I tried this first
in a Plasma session. When the screens came back to life I had only a
black screen (k
BTW how soon will Ubuntu upgrade to Qt 5.6?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551122
Title:
Crash on screen power save
To manage notifications about this bug go to:
https://bugs.launch
likewise with 5.5.1+dfsg-15ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551122
Title:
Crash on screen power save
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Updated to 5.5.1+dfsg-14ubuntu3. It's not enough to prevent Plasma from
crashing if I disconnect/reconnect both monitors simultaneously with my
script.
#!/bin/sh
restore=`unxrandr`
outputs=`xrandr | grep -i "^\\w" | grep connected | cut -d' ' -f1`
alloff="xrandr"
for o in $outputs
do
allo
I installed the ppa. I have two monitors. Disconnecting and
reconnecting one is OK, but I have a script for disconnecting and
reconnecting both; in that case plasma still crashes.
#!/bin/sh
Public bug reported:
I'm reporting this on behalf of a coworker who has a 4K monitor, which
disconnects whenever it sleeps. Older monitors didn't do that; but Qt
5.5 tries to be honest about it: the QScreen is destroyed whenever its
corresponding monitor is disconnected, QGuiApplication::primaryS
This is quite a severe bug. If you have a touchscreen connected, and
you have touched it at some point:
1) start gitk or tkinfo or a recent Qt Creator (or probably many other Qt 5
programs)
2) scroll some long text with the mouse wheel
3) move the mouse
It selects text as if the left mouse butt
Till,
Thanks for the comprehensive explanation. It does indeed work nicely now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070770
Title:
bluetoothd dies with glibc malloc memory corruption whe
To use multirom, I need to install kernel_kexec_42.zip as described here
http://rootingandroid.net/how-to-install-multiple-roms-and-ubuntu-on-a-nexus-7/
(I found out when doing an apt-get upgrade that it wouldn't boot anymore, after
the kernel was upgraded)
Then I'm not seeing that there is a blue
I have this issue on Gentoo, was googling and found this thread. It
does NOT happen with a USB keyboard. But I'm missing my good old Model
M so I want to keep trying. No idea how to fix it though. Could there
be a BIOS update to fix it?
--
You received this bug notification because you are a
15 matches
Mail list logo
