[Bug 170049] Re: Inverted ruler co-ordinate system
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 on the page, numerically. If I'm drawing a room (furniture layout etc.), I don't want the corner of the room to need to be at the corner of the page. It should be whichever corner I decided to start measuring from. (And that in fact is what I'm trying to do at this very moment.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/170049 Title: Inverted ruler co-ordinate system To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/170049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778649] [NEW] clang headers aren't installed or linked in /usr/include/clang-c
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 these headers only in /usr/lib/llvm-6.0/include/clang-c, or an oversight? It will be an issue for any software that attempts to reuse parts of clang to build other tools. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libclang-6.0-dev 1:6.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 26 08:52:55 2018 SourcePackage: llvm-toolchain-6.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: llvm-toolchain-6.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778649 Title: clang headers aren't installed or linked in /usr/include/clang-c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-6.0/+bug/1778649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777994] [NEW] the header xcb/xinput.h is missing
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 of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774242] Re: Wacom touchscreens should use libinput, not wacom driver
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, whichever is installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774242] [NEW] Wacom touchscreens should use libinput, not wacom driver
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 "wacom" EndSection The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either. I also verified it with Peter Hutterer's old cairo- based mt-touch test program. I suspect we will get some users mistakenly writing up Qt bugs about this if you don't ship a fix. (Seems to me that already happened at least once, actually.) Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically been only for Wacom tablets and in-screen stylus digitizers, and IMO that continues to be the case. libinput is a much better choice of driver for this hardware (so is evdev for that matter), so I changed it to Driver "libinput" and got it working. (Wayland uses libinput, so in a wayland session, touch already works fine in Qt apps on this hardware.) I'm one of the Qt Quick maintainers, most concerned with touch handling, and I've also written some of the Qt xcb code for dealing with XInput touch and tablet devices. So if you think that there's something wrong with Qt, such that it should still work anyway to use a wacom driver for a Wacom touchscreen, let me know. These AES devices are still new to me (that's why I got a Yoga, to try it out). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/70-wacom.conf] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 19:40:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should use libinput, not wacom driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551122] Re: Crash on screen power save
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 (kwin still running), no applications. Killed X and logged in again with OpenBox, and ran Creator and Assistant again. Kerchunk script, and this time Creator crashed but Assistant survived. Ran Creator again, used arandr to disable one monitor. Ran the script again, and again Creator crashed while Assistant survived. Tried again with the qopenglwindow example; that survives the kerchunk script too. Maybe if I could have a look at which patches you have cherry-picked on top of 5.5, could figure out what is still missing. -- 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/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551122] Re: Crash on screen power save
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.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551122] Re: Crash on screen power save
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/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1551122] Re: Crash on screen power save
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 alloff="$alloff --output $o --off" done echo $alloff echo $restore $alloff sleep 2 $restore But at least applications tend to survive, and plasma restarts itself. -- 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/ubuntu/+source/qtbase-opensource-src/+bug/1551122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548766] Re: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases)
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 restore=`unxrandr` outputs=`xrandr | grep -i "^\\w" | grep connected | cut -d' ' -f1` alloff="xrandr" for o in $outputs do alloff="$alloff --output $o --off" done echo $alloff echo $restore $alloff sleep 2 $restore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548766 Title: Plasma crashes when the monitor is disconnected (when it sleeps, in some cases) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548766] [NEW] KDE crashes when the monitor is disconnected (when it sleeps, in some cases)
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::primaryScreen() returns null, and so on. KDE developers have been complaining. So in Qt 5.6 we made it keep the last-remaining QScreen as a fake instance, whenever the last monitor is disconnected. The main patch is here https://codereview.qt-project.org/#/c/138201/ You might need to cherry-pick that (a094af001795c9651b299d700a992150d1aba33a in qtbase) for as long as you are shipping Qt 5.5, to get Kubuntu behaving decently. It's relevant on Ubuntu 16.04. Too bad that Ubuntu LTS is not shipping the LTS Qt 5.6 release, but I know we are behind on our release schedule. Some users have also reported that their laptop's screen disconnects when it sleeps. And I have often experienced 5.5-based builds of Creator crashing or disappearing when I switch machines on my KVM. So, sorry that we didn't fix it sooner. It was my mistake for believing that modeling disappearing screens "correctly" was a good idea: it turned out to be a platform inconsistency which developers were not ready for. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548766 Title: KDE crashes when the monitor is disconnected (when it sleeps, in some cases) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1548766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1015183] Re: Inconsistent mouse events for Acer T231H multitouch monitor
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 button was being pressed. So in other words if you have a touchscreen your mouse wheel isn't very useful anymore in certain applications. I think it should be fixed in 12.04 too, not just in newer releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1015183 Title: Inconsistent mouse events for Acer T231H multitouch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1015183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070770] Re: bluetoothd dies with glibc malloc memory corruption when used with brcm_patchram
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 when used with brcm_patchram To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1070770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070770] Re: bluetoothd dies with glibc malloc memory corruption when used with brcm_patchram
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 bluetooth device. lsusb doesn't find one, hcitool scan says "No such device" and so on. Does there need to be an hci attach somewhere, if this is a serial-attached BT chip? Or is it just a missing driver in that kernel? If so, could someone provide an updated kernel image that has the bluetooth fixes and also the kexec-hardboot patch for multirom? -- 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 when used with brcm_patchram To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1070770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658072] Re: Keyboard keys repeat
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658072 Title: Keyboard keys repeat -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
