[05:21] <xubuntu30w> O hai, could anyone help with an Xubuntu 18.04.3 issue with touchscreen being identified wrong by xinput? It should be an easy fix I hope
[05:22] <well_laid_lawn> xubuntu30w:  do you know the hardware inviolved ?
[05:25] <xubuntu30w> @well_laid_lawn it's the touchscreen on an HP RP7800 POS terminal, yes
[05:25] <xubuntu30w> what I can tell you is that it seems to identify itself as two devices, both show up in evtest(1)
[05:26] <xubuntu30w> "HID TOUCH HID Touch Panel Touchscreen" (/dev/input/event4) and "HID TOUCH HID Touch Panel Mouse" (/dev/input/event5)
[05:26] <xubuntu30w> event4 does nothing. event5 generates events exactly like you'd expect when the screen is touched
[05:27] <xubuntu30w> Oops sorry, it's event4 that works and event5 that doesn't
[05:28] <xubuntu30w> However, the only one that shows up in "xinput list" is "HID TOUCH HID Touch Panel Mouse" (the dead one)
[05:29] <xubuntu30w> That's also the only one that shows up in Settings -> Mouse and Touchpad
[05:30] <well_laid_lawn> so you touch the screen to click on something and nothing happens ?
[05:30] <xubuntu30w> Exactly, nothing happens.
[05:31] <well_laid_lawn> I don't use touch screens but we'll see what the interwebs says about it
[05:32] <xubuntu30w> I've been trying to google up what to do for like 2 days, but all the hits I get are like "put ~~~ in Xorg.conf", yet this version of Xubuntu doesn't seem to *have* Xorg.conf :/
[05:34] <well_laid_lawn> it's in ~/.local/share nowadays
[05:34] <well_laid_lawn> I had no luck with a web search 'cept hp.com stuff
[05:35] <xubuntu30w> the thing is that since it'll talk to evtest(1), it's just a case of getting Xinput to accept input from it
[05:35] <xubuntu30w> then I'm sure it'll work
[05:36] <well_laid_lawn> Xorg has to load the right module for it
[05:36] <xubuntu30w> OK, I see
[05:36] <well_laid_lawn> which is probably what you found about editing xorg.conf
[05:37] <xubuntu30w> I didn't find anything specific to this one very touchscreen, what I was looking at was more generic
[05:38] <well_laid_lawn> no harm in trying
[05:38] <well_laid_lawn> can always unedit a file
[05:50] <xubuntu30w> I mean, I didn't even get as far as finding anything that I could paste into an xorg.conf :/
[05:50] <xubuntu30w> like "generic touchscreen" kind of example
[05:51] <well_laid_lawn> xubuntu30w:  it might pay to check dmesg and see what it says about the hardware
[05:55] <xubuntu30w> well_laid_lawn let's have a look
[05:55] <xubuntu30w> hang on
[05:56] <well_laid_lawn> https://wiki.archlinux.org/index.php/Touchscreen might help
[08:32] <bodiccea> Do you use "radiotray" ? It used to work, but recently, it fails when system locks. Impossible to relaunch it too...
[09:05] <hans_> i've seen it TWICE now, i'm pretty sure that: if you install xubuntu through "xubuntu-18.04-desktop-amd64.iso" then you will get a functional apt-get package tab-autocomplete, but if you install it through "xubuntu-18.04.3-desktop-amd64.iso" it will be broken o.0
[09:06] <hans_> anyhow, the last 2 installs i did via xubuntu-18.04.3-desktop-amd64.iso had broken apt-get autocomplete
=== byteturtle_ is now known as byteturtle
=== lightero1l is now known as lighterowl
[11:44] <hans_> how do i add custom programs/launchers to the start menu? put my .desktop file in /usr/share/applications ? is that the correct way to do it?
[11:45] <hans_> idk if it's the correct way to do it, but it worked at least ^^
[11:45] <lighterowl> /usr/share/applications is for system-wide menus, while user ones should go to ~/.local/share/applications.
[11:46] <hans_> thanks
[16:43] <Ural> People, maybe we help me? Please.. I press left mouse key, for set desktop background - but not see background pictures (wallpapers) in folder for it. This wallpapers exist in folder, but i not see its in desktop-settings manager.
[16:48] <lighterowl> you mean the right mouse key :)
[16:49] <lighterowl> Ural: are you sure you've got the right "Folder:" selected under the available thumbnails? I fall for this from time to time.
[16:58] <Ural> In this folder exist wallpapers in jpg
[17:01] <lighterowl> Ural: the only thing that comes to mind is running "xfdesktop-settings -e" from the console and searching the debug log for the name of the file. perhaps there's something blocking the application from reading it.
[17:07] <Ural> Thanks! I do it and see wallpapers
[17:07] <lighterowl> oh
[17:07] <lighterowl> that's surprising. :
[17:07] <lighterowl> :)
[17:07] <Ural> But if i try to change it, it write
[17:09] <Ural> backdrop screen0 monitor0 workspace0 last-image DBG[main.c:1141] cb_folder_selection_changed(): folder didn't change
[17:15] <lighterowl> if you search the log for the name of the file you want to use, does it find anything?
[17:15] <Ural> and (xfdesktop-settings:5689): GLib-GIO-CRITICAL **: 22:14:50.405: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
[17:16] <lighterowl> wow, it's really late over there.
[17:17] <lighterowl> Ural: that sounds like the thumbnailer wasn't running and the desktop settings application cannot connect to it ... which is weird.
[17:18] <Ural> Hmmm
[17:18] <lighterowl> Ural: if you run "pgrep tumblerd" in the console, is there any output?
[17:19] <Ural> 5698
[17:20] <lighterowl> huh.
[17:24] <lighterowl> Ural: the only thing that comes to mind is forcing a refresh of the thumbnails by creating a new thumbnail cache. if that won't work, then I have no idea what might be wrong.
[17:25] <Ural> And how i can to do it?
[17:25] <Ural> Creating new thrumbnal cache?
[17:25] <lighterowl> mv ~/.cache/thumbnails ~/.cache/thumbnails.backup
[17:25] <lighterowl> this will move the current thumbnail cache directory to a backup one, so if you run xfdesktop-settings again, the cache should be recreated.
[17:27] <Ural> Thanks a lot!!! All work!! Work again. Super!!
[17:28] <lighterowl> не за что, спокойной ночи :)
[17:33] <Ural> Спасибо!!!
[20:26] <xubuntu52w> I attempted to a distribution upgrade from 18.04 to 19.10, but it got stuck at the installation stage. It unpacked some libc packages, but then got stuck at "De-configuring libc6:i386 (2.27-3ubuntu1) ...". It has been there for over a day. After killing the upgrade, how do I make sure I don't end up with a broken system? I want to avoid doing a
[20:26] <xubuntu52w> reinstall.
[20:28] <gnrp> xubuntu52w: Try on the console a `dpkg --configure -a`
[21:46] <emant999x> hello